From ihsan at opencsw.org Sat Nov 1 00:21:41 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Sat, 01 Nov 2008 00:21:41 +0100 Subject: [csw-maintainers] new build sparc: zooommm.... In-Reply-To: <20081031125610.Q95235@bolthole.com> References: <20081031125610.Q95235@bolthole.com> Message-ID: <490B9305.1040207@opencsw.org> Am 31.10.2008 20:56 Uhr, Philip Brown schrieb: > It's a direct-access box, so whoever handles DNS, could put an entry for it. > I'm thinking sparc8s.go.opencsw.org perhaps? That's me. :-) > ("go" for "gore", like "bo" was for "baltic online". I dunno) build8s.go.opencsw.org points now to 157.204.22.39. Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From dam at opencsw.org Sat Nov 1 09:35:26 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 1 Nov 2008 09:35:26 +0100 Subject: [csw-maintainers] new build sparc: zooommm.... In-Reply-To: <20081031143556.V95235@bolthole.com> References: <20081031125610.Q95235@bolthole.com> <1557267B-888A-4D97-8C70-2C7DF6839BFF@opencsw.org> <490B7553.7030602@opencsw.org> <7DE89681-8B96-486F-94A7-3D16066AD67E@opencsw.org> <20081031143556.V95235@bolthole.com> Message-ID: <74ADF476-F62F-4497-A22F-737E1FAA7F25@opencsw.org> Hi, Am 31.10.2008 um 22:35 schrieb Philip Brown: > On Fri, Oct 31, 2008 at 10:24:45PM +0100, Dagobert Michelsen wrote: >>> If anyone has Solaris 8 x86 ISOs it should be possible to set that >>> up in >>> a VMWare instance on any machine. >> >> Unfortunately not, as ESX emulates only SCSI busses and there >> is no driver for it in Solaris 8 x86. > > But perhaps there is a need for a solaris 8 driver for the *specific* > scsi bus controller ESX provides. That's what I meant. It was late yesterday :-P > There certainly seem to be lots of web pages complaining that > solaris 8 > does not run under ESX. Am 31.10.2008 um 23:30 schrieb Trygve Laugst?l: >> Unfortunately not, as ESX emulates only SCSI busses and there >> is no driver for it in Solaris 8 x86. If you have a solution >> for this I'd virtualize it immediately. > > The latest release actually support Solaris 8. Did you manage to run Solaris 8 x86 under VMware ESX 3.0.2 or 3.5? If yes, I would like to know what SCSI driver you used. > As you say, though, probably better to run under solaris 10 if that is > an option. That would only help 50% as library packages for 32 and 64 bit must be compiled under Solaris 8 and 10 - we must have both in one farm or you can't build lots of packages. Best regards -- Dago From glaw at opencsw.org Sat Nov 1 11:33:38 2008 From: glaw at opencsw.org (Gary Law) Date: Sat, 1 Nov 2008 10:33:38 +0000 Subject: [csw-maintainers] Topics for IRL In-Reply-To: <343A2AE3-DFC1-4B14-911F-67161138B3B4@opencsw.org> References: <343A2AE3-DFC1-4B14-911F-67161138B3B4@opencsw.org> Message-ID: 2008/10/31 Dagobert Michelsen > > > * **Source**. > (*) The project should formally adopt GAR for Sol 9 and 10 builds and make use of GAR mandatory for all packages. Future Solaris packaging standards might mean a switch to pkgbuild or something else entirely. Incidentally, not all my packages are in GAR and I don't like it as a tool, however, maintainers having private scripts to build stuff is untransparent and makes taking on the maintenance of an existing package very difficult in some cases. > * **Key**. > (*) The Key should be owned by all of and only the board members. > > * **Board**. > For me this is the most important point. The > nomination/election is one of the keys on the meeting. (*) Can maintainers who don't attend vote? > > * **Release Process**. > You might want to take a look at Hudson, which is a nice Continuous Integration server that I've used for automated builds in the past. > > * **Distributed**. > > I don't know if distribution is really that good +1 > . ... It may be sufficient to replicate the server > backups to different people so the infrastructure can be > rebuild quickly if anything happens. (*) The board members should maintain the infrastructure (delegating to corporations or people as they see fit). Everything should be replicated in two places, ideally I guess one in Europe and one in North America. LDAP, SVN, DNS, web servers, wiki servers... all of these things can be made to work in a fully redundant fashion across a WAN. NFS might be a struggle though. (*) I've got one more, and this is probably going to be a little controversial... we should move out of /opt/csw and into /opt/opencsw. Blastwave Inc is still distributing into /opt/csw and the scope for end user confusion and incompatible software releases is huge. Although this sounds like a lot of work, if everything is in GAR, and everything needs to be rebuilt for Sol 9 in the next six months, it's really not a lot of extra work. I've got big reservations about maintaining stuff through opencsw that installs into /opt/csw. -- Gary Law glaw at opencsw.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From dam at opencsw.org Sat Nov 1 11:54:40 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 1 Nov 2008 11:54:40 +0100 Subject: [csw-maintainers] Topics for IRL In-Reply-To: References: <343A2AE3-DFC1-4B14-911F-67161138B3B4@opencsw.org> Message-ID: <4DE07271-5CBD-4022-B736-9248070EB132@opencsw.org> Hi Gary, Am 01.11.2008 um 11:33 schrieb Gary Law: > 2008/10/31 Dagobert Michelsen > > > * **Source**. > > (*) The project should formally adopt GAR for Sol 9 and 10 builds > and make use of GAR mandatory for all packages. That would be good, yes. However, we have quite a mount of existing packages which are not in GAR and which are currently orphaned. Would you drop them? > Future Solaris packaging standards might mean a switch to pkgbuild > or something else entirely. It will become mandatory when Solaris 10 support is dropped. Until then, we have to produce System V packages, and that will be for quite some years from now. > Incidentally, not all my packages are in GAR and I don't like it as > a tool, however, maintainers having private scripts to build stuff > is untransparent and makes taking on the maintenance of an existing > package very difficult in some cases. If I can help you moving your packages to GAR let me know. Currently I am preparing some more docs and a presentation with an introduction to GAR to be held during IRL. > > * **Key**. > > (*) The Key should be owned by all of and only the board members. That could be a solution and should be discussed during the meeting. > > * **Board**. > For me this is the most important point. The > nomination/election is one of the keys on the meeting. > > (*) Can maintainers who don't attend vote? Not for the board at this time. If I got Ihsan correctly, it is mandatory in Swiss law for the incorporated society to meet in person at least once. After the founding, the board can accept members which have a right to vote. After that "remote-elections" should be possible. > > * **Release Process**. > > You might want to take a look at Hudson, which is a nice Continuous > Integration server that I've used for automated builds in the past. Like this :-) http://buildfarm.opencsw.org/hudson/ It will become fully functional when a package can be checked out individually (without checking out the whole tree). Trygve set this up, thanks! > > * **Distributed**. > > I don't know if distribution is really that good > > +1 > > . ... It may be sufficient to replicate the server > backups to different people so the infrastructure can be > rebuild quickly if anything happens. > > (*) The board members should maintain the infrastructure > (delegating to corporations or people as they see fit). Everything > should be replicated in two places, ideally I guess one in Europe > and one in North America. LDAP, SVN, DNS, web servers, wiki > servers... all of these things can be made to work in a fully > redundant fashion across a WAN. NFS might be a struggle though. > > (*) I've got one more, and this is probably going to be a little > controversial... we should move out of /opt/csw and into /opt/ > opencsw. Blastwave Inc is still distributing into /opt/csw and the > scope for end user confusion and incompatible software releases is > huge. Although this sounds like a lot of work, if everything is in > GAR, and everything needs to be rebuilt for Sol 9 in the next six > months, it's really not a lot of extra work. I've got big > reservations about maintaining stuff through opencsw that installs > into /opt/csw. Difficult. *If* we change the prefix, then there must be a converter for installation to go from csw/ to opencsw/, but personally I would like to postpone that until we see how each project performs. Discussion welcome. Best regards -- Dago -------------- next part -------------- An HTML attachment was scrubbed... URL: From garylaw at garylaw.net Sat Nov 1 13:17:42 2008 From: garylaw at garylaw.net (Gary Law) Date: Sat, 1 Nov 2008 12:17:42 +0000 Subject: [csw-maintainers] Topics for IRL In-Reply-To: <4DE07271-5CBD-4022-B736-9248070EB132@opencsw.org> References: <343A2AE3-DFC1-4B14-911F-67161138B3B4@opencsw.org> <4DE07271-5CBD-4022-B736-9248070EB132@opencsw.org> Message-ID: Hi Dago 2008/11/1 Dagobert Michelsen > Hi Gary, > Am 01.11.2008 um 11:33 schrieb Gary Law: > > 2008/10/31 Dagobert Michelsen > >> >> > * **Source**. >> > > (*) The project should formally adopt GAR for Sol 9 and 10 builds and make > use of GAR mandatory for all packages. > > > That would be good, yes. However, we have quite a mount of existing > packages which are not in GAR and which are currently orphaned. Would > you drop them? > Not immediately. I believe the Solaris 8 end of support is March 2009, so I'd make that the target date for a new system. Everything built on Solaris 9, out of GAR (and with a new install path -- see below). > > If I can help you moving your packages to GAR let me know. > Currently I am preparing some more docs and a presentation > with an introduction to GAR to be held during IRL. > Thanks. I have an absolute pig of a package to deal with. > (*) Can maintainers who don't attend vote? > > Not for the board at this time. If I got Ihsan correctly, > it is mandatory in Swiss law for the incorporated society > to meet in person at least once. After the founding, the > board can accept members which have a right to vote. > After that "remote-elections" should be possible. > Great. Please hold an all-maintainers election ASAP after incorporation. I don't suppose it would be likely to change the composition of the board, but would give maintainers a sense of ownership. > > > * **Release Process**. > > You might want to take a look at Hudson, which is a nice Continuous > Integration server that I've used for automated builds in the past. > > > Like this :-) > http://buildfarm.opencsw.org/hudson/ > Oh fantastic. If you dive deep enough through the links eventually absolute links to: http://hudson:8070 start appearing, which don't work. Still, this is completely the right way to go IMHO. I'll try and get my packages in there. > > > (*) I've got one more, and this is probably going to be a little > controversial... we should move out of /opt/csw and into /opt/opencsw. > Blastwave Inc is still distributing into /opt/csw and the scope for end user > confusion and incompatible software releases is huge. Although this sounds > like a lot of work, if everything is in GAR, and everything needs to be > rebuilt for Sol 9 in the next six months, it's really not a lot of extra > work. I've got big reservations about maintaining stuff through opencsw that > installs into /opt/csw. > > > Difficult. *If* we change the prefix, then there must be a > converter for installation to go from csw/ to opencsw/, but > personally I would like to postpone that until we see how > each project performs. Discussion welcome. > > Like changing to GAR only, it would be impossible overnight. But set a target date six months out, and I think it's realistic to get everything rebuilt, out of version controlled repo, off the new minimum standard (Solaris 9). We might loose a few packages or maintainers along the way, but end up in a much better place for running and maintaining the project long term. Also, what's the alternative? Having two projects targeting the same install path? That is not sustainable going forward and the project's credibility will suffer. Gary -- Gary Law glaw at opencsw.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From dam at opencsw.org Sat Nov 1 13:39:04 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 1 Nov 2008 13:39:04 +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: Hi Gary, Am 01.11.2008 um 13:17 schrieb Gary Law: >> > * **Release Process**. >> >> You might want to take a look at Hudson, which is a nice >> Continuous Integration server that I've used for automated builds >> in the past. > > Like this :-) > http://buildfarm.opencsw.org/hudson/ > > Oh fantastic. If you dive deep enough through the links eventually > absolute links to: > http://hudson:8070 > start appearing, which don't work. Oops. Trygve, any clues how to fix this? > Still, this is completely the right way to go IMHO. I'll try and > get my packages in there. This will be done automatically once we have single package checkout in GAR. Auto-build on commit :-) > >> (*) I've got one more, and this is probably going to be a little >> controversial... we should move out of /opt/csw and into /opt/ >> opencsw. Blastwave Inc is still distributing into /opt/csw and the >> scope for end user confusion and incompatible software releases is >> huge. Although this sounds like a lot of work, if everything is in >> GAR, and everything needs to be rebuilt for Sol 9 in the next six >> months, it's really not a lot of extra work. I've got big >> reservations about maintaining stuff through opencsw that installs >> into /opt/csw. > > Difficult. *If* we change the prefix, then there must be a > converter for installation to go from csw/ to opencsw/, but > personally I would like to postpone that until we see how > each project performs. Discussion welcome. > > > Like changing to GAR only, it would be impossible overnight. But > set a target date six months out, and I think it's realistic to get > everything rebuilt, out of version controlled repo, off the new > minimum standard (Solaris 9). We might loose a few packages or > maintainers along the way, but end up in a much better place for > running and maintaining the project long term. That would imply to also change the package prefix CSW to something else. I completely agree that it is a Bad Thing(TM) to have two projects work on the same prefix. However, the "inheritor" of CSW (Phil, after Alan DuBoff) is at OpenCSW and most of the maintainers too. I don't know how they feel about changing the prefix. Personally, I think OpenCSW has the moral right to stick to /opt/csw, but that is just my opinion and I would accept a majority decision on this of course. Fellow maintainers, what do you think? > Also, what's the alternative? Having two projects targeting the > same install path? That is not sustainable going forward and the > project's credibility will suffer. The question is: will the maintainers here will accept leaving the prefix to Blastwave and start with a new one. Apart from that it would be cool to allow customized package trees with different suffixes (e. g. like optimized trees for T1/T2). However, that would impose quite an extra amount for package maintainers (not for all, but there are nasty ones). Best regards -- Dago -------------- next part -------------- An HTML attachment was scrubbed... URL: From garylaw at garylaw.net Sat Nov 1 14:38:42 2008 From: garylaw at garylaw.net (Gary Law) Date: Sat, 1 Nov 2008 13:38:42 +0000 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: 2008/11/1 Dagobert Michelsen > > Still, this is completely the right way to go IMHO. I'll try and get my > packages in there. > > > This will be done automatically once we have single package > checkout in GAR. Auto-build on commit :-) > Yay! Exactly the way it should be. :) > > Personally, I think OpenCSW has the > moral right to stick to /opt/csw > Having the moral right is all well and good, but it is not pragmatic to use /opt/csw indefinitely. > The question is: will the maintainers here will accept leaving the > prefix to Blastwave and start with a new one. > I could be wrong, but I guess most maintainers want it somewhere in /opt that no-one else is using. > > Apart from that it would be cool to allow customized package trees > with different suffixes (e. g. like optimized trees for T1/T2). > However, that would impose quite an extra amount for package > maintainers (not for all, but there are nasty ones). > If we get everything in GAR, and automated builds, lots of stuff becomes loads easier. Gary -- Gary Law glaw at opencsw.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From bonivart at opencsw.org Sat Nov 1 15:13:53 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Sat, 1 Nov 2008 15:13:53 +0100 Subject: [csw-maintainers] Want to test an alternative to pkg-get? In-Reply-To: References: <625385e30809190604x4c76f8fdsb380ccc9fb00165f@mail.gmail.com> Message-ID: <625385e30811010713u5bfe39cdl761fc488a034c19@mail.gmail.com> This is really weird, I just got this mail and I see that you sent it September 23rd, according to the headers it's been sitting on an opencsw mail server until today. Maybe your gmail account wasn't allowed to post to the list and it has been stuck waiting for approval. I use gmail too but I've set it up to send as my opencsw account. When I forget to change my from address the same thing happens. On Tue, Sep 23, 2008 at 10:57 AM, Gary Law wrote: > (*) the pkgtool installer wants my /opt to be root:bin, not root:sys Version 1.1 has a trimmed prototype that doesn't include /etc/opt, /opt and /var/opt to minimize risk of modifying the attributes of already existing directories. > (*) there's no mention of the configuration file in the man page. How do I > set which mirrors to use? ibiblio seems to be the default mirror which is > hard coded into the tool, and the pkgtool.conf file is referenced by the > code too, but it's format is undocumented. AFAIK ibiblio is mirroring > packages off of Blastwave Inc., not opencsw. I'll look into improving the man page. Please look at http://wiki.opencsw.org/pkgutil for more info, also in 1.1 the conf-file is better documented. I think the mirror issue has finally been settled, ibiblio as an example has chosen to mirror blastwave as blastwave and opencsw as opencsw, the old csw path has been removed. The path should be correct in 1.1. > (*) My gut feel, completely untested, is this is faster than pkg-get. I have done some simple tests and it's usually faster than pkg-get but some may think pkg-get is faster because it gets busy right away downloading and extracting packages so it can find dependencies. Pkgutil may seem slower at the beginning when it's presenting new, updated and current packages but to me that info is really valuable. I haven't optimized the algorithms either yet so there may be better speed in the future. Right now I'm mostly working on features. > (*) how is the gpg signing turned on/off? It should be off by default, you have to turn it on by setting that option (use_gpg=true) in pkgutil.conf. If pkgutil doesn't find gpg support it will tell you which package you need to install. > (*) Functionally, works perfectly during my limited tesing. Excellent! > (*) Love the "I'm going to do this now" option. You mean the --nomod option? I've used it a lot during testing. :-) -- /peter From phil at bolthole.com Sat Nov 1 19:32:17 2008 From: phil at bolthole.com (Philip Brown) Date: Sat, 1 Nov 2008 11:32:17 -0700 Subject: [csw-maintainers] OpenCSW Prefix In-Reply-To: ; from dam@opencsw.org on Sat, Nov 01, 2008 at 01:39:04PM +0100 References: <343A2AE3-DFC1-4B14-911F-67161138B3B4@opencsw.org> <4DE07271-5CBD-4022-B736-9248070EB132@opencsw.org> Message-ID: <20081101113217.A82853@bolthole.com> On Sat, Nov 01, 2008 at 01:39:04PM +0100, Dagobert Michelsen wrote: > That would imply to also change the package prefix CSW to something > else. > I completely agree that it is a Bad Thing(TM) to have two projects work > on the same prefix. However, the "inheritor" of CSW (Phil, after Alan > DuBoff) is at OpenCSW and most of the maintainers too. I don't know how > they feel about changing the prefix. Personally, I think OpenCSW has the > moral right to stick to /opt/csw, but that is just my opinion and I > would accept a majority decision on this of course. > > Fellow maintainers, what do you think? Additionally, someone once said that blastwave maintainers (a few months ago) were supposedly already planning to move THEIR stuff to stop using "CSW". I'm guessing that Dennis decided against that, because he likes to claim he owns everything. But he does NOT own CSW. For us to change, undermines us, in my opinion. From ihsan at opencsw.org Sat Nov 1 21:30:48 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Sat, 01 Nov 2008 21:30:48 +0100 Subject: [csw-maintainers] Want to test an alternative to pkg-get? In-Reply-To: <625385e30811010713u5bfe39cdl761fc488a034c19@mail.gmail.com> References: <625385e30809190604x4c76f8fdsb380ccc9fb00165f@mail.gmail.com> <625385e30811010713u5bfe39cdl761fc488a034c19@mail.gmail.com> Message-ID: <490CBC78.9080300@opencsw.org> Am 1.11.2008 15:13 Uhr, Peter Bonivart schrieb: > This is really weird, I just got this mail and I see that you sent it > September 23rd, according to the headers it's been sitting on an > opencsw mail server until today. Maybe your gmail account wasn't > allowed to post to the list and it has been stuck waiting for > approval. I use gmail too but I've set it up to send as my opencsw > account. When I forget to change my from address the same thing > happens. You have to use your @opencsw.org address to post to this list and his mail was hold by the malinglist software. Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From glaw at opencsw.org Sat Nov 1 21:37:44 2008 From: glaw at opencsw.org (Gary Law) Date: Sat, 1 Nov 2008 20:37:44 +0000 Subject: [csw-maintainers] OpenCSW Prefix In-Reply-To: <20081101113217.A82853@bolthole.com> References: <343A2AE3-DFC1-4B14-911F-67161138B3B4@opencsw.org> <4DE07271-5CBD-4022-B736-9248070EB132@opencsw.org> <20081101113217.A82853@bolthole.com> Message-ID: Hi Phil 2008/11/1 Philip Brown > > > Fellow maintainers, what do you think? > > Additionally, someone once said that blastwave maintainers (a few months > ago) were supposedly already planning to move THEIR stuff to stop using > "CSW". Were it to happen, of course, that would be great. But there is no evidence of this actually happening. > I'm guessing that Dennis decided against that, because he likes to claim he > owns everything. > But he does NOT own CSW. > > > For us to change, undermines us, in my opinion. > I'm not sure in what way a change to a directory path undermines opencsw. I am sure that if both organisations plough on regardless using /opt/csw it will undermine both parties -- it clearly isn't in the best interests of end users. And now I come to think of it, the dependency declarations are also going to be impossible to reliably resolve if two organisations produce software called CSWfoo, CSWbar... Gary -- Gary Law -------------- next part -------------- An HTML attachment was scrubbed... URL: From phil at bolthole.com Sat Nov 1 22:05:42 2008 From: phil at bolthole.com (Philip Brown) Date: Sat, 1 Nov 2008 14:05:42 -0700 Subject: [csw-maintainers] OpenCSW Prefix In-Reply-To: ; from glaw@opencsw.org on Sat, Nov 01, 2008 at 08:37:44PM +0000 References: <343A2AE3-DFC1-4B14-911F-67161138B3B4@opencsw.org> <4DE07271-5CBD-4022-B736-9248070EB132@opencsw.org> <20081101113217.A82853@bolthole.com> Message-ID: <20081101140542.C82853@bolthole.com> On Sat, Nov 01, 2008 at 08:37:44PM +0000, Gary Law wrote: > I am sure that if both organisations plough on regardless using /opt/csw it > will undermine both parties -- it clearly isn't in the best interests of end > users. > > And now I come to think of it, the dependency declarations are also going to > be impossible to reliably resolve if two organisations produce software > called CSWfoo, CSWbar... what is the problem? its not like someone would want to use both sets of packages From glaw at opencsw.org Sat Nov 1 22:52:58 2008 From: glaw at opencsw.org (Gary Law) Date: Sat, 1 Nov 2008 21:52:58 +0000 Subject: [csw-maintainers] OpenCSW Prefix In-Reply-To: <20081101140542.C82853@bolthole.com> References: <343A2AE3-DFC1-4B14-911F-67161138B3B4@opencsw.org> <4DE07271-5CBD-4022-B736-9248070EB132@opencsw.org> <20081101113217.A82853@bolthole.com> <20081101140542.C82853@bolthole.com> Message-ID: 2008/11/1 Philip Brown > > > > And now I come to think of it, the dependency declarations are also going > to > > be impossible to reliably resolve if two organisations produce software > > called CSWfoo, CSWbar... > > what is the problem? > its not like someone would want to use both sets of packages > It's highly likely someone will intentionally want to use both. There are already packages in one and not the other. And versions are different for many things. Equally concerning is that people will accidentally use both. If they change mirror to the wrong upstream things won't work as they should. Users will become annoyed when they find out why, and go back to downloading by hand from Sunfreeware. The whole point of using things like /opt/$NAME for directories and prefixing the package name is to prevent namespace clashes ... I stand by my opinion that both Blastwave and opencsw are going to look very, very foolish if they both distribute into /opt/csw. -- Gary Law glaw at opencsw.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From ihsan at opencsw.org Sun Nov 2 13:44:58 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Sun, 02 Nov 2008 13:44:58 +0100 Subject: [csw-maintainers] IRL Meeting - new date Message-ID: <490DA0CA.1020008@opencsw.org> Hello, I've been talking with Phil about the IRL meeting and for him it would be possible, to attend to the IRL meeting, if it's taking place on 5/6/7 December. As far Phil would come from far way (it's a 12 hours flight for him), I would like to ask, if it's possible for you guys to postpone this date. Please let me know, so we can plan something for this date. Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From ihsan at opencsw.org Sun Nov 2 14:38:47 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Sun, 02 Nov 2008 14:38:47 +0100 Subject: [csw-maintainers] OpenCSW maintainers list now public Message-ID: <490DAD67.60203@opencsw.org> Hello, As already mentioned, all posts after 1st November are public! The mailing list is announced on https://lists.opencsw.org/mailman/listinfo and the archive is readable on http://lists.opencsw.org/pipermail/maintainers/ . Only maintainers can post to the list. Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From trygvel at opencsw.org Sun Nov 2 15:10:39 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sun, 02 Nov 2008 15:10:39 +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: <490DB4DF.1040802@opencsw.org> Dagobert Michelsen wrote: > Hi Gary, > > Am 01.11.2008 um 13:17 schrieb Gary Law: >> >>> > * **Release Process**. >>> >>> You might want to take a look at Hudson, which is a nice >>> Continuous Integration server that I've used for automated builds >>> in the past. >> >> Like this :-) >> http://buildfarm.opencsw.org/hudson/ >> >> >> Oh fantastic. If you dive deep enough through the links eventually >> absolute links to: >> http://hudson:8070 >> start appearing, which don't work. > > Oops. Trygve, any clues how to fix this? Odd. Where did you find that link? >> Still, this is completely the right way to go IMHO. I'll try and get >> my packages in there. > > This will be done automatically once we have single package > checkout in GAR. Auto-build on commit :-) > >> >>> (*) I've got one more, and this is probably going to be a little >>> controversial... we should move out of /opt/csw and into >>> /opt/opencsw. Blastwave Inc is still distributing into /opt/csw >>> and the scope for end user confusion and incompatible software >>> releases is huge. Although this sounds like a lot of work, if >>> everything is in GAR, and everything needs to be rebuilt for Sol >>> 9 in the next six months, it's really not a lot of extra work. >>> I've got big reservations about maintaining stuff through opencsw >>> that installs into /opt/csw. >> >> Difficult. *If* we change the prefix, then there must be a >> converter for installation to go from csw/ to opencsw/, but >> personally I would like to postpone that until we see how >> each project performs. Discussion welcome. >> >> >> Like changing to GAR only, it would be impossible overnight. But set a >> target date six months out, and I think it's realistic to get >> everything rebuilt, out of version controlled repo, off the new >> minimum standard (Solaris 9). We might loose a few packages or >> maintainers along the way, but end up in a much better place for >> running and maintaining the project long term. > > That would imply to also change the package prefix CSW to something else. > I completely agree that it is a Bad Thing(TM) to have two projects work > on the same prefix. However, the "inheritor" of CSW (Phil, after Alan > DuBoff) is at OpenCSW and most of the maintainers too. I don't know how > they feel about changing the prefix. Personally, I think OpenCSW has the > moral right to stick to /opt/csw, but that is just my opinion and I would > accept a majority decision on this of course. > > Fellow maintainers, what do you think? > >> Also, what's the alternative? Having two projects targeting the same >> install path? That is not sustainable going forward and the project's >> credibility will suffer. > > The question is: will the maintainers here will accept leaving the > prefix to Blastwave and start with a new one. > > Apart from that it would be cool to allow customized package trees > with different suffixes (e. g. like optimized trees for T1/T2). > However, that would impose quite an extra amount for package > maintainers (not for all, but there are nasty ones). I don't care what we do as all the packages should be rebuilt for Solaris 9+ anyway, but the only thing that matters is what our consumers need. If we are to move we really need to document how to transition from the Original Blastwave packages to the new OpenCSW packages. Perhaps it is an alternative to use /opt/opencsw for the binary root and use /etc/opt/csw for configuration files? -- Trygve From trygvel at opencsw.org Sun Nov 2 15:13:30 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sun, 02 Nov 2008 15:13:30 +0100 Subject: [csw-maintainers] IRL Meeting - new date In-Reply-To: <490DA0CA.1020008@opencsw.org> References: <490DA0CA.1020008@opencsw.org> Message-ID: <490DB58A.6090000@opencsw.org> Ihsan Dogan wrote: > Hello, > > I've been talking with Phil about the IRL meeting and for him it would > be possible, to attend to the IRL meeting, if it's taking place on 5/6/7 > December. > > As far Phil would come from far way (it's a 12 hours flight for him), I > would like to ask, if it's possible for you guys to postpone this date. > > Please let me know, so we can plan something for this date. Works for me. -- Trygve From Murray.Jensen at csiro.au Sun Nov 2 15:19:14 2008 From: Murray.Jensen at csiro.au (Murray.Jensen at csiro.au) Date: Mon, 3 Nov 2008 01:19:14 +1100 Subject: [csw-maintainers] new packages pymxbase and pypgsql for testing Message-ID: <9085.1225635554@gerd> Unfortunately I don't have access to the testing area so they are sitting in my home directory on www.opencsw.org (/home/mjensen) ... 7ca5cc173202e77c55d0f795b932e5eb pymxbase-3.1.1,REV=2008.10.31-SunOS5.8-i386-CSW.pkg.gz c931403b91add50a0032fee98a03fcd6 pymxbase-3.1.1,REV=2008.10.31-SunOS5.8-sparc-CSW.pkg.gz 81aae9076588e4c1e70aec4e8e4d8c10 pypgsql-2.5.1,REV=2008.11.01-SunOS5.8-i386-CSW.pkg.gz 5c338d5a2dcb414296eff3e2c1fcd53a pypgsql-2.5.1,REV=2008.11.01-SunOS5.8-sparc-CSW.pkg.gz If some kind soul could put them into testing I'd appreciate it. Cheers! Murray... PS: I am not maintainer for these, but I noticed a conflict when using a python script (cvs2svn) and the maintainer was marked as retired so I just went ahead and built them - it was almost trivial anyway, python modules seem to do everything for you. From glaw at opencsw.org Sun Nov 2 15:54:39 2008 From: glaw at opencsw.org (Gary Law) Date: Sun, 2 Nov 2008 14:54:39 +0000 Subject: [csw-maintainers] OpenCSW Prefix In-Reply-To: <490DB4DF.1040802@opencsw.org> References: <343A2AE3-DFC1-4B14-911F-67161138B3B4@opencsw.org> <4DE07271-5CBD-4022-B736-9248070EB132@opencsw.org> <490DB4DF.1040802@opencsw.org> Message-ID: 2008/11/2 Trygve Laugst?l > >> Like this :-) > >> http://buildfarm.opencsw.org/hudson/ > >> > >> > >> Oh fantastic. If you dive deep enough through the links eventually > >> absolute links to: > >> http://hudson:8070 > >> start appearing, which don't work. > > > > Oops. Trygve, any clues how to fix this? > > Odd. Where did you find that link? > go here: http://buildfarm.opencsw.org/hudson/ click new job (top left) takes you here: http://buildfarm.opencsw.org/hudson/newJob job name: test - ignore - 3 select copy job from, and input jetty6 - sparc-solaris2.8 click ok, takes you here: http://hudson:8070/hudson/job/test%202%20--%20ignore/configure > I don't care what we do as all the packages should be rebuilt for > Solaris 9+ anyway, but the only thing that matters is what our consumers > need. > > If we are to move we really need to document how to transition from the > Original Blastwave packages to the new OpenCSW packages. Perhaps it is > an alternative to use /opt/opencsw for the binary root and use > /etc/opt/csw for configuration files? > you'll hit collisions again if you go for /etc/opt/csw ... needs to be /etc/opt/opencsw too... B T W has anyone got a link to the GAR documentation? All the pages on the opencsw site talk about building things the long/difficult/many manual steps way... Thanks Gary -- Gary Law glaw at opencsw.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From william at wbonnet.net Sun Nov 2 17:10:22 2008 From: william at wbonnet.net (William Bonnet) Date: Sun, 02 Nov 2008 16:10:22 +0000 Subject: [csw-maintainers] IRL Meeting - new date In-Reply-To: <490DB58A.6090000@opencsw.org> References: <490DA0CA.1020008@opencsw.org> <490DB58A.6090000@opencsw.org> Message-ID: <490DD0EE.50108@wbonnet.net> Hi >> Hello, >> >> I've been talking with Phil about the IRL meeting and for him it would >> be possible, to attend to the IRL meeting, if it's taking place on 5/6/7 >> December. >> >> As far Phil would come from far way (it's a 12 hours flight for him), I >> would like to ask, if it's possible for you guys to postpone this date. >> >> Please let me know, so we can plan something for this date. >> > > Works for me. > It works for me. I confirm i'll be there. cheers, W. From ihsan at opencsw.org Sun Nov 2 16:43:13 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Sun, 02 Nov 2008 16:43:13 +0100 Subject: [csw-maintainers] new packages pymxbase and pypgsql for testing In-Reply-To: <9085.1225635554@gerd> References: <9085.1225635554@gerd> Message-ID: <490DCA91.2090102@opencsw.org> Am 2.11.2008 15:19 Uhr, Murray.Jensen at csiro.au schrieb: > Unfortunately I don't have access to the testing area so they are sitting > in my home directory on www.opencsw.org (/home/mjensen) ... Oups, there was no /testing. /home/testing is now www.opencsw.org/testing > 7ca5cc173202e77c55d0f795b932e5eb pymxbase-3.1.1,REV=2008.10.31-SunOS5.8-i386-CSW.pkg.gz > c931403b91add50a0032fee98a03fcd6 pymxbase-3.1.1,REV=2008.10.31-SunOS5.8-sparc-CSW.pkg.gz > 81aae9076588e4c1e70aec4e8e4d8c10 pypgsql-2.5.1,REV=2008.11.01-SunOS5.8-i386-CSW.pkg.gz > 5c338d5a2dcb414296eff3e2c1fcd53a pypgsql-2.5.1,REV=2008.11.01-SunOS5.8-sparc-CSW.pkg.gz > > If some kind soul could put them into testing I'd appreciate it. Cheers! Ok, just moved them to /home/testing. Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From trygvel at opencsw.org Sun Nov 2 18:05:46 2008 From: trygvel at opencsw.org (=?UTF-8?B?VHJ5Z3ZlIExhdWdzdMO4bA==?=) Date: Sun, 02 Nov 2008 18:05:46 +0100 Subject: [csw-maintainers] OpenCSW Prefix In-Reply-To: References: <343A2AE3-DFC1-4B14-911F-67161138B3B4@opencsw.org> <4DE07271-5CBD-4022-B736-9248070EB132@opencsw.org> <490DB4DF.1040802@opencsw.org> Message-ID: <490DDDEA.9030305@opencsw.org> Gary Law wrote: > 2008/11/2 Trygve Laugst?l > > > >> Like this :-) > >> http://buildfarm.opencsw.org/hudson/ > >> > >> > >> Oh fantastic. If you dive deep enough through the links eventually > >> absolute links to: > >> http://hudson:8070 > >> start appearing, which don't work. > > > > Oops. Trygve, any clues how to fix this? > > Odd. Where did you find that link? > > > go here: > http://buildfarm.opencsw.org/hudson/ > click new job (top left) > takes you here: > http://buildfarm.opencsw.org/hudson/newJob > job name: test - ignore - 3 > select copy job from, and input > jetty6 - sparc-solaris2.8 > click ok, takes you here: > http://hudson:8070/hudson/job/test%202%20--%20ignore/configure Thanks, I'll take a look once I have some time. -- Trygve From dam at opencsw.org Sun Nov 2 21:20:16 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 2 Nov 2008 21:20:16 +0100 Subject: [csw-maintainers] IRL Meeting - new date In-Reply-To: <490DA0CA.1020008@opencsw.org> References: <490DA0CA.1020008@opencsw.org> Message-ID: <52F94DAC-0BD3-4CB2-8BB1-010FA9B12591@opencsw.org> Hi Ihsan, Am 02.11.2008 um 13:44 schrieb Ihsan Dogan: > I've been talking with Phil about the IRL meeting and for him it would > be possible, to attend to the IRL meeting, if it's taking place on > 5/6/7 > December. > > As far Phil would come from far way (it's a 12 hours flight for > him), I > would like to ask, if it's possible for you guys to postpone this > date. > > Please let me know, so we can plan something for this date. Sure I'll be there. Best regards -- Dago From ihsan at opencsw.org Sun Nov 2 21:34:09 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Sun, 02 Nov 2008 21:34:09 +0100 Subject: [csw-maintainers] IRL Meeting - new date In-Reply-To: <52F94DAC-0BD3-4CB2-8BB1-010FA9B12591@opencsw.org> References: <490DA0CA.1020008@opencsw.org> <52F94DAC-0BD3-4CB2-8BB1-010FA9B12591@opencsw.org> Message-ID: <490E0EC1.6080802@opencsw.org> Am 2.11.2008 21:20 Uhr, Dagobert Michelsen schrieb: >> Please let me know, so we can plan something for this date. > Sure I'll be there. Thanks. I've updated by the way the wiki page: http://wiki.opencsw.org/irl-meeting Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From dam at opencsw.org Sun Nov 2 23:27:19 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 2 Nov 2008 23:27:19 +0100 Subject: [csw-maintainers] OpenCSW Prefix In-Reply-To: References: <343A2AE3-DFC1-4B14-911F-67161138B3B4@opencsw.org> <4DE07271-5CBD-4022-B736-9248070EB132@opencsw.org> <490DB4DF.1040802@opencsw.org> Message-ID: <40984868-1992-4438-9571-F18CA5BBEC8D@opencsw.org> Hi Gary, Am 02.11.2008 um 15:54 schrieb Gary Law: > B T W has anyone got a link to the GAR documentation? All the pages > on the opencsw site talk about building things the long/difficult/ > many manual steps way... I am currently converting / rewriting the GAR documentation to https://apps.sourceforge.net/mediawiki/gar/index.php?title=Main_Page There is not much there yet, but the newer features like dynamic prototypes and modulated builds haven't been documented at all yet, so please stand by for those. Just if anyone asks: I use the SF Wiki because GAR is also at SF, so the GAR project is fully SF-hosted. Best regards -- Dago From dam at opencsw.org Sun Nov 2 23:47:41 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 2 Nov 2008 23:47:41 +0100 Subject: [csw-maintainers] Java... again! Message-ID: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> Hi, I am currently thinking of packaging the JDKs / JREs to CSW packages. There is this license thing that they may be shipped when an application needs them. How about preventing normal installation but allowing installation when they are listed as dependency? Best regards -- Dago From phil at bolthole.com Mon Nov 3 00:21:11 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 2 Nov 2008 15:21:11 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org>; from dam@opencsw.org on Sun, Nov 02, 2008 at 11:47:41PM +0100 References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> Message-ID: <20081102152111.A95853@bolthole.com> On Sun, Nov 02, 2008 at 11:47:41PM +0100, Dagobert Michelsen wrote: > Hi, > > I am currently thinking of packaging the JDKs / JREs to CSW packages. > There is this license thing that they may be shipped when an application > needs them. How about preventing normal installation but allowing > installation when they are listed as dependency? sounds kinda inappropriate. far as I remember, various linxen have methods to distribute a JRE. So try something similar? From jakegoerzen at gmail.com Mon Nov 3 01:45:13 2008 From: jakegoerzen at gmail.com (Jake Goerzen) Date: Sun, 2 Nov 2008 16:45:13 -0800 Subject: [csw-maintainers] updated pkgs in /testing Message-ID: <315c02ae0811021645w76a5127awc99727e77c8f75e@mail.gmail.com> Hello, The following packages have been created at the build farm and placed in /home/testing: bcc519e0391b6bc71a26b4b7350de8ae libsdl-1.2.13,REV=2008.11.02-SunOS5.8-i386-CSW.pkg.gz efebcbf4b20557b5a6148675b797ee1d libsdl-1.2.13,REV=2008.11.02-SunOS5.8-sparc-CSW.pkg.gz e2a65fd3d41f34ce3e256af238a3b56c sdlttf-2.0.9,REV=2008.11.02-SunOS5.8-i386-CSW.pkg.gz 0cb28851f81998041b3fe615f834887c sdlttf-2.0.9,REV=2008.11.02-SunOS5.8-sparc-CSW.pkg.gz BTW, I noticed that http://www.opencsw.org/testing goes to a different place than http://mirror.opencsw.org/testing. Maybe they should both go to the same place for less confusion? Thanks, Jake -------------- next part -------------- An HTML attachment was scrubbed... URL: From dam at opencsw.org Mon Nov 3 15:13:10 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 3 Nov 2008 15:13:10 +0100 Subject: [csw-maintainers] updated pkgs in /testing In-Reply-To: <315c02ae0811021645w76a5127awc99727e77c8f75e@mail.gmail.com> References: <315c02ae0811021645w76a5127awc99727e77c8f75e@mail.gmail.com> Message-ID: Hi, Am 03.11.2008 um 01:45 schrieb Jake Goerzen: > BTW, I noticed that http://www.opencsw.org/testing goes to a > different place than http://mirror.opencsw.org/testing. Maybe they > should both go to the same place for less confusion? Yes. Having two /testing is a bad idea. Am 03.11.2008 um 03:43 schrieb : > On Mon, 3 Nov 2008 07:28:24 +1100, Dagobert Michelsen writes: >> You do have now :-) I set up a buildfarm account for you on >> login.opencsw.org >> and the most frequently used testing is >> http://buildfarm.opencsw.org/testing/ >> which is available from /home/testing/ from there. You should be able >> to login >> from www.opencsw.org with >> ssh mjensen at login.opencsw.org > > OK, thanks Dago - that all works. So this means we have two /testing > areas now - is that a good idea? Cheers! No again. I have copied them to http://buildfarm.opencsw.org/testing. Ihsan, could you please install a redirect from www.opencsw.org/testing to buildfarm.opencsw.org/testing? Best regards -- Dago -------------- next part -------------- An HTML attachment was scrubbed... URL: From trygvel at opencsw.org Mon Nov 3 16:29:29 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Mon, 03 Nov 2008 16:29:29 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> Message-ID: <490F18D9.7090702@opencsw.org> Dagobert Michelsen wrote: > Hi, > > I am currently thinking of packaging the JDKs / JREs to CSW packages. > There is this license thing that they may be shipped when an application > needs them. How about preventing normal installation but allowing > installation when they are listed as dependency? What Debian and Ubuntu (and possibly others) do is that they have a package to create the Java packages. It take the downloaded bundle as input and give you a .deb out with generated dependency information. We (you) could start there as a starting point. -- Trygve From phil at bolthole.com Mon Nov 3 17:50:11 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 3 Nov 2008 08:50:11 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <490F18D9.7090702@opencsw.org>; from trygvel@opencsw.org on Mon, Nov 03, 2008 at 04:29:29PM +0100 References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> Message-ID: <20081103085011.B95235@bolthole.com> On Mon, Nov 03, 2008 at 04:29:29PM +0100, Trygve Laugst?l wrote: > What Debian and Ubuntu (and possibly others) do is that they have a > package to create the Java packages. It take the downloaded bundle as > input and give you a .deb out with generated dependency information. We > (you) could start there as a starting point. Contrariwise... solaris DOES SHIP with a java runtime! So our "java package", could merely be some kind of user-updatable symlink for /opt/csw/java, to point to /usr/java, for example. Ideally, with some comments and hints in our readme about where to get the latest updates, etc, etc. there's a few varients on this. for example we could have /opt/csw/bin/{jre,java} as symlinks or wrappers to somewhere.... etc, etc. From ihsan at opencsw.org Mon Nov 3 20:05:16 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Mon, 03 Nov 2008 20:05:16 +0100 Subject: [csw-maintainers] updated pkgs in /testing In-Reply-To: References: <315c02ae0811021645w76a5127awc99727e77c8f75e@mail.gmail.com> Message-ID: <490F4B6C.3020403@opencsw.org> Am 3.11.2008 15:13 Uhr, Dagobert Michelsen schrieb: > Ihsan, could you please install a redirect from www.opencsw.org/testing > > to buildfarm.opencsw.org/testing? done -- ihsan at dogan.ch http://blog.dogan.ch/ From dam at opencsw.org Tue Nov 4 11:44:30 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 4 Nov 2008 11:44:30 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081103085011.B95235@bolthole.com> References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> Message-ID: Hi Phil, Am 03.11.2008 um 17:50 schrieb Philip Brown: > On Mon, Nov 03, 2008 at 04:29:29PM +0100, Trygve Laugst?l wrote: >> What Debian and Ubuntu (and possibly others) do is that they have a >> package to create the Java packages. It take the downloaded bundle as >> input and give you a .deb out with generated dependency >> information. We >> (you) could start there as a starting point. > > Contrariwise... solaris DOES SHIP with a java runtime! > So our "java package", could merely be some kind of user-updatable > symlink > for /opt/csw/java, to point to /usr/java, for example. > Ideally, with some comments and hints in our readme about where to > get the > latest updates, etc, etc. > > there's a few varients on this. for example we could have > /opt/csw/bin/{jre,java} as symlinks or wrappers to somewhere.... > etc, etc. There are several reasons why I think it would be nice to have JRE and JDK as CSW packages: 1. Installation would be easier Currently you have to download packages for 32 and 64 bit and issue special install commands instead of pkg-get -i jdk13 jre15 2. Updates would be installed automatically The minor version (like the "2" in 1.4.2) are bugfix releases which would be repackaged ASAP and an 3. Certain CSW packages relying on a specific Java version could just depend on it. I am not sure I got your point in linking to /usr. Extrapolating from our policy I would make the CSW Java independent from the system Java. Best regards -- Dago From trygvel at opencsw.org Tue Nov 4 13:36:00 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Tue, 04 Nov 2008 13:36:00 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081103085011.B95235@bolthole.com> References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> Message-ID: <491041B0.5000501@opencsw.org> Philip Brown wrote: > On Mon, Nov 03, 2008 at 04:29:29PM +0100, Trygve Laugst?l wrote: >> What Debian and Ubuntu (and possibly others) do is that they have a >> package to create the Java packages. It take the downloaded bundle as >> input and give you a .deb out with generated dependency information. We >> (you) could start there as a starting point. > > Contrariwise... solaris DOES SHIP with a java runtime! Uhm, Solaris 8 ships like jdk 1.2 or something. > So our "java package", could merely be some kind of user-updatable symlink > for /opt/csw/java, to point to /usr/java, for example. > Ideally, with some comments and hints in our readme about where to get the > latest updates, etc, etc. > > there's a few varients on this. for example we could have > /opt/csw/bin/{jre,java} as symlinks or wrappers to somewhere.... > etc, etc. To me, depending only on our own packages + base Solaris (of whatever version we're currently basing our stuff on) is what we need to do to deliver quality packages. We need this. Maybe only for building packages, but still. -- Trygve From phil at bolthole.com Tue Nov 4 15:05:17 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 4 Nov 2008 06:05:17 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: ; from dam@opencsw.org on Tue, Nov 04, 2008 at 11:44:30AM +0100 References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> Message-ID: <20081104060517.B68247@bolthole.com> On Tue, Nov 04, 2008 at 11:44:30AM +0100, Dagobert Michelsen wrote: > > There are several reasons why I think it would be nice to have > JRE and JDK as CSW packages: > .... I dont disagree. If you find a way to cleanly redistribute, I think it's a good idea. > I am not sure I got your point in linking to /usr. Extrapolating > from our policy I would make the CSW Java independent from the > system Java. Well, I think that there is a benefit in at least having One Standard Place for java. So that our programs that NEED java, can set JAVA_HOME to it and just go, if they dont have any funky requirements. The issue of WHICH java runtime it would point to, I think would be best left to a combination of [our CSW java tzar, TBD], and the customer site admin. From phil at bolthole.com Wed Nov 5 18:13:31 2008 From: phil at bolthole.com (Philip Brown) Date: Wed, 5 Nov 2008 09:13:31 -0800 Subject: [csw-maintainers] cheap flights USA<->europe? Message-ID: <20081105091331.A52830@bolthole.com> So.... before I officially book a flight... anyone know of good ways to get some really good deals for flights from california to switzerland? :-) From mmayer at mmayer.net Wed Nov 5 19:31:30 2008 From: mmayer at mmayer.net (Markus Mayer) Date: Wed, 5 Nov 2008 10:31:30 -0800 Subject: [csw-maintainers] checkpkg error Message-ID: <20081105183129.GA3001@bender.opencsw.org> Hi, Does anybody know where this error is coming from? build8s% checkpkg work/mmayer-build8s.d/libcups-1.3.9,REV\=2008.11.05-SunOS5.8-sparc-CSW.pkg.gz Examining work/mmayer-build8s.d/libcups-1.3.9,REV=2008.11.05-SunOS5.8-sparc-CSW.pkg.gz Looking for bad strings... Extracting files for more detailed inspection... CSWlibcups/pkginfo 2 blocks ERROR: filename missing full version field 1.3.9,REV=2008.11.02 This used to work the very first time I packed up the individual CUPS packages, but no longer such luck. Looking at pkginfo I see this: PKG=CSWlibcups NAME=libcups - Libraries for the Common UNIX Printing System ARCH=sparc VERSION=1.3.9,REV=2008.11.02 CATEGORY=application VENDOR=http://www.cups.org/ packaged for CSW by Unknown EMAIL=Unknown PSTAMP=mmayer at build8s-r2204UNCOMMITTED-20081102210321 CLASSES=none HOTLINE=http://www.opencsw.org/bugtrack/ I obviously still need to modify the VENDOR and EMAIL field, but VERSION seems just fine to me. Thanks, -Markus From ihsan at opencsw.org Wed Nov 5 19:42:42 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Wed, 05 Nov 2008 19:42:42 +0100 Subject: [csw-maintainers] cheap flights USA<->europe? In-Reply-To: <20081105091331.A52830@bolthole.com> References: <20081105091331.A52830@bolthole.com> Message-ID: <4911E922.1030504@opencsw.org> Hi Phil, Am 5.11.2008 18:13 Uhr, Philip Brown schrieb: > So.... before I officially book a flight... anyone know of good ways to get > some really good deals for flights from california to switzerland? :-) Where in California? Los Angeles? The closest airport is Zurich, but Basel/Mulhouse or Stuttgart are also close. Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From phil at bolthole.com Wed Nov 5 19:52:06 2008 From: phil at bolthole.com (Philip Brown) Date: Wed, 5 Nov 2008 10:52:06 -0800 Subject: [csw-maintainers] checkpkg error In-Reply-To: <20081105183129.GA3001@bender.opencsw.org>; from mmayer@mmayer.net on Wed, Nov 05, 2008 at 10:31:30AM -0800 References: <20081105183129.GA3001@bender.opencsw.org> Message-ID: <20081105105206.I95235@bolthole.com> On Wed, Nov 05, 2008 at 10:31:30AM -0800, Markus Mayer wrote: > Hi, > > Does anybody know where this error is coming from? you goofed, that's where :-) > > build8s% checkpkg > work/mmayer-build8s.d/libcups-1.3.9,REV\=2008.11.05 > Looking at pkginfo I see this: > > VERSION=1.3.9,REV=2008.11.02 They dont match! From phil at bolthole.com Wed Nov 5 19:55:34 2008 From: phil at bolthole.com (Philip Brown) Date: Wed, 5 Nov 2008 10:55:34 -0800 Subject: [csw-maintainers] cheap flights USA<->europe? In-Reply-To: <4911E922.1030504@opencsw.org>; from ihsan@opencsw.org on Wed, Nov 05, 2008 at 07:42:42PM +0100 References: <20081105091331.A52830@bolthole.com> <4911E922.1030504@opencsw.org> Message-ID: <20081105105534.J95235@bolthole.com> On Wed, Nov 05, 2008 at 07:42:42PM +0100, Ihsan Dogan wrote: > Hi Phil, > > Am 5.11.2008 18:13 Uhr, Philip Brown schrieb: > > > So.... before I officially book a flight... anyone know of good ways to get > > some really good deals for flights from california to switzerland? :-) > > Where in California? Los Angeles? > > The closest airport is Zurich, but Basel/Mulhouse or Stuttgart are also > close. My closest "major" ones are LAX, and also irvine (SNA) I work by LAX, but live inbetween LAX and SNA. From william at wbonnet.net Wed Nov 5 20:18:14 2008 From: william at wbonnet.net (William Bonnet) Date: Wed, 05 Nov 2008 20:18:14 +0100 Subject: [csw-maintainers] cheap flights USA<->europe? In-Reply-To: <20081105105534.J95235@bolthole.com> References: <20081105091331.A52830@bolthole.com> <4911E922.1030504@opencsw.org> <20081105105534.J95235@bolthole.com> Message-ID: <4911F176.4020306@wbonnet.net> Hi Philip > My closest "major" ones are LAX, and also irvine (SNA) > I work by LAX, but live inbetween LAX and SNA. > You may also consider Paris ? It is about 600 km far from Paris. You can then go by train (about 200? for the two tickets). I can make reservation here for you. I believe that Peter leave from Paris, so do i. So if you choose to come to Paris, maybe we can go by car from Paris to Zurich. It is about 600km, mostly highway. so it will be something like a 6 hours drive we could do together ( i will provide the car ;) ) 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.guses.org French speaking Solaris User Group From mmayer at mmayer.net Wed Nov 5 21:20:52 2008 From: mmayer at mmayer.net (Markus Mayer) Date: Wed, 5 Nov 2008 12:20:52 -0800 Subject: [csw-maintainers] checkpkg error In-Reply-To: <20081105105206.I95235@bolthole.com> References: <20081105183129.GA3001@bender.opencsw.org> <20081105105206.I95235@bolthole.com> Message-ID: <20081105202051.GA6128@bender.opencsw.org> On Wednesday, 05 Nov 2008 10:52 -0800, Philip Brown wrote: >On Wed, Nov 05, 2008 at 10:31:30AM -0800, Markus Mayer wrote: >> Hi, >> >> Does anybody know where this error is coming from? > >you goofed, that's where :-) > >> Looking at pkginfo I see this: >> >> VERSION=1.3.9,REV=2008.11.02 > >They dont match! Okay, that makes sense. But I still see two issues: 1) the error message checkpkg prints is misleading (the full version field is present, there is a mismatch, however). 2) Where are the dates coming from? I didn't specify either one. I was simply testing the packaging by re-packaging a previously compiled CUPS tree. One date is obviously today's, the other one seems to be when the package was built. I don't want to have to rebuild everything simply to get the dates right, if all I want to do is package up the binaries I already have. Regards, -Markus From phil at bolthole.com Wed Nov 5 21:30:12 2008 From: phil at bolthole.com (Philip Brown) Date: Wed, 5 Nov 2008 12:30:12 -0800 Subject: [csw-maintainers] checkpkg error In-Reply-To: <20081105202051.GA6128@bender.opencsw.org>; from mmayer@mmayer.net on Wed, Nov 05, 2008 at 12:20:52PM -0800 References: <20081105183129.GA3001@bender.opencsw.org> <20081105105206.I95235@bolthole.com> <20081105202051.GA6128@bender.opencsw.org> Message-ID: <20081105123012.S95235@bolthole.com> On Wed, Nov 05, 2008 at 12:20:52PM -0800, Markus Mayer wrote: > ... > 2) Where are the dates coming from? I didn't specify either one. I was > simply testing the packaging by re-packaging a previously compiled CUPS > tree. I'm guessing "from GAR", so I see that as a bug in gar. If you do it "the old fashioned way", using my createpkg script, you never have this problem, since it always creates the filename based on the pkginfo ;-) > One date is obviously today's, the other one seems to be when the > package was built. I don't want to have to rebuild everything simply to > get the dates right, if all I want to do is package up the binaries I > already have. Well, you might consider using createpkg then, for this specific rebuild. reminder: if you have valid pkginfo, depend, copyright, prototype files in your current directory, then all you need do is type createpkg -r /path/to/relative-root and it will build the package for you, presuming you have your binaries layed out in some tree like /path/to/relative-root/opt/csw/bin/blahblah If you have them "installed normally", directly to /opt/csw, then you could use createpkg -r / and it would work,as long as you have pkginfo and so on, in your current dir. From dam at opencsw.org Wed Nov 5 22:03:36 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 5 Nov 2008 22:03:36 +0100 Subject: [csw-maintainers] checkpkg error In-Reply-To: <20081105202051.GA6128@bender.opencsw.org> References: <20081105183129.GA3001@bender.opencsw.org> <20081105105206.I95235@bolthole.com> <20081105202051.GA6128@bender.opencsw.org> Message-ID: Hi Markus, Am 05.11.2008 um 21:20 schrieb Markus Mayer: > On Wednesday, 05 Nov 2008 10:52 -0800, Philip Brown wrote: >> On Wed, Nov 05, 2008 at 10:31:30AM -0800, Markus Mayer wrote: >>> Hi, >>> >>> Does anybody know where this error is coming from? >> >> you goofed, that's where :-) > One date is obviously today's, the other one seems to be when the > package was built. I don't want to have to rebuild everything simply > to > get the dates right, if all I want to do is package up the binaries I > already have. This error occurs when building a packages takes more than a day. Just give the whole package a respin (or use "gmake reinstall", "gmake repackage") and it should work. Best regards -- Dago From dam at opencsw.org Wed Nov 5 22:05:53 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 5 Nov 2008 22:05:53 +0100 Subject: [csw-maintainers] checkpkg error In-Reply-To: <20081105123012.S95235@bolthole.com> References: <20081105183129.GA3001@bender.opencsw.org> <20081105105206.I95235@bolthole.com> <20081105202051.GA6128@bender.opencsw.org> <20081105123012.S95235@bolthole.com> Message-ID: <4C0E4B7E-8C8F-4E35-8545-1AB0013351EA@opencsw.org> Hi Phil, Am 05.11.2008 um 21:30 schrieb Philip Brown: > On Wed, Nov 05, 2008 at 12:20:52PM -0800, Markus Mayer wrote: >> ... >> 2) Where are the dates coming from? I didn't specify either one. I >> was >> simply testing the packaging by re-packaging a previously compiled >> CUPS >> tree. > > I'm guessing "from GAR", so I see that as a bug in gar. It sure is. However, if you build a package in one turn you don't run into this and there are nastier things to fix first. Best regards -- Dago From phil at bolthole.com Wed Nov 5 22:35:59 2008 From: phil at bolthole.com (Philip Brown) Date: Wed, 5 Nov 2008 13:35:59 -0800 Subject: [csw-maintainers] checkpkg error In-Reply-To: <4C0E4B7E-8C8F-4E35-8545-1AB0013351EA@opencsw.org>; from dam@opencsw.org on Wed, Nov 05, 2008 at 10:05:53PM +0100 References: <20081105183129.GA3001@bender.opencsw.org> <20081105105206.I95235@bolthole.com> <20081105202051.GA6128@bender.opencsw.org> <20081105123012.S95235@bolthole.com> <4C0E4B7E-8C8F-4E35-8545-1AB0013351EA@opencsw.org> Message-ID: <20081105133559.U95235@bolthole.com> On Wed, Nov 05, 2008 at 10:05:53PM +0100, Dagobert Michelsen wrote: > Hi Phil, *wave* > > I'm guessing "from GAR", so I see that as a bug in gar. > > It sure is. However, if you build a package in one turn > you don't run into this and there are nastier things to > fix first. > of course, if someone else were to look at it and submit a fix for it, I'm sure that would work too... :-D Dagobert doesnt have to be the only one to patch gar.... From dam at opencsw.org Thu Nov 6 09:02:06 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 6 Nov 2008 09:02:06 +0100 Subject: [csw-maintainers] New buildfarm at Gore Message-ID: <6FDDDCA2-502B-4617-ADAF-19E4885CBF86@opencsw.org> Hi, we have a new build server available sponsored by W. L. Gore company (yes, like "Gore-Tex") and organized by Phil. It is a V240 2 x 1.5 GHz 8 GB Ram 2 x 73 GB and 2 x 146 GB Disk Thanks! The server is reachable as build8s.go.opencsw.org (go = Gore) directly from the internet. All accounts from the bo-farm have also been created there and the SSH keys have been transferred, so each maintainer having a login at "bo" should also be able to login to "go". There should be the same set of CSW packages installed on the bo- and go-farm. Please still deliver packages to /home/testing on the bo farm to allow a single download location. Farm access has been documented at Best regards -- Dago From phil at bolthole.com Thu Nov 6 18:24:19 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 6 Nov 2008 09:24:19 -0800 Subject: [csw-maintainers] New buildfarm at Gore In-Reply-To: <6FDDDCA2-502B-4617-ADAF-19E4885CBF86@opencsw.org>; from dam@opencsw.org on Thu, Nov 06, 2008 at 09:02:06AM +0100 References: <6FDDDCA2-502B-4617-ADAF-19E4885CBF86@opencsw.org> Message-ID: <20081106092419.C95235@bolthole.com> On Thu, Nov 06, 2008 at 09:02:06AM +0100, Dagobert Michelsen wrote: > ... > Please still deliver packages to /home/testing > on the bo farm to allow a single download location. clarification: If you want to put packages in a "testing" space, then please put them there. If and when you are satisfied your packages are ready for RELEASE, however,... please still scp them to www.opencsw.org:/home/newpkgs as previously, and as documented in our standards pages. From pfelecan at blastwave.org Thu Nov 6 19:28:07 2008 From: pfelecan at blastwave.org (Peter FELECAN) Date: Thu, 06 Nov 2008 19:28:07 +0100 Subject: [csw-maintainers] cheap flights USA<->europe? In-Reply-To: <4911F176.4020306@wbonnet.net> (William Bonnet's message of "Wed\, 05 Nov 2008 20\:18\:14 +0100") References: <20081105091331.A52830@bolthole.com> <4911E922.1030504@opencsw.org> <20081105105534.J95235@bolthole.com> <4911F176.4020306@wbonnet.net> Message-ID: William Bonnet writes: > I believe that Peter leave from Paris, so do i. So if you choose to come > to Paris, maybe we can go by car from Paris to Zurich. It is about > 600km, mostly highway. so it will be something like a 6 hours drive we > could do together ( i will provide the car ;) ) I'm using for all my trips Lufthansa. They have very cheap inter-city flights, e.g. Paris--Zurich 168 euros for a round trip. A Los Angeles--Zurich trip is around 600 euros (764 USD) and I don't know if that falls in the cheap category... Now, for making the 1200 km by car, why not, we can share the fees --- need to evaluate if they are less than a plane ticket --- but I wonder if it's very green. -- Peter From ihsan at opencsw.org Thu Nov 6 20:27:39 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Thu, 06 Nov 2008 20:27:39 +0100 Subject: [csw-maintainers] cheap flights USA<->europe? In-Reply-To: <20081105105534.J95235@bolthole.com> References: <20081105091331.A52830@bolthole.com> <4911E922.1030504@opencsw.org> <20081105105534.J95235@bolthole.com> Message-ID: <4913452B.3060300@opencsw.org> Am 5.11.2008 19:55 Uhr, Philip Brown schrieb: > My closest "major" ones are LAX, and also irvine (SNA) > I work by LAX, but live inbetween LAX and SNA. With "Swiss International" from LAX to ZRH, direct fligth: 661.- $. I've checked also other airports and airlines and it looks like, that this is the cheapest offer I can find. --> http://www.swiss.com/ Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From phil at bolthole.com Thu Nov 6 20:36:11 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 6 Nov 2008 11:36:11 -0800 Subject: [csw-maintainers] cheap flights USA<->europe? In-Reply-To: <4913452B.3060300@opencsw.org>; from ihsan@opencsw.org on Thu, Nov 06, 2008 at 08:27:39PM +0100 References: <20081105091331.A52830@bolthole.com> <4911E922.1030504@opencsw.org> <20081105105534.J95235@bolthole.com> <4913452B.3060300@opencsw.org> Message-ID: <20081106113611.Q95235@bolthole.com> On Thu, Nov 06, 2008 at 08:27:39PM +0100, Ihsan Dogan wrote: > Am 5.11.2008 19:55 Uhr, Philip Brown schrieb: > > > My closest "major" ones are LAX, and also irvine (SNA) > > I work by LAX, but live inbetween LAX and SNA. > > With "Swiss International" from LAX to ZRH, direct fligth: 661.- $. > > I've checked also other airports and airlines and it looks like, that > this is the cheapest offer I can find. Awesome! thanks From jakegoerzen at gmail.com Fri Nov 7 16:07:36 2008 From: jakegoerzen at gmail.com (Jake Goerzen) Date: Fri, 7 Nov 2008 07:07:36 -0800 Subject: [csw-maintainers] now in /testing: freeciv 2.0.10 Message-ID: <315c02ae0811070707i6973c74akc48d8138c23b3a52@mail.gmail.com> updated freeciv 2.0.10 pkgs are available in /testing: 7f36723348f271a071ae1ed162edafb6 freeciv-2.0.10,REV=2008.11.07-SunOS5.8-i386-CSW.pkg.gz e18a80f6832a4f4247d4fa4e0085b7c4 freeciv-2.0.10,REV=2008.11.07-SunOS5.8-sparc-CSW.pkg.gz Thanks, Jake -------------- next part -------------- An HTML attachment was scrubbed... URL: From dam at opencsw.org Fri Nov 7 20:43:37 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 7 Nov 2008 20:43:37 +0100 Subject: [csw-maintainers] Contents of devel@ list Message-ID: Hi, I am having a little talk with Phil about the contents of the devel@ mailing list: Am 07.11.2008 um 18:06 schrieb Philip Brown: > On Fri, Nov 07, 2008 at 05:06:23PM +0100, Dagobert Michelsen wrote: >> BTW: If the package gets pushed to current there should be also >> a mail to devel at . I am thinking of devel@ as a high frequency >> list to get a detailed understanding of what is going on. > > Hmm.. I think announcing a release of packages as they happen, is > unneccessary spam. If a bunch of people really want that, then > that's fine > with me. but I think you should ask how many people are actually > INTERSTED > in that, before we do that :-) > a reminder: a weekly email to newpkgs mailing list, already happens. For me it is interesting when my packages get processed and are batched to current/. The newpkgs@ list is for users who want to know what is released (BTW: We should provide RSS for released to current/ also. Phil? ;-) Would you consider this useful or noise? Best regards -- Dago From phil at bolthole.com Fri Nov 7 20:50:30 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 7 Nov 2008 11:50:30 -0800 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: ; from dam@opencsw.org on Fri, Nov 07, 2008 at 08:43:37PM +0100 References: Message-ID: <20081107115030.D95235@bolthole.com> On Fri, Nov 07, 2008 at 08:43:37PM +0100, Dagobert Michelsen wrote: > > For me it is interesting when my packages get processed and are batched > to current/. The newpkgs@ list is for users who want to know what is > released (BTW: We should provide RSS for released to current/ also. > Phil? ;-) Hmm.. perhaps I misunderstood what you were asking. I thought when you described "batched to current", you were talking about "when it is released", as the same thing. But you seem to be referring to them as different things now. Perhaps you could clarify? From dam at opencsw.org Fri Nov 7 20:59:32 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 7 Nov 2008 20:59:32 +0100 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: <20081107115030.D95235@bolthole.com> References: <20081107115030.D95235@bolthole.com> Message-ID: <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org> Hi Phil, Am 07.11.2008 um 20:50 schrieb Philip Brown: > On Fri, Nov 07, 2008 at 08:43:37PM +0100, Dagobert Michelsen wrote: >> For me it is interesting when my packages get processed and are >> batched >> to current/. The newpkgs@ list is for users who want to know what is >> released (BTW: We should provide RSS for released to current/ also. >> Phil? ;-) > > Hmm.. perhaps I misunderstood what you were asking. I thought when you > described "batched to current", you were talking about "when it is > released", as the same thing. > But you seem to be referring to them as different things now. > Perhaps you could clarify? When I move a package to www.opencsw.org:/newpkgs I write a mail to the unstable release manager (read: you) and you process it. This usually occurs within a day or two and you usually write back a mail that the package is accepted. The idea is to have this formalized like that when you batch the package for master mirror distribution an email is send automatically to devel@ that this has been done. Best regards -- Dago From phil at bolthole.com Fri Nov 7 21:24:31 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 7 Nov 2008 12:24:31 -0800 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org>; from dam@opencsw.org on Fri, Nov 07, 2008 at 08:59:32PM +0100 References: <20081107115030.D95235@bolthole.com> <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org> Message-ID: <20081107122431.F95235@bolthole.com> On Fri, Nov 07, 2008 at 08:59:32PM +0100, Dagobert Michelsen wrote: > When I move a package to www.opencsw.org:/newpkgs I write a > mail to the unstable release manager (read: you) and you > process it. This usually occurs within a day or two and > you usually write back a mail that the package is accepted. > The idea is to have this formalized like that when you > batch the package for master mirror distribution an email > is send automatically to devel@ that this has been done. Oh.... you are trying to keep an eye on the part between "i copy it into the batching area" vs "it goes public". because in the past, I have sometimes taken a while between the two. As a side note, I anticipate that gap to be much much shorter these days, since the processes runs smoother for me now. Additionally, our front webpage, and the "newpkgs" mailing list, both actually get their information from the internal batching area :-} So we already have an "updated daily" reference of what is in that area. As mentioned previously, I could make the front web page updated hourly, if you like. Unless people really want an actual individual EMAIL to go out somewhere, every time a package hits that area. Do people want to see that? or is the insert on www.opencsw.org enough? (either once a day, or once an hour?) From jgoerzen at opencsw.org Fri Nov 7 22:56:45 2008 From: jgoerzen at opencsw.org (Jake Goerzen) Date: Fri, 7 Nov 2008 13:56:45 -0800 Subject: [csw-maintainers] request pkg(s) installed on buildfarm Message-ID: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> Currently installed SDL libraries on buildfarm: build8s% /opt/csw/bin/pkg-get -c | grep sdl libsdl 1.2.9 SAME sdlimage [Not installed] 1.2.4,REV=2006.05.03 sdlmixer [Not installed] 1.2.6,REV=2007.02.27 sdlnet [Not installed] 1.2.5,REV=2006.05.04 sdlsound [Not installed] 1.0.1,REV=2006.06.17 sdlttf [Not installed] 2.0.6,REV=2006.06.17 Please install "CSWsdlimage, CSWsdlmixer & CSWsdlttf" These are prerequisites for building proper freeciv and wesnoth packages. Thanks, Jake -------------- next part -------------- An HTML attachment was scrubbed... URL: From phil at bolthole.com Sat Nov 8 05:43:14 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 7 Nov 2008 20:43:14 -0800 Subject: [csw-maintainers] cheap flights USA<->europe? In-Reply-To: <20081105091331.A52830@bolthole.com>; from phil@bolthole.com on Wed, Nov 05, 2008 at 09:13:31AM -0800 References: <20081105091331.A52830@bolthole.com> Message-ID: <20081107204314.B22627@bolthole.com> On Wed, Nov 05, 2008 at 09:13:31AM -0800, Philip Brown wrote: > So.... before I officially book a flight... anyone know of good ways to get > some really good deals for flights from california to switzerland? :-) fyi: kayak.com ended up giving me the best amount of choices. and also told me, "go to united.com and book direct, to save yourself even more money!" From dam at opencsw.org Sat Nov 8 07:33:35 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 8 Nov 2008 07:33:35 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> Message-ID: <5A254E01-AD38-40EE-86AD-9823C2026452@opencsw.org> Hi Jake, Am 07.11.2008 um 22:56 schrieb Jake Goerzen: > Please install "CSWsdlimage, CSWsdlmixer & CSWsdlttf" These are > prerequisites for building proper freeciv and wesnoth packages. Done. Best regards -- Dago From dam at opencsw.org Sat Nov 8 10:59:32 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 8 Nov 2008 10:59:32 +0100 Subject: [csw-maintainers] Update on 'login' Message-ID: Hi, I updated today login.opencsw.org to match current/. I hope you didn't experiences any troubles due to removed and reinstaled packages. Thanks! -- Dago From dam at opencsw.org Sat Nov 8 16:40:29 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 8 Nov 2008 16:40:29 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <491041B0.5000501@opencsw.org> References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> Message-ID: Hi, Am 04.11.2008 um 13:36 schrieb Trygve Laugst?l: > To me, depending only on our own packages + base Solaris (of whatever > version we're currently basing our stuff on) is what we need to do to > deliver quality packages. > > We need this. Maybe only for building packages, but still. We have this. Now in testing/: jre13-1.3.1_22,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz jre13-1.3.1_22,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz jre14-1.4.2_17,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz jre14-1.4.2_17,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz jre5-1.5.0_15,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz jre5-1.5.0_15,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz jre6-6u7,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz jre6-6u7,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz jdk13-1.3.1_22,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz jdk13-1.3.1_22,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz jdk14-1.4.2_17,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz jdk14-1.4.2_17,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz jdk5-1.5.0_15,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz jdk5-1.5.0_15,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz jdk6-6u7,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz jdk6-6u7,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz Fellow Java Gurus, please test. Thanks! -- Dago From james at opencsw.org Sat Nov 8 17:06:10 2008 From: james at opencsw.org (James Lee) Date: Sat, 08 Nov 2008 16:06:10 GMT Subject: [csw-maintainers] Java... again! In-Reply-To: References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> Message-ID: <20081108.16061000.3036193704@gyor.oxdrove.co.uk> On 08/11/08, 15:40:29, Dagobert Michelsen wrote regarding Re: [csw-maintainers] Java... again!: > jdk5-1.5.0_15,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz > jdk5-1.5.0_15,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz > jdk6-6u7,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz > jdk6-6u7,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz Latest 1.5 is Update 16 http://java.sun.com/javase/downloads/index_jdk5.jsp The latest 1.6 is Update 10. http://java.sun.com/javase/downloads/index.jsp It identifies itself: $ java -version java version "1.6.0_10" Java(TM) SE Runtime Environment (build 1.6.0_10-b33) Java HotSpot(TM) Server VM (build 11.0-b15, mixed mode) So why use break the pattern of naming, I'd expect the package to be identified similarly as "1.6.0_10". From trygvel at opencsw.org Sun Nov 9 11:32:47 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sun, 09 Nov 2008 11:32:47 +0100 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: <20081107122431.F95235@bolthole.com> References: <20081107115030.D95235@bolthole.com> <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org> <20081107122431.F95235@bolthole.com> Message-ID: <4916BC4F.8010606@opencsw.org> Philip Brown wrote: > On Fri, Nov 07, 2008 at 08:59:32PM +0100, Dagobert Michelsen wrote: >> When I move a package to www.opencsw.org:/newpkgs I write a >> mail to the unstable release manager (read: you) and you >> process it. This usually occurs within a day or two and >> you usually write back a mail that the package is accepted. >> The idea is to have this formalized like that when you >> batch the package for master mirror distribution an email >> is send automatically to devel@ that this has been done. > > Oh.... you are trying to keep an eye on the part between > > "i copy it into the batching area" > vs > "it goes public". > > because in the past, I have sometimes taken a while between the two. > As a side note, I anticipate that gap to be much much shorter these days, > since the processes runs smoother for me now. > > Additionally, our front webpage, and the "newpkgs" mailing list, both > actually get their information from the internal batching area :-} > So we already have an "updated daily" reference of what is in that area. > > As mentioned previously, I could make the front web page updated hourly, if > you like. > Unless people really want an actual individual EMAIL to go out somewhere, > every time a package hits that area. > > Do people want to see that? or is the insert on www.opencsw.org enough? > (either once a day, or once an hour?) I wouldn't mind an email when a packages moves from one state to another. I would also like an Atom feed with new and updated packages so that people can follow the changes. In the future I wouldn't mind including the change log of what's changed. -- Trygve From trygvel at opencsw.org Sun Nov 9 11:34:47 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sun, 09 Nov 2008 11:34:47 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> Message-ID: <4916BCC7.9000104@opencsw.org> Jake Goerzen wrote: > Currently installed SDL libraries on buildfarm: > > build8s% /opt/csw/bin/pkg-get -c | grep sdl > libsdl 1.2.9 SAME > sdlimage [Not installed] 1.2.4,REV=2006.05.03 > sdlmixer [Not installed] 1.2.6,REV=2007.02.27 > sdlnet [Not installed] 1.2.5,REV=2006.05.04 > sdlsound [Not installed] 1.0.1,REV=2006.06.17 > sdlttf [Not installed] 2.0.6,REV=2006.06.17 Would it be possible to run "pkg-get -c|grep -v SAME" and have it spit out an email when stuff is outdated? -- Trygve From dam at opencsw.org Sun Nov 9 11:49:41 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 9 Nov 2008 11:49:41 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <4916BCC7.9000104@opencsw.org> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> Message-ID: <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> Hi Trygve, Am 09.11.2008 um 11:34 schrieb Trygve Laugst?l: > Would it be possible to run "pkg-get -c|grep -v SAME" and have it spit > out an email when stuff is outdated? Do you mean this? pkg-get -c|grep -v SAME|grep -v "Not installed" Should the email go to the farm manager to fix this ASAP or once per day to devel@? Best regards -- Dago From dam at opencsw.org Sun Nov 9 11:57:50 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 9 Nov 2008 11:57:50 +0100 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: <4916BC4F.8010606@opencsw.org> References: <20081107115030.D95235@bolthole.com> <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org> <20081107122431.F95235@bolthole.com> <4916BC4F.8010606@opencsw.org> Message-ID: Hi, Am 09.11.2008 um 11:32 schrieb Trygve Laugst?l: > Philip Brown wrote: >> Oh.... you are trying to keep an eye on the part between >> >> "i copy it into the batching area" >> vs >> "it goes public". >> >> because in the past, I have sometimes taken a while between the two. >> As a side note, I anticipate that gap to be much much shorter these >> days, >> since the processes runs smoother for me now. >> >> Additionally, our front webpage, and the "newpkgs" mailing list, both >> actually get their information from the internal batching area :-} >> So we already have an "updated daily" reference of what is in that >> area. >> >> As mentioned previously, I could make the front web page updated >> hourly, if >> you like. >> Unless people really want an actual individual EMAIL to go out >> somewhere, >> every time a package hits that area. >> >> Do people want to see that? or is the insert on www.opencsw.org >> enough? >> (either once a day, or once an hour?) > > I wouldn't mind an email when a packages moves from one state to > another. Yes, to devel@ please. I guess we should keep maintainers@ free from automated posts. > I would also like an Atom feed with new and updated packages so > that people can follow the changes. Do you mind doing that yourself? Ihsan can set up a file on www.opencsw.org:/var/www/www.opencsw.org/htdocs/ where you can deliver the xml. > In the future I wouldn't mind including the change log of what's > changed. Where should that information come from? Best regards -- Dago From bonivart at opencsw.org Sun Nov 9 12:02:23 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 9 Nov 2008 12:02:23 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <4916BCC7.9000104@opencsw.org> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> Message-ID: <625385e30811090302s4266abf1p784d603a5ea3b59d@mail.gmail.com> On Sun, Nov 9, 2008 at 11:34 AM, Trygve Laugst?l wrote: > Jake Goerzen wrote: >> Currently installed SDL libraries on buildfarm: >> >> build8s% /opt/csw/bin/pkg-get -c | grep sdl >> libsdl 1.2.9 SAME >> sdlimage [Not installed] 1.2.4,REV=2006.05.03 >> sdlmixer [Not installed] 1.2.6,REV=2007.02.27 >> sdlnet [Not installed] 1.2.5,REV=2006.05.04 >> sdlsound [Not installed] 1.0.1,REV=2006.06.17 >> sdlttf [Not installed] 2.0.6,REV=2006.06.17 > > Would it be possible to run "pkg-get -c|grep -v SAME" and have it spit > out an email when stuff is outdated? pkgutil -e somebody at somewhere.com -- /peter From bonivart at opencsw.org Sun Nov 9 12:05:09 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 9 Nov 2008 12:05:09 +0100 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: References: <20081107115030.D95235@bolthole.com> <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org> <20081107122431.F95235@bolthole.com> <4916BC4F.8010606@opencsw.org> Message-ID: <625385e30811090305j6453d39bh89d59f7f7cb641cc@mail.gmail.com> On Sun, Nov 9, 2008 at 11:57 AM, Dagobert Michelsen wrote: > Yes, to devel@ please. I guess we should keep maintainers@ > free from automated posts. Why not to the newpkgs list? -- /peter From dam at opencsw.org Sun Nov 9 13:51:26 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 9 Nov 2008 13:51:26 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081108.16061000.3036193704@gyor.oxdrove.co.uk> References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> Message-ID: Hi James, Am 08.11.2008 um 17:06 schrieb James Lee: > On 08/11/08, 15:40:29, Dagobert Michelsen wrote > regarding > Re: [csw-maintainers] Java... again!: > >> jdk5-1.5.0_15,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz >> jdk5-1.5.0_15,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz >> jdk6-6u7,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz >> jdk6-6u7,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz > > Latest 1.5 is Update 16 > http://java.sun.com/javase/downloads/index_jdk5.jsp > > The latest 1.6 is Update 10. > http://java.sun.com/javase/downloads/index.jsp I got them from the archive page. Who can imagine archived versions would be old? Me??? Oh well... Heres some warmed up Java in : jre13-1.3.1_22,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz jre13-1.3.1_22,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz jre14-1.4.2_17,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz jre14-1.4.2_17,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz jre5-1.5.0_16,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz jre5-1.5.0_16,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz jre6-1.6.0_10,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz jre6-1.6.0_10,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz jdk13-1.3.1_22,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz jdk13-1.3.1_22,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz jdk14-1.4.2_17,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz jdk14-1.4.2_17,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz jdk5-1.5.0_16,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz jdk5-1.5.0_16,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz jdk6-1.6.0_10,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz jdk6-1.6.0_10,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz > It identifies itself: > > $ java -version > java version "1.6.0_10" > Java(TM) SE Runtime Environment (build 1.6.0_10-b33) > Java HotSpot(TM) Server VM (build 11.0-b15, mixed mode) > > So why use break the pattern of naming, I'd expect the package to be > identified similarly as "1.6.0_10". I should never have followed marketing numbers. The package now identified itself with the technical version number. James, do you mind testing these? Best regards -- Dago From phil at bolthole.com Sun Nov 9 16:49:25 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 9 Nov 2008 07:49:25 -0800 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <4916BCC7.9000104@opencsw.org>; from trygvel@opencsw.org on Sun, Nov 09, 2008 at 11:34:47AM +0100 References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> Message-ID: <20081109074925.F84797@bolthole.com> On Sun, Nov 09, 2008 at 11:34:47AM +0100, Trygve Laugst?l wrote: > Would it be possible to run "pkg-get -c|grep -v SAME" and have it spit > out an email when stuff is outdated? > fyi, pkg-get 4.0 "pkg-get -c" automatically skips "SAME". I had a beta version out months ago that did this, but of course it's lost to blastwave nukage now. I had THOUGHT I put a repackaged version up in our "testing" dir though. Hmmm.... From william at wbonnet.net Sun Nov 9 17:09:29 2008 From: william at wbonnet.net (William Bonnet) Date: Sun, 09 Nov 2008 17:09:29 +0100 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: <625385e30811090305j6453d39bh89d59f7f7cb641cc@mail.gmail.com> References: <20081107115030.D95235@bolthole.com> <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org> <20081107122431.F95235@bolthole.com> <4916BC4F.8010606@opencsw.org> <625385e30811090305j6453d39bh89d59f7f7cb641cc@mail.gmail.com> Message-ID: <49170B39.2060607@wbonnet.net> Peter Bonivart a ?crit : > On Sun, Nov 9, 2008 at 11:57 AM, Dagobert Michelsen wrote: > >> Yes, to devel@ please. I guess we should keep maintainers@ >> free from automated posts. >> > > Why not to the newpkgs list? > > newpkgs is supposed to be used only for release announcement ? isn't it ? From william at wbonnet.net Sun Nov 9 17:13:48 2008 From: william at wbonnet.net (William Bonnet) Date: Sun, 09 Nov 2008 17:13:48 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> Message-ID: <49170C3C.8060707@wbonnet.net> Hi > Do you mean this? > pkg-get -c|grep -v SAME|grep -v "Not installed" > > Should the email go to the farm manager to fix this ASAP > or once per day to devel@? > It is a good idea Maybe we should have a set of scripts for monitoring machines in the build farm ? Each machine in the farm would run the same scripts used for monitoring and reporting. Package installed on the build machine are one of the needs. We could also add disk space monitoring. Even if then problem has not yet been encountered it would be useful to report this before it happens :) We could also setup a nagios monitoring this kind of things. There is not yet a plugin used to monitor package installation, but i think it could be done. Cheers, W. From phil at bolthole.com Sun Nov 9 17:22:43 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 9 Nov 2008 08:22:43 -0800 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <49170C3C.8060707@wbonnet.net>; from william@wbonnet.net on Sun, Nov 09, 2008 at 05:13:48PM +0100 References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> <49170C3C.8060707@wbonnet.net> Message-ID: <20081109082243.H84797@bolthole.com> On Sun, Nov 09, 2008 at 05:13:48PM +0100, William Bonnet wrote: > > We could also setup a nagios monitoring this kind of things. There is > not yet a plugin used to monitor package installation, but i think it > could be done. Or... you could enable "email on install" in pkgadd, if you really want an alert sent everytime a package is installed. From bonivart at opencsw.org Sun Nov 9 19:27:20 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 9 Nov 2008 19:27:20 +0100 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: <49170B39.2060607@wbonnet.net> References: <20081107115030.D95235@bolthole.com> <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org> <20081107122431.F95235@bolthole.com> <4916BC4F.8010606@opencsw.org> <625385e30811090305j6453d39bh89d59f7f7cb641cc@mail.gmail.com> <49170B39.2060607@wbonnet.net> Message-ID: <625385e30811091027m3c8c5406pf0019e1e173547ef@mail.gmail.com> On Sun, Nov 9, 2008 at 5:09 PM, William Bonnet wrote: > newpkgs is supposed to be used only for release announcement ? isn't it ? Yes, but isn't this about just that, announcing that a package is being released to unstable? It's described as a weekly mailing list so it wouldn't be that low volume any more but it's more on target than devel to me. But it doesn't matter much where it goes, if someone thinks it's too noisy it's easy to filter out with the mail client. -- /peter From william at wbonnet.net Sun Nov 9 19:28:48 2008 From: william at wbonnet.net (William Bonnet) Date: Sun, 09 Nov 2008 19:28:48 +0100 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: <625385e30811091027m3c8c5406pf0019e1e173547ef@mail.gmail.com> References: <20081107115030.D95235@bolthole.com> <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org> <20081107122431.F95235@bolthole.com> <4916BC4F.8010606@opencsw.org> <625385e30811090305j6453d39bh89d59f7f7cb641cc@mail.gmail.com> <49170B39.2060607@wbonnet.net> <625385e30811091027m3c8c5406pf0019e1e173547ef@mail.gmail.com> Message-ID: <49172BE0.8010108@wbonnet.net> Peter Bonivart a ?crit : > On Sun, Nov 9, 2008 at 5:09 PM, William Bonnet wrote: > >> newpkgs is supposed to be used only for release announcement ? isn't it ? >> > > Yes, but isn't this about just that, announcing that a package is > being released to unstable? It's described as a weekly mailing list so > it wouldn't be that low volume any more but it's more on target than > devel to me. > Sure. I was thinking it was about instaled packages :) Sorry... I think it would be iteresting for users to receive both testing and unstable release. We may also have more users actally "testing" packages and more feedbacks. cheers From dam at opencsw.org Sun Nov 9 19:55:03 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 9 Nov 2008 19:55:03 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <49170C3C.8060707@wbonnet.net> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> <49170C3C.8060707@wbonnet.net> Message-ID: <77C43230-E691-4AFA-876B-0C3A5FB2D19A@opencsw.org> Hi William, Am 09.11.2008 um 17:13 schrieb William Bonnet: > Maybe we should have a set of scripts for monitoring machines in the > build farm ? Each machine in the farm would run the same scripts used > for monitoring and reporting. Package installed on the build machine > are > one of the needs. We could also add disk space monitoring. Even if > then > problem has not yet been encountered it would be useful to report this > before it happens :) I just packages the SE Toolkit and Orca. Good opportunity to eat our own dogfood. > We could also setup a nagios monitoring this kind of things. There is > not yet a plugin used to monitor package installation, but i think it > could be done. Are you volunteering for building an agent for this? ;-) BTW: Nagios was maintained by Alex Moore, who has retired. Making an updated Nagios would be nice too. Best regards -- Dago From dam at opencsw.org Sun Nov 9 20:57:17 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 9 Nov 2008 20:57:17 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <20081109082243.H84797@bolthole.com> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> <49170C3C.8060707@wbonnet.net> <20081109082243.H84797@bolthole.com> Message-ID: <8AB00139-0E57-41EE-9F95-FEEC84641090@opencsw.org> Am 09.11.2008 um 17:22 schrieb Philip Brown: > On Sun, Nov 09, 2008 at 05:13:48PM +0100, William Bonnet wrote: >> >> We could also setup a nagios monitoring this kind of things. There is >> not yet a plugin used to monitor package installation, but i think it >> could be done. > > Or... you could enable "email on install" in pkgadd, if you really > want an > alert sent everytime a package is installed. What feature is this? It doesn't seem to be documented in pkgadd(1m) or admin(4). Do you have a pointer for me? Thanks! -- Dago From bonivart at opencsw.org Sun Nov 9 21:22:30 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 9 Nov 2008 21:22:30 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <8AB00139-0E57-41EE-9F95-FEEC84641090@opencsw.org> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> <49170C3C.8060707@wbonnet.net> <20081109082243.H84797@bolthole.com> <8AB00139-0E57-41EE-9F95-FEEC84641090@opencsw.org> Message-ID: <625385e30811091222q174f2bf4y2b2d16eeb96eee3@mail.gmail.com> On Sun, Nov 9, 2008 at 8:57 PM, Dagobert Michelsen wrote: > What feature is this? It doesn't seem to be documented > in pkgadd(1m) or admin(4). Do you have a pointer for me? This is from the admin(4) page for Solaris 8: "mail Defines a list of users to whom mail should be sent following installation of a package. If the list is empty, no mail is sent. If the parameter is not present in the admin file, the default value of root is used. The ask value cannot be used with this parameter." http://docs.sun.com/app/docs/doc/806-0633/6j9vn6q29?l=en&a=view&q=admin(4)+solaris+8 -- /peter From dam at opencsw.org Sun Nov 9 21:26:48 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 9 Nov 2008 21:26:48 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <625385e30811091222q174f2bf4y2b2d16eeb96eee3@mail.gmail.com> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> <49170C3C.8060707@wbonnet.net> <20081109082243.H84797@bolthole.com> <8AB00139-0E57-41EE-9F95-FEEC84641090@opencsw.org> <625385e30811091222q174f2bf4y2b2d16eeb96eee3@mail.gmail.com> Message-ID: <645DE6F9-38AA-42E7-A634-38C755579B7C@opencsw.org> Hi, Am 09.11.2008 um 21:22 schrieb Peter Bonivart: > On Sun, Nov 9, 2008 at 8:57 PM, Dagobert Michelsen > wrote: >> What feature is this? It doesn't seem to be documented >> in pkgadd(1m) or admin(4). Do you have a pointer for me? > > This is from the admin(4) page for Solaris 8: > > "mail > > Defines a list of users to whom mail should be sent following > installation of a package. If the list is empty, no mail is sent. If > the parameter is not present in the admin file, the default value of > root is used. The ask value cannot be used with this parameter." > > http://docs.sun.com/app/docs/doc/806-0633/6j9vn6q29?l=en&a=view&q=admin(4)+solaris+8 Am 09.11.2008 um 17:22 schrieb Philip Brown: > On Sun, Nov 09, 2008 at 05:13:48PM +0100, William Bonnet wrote: >> >> We could also setup a nagios monitoring this kind of things. There is >> not yet a plugin used to monitor package installation, but i think it >> could be done. > > Or... you could enable "email on install" in pkgadd, if you really > want an > alert sent everytime a package is installed. I see. Does anyone feel the need I activate that on the buildfarms to mail to devel@ or is the versionmatrix enough? Best regards -- Dago From bonivart at opencsw.org Sun Nov 9 21:32:00 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 9 Nov 2008 21:32:00 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <645DE6F9-38AA-42E7-A634-38C755579B7C@opencsw.org> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> <49170C3C.8060707@wbonnet.net> <20081109082243.H84797@bolthole.com> <8AB00139-0E57-41EE-9F95-FEEC84641090@opencsw.org> <625385e30811091222q174f2bf4y2b2d16eeb96eee3@mail.gmail.com> <645DE6F9-38AA-42E7-A634-38C755579B7C@opencsw.org> Message-ID: <625385e30811091232y24e0f7c3l6235250088fb81c0@mail.gmail.com> On Sun, Nov 9, 2008 at 9:26 PM, Dagobert Michelsen wrote: > I see. Does anyone feel the need I activate that on the buildfarms > to mail to devel@ or is the versionmatrix enough? Too much info for me. The version matrix (which is great btw) in combination with "updates available" e-mails are enough for me. -- /peter From william at wbonnet.net Mon Nov 10 10:08:27 2008 From: william at wbonnet.net (William Bonnet) Date: Mon, 10 Nov 2008 10:08:27 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <645DE6F9-38AA-42E7-A634-38C755579B7C@opencsw.org> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> <49170C3C.8060707@wbonnet.net> <20081109082243.H84797@bolthole.com> <8AB00139-0E57-41EE-9F95-FEEC84641090@opencsw.org> <625385e30811091222q174f2bf4y2b2d16eeb96eee3@mail.gmail.com> <645DE6F9-38AA-42E7-A634-38C755579B7C@opencsw.org> Message-ID: <4917FA0B.1050803@wbonnet.net> hi > I see. Does anyone feel the need I activate that on the buildfarms > to mail to devel@ or is the versionmatrix enough? > I think both are interesting. IMHO i think that it would be interesting to have a buildfarm mailing list to which such email would be sent. It would be intersting for people running other builfarm to receive notification email when they have to install a package. Version matrix is a good tool, but i prefer to receive email when i have something to do, instead of going to a web page to see if i have something to do. As i said in a previous email, we could also send to this list notification like host up and down alerts. Next in my todo list is Finish FF3 and its dependencies today give you (Dago) access to the webserver running wordpress install my V240 and nagios. Cheers, W. From dam at opencsw.org Mon Nov 10 11:09:04 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 10 Nov 2008 11:09:04 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <4917FA0B.1050803@wbonnet.net> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> <49170C3C.8060707@wbonnet.net> <20081109082243.H84797@bolthole.com> <8AB00139-0E57-41EE-9F95-FEEC84641090@opencsw.org> <625385e30811091222q174f2bf4y2b2d16eeb96eee3@mail.gmail.com> <645DE6F9-38AA-42E7-A634-38C755579B7C@opencsw.org> <4917FA0B.1050803@wbonnet.net> Message-ID: <3CBD014C-ECC1-4D9A-BEC4-FE166092C33F@opencsw.org> Hi William, Am 10.11.2008 um 10:08 schrieb William Bonnet: >> I see. Does anyone feel the need I activate that on the buildfarms >> to mail to devel@ or is the versionmatrix enough? >> > > I think both are interesting. > > IMHO i think that it would be interesting to have a buildfarm mailing > list to which such email would be sent. It would be intersting for > people running other builfarm to receive notification email when they > have to install a package. There is already a mailing list for buildfarm managers: I don't know if self-subscription is enabled for that list. Otherwise Ihsan can add you to the list. If you are ready with your V240 we can try the emailing service. > Version matrix is a good tool, but i prefer > to receive email when i have something to do, instead of going to a > web > page to see if i have something to do. As i said in a previous > email, we > could also send to this list notification like host up and down > alerts. > > Next in my todo list is > > Finish FF3 and its dependencies today > give you (Dago) access to the webserver running wordpress > install my V240 and nagios. Excellent. Thanks! -- Dago From trygvel at opencsw.org Mon Nov 10 16:58:06 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Mon, 10 Nov 2008 16:58:06 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> Message-ID: <49185A0E.8040602@opencsw.org> Dagobert Michelsen wrote: > Hi Trygve, > > Am 09.11.2008 um 11:34 schrieb Trygve Laugst?l: >> Would it be possible to run "pkg-get -c|grep -v SAME" and have it spit >> out an email when stuff is outdated? > > Do you mean this? > pkg-get -c|grep -v SAME|grep -v "Not installed" No, all packages should always be installed. > Should the email go to the farm manager to fix this ASAP > or once per day to devel@? To me, mailing the farm managers and the version matrix is sufficient. If stuff is missing I can nag the farm manager by pointing to the matrix. -- Trygve From trygvel at opencsw.org Mon Nov 10 16:59:46 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Mon, 10 Nov 2008 16:59:46 +0100 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: References: <20081107115030.D95235@bolthole.com> <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org> <20081107122431.F95235@bolthole.com> <4916BC4F.8010606@opencsw.org> Message-ID: <49185A72.9040606@opencsw.org> Dagobert Michelsen wrote: > Hi, > > Am 09.11.2008 um 11:32 schrieb Trygve Laugst?l: >> Philip Brown wrote: >>> Oh.... you are trying to keep an eye on the part between >>> >>> "i copy it into the batching area" >>> vs >>> "it goes public". >>> >>> because in the past, I have sometimes taken a while between the two. >>> As a side note, I anticipate that gap to be much much shorter these >>> days, >>> since the processes runs smoother for me now. >>> >>> Additionally, our front webpage, and the "newpkgs" mailing list, both >>> actually get their information from the internal batching area :-} >>> So we already have an "updated daily" reference of what is in that >>> area. >>> >>> As mentioned previously, I could make the front web page updated >>> hourly, if >>> you like. >>> Unless people really want an actual individual EMAIL to go out >>> somewhere, >>> every time a package hits that area. >>> >>> Do people want to see that? or is the insert on www.opencsw.org >>> enough? >>> (either once a day, or once an hour?) >> I wouldn't mind an email when a packages moves from one state to >> another. > > Yes, to devel@ please. I guess we should keep maintainers@ > free from automated posts. > >> I would also like an Atom feed with new and updated packages so >> that people can follow the changes. > > Do you mind doing that yourself? Ihsan can set up a file on > www.opencsw.org:/var/www/www.opencsw.org/htdocs/ where you > can deliver the xml. I can create the Atom XML, but I don't know how to get the data. If the data is in a SQL database I can make a php page that generate the file. >> In the future I wouldn't mind including the change log of what's >> changed. > > Where should that information come from? From the change log file that the maintainer deliver when the .pkg is uploaded :). I know it doesn't exist, but I (as a user) would like to know what has changed when new packages are installed. This is very useful information to browse when looking at the front page and wondering why there is a new package available. In particular for bug fixes. -- Trygve From phil at bolthole.com Mon Nov 10 17:47:05 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 10 Nov 2008 08:47:05 -0800 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: <49185A72.9040606@opencsw.org>; from trygvel@opencsw.org on Mon, Nov 10, 2008 at 04:59:46PM +0100 References: <20081107115030.D95235@bolthole.com> <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org> <20081107122431.F95235@bolthole.com> <4916BC4F.8010606@opencsw.org> <49185A72.9040606@opencsw.org> Message-ID: <20081110084705.A94907@bolthole.com> On Mon, Nov 10, 2008 at 04:59:46PM +0100, Trygve Laugst?l wrote: > >> In the future I wouldn't mind including the change log of what's > >> changed. > > > > Where should that information come from? > > From the change log file that the maintainer deliver when the .pkg is > uploaded :). I know it doesn't exist, but I (as a user) would like to > know what has changed when new packages are installed. This is very > useful information to browse when looking at the front page and > wondering why there is a new package available. In particular for bug fixes. We had this discussion a year or three ago on the maintainers list. Some of the issues were: for one thing, we couldnt agree on whether the "upstream" changes should be in this file or not. I personally would say "not". and as a side comment, the vast majority of "new packages" are simply due to "new version upstream". and the vast majority of csw-side changes, are "oops, I made a mistake". Most of which are not really anything the user would care about, beyond "ok i'm glad you fixed that dumb thing". From trygvel at opencsw.org Mon Nov 10 17:58:27 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Mon, 10 Nov 2008 17:58:27 +0100 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: <20081110084705.A94907@bolthole.com> References: <20081107115030.D95235@bolthole.com> <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org> <20081107122431.F95235@bolthole.com> <4916BC4F.8010606@opencsw.org> <49185A72.9040606@opencsw.org> <20081110084705.A94907@bolthole.com> Message-ID: <49186833.9070802@opencsw.org> Philip Brown wrote: > On Mon, Nov 10, 2008 at 04:59:46PM +0100, Trygve Laugst?l wrote: >>>> In the future I wouldn't mind including the change log of what's >>>> changed. >>> Where should that information come from? >> From the change log file that the maintainer deliver when the .pkg is >> uploaded :). I know it doesn't exist, but I (as a user) would like to >> know what has changed when new packages are installed. This is very >> useful information to browse when looking at the front page and >> wondering why there is a new package available. In particular for bug fixes. > > We had this discussion a year or three ago on the maintainers list. > Some of the issues were: for one thing, we couldnt agree on whether the > "upstream" changes should be in this file or not. > > I personally would say "not". Me too, but I would point to the upstream release notes if available. > and as a side comment, the vast majority of "new packages" are simply due > to "new version upstream". and the vast majority of csw-side changes, are > "oops, I made a mistake". Most of which are not really anything the user > would care about, beyond "ok i'm glad you fixed that dumb thing". Know if it was only because of a upstream change or a packaging bug would be nice to know. I know I've made a few releases because of packaging issues. Most because I'm still new, but I wouldn't mind knowing it. From a PR perspective it will show more precisely what we're doing, but that you can also read from an atom feed. -- Trygve From phil at bolthole.com Mon Nov 10 18:08:42 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 10 Nov 2008 09:08:42 -0800 Subject: [csw-maintainers] pkg-get 4.0beta Message-ID: <20081110090842.B94907@bolthole.com> FYI: I've done a quickie repackage of pkg-get 4.0beta. http://mirror.opencsw.org/testing/pkg_get-4,0,REV=2008.11.10.beta-SunOS5.8-all-CSW.pkg It's not feature-complete, and has a few bugs in it, im sure. But it does have things like: pkg-get -c(compare) only shows installed packages (It DOES show "SAME" though, so my mistake on my prior claim about that) pkg-get -c -a shows remote versions of "all" packages, and compares to installed, if there is a version installed. pkg-get -u -v shows how many bytes would be downloaded, AND shows dependancies that would have to be downloaded. Sample: $ /opt/csw/bin/pkg-get -v -u pidgin DEBUG-ONLY/VERBOSE MODE: level=1 CSWpidgin pidgin 10763591 bytes CSWpng png 587563 bytes There are also a few misc bugfixes here and there. This is actually code I wrote waay back, many months ago, and released as a beta package, that got buried with Dennis's powerplay. January 2008, even. Although I dont remember when I published the prior "beta" package. Now that things have calmed down, I will hopefully be able to bring it up to good enough quality for a full release. Particularly if people show interest and give me a nudge , or some feedback ;-) From phil at bolthole.com Mon Nov 10 18:10:34 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 10 Nov 2008 09:10:34 -0800 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: <49186833.9070802@opencsw.org>; from trygvel@opencsw.org on Mon, Nov 10, 2008 at 05:58:27PM +0100 References: <20081107115030.D95235@bolthole.com> <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org> <20081107122431.F95235@bolthole.com> <4916BC4F.8010606@opencsw.org> <49185A72.9040606@opencsw.org> <20081110084705.A94907@bolthole.com> <49186833.9070802@opencsw.org> Message-ID: <20081110091034.C94907@bolthole.com> On Mon, Nov 10, 2008 at 05:58:27PM +0100, Trygve Laugst?l wrote: > > Know if it was only because of a upstream change or a packaging bug > would be nice to know. Well, that was ONE "nice" thing about the "REV=xxxx" field being optional except for secondary release of the same version :-} If there was no REV field, you could be fairly sure it was a simple upstream update. > From a PR perspective it will show more precisely what we're doing, but > that you can also read from an atom feed. I think it could be nice to support as some kind of optional thing. From phil at bolthole.com Mon Nov 10 20:39:14 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 10 Nov 2008 11:39:14 -0800 Subject: [csw-maintainers] newpkgs notes, on why packages may be held there Message-ID: <20081110113914.G94907@bolthole.com> FYI: Becaue I tend to forget, myself, I have now started to keep notes on why particular packages are being 'held' in newpkgs. I used to keep an old file in my home dir, but it will be /home/newpkgs/00-README from now on. Nice and easy to spot now. and also FYI: I always email people when there are issues with their packages. There is no additional requirement for people to go read that file themselves. This is just so I can delete my old emails safely, without forgetting why a package is sitting there. Or as a reminder to YOU, if you happen to forget the issue with your own package ;-) From phil at bolthole.com Tue Nov 11 16:05:59 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 11 Nov 2008 07:05:59 -0800 Subject: [csw-maintainers] ARCH=all packages Message-ID: <20081111070559.C90125@bolthole.com> Peter B. and I are having a disagreement about the concept of ARCH=all packages, so I thought I would bring the discussion here. The issue is that he wishes to bundle specific binaries for wget in his pkgutil package, AND call it ARCH=all. (he wants to bundle one for sparc and one for x86) I suggested that he either remove the binaries and use pure perl, (either with a full wget replacement, or to use it to download "the appropriate binary") or split it up into two separate packages, with appropriate ARCH settings for the binary he includes in each one. He refuses to take either path, or offer a third one. Our standards pages say, http://www.opencsw.org/standards/build "{ARCH} is usually the output of `uname -p`. But for certain special packages that run on all solaris hardware, or are otherwise architecture-neutral, it may be preferable to have ARCH=all " I say that this means that archtecture specific binaries, should not be in "ARCH=all" packages. Even if you do not agree that the words clearly state that, it was certainly my INTENTION when I wrote the standard. I wanted "ARCH=all" to clearly indicate, "this package will work EVERYWHERE, it will never need recompiling, and it is safe to be shared in some kind of NFS /opt/csw for any and all solaris machines to use." In other words, ARCH=all should be reserved for things like raw arch-neutral data files, docs, java, and shellscripts/perl/python. (I originally intended to use "ARCH=any"... however, I followed sun's lead; sun uses ARCH=all, and does not use ARCH=any, to the best of my knowlege, for this purpose) What are peoples' comments on this? From pfelecan at blastwave.org Tue Nov 11 16:13:58 2008 From: pfelecan at blastwave.org (Peter FELECAN) Date: Tue, 11 Nov 2008 16:13:58 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111070559.C90125@bolthole.com> (Philip Brown's message of "Tue\, 11 Nov 2008 07\:05\:59 -0800") References: <20081111070559.C90125@bolthole.com> Message-ID: Philip Brown writes: > In other words, ARCH=all should be reserved for things like raw > arch-neutral data files, docs, java, and shellscripts/perl/python. +1 -- Peter From james at opencsw.org Tue Nov 11 17:03:21 2008 From: james at opencsw.org (James Lee) Date: Tue, 11 Nov 2008 16:03:21 GMT Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111070559.C90125@bolthole.com> References: <20081111070559.C90125@bolthole.com> Message-ID: <20081111.16032100.3120983528@gyor.oxdrove.co.uk> On 11/11/08, 15:05:59, Philip Brown wrote regarding [csw-maintainers] ARCH=all packages: > The issue is that he wishes to bundle specific binaries for wget in his > pkgutil package, AND call it ARCH=all. > (he wants to bundle one for sparc and one for x86) > I suggested that he either remove the binaries and use pure perl, > (either with a full wget replacement, or to use it to download > "the appropriate binary") > or split it up into two separate packages, with appropriate ARCH settings > for the binary he includes in each one. > Our standards pages say, > http://www.opencsw.org/standards/build > "{ARCH} is usually the output of `uname -p`. But for certain special > packages that run on all solaris hardware, or are otherwise > architecture-neutral, it may be preferable to have ARCH=all " > I say that this means that archtecture specific binaries, should not be > in "ARCH=all" packages. Even if you do not agree that the words clearly > state that, it was certainly my INTENTION when I wrote the standard. > I wanted "ARCH=all" to clearly indicate, "this package will work > EVERYWHERE, it will never need recompiling, and it is safe to be shared > in some kind of NFS /opt/csw for any and all solaris machines to use." We do make arch specific packages that include binaries that don't run on all machines, eg, amd64 files in i386 packages and vis2 files in sparc packages. Therefore if an isaexec like mechanism is used to invoke wget then it meets "this package will work EVERYWHERE". CSWelipse used to be an example of this, from eclipse-3.0-SunOS5.8-all-CSW.pkg.gz: /opt/csw/lib/eclipse/eclipse.i386 /opt/csw/lib/eclipse/eclipse.sparc out of an 80MB package. Unlike eclipse, wget is many times bigger that pkgutil so why not just make each arch specific. We normally split out arch neutral files to save storage space eg, the language files of OpenOffice.org, but here there is only small saving on mirror storage but offset by a large increase user download and user storage. -rwxr-xr-x 1 james staff 164576 Nov 10 17:25 wget-i386* -rwxr-xr-x 1 james staff 224672 Nov 10 17:25 wget-sparc* -rwxr-xr-x 1 james staff 29124 Nov 11 08:41 pkgutil* The gain is what? To offer a single download for pkgutil and so simplify the first step documentation and set up actions. My choice is use perl as the default downloader. Task one for the tool can be to install CSWwget. James. From bonivart at opencsw.org Tue Nov 11 17:09:58 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Tue, 11 Nov 2008 17:09:58 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111070559.C90125@bolthole.com> References: <20081111070559.C90125@bolthole.com> Message-ID: <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com> On Tue, Nov 11, 2008 at 4:05 PM, Philip Brown wrote: > He refuses to take either path, or offer a third one. Because it works fine the way it is and it's easier for the users to not have to make a choice since this is likely to be the first package they download manually to get going. Mac packages often contain code for both PowerPC and x86 so they don't have to choose. It's the same thing. You approved the two first versions of pkgutil with exactly the same design. Not to mention your own pkg-get is incorrectly named without the REV-field which is real easy to read from the standard without any convoluted interpretations. You also chose to not gzip it so it would be easier for your users. This is also for being helpful to the users. But that obviously doesn't mean anything to you when it's not your own package. > In other words, ARCH=all should be reserved for things like raw > arch-neutral data files, docs, java, and shellscripts/perl/python. Which is exactly what pkgutil contains from a user point of view, three perl scripts in bin. -- /peter From bwalton at opencsw.org Tue Nov 11 17:16:59 2008 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 11 Nov 2008 11:16:59 -0500 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111070559.C90125@bolthole.com> References: <20081111070559.C90125@bolthole.com> Message-ID: <1226420167-sup-615@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Tue Nov 11 10:05:59 -0500 2008: > Peter B. and I are having a disagreement about the concept of ARCH=all > packages, so I thought I would bring the discussion here. > > The issue is that he wishes to bundle specific binaries for wget in his > pkgutil package, AND call it ARCH=all. > (he wants to bundle one for sparc and one for x86) > > I suggested that he either remove the binaries and use pure perl, > (either with a full wget replacement, or to use it to download > "the appropriate binary") > or split it up into two separate packages, with appropriate ARCH settings > for the binary he includes in each one. A few ideas: 1. Does the standard perl as shipped on sol8 include Net::HTTP and a checksumming module sufficient for pulling down a wget binary and verifying it? If so, I think that would ultimately be the best solution, as you don't want these 'spare' wget binaries after the system is 'csw bootstrapped' anyway. 2. Alternately, the tool could bootstrap the installation of Net::HTTP from cpan? This treads into territory that could cause problems too, since it will affect things outside of /opt/csw. 3. Include ascii-armored(/clear-signed?) versions of the applicable wget binaries in the share/doc/pkgutil/bootstrap part of the packages' file tree? > I say that this means that architecture specific binaries, should not be in > "ARCH=all" packages. Even if you do not agree that the words clearly state > that, it was certainly my INTENTION when I wrote the standard. > I wanted "ARCH=all" to clearly indicate, "this package will work > EVERYWHERE, it will never need recompiling, and it is safe to be shared in > some kind of NFS /opt/csw for any and all solaris machines to use." I agree with this and think it's best to adhere to it if at all possible. If any package were to be made an exception though, this would be a good candidate in my estimation since it has a pivotal role in getting a system boot-strapped to csw in the first place. > In other words, ARCH=all should be reserved for things like raw > arch-neutral data files, docs, java, and shellscripts/perl/python. If the wget binaries were no longer in binary form (ascii armored), would that skirt the definition enough to appease all? pkgutil would simply treat them as data and use the appropriate one to pull down the CSWwget package initially... The definition of ARCH=all could also be taken to mean that the package will provide equal _functionality_ on all supported machines, which in this case it would. I'm not suggesting that this _should_ be how the definition is read, just that it _could_ be read that way. -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 Nov 11 17:24:49 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 11 Nov 2008 08:24:49 -0800 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <1226420167-sup-615@ntdws12.chass.utoronto.ca>; from bwalton@opencsw.org on Tue, Nov 11, 2008 at 11:16:59AM -0500 References: <20081111070559.C90125@bolthole.com> <1226420167-sup-615@ntdws12.chass.utoronto.ca> Message-ID: <20081111082449.B66221@bolthole.com> On Tue, Nov 11, 2008 at 11:16:59AM -0500, Ben Walton wrote: > A few ideas: > > 1. Does the standard perl as shipped on sol8 include Net::HTTP no. only IO::Socket comes close. I suggested that peter include Net::Ftp and use that. > 3. Include ascii-armored(/clear-signed?) versions of the applicable wget > binaries in the share/doc/pkgutil/bootstrap part of the packages' file > tree? It's not the issue of "binary" so much as it is "arch specific". ascii "arch specific" data is not allowed in "ARCH=all" either. As a side note: At the top level of every mirror is "wget.sparc" and "wget.i386". it is fairly easy to either use perl-ftp, or /bin/ftp, to grab them automatically, if needed. From phil at bolthole.com Tue Nov 11 17:30:44 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 11 Nov 2008 08:30:44 -0800 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com>; from bonivart@opencsw.org on Tue, Nov 11, 2008 at 05:09:58PM +0100 References: <20081111070559.C90125@bolthole.com> <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com> Message-ID: <20081111083044.C66221@bolthole.com> On Tue, Nov 11, 2008 at 05:09:58PM +0100, Peter Bonivart wrote: > > You approved the two first versions of pkgutil with exactly the same > design. I didnt notice the problem earlier. If I did, I wouldnt have let it through then either. > Not to mention your own pkg-get is incorrectly named without > the REV-field I fixed that. > You also chose to not gzip it so it would be easier for your users. As I already pointed out in email, that is a *requirement* for use, since solaris 8 core does not include gzip, and it is logical that they would want to use pkg-get to install gzip. If you had said you wanted to do similarly with yours, I would have said that's fine, for the same reasons. > > In other words, ARCH=all should be reserved for things like raw > > arch-neutral data files, docs, java, and shellscripts/perl/python. > > Which is exactly what pkgutil contains from a user point of view, > three perl scripts in bin. It doesnt matter what the user "sees". It matters that the description/labelling of the package, match the package. The contents of the package, do not match the above description of ARCH=all $ file CSWpkgutil/root/opt/csw/libexec/pkgutil/wget-i386 CSWpkgutil/root/opt/csw/libexec/pkgutil/wget-i386: ELF 32-bit LSB executable 80386 Version 1, dynamically linked, stripped From william at wbonnet.net Tue Nov 11 17:31:18 2008 From: william at wbonnet.net (William Bonnet) Date: Tue, 11 Nov 2008 17:31:18 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: References: <20081111070559.C90125@bolthole.com> Message-ID: <4919B356.6070006@wbonnet.net> Peter FELECAN a ?crit : > Philip Brown writes: > > >> In other words, ARCH=all should be reserved for things like raw >> arch-neutral data files, docs, java, and shellscripts/perl/python. >> > > +1 > +1 From william at wbonnet.net Tue Nov 11 17:33:32 2008 From: william at wbonnet.net (William Bonnet) Date: Tue, 11 Nov 2008 17:33:32 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111.16032100.3120983528@gyor.oxdrove.co.uk> References: <20081111070559.C90125@bolthole.com> <20081111.16032100.3120983528@gyor.oxdrove.co.uk> Message-ID: <4919B3DC.1090301@wbonnet.net> Hi James > Therefore if an isaexec like mechanism is used to invoke wget then it > meets "this package will work EVERYWHERE". CSWelipse used to be an > example of this, from eclipse-3.0-SunOS5.8-all-CSW.pkg.gz: > /opt/csw/lib/eclipse/eclipse.i386 > /opt/csw/lib/eclipse/eclipse.sparc > out of an 80MB package. > Yes but it is an old example ;) Now you have an eclipse common packge which is arch independent, and two arch dependent package. The recent version have more than one binary to provide. Cheers, W. From bwalton at opencsw.org Tue Nov 11 17:56:18 2008 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 11 Nov 2008 11:56:18 -0500 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111082449.B66221@bolthole.com> References: <20081111070559.C90125@bolthole.com> <1226420167-sup-615@ntdws12.chass.utoronto.ca> <20081111082449.B66221@bolthole.com> Message-ID: <1226420869-sup-1782@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Tue Nov 11 11:24:49 -0500 2008: > only IO::Socket comes close. Using IO::Socket to approximate wget would be painful. > > 3. Include ascii-armored(/clear-signed?) versions of the applicable wget > > binaries in the share/doc/pkgutil/bootstrap part of the packages' file > > tree? > > It's not the issue of "binary" so much as it is "arch specific". > ascii "arch specific" data is not allowed in "ARCH=all" either. Taking this stance would mean that shipping asm code examples for different architectures in a doc/$assembler/examples would violate the ARCH=all requirements too, no? > As a side note: > At the top level of every mirror is "wget.sparc" and "wget.i386". > it is fairly easy to either use perl-ftp, or /bin/ftp, to grab them > automatically, if needed. Yes, that would work too...automating /bin/ftp is a pita though. And I don't think it supports PASSIVE ftp, which may be an issue at some sites. HTTP is an easier target protocol from this vantage, although lack of a nice tool by default is why we're having this discussion in the first place! :) I don't really care one way or another how this is eventually handled. Ease of use for the end users should be the key requirement, so any solution that allows them to forgo an extra manual download works for me. 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 Nov 11 18:05:34 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 11 Nov 2008 09:05:34 -0800 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <1226420869-sup-1782@ntdws12.chass.utoronto.ca>; from bwalton@opencsw.org on Tue, Nov 11, 2008 at 11:56:18AM -0500 References: <20081111070559.C90125@bolthole.com> <1226420167-sup-615@ntdws12.chass.utoronto.ca> <20081111082449.B66221@bolthole.com> <1226420869-sup-1782@ntdws12.chass.utoronto.ca> Message-ID: <20081111090534.D66221@bolthole.com> On Tue, Nov 11, 2008 at 11:56:18AM -0500, Ben Walton wrote: > > It's not the issue of "binary" so much as it is "arch specific". > > ascii "arch specific" data is not allowed in "ARCH=all" either. > > Taking this stance would mean that shipping asm code examples for > different architectures in a doc/$assembler/examples would violate the > ARCH=all requirements too, no? oooo... way to dance the line right to the edge :-) Giving "examples", I think is equivalent to "documentation", though. From bwalton at opencsw.org Tue Nov 11 18:11:21 2008 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 11 Nov 2008 12:11:21 -0500 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111090534.D66221@bolthole.com> References: <20081111070559.C90125@bolthole.com> <1226420167-sup-615@ntdws12.chass.utoronto.ca> <20081111082449.B66221@bolthole.com> <1226420869-sup-1782@ntdws12.chass.utoronto.ca> <20081111090534.D66221@bolthole.com> Message-ID: <1226423256-sup-2969@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Tue Nov 11 12:05:34 -0500 2008: > On Tue, Nov 11, 2008 at 11:56:18AM -0500, Ben Walton wrote: > > > It's not the issue of "binary" so much as it is "arch specific". > > > ascii "arch specific" data is not allowed in "ARCH=all" either. > > > > Taking this stance would mean that shipping asm code examples for > > different architectures in a doc/$assembler/examples would violate the > > ARCH=all requirements too, no? > > oooo... way to dance the line right to the edge :-) > Giving "examples", I think is equivalent to "documentation", though. Nobody said we couldn't have fun here! :) You could look at it as something potentially consumable by the binaries that ship with the package, which would allow wget binaries in ascii form to get through the definition too. Anyway, if there is a reasonable way to acquire wget without bending the definitions, that's clearly better. -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 bonivart at opencsw.org Tue Nov 11 18:33:27 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Tue, 11 Nov 2008 18:33:27 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111083044.C66221@bolthole.com> References: <20081111070559.C90125@bolthole.com> <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com> <20081111083044.C66221@bolthole.com> Message-ID: <625385e30811110933s17a2940fk987fbb6734910f5f@mail.gmail.com> On Tue, Nov 11, 2008 at 5:30 PM, Philip Brown wrote: > It doesnt matter what the user "sees". It matters that the > description/labelling of the package, match the package. > The contents of the package, do not match the above description of ARCH=all That's just your interpretation to make this more complicated than it needs to be. The package runs on all architectures we support and should therefor be delivered as one package, that's a much more reasonable interpretation. There's no harm in it and it's simpler for the user to get going. -- /peter From a.cervellin at acm.org Tue Nov 11 18:55:02 2008 From: a.cervellin at acm.org (Alessio) Date: Tue, 11 Nov 2008 18:55:02 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <625385e30811110933s17a2940fk987fbb6734910f5f@mail.gmail.com> References: <20081111070559.C90125@bolthole.com> <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com> <20081111083044.C66221@bolthole.com> <625385e30811110933s17a2940fk987fbb6734910f5f@mail.gmail.com> Message-ID: <4919C6F6.90404@acm.org> Peter Bonivart wrote: > On Tue, Nov 11, 2008 at 5:30 PM, Philip Brown wrote: >> It doesnt matter what the user "sees". It matters that the >> description/labelling of the package, match the package. >> The contents of the package, do not match the above description of ARCH=all > > That's just your interpretation to make this more complicated than it > needs to be. The package runs on all architectures we support and > should therefor be delivered as one package, that's a much more > reasonable interpretation. > > There's no harm in it and it's simpler for the user to get going. +1 From phil at bolthole.com Tue Nov 11 19:05:30 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 11 Nov 2008 10:05:30 -0800 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <4919C6F6.90404@acm.org>; from a.cervellin@acm.org on Tue, Nov 11, 2008 at 06:55:02PM +0100 References: <20081111070559.C90125@bolthole.com> <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com> <20081111083044.C66221@bolthole.com> <625385e30811110933s17a2940fk987fbb6734910f5f@mail.gmail.com> <4919C6F6.90404@acm.org> Message-ID: <20081111100530.E66221@bolthole.com> On Tue, Nov 11, 2008 at 06:55:02PM +0100, Alessio wrote: > Peter Bonivart wrote: > > On Tue, Nov 11, 2008 at 5:30 PM, Philip Brown wrote: > >> It doesnt matter what the user "sees". It matters that the > >> description/labelling of the package, match the package. > >> The contents of the package, do not match the above description of ARCH=all > > > > That's just your interpretation to make this more complicated than it > > needs to be. The package runs on all architectures we support and > > should therefor be delivered as one package, that's a much more > > reasonable interpretation. > > > > There's no harm in it and it's simpler for the user to get going. > > +1 Are you still a maintainer here Alessio? I thought that you only packaged for blastwave.org now? From a.cervellin at acm.org Tue Nov 11 19:33:13 2008 From: a.cervellin at acm.org (Alessio) Date: Tue, 11 Nov 2008 19:33:13 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111100530.E66221@bolthole.com> References: <20081111070559.C90125@bolthole.com> <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com> <20081111083044.C66221@bolthole.com> <625385e30811110933s17a2940fk987fbb6734910f5f@mail.gmail.com> <4919C6F6.90404@acm.org> <20081111100530.E66221@bolthole.com> Message-ID: <4919CFE9.6040600@acm.org> Philip Brown wrote: > On Tue, Nov 11, 2008 at 06:55:02PM +0100, Alessio wrote: >> Peter Bonivart wrote: >>> On Tue, Nov 11, 2008 at 5:30 PM, Philip Brown wrote: >>>> It doesnt matter what the user "sees". It matters that the >>>> description/labelling of the package, match the package. >>>> The contents of the package, do not match the above description of ARCH=all >>> That's just your interpretation to make this more complicated than it >>> needs to be. The package runs on all architectures we support and >>> should therefor be delivered as one package, that's a much more >>> reasonable interpretation. >>> >>> There's no harm in it and it's simpler for the user to get going. >> +1 > > Are you still a maintainer here Alessio? no, i didn't give up, as i always said - because i like to be clear - i join both the projects waiting to see how things are organized and how much *open* are these projects. and of course, i'm not the only maintainer in this situation. actually, the future does not seem to be clear on blastwave nor on opencsw (maybe after the IRL meeting...) whenever i'll leave this project, i'll just announce that. in the meanwhile if someone wants to take over some of my packages, he's of course free to do so. > I thought that you only packaged for blastwave.org now? the only package i released recently in the blastwave catalog is seamonkey, and i've not yet released it on csw because i still have to learn gar. From phil at bolthole.com Tue Nov 11 19:48:28 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 11 Nov 2008 10:48:28 -0800 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <4919CFE9.6040600@acm.org>; from a.cervellin@acm.org on Tue, Nov 11, 2008 at 07:33:13PM +0100 References: <20081111070559.C90125@bolthole.com> <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com> <20081111083044.C66221@bolthole.com> <625385e30811110933s17a2940fk987fbb6734910f5f@mail.gmail.com> <4919C6F6.90404@acm.org> <20081111100530.E66221@bolthole.com> <4919CFE9.6040600@acm.org> Message-ID: <20081111104828.F66221@bolthole.com> On Tue, Nov 11, 2008 at 07:33:13PM +0100, Alessio wrote: > > I thought that you only packaged for blastwave.org now? > > the only package i released recently in the blastwave catalog is > seamonkey, and i've not yet released it on csw because i still have to > learn gar. "have to" is rather an overstatement. There is still no requirement to put things in gar, before putting a package in newpkgs here. From a.cervellin at acm.org Tue Nov 11 19:51:22 2008 From: a.cervellin at acm.org (Alessio) Date: Tue, 11 Nov 2008 19:51:22 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111104828.F66221@bolthole.com> References: <20081111070559.C90125@bolthole.com> <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com> <20081111083044.C66221@bolthole.com> <625385e30811110933s17a2940fk987fbb6734910f5f@mail.gmail.com> <4919C6F6.90404@acm.org> <20081111100530.E66221@bolthole.com> <4919CFE9.6040600@acm.org> <20081111104828.F66221@bolthole.com> Message-ID: <4919D42A.2060306@acm.org> Philip Brown wrote: > On Tue, Nov 11, 2008 at 07:33:13PM +0100, Alessio wrote: >>> I thought that you only packaged for blastwave.org now? >> the only package i released recently in the blastwave catalog is >> seamonkey, and i've not yet released it on csw because i still have to >> learn gar. > > "have to" is rather an overstatement. There is still no requirement to put > things in gar, before putting a package in newpkgs here. i thought GAR was the standard adopted for opencsw... does this mean we can still package the old way and continue to ignore gar? From dam at opencsw.org Tue Nov 11 19:57:45 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 11 Nov 2008 19:57:45 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <4919D42A.2060306@acm.org> References: <20081111070559.C90125@bolthole.com> <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com> <20081111083044.C66221@bolthole.com> <625385e30811110933s17a2940fk987fbb6734910f5f@mail.gmail.com> <4919C6F6.90404@acm.org> <20081111100530.E66221@bolthole.com> <4919CFE9.6040600@acm.org> <20081111104828.F66221@bolthole.com> <4919D42A.2060306@acm.org> Message-ID: Hi Alessio, Am 11.11.2008 um 19:51 schrieb Alessio: > Philip Brown wrote: >> On Tue, Nov 11, 2008 at 07:33:13PM +0100, Alessio wrote: >> >>> I thought that you only packaged for blastwave.org now? >>> the only package i released recently in the blastwave catalog is >>> seamonkey, and i've not yet released it on csw because i still >>> have to >>> learn gar. >> >> "have to" is rather an overstatement. There is still no requirement >> to put >> things in gar, before putting a package in newpkgs here. > > i thought GAR was the standard adopted for opencsw... does this mean > we > can still package the old way and continue to ignore gar? At this moment it is possible to deliver packages which have no build description in GAR, yes. I am in favor of changing this when we have a usable documentation for GAR which we don't have yet. I have converted some documentation at but especially the tutorial is not finished, the new features are not document and there is no reference section. But yes, as of today you can submit packages built with everything you want. Best regards -- Dago From dam at opencsw.org Tue Nov 11 19:59:31 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 11 Nov 2008 19:59:31 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111100530.E66221@bolthole.com> References: <20081111070559.C90125@bolthole.com> <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com> <20081111083044.C66221@bolthole.com> <625385e30811110933s17a2940fk987fbb6734910f5f@mail.gmail.com> <4919C6F6.90404@acm.org> <20081111100530.E66221@bolthole.com> Message-ID: <2728D8EC-6849-4533-A131-28FF5E4C3C11@opencsw.org> Hi Phil, Am 11.11.2008 um 19:05 schrieb Philip Brown: > On Tue, Nov 11, 2008 at 06:55:02PM +0100, Alessio wrote: >> +1 > > Are you still a maintainer here Alessio? Yes, because he promised to build a new pbzip2 for me which can (finally!) compress streams from stdin :-) Best regards -- Dago From phil at bolthole.com Tue Nov 11 20:00:38 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 11 Nov 2008 11:00:38 -0800 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <4919D42A.2060306@acm.org>; from a.cervellin@acm.org on Tue, Nov 11, 2008 at 07:51:22PM +0100 References: <20081111070559.C90125@bolthole.com> <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com> <20081111083044.C66221@bolthole.com> <625385e30811110933s17a2940fk987fbb6734910f5f@mail.gmail.com> <4919C6F6.90404@acm.org> <20081111100530.E66221@bolthole.com> <4919CFE9.6040600@acm.org> <20081111104828.F66221@bolthole.com> <4919D42A.2060306@acm.org> Message-ID: <20081111110038.G66221@bolthole.com> On Tue, Nov 11, 2008 at 07:51:22PM +0100, Alessio wrote: > i thought GAR was the standard adopted for opencsw... does this mean we > can still package the old way and continue to ignore gar? At this time, yes. From dam at opencsw.org Tue Nov 11 20:35:15 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 11 Nov 2008 20:35:15 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111070559.C90125@bolthole.com> References: <20081111070559.C90125@bolthole.com> Message-ID: <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> Hi, Am 11.11.2008 um 16:05 schrieb Philip Brown: > Our standards pages say, > > http://www.opencsw.org/standards/build > "{ARCH} is usually the output of `uname -p`. But for certain special > packages that run on all solaris hardware, or are otherwise > architecture-neutral, it may be preferable to have ARCH=all " Well, the standard is not clear in this point. It could mean (a) the package doesn't contain data which is interpreted differently on different platforms (b) the package can be used on any platform, irregardless of how this is achieved. > I say that this means that archtecture specific binaries, should not > be in > "ARCH=all" packages. Complying to a standard is not a virtue on its own. When you wrote this you had an idea what you invented it for. The only thing I can think of is to save disk space. We may discuss here "cleanlyness of implementation" or "pureness of packages", but does it really get to the point? IMHO the point is "Does it work?" And providing multiple binaries in one package does work. There was the argument of diskspace when installed. This can be easily solved by putting the different binaries in separate install classes (like 'sparc' and 'i386') and install only the binary needed. > Even if you do not agree that the words clearly state > that, it was certainly my INTENTION when I wrote the standard. That's the nice thing about standards, isn't it? ;-) For myself I maintain the SE Toolkit (RICHPse), which traditionally is a package that contains binaries for sparc and x86 for maximum ease of use. However, I made two packages because having one large package is not easier for the users. But converting the build-infrastructure from the package was hell :-P ...and now please forget all of what I wrote above. Because those were technical arguments. Including binaries for sparc and i386 does work, and having two packages works also. The whole discussion is not technical. So gentlemen, please: Peter: Is it really that important to have one fat package instead of two? An admin usually does know on which platform he is on. Will the package be installed on NFS and would it be run from sparc and i386 at the same time? I guess not. So two packages won't hurt and would fully comply with the OpenCSW standard without further discussion. Phil: The standard is not clear here, regardless of what you intended with it. The package does work and it is usually the responsibility of the maintainer to build the package in the best way he thinks. The release manager (you :-) can give advice on improvements, but if the maintainer is reluctant to implement them the package must be released. Unless, of course, it violates the standard... So, Peter, would you please deliver two packages and you, Phil, then release the combined package? ;-) Best regards -- Dago From a.cervellin at acm.org Tue Nov 11 20:43:03 2008 From: a.cervellin at acm.org (Alessio) Date: Tue, 11 Nov 2008 20:43:03 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <2728D8EC-6849-4533-A131-28FF5E4C3C11@opencsw.org> References: <20081111070559.C90125@bolthole.com> <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com> <20081111083044.C66221@bolthole.com> <625385e30811110933s17a2940fk987fbb6734910f5f@mail.gmail.com> <4919C6F6.90404@acm.org> <20081111100530.E66221@bolthole.com> <2728D8EC-6849-4533-A131-28FF5E4C3C11@opencsw.org> Message-ID: <4919E047.5070300@acm.org> Dagobert Michelsen wrote: > Hi Phil, > > Am 11.11.2008 um 19:05 schrieb Philip Brown: >> On Tue, Nov 11, 2008 at 06:55:02PM +0100, Alessio wrote: >>> +1 >> Are you still a maintainer here Alessio? > > Yes, because he promised to build a new pbzip2 for me > which can (finally!) compress streams from stdin :-) and as you could have seen, i have not yet released it even for blastwave. i downloaded the sources and had some minor problems packaging it, but i promise i'll do. From bonivart at opencsw.org Tue Nov 11 22:13:04 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Tue, 11 Nov 2008 22:13:04 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> Message-ID: <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> On Tue, Nov 11, 2008 at 8:35 PM, Dagobert Michelsen wrote: > Peter: Is it really that important to have one fat package > instead of two? An admin usually does know on which platform > he is on. Will the package be installed on NFS and would it > be run from sparc and i386 at the same time? I guess not. > So two packages won't hurt and would fully comply with the > OpenCSW standard without further discussion. I liked your idea with install classes but since that would also provide binaries for both sparc and i386 our self-appointed release dictator would block that too. > Phil: The standard is not clear here, regardless of what you > intended with it. The package does work and it is usually > the responsibility of the maintainer to build the package > in the best way he thinks. The release manager (you :-) can > give advice on improvements, but if the maintainer is > reluctant to implement them the package must be released. > Unless, of course, it violates the standard... Some nice points there. Better yet would be if the release process would be shared between several (active, not spares) people to bring some democracy to this important process. To be voted down by a majority is fine but having one man to write the standard, interpret the standard and even rewrite it to fit his means if necessary, singlehandedly control all releases and ruling in all matters overall is just wrong in a community that calls itself open. It should however be noted that said man of course protested against that name. Dennis used to complain about it and he was right about that. Maybe Z?rich can bring some much needed change. > So, Peter, would you please deliver two packages and > you, Phil, then release the combined package? ;-) I will do that because at this point it's the only way to get it released at all and I won't give Phil the pleasure of not having it released just to prove a point. -- /peter From dam at opencsw.org Tue Nov 11 22:17:16 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 11 Nov 2008 22:17:16 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> Message-ID: <51C0A148-67DA-4121-B3E2-4A107E04CA60@opencsw.org> Hi Peter, Am 11.11.2008 um 22:13 schrieb Peter Bonivart: > Maybe Z?rich can bring some much needed change. So, you're coming then? Best regards -- Dago From bonivart at opencsw.org Tue Nov 11 22:28:25 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Tue, 11 Nov 2008 22:28:25 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <51C0A148-67DA-4121-B3E2-4A107E04CA60@opencsw.org> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <51C0A148-67DA-4121-B3E2-4A107E04CA60@opencsw.org> Message-ID: <625385e30811111328h79e42f9dsad7f772e4ff19583@mail.gmail.com> On Tue, Nov 11, 2008 at 10:17 PM, Dagobert Michelsen wrote: > Am 11.11.2008 um 22:13 schrieb Peter Bonivart: >> Maybe Z?rich can bring some much needed change. > > So, you're coming then? No, I don't want to be in the same country as Phil. Seriously, you, and probably all others who will attend, know where I stand. If I'm alone thinking we need to open up a lot of stuff then I will have to accept that and decide if I want to keep butting heads with Phil or do something else with my time. For reference, here's some suggestions I wrote a while ago: http://wiki.opencsw.org/suggestions -- /peter From phil at bolthole.com Tue Nov 11 22:31:35 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 11 Nov 2008 13:31:35 -0800 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com>; from bonivart@opencsw.org on Tue, Nov 11, 2008 at 10:13:04PM +0100 References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> Message-ID: <20081111133135.M66221@bolthole.com> On Tue, Nov 11, 2008 at 10:13:04PM +0100, Peter Bonivart wrote: > > Some nice points there. Better yet would be if the release process > would be shared between several (active, not spares) people to bring > some democracy to this important process. Meaning, you want to have someone else to push your package though, who wont hold you to standards. You claim you want democracy, when things arent going your way. But here's the thing; Democracy is all about "the majority of people who 'vote'", and the majority of people who "voted" here today on the list, were in favor of keeping ARCH=all free of arch specific binaries. So if you TRUELY respected this democracy you claim you wanted, you would say, "sorry, I was wrong; i'll go with the majority", and strip out the binaries completely. but it seems to be more about "not letting me 'score' a point" with you, even though I dont give a toss about that: > > So, Peter, would you please deliver two packages and > > you, Phil, then release the combined package? ;-) > > I will do that because at this point it's the only way to get it > released at all and I won't give Phil the pleasure of not having it > released just to prove a point. So anyway, I will be happy to push through your package once it no longer violates standards. Now, are you going to be an active opencsw maintainer, and update any of your OTHER packages? Or just the one package that you wrote for the purpose of trying to undermine me? I'll point out that you have over 25 packages under your name, and many of them appear to be out of date. Some are woefully out of date. Some only somewhat out of date. But some of the ones out of date, are important ones: BIND, dhcp, mailscanner Yet you are spending all your time on a package that we dont actually "need" at the moment. From a.cervellin at acm.org Tue Nov 11 22:36:33 2008 From: a.cervellin at acm.org (Alessio) Date: Tue, 11 Nov 2008 22:36:33 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111133135.M66221@bolthole.com> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> Message-ID: <4919FAE1.7000304@acm.org> Philip Brown wrote: > Yet you are spending all your time on a package that we dont actually > "need" at the moment. not really true, many people complained about the lack of an open pkg-fetching tool. From bonivart at opencsw.org Tue Nov 11 23:04:54 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Tue, 11 Nov 2008 23:04:54 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111133135.M66221@bolthole.com> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> Message-ID: <625385e30811111404x2f4b7c51je75b0a0aae27ed87@mail.gmail.com> On Tue, Nov 11, 2008 at 10:31 PM, Philip Brown wrote: > Meaning, you want to have someone else to push your package though, who > wont hold you to standards. No, I wanted this for a long time, long before the fork between BW and OpenCSW actually. But it's typical for you to enlarge a current issue. You did it with the wiki and you do it now for one package. You, and all other who are interested, can take a look at the revision history on the wiki page I linked to if you want to see when I wrote that. Not that long ago but long before the latest issues between you and me. > You claim you want democracy, when things arent going your way. I can live with democracy, how about you? > Now, are you going to be an active opencsw maintainer, and update any of > your OTHER packages? Or just the one package that you wrote for the > purpose of trying to undermine me? Nice of you to let others know in your own words what you think of my effort with pkgutil. Makes a much stronger point than if I had to repeat something you have said before, that could be questioned but this you wrote yourself. > I'll point out that you have over 25 packages under your name, and many of > them appear to be out of date. Some are woefully out of date. Some only > somewhat out of date. But some of the ones out of date, are important ones: > BIND, dhcp, mailscanner > Yet you are spending all your time on a package that we dont actually > "need" at the moment. Again, before you complain/block others you should clean your own house. To make just one example, I requested an update of your antiword to use for my MailScanner. You have 0.33 packaged which I can't even find listed on their site any longer, the latest 0.37 is from 2005, too much to ask for you to have had time to update? You never even replied to me. To mention BIND is kind of an insult since I very quickly had a safe version released when there was a large DNS flaw circulating this summer and I got lots of credit for it. I would again like to thank those who on short notice helped testing the package. You on the other hand wasted a few precious days extra, that was the start of a debate regarding automated release processes. Maybe not the best example for you to choose... Regarding the "need" for something besides pkg-get it has popped up more than once for several reasons, most regarding your closed license and your total unwillingness to listen to your users. I think there's plenty that can be improved upon and I already have. -- /peter From phil at bolthole.com Tue Nov 11 23:28:13 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 11 Nov 2008 14:28:13 -0800 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <4919FAE1.7000304@acm.org>; from a.cervellin@acm.org on Tue, Nov 11, 2008 at 10:36:33PM +0100 References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> Message-ID: <20081111142813.N66221@bolthole.com> On Tue, Nov 11, 2008 at 10:36:33PM +0100, Alessio wrote: > Philip Brown wrote: > > > Yet you are spending all your time on a package that we dont actually > > "need" at the moment. > > not really true, many people complained about the lack of an open > pkg-fetching tool. That is true, multiple people complained about that issue. But it isnt exactly a functional "need", in the sense of, "it doesnt make our packages work better", or keep them up to date any faster, etc. To my mind, the more pressing need, is to update our out-of-date packages. From a.cervellin at acm.org Tue Nov 11 23:38:13 2008 From: a.cervellin at acm.org (Alessio) Date: Tue, 11 Nov 2008 23:38:13 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111142813.N66221@bolthole.com> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> Message-ID: <491A0955.5020806@acm.org> Philip Brown wrote: > On Tue, Nov 11, 2008 at 10:36:33PM +0100, Alessio wrote: >> Philip Brown wrote: >> >>> Yet you are spending all your time on a package that we dont actually >>> "need" at the moment. >> not really true, many people complained about the lack of an open >> pkg-fetching tool. > > That is true, multiple people complained about that issue. But it isnt > exactly a functional "need", in the sense of, "it doesnt make our packages > work better", or keep them up to date any faster, etc. this is not the point: having a direction board, or having a distributed build farms, or having a wiki, or having an open packaging system, and so on don't make packages work better too, but they are priority things to debate before we continue releasing/updating packages, IMHO. > To my mind, the more pressing need, is to update our out-of-date packages. to your mind, to my mind the more pressing needs are the ones i listed in the mail "the real 1st step" of august 11th, and many if you agreed about it (you too). briefly, priorities are the definition of the community, of the rules, of the management, of the direction board, of the pkg-fetching tool "reference implementation", of the catalog format, of the joining rules, and many other things. later, you can update packages... otherwise, this is blastwave. From phil at bolthole.com Tue Nov 11 23:46:38 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 11 Nov 2008 14:46:38 -0800 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <491A0955.5020806@acm.org>; from a.cervellin@acm.org on Tue, Nov 11, 2008 at 11:38:13PM +0100 References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> <491A0955.5020806@acm.org> Message-ID: <20081111144638.O66221@bolthole.com> On Tue, Nov 11, 2008 at 11:38:13PM +0100, Alessio wrote: > > That is true, multiple people complained about that issue. But it isnt > > exactly a functional "need", in the sense of, "it doesnt make our packages > > work better", or keep them up to date any faster, etc. > > this is not the point: having a direction board, or having a distributed > build farms, or having a wiki, or having an open packaging system, and > so on don't make packages work better too, but they are priority things > to debate before we continue releasing/updating packages, IMHO. I think that those things can continue to be worked on in parallel to updating packages. > to your mind, to my mind the more pressing needs are the ones i listed > in the mail "the real 1st step" of august 11th, and many if you agreed > about it (you too). and I believe they are all listed on the wiki page that peter referenced, and some of them have been listed as already being addressed. Progress is being made in the areas you have listed concerns in. Further progress will be made at the IRL meeting. Meantime, lets also continue to meet the needs of our users, rather than bring things to a grinding halt, Dennis-style. From phil at bolthole.com Wed Nov 12 00:07:45 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 11 Nov 2008 15:07:45 -0800 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <625385e30811111404x2f4b7c51je75b0a0aae27ed87@mail.gmail.com>; from bonivart@opencsw.org on Tue, Nov 11, 2008 at 11:04:54PM +0100 References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <625385e30811111404x2f4b7c51je75b0a0aae27ed87@mail.gmail.com> Message-ID: <20081111150745.P66221@bolthole.com> On Tue, Nov 11, 2008 at 11:04:54PM +0100, Peter Bonivart wrote: > Again, before you complain/block others you should clean your own > house. To make just one example, I requested an update of your > antiword to use for my MailScanner. You have 0.33 packaged which I > can't even find listed on their site any longer, the latest 0.37 is > from 2005, too much to ask for you to have had time to update? I apologise for that dropping off my radar. I have now packaged up the latest version. As far as I know, all of my other packages are up to date. From james at opencsw.org Wed Nov 12 10:54:43 2008 From: james at opencsw.org (James Lee) Date: Wed, 12 Nov 2008 09:54:43 GMT Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111070559.C90125@bolthole.com> References: <20081111070559.C90125@bolthole.com> Message-ID: <20081112.9544300.2897156652@gyor.oxdrove.co.uk> On 11/11/08, 15:05:59, Philip Brown wrote regarding [csw-maintainers] ARCH=all packages: > I suggested that he either remove the binaries and use pure perl, > (either with a full wget replacement, or to use it to download > "the appropriate binary") > or split it up into two separate packages, with appropriate ARCH settings > for the binary he includes in each one. > He refuses to take either path, or offer a third one. Third way: The pkgutil package in the CSW collection has no wget and depends on CSWwget and CSWperl (plus anything else needed). It can be installed using pkg-get and update itself. How does a novice user install this using only 17 key strokes? He/she doesn't. For this provide a first time install only package that contains both wget binaries and maybe hobbled options so it runs in a basic Solaris 8 environment. The first time it runs it will install its depends (wget, perl) and update itself to the latest and greatest all-arch standards-friendly slim-line pkgutil. A "How to Begin" text can the have easier instructions and use a web download with simplified naming and a fixed URL - no version needed in file name. James. From dam at opencsw.org Wed Nov 12 12:54:25 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 12 Nov 2008 12:54:25 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081112.9544300.2897156652@gyor.oxdrove.co.uk> References: <20081111070559.C90125@bolthole.com> <20081112.9544300.2897156652@gyor.oxdrove.co.uk> Message-ID: <69B38927-56A5-4646-9465-69ED53C06365@opencsw.org> Hi James, Am 12.11.2008 um 10:54 schrieb James Lee: > Third way: > > The pkgutil package in the CSW collection has no wget and depends on > CSWwget and CSWperl (plus anything else needed). It can be installed > using pkg-get and update itself. > > How does a novice user install this using only 17 key strokes? He/she > doesn't. For this provide a first time install only package that > contains both wget binaries and maybe hobbled options so it runs in a > basic Solaris 8 environment. The first time it runs it will install > its depends (wget, perl) and update itself to the latest and greatest > all-arch standards-friendly slim-line pkgutil. > > A "How to Begin" text can the have easier instructions and use a web > download with simplified naming and a fixed URL - no version needed in > file name. Good solution. That way the repository stays clean and Peter makes his users happy :-) Best regards -- Dago From trygvel at opencsw.org Wed Nov 12 14:06:54 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Wed, 12 Nov 2008 14:06:54 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> Message-ID: <491AD4EE.3010100@opencsw.org> Peter Bonivart wrote: > On Tue, Nov 11, 2008 at 8:35 PM, Dagobert Michelsen wrote: >> Peter: Is it really that important to have one fat package >> instead of two? An admin usually does know on which platform >> he is on. Will the package be installed on NFS and would it >> be run from sparc and i386 at the same time? I guess not. >> So two packages won't hurt and would fully comply with the >> OpenCSW standard without further discussion. > > I liked your idea with install classes but since that would also > provide binaries for both sparc and i386 our self-appointed release > dictator would block that too. > >> Phil: The standard is not clear here, regardless of what you >> intended with it. The package does work and it is usually >> the responsibility of the maintainer to build the package >> in the best way he thinks. The release manager (you :-) can >> give advice on improvements, but if the maintainer is >> reluctant to implement them the package must be released. >> Unless, of course, it violates the standard... > > Some nice points there. Better yet would be if the release process > would be shared between several (active, not spares) people to bring > some democracy to this important process. To be voted down by a > majority is fine but having one man to write the standard, interpret > the standard and even rewrite it to fit his means if necessary, > singlehandedly control all releases and ruling in all matters overall > is just wrong in a community that calls itself open. It should however > be noted that said man of course protested against that name. Come on. While he's still the only one he is at least discussing it in public with the intention to come to a conclusion. One thing that has happened since the fork are more discussions and openness (at least in my opinion). The situation is getting better, slowly. Moving and coordinating a big, distributed crowd like us is a very slow process. Zurich will hopefully define some ground rules, but we still have lots of kinks to work out. -- Trygve From trygvel at opencsw.org Wed Nov 12 14:10:19 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Wed, 12 Nov 2008 14:10:19 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111142813.N66221@bolthole.com> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> Message-ID: <491AD5BB.1010705@opencsw.org> Philip Brown wrote: > On Tue, Nov 11, 2008 at 10:36:33PM +0100, Alessio wrote: >> Philip Brown wrote: >> >>> Yet you are spending all your time on a package that we dont actually >>> "need" at the moment. >> not really true, many people complained about the lack of an open >> pkg-fetching tool. > > That is true, multiple people complained about that issue. But it isnt > exactly a functional "need", in the sense of, "it doesnt make our packages > work better", or keep them up to date any faster, etc. > > To my mind, the more pressing need, is to update our out-of-date packages. As a group of volunteers you really don't have the right to tell people what they should work on. Peter and everyone else has their own right to work on what they feel like. So do you, and if you feel that the packages you mention should be updated, you should feel free to do so. -- Trygve From trygvel at opencsw.org Wed Nov 12 14:14:18 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Wed, 12 Nov 2008 14:14:18 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111070559.C90125@bolthole.com> References: <20081111070559.C90125@bolthole.com> Message-ID: <491AD6AA.8050201@opencsw.org> Philip Brown wrote: > Peter B. and I are having a disagreement about the concept of ARCH=all > packages, so I thought I would bring the discussion here. > > The issue is that he wishes to bundle specific binaries for wget in his > pkgutil package, AND call it ARCH=all. > (he wants to bundle one for sparc and one for x86) > > I suggested that he either remove the binaries and use pure perl, > (either with a full wget replacement, or to use it to download > "the appropriate binary") > or split it up into two separate packages, with appropriate ARCH settings > for the binary he includes in each one. > > He refuses to take either path, or offer a third one. > > Our standards pages say, > > http://www.opencsw.org/standards/build > "{ARCH} is usually the output of `uname -p`. But for certain special > packages that run on all solaris hardware, or are otherwise > architecture-neutral, it may be preferable to have ARCH=all " > > I say that this means that archtecture specific binaries, should not be in > "ARCH=all" packages. Even if you do not agree that the words clearly state > that, it was certainly my INTENTION when I wrote the standard. > I wanted "ARCH=all" to clearly indicate, "this package will work > EVERYWHERE, it will never need recompiling, and it is safe to be shared in > some kind of NFS /opt/csw for any and all solaris machines to use." > > In other words, ARCH=all should be reserved for things like raw > arch-neutral data files, docs, java, and shellscripts/perl/python. > > (I originally intended to use "ARCH=any"... however, I followed sun's > lead; sun uses ARCH=all, and does not use ARCH=any, to the best > of my knowlege, for this purpose) > > > What are peoples' comments on this? Another option: * Let pkgtool depend on the Perl modules required to do HTTP/FTP stuff * Create (if not already) packages for the modules * Create a pkg stream that includes all the packages and make that downloadable from the frontpage as a "getting started" tool like pkg-get. * PROFIT! The added bonus here is that the pkgtool code and package is kept clean, and once the system is bootstrapped it will be updated like any other package. -- Trygve From dam at opencsw.org Thu Nov 13 17:49:59 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 13 Nov 2008 17:49:59 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <491AD5BB.1010705@opencsw.org> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> <491AD5BB.1010705@opencsw.org> Message-ID: <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> Hi Trygve, Am 12.11.2008 um 14:10 schrieb Trygve Laugst?l: > As a group of volunteers you really don't have the right to tell > people > what they should work on. Peter and everyone else has their own > right to > work on what they feel like. So do you, and if you feel that the > packages you mention should be updated, you should feel free to do so. Of course you are free to work on the projects you like. However, when you release a package, you have the responsibility to update it regularly and fix bugs as they are reported. Having major bugs open for a year or more is simply unacceptable. I am working on a webpage to make this more transparent and to make sure that critical bugs are cared for. The tool is not ready yet, but I'll hope to publish something useful before Zurich so we know where we stand. Best regards -- Dago From william at wbonnet.net Thu Nov 13 18:06:55 2008 From: william at wbonnet.net (William Bonnet) Date: Thu, 13 Nov 2008 18:06:55 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> <491AD5BB.1010705@opencsw.org> <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> Message-ID: <491C5EAF.2090903@wbonnet.net> Hi > Of course you are free to work on the projects you like. However, > when you release a package, you have the responsibility to > update it regularly and fix bugs as they are reported. Having > major bugs open for a year or more is simply unacceptable. > I am working on a webpage to make this more transparent > and to make sure that critical bugs are cared for. The tool is > not ready yet, but I'll hope to publish something useful > before Zurich so we know where we stand. > Would it be possible to receive again the mails with the list of openbugs ? Once FF3 is built, I would like to work on an automated procedure that would notify maintainers of updates (ie : I would receive an email notifying me that FF 2.0.0.17 is no longer the latest available, 2.0.0.18 is available). I talked about this with Yann a few monthes ago. It seems something exists in GAR but i never managed to get it working. If you work on ths please let me know, maybe we can effort on this. cheers From yann at pleiades.fr.eu.org Thu Nov 13 18:08:46 2008 From: yann at pleiades.fr.eu.org (Yann Rouillard) Date: Thu, 13 Nov 2008 18:08:46 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <491C5EAF.2090903@wbonnet.net> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> <491AD5BB.1010705@opencsw.org> <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> <491C5EAF.2090903@wbonnet.net> Message-ID: <491C5F1E.1000608@pleiades.fr.eu.org> William Bonnet a ?crit : > Hi > Once FF3 is built, I would like to work on an automated procedure that > would notify maintainers of updates (ie : I would receive an email > notifying me that FF 2.0.0.17 is no longer the latest available, > 2.0.0.18 is available). I talked about this with Yann a few monthes ago. > It seems something exists in GAR but i never managed to get it working. It's currently a ugly hack and I am not sure it still works. Yann From dam at opencsw.org Thu Nov 13 20:26:08 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 13 Nov 2008 20:26:08 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <491C5EAF.2090903@wbonnet.net> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> <491AD5BB.1010705@opencsw.org> <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> <491C5EAF.2090903@wbonnet.net> Message-ID: <30320D83-B4BD-4805-921F-3FAA0CB29E82@opencsw.org> Hi William, Am 13.11.2008 um 18:06 schrieb William Bonnet: >> Of course you are free to work on the projects you like. However, >> when you release a package, you have the responsibility to >> update it regularly and fix bugs as they are reported. Having >> major bugs open for a year or more is simply unacceptable. >> I am working on a webpage to make this more transparent >> and to make sure that critical bugs are cared for. The tool is >> not ready yet, but I'll hope to publish something useful >> before Zurich so we know where we stand. >> > > Would it be possible to receive again the mails with the list of > openbugs ? Do you mean when a new bug is entered? Don't know. Phil? > Once FF3 is built, I would like to work on an automated procedure that > would notify maintainers of updates (ie : I would receive an email > notifying me that FF 2.0.0.17 is no longer the latest available, > 2.0.0.18 is available). I talked about this with Yann a few monthes > ago. > It seems something exists in GAR but i never managed to get it > working. > > If you work on ths please let me know, maybe we can effort on this. I am thinking of tailoring UFILES_REGEX (the GAR update mechanism) to Mantis to automatically generate an UPDATE request for that package which then gets mailed to the maintainer via Mantis. That way it is clearly visible through bug workflow tools what needs to be done. Best regards -- Dago From phil at bolthole.com Thu Nov 13 20:37:23 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 13 Nov 2008 11:37:23 -0800 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <30320D83-B4BD-4805-921F-3FAA0CB29E82@opencsw.org>; from dam@opencsw.org on Thu, Nov 13, 2008 at 08:26:08PM +0100 References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> <491AD5BB.1010705@opencsw.org> <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> <491C5EAF.2090903@wbonnet.net> <30320D83-B4BD-4805-921F-3FAA0CB29E82@opencsw.org> Message-ID: <20081113113723.A72975@bolthole.com> On Thu, Nov 13, 2008 at 08:26:08PM +0100, Dagobert Michelsen wrote: > > Would it be possible to receive again the mails with the list of > > openbugs ? > > Do you mean when a new bug is entered? Don't know. Phil? no, the "new bug" thing should be working again. perhaps what he was referring to, was what James did during "freeze" cycles. From dam at opencsw.org Thu Nov 13 21:32:52 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 13 Nov 2008 21:32:52 +0100 Subject: [csw-maintainers] build8s at Gore buildfarm down Message-ID: <4027EF7F-041A-4954-A653-0F617CB992AB@opencsw.org> Hi, I am currently moving /home to a bigger disk on build8s.go.opencsw.org on user request. This may take some time. I'll post when the operation is finished. Best regards -- Dago From william at wbonnet.net Thu Nov 13 22:10:18 2008 From: william at wbonnet.net (William Bonnet) Date: Thu, 13 Nov 2008 22:10:18 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <30320D83-B4BD-4805-921F-3FAA0CB29E82@opencsw.org> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> <491AD5BB.1010705@opencsw.org> <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> <491C5EAF.2090903@wbonnet.net> <30320D83-B4BD-4805-921F-3FAA0CB29E82@opencsw.org> Message-ID: <491C97BA.50501@wbonnet.net> Hi > Do you mean when a new bug is entered? Don't know. Phil? > Yes, and also the weekly reminder. > I am thinking of tailoring UFILES_REGEX (the GAR update mechanism) > to Mantis to automatically generate an UPDATE request for that > package which then gets mailed to the maintainer via Mantis. > That way it is clearly visible through bug workflow tools what needs > to be done. > If think it is what i was asking for, even better :) Tell me if you need a tester or some help to set it up. There is a lot of packages to process... 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 phil at bolthole.com Thu Nov 13 22:13:38 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 13 Nov 2008 13:13:38 -0800 Subject: [csw-maintainers] mantis, email notifications In-Reply-To: <20081113113723.A72975@bolthole.com>; from phil@bolthole.com on Thu, Nov 13, 2008 at 11:37:23AM -0800 References: <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> <491AD5BB.1010705@opencsw.org> <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> <491C5EAF.2090903@wbonnet.net> <30320D83-B4BD-4805-921F-3FAA0CB29E82@opencsw.org> <20081113113723.A72975@bolthole.com> Message-ID: <20081113131338.B72975@bolthole.com> On Thu, Nov 13, 2008 at 11:37:23AM -0800, Philip Brown wrote: > no, the "new bug" thing should be working again. Buuuttt, apaprently it isnt. I did not get email notification, when a bug was filed yesterday or so against one of my packages. arg. From trygvel at opencsw.org Fri Nov 14 00:14:04 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Fri, 14 Nov 2008 00:14:04 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> <491AD5BB.1010705@opencsw.org> <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> Message-ID: <491CB4BC.9010504@opencsw.org> Dagobert Michelsen wrote: > Hi Trygve, > > Am 12.11.2008 um 14:10 schrieb Trygve Laugst?l: >> As a group of volunteers you really don't have the right to tell >> people >> what they should work on. Peter and everyone else has their own >> right to >> work on what they feel like. So do you, and if you feel that the >> packages you mention should be updated, you should feel free to do so. > > Of course you are free to work on the projects you like. However, > when you release a package, you have the responsibility to > update it regularly and fix bugs as they are reported. Having > major bugs open for a year or more is simply unacceptable. > I am working on a webpage to make this more transparent > and to make sure that critical bugs are cared for. The tool is > not ready yet, but I'll hope to publish something useful > before Zurich so we know where we stand. Well, this is something that we have to talk about in Zurich. I really can't be expected to update my packages within a certain number of days after a new release/bug/whatever. It is not that I'm going to do it if I have the time, but I don't want to be know as a "bad" maintainer if I don't. I really don't like the fact that we talk about "mine" and "your" packages all the time, they are *our* packages! Having a primary maintainer is probably wise (though it could also be a set of primary maintainers) as those are most likely to know how to fix bugs. If a primary maintainer fails to update the package within reasonable time, I would *hope* that someone can pick up the pieces and publish it. To help supporting a process like that I hope that we can focus on re-producible builds and a better validation framework with Hudson. -- Trygve From william at wbonnet.net Fri Nov 14 00:26:39 2008 From: william at wbonnet.net (William Bonnet) Date: Fri, 14 Nov 2008 00:26:39 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <491CB4BC.9010504@opencsw.org> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> <491AD5BB.1010705@opencsw.org> <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> <491CB4BC.9010504@opencsw.org> Message-ID: <491CB7AF.5070309@wbonnet.net> Hi > I really don't like the fact that we talk about "mine" and "your" > packages all the time, they are *our* packages! Having a primary > maintainer is probably wise (though it could also be a set of primary > maintainers) as those are most likely to know how to fix bugs. If a > primary maintainer fails to update the package within reasonable time, I > would *hope* that someone can pick up the pieces and publish it. > Once again i suggest to create team for set of packages. This has certainly to be discussed in zurich. Basically the idea is that key packages (Mozilla's spawns (FF TB SM), Apache, ssh, foo) or set of packages likke desktop environment (kde, gnome, xfce) should be handle by a team. Organisation has to be defined, but it could be composed of a leader and contributors who can alsoupdate and release things or a "main maintainer" and a "backup maintainer". IMHO we clearly have to define an organization which can handle the problem of releasing security updates when main packager is unavailable for a reasonnable time. 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 phil at bolthole.com Fri Nov 14 00:27:02 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 13 Nov 2008 15:27:02 -0800 Subject: [csw-maintainers] Anyone interested in taking on a NEW package? Message-ID: <20081113152702.H72975@bolthole.com> FYI: there has been a request on our "requested packages" page, for packaging up "inkscape. it is touted as somewhat like adobe illustrator, and outputs in SVG (vector) format. If anyone feels included to take on something spiffy... That would be a cool thing for us to have a package of. http://www.inkscape.org/ From william at wbonnet.net Fri Nov 14 07:50:37 2008 From: william at wbonnet.net (William Bonnet) Date: Fri, 14 Nov 2008 07:50:37 +0100 Subject: [csw-maintainers] Firefox 2.0.0.18 is available Message-ID: <491D1FBD.1010802@wbonnet.net> Hi, The latest update of Firefox (version 2.0.0.18) is now available from testing. This release includes several security fixes ( http://www.mozilla.org/security/known-vulnerabilities/firefox20.html#firefox2.0.0.18 ). The release notes are availables from this place ( http://www.mozilla-europe.org/en/products/firefox/2.0.0.18/releasenotes/ ). This update should be pushed to unstable soon. Thanks for your feedbacks if you experience any problem with this testing version. Best regards, -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From dam at opencsw.org Fri Nov 14 10:25:20 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 14 Nov 2008 10:25:20 +0100 Subject: [csw-maintainers] build8s at Gore buildfarm up again In-Reply-To: <4027EF7F-041A-4954-A653-0F617CB992AB@opencsw.org> References: <4027EF7F-041A-4954-A653-0F617CB992AB@opencsw.org> Message-ID: Hi, Am 13.11.2008 um 21:32 schrieb Dagobert Michelsen: > I am currently moving /home to a bigger disk on > build8s.go.opencsw.org > on user request. This may take some time. I'll > post when the operation is finished. The machine is available again and there are now ca. 135 GB free in /home. Best regards -- Dago From dam at opencsw.org Fri Nov 14 10:41:51 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 14 Nov 2008 10:41:51 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <491C97BA.50501@wbonnet.net> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> <491AD5BB.1010705@opencsw.org> <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> <491C5EAF.2090903@wbonnet.net> <30320D83-B4BD-4805-921F-3FAA0CB29E82@opencsw.org> <491C97BA.50501@wbonnet.net> Message-ID: Hi, Am 13.11.2008 um 18:08 schrieb Yann Rouillard: > William Bonnet a ?crit : >> Once FF3 is built, I would like to work on an automated procedure >> that >> would notify maintainers of updates (ie : I would receive an email >> notifying me that FF 2.0.0.17 is no longer the latest available, >> 2.0.0.18 is available). I talked about this with Yann a few monthes >> ago. >> It seems something exists in GAR but i never managed to get it >> working. > > It's currently a ugly hack and I am not sure it still works. Yann, would you be willing to take a look at it? Am 13.11.2008 um 22:10 schrieb William Bonnet: >> I am thinking of tailoring UFILES_REGEX (the GAR update mechanism) >> to Mantis to automatically generate an UPDATE request for that >> package which then gets mailed to the maintainer via Mantis. >> That way it is clearly visible through bug workflow tools what needs >> to be done. >> > > If think it is what i was asking for, even better :) > > Tell me if you need a tester or some help to set it up. There is a lot > of packages to process... William, what is needed after the mechanism in general works is updating all Makefile with UFILES_REGEX to actually look for updated versions. If you could help updating all the Makefile would be great. After that we can integrate the found results in Mantis. Best regards -- Dago From dam at opencsw.org Fri Nov 14 11:18:53 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 14 Nov 2008 11:18:53 +0100 Subject: [csw-maintainers] Topics on IRL meeting In-Reply-To: <491CB7AF.5070309@wbonnet.net> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> <491AD5BB.1010705@opencsw.org> <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> <491CB4BC.9010504@opencsw.org> <491CB7AF.5070309@wbonnet.net> Message-ID: Hi, Am 14.11.2008 um 00:26 schrieb William Bonnet: > Basically the idea is that key packages (Mozilla's spawns (FF TB > SM), Apache, ssh, foo) or set of packages likke desktop environment > (kde, gnome, xfce) should be handle by a team. Organisation has to > be defined, but it could be composed of a leader and contributors > who can alsoupdate and release things or a "main maintainer" and a > "backup maintainer". I added this to as a lists of topics to talk about. After collecting issues we should group similar items, define a timeframe for discussion and define a chairman for each discussion. I suggest we keep the collections of topics to talk about open for another week until 21.11.08, then group the items. It is not that we can not talk about other items, but because of the vast amount of things to take care of we may get lost in discussion without results without tight structure for the main Saturday. So, feel free to add topics to that page. Best regards -- Dago From mmayer at mmayer.net Fri Nov 14 19:57:17 2008 From: mmayer at mmayer.net (Markus Mayer) Date: Fri, 14 Nov 2008 10:57:17 -0800 Subject: [csw-maintainers] Ouchies Message-ID: <20081114185716.GA13988@bender.opencsw.org> http://biz.yahoo.com/ap/081114/sun_microsystems_layoffs.html I don't know how accurate this assessment is, but it doesn't sound too good: "[...]Sun's latest woes have ramped up speculation that one of the most storied names in computing could be snapped up dirt-cheap by a bigger rival. Hewlett-Packard Co., IBM Corp., and Dell Inc. are all possible suitors." ... "Sun's share price gives the company a market value of roughly $3 billion. Yet at the end of September, Sun had $3.1 billion in cash on hand. The gap indicates extreme pessimism about the company's prospects." Regards, -Markus From phil at bolthole.com Fri Nov 14 20:12:15 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 14 Nov 2008 11:12:15 -0800 Subject: [csw-maintainers] Ouchies In-Reply-To: <20081114185716.GA13988@bender.opencsw.org>; from mmayer@mmayer.net on Fri, Nov 14, 2008 at 10:57:17AM -0800 References: <20081114185716.GA13988@bender.opencsw.org> Message-ID: <20081114111215.K21898@bolthole.com> On Fri, Nov 14, 2008 at 10:57:17AM -0800, Markus Mayer wrote: > > http://biz.yahoo.com/ap/081114/sun_microsystems_layoffs.html > > I don't know how accurate this assessment is, but it doesn't sound > too good: > > "[...]Sun's latest woes have ramped up speculation that one of the most > storied names in computing could be snapped up dirt-cheap by a bigger > rival. Hewlett-Packard Co., IBM Corp., and Dell Inc. are all possible > suitors." Ugh. well, it's not too surprising, when they are wasting time trying to make [Solaris next] "Just like linux", instead of just taking "the good bits" from it, and combining it with what makes people like Sun/Solaris over linux. Arg. From phil at bolthole.com Fri Nov 14 20:23:46 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 14 Nov 2008 11:23:46 -0800 Subject: [csw-maintainers] Ouchies In-Reply-To: <20081114111215.K21898@bolthole.com>; from phil@bolthole.com on Fri, Nov 14, 2008 at 11:12:15AM -0800 References: <20081114185716.GA13988@bender.opencsw.org> <20081114111215.K21898@bolthole.com> Message-ID: <20081114112346.M21898@bolthole.com> On Fri, Nov 14, 2008 at 11:12:15AM -0800, Philip Brown wrote: > On Fri, Nov 14, 2008 at 10:57:17AM -0800, Markus Mayer wrote: > > > > http://biz.yahoo.com/ap/081114/sun_microsystems_layoffs.html Hmph. more from this. Looks like Schwartz fancies himself has a hachet man. "The company has done several rounds of big layoffs in the last three years. Sun has cut 2,700 jobs since August of last year in two separate restructurings. The company had previously cut about 4,000 jobs after Schwartz took over as CEO from co-founder Scott McNealy in 2006." one piece of potential "good" news, is that they are splitting off OS into a separate division once again. We'll see if there's anyone sane left at sun to do a good job of heading it up. sigh. From ihsan at opencsw.org Fri Nov 14 20:42:39 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Fri, 14 Nov 2008 20:42:39 +0100 Subject: [csw-maintainers] Ouchies In-Reply-To: <20081114185716.GA13988@bender.opencsw.org> References: <20081114185716.GA13988@bender.opencsw.org> Message-ID: <491DD4AF.5000000@opencsw.org> Am 14.11.2008 19:57 Uhr, Markus Mayer schrieb: > I don't know how accurate this assessment is, but it doesn't sound > too good: > > "[...]Sun's latest woes have ramped up speculation that one of the most > storied names in computing could be snapped up dirt-cheap by a bigger > rival. Hewlett-Packard Co., IBM Corp., and Dell Inc. are all possible > suitors." > ... > "Sun's share price gives the company a market value of roughly $3 > billion. Yet at the end of September, Sun had $3.1 billion in cash on > hand. The gap indicates extreme pessimism about the company's > prospects." Sun's stock is now at 4.23. It was never that low since 1994! Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ -------------- next part -------------- A non-text attachment was scrubbed... Name: chart_V_3548367_67_1Y.gif Type: image/gif Size: 6669 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: chart_V_3548367_67_1994-04-23_1994-12-31.gif Type: image/gif Size: 6232 bytes Desc: not available URL: From buysse at umn.edu Fri Nov 14 20:44:55 2008 From: buysse at umn.edu (Joshua Buysse) Date: Fri, 14 Nov 2008 13:44:55 -0600 Subject: [csw-maintainers] Ouchies In-Reply-To: <491DD4AF.5000000@opencsw.org> References: <20081114185716.GA13988@bender.opencsw.org> <491DD4AF.5000000@opencsw.org> Message-ID: <62E40CD3-E9E6-4E15-BC75-4222A2B55477@umn.edu> On Nov 14, 2008, at 1:42 PM, Ihsan Dogan wrote: > Am 14.11.2008 19:57 Uhr, Markus Mayer schrieb: >> ... >> "Sun's share price gives the company a market value of roughly $3 >> billion. Yet at the end of September, Sun had $3.1 billion in cash on >> hand. The gap indicates extreme pessimism about the company's >> prospects." > > Sun's stock is now at 4.23. It was never that low since 1994! Are you factoring in that they reverse-split the stock at least once, last couple of years? -J -- Joshua Buysse, System Engineer College of Liberal Arts, Office of Information Technology University of Minnesota "The First Amendment is often inconvenient. But that is besides the point. Inconvenience does not absolve the government of its obligation to tolerate speech." -- Justice Anthony M. Kennedy -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL: From phil at bolthole.com Fri Nov 14 20:57:44 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 14 Nov 2008 11:57:44 -0800 Subject: [csw-maintainers] mantis email.. working....? Message-ID: <20081114115744.P21898@bolthole.com> It appears that Ihsan(?) has managed to unstick something, and I see a flood of old mantis-related emails coming through now :-) I was also trying to just look at things at the same time though. In theory, my "looking" should not have unstuck anything. i only used mailx locally. So, confirmation would be nice, on what was done...? From buysse at cla.umn.edu Fri Nov 14 20:26:41 2008 From: buysse at cla.umn.edu (Joshua Buysse) Date: Fri, 14 Nov 2008 13:26:41 -0600 Subject: [csw-maintainers] Ouchies In-Reply-To: <20081114111215.K21898@bolthole.com> References: <20081114185716.GA13988@bender.opencsw.org> <20081114111215.K21898@bolthole.com> Message-ID: <6A7D9D60-B8AA-4FC3-9AAA-810E0E379AA3@cla.umn.edu> >> http://biz.yahoo.com/ap/081114/sun_microsystems_layoffs.html >> >> I don't know how accurate this assessment is, but it doesn't sound >> too good: >> >> "[...]Sun's latest woes have ramped up speculation that one of the >> most >> storied names in computing could be snapped up dirt-cheap by a bigger >> rival. Hewlett-Packard Co., IBM Corp., and Dell Inc. are all possible >> suitors Hmm. Market cap == cash on hand. Why not go private? Sun should buy itself out and be done with it. Then, focus on long-term stability instead of bloody quarterly earnings. > well, it's not too surprising, when they are wasting time trying to > make > [Solaris next] "Just like linux", instead of just taking > "the good bits" from it, and combining it with what makes people like > Sun/Solaris over linux. -- Joshua Buysse, System Engineer College of Liberal Arts, Office of Information Technology University of Minnesota "A good programmer is someone who looks both ways before crossing a one-way street." -- Doug Linder -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL: From ihsan at opencsw.org Fri Nov 14 22:34:26 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Fri, 14 Nov 2008 22:34:26 +0100 Subject: [csw-maintainers] Ouchies In-Reply-To: <6A7D9D60-B8AA-4FC3-9AAA-810E0E379AA3@cla.umn.edu> References: <20081114185716.GA13988@bender.opencsw.org> <20081114111215.K21898@bolthole.com> <6A7D9D60-B8AA-4FC3-9AAA-810E0E379AA3@cla.umn.edu> Message-ID: <491DEEE2.4060302@opencsw.org> Am 14.11.2008 20:26 Uhr, Joshua Buysse schrieb: >>> "[...]Sun's latest woes have ramped up speculation that one of the most >>> storied names in computing could be snapped up dirt-cheap by a bigger >>> rival. Hewlett-Packard Co., IBM Corp., and Dell Inc. are all possible >>> suitors > Hmm. Market cap == cash on hand. Why not go private? Sun should buy > itself out and be done with it. Then, focus on long-term stability > instead of bloody quarterly earnings. A few years ago, I've read a report about Toyota. The journalist asked, what is the secret of Toyota to be that successful. The answer was, that Toyota is not focused on quarterly earnings. Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From ihsan at opencsw.org Fri Nov 14 22:36:29 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Fri, 14 Nov 2008 22:36:29 +0100 Subject: [csw-maintainers] Ouchies In-Reply-To: <62E40CD3-E9E6-4E15-BC75-4222A2B55477@umn.edu> References: <20081114185716.GA13988@bender.opencsw.org> <491DD4AF.5000000@opencsw.org> <62E40CD3-E9E6-4E15-BC75-4222A2B55477@umn.edu> Message-ID: <491DEF5D.1030008@opencsw.org> Am 14.11.2008 20:44 Uhr, Joshua Buysse schrieb: >> Sun's stock is now at 4.23. It was never that low since 1994! > Are you factoring in that they reverse-split the stock at least once, > last couple of years? After I read that the stock is on 4 $, I was only wondering when it was that low the last time. Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From ihsan at opencsw.org Fri Nov 14 22:38:04 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Fri, 14 Nov 2008 22:38:04 +0100 Subject: [csw-maintainers] mantis email.. working....? In-Reply-To: <20081114115744.P21898@bolthole.com> References: <20081114115744.P21898@bolthole.com> Message-ID: <491DEFBC.2040206@opencsw.org> Am 14.11.2008 20:57 Uhr, Philip Brown schrieb: > It appears that Ihsan(?) has managed to unstick something, and I see a > flood of old mantis-related emails coming through now :-) Well, I just copied the database to the new machine. I hope you don't need anything from the old machine, because it's turned off. Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From phil at bolthole.com Fri Nov 14 22:48:07 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 14 Nov 2008 13:48:07 -0800 Subject: [csw-maintainers] mantis email.. working....? In-Reply-To: <491DEFBC.2040206@opencsw.org>; from ihsan@opencsw.org on Fri, Nov 14, 2008 at 10:38:04PM +0100 References: <20081114115744.P21898@bolthole.com> <491DEFBC.2040206@opencsw.org> Message-ID: <20081114134807.V21898@bolthole.com> On Fri, Nov 14, 2008 at 10:38:04PM +0100, Ihsan Dogan wrote: > Am 14.11.2008 20:57 Uhr, Philip Brown schrieb: > > > It appears that Ihsan(?) has managed to unstick something, and I see a > > flood of old mantis-related emails coming through now :-) > > Well, I just copied the database to the new machine. I hope you don't > need anything from the old machine, because it's turned off. Urrrr... that sounds like, "you didnt do anything". all i did, was run "mailx -v". so maybe that somehow unstuck email. on www.opencsw.org Soo... I'm going to permenantly change the way mantis sends email, to use "connect via SMTP to localhost" and hope that makes things behave better. From phil at bolthole.com Fri Nov 14 22:54:55 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 14 Nov 2008 13:54:55 -0800 Subject: [csw-maintainers] mantis email.. working....? In-Reply-To: <20081114134807.V21898@bolthole.com>; from phil@bolthole.com on Fri, Nov 14, 2008 at 01:48:07PM -0800 References: <20081114115744.P21898@bolthole.com> <491DEFBC.2040206@opencsw.org> <20081114134807.V21898@bolthole.com> Message-ID: <20081114135455.W21898@bolthole.com> On Fri, Nov 14, 2008 at 01:48:07PM -0800, Philip Brown wrote: > Soo... I'm going to permenantly change the way mantis sends email, to use > "connect via SMTP to localhost" and hope that makes things behave better. > that didnt help either??? really odd. email worked when mantis was first set up. From bonivart at opencsw.org Fri Nov 14 23:29:13 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Fri, 14 Nov 2008 23:29:13 +0100 Subject: [csw-maintainers] Class Action Scripts package described on the wiki Message-ID: <625385e30811141429m3e0505f5p321540c14931f443@mail.gmail.com> I have written some about how to support SMF in your packages by using our CSWcswclassutils package that contains class action scripts. It's real easy to add support for SMF in your new and existing packages and it only takes about a minute. Read more here: http://wiki.opencsw.org/cswclassutils The package also contains two scripts from Phil that helps with preserving config files during upgrades. Those have yet to be documented on the wiki. If you read this Phil, feel free to edit those parts of the page. -- /peter From phil at bolthole.com Fri Nov 14 23:48:37 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 14 Nov 2008 14:48:37 -0800 Subject: [csw-maintainers] Class Action Scripts package described on the wiki In-Reply-To: <625385e30811141429m3e0505f5p321540c14931f443@mail.gmail.com>; from bonivart@opencsw.org on Fri, Nov 14, 2008 at 11:29:13PM +0100 References: <625385e30811141429m3e0505f5p321540c14931f443@mail.gmail.com> Message-ID: <20081114144837.Y21898@bolthole.com> On Fri, Nov 14, 2008 at 11:29:13PM +0100, Peter Bonivart wrote: > I have written some about how to support SMF in your packages by using > our CSWcswclassutils package that contains class action scripts. It's > real easy to add support for SMF in your new and existing packages and > it only takes about a minute. > > Read more here: http://wiki.opencsw.org/cswclassutils > Thanks for writing web docs for it. I've made a link to that page from our main smf page. As a reminder to folks: there are TWO big gain from using SMF support from CSWcswclassutils: 1. You may be able to eliminate any postinstall/preremove scripts from your package 2. If we figure out a way later on, to improve the way we handle SMF; you dont have to repackage your package to take advantage of it! The cswclassutils package will get updated once, so everyone else using it, wont have to repackage as well. From phil at bolthole.com Sat Nov 15 00:01:47 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 14 Nov 2008 15:01:47 -0800 Subject: [csw-maintainers] Class Action Scripts package described on the wiki In-Reply-To: <625385e30811141429m3e0505f5p321540c14931f443@mail.gmail.com>; from bonivart@opencsw.org on Fri, Nov 14, 2008 at 11:29:13PM +0100 References: <625385e30811141429m3e0505f5p321540c14931f443@mail.gmail.com> Message-ID: <20081114150147.Z21898@bolthole.com> Hmmm... a side note, after reading your docs, and looking through the latest script again; If someone defines f cswinitsmf /etc/opt/csw/init.d/cswfoo 0755 root bin and the normal default FMRI will be svc:/network/cswfoo:default It appears that using the #FMRI xyz allows you to override the /network part, but "cswfoo" will be preserved, reguardless of anything you put in. Is that correct? I think that probably is the best behaviour overall, but it's been a long time since we discussed it, so I dont remmeber any more :-} Just wanted to first make sure that the above is true, and then update the docs to be completely clear about that. From bonivart at opencsw.org Sat Nov 15 00:14:15 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Sat, 15 Nov 2008 00:14:15 +0100 Subject: [csw-maintainers] Class Action Scripts package described on the wiki In-Reply-To: <20081114150147.Z21898@bolthole.com> References: <625385e30811141429m3e0505f5p321540c14931f443@mail.gmail.com> <20081114150147.Z21898@bolthole.com> Message-ID: <625385e30811141514r1e1587d6sa990dd0db2694be2@mail.gmail.com> On Sat, Nov 15, 2008 at 12:01 AM, Philip Brown wrote: > Hmmm... a side note, after reading your docs, and looking through the latest > script again; > > If someone defines > > f cswinitsmf /etc/opt/csw/init.d/cswfoo 0755 root bin > > and the normal default FMRI will be > > svc:/network/cswfoo:default > > It appears that using the > > #FMRI xyz > > allows you to override the /network part, but "cswfoo" will be preserved, > reguardless of anything you put in. > > Is that correct? Yes, that is correct. It's only the path that can be affected, the name will always come from the init script name. That is, FMRI can change the default "network" into something else, e.g. "network/smtp", but the init script name will always be appended to it. -- /peter From pfelecan at opencsw.org Sat Nov 15 12:10:35 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Sat, 15 Nov 2008 12:10:35 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <625385e30811111328h79e42f9dsad7f772e4ff19583@mail.gmail.com> (Peter Bonivart's message of "Tue\, 11 Nov 2008 22\:28\:25 +0100") References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <51C0A148-67DA-4121-B3E2-4A107E04CA60@opencsw.org> <625385e30811111328h79e42f9dsad7f772e4ff19583@mail.gmail.com> Message-ID: "Peter Bonivart" writes: > On Tue, Nov 11, 2008 at 10:17 PM, Dagobert Michelsen wrote: >> Am 11.11.2008 um 22:13 schrieb Peter Bonivart: >>> Maybe Z?rich can bring some much needed change. > If I'm alone thinking we need to open up a lot of stuff then I You're not alone. > For reference, here's some suggestions I wrote a while ago: > http://wiki.opencsw.org/suggestions A very good basis for parts of the bylaws of the organization. -- Peter From pfelecan at opencsw.org Sat Nov 15 18:43:14 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Sat, 15 Nov 2008 18:43:14 +0100 Subject: [csw-maintainers] "contact maintainer" facility doesn't work Message-ID: The following link: http://www.opencsw.org/eml.php doesn't work; after entering the sender's address and the message, I see: "SERVER ERROR: Cannot submit form.Please try again later." Can this be corrected please? Also, can we have a single page form, i.e. all the information and the submit button on the same page --- currently we have 3 pages... -- Peter From pfelecan at opencsw.org Sat Nov 15 18:47:56 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Sat, 15 Nov 2008 18:47:56 +0100 Subject: [csw-maintainers] mantis access Message-ID: I'm trying to access mantis with the old user name/password couple. It doesn't work. Is the user pfelecan still valid/existing? If yes, I would like my password reset to a known value. BTW, who's in charge with the administration of mantis? -- Peter From trygvel at opencsw.org Sat Nov 15 19:42:40 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sat, 15 Nov 2008 19:42:40 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> Message-ID: <491F1820.6080608@opencsw.org> Dagobert Michelsen wrote: > Hi James, > > Am 08.11.2008 um 17:06 schrieb James Lee: >> On 08/11/08, 15:40:29, Dagobert Michelsen wrote >> regarding >> Re: [csw-maintainers] Java... again!: >> >>> jdk5-1.5.0_15,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz >>> jdk5-1.5.0_15,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz >>> jdk6-6u7,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz >>> jdk6-6u7,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz >> Latest 1.5 is Update 16 >> http://java.sun.com/javase/downloads/index_jdk5.jsp >> >> The latest 1.6 is Update 10. >> http://java.sun.com/javase/downloads/index.jsp > > I got them from the archive page. Who can imagine > archived versions would be old? Me??? Oh well... > Heres some warmed up Java in > : > > jre13-1.3.1_22,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz > jre13-1.3.1_22,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz > jre14-1.4.2_17,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz > jre14-1.4.2_17,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz > jre5-1.5.0_16,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz > jre5-1.5.0_16,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz > jre6-1.6.0_10,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz > jre6-1.6.0_10,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz > > jdk13-1.3.1_22,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz > jdk13-1.3.1_22,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz > jdk14-1.4.2_17,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz > jdk14-1.4.2_17,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz > jdk5-1.5.0_16,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz > jdk5-1.5.0_16,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz > jdk6-1.6.0_10,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz > jdk6-1.6.0_10,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz > >> It identifies itself: >> >> $ java -version >> java version "1.6.0_10" >> Java(TM) SE Runtime Environment (build 1.6.0_10-b33) >> Java HotSpot(TM) Server VM (build 11.0-b15, mixed mode) >> >> So why use break the pattern of naming, I'd expect the package to be >> identified similarly as "1.6.0_10". > > I should never have followed marketing numbers. The package > now identified itself with the technical version number. > > James, do you mind testing these? Some comments: * Can the JDKs be installed under /opt/csw/jdk to reduce the /opt/csw clutter. That also more similar to how it is installed under /usr * I like the way Sun does it with their "instances". If my package depend on Java 5 or 6 I would like to default the JDK path to /opt/csw/jdk/instance/jdk1.5.0. $ ls -l /usr/jdk /usr/jdk/instances/ /usr/jdk: total 10 drwxr-xr-x 4 root bin 512 Feb 29 2008 instances lrwxrwxrwx 1 root other 18 Nov 5 16:30 jdk1.5.0_16 -> instances/jdk1.5.0 lrwxrwxrwx 1 root other 18 Nov 5 16:43 jdk1.6.0_10 -> instances/jdk1.6.0 lrwxrwxrwx 1 root other 11 Nov 5 16:43 latest -> jdk1.6.0_10 drwxr-xr-x 7 root bin 512 Nov 5 16:46 packages /usr/jdk/instances/: total 4 drwxr-xr-x 9 root bin 512 Nov 5 16:49 jdk1.5.0 drwxr-xr-x 9 root bin 512 Nov 5 16:51 jdk1.6.0 -- Trygve From ihsan at opencsw.org Sat Nov 15 21:45:55 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Sat, 15 Nov 2008 21:45:55 +0100 Subject: [csw-maintainers] "contact maintainer" facility doesn't work In-Reply-To: References: Message-ID: <491F3503.3070200@opencsw.org> Hello Peter, On 11/15/08 18:43, Peter FELECAN wrote: > The following link: http://www.opencsw.org/eml.php doesn't work; after > entering the sender's address and the message, I see: > > "SERVER ERROR: Cannot submit form.Please try again later." I just fixed that. The problem was, that PHP was not using /usr/lib/sendmail. Ihsan -- http://blog.dogan.ch/ http://ihsan.dogan.ch/ From phil at bolthole.com Sat Nov 15 21:48:08 2008 From: phil at bolthole.com (Philip Brown) Date: Sat, 15 Nov 2008 12:48:08 -0800 Subject: [csw-maintainers] mantis access In-Reply-To: ; from pfelecan@opencsw.org on Sat, Nov 15, 2008 at 06:47:56PM +0100 References: Message-ID: <20081115124808.B40283@bolthole.com> On Sat, Nov 15, 2008 at 06:47:56PM +0100, Peter FELECAN wrote: > I'm trying to access mantis with the old user name/password couple. It > doesn't work. > > Is the user pfelecan still valid/existing? If yes, I would like my > password reset to a known value. > > BTW, who's in charge with the administration of mantis? i'd rather not be. but effectly, I am :-} i just reset it. course, that wouldht actually HELP you, if email isnt working. but hopefully, Ihsan's fix has it working again now. From dam at opencsw.org Sat Nov 15 23:52:11 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 15 Nov 2008 23:52:11 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <491F1820.6080608@opencsw.org> References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> Message-ID: Hi Trygve, Am 15.11.2008 um 19:42 schrieb Trygve Laugst?l: > Some comments: > > * Can the JDKs be installed under /opt/csw/jdk to reduce the /opt/csw > clutter. That also more similar to how it is installed under /usr Sure. > * I like the way Sun does it with their "instances". If my package > depend on Java 5 or 6 I would like to default the JDK path to > /opt/csw/jdk/instance/jdk1.5.0. > > $ ls -l /usr/jdk /usr/jdk/instances/ > /usr/jdk: > total 10 > drwxr-xr-x 4 root bin 512 Feb 29 2008 instances > lrwxrwxrwx 1 root other 18 Nov 5 16:30 jdk1.5.0_16 -> > instances/jdk1.5.0 > lrwxrwxrwx 1 root other 18 Nov 5 16:43 jdk1.6.0_10 -> > instances/jdk1.6.0 > lrwxrwxrwx 1 root other 11 Nov 5 16:43 latest -> > jdk1.6.0_10 > drwxr-xr-x 7 root bin 512 Nov 5 16:46 packages > > /usr/jdk/instances/: > total 4 > drwxr-xr-x 9 root bin 512 Nov 5 16:49 jdk1.5.0 > drwxr-xr-x 9 root bin 512 Nov 5 16:51 jdk1.6.0 But why /usr/jdk/instances/jdkxxx instead of /usr/jdk/jdkxxxx? Why is there the symlink? And: Should this also be true for JREs? Best regards -- Dago From william at wbonnet.net Sun Nov 16 00:48:39 2008 From: william at wbonnet.net (William Bonnet) Date: Sun, 16 Nov 2008 00:48:39 +0100 Subject: [csw-maintainers] Installing new package on the farm Message-ID: <491F5FD7.3010107@wbonnet.net> Hi Please Dago could you install some new package on the farm ? The packages are "proto" from Xorg which are missing from Solaris. I created these packages to build the dependencies of Firefox. I will have more installation request in the next hours/days. Dependencies will be built step by step... Thanks in advance 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 phil at bolthole.com Sun Nov 16 02:54:48 2008 From: phil at bolthole.com (Philip Brown) Date: Sat, 15 Nov 2008 17:54:48 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: ; from dam@opencsw.org on Sat, Nov 15, 2008 at 11:52:11PM +0100 References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> Message-ID: <20081115175448.A45790@bolthole.com> On Sat, Nov 15, 2008 at 11:52:11PM +0100, Dagobert Michelsen wrote: > Hi Trygve, > > Am 15.11.2008 um 19:42 schrieb Trygve Laugst?l: > > Some comments: > > > > * Can the JDKs be installed under /opt/csw/jdk to reduce the /opt/csw > > clutter. That also more similar to how it is installed under /usr > > Sure. waitaminit.. what about if they only want runtimes? seems like perhaps /opt/csw/java might be better. soo... /opt/csw/java/1.5.0 and under 1.5.0 would be both runtime and jdk executables? From frederic.vandevelde at paradigmo.com Sun Nov 16 10:02:20 2008 From: frederic.vandevelde at paradigmo.com (frederic.vandevelde at paradigmo.com) Date: Sun, 16 Nov 2008 10:02:20 +0100 Subject: [csw-maintainers] newpkgs notes, on why packages may be held there In-Reply-To: <20081110113914.G94907@bolthole.com> References: <20081110113914.G94907@bolthole.com> Message-ID: Hi, Stupid question but where is newpkgs located now ? Frederic. On 10 Nov 2008, at 20:39, Philip Brown wrote: > FYI: Becaue I tend to forget, myself, I have now started to keep > notes on why > particular packages are being 'held' in newpkgs. > > I used to keep an old file in my home dir, but it will be > /home/newpkgs/00-README > from now on. > Nice and easy to spot now. > > > and also FYI: I always email people when there are issues with their > packages. There is no additional requirement for people to go read > that > file themselves. This is just so I can delete my old emails safely, > without forgetting why a package is sitting there. Or as a reminder > to YOU, > if you happen to forget the issue with your own package ;-) > > > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers From bonivart at opencsw.org Sun Nov 16 10:05:26 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 16 Nov 2008 10:05:26 +0100 Subject: [csw-maintainers] newpkgs notes, on why packages may be held there In-Reply-To: References: <20081110113914.G94907@bolthole.com> Message-ID: <625385e30811160105n6adc703am7347a4013a5a103a@mail.gmail.com> On Sun, Nov 16, 2008 at 10:02 AM, wrote: > Hi, > > Stupid question but where is newpkgs located now ? Use scp from the build farm to transfer your packages to www.opencsw.org:/home/newpkgs. -- /peter From fred at opencsw.org Sun Nov 16 10:20:40 2008 From: fred at opencsw.org (Frederic Van De Velde) Date: Sun, 16 Nov 2008 10:20:40 +0100 Subject: [csw-maintainers] newpkgs notes, on why packages may be held there In-Reply-To: <625385e30811160105n6adc703am7347a4013a5a103a@mail.gmail.com> References: <20081110113914.G94907@bolthole.com> <625385e30811160105n6adc703am7347a4013a5a103a@mail.gmail.com> Message-ID: <52DB87A1-3B0F-4C11-AE55-C7DE23098914@opencsw.org> Seems my ssh key isn't there: fred at login [login]:/home/fred/staging/build-16.Nov.2008 > scp * www.opencsw.org :/home/newpkgs/ Password: Fred. On 16 Nov 2008, at 10:05, Peter Bonivart wrote: > On Sun, Nov 16, 2008 at 10:02 AM, > wrote: >> Hi, >> >> Stupid question but where is newpkgs located now ? > > Use scp from the build farm to transfer your packages to > www.opencsw.org:/home/newpkgs. > > -- > /peter > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers From pfelecan at opencsw.org Sun Nov 16 10:24:58 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Sun, 16 Nov 2008 10:24:58 +0100 Subject: [csw-maintainers] "contact maintainer" facility doesn't work References: <491F3503.3070200@opencsw.org> Message-ID: Ihsan Dogan writes: > Hello Peter, > > On 11/15/08 18:43, Peter FELECAN wrote: > >> The following link: http://www.opencsw.org/eml.php doesn't work; after >> entering the sender's address and the message, I see: >> >> "SERVER ERROR: Cannot submit form.Please try again later." > > I just fixed that. The problem was, that PHP was not using > /usr/lib/sendmail. Thank you Ihsan. It works now. -- Peter From pfelecan at opencsw.org Sun Nov 16 10:28:12 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Sun, 16 Nov 2008 10:28:12 +0100 Subject: [csw-maintainers] mantis access In-Reply-To: <20081115124808.B40283@bolthole.com> (Philip Brown's message of "Sat\, 15 Nov 2008 12\:48\:08 -0800") References: <20081115124808.B40283@bolthole.com> Message-ID: Philip Brown writes: > On Sat, Nov 15, 2008 at 06:47:56PM +0100, Peter FELECAN wrote: >> I'm trying to access mantis with the old user name/password couple. It >> doesn't work. >> >> Is the user pfelecan still valid/existing? If yes, I would like my >> password reset to a known value. >> >> BTW, who's in charge with the administration of mantis? > > i'd rather not be. but effectly, I am :-} Please add this topic int the Wiki for discussion at IRL --- I think that under the heading "people" should be alright. > i just reset it. course, that wouldht actually HELP you, if email isnt > working. but hopefully, Ihsan's fix has it working again now. It works and I succeeded resetting my Mantis password. Thank you. -- Peter From frederic.vandevelde at paradigmo.com Sun Nov 16 10:00:28 2008 From: frederic.vandevelde at paradigmo.com (frederic.vandevelde at paradigmo.com) Date: Sun, 16 Nov 2008 10:00:28 +0100 Subject: [csw-maintainers] newpkgs notes, on why packages may be held there In-Reply-To: <20081110113914.G94907@bolthole.com> References: <20081110113914.G94907@bolthole.com> Message-ID: Hi, Stupid question but where is newpkgs located now ? Frederic. On 10 Nov 2008, at 20:39, Philip Brown wrote: > FYI: Becaue I tend to forget, myself, I have now started to keep > notes on why > particular packages are being 'held' in newpkgs. > > I used to keep an old file in my home dir, but it will be > /home/newpkgs/00-README > from now on. > Nice and easy to spot now. > > > and also FYI: I always email people when there are issues with their > packages. There is no additional requirement for people to go read > that > file themselves. This is just so I can delete my old emails safely, > without forgetting why a package is sitting there. Or as a reminder > to YOU, > if you happen to forget the issue with your own package ;-) > > > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers From trygvel at opencsw.org Sun Nov 16 12:21:32 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sun, 16 Nov 2008 12:21:32 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> Message-ID: <4920023C.3030701@opencsw.org> Dagobert Michelsen wrote: > Hi Trygve, > > Am 15.11.2008 um 19:42 schrieb Trygve Laugst?l: >> Some comments: >> >> * Can the JDKs be installed under /opt/csw/jdk to reduce the /opt/csw >> clutter. That also more similar to how it is installed under /usr > > Sure. > >> * I like the way Sun does it with their "instances". If my package >> depend on Java 5 or 6 I would like to default the JDK path to >> /opt/csw/jdk/instance/jdk1.5.0. >> >> $ ls -l /usr/jdk /usr/jdk/instances/ >> /usr/jdk: >> total 10 >> drwxr-xr-x 4 root bin 512 Feb 29 2008 instances >> lrwxrwxrwx 1 root other 18 Nov 5 16:30 jdk1.5.0_16 -> >> instances/jdk1.5.0 >> lrwxrwxrwx 1 root other 18 Nov 5 16:43 jdk1.6.0_10 -> >> instances/jdk1.6.0 >> lrwxrwxrwx 1 root other 11 Nov 5 16:43 latest -> >> jdk1.6.0_10 >> drwxr-xr-x 7 root bin 512 Nov 5 16:46 packages >> >> /usr/jdk/instances/: >> total 4 >> drwxr-xr-x 9 root bin 512 Nov 5 16:49 jdk1.5.0 >> drwxr-xr-x 9 root bin 512 Nov 5 16:51 jdk1.6.0 > > But why /usr/jdk/instances/jdkxxx instead of /usr/jdk/jdkxxxx? Dunno, got to ask Sun about that :) > Why is there the symlink? > > And: Should this also be true for JREs?\ IMO yes, but I just tried to download all the 1.4, 1.5 and 1.6 JREs and they don't have pkg installers for any of them. Phil asked if the directory should be "java" and that what what I originally wanted too, but Sun uses /usr/java as a symlink to the latest java, just like /usr/jdk/latest. So this is what I want: /opt/csw/jdk/jdk1.5.0_16 /opt/csw/jdk/instances/jdk1.5.0 -> ../jdk1.5.0_16 /opt/csw/jdk/jdk1.6.0_10 /opt/csw/jdk/instances/jdk1.6.0 -> ../jdk1.5.0_10 And for the JREs: /opt/csw/jre/jdk1.5.0_16 /opt/csw/jre/instances/jdk1.5.0 -> ../jdk1.5.0_16 /opt/csw/jre/jdk1.6.0_10 /opt/csw/jre/instances/jdk1.6.0 -> ../jdk1.5.0_10 I wouldn't mind having a "latest" symlink too, but then we need a way to figure out if a package is "newer" than another (like, if I install CSWjdk6 and then CSWjdk5, I don't want the symlink to be overwritten). -- Trygve From ihsan at opencsw.org Sun Nov 16 12:26:33 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Sun, 16 Nov 2008 12:26:33 +0100 Subject: [csw-maintainers] newpkgs notes, on why packages may be held there In-Reply-To: <52DB87A1-3B0F-4C11-AE55-C7DE23098914@opencsw.org> References: <20081110113914.G94907@bolthole.com> <625385e30811160105n6adc703am7347a4013a5a103a@mail.gmail.com> <52DB87A1-3B0F-4C11-AE55-C7DE23098914@opencsw.org> Message-ID: <49200369.3060700@opencsw.org> Am 16.11.2008 10:20 Uhr, Frederic Van De Velde schrieb: > Seems my ssh key isn't there: > > fred at login [login]:/home/fred/staging/build-16.Nov.2008 > scp * www.opencsw.org > :/home/newpkgs/ > Password: Could you please send me you ssh public key? I'll add it to your account. Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From dam at opencsw.org Sun Nov 16 14:41:23 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 16 Nov 2008 14:41:23 +0100 Subject: [csw-maintainers] Installing new package on the farm In-Reply-To: <491F5FD7.3010107@wbonnet.net> References: <491F5FD7.3010107@wbonnet.net> Message-ID: <4F938ABC-5CB0-4E20-B671-BF8A439BA7F4@opencsw.org> Hi William, Am 16.11.2008 um 00:48 schrieb William Bonnet: > Please Dago could you install some new package on the farm ? The > packages are "proto" from Xorg which are missing from Solaris. I > created > these packages to build the dependencies of Firefox. The following packages have been installed on build8s build8x on the Baltic Online buildfarm: application CSWinputproto inputproto - inputproto application CSWkbproto kbproto - kbproto application CSWrenderproto renderproto - renderproto application CSWxcbproto xcbproto - xcb-proto application CSWxextproto xextproto - xextproto application CSWxproto xproto - xproto There is a conflict on /opt/csw/include/X11/extensions/render.h /opt/csw/include/X11/extensions/renderproto.h between the old CSWrenderdev and the new CSWrenderproto. And a conflict on /opt/csw/include/X11/Xfuncproto.h between the old CSWlibxcomposite and the new CSWxproto. I overwrote the existing files with the new ones. > I will have more installation request in the next hours/days. > Dependencies will be built step by step... Sure. Just let me know. Best regards -- Dago From william at wbonnet.net Sun Nov 16 21:11:42 2008 From: william at wbonnet.net (William Bonnet) Date: Sun, 16 Nov 2008 21:11:42 +0100 Subject: [csw-maintainers] Installing new package on the farm In-Reply-To: <4F938ABC-5CB0-4E20-B671-BF8A439BA7F4@opencsw.org> References: <491F5FD7.3010107@wbonnet.net> <4F938ABC-5CB0-4E20-B671-BF8A439BA7F4@opencsw.org> Message-ID: <49207E7E.9090504@wbonnet.net> Hi Dagobert Thanks > There is a conflict on > /opt/csw/include/X11/extensions/render.h > /opt/csw/include/X11/extensions/renderproto.h > between the old CSWrenderdev and the new CSWrenderproto. > > And a conflict on > /opt/csw/include/X11/Xfuncproto.h > between the old CSWlibxcomposite and the new CSWxproto. > I will update this two packages in the next updates. Conflicts will be solved. > Sure. Just let me know. > I continue the compilation and will ask you more maybe tonight or tomorrow. 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 dam at opencsw.org Sun Nov 16 21:29:07 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 16 Nov 2008 21:29:07 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <4920023C.3030701@opencsw.org> References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> Message-ID: Hi Trygve, Am 16.11.2008 um 12:21 schrieb Trygve Laugst?l: > Dagobert Michelsen wrote: >> Why is there the symlink? >> >> And: Should this also be true for JREs?\ > > IMO yes, but I just tried to download all the 1.4, 1.5 and 1.6 JREs > and > they don't have pkg installers for any of them. > > Phil asked if the directory should be "java" and that what what I > originally wanted too, but Sun uses /usr/java as a symlink to the > latest > java, just like /usr/jdk/latest. > > So this is what I want: > > /opt/csw/jdk/jdk1.5.0_16 > /opt/csw/jdk/instances/jdk1.5.0 -> ../jdk1.5.0_16 > > /opt/csw/jdk/jdk1.6.0_10 > /opt/csw/jdk/instances/jdk1.6.0 -> ../jdk1.5.0_10 > > And for the JREs: > > /opt/csw/jre/jdk1.5.0_16 > /opt/csw/jre/instances/jdk1.5.0 -> ../jdk1.5.0_16 > > /opt/csw/jre/jdk1.6.0_10 > /opt/csw/jre/instances/jdk1.6.0 -> ../jdk1.5.0_10 Sun does it just opposite: root at csw [global]:/usr/jdk > ls -la total 14 drwxr-xr-x 4 root bin 512 Aug 18 18:09 . drwxr-xr-x 39 root sys 1024 Aug 19 11:29 .. drwxr-xr-x 3 root bin 512 Aug 18 17:07 instances lrwxrwxrwx 1 root other 7 Aug 18 17:07 j2sdk1.4.2_16 - > ../j2se lrwxrwxrwx 1 root other 18 Aug 18 18:09 jdk1.5.0_16 -> instances/jdk1.5.0 lrwxrwxrwx 1 root other 11 Aug 18 18:09 latest -> jdk1.5.0_16 drwxr-xr-x 8 root bin 512 Aug 18 17:19 packages The files in instances/ and links in jdk/. > I wouldn't mind having a "latest" symlink too, but then we need a > way to > figure out if a package is "newer" than another (like, if I install > CSWjdk6 and then CSWjdk5, I don't want the symlink to be overwritten). Is it really useful to have a just-the-latest-I-don't-care-Java? I would imagine it would be best to have an apache-like configuration: The Java software maintainers (e. g. Tomcat) chooses the build jre and depends on that. The version is now 1.4.2, should that be jdk14 or jdk142? James, any advice? Best regards -- Dago From phil at bolthole.com Sun Nov 16 22:19:59 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 16 Nov 2008 13:19:59 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: ; from dam@opencsw.org on Sun, Nov 16, 2008 at 09:29:07PM +0100 References: <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> Message-ID: <20081116131959.D99438@bolthole.com> On Sun, Nov 16, 2008 at 09:29:07PM +0100, Dagobert Michelsen wrote: > Is it really useful to have a just-the-latest-I-don't-care-Java? *yes*. Perhaps we could handle it, by having a top level CSWjava, that made symlinks directly /opt/csw/bin/java -> whereever. or, be a shellscript wrapper would probably be better. From james at opencsw.org Mon Nov 17 10:59:25 2008 From: james at opencsw.org (James Lee) Date: Mon, 17 Nov 2008 09:59:25 GMT Subject: [csw-maintainers] Java... again! In-Reply-To: <20081116131959.D99438@bolthole.com> References: <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081116131959.D99438@bolthole.com> Message-ID: <20081117.9592500.3837896452@gyor.oxdrove.co.uk> On 16/11/08, 21:19:59, Philip Brown wrote regarding Re: [csw-maintainers] Java... again!: > > Is it really useful to have a just-the-latest-I-don't-care-Java? > *yes*. > Perhaps we could handle it, by having a top level CSWjava, that made > symlinks directly > /opt/csw/bin/java -> whereever. > or, be a shellscript wrapper would probably be better. An /opt/csw/bin/java link would work. It's possible for java to work out where the jre is from System.getProperty("java.home"); There are a lot of other files in ${JAVA_HOME}/bin that would need to be in /opt/csw/bin too. James. From james at opencsw.org Mon Nov 17 10:59:26 2008 From: james at opencsw.org (James Lee) Date: Mon, 17 Nov 2008 09:59:26 GMT Subject: [csw-maintainers] Java... again! In-Reply-To: References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> Message-ID: <20081117.9592600.991638692@gyor.oxdrove.co.uk> On 16/11/08, 20:29:07, Dagobert Michelsen wrote regarding Re: [csw-maintainers] Java... again!: > > I wouldn't mind having a "latest" symlink too, but then we need a > > way to > > figure out if a package is "newer" than another (like, if I install > > CSWjdk6 and then CSWjdk5, I don't want the symlink to be overwritten). > Is it really useful to have a just-the-latest-I-don't-care-Java? I've yet to find anything that didn't work with the latest - and work better. (Not counting certification issues.) It's possible to build low version compatibility with "-source" and "-target". > I would imagine it would be best to have an apache-like configuration: > The Java software maintainers (e. g. Tomcat) chooses the build jre > and depends on that. In fact Tomcat will need a JDK because it uses tools.jar. If we have packages that depend on both the JRE and JDK we end up with 2 JREs. A JDK packs a JRE so the CSW dependency based delivery model should follow this: JDK requires JRE. We have a fundamental problem with update and Java. As Java is an "environment", dependent packages that run as servers need restarting when java is updated. (This is also affects libraries that are updated and (fail to) support running servers.) James. From phil at bolthole.com Mon Nov 17 18:03:49 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 17 Nov 2008 09:03:49 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081117.9592500.3837896452@gyor.oxdrove.co.uk>; from james@opencsw.org on Mon, Nov 17, 2008 at 09:59:25AM +0000 References: <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081116131959.D99438@bolthole.com> <20081117.9592500.3837896452@gyor.oxdrove.co.uk> Message-ID: <20081117090349.G21898@bolthole.com> On Mon, Nov 17, 2008 at 09:59:25AM +0000, James Lee wrote: > > An /opt/csw/bin/java link would work. It's possible for java to work > out where the jre is from System.getProperty("java.home"); too bad that most things dont USE that. there's lot of badly written java code. you're lucky if it even pays attention to JAVA_HOME. > There are a lot of other files in ${JAVA_HOME}/bin that would need to > be in /opt/csw/bin too. ugh. i hope not "lots". But that would be a reason why it wouuld be better as a wrapper than a symlink. Because a wrapper could set JAVA_HOME appropriately, to where it "really" is. From buysse at umn.edu Mon Nov 17 18:06:20 2008 From: buysse at umn.edu (Joshua Buysse) Date: Mon, 17 Nov 2008 11:06:20 -0600 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081117090349.G21898@bolthole.com> References: <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081116131959.D99438@bolthole.com> <20081117.9592500.3837896452@gyor.oxdrove.co.uk> <20081117090349.G21898@bolthole.com> Message-ID: >> There are a lot of other files in ${JAVA_HOME}/bin that would need to >> be in /opt/csw/bin too. > > ugh. i hope not "lots". > But that would be a reason why it wouuld be better as a wrapper than a > symlink. > Because a wrapper could set JAVA_HOME appropriately, to where it > "really" > is. Would it be worth considering debian's alternatives system? There are other places it could be used as well (multiple versions of perl, python, ruby, etc.) -- Joshua Buysse, System Engineer University of Minnesota, College of Liberal Arts "Daleks do not accept apologies! EXTERMINATE!" -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL: From phil at bolthole.com Mon Nov 17 18:15:56 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 17 Nov 2008 09:15:56 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: ; from buysse@umn.edu on Mon, Nov 17, 2008 at 11:06:20AM -0600 References: <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081116131959.D99438@bolthole.com> <20081117.9592500.3837896452@gyor.oxdrove.co.uk> <20081117090349.G21898@bolthole.com> Message-ID: <20081117091556.J21898@bolthole.com> On Mon, Nov 17, 2008 at 11:06:20AM -0600, Joshua Buysse wrote: > Would it be worth considering debian's alternatives system? There are > other places it could be used as well (multiple versions of perl, > python, ruby, etc.) > it might be. My personal philosophy when comparing things to "how debian does it", is to write up a top level abstract of "what it does", [being as specific as possible, while explicitly NOT including implementation details] Then consider whether we need/want it Then, IF the answer is yes, consider what implementations might be like. From phil at bolthole.com Mon Nov 17 18:37:02 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 17 Nov 2008 09:37:02 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <4920023C.3030701@opencsw.org>; from trygvel@opencsw.org on Sun, Nov 16, 2008 at 12:21:32PM +0100 References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> Message-ID: <20081117093702.Q21898@bolthole.com> On Sun, Nov 16, 2008 at 12:21:32PM +0100, Trygve Laugst?l wrote: > Phil asked if the directory should be "java" and that what what I > originally wanted too, but Sun uses /usr/java as a symlink to the latest > java, just like /usr/jdk/latest. > > So this is what I want: > > /opt/csw/jdk/jdk1.5.0_16 > /opt/csw/jdk/instances/jdk1.5.0 -> ../jdk1.5.0_16 > > /opt/csw/jdk/jdk1.6.0_10 > /opt/csw/jdk/instances/jdk1.6.0 -> ../jdk1.5.0_10 Hmm. I dont think it is nice to "burn" two top-level directories, one for jdk and one for kre. Why dont you like having a combined directory, /opt/csw/java/1.5.0_16 that has both the jre and jdk of that version under it? From buysse at umn.edu Mon Nov 17 18:59:02 2008 From: buysse at umn.edu (Joshua Buysse) Date: Mon, 17 Nov 2008 11:59:02 -0600 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081117093702.Q21898@bolthole.com> References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> Message-ID: On Nov 17, 2008, at 11:37 AM, Philip Brown wrote: > On Sun, Nov 16, 2008 at 12:21:32PM +0100, Trygve Laugst?l wrote: >> Phil asked if the directory should be "java" and that what what I >> originally wanted too, but Sun uses /usr/java as a symlink to the >> latest >> java, just like /usr/jdk/latest. >> >> So this is what I want: >> >> /opt/csw/jdk/jdk1.5.0_16 >> /opt/csw/jdk/instances/jdk1.5.0 -> ../jdk1.5.0_16 >> >> /opt/csw/jdk/jdk1.6.0_10 >> /opt/csw/jdk/instances/jdk1.6.0 -> ../jdk1.5.0_10 > > Hmm. I dont think it is nice to "burn" two top-level directories, > one for > jdk and one for kre. > > Why dont you like having a combined directory, > > /opt/csw/java/1.5.0_16 > > that has both the jre and jdk of that version under it? Compromise: /opt/csw/java/bin/java -> ../instances/jre/bin/java /opt/csw/java/bin/javac -> ../instances/jdk/bin/javac /opt/csw/java/bin/keytool -> ../instances/jdk/bin/keytool ... /opt/csw/java/instances/jdk-1.5.0_16 /opt/csw/java/instances/jdk -> jdk-1.5.0_16 /opt/csw/java/instances/jre -> jdk-1.5.0_16 ? -- Joshua Buysse, System Engineer University of Minnesota, College of Liberal Arts We must not confuse dissent with disloyalty. -Edward R. Murrow -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL: From phil at bolthole.com Mon Nov 17 19:09:28 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 17 Nov 2008 10:09:28 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: ; from buysse@umn.edu on Mon, Nov 17, 2008 at 11:59:02AM -0600 References: <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> Message-ID: <20081117100928.U21898@bolthole.com> On Mon, Nov 17, 2008 at 11:59:02AM -0600, Joshua Buysse wrote: > > On Nov 17, 2008, at 11:37 AM, Philip Brown wrote: > > Why dont you like having a combined directory, > > > > /opt/csw/java/1.5.0_16 > > > > that has both the jre and jdk of that version under it? > > > Compromise: > > /opt/csw/java/bin/java -> ../instances/jre/bin/java > /opt/csw/java/bin/javac -> ../instances/jdk/bin/javac > /opt/csw/java/bin/keytool -> ../instances/jdk/bin/keytool > ... > /opt/csw/java/instances/jdk-1.5.0_16 > /opt/csw/java/instances/jdk -> jdk-1.5.0_16 > /opt/csw/java/instances/jre -> jdk-1.5.0_16 > > ? Hmm. interesting. I'll ask again , though, because I'm not understanding: why dont you like the top level directory as "java"? What are you envisioning being in /opt/csw/java, besides the single directory "instances"? (I'll mention that currently, we already have documented, and in use, a standard for jar files, to live in /opt/csw/share/java http://www.opencsw.org/standards/layout mentions this) From buysse at cla.umn.edu Mon Nov 17 19:16:03 2008 From: buysse at cla.umn.edu (Joshua Buysse) Date: Mon, 17 Nov 2008 12:16:03 -0600 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081117100928.U21898@bolthole.com> References: <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <20081117100928.U21898@bolthole.com> Message-ID: <35B1F1AD-0544-4B87-B2FE-414470AEE7FD@cla.umn.edu> On Nov 17, 2008, at 12:09 PM, Philip Brown wrote: >> /opt/csw/java/bin/java -> ../instances/jre/bin/java >> /opt/csw/java/bin/javac -> ../instances/jdk/bin/javac >> /opt/csw/java/bin/keytool -> ../instances/jdk/bin/keytool >> ... >> /opt/csw/java/instances/jdk-1.5.0_16 >> /opt/csw/java/instances/jdk -> jdk-1.5.0_16 >> /opt/csw/java/instances/jre -> jdk-1.5.0_16 >> >> ? > > Hmm. interesting. I'll ask again , though, because I'm not > understanding: > why dont you like the top level directory as "java"? > What are you envisioning being in /opt/csw/java, besides the single > directory "instances"? Directories for bin, lib, man, and include that point through to the "active" instance (jdk/jre symlinks in instances). That way, a currently selected java version can always be found if PATH includes / opt/csw/java/bin, and MANPATH includes /opt/csw/java/man (or /opt/csw/ java/share/man, but that's not how Sun packages it). > (I'll mention that currently, we already have documented, and in use, > a standard for jar files, to live in /opt/csw/share/java > > http://www.opencsw.org/standards/layout > mentions this) > > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers -- Joshua Buysse, System Engineer University of Minnesota, College of Liberal Arts "I was such a geek that if I could go back in time, I would kick my own ass." -- Wil Wheaton -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL: From phil at bolthole.com Mon Nov 17 19:23:45 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 17 Nov 2008 10:23:45 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <35B1F1AD-0544-4B87-B2FE-414470AEE7FD@cla.umn.edu>; from buysse@cla.umn.edu on Mon, Nov 17, 2008 at 12:16:03PM -0600 References: <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <20081117100928.U21898@bolthole.com> <35B1F1AD-0544-4B87-B2FE-414470AEE7FD@cla.umn.edu> Message-ID: <20081117102345.V21898@bolthole.com> On Mon, Nov 17, 2008 at 12:16:03PM -0600, Joshua Buysse wrote: > > What are you envisioning being in /opt/csw/java, besides the single > > directory "instances"? > > Directories for bin, lib, man, and include that point through to the > "active" instance (jdk/jre symlinks in instances). That way, a > currently selected java version can always be found if PATH includes / > opt/csw/java/bin, and MANPATH includes /opt/csw/java/man (or /opt/csw/ > java/share/man, but that's not how Sun packages it). What about /opt/csw/java/bin, lib, man, being symlinks to ./{VERSION}/bin, instead of ./instances/{VERSION}/bin ? I personally think that is a little cleaner; shorter paths are usually nicer, in my opinion :-) From buysse at umn.edu Mon Nov 17 19:45:13 2008 From: buysse at umn.edu (Joshua Buysse) Date: Mon, 17 Nov 2008 12:45:13 -0600 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081117102345.V21898@bolthole.com> References: <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <20081117100928.U21898@bolthole.com> <35B1F1AD-0544-4B87-B2FE-414470AEE7FD@cla.umn.edu> <20081117102345.V21898@bolthole.com> Message-ID: On Nov 17, 2008, at 12:23 PM, Philip Brown wrote: > On Mon, Nov 17, 2008 at 12:16:03PM -0600, Joshua Buysse wrote: >>> What are you envisioning being in /opt/csw/java, besides the single >>> directory "instances"? >> >> Directories for bin, lib, man, and include that point through to the >> "active" instance (jdk/jre symlinks in instances). That way, a >> currently selected java version can always be found if PATH >> includes / >> opt/csw/java/bin, and MANPATH includes /opt/csw/java/man (or /opt/ >> csw/ >> java/share/man, but that's not how Sun packages it). > > What about /opt/csw/java/bin, lib, man, being symlinks to ./ > {VERSION}/bin, > instead of ./instances/{VERSION}/bin ? > > I personally think that is a little cleaner; shorter paths are usually > nicer, in my opinion :-) No real difference, as long as a current/active symlink is used -- the key is that only one symlink needs to be changed to switch the default version of java. (ie, in /opt/csw/java, current -> jdk-1.5.0_16, or jdk -> jdk-1.4.2_xx, etc.) The java plugin for firefox should probably symlink to /opt/csw/java/ current/... as well. -- Joshua Buysse, System Engineer University of Minnesota, College of Liberal Arts We must not confuse dissent with disloyalty. -Edward R. Murrow -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL: From phil at bolthole.com Mon Nov 17 19:52:15 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 17 Nov 2008 10:52:15 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081117102345.V21898@bolthole.com>; from phil@bolthole.com on Mon, Nov 17, 2008 at 10:23:45AM -0800 References: <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <20081117100928.U21898@bolthole.com> <35B1F1AD-0544-4B87-B2FE-414470AEE7FD@cla.umn.edu> <20081117102345.V21898@bolthole.com> Message-ID: <20081117105215.W21898@bolthole.com> On Mon, Nov 17, 2008 at 10:23:45AM -0800, Philip Brown wrote: > > What about /opt/csw/java/bin, lib, man, being symlinks to ./{VERSION}/bin, > instead of ./instances/{VERSION}/bin ? or, if we wanted to be completely consistent, by a user setting JAVA_HOME, PATH, etc to /opt/csw/java/someversion perhaps have /opt/csw/java/default/bin -> ../{VERSION}/bin and so forth, so that /opt/csw/java only contains version subdirectories directly or having /opt/csw/java/default itself be a symlink to a specific version dir. (That's actually what they do at USC a lot. Seems to be appropriate in this case, maybe ) From phil at bolthole.com Mon Nov 17 19:54:18 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 17 Nov 2008 10:54:18 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: ; from buysse@umn.edu on Mon, Nov 17, 2008 at 12:45:13PM -0600 References: <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <20081117100928.U21898@bolthole.com> <35B1F1AD-0544-4B87-B2FE-414470AEE7FD@cla.umn.edu> <20081117102345.V21898@bolthole.com> Message-ID: <20081117105418.X21898@bolthole.com> On Mon, Nov 17, 2008 at 12:45:13PM -0600, Joshua Buysse wrote: > No real difference, as long as a current/active symlink is used -- the > key is that only one symlink needs to be changed to switch the default > version of java. (ie, in /opt/csw/java, current -> jdk-1.5.0_16, or > jdk -> jdk-1.4.2_xx, etc.) > > The java plugin for firefox should probably symlink to /opt/csw/java/ > current/... as well. so then we get to quibble about whether that symlink should be called "current", "default", "stable", "latest", ...... :-) I think that "default" seems to most closely fit the purpose of the thing. From trygvel at opencsw.org Mon Nov 17 19:44:45 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Mon, 17 Nov 2008 19:44:45 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081117093702.Q21898@bolthole.com> References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> Message-ID: <4921BB9D.4030403@opencsw.org> Philip Brown wrote: > On Sun, Nov 16, 2008 at 12:21:32PM +0100, Trygve Laugst?l wrote: >> Phil asked if the directory should be "java" and that what what I >> originally wanted too, but Sun uses /usr/java as a symlink to the latest >> java, just like /usr/jdk/latest. >> >> So this is what I want: >> >> /opt/csw/jdk/jdk1.5.0_16 >> /opt/csw/jdk/instances/jdk1.5.0 -> ../jdk1.5.0_16 >> >> /opt/csw/jdk/jdk1.6.0_10 >> /opt/csw/jdk/instances/jdk1.6.0 -> ../jdk1.5.0_10 > > Hmm. I dont think it is nice to "burn" two top-level directories, one for > jdk and one for kre. > > Why dont you like having a combined directory, > > /opt/csw/java/1.5.0_16 > > that has both the jre and jdk of that version under it? Because Sun uses /usr/java as a complete JDK isntallation (or was it JRE?..) -- Trygve From phil at bolthole.com Mon Nov 17 20:17:30 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 17 Nov 2008 11:17:30 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <4921BB9D.4030403@opencsw.org>; from trygvel@opencsw.org on Mon, Nov 17, 2008 at 07:44:45PM +0100 References: <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> Message-ID: <20081117111730.B21898@bolthole.com> On Mon, Nov 17, 2008 at 07:44:45PM +0100, Trygve Laugst?l wrote: > Philip Brown wrote: > > Why dont you like having a combined directory, > > > > /opt/csw/java/1.5.0_16 > > > > that has both the jre and jdk of that version under it? > > Because Sun uses /usr/java as a complete JDK isntallation (or was it JRE?..) Hmm... I'm not sure what you are disliking here. Are you going with the principle that "anything with java as the last component of its name, should be a full runtime", usable as JAVA_HOME? Just becuase sun does it that way? Do you not think that JAVA_HOME=/opt/csw/java/default would be just as appropriate? And, given that sun seems to give users a choice of JAVA_HOME=/usr/java JAVA_HOME=/usr/js2e JAVA_HOME=/usr/jdk/j2sdk1.4.2.16 JAVA_HOME=/usr/jdk/jdk1.5.0_16 JAVA_HOME=/usr/jdk/instances/jdk1.5.0 JAVA_HOME=/usr/jdk/latest # oh look!! looks like /opt/csw/java/default :) I think that in this case, we should toss out what sun does, and start with our own CONSISTENT naming, that can stay consistent pretty much from now until forever :-) (JAVA_HOME=/opt/csw/java/{pick-your-version}, where version can also be "default") From trygvel at opencsw.org Mon Nov 17 20:26:25 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Mon, 17 Nov 2008 20:26:25 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081117111730.B21898@bolthole.com> References: <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> Message-ID: <4921C561.5030406@opencsw.org> Philip Brown wrote: > On Mon, Nov 17, 2008 at 07:44:45PM +0100, Trygve Laugst?l wrote: >> Philip Brown wrote: >>> Why dont you like having a combined directory, >>> >>> /opt/csw/java/1.5.0_16 >>> >>> that has both the jre and jdk of that version under it? >> Because Sun uses /usr/java as a complete JDK isntallation (or was it JRE?..) > > Hmm... I'm not sure what you are disliking here. > Are you going with the principle that "anything with java as the last > component of its name, should be a full runtime", usable as JAVA_HOME? > Just becuase sun does it that way? > > Do you not think that JAVA_HOME=/opt/csw/java/default > would be just as appropriate? > > And, given that sun seems to give users a choice of > JAVA_HOME=/usr/java > JAVA_HOME=/usr/js2e > JAVA_HOME=/usr/jdk/j2sdk1.4.2.16 > JAVA_HOME=/usr/jdk/jdk1.5.0_16 > JAVA_HOME=/usr/jdk/instances/jdk1.5.0 > JAVA_HOME=/usr/jdk/latest # oh look!! looks like /opt/csw/java/default :) > > I think that in this case, we should toss out what sun does, and start with > our own CONSISTENT naming, that can stay consistent pretty much from now > until forever :-) > > (JAVA_HOME=/opt/csw/java/{pick-your-version}, where version can > also be "default") I'm all for consistency and my point was really "just because sun does it". By not inventing *yet* another way to find the Java runtime we're saving some brain cells. As long as it is doable. /opt/csw is already a pretty decent mess if you ask mere. Stuff is no where near self consistent or similar to /etc, either Solaris or other distros. -- Trygve From phil at bolthole.com Mon Nov 17 20:46:08 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 17 Nov 2008 11:46:08 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <4921C561.5030406@opencsw.org>; from trygvel@opencsw.org on Mon, Nov 17, 2008 at 08:26:25PM +0100 References: <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> Message-ID: <20081117114608.C21898@bolthole.com> On Mon, Nov 17, 2008 at 08:26:25PM +0100, Trygve Laugst?l wrote: > Philip Brown wrote: > > I think that in this case, we should toss out what sun does, and start with > > our own CONSISTENT naming, that can stay consistent pretty much from now > > until forever :-) > > > > (JAVA_HOME=/opt/csw/java/{pick-your-version}, where version can > > also be "default") > > I'm all for consistency and my point was really "just because sun does > it". By not inventing *yet* another way to find the Java runtime we're > saving some brain cells. ok... I think you're saying that you're ok with the above "consistent" strategy, so I think I am counting 3 "votes" in favour of the above, and none opposed so far. > /opt/csw is already a > pretty decent mess if you ask mere. Stuff is no where near self > consistent or similar to /etc, either Solaris or other distros. I do agree that in certain areas, our packages are inconsistent. and I think that we should all be 'encouraged',and encourage one another, to clean things up. I for one, will be "cleaning up" my very old and ugly apache1 package, to finally adhere to the proper standards, of "writable stuff belongs in /var/opt/csw/pkgname, NOT /opt/csw/var" and so on. But that will take a large amount of work, so it's waiting for next weekend :-/ From dam at opencsw.org Mon Nov 17 21:15:27 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 17 Nov 2008 21:15:27 +0100 Subject: [csw-maintainers] Maintainer buglisting available Message-ID: <682C3E40-526A-4D19-9F36-D1DD00AB47C9@opencsw.org> Fellow maintainers, as you all know there is the Mantis bugtracking system at However, some research showed that there is quite an amount of reported bugs. Some new, some old, some already fixed but not acknowledged or closed. I can say for myself that tracking bugs in Mantis was not that straightforward as it could be. To make open bugs more prominent I added a link to the bottom of each maintainer page which shows all bugs for packages the maintainer is responsible for needing attention. So please see what you have missed in the past ;-) Additionally, there are three packages orphaned which are not associated to a maintainer: These are * dsniff * netsnmp * ntop It would be very nice if a maintainer would be willing to adopt them as those packages are all quite prominent. Best regards -- Dago From phil at bolthole.com Mon Nov 17 22:43:20 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 17 Nov 2008 13:43:20 -0800 Subject: [csw-maintainers] bio pages Message-ID: <20081117134320.I21898@bolthole.com> FYI: I bumped over the php code that handles the "bio" inclusion, for your maintainer page. It has not been working since the move, up until now. So, http://www.opencsw.org/maintainers/yourlogin will once again include $HOME/public_html/bio.html if you create it and make it publically readable. From dam at opencsw.org Mon Nov 17 22:45:25 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 17 Nov 2008 22:45:25 +0100 Subject: [csw-maintainers] Experimental Atom Feed for testing/ Message-ID: Fellow maintainers, tonight I hacked a rudimentary atom feed for testing/. Please subscribe to Maybe someone has a link for me on how to integrate this to the testing.html webpage. Feed-back :-) as always welcome. Best regards -- Dago From dam at opencsw.org Mon Nov 17 22:56:40 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 17 Nov 2008 22:56:40 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081117114608.C21898@bolthole.com> References: <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> Message-ID: <5F994B04-687B-4AC3-91AE-DAAE62F4716B@opencsw.org> Hi, Am 17.11.2008 um 20:46 schrieb Philip Brown: > ok... I think you're saying that you're ok with the above "consistent" > strategy, so I think I am counting 3 "votes" in favour of the above, > and > none opposed so far. Is this an agreeable solution or is there still need for discussion? If everyone on this list can live with this I'll repackage after this spec. But not before as it takes forever to pack 100+ MB :-P What about JDK/JRE separation? JDK includes a JRE but essentially I don't want to extract the JRE from there as this is mainly asking for trouble. Should we just distribute the JDK then? Best regards -- Dago From phil at bolthole.com Tue Nov 18 02:24:08 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 17 Nov 2008 17:24:08 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <5F994B04-687B-4AC3-91AE-DAAE62F4716B@opencsw.org>; from dam@opencsw.org on Mon, Nov 17, 2008 at 10:56:40PM +0100 References: <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> <5F994B04-687B-4AC3-91AE-DAAE62F4716B@opencsw.org> Message-ID: <20081117172408.D39788@bolthole.com> On Mon, Nov 17, 2008 at 10:56:40PM +0100, Dagobert Michelsen wrote: > ... > What about JDK/JRE separation? JDK includes a JRE but > essentially I don't want to extract the JRE from there > as this is mainly asking for trouble. Should we just > distribute the JDK then? ?!?!?!? Personally, I think we serve our users well, by splitting out jre. I would guess that a vast majority of people who "need java", actualy just specifically need the JRE. Unless the jdk addds only a trivial amount of extra bytes (and I'm pretty sure it's not trivial! :-) seems like the best thing to do is split em. I dont see what this "trouble" would be that you reference. Perhaps you could explain further. From trygvel at opencsw.org Tue Nov 18 07:51:57 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Tue, 18 Nov 2008 07:51:57 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081117172408.D39788@bolthole.com> References: <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> <5F994B04-687B-4AC3-91AE-DAAE62F4716B@opencsw.org> <20081117172408.D39788@bolthole.com> Message-ID: <4922660D.9070203@opencsw.org> Philip Brown wrote: > On Mon, Nov 17, 2008 at 10:56:40PM +0100, Dagobert Michelsen wrote: >> ... >> What about JDK/JRE separation? JDK includes a JRE but >> essentially I don't want to extract the JRE from there >> as this is mainly asking for trouble. Should we just >> distribute the JDK then? > > ?!?!?!? > > Personally, I think we serve our users well, by splitting out jre. > > I would guess that a vast majority of people who "need java", actualy > just specifically need the JRE. > > > Unless the jdk addds only a trivial amount of extra bytes (and I'm pretty > sure it's not trivial! :-) seems like the best thing to do is split em. > I dont see what this "trouble" would be that you reference. Perhaps you > could explain further. I agree with Phil here, we need two packages. I would never use JDK or JRE package that has been modified by upstream packages, just see the just that Debian tries deliver with their "java" packages. -- Trygve From trygvel at opencsw.org Tue Nov 18 07:54:09 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Tue, 18 Nov 2008 07:54:09 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081117114608.C21898@bolthole.com> References: <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> Message-ID: <49226691.1040706@opencsw.org> Philip Brown wrote: > On Mon, Nov 17, 2008 at 08:26:25PM +0100, Trygve Laugst?l wrote: >> Philip Brown wrote: >>> I think that in this case, we should toss out what sun does, and start with >>> our own CONSISTENT naming, that can stay consistent pretty much from now >>> until forever :-) >>> >>> (JAVA_HOME=/opt/csw/java/{pick-your-version}, where version can >>> also be "default") >> I'm all for consistency and my point was really "just because sun does >> it". By not inventing *yet* another way to find the Java runtime we're >> saving some brain cells. > > ok... I think you're saying that you're ok with the above "consistent" > strategy, so I think I am counting 3 "votes" in favour of the above, and > none opposed so far. I would vote +1 for /opt/csw/jdk and /opt/csw/jdk, because that is nearer to what Sun does, but I won't try to veto a hiearchy with more consistency under /opt/csw/java :) >> /opt/csw is already a >> pretty decent mess if you ask mere. Stuff is no where near self >> consistent or similar to /etc, either Solaris or other distros. > > I do agree that in certain areas, our packages are inconsistent. and I > think that we should all be 'encouraged',and encourage one another, to > clean things up. > > I for one, will be "cleaning up" my very old and ugly apache1 package, to > finally adhere to the proper standards, of > "writable stuff belongs in /var/opt/csw/pkgname, NOT /opt/csw/var" > and so on. > > > But that will take a large amount of work, so it's waiting for next weekend > :-/ Great! How about configuration files? Are they going under /etc/opt/csw to? -- Trygve From trygvel at opencsw.org Tue Nov 18 08:01:07 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Tue, 18 Nov 2008 08:01:07 +0100 Subject: [csw-maintainers] Experimental Atom Feed for testing/ In-Reply-To: References: Message-ID: <49226833.8030606@opencsw.org> Dagobert Michelsen wrote: > Fellow maintainers, > > tonight I hacked a rudimentary atom feed for testing/. Woho! > Please subscribe to > The feed work just fine in my Atom reader (Bloglines.com) and in Opera. Not sure why you put feed:// instead of http:// in the link, Atom feeds tent to be transported over HTTP. > Maybe someone has a link for me on how to integrate this to > the testing.html webpage. For the HTML integration you can follow nearly any blog, but [1] one had lots of examples in it's tags: So I think if you put this in it should work: billion. Yet at the end of September, Sun had $3.1 billion in cash on > hand. The gap indicates extreme pessimism about the company's > prospects." Did Sun know this in advance? Without the 1:4 join, the price of a share would be < 1 $ J?rg -- EMail:joerg at schily.isdn.cs.tu-berlin.de (home) J?rg Schilling D-13353 Berlin js at cs.tu-berlin.de (uni) schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily From phil at bolthole.com Tue Nov 18 15:50:14 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 18 Nov 2008 06:50:14 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <49226691.1040706@opencsw.org>; from trygvel@opencsw.org on Tue, Nov 18, 2008 at 07:54:09AM +0100 References: <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> <49226691.1040706@opencsw.org> Message-ID: <20081118065014.B46481@bolthole.com> On Tue, Nov 18, 2008 at 07:54:09AM +0100, Trygve Laugst?l wrote: > > I for one, will be "cleaning up" my very old and ugly apache1 package, to > > finally adhere to the proper standards, of > > "writable stuff belongs in /var/opt/csw/pkgname, NOT /opt/csw/var" > > and so on. > > > > > > But that will take a large amount of work, so it's waiting for next weekend > > :-/ > > Great! > > How about configuration files? Are they going under /etc/opt/csw to? Yeah. and so on, and so forth. hence the "a lot of work" :-/ From trygvel at opencsw.org Tue Nov 18 22:36:39 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Tue, 18 Nov 2008 22:36:39 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081118065014.B46481@bolthole.com> References: <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> <49226691.1040706@opencsw.org> <20081118065014.B46481@bolthole.com> Message-ID: <49233567.7030101@opencsw.org> Philip Brown wrote: > On Tue, Nov 18, 2008 at 07:54:09AM +0100, Trygve Laugst?l wrote: >>> I for one, will be "cleaning up" my very old and ugly apache1 package, to >>> finally adhere to the proper standards, of >>> "writable stuff belongs in /var/opt/csw/pkgname, NOT /opt/csw/var" >>> and so on. >>> >>> >>> But that will take a large amount of work, so it's waiting for next weekend >>> :-/ >> Great! >> >> How about configuration files? Are they going under /etc/opt/csw to? > > Yeah. and so on, and so forth. hence the "a lot of work" :-/ :) Is that something that is a part of the standards and something that your script is checking for? -- Trygve From phil at bolthole.com Tue Nov 18 23:42:16 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 18 Nov 2008 14:42:16 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <49233567.7030101@opencsw.org>; from trygvel@opencsw.org on Tue, Nov 18, 2008 at 10:36:39PM +0100 References: <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> <49226691.1040706@opencsw.org> <20081118065014.B46481@bolthole.com> <49233567.7030101@opencsw.org> Message-ID: <20081118144216.A72261@bolthole.com> On Tue, Nov 18, 2008 at 10:36:39PM +0100, Trygve Laugst?l wrote: > > Is that something that is a part of the standards and something that > your script is checking for? yes it is part of the standards. No, it isnt something you can really progamatically check for. From trygvel at opencsw.org Wed Nov 19 01:29:39 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Wed, 19 Nov 2008 01:29:39 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081118144216.A72261@bolthole.com> References: <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> <49226691.1040706@opencsw.org> <20081118065014.B46481@bolthole.com> <49233567.7030101@opencsw.org> <20081118144216.A72261@bolthole.com> Message-ID: <49235DF3.3020601@opencsw.org> Philip Brown wrote: > On Tue, Nov 18, 2008 at 10:36:39PM +0100, Trygve Laugst?l wrote: >> Is that something that is a part of the standards and something that >> your script is checking for? > > yes it is part of the standards. No, it isnt something you can really > progamatically check for. I was just wondering, since just about every CSW package that I've installed has config files under /opt/csw/etc. Wouldn't it be possible to just check the prototype for files under /opt/csw/etc? -- Trygve From phil at bolthole.com Wed Nov 19 02:31:01 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 18 Nov 2008 17:31:01 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <49235DF3.3020601@opencsw.org>; from trygvel@opencsw.org on Wed, Nov 19, 2008 at 01:29:39AM +0100 References: <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> <49226691.1040706@opencsw.org> <20081118065014.B46481@bolthole.com> <49233567.7030101@opencsw.org> <20081118144216.A72261@bolthole.com> <49235DF3.3020601@opencsw.org> Message-ID: <20081118173101.A14182@bolthole.com> On Wed, Nov 19, 2008 at 01:29:39AM +0100, Trygve Laugst?l wrote: > > yes it is part of the standards. No, it isnt something you can really > > progamatically check for. > > I was just wondering, since just about every CSW package that I've > installed has config files under /opt/csw/etc. > > Wouldn't it be possible to just check the prototype for files under > /opt/csw/etc? well, i actually plan to put in a check for /opt/csw/var. since that should pretty much never exist any more. However, /opt/csw/etc is different. Some programs, SHOULD have global configs in /opt/csw/etc. Some should have local configs in /etc/opt/csw It is impossible for an automated check to "know" which type of program it is checking :-} From jgoerzen at opencsw.org Wed Nov 19 07:16:57 2008 From: jgoerzen at opencsw.org (Jake Goerzen) Date: Tue, 18 Nov 2008 22:16:57 -0800 Subject: [csw-maintainers] now in /testing: freeciv 2.1.6 Message-ID: <315c02ae0811182216w11ca1004r92f7b0f43d207c3d@mail.gmail.com> updated packages of freeciv version 2.1.6 are available in /testing http://buildfarm.opencsw.org/testing/freeciv-2.1.6,REV=2008.11.19-SunOS5.8-i386-CSW.pkg.gz http://buildfarm.opencsw.org/testing/freeciv-2.1.6,REV=2008.11.19-SunOS5.8-sparc-CSW.pkg.gz -------------- next part -------------- An HTML attachment was scrubbed... URL: From bonivart at opencsw.org Wed Nov 19 22:12:17 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Wed, 19 Nov 2008 22:12:17 +0100 Subject: [csw-maintainers] /testing - BIND 9.4.2-P2, MailScanner 4.71, SpamAssassin 3.2.5, TNEF 1.4.5 Message-ID: <625385e30811191312j6f385203mb1d3ea95d72f1c38@mail.gmail.com> I have a few updated packages in testing and would like some help if possible. Bind is a small update from the very important one this summer but it could still be very interesting since the security fix is now a more permanent one that should consume less resources. Many of us noticed that Bind used more resources to do the same job so it will be interesting to see if that is now better again. http://mirror.opencsw.org/testing/bind-9.4.2,REV=2008.11.19_rev=P2-SunOS5.8-i386-CSW.pkg.gz http://mirror.opencsw.org/testing/bind-9.4.2,REV=2008.11.19_rev=P2-SunOS5.8-sparc-CSW.pkg.gz The second one is MailScanner, 4.72 has just been released but only supports ClamAV 0.94 which we don't yet have here so I'm going to release 4.71 instead and keep working on ClamAV. I have included SMF support in the package now. http://mirror.opencsw.org/testing/mailscanner-4.71.10.1,REV=2008.11.18-SunOS5.8-all-CSW.pkg.gz This one may interest many of you. I took over the package from Alex Moore and didn't find much documentation but I have tried to package it exactly as he did so not to cause any problems. The only intended change is that "local state dir" (where sa-update downloads rules) is changed from /opt/csw/var to /var/opt/csw/spamassassin. http://mirror.opencsw.org/testing/spamassassin-3.2.5,REV=2008.11.19-SunOS5.8-i386-CSW.pkg.gz http://mirror.opencsw.org/testing/spamassassin-3.2.5,REV=2008.11.19-SunOS5.8-sparc-CSW.pkg.gz Last one is a small utility to decode Microsoft's intrusion into the mail world. They couldn't use HTML to format mail like everyone else but had to invent their own format and happily sends it over the internet even though only Outlook (Lookout?) can parse it. When you get a winmail.dat file you know you have been TNEF:ed. :-) This utility can decode that file and is used by e.g. MailScanner to automatically replace TNEF in a transparent fashion. http://mirror.opencsw.org/testing/tnef-1.4.5,REV=2008.11.18-SunOS5.8-i386-CSW.pkg.gz http://mirror.opencsw.org/testing/tnef-1.4.5,REV=2008.11.18-SunOS5.8-sparc-CSW.pkg.gz -- /peter From jgoerzen at opencsw.org Thu Nov 20 02:29:59 2008 From: jgoerzen at opencsw.org (Jake Goerzen) Date: Wed, 19 Nov 2008 17:29:59 -0800 Subject: [csw-maintainers] updated freeciv 2.1.6 pkgs in /testing Message-ID: <315c02ae0811191729p11a7b9bfw7c5bef8501b84b19@mail.gmail.com> I have built new freeciv 2.1.6 packages and placed them in /testing: http://buildfarm.opencsw.org/testing/freeciv-2.1.6,REV=2008.11.20-SunOS5.8-i386-CSW.pkg.gz http://buildfarm.opencsw.org/testing/freeciv-2.1.6,REV=2008.11.20-SunOS5.8-sparc-CSW.pkg.gz I don't have any x86 host to test the x86 pkg but the sparc pkg works great. Please someone test the x86 pkg and let me know. Thanks, Jake -------------- next part -------------- An HTML attachment was scrubbed... URL: From fred at opencsw.org Thu Nov 20 12:52:24 2008 From: fred at opencsw.org (Frederic Van De Velde) Date: Thu, 20 Nov 2008 12:52:24 +0100 Subject: [csw-maintainers] where is testing ? Message-ID: How do I put files in buildfarm.opencsw.org/testing ? Fred. From bonivart at opencsw.org Thu Nov 20 13:35:10 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Thu, 20 Nov 2008 13:35:10 +0100 Subject: [csw-maintainers] where is testing ? In-Reply-To: References: Message-ID: <625385e30811200435l3916ca1cr37224515e32538a7@mail.gmail.com> On Thu, Nov 20, 2008 at 12:52 PM, Frederic Van De Velde wrote: > > How do I put files in buildfarm.opencsw.org/testing ? Copy them to /home/testing. -- /peter From dam at opencsw.org Thu Nov 20 13:36:26 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 20 Nov 2008 13:36:26 +0100 Subject: [csw-maintainers] where is testing ? In-Reply-To: References: Message-ID: <40266351-3F85-438D-B569-FDA4C07C95C6@opencsw.org> Hi Frederic, Am 20.11.2008 um 12:52 schrieb Frederic Van De Velde: > How do I put files in buildfarm.opencsw.org/testing ? You copy them to /home/testing/ :-) Don't get yourself distracted by not seeing it as it is wildcard-automounted. Best regards -- Dago From william at wbonnet.net Thu Nov 20 13:53:52 2008 From: william at wbonnet.net (William Bonnet) Date: Thu, 20 Nov 2008 13:53:52 +0100 Subject: [csw-maintainers] where is testing ? In-Reply-To: <40266351-3F85-438D-B569-FDA4C07C95C6@opencsw.org> References: <40266351-3F85-438D-B569-FDA4C07C95C6@opencsw.org> Message-ID: <49255DE0.3010401@wbonnet.net> Dagobert Michelsen a ?crit : > Hi Frederic, > > Am 20.11.2008 um 12:52 schrieb Frederic Van De Velde: > >> How do I put files in buildfarm.opencsw.org/testing ? >> > > You copy them to /home/testing/ :-) Don't get yourself > distracted by not seeing it as it is wildcard-automounted. > > And where is newpkgs ? :) I haven't checked, but are these information availables from the website ? cheers W. From bonivart at opencsw.org Thu Nov 20 14:09:12 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Thu, 20 Nov 2008 14:09:12 +0100 Subject: [csw-maintainers] where is testing ? In-Reply-To: <49255DE0.3010401@wbonnet.net> References: <40266351-3F85-438D-B569-FDA4C07C95C6@opencsw.org> <49255DE0.3010401@wbonnet.net> Message-ID: <625385e30811200509w5b60b270r36a447e1a2aee58b@mail.gmail.com> On Thu, Nov 20, 2008 at 1:53 PM, William Bonnet wrote: > And where is newpkgs ? :) > > I haven't checked, but are these information availables from the website ? Scp your packages to www.opencsw.org:/home/newpkgs. http://www.opencsw.org/standards/pkg-walkthrough "When you're satisfied that the package is worthy of public release, copy your finished packages to /home/newpkgs on www.opencsw.org and let Phil know they are ready. (remove them from /testing at this time, if they are there)" -- /peter From dam at opencsw.org Thu Nov 20 14:09:43 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 20 Nov 2008 14:09:43 +0100 Subject: [csw-maintainers] where is testing ? In-Reply-To: <49255DE0.3010401@wbonnet.net> References: <40266351-3F85-438D-B569-FDA4C07C95C6@opencsw.org> <49255DE0.3010401@wbonnet.net> Message-ID: Hi William, Am 20.11.2008 um 13:53 schrieb William Bonnet: > Dagobert Michelsen a ?crit : >> Am 20.11.2008 um 12:52 schrieb Frederic Van De Velde: >>> How do I put files in buildfarm.opencsw.org/testing ? >> >> You copy them to /home/testing/ :-) Don't get yourself >> distracted by not seeing it as it is wildcard-automounted. >> > > And where is newpkgs ? :) > > I haven't checked, but are these information availables from the > website ? Yes, but somewhat hidden: When you're satisfied that the package is worthy of public release, copy your finished packages to /home/newpkgs on www.opencsw.org and let Phil know they are ready. (remove them from /testing at this time, if they are there) I guess it would be good to have a wiki page which summarizes all the info needed for a new maintainer, written by a new maintainer. Volunteers? Best regards -- Dago From bonivart at opencsw.org Thu Nov 20 14:12:59 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Thu, 20 Nov 2008 14:12:59 +0100 Subject: [csw-maintainers] where is testing ? In-Reply-To: References: <40266351-3F85-438D-B569-FDA4C07C95C6@opencsw.org> <49255DE0.3010401@wbonnet.net> Message-ID: <625385e30811200512l331744efkee5c2ac40ad12427@mail.gmail.com> On Thu, Nov 20, 2008 at 2:09 PM, Dagobert Michelsen wrote: > I guess it would be good to have a wiki page which summarizes all the > info needed for a new maintainer, written by a new maintainer. > Volunteers? Yes, a simple page documenting the steps involved without going into detail, it could instead link to the official documentation (which is a mess). -- /peter From phil at bolthole.com Thu Nov 20 18:28:44 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 20 Nov 2008 09:28:44 -0800 Subject: [csw-maintainers] where is testing ? In-Reply-To: ; from dam@opencsw.org on Thu, Nov 20, 2008 at 02:09:43PM +0100 References: <40266351-3F85-438D-B569-FDA4C07C95C6@opencsw.org> <49255DE0.3010401@wbonnet.net> Message-ID: <20081120092844.C23285@bolthole.com> On Thu, Nov 20, 2008 at 02:09:43PM +0100, Dagobert Michelsen wrote: > > I haven't checked, but are these information availables from the > > website ? > > Yes, but somewhat hidden: > > "When you're satisfied that the package is worthy of public release, copy > your finished packages to /home/newpkgs on www.opencsw.org and let > Phil know...." It is ALSO mentioned on the TOP level page. http://www.opencsw.org/standards/ near the bottom, in the "pkg file creation" section From dam at opencsw.org Fri Nov 21 10:26:41 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 21 Nov 2008 10:26:41 +0100 Subject: [csw-maintainers] Upgrade of build8x today! Message-ID: <019753DE-449D-414D-BB68-E519E7AD5144@opencsw.org> Hi, the server build8x will be changed to new hardware from 867 MHz, 384 MB to 2400 MHz, 512 MB Not great, but better. For this there will be a downtime within the next 8 hours where the old host gets synced over and the new server will be put in place. I'll keep you informed. Best regards -- Dago From bonivart at opencsw.org Fri Nov 21 11:20:54 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Fri, 21 Nov 2008 11:20:54 +0100 Subject: [csw-maintainers] Anyone want to update libxml2? Message-ID: <625385e30811210220t3fa1d4fbvc919abe90b069f41@mail.gmail.com> The libxml2 package we have is both outdated and broken (build machine paths in it). Would any one be interested in updating it? I don't think Ken Mays will. http://www.opencsw.org/packages/libxml2 The source link is not updated any more, go to ftp://xmlsoft.org/libxml2/ instead. -- /peter From dam at opencsw.org Fri Nov 21 12:24:32 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 21 Nov 2008 12:24:32 +0100 Subject: [csw-maintainers] Anyone want to update libxml2? In-Reply-To: <625385e30811210220t3fa1d4fbvc919abe90b069f41@mail.gmail.com> References: <625385e30811210220t3fa1d4fbvc919abe90b069f41@mail.gmail.com> Message-ID: <5FB12541-2DA5-4FF7-BC53-D06B8EABD1DE@opencsw.org> Hi Peter, Am 21.11.2008 um 11:20 schrieb Peter Bonivart: > The libxml2 package we have is both outdated and broken (build machine > paths in it). Would any one be interested in updating it? I don't > think Ken Mays will. > > http://www.opencsw.org/packages/libxml2 > > The source link is not updated any more, go to > ftp://xmlsoft.org/libxml2/ instead. I did libxml2 as example for multi-isa-builds. The repackage already runs and 2.6.30 will hopefully be ready this evening. BTW: Anyone want to update python and make a 64 bit version? Best regards -- Dago From dam at opencsw.org Fri Nov 21 13:21:12 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 21 Nov 2008 13:21:12 +0100 Subject: [csw-maintainers] build8x is now down Message-ID: <9AD4CC7E-6DE2-4D79-98E5-23A88EABBDF5@opencsw.org> Hi, the server build8x will now be down. Please standby... -- Dago From phil at bolthole.com Fri Nov 21 15:34:19 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 21 Nov 2008 06:34:19 -0800 Subject: [csw-maintainers] Upgrade of build8x today! In-Reply-To: <019753DE-449D-414D-BB68-E519E7AD5144@opencsw.org>; from dam@opencsw.org on Fri, Nov 21, 2008 at 10:26:41AM +0100 References: <019753DE-449D-414D-BB68-E519E7AD5144@opencsw.org> Message-ID: <20081121063419.B35332@bolthole.com> On Fri, Nov 21, 2008 at 10:26:41AM +0100, Dagobert Michelsen wrote: > Hi, > > the server build8x will be changed to new hardware from > 867 MHz, 384 MB > to > 2400 MHz, 512 MB > Not great, but better. wow.. well, I'd call it great! :-) From phil at bolthole.com Fri Nov 21 15:38:45 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 21 Nov 2008 06:38:45 -0800 Subject: [csw-maintainers] 64-bit python In-Reply-To: <5FB12541-2DA5-4FF7-BC53-D06B8EABD1DE@opencsw.org>; from dam@opencsw.org on Fri, Nov 21, 2008 at 12:24:32PM +0100 References: <625385e30811210220t3fa1d4fbvc919abe90b069f41@mail.gmail.com> <5FB12541-2DA5-4FF7-BC53-D06B8EABD1DE@opencsw.org> Message-ID: <20081121063845.C35332@bolthole.com> On Fri, Nov 21, 2008 at 12:24:32PM +0100, Dagobert Michelsen wrote: > > BTW: Anyone want to update python and make a 64 bit version? > yikes. Do you know if "compiled" python will run equally well with the 64bit runtime, as from the regular 32bit one? I'm guessing not. if not, then this might be a good reason to deviate from our usual practice of "ship 64bit with 32bit package", and make a separate "python64" package. From dam at opencsw.org Fri Nov 21 15:44:57 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 21 Nov 2008 15:44:57 +0100 Subject: [csw-maintainers] build8x is up again In-Reply-To: <9AD4CC7E-6DE2-4D79-98E5-23A88EABBDF5@opencsw.org> References: <9AD4CC7E-6DE2-4D79-98E5-23A88EABBDF5@opencsw.org> Message-ID: <23ADFDC4-D6F4-43AF-820C-3A71F278CD8A@opencsw.org> Hi, Am 21.11.2008 um 13:21 schrieb Dagobert Michelsen: > the server build8x will now be down. The server build8x is now migrated to a new machine and can be used again. Please let me know if you encounter something unusual. Best regards -- Dago From dam at opencsw.org Fri Nov 21 16:42:51 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 21 Nov 2008 16:42:51 +0100 Subject: [csw-maintainers] libxml2 2.7.2 available In-Reply-To: <625385e30811210220t3fa1d4fbvc919abe90b069f41@mail.gmail.com> References: <625385e30811210220t3fa1d4fbvc919abe90b069f41@mail.gmail.com> Message-ID: <572D2121-9990-4497-A70D-2C58D83A45BC@opencsw.org> Hi Peter, Am 21.11.2008 um 11:20 schrieb Peter Bonivart: > The libxml2 package we have is both outdated and broken (build machine > paths in it). Would any one be interested in updating it? I don't > think Ken Mays will. > > http://www.opencsw.org/packages/libxml2 > > The source link is not updated any more, go to > ftp://xmlsoft.org/libxml2/ instead. libxml2 and related packages have been updated and are ready for testing/: libxml2-2.7.2,REV=2008.11.21-SunOS5.8-i386-CSW.pkg.gz libxml2-2.7.2,REV=2008.11.21-SunOS5.8-sparc-CSW.pkg.gz libxml2_devel-2.7.2,REV=2008.11.21-SunOS5.8-i386-CSW.pkg.gz libxml2_devel-2.7.2,REV=2008.11.21-SunOS5.8-sparc-CSW.pkg.gz pylibxml2-2.7.2,REV=2008.11.21-SunOS5.8-sparc-CSW.pkg.gz pylibxml2-2.7.2,REV=2008.11.21-SunOS5.8-i386-CSW.pkg.gz Feedback as always welcome! Best regards -- Dago From dam at opencsw.org Fri Nov 21 17:46:25 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 21 Nov 2008 17:46:25 +0100 Subject: [csw-maintainers] mGAR will arrive soon Message-ID: Hi, as you may have noticed I have begun transforming GAR to the new mGAR (=modularized GAR) structure. This will allow - building for multiple ISAs easily (like 32 and 64 bit) - building packages with legacy libraries easily (several versions in one package) - continous integration with Hudson - easier transition between major GAR updates as this can be done on a per-package basis. - dynamic prototypes to automatically split a software in multiple packages by rules - later "source packages" At some time in the near future the current trunk will be deleted and from that point on work should be done against the new mgar-tree. Feel free to work on trunk/ until then, the changes should be easily mergable. I'll write up some docs which explain how the old and new versions differ. Best regards -- Dago From bwalton at opencsw.org Fri Nov 21 18:09:28 2008 From: bwalton at opencsw.org (Ben Walton) Date: Fri, 21 Nov 2008 12:09:28 -0500 Subject: [csw-maintainers] git? Message-ID: <1227287196-sup-2976@ntdws12.chass.utoronto.ca> Hi All, I notice that there is a GAR build description for git, but there doesn't seem to be a released package for it. Is anyone working on this? If not, I'd be willing to give it a crack. I think my group will be standardizing on git in the near future, so having it for our solaris boxes in addition to our linux machines would be very helpful. -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 Nov 22 17:06:28 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 22 Nov 2008 17:06:28 +0100 Subject: [csw-maintainers] git? In-Reply-To: <1227287196-sup-2976@ntdws12.chass.utoronto.ca> References: <1227287196-sup-2976@ntdws12.chass.utoronto.ca> Message-ID: <875C8A1F-F3F6-4D57-AEC7-1D1DFB3F04F7@opencsw.org> Hi Ben, Am 21.11.2008 um 18:09 schrieb Ben Walton: > I notice that there is a GAR build description for git, but there > doesn't seem to be a released package for it. Is anyone working on > this? If not, I'd be willing to give it a crack. I did a start at trunk/devel/git. However, you need asciidoc for that. I packaged 8.2.5 some time ago but the package seems to have gotten lost during the split. I'll repackage 8.2.7 ASAP and keep you informed. If I recall correctly there were dependencies on XML catalogs which I was unable to fix. Anyway, feel free to take it over. > I think my group > will be standardizing on git in the near future, so having it for our > solaris boxes in addition to our linux machines would be very helpful. Best maintainers are the ones who actually use their packages :-) Best regards -- Dago From bwalton at opencsw.org Sat Nov 22 17:29:20 2008 From: bwalton at opencsw.org (Ben Walton) Date: Sat, 22 Nov 2008 11:29:20 -0500 Subject: [csw-maintainers] git? In-Reply-To: <875C8A1F-F3F6-4D57-AEC7-1D1DFB3F04F7@opencsw.org> References: <1227287196-sup-2976@ntdws12.chass.utoronto.ca> <875C8A1F-F3F6-4D57-AEC7-1D1DFB3F04F7@opencsw.org> Message-ID: <1227370964-sup-8443@ntdws12.chass.utoronto.ca> Excerpts from Dagobert Michelsen's message of Sat Nov 22 11:06:28 -0500 2008: > I did a start at trunk/devel/git. However, you need asciidoc for > that. I packaged 8.2.5 some time ago but the package seems to > have gotten lost during the split. I'll repackage 8.2.7 ASAP > and keep you informed. I started on this package yesterday too. I installed it locally to build git, but figured a package is better so that the GAR description was not dependent on my 'special' PATH. I'm almost done writing a configure.ac and Makefile.in for it (which I'll kick upstream) so that building the package is doable. > If I recall correctly there were dependencies on XML catalogs > which I was unable to fix. I believe that the git folks did some workaround so that the 8.x series could be used to build the docs for git. This was the source of my proxy question yesterday too. The git build currently stops because one of the xml/xslt tools can't pull down a file from sourceforge to validate the xml domain. > Anyway, feel free to take it over. Sure, I can do that. Maybe I'll have better luck with this than with ruby! :) [I've kicked a report up to ruby-core at ruby-lang, but haven't gotten any nibbles yet. I did discover that solaris 8 is, at best, minimally supported only because it's a POSIX environment...] > Best maintainers are the ones who actually use their packages :-) Eating ones own dogfood is always a good thing. Have a good weekend. -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 dam at opencsw.org Sat Nov 22 23:34:50 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 22 Nov 2008 23:34:50 +0100 Subject: [csw-maintainers] git? In-Reply-To: <1227370964-sup-8443@ntdws12.chass.utoronto.ca> References: <1227287196-sup-2976@ntdws12.chass.utoronto.ca> <875C8A1F-F3F6-4D57-AEC7-1D1DFB3F04F7@opencsw.org> <1227370964-sup-8443@ntdws12.chass.utoronto.ca> Message-ID: <7987A90D-9749-4F3C-9933-31C688A44915@opencsw.org> Hi Ben, Am 22.11.2008 um 17:29 schrieb Ben Walton: > Excerpts from Dagobert Michelsen's message of Sat Nov 22 11:06:28 > -0500 2008: > >> I did a start at trunk/devel/git. However, you need asciidoc for >> that. I packaged 8.2.5 some time ago but the package seems to >> have gotten lost during the split. I'll repackage 8.2.7 ASAP >> and keep you informed. > > I started on this package yesterday too. I installed it locally to > build git, but figured a package is better so that the GAR > description was not dependent on my 'special' PATH. I'm almost done > writing a configure.ac and Makefile.in for it (which I'll kick > upstream) so that building the package is doable. Very good! Feel free to take over asciidoc too. >> If I recall correctly there were dependencies on XML catalogs >> which I was unable to fix. > > I believe that the git folks did some workaround so that the 8.x > series could be used to build the docs for git. This was the source > of my proxy question yesterday too. The git build currently stops > because one of the xml/xslt tools can't pull down a file from > sourceforge to validate the xml domain. Yes, and I couldn't get it to validate even with internet access. Best regards -- Dago From dam at opencsw.org Sun Nov 23 21:49:46 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 23 Nov 2008 21:49:46 +0100 Subject: [csw-maintainers] Merry christmas! Message-ID: <55BD3712-DF63-45FD-8FF2-2974AF1FD505@opencsw.org> Fellow maintainers! I know it is not christmas yet, but I am happy to announce a new Sparc machine for package building. The current machine is a SF280R with 1 x 750 MHz, 2 GB Ram and 7 x 250 GB SCSI-IDE The new machine is a T5220, 4 x 1.2 GHz Cores (32 Strands), 8 GB Ram, 8 x 146 GB SAS It will be available for Solaris 10 Sparc package building, Solaris 8 Sparc package building (via Solaris 8 Branded Zones), Hudson Continous Integration and LDAP. For the transition I will need to temporarily disable some functions on the current machine as services will move over to the new machine one at a time. I will announce downtimes when needed. ...and theres more good news: There will be temporarily an additional x86 machine available. It is a X4440 with 4 x AMD 8356 2.3 GHz (16 cores total), 16 GB Ram for Solaris 10 x86 package building. I'll announce when it is ready to use. So, when you're idling along now is the time to start some big packages like qt4 or gcc. Best regards -- Dago From dam at opencsw.org Sun Nov 23 22:57:10 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 23 Nov 2008 22:57:10 +0100 Subject: [csw-maintainers] 64-bit python In-Reply-To: <20081121063845.C35332@bolthole.com> References: <625385e30811210220t3fa1d4fbvc919abe90b069f41@mail.gmail.com> <5FB12541-2DA5-4FF7-BC53-D06B8EABD1DE@opencsw.org> <20081121063845.C35332@bolthole.com> Message-ID: <00576986-F170-40A9-B3D6-0D27AB001CE1@opencsw.org> HI PHIL, Am 21.11.2008 um 15:38 schrieb Philip Brown: > On Fri, Nov 21, 2008 at 12:24:32PM +0100, Dagobert Michelsen wrote: >> >> BTW: Anyone want to update python and make a 64 bit version? > > yikes. > > Do you know if "compiled" python will run equally well with the 64bit > runtime, as from the regular 32bit one? > I'm guessing not. > > if not, then this might be a good reason to deviate from our usual > practice > of "ship 64bit with 32bit package", and make a separate "python64" > package. This goes equally well for Perl. And the binary packages must then be build for 32/64 bit Perl also :-P And for Perl with ithreads :-P== Best regards -- Dago From william at wbonnet.net Sun Nov 23 23:10:40 2008 From: william at wbonnet.net (William Bonnet) Date: Sun, 23 Nov 2008 23:10:40 +0100 Subject: [csw-maintainers] where is testing ? In-Reply-To: References: <40266351-3F85-438D-B569-FDA4C07C95C6@opencsw.org> <49255DE0.3010401@wbonnet.net> Message-ID: <4929D4E0.4060500@wbonnet.net> Hi > When you're satisfied that the package is worthy of public release, copy > > your finished packages to /home/newpkgs on www.opencsw.org and let > Phil know > > Could you please check that i have write access to this place ? or maybe i am not using the good scp argument ? scp firefox-2.0.0.18,REV\=2008.11.14-SunOS5.8-* www.opencsw.org:/home/newpkgs ssh: Could not resolve hostname www.opencsw.org: host/servname not known scp firefox-2.0.0.18,REV\=2008.11.14-SunOS5.8-* www:/home/newpkgs ssh: Could not resolve hostname www: host/servname not known 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 Sun Nov 23 23:16:25 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 23 Nov 2008 23:16:25 +0100 Subject: [csw-maintainers] where is testing ? In-Reply-To: <4929D4E0.4060500@wbonnet.net> References: <40266351-3F85-438D-B569-FDA4C07C95C6@opencsw.org> <49255DE0.3010401@wbonnet.net> <4929D4E0.4060500@wbonnet.net> Message-ID: Hi William, Am 23.11.2008 um 23:10 schrieb William Bonnet: >> When you're satisfied that the package is worthy of public release, >> copy >> >> your finished packages to /home/newpkgs on www.opencsw.org and let >> Phil know >> >> > Could you please check that i have write access to this place ? or > maybe > i am not using the good scp argument ? > > scp firefox-2.0.0.18,REV\=2008.11.14-SunOS5.8-* > www.opencsw.org:/home/newpkgs > ssh: Could not resolve hostname www.opencsw.org: host/servname not > known > > scp firefox-2.0.0.18,REV\=2008.11.14-SunOS5.8-* www:/home/newpkgs > ssh: Could not resolve hostname www: host/servname not known You must do this from 'login.bo.opencsw.org', the build-machines are not directly connected to the internet. Best regards -- Dago From william at wbonnet.net Sun Nov 23 23:22:51 2008 From: william at wbonnet.net (William Bonnet) Date: Sun, 23 Nov 2008 23:22:51 +0100 Subject: [csw-maintainers] where is testing ? In-Reply-To: References: <40266351-3F85-438D-B569-FDA4C07C95C6@opencsw.org> <49255DE0.3010401@wbonnet.net> <4929D4E0.4060500@wbonnet.net> Message-ID: <4929D7BB.8030309@wbonnet.net> Hi > You must do this from 'login.bo.opencsw.org', the build-machines > are not directly connected to the internet. > I forgot that... :) It's now prompting me for a password. Would it be possible to setup my ssh key ? because it seems that if one day i had this password, then i also forgot it. 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 phil at bolthole.com Mon Nov 24 02:41:28 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 23 Nov 2008 17:41:28 -0800 Subject: [csw-maintainers] 64-bit python In-Reply-To: <00576986-F170-40A9-B3D6-0D27AB001CE1@opencsw.org>; from dam@opencsw.org on Sun, Nov 23, 2008 at 10:57:10PM +0100 References: <625385e30811210220t3fa1d4fbvc919abe90b069f41@mail.gmail.com> <5FB12541-2DA5-4FF7-BC53-D06B8EABD1DE@opencsw.org> <20081121063845.C35332@bolthole.com> <00576986-F170-40A9-B3D6-0D27AB001CE1@opencsw.org> Message-ID: <20081123174128.B76485@bolthole.com> On Sun, Nov 23, 2008 at 10:57:10PM +0100, Dagobert Michelsen wrote: > HI PHIL, :-D > > Am 21.11.2008 um 15:38 schrieb Philip Brown: > > if not, then this might be a good reason to deviate from our usual > > practice of "ship 64bit with 32bit package", and make a separate > > "python64" package. > > This goes equally well for Perl. *gag* *choke*... 64bit perl??? as if perl wasnt bloated enough?!!! :-} Actually, i'm not exactly sure why someone would want 64bit python either. could someone enlighten us? From buysse at cla.umn.edu Mon Nov 24 03:21:32 2008 From: buysse at cla.umn.edu (Joshua Buysse) Date: Sun, 23 Nov 2008 20:21:32 -0600 Subject: [csw-maintainers] 64-bit python In-Reply-To: <20081123174128.B76485@bolthole.com> References: <625385e30811210220t3fa1d4fbvc919abe90b069f41@mail.gmail.com> <5FB12541-2DA5-4FF7-BC53-D06B8EABD1DE@opencsw.org> <20081121063845.C35332@bolthole.com> <00576986-F170-40A9-B3D6-0D27AB001CE1@opencsw.org> <20081123174128.B76485@bolthole.com> Message-ID: >> Am 21.11.2008 um 15:38 schrieb Philip Brown: >>> if not, then this might be a good reason to deviate from our usual >>> practice of "ship 64bit with 32bit package", and make a separate >>> "python64" package. >> >> This goes equally well for Perl. > > *gag* *choke*... 64bit perl??? as if perl wasnt bloated enough?!!! :-} > > Actually, i'm not exactly sure why someone would want 64bit python > either. > could someone enlighten us? Sadly, I had to build a 64-bit python internally a while back. Researchers using bioinformatics toolkits (for purposes other than what was intended, but cool idea). The code was written in Python, using FEBRL (http://datamining.anu.edu.au/projects/linkage.html). They were linking individual census records between different years, and the datafiles are in the tens or hundreds of gigs. Damn thing needed to load the entire set into memory, and even using MPI, it was a beast. Researchers do use scripting languages with huge data sets, especially in the biosciences. -- Joshua Buysse, System Engineer University of Minnesota, College of Liberal Arts "When fascism comes to America, it will be wrapped in an American flag and carrying a cross." -- Sinclair Lewis -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL: From ihsan at opencsw.org Mon Nov 24 09:07:11 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Mon, 24 Nov 2008 09:07:11 +0100 Subject: [csw-maintainers] where is testing ? In-Reply-To: <4929D7BB.8030309@wbonnet.net> References: <40266351-3F85-438D-B569-FDA4C07C95C6@opencsw.org> <49255DE0.3010401@wbonnet.net> <4929D4E0.4060500@wbonnet.net> <4929D7BB.8030309@wbonnet.net> Message-ID: <492A60AF.1080706@opencsw.org> Good morning, Am 23.11.2008 23:22 Uhr, William Bonnet schrieb: >> You must do this from 'login.bo.opencsw.org', the build-machines >> are not directly connected to the internet. >> > I forgot that... :) > > It's now prompting me for a password. Would it be possible to setup my > ssh key ? because it seems that if one day i had this password, then i > also forgot it. I copied your public key from the build machines now. Can you please try again? Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From william at wbonnet.net Mon Nov 24 13:26:55 2008 From: william at wbonnet.net (William Bonnet) Date: Mon, 24 Nov 2008 13:26:55 +0100 Subject: [csw-maintainers] where is testing ? In-Reply-To: <492A60AF.1080706@opencsw.org> References: <40266351-3F85-438D-B569-FDA4C07C95C6@opencsw.org> <49255DE0.3010401@wbonnet.net> <4929D4E0.4060500@wbonnet.net> <4929D7BB.8030309@wbonnet.net> <492A60AF.1080706@opencsw.org> Message-ID: <492A9D8F.7040204@wbonnet.net> Ihsan Dogan a ?crit : > Good morning, > > Am 23.11.2008 23:22 Uhr, William Bonnet schrieb: > > >>> You must do this from 'login.bo.opencsw.org', the build-machines >>> are not directly connected to the internet. >>> >>> >> I forgot that... :) >> >> It's now prompting me for a password. Would it be possible to setup my >> ssh key ? because it seems that if one day i had this password, then i >> also forgot it. >> > > I copied your public key from the build machines now. Can you please try > again? > It works. Thanks Firfox 2.0.0.18 has been pushed to unstable and removed from testing. cheers From dam at opencsw.org Mon Nov 24 14:11:26 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 24 Nov 2008 14:11:26 +0100 Subject: [csw-maintainers] 64-bit python In-Reply-To: <20081123174128.B76485@bolthole.com> References: <625385e30811210220t3fa1d4fbvc919abe90b069f41@mail.gmail.com> <5FB12541-2DA5-4FF7-BC53-D06B8EABD1DE@opencsw.org> <20081121063845.C35332@bolthole.com> <00576986-F170-40A9-B3D6-0D27AB001CE1@opencsw.org> <20081123174128.B76485@bolthole.com> Message-ID: <9903E2B3-DB76-4DE7-B86C-A9E5F85C827F@opencsw.org> Hi Phil, Am 24.11.2008 um 02:41 schrieb Philip Brown: >> Am 21.11.2008 um 15:38 schrieb Philip Brown: >>> if not, then this might be a good reason to deviate from our usual >>> practice of "ship 64bit with 32bit package", and make a separate >>> "python64" package. >> >> This goes equally well for Perl. > > *gag* *choke*... 64bit perl??? as if perl wasnt bloated enough?!!! :-} > > Actually, i'm not exactly sure why someone would want 64bit python > either. > could someone enlighten us? Features of 64 bit Perl: - >256 filedescriptors - >2GB Ram I needed both of them for an OpenLDAP Perl backend. Building a full 64 bit chain is not that hard and would give us some extra merits ==*:-) Best regards -- Dago From dam at opencsw.org Mon Nov 24 14:57:26 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 24 Nov 2008 14:57:26 +0100 Subject: [csw-maintainers] 64-bit python In-Reply-To: References: <625385e30811210220t3fa1d4fbvc919abe90b069f41@mail.gmail.com> <5FB12541-2DA5-4FF7-BC53-D06B8EABD1DE@opencsw.org> <20081121063845.C35332@bolthole.com> <00576986-F170-40A9-B3D6-0D27AB001CE1@opencsw.org> <20081123174128.B76485@bolthole.com> Message-ID: <5670D8CE-A3D8-495E-8B4F-61DA35ED2F21@opencsw.org> Hi Joshua, Am 24.11.2008 um 03:21 schrieb Joshua Buysse: >>> Am 21.11.2008 um 15:38 schrieb Philip Brown: >>>> if not, then this might be a good reason to deviate from our usual >>>> practice of "ship 64bit with 32bit package", and make a separate >>>> "python64" package. >>> >>> This goes equally well for Perl. >> >> *gag* *choke*... 64bit perl??? as if perl wasnt bloated >> enough?!!! :-} >> >> Actually, i'm not exactly sure why someone would want 64bit python >> either. >> could someone enlighten us? > > Sadly, I had to build a 64-bit python internally a while back. > Researchers using bioinformatics toolkits (for purposes other than > what was intended, but cool idea). The code was written in Python, > using FEBRL (http://datamining.anu.edu.au/projects/linkage.html). > They were linking individual census records between different years, > and the datafiles are in the tens or hundreds of gigs. Damn thing > needed to load the entire set into memory, and even using MPI, it > was a beast. > > Researchers do use scripting languages with huge data sets, > especially in the biosciences. IIRC Python is currently orphaned. As you seem to be quite qualified: do you like to take over Python and make a 64 bit version? I guess we will need some discussion on how to handle this in general for Python/Perl/OpenLDAP. Best regards -- Dago From bwalton at opencsw.org Mon Nov 24 17:52:12 2008 From: bwalton at opencsw.org (Ben Walton) Date: Mon, 24 Nov 2008 11:52:12 -0500 Subject: [csw-maintainers] asciidoc in testing/ Message-ID: <1227545407-sup-9703@ntdws12.chass.utoronto.ca> Hi All, If you're looking for YADGTg (yet another documentation generation tool ), you can give asciidoc a try. It's in testing/ now. I've installed it locally and it seems generally ok at this point (I've run a bunch of the git documentation through it so far). Comments are welcome. 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 Nov 24 20:49:44 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Mon, 24 Nov 2008 20:49:44 +0100 Subject: [csw-maintainers] Popularity statistics Message-ID: <492B0558.7050605@opencsw.org> Hi I was wondering if there are any download statistics available for the packages? -- Trygve From bonivart at opencsw.org Mon Nov 24 20:58:21 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Mon, 24 Nov 2008 20:58:21 +0100 Subject: [csw-maintainers] Popularity statistics In-Reply-To: <492B0558.7050605@opencsw.org> References: <492B0558.7050605@opencsw.org> Message-ID: <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com> On Mon, Nov 24, 2008 at 8:49 PM, Trygve Laugst?l wrote: > Hi > > I was wondering if there are any download statistics available for the > packages? That would be interesting, even just from a single mirror. We could also see which arch and release is most popular. Does any of the mirrors offer such service or let us fix it ourselves? -- /peter From phil at bolthole.com Mon Nov 24 21:05:35 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 24 Nov 2008 12:05:35 -0800 Subject: [csw-maintainers] Popularity statistics In-Reply-To: <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com>; from bonivart@opencsw.org on Mon, Nov 24, 2008 at 08:58:21PM +0100 References: <492B0558.7050605@opencsw.org> <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com> Message-ID: <20081124120535.O25010@bolthole.com> On Mon, Nov 24, 2008 at 08:58:21PM +0100, Peter Bonivart wrote: > On Mon, Nov 24, 2008 at 8:49 PM, Trygve Laugst?l wrote: > > Hi > > > > I was wondering if there are any download statistics available for the > > packages? > > That would be interesting, even just from a single mirror. > > We could also see which arch and release is most popular. > > Does any of the mirrors offer such service or let us fix it ourselves? ibiblio Stats were published previously on the maintainers list based on ibiblio stats. From trygvel at opencsw.org Mon Nov 24 21:09:37 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Mon, 24 Nov 2008 21:09:37 +0100 Subject: [csw-maintainers] Popularity statistics In-Reply-To: <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com> References: <492B0558.7050605@opencsw.org> <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com> Message-ID: <492B0A01.6070501@opencsw.org> Peter Bonivart wrote: > On Mon, Nov 24, 2008 at 8:49 PM, Trygve Laugst?l wrote: >> Hi >> >> I was wondering if there are any download statistics available for the >> packages? > > That would be interesting, even just from a single mirror. Yeah, that should be sufficient to show the distribution. > We could also see which arch and release is most popular. My idea was to use the data to prioritize our work for those who want to contribute to the project as a "whole" and help out with getting packages for the most popular packages. -- Trygve From william at wbonnet.net Mon Nov 24 21:10:33 2008 From: william at wbonnet.net (William Bonnet) Date: Mon, 24 Nov 2008 21:10:33 +0100 Subject: [csw-maintainers] Popularity statistics In-Reply-To: <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com> References: <492B0558.7050605@opencsw.org> <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com> Message-ID: <492B0A39.9060501@wbonnet.net> Hi > Does any of the mirrors offer such service or let us fix it ourselves? > It would certainly be easy to install something like awstats and parse mirror logs ? It's added to my todo list. -- 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 william at wbonnet.net Mon Nov 24 21:10:39 2008 From: william at wbonnet.net (William Bonnet) Date: Mon, 24 Nov 2008 21:10:39 +0100 Subject: [csw-maintainers] Popularity statistics In-Reply-To: <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com> References: <492B0558.7050605@opencsw.org> <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com> Message-ID: <492B0A3F.40708@wbonnet.net> Hi > Does any of the mirrors offer such service or let us fix it ourselves? > It would certainly be easy to install something like awstats and parse mirror logs ? It's added to my todo list. 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 phil at bolthole.com Mon Nov 24 21:27:59 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 24 Nov 2008 12:27:59 -0800 Subject: [csw-maintainers] Popularity statistics In-Reply-To: <492B0A01.6070501@opencsw.org>; from trygvel@opencsw.org on Mon, Nov 24, 2008 at 09:09:37PM +0100 References: <492B0558.7050605@opencsw.org> <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com> <492B0A01.6070501@opencsw.org> Message-ID: <20081124122759.Q25010@bolthole.com> On Mon, Nov 24, 2008 at 09:09:37PM +0100, Trygve Laugst?l wrote: > > My idea was to use the data to prioritize our work for those who want to > contribute to the project as a "whole" and help out with getting > packages for the most popular packages. In some ways, seems like that is non-productive at the start. Wouldnt the "most popular packages" naturally get the most help anyway? Contrariwise, the ones that "need the most help", might be the ones that no-one uses, becuase they are too out of date for people to use any more. I think Dagobert's buglist would probably be the most targetted way to identify "packages that need the most help.". And then there's stuff like samba. sigh. I made a gigantic test package a while back, and put it in testing. but have had zero feedback. Since I dont use samba myself, I really need SOMEONE to give me feedback about it before I put more work into splitting it up n stuff. (or, someone else is very welcome to take it over and I'll give them what notes I have) From bonivart at opencsw.org Mon Nov 24 21:45:27 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Mon, 24 Nov 2008 21:45:27 +0100 Subject: [csw-maintainers] Popularity statistics In-Reply-To: <20081124122759.Q25010@bolthole.com> References: <492B0558.7050605@opencsw.org> <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com> <492B0A01.6070501@opencsw.org> <20081124122759.Q25010@bolthole.com> Message-ID: <625385e30811241245i7cbf0d00j19d05b68e5bf93fc@mail.gmail.com> On Mon, Nov 24, 2008 at 9:27 PM, Philip Brown wrote: > I think Dagobert's buglist would probably be the most targetted way to > identify "packages that need the most help.". Another simple thing would be to use James' package list to find the oldest packages (with his Last Changed field). A quick review of those might find us a lot of packages that need updates but are orphaned. -- /peter From dam at opencsw.org Mon Nov 24 22:54:13 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 24 Nov 2008 22:54:13 +0100 Subject: [csw-maintainers] Popularity statistics In-Reply-To: <20081124122759.Q25010@bolthole.com> References: <492B0558.7050605@opencsw.org> <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com> <492B0A01.6070501@opencsw.org> <20081124122759.Q25010@bolthole.com> Message-ID: <26525A94-F51C-498B-8A6B-A0662945D58A@opencsw.org> Hi, Am 24.11.2008 um 21:27 schrieb Philip Brown: > I think Dagobert's buglist would probably be the most targetted way to > identify "packages that need the most help.". If someone has some spare cycles: there is another buglist sorted by number of reported bugs without maintainer distinction: Feel free to take over any orphaned or sabbatical packages if you have spare cycles. Best regards -- Dago From trygvel at opencsw.org Tue Nov 25 00:31:00 2008 From: trygvel at opencsw.org (=?UTF-8?B?VHJ5Z3ZlIExhdWdzdMO4bA==?=) Date: Tue, 25 Nov 2008 00:31:00 +0100 Subject: [csw-maintainers] asciidoc in testing/ In-Reply-To: <1227545407-sup-9703@ntdws12.chass.utoronto.ca> References: <1227545407-sup-9703@ntdws12.chass.utoronto.ca> Message-ID: <492B3934.6090909@opencsw.org> Ben Walton wrote: > Hi All, > > If you're looking for YADGTg (yet another documentation generation tool > ), you can give asciidoc a try. It's in testing/ now. I've > installed it locally and it seems generally ok at this point (I've run > a bunch of the git documentation through it so far). Is it not in GAR yet? I was using your package as a test package for Hudson [1] but it failed because it is still trying to download 8.2.5 instead of .7 that you've built. [1]: http://buildfarm.opencsw.org/hudson/job/asciidoc-solaris-8-sparc [2]: http://buildfarm.opencsw.org/hudson/job/asciidoc-solaris-8-sparc/2/console -- Trygve From bwalton at opencsw.org Tue Nov 25 14:41:54 2008 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 25 Nov 2008 08:41:54 -0500 Subject: [csw-maintainers] asciidoc in testing/ In-Reply-To: <492B3934.6090909@opencsw.org> References: <1227545407-sup-9703@ntdws12.chass.utoronto.ca> <492B3934.6090909@opencsw.org> Message-ID: <1227620493-sup-7116@ntdws12.chass.utoronto.ca> Excerpts from Trygve Laugst?l's message of Mon Nov 24 18:31:00 -0500 2008: > Is it not in GAR yet? I was using your package as a test package for > Hudson [1] but it failed because it is still trying to download 8.2.5 > instead of .7 that you've built. It should be checked into GAR...commits 2349 and 2350. -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 dam at opencsw.org Tue Nov 25 15:20:31 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 25 Nov 2008 15:20:31 +0100 Subject: [csw-maintainers] Server build8s will be unavailable for upgrade Message-ID: Hi, I will take build8s down in the next hour for snapshotting and migration to the T5220. A notification will be send when the server is up again. Sorry for the inconvenience -- Dago From bwalton at artsci.utoronto.ca Tue Nov 25 15:42:09 2008 From: bwalton at artsci.utoronto.ca (Ben Walton) Date: Tue, 25 Nov 2008 09:42:09 -0500 Subject: [csw-maintainers] asciidoc in testing/ In-Reply-To: <492B3934.6090909@opencsw.org> References: <1227545407-sup-9703@ntdws12.chass.utoronto.ca> <492B3934.6090909@opencsw.org> Message-ID: <1227623972-sup-2920@ntdws12.chass.utoronto.ca> Excerpts from Trygve Laugst?l's message of Mon Nov 24 18:31:00 -0500 2008: Hi Trygve, > Is it not in GAR yet? I was using your package as a test package for > Hudson [1] but it failed because it is still trying to download 8.2.5 > instead of .7 that you've built. You likely pointed Hudson at apps/asciidoc. I rolled my asciidoc from utils/asciidoc, as I'd created that workspace before seeing Dago's old apps/ version. I just checked in the svn rm of apps/asciidoc...hadn't planned to do that until my version was accepted and hadn't planned on anyone else looking at it!. Sorry for the confusion. -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 bwalton at opencsw.org Tue Nov 25 15:50:31 2008 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 25 Nov 2008 09:50:31 -0500 Subject: [csw-maintainers] asciidoc in testing/ In-Reply-To: <492B3934.6090909@opencsw.org> References: <1227545407-sup-9703@ntdws12.chass.utoronto.ca> <492B3934.6090909@opencsw.org> Message-ID: <1227624553-sup-361@ntdws12.chass.utoronto.ca> Excerpts from Trygve Laugst?l's message of Mon Nov 24 18:31:00 -0500 2008: Hi Trygve, > Is it not in GAR yet? I was using your package as a test package for > Hudson [1] but it failed because it is still trying to download 8.2.5 > instead of .7 that you've built. You likely pointed Hudson at apps/asciidoc. I rolled my asciidoc from utils/asciidoc, as I'd created that workspace before seeing Dago's old apps/ version. I just checked in the svn rm of apps/asciidoc...hadn't planned to do that until my version accepted and hadn't planned on anyone else looking at it!. Sorry for the confusion. 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. From dam at opencsw.org Tue Nov 25 16:52:34 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 25 Nov 2008 16:52:34 +0100 Subject: [csw-maintainers] Server build8s is available again In-Reply-To: References: Message-ID: <4EAB5D17-FEB9-4A5E-80E1-7CCB38D9CBA4@opencsw.org> Hi, Am 25.11.2008 um 15:20 schrieb Dagobert Michelsen: > I will take build8s down in the next hour for snapshotting > and migration to the T5220. A notification will be send when > the server is up again. The server build8s is up and running again. Feel free to continue your packaging work. Best regards -- Dago From dam at opencsw.org Tue Nov 25 17:31:21 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 25 Nov 2008 17:31:21 +0100 Subject: [csw-maintainers] build10s will be migrated today Message-ID: Hi, I will also migrate build10s today to the new machine. The server will be shut down in a couple of minutes. I'll post when it is ready again. Best regards -- Dago From dam at opencsw.org Tue Nov 25 18:28:09 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 25 Nov 2008 18:28:09 +0100 Subject: [csw-maintainers] build10s will be migrated today In-Reply-To: References: Message-ID: <16EA62EF-567F-4D2D-83F0-CC2EEE9A515D@opencsw.org> Hi, Am 25.11.2008 um 17:31 schrieb Dagobert Michelsen: > I will also migrate build10s today to the new machine. > The server will be shut down in a couple of minutes. I'll post > when it is ready again. The server build10s is available again. Happy packaging -- Dago From debertin at opencsw.org Tue Nov 25 20:29:07 2008 From: debertin at opencsw.org (debertin at opencsw.org) Date: Tue, 25 Nov 2008 13:29:07 -0600 Subject: [csw-maintainers] Forcing use of GNU binutils Message-ID: <18732.20995.799922.766973@autumn.msi.umn.edu> I know, use of GNU binutils on Solaris is usually not recommended, but I'm building a LISP compiler that produces assembly that only GNU "as" can parse, so there is no way around it. I've been using a locally-built GCC out of my homedir that I compiled with --with-as= and --with-gnu-as, but if there is a runtime GCC flag that does the same thing then it will make my job a lot easier. Thanks -- -Dan -- Dan Debertin Unix Systems Administrator Minnesota Supercomputing Institute University of Minnesota 541 Walter 117 Pleasant Street SE Minneapolis, MN 55455 debertin at msi.umn.edu 612.626.8926 From phil at bolthole.com Tue Nov 25 20:36:45 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 25 Nov 2008 11:36:45 -0800 Subject: [csw-maintainers] Forcing use of GNU binutils In-Reply-To: <18732.20995.799922.766973@autumn.msi.umn.edu>; from debertin@opencsw.org on Tue, Nov 25, 2008 at 01:29:07PM -0600 References: <18732.20995.799922.766973@autumn.msi.umn.edu> Message-ID: <20081125113645.U25010@bolthole.com> On Tue, Nov 25, 2008 at 01:29:07PM -0600, debertin at opencsw.org wrote: > I know, use of GNU binutils on Solaris is usually not recommended, but > I'm building a LISP compiler that produces assembly that only GNU "as" > can parse, so there is no way around it. > > I've been using a locally-built GCC out of my homedir that I compiled > with --with-as= and --with-gnu-as, but if there is a runtime GCC flag > that does the same thing then it will make my job a lot easier. there is also the option, in some more sanely suported source code, to explicitly define an assembler. you might look for that option also. From james at opencsw.org Tue Nov 25 20:58:08 2008 From: james at opencsw.org (James Lee) Date: Tue, 25 Nov 2008 19:58:08 GMT Subject: [csw-maintainers] Merry christmas! In-Reply-To: <55BD3712-DF63-45FD-8FF2-2974AF1FD505@opencsw.org> References: <55BD3712-DF63-45FD-8FF2-2974AF1FD505@opencsw.org> Message-ID: <20081125.19580800.154957751@gyor.oxdrove.co.uk> On 23/11/08, 20:49:46, Dagobert Michelsen wrote regarding [csw-maintainers] Merry christmas!: > I know it is not christmas yet, but I am happy to announce > a new Sparc machine for package building. May we ask, have Santa's Elves fashioned this from moss and reindeer antler or do we have someone else to thank? James. From james at opencsw.org Tue Nov 25 20:58:09 2008 From: james at opencsw.org (James Lee) Date: Tue, 25 Nov 2008 19:58:09 GMT Subject: [csw-maintainers] Server build8s is available again In-Reply-To: <4EAB5D17-FEB9-4A5E-80E1-7CCB38D9CBA4@opencsw.org> References: <4EAB5D17-FEB9-4A5E-80E1-7CCB38D9CBA4@opencsw.org> Message-ID: <20081125.19580900.1221328234@gyor.oxdrove.co.uk> On 25/11/08, 15:52:34, Dagobert Michelsen wrote regarding Re: [csw-maintainers] Server build8s is available again: > > and migration to the T5220. A notification will be send when > > the server is up again. > The server build8s is up and running again. Feel free > to continue your packaging work. gmake[3]: warning: Clock skew detected. Your build may be incomplete. ... gmake[3]: Warning: File `Makefile' has modification time 1.9e+02 s in the future ... It would be rude not do do a timing test, so I did a test build of GraphicsMagick-1.3.1: pandora V240 2 x 1500MHz US3i: real 7:09.891 user 0.033 sys 0.070 build8s T5220 32 x 1165MHz UltraSPARC T2: real 11:41.853 user 39:13.994 sys 7:57.193 "gmake -j 32" should test the robustness of the Makefiles although it appeared not to use that many jobs. A lot of build time is spent (needlessly) running ./configure in one-at-a-time mode - do I really need to discover if f77 takes -g? James. From dam at opencsw.org Wed Nov 26 12:57:03 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 26 Nov 2008 12:57:03 +0100 Subject: [csw-maintainers] asciidoc in testing/ In-Reply-To: <1227545407-sup-9703@ntdws12.chass.utoronto.ca> References: <1227545407-sup-9703@ntdws12.chass.utoronto.ca> Message-ID: <028F5059-6A2F-4621-BE5A-C3BF71E4E369@opencsw.org> Hi Ben, Am 24.11.2008 um 17:52 schrieb Ben Walton: > If you're looking for YADGTg (yet another documentation generation > tool > ), you can give asciidoc a try. It's in testing/ now. I've > installed it locally and it seems generally ok at this point (I've run > a bunch of the git documentation through it so far). The file in testing/ had 640 permissions. Please make sure that the files are 644 as the catalog builder cannot read it otherwise. I fixed that for now. Best regards -- Dago From dam at opencsw.org Wed Nov 26 13:09:25 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 26 Nov 2008 13:09:25 +0100 Subject: [csw-maintainers] Merry christmas! In-Reply-To: <20081125.19580800.154957751@gyor.oxdrove.co.uk> References: <55BD3712-DF63-45FD-8FF2-2974AF1FD505@opencsw.org> <20081125.19580800.154957751@gyor.oxdrove.co.uk> Message-ID: <7B6DD977-049F-4E02-9B9D-9E2F67F5CA1B@opencsw.org> Hi James, Am 25.11.2008 um 20:58 schrieb James Lee: > On 23/11/08, 20:49:46, Dagobert Michelsen wrote > regarding > [csw-maintainers] Merry christmas!: > >> I know it is not christmas yet, but I am happy to announce >> a new Sparc machine for package building. > > May we ask, have Santa's Elves fashioned this from moss and > reindeer antler or do we have someone else to thank? The machine was previously used for testing LDOMs in our lab. As we also have a T1000 these tests can also be done on that machine. So, thank my colleagues and my boss. Best regards -- Dago From dam at opencsw.org Wed Nov 26 13:11:31 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 26 Nov 2008 13:11:31 +0100 Subject: [csw-maintainers] Server build8s is available again In-Reply-To: <20081125.19580900.1221328234@gyor.oxdrove.co.uk> References: <4EAB5D17-FEB9-4A5E-80E1-7CCB38D9CBA4@opencsw.org> <20081125.19580900.1221328234@gyor.oxdrove.co.uk> Message-ID: <62A953D6-B7E1-487D-B4D9-4F66BF73A470@opencsw.org> Hi James, Am 25.11.2008 um 20:58 schrieb James Lee: > gmake[3]: warning: Clock skew detected. Your build may be > incomplete. > ... > gmake[3]: Warning: File `Makefile' has modification time 1.9e+02 s > in the > future > ... There was a glitch in the network configuration which prevented xntpd from synchronizing. Should be fixed now. > It would be rude not do do a timing test, so I did a test build of > GraphicsMagick-1.3.1: > > pandora V240 2 x 1500MHz US3i: > > real 7:09.891 > user 0.033 > sys 0.070 > > > build8s T5220 32 x 1165MHz UltraSPARC T2: > > real 11:41.853 > user 39:13.994 > sys 7:57.193 > > > > "gmake -j 32" should test the robustness of the Makefiles although it > appeared not to use that many jobs. A lot of build time is spent > (needlessly) running ./configure in one-at-a-time mode - do I really > need to discover if f77 takes -g? I presume you did the build tests from your homedir? That is still NFS-mounted from the 750 MHz 280R at BO. Please retest after that has been migrated also. Thanks for testing! -- Dago From bwalton at opencsw.org Wed Nov 26 15:13:44 2008 From: bwalton at opencsw.org (Ben Walton) Date: Wed, 26 Nov 2008 09:13:44 -0500 Subject: [csw-maintainers] mktemp on build farm Message-ID: <1227708770-sup-3685@ntdws12.chass.utoronto.ca> Hi Dago, Could you pop mktemp onto the BO machines? 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 Nov 26 15:33:05 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 26 Nov 2008 15:33:05 +0100 Subject: [csw-maintainers] mktemp on build farm In-Reply-To: <1227708770-sup-3685@ntdws12.chass.utoronto.ca> References: <1227708770-sup-3685@ntdws12.chass.utoronto.ca> Message-ID: <2CFB3D50-9805-4B6E-872F-E1AB9D74D94A@opencsw.org> Hi Ben, Am 26.11.2008 um 15:13 schrieb Ben Walton: > Could you pop mktemp onto the BO machines? Done. Best regards -- Dago From dam at opencsw.org Wed Nov 26 16:05:46 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 26 Nov 2008 16:05:46 +0100 Subject: [csw-maintainers] IMPORTANT: Transition to mGAR Message-ID: <890EF0AE-E169-4A84-90C0-DF7A2A74CEAD@opencsw.org> Hi, the transition to mGAR is almost finished. The documentation is linked from Please read it. I have already merged commits after r2333 to mGAR. The directories csw/trunk csw/tags csw/branches/dam csw/branches/joyent csw/branches/modularpkg csw/branches/yann will be deleted as experimental GAR implementations can now be done on a per-package basis. The deletion will occur at the end of the week. Please make sure to migrate all your modified checkouts to mGAR by then. (For maintainers not yet familiar with Subversion: a deletions means it is no longer visible. By using the revision number it will always be possible to get everything back, even if it is deleted in the current revision). Best regards -- Dago From fred at opencsw.org Thu Nov 27 11:48:55 2008 From: fred at opencsw.org (Frederic Van De Velde) Date: Thu, 27 Nov 2008 11:48:55 +0100 Subject: [csw-maintainers] IMPORTANT: Transition to mGAR In-Reply-To: <890EF0AE-E169-4A84-90C0-DF7A2A74CEAD@opencsw.org> References: <890EF0AE-E169-4A84-90C0-DF7A2A74CEAD@opencsw.org> Message-ID: <689E05BB-57B7-488D-BEBD-9BF942FE94EE@opencsw.org> Hi, Very good work. I'm trying to add one package to the cpan tree. I followed the procedure on the wiki ( the one with partial repository checkout) but can't manage to do it. Let's take a concrete example, I have a directory /home/fred/mgar where I downloaded some existing packages into their subdirectories with this command: svn co https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/cpan/My-Perl-Module I have then: /home/fred/mgar/My-Perl-Module/[trunk/branches/tags] Now I want to add a new perl module, what's the procedure ? Regards, Frederic. On 26 Nov 2008, at 16:05, Dagobert Michelsen wrote: > Hi, > > the transition to mGAR is almost finished. The documentation > is linked from > title=Main_Page> > Please read it. > > I have already merged commits after r2333 to mGAR. > > The directories > csw/trunk > csw/tags > csw/branches/dam > csw/branches/joyent > csw/branches/modularpkg > csw/branches/yann > will be deleted as experimental GAR implementations can now be done > on a per-package basis. The deletion will occur at the end of the > week. Please make sure to migrate all your modified checkouts > to mGAR by then. (For maintainers not yet familiar with Subversion: > a deletions means it is no longer visible. By using the revision > number > it will always be possible to get everything back, even if it is > deleted > in the current revision). > > > Best regards > > -- Dago > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers From dam at opencsw.org Thu Nov 27 13:20:03 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 27 Nov 2008 13:20:03 +0100 Subject: [csw-maintainers] BO Buildfarm will be down due to migration Message-ID: <57E10DB6-126E-4AEC-A222-B2C809D79EBB@opencsw.org> Hi, today I will migrate the remaining parts "login", NFS and Web to the T5220. The machine will be unavailable during this time. I'll post when the migration is finished. Best regards -- Dago From dam at opencsw.org Thu Nov 27 22:28:12 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 27 Nov 2008 22:28:12 +0100 Subject: [csw-maintainers] BO Buildfarm will be down due to migration In-Reply-To: <57E10DB6-126E-4AEC-A222-B2C809D79EBB@opencsw.org> References: <57E10DB6-126E-4AEC-A222-B2C809D79EBB@opencsw.org> Message-ID: <1530472E-819B-4A7A-8301-363B1F1768F8@opencsw.org> Hi, Am 27.11.2008 um 13:20 schrieb Dagobert Michelsen: > today I will migrate the remaining parts "login", NFS and Web > to the T5220. The machine will be unavailable during this time. > I'll post when the migration is finished. Everything has been migrated to the new machine and should work as before. Unfortunately build8x has an issue with the boot archive which I can not fix from home (where I am right now) as it is an old PC without remote console. This will be fixed tomorrow. Please let me know if you encounter anything else suspicious. James: Please repeat your benchmark, and the clock should now be running in sync too. Best regards -- Dago From dam at opencsw.org Thu Nov 27 23:52:46 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 27 Nov 2008 23:52:46 +0100 Subject: [csw-maintainers] IMPORTANT: Transition to mGAR In-Reply-To: <689E05BB-57B7-488D-BEBD-9BF942FE94EE@opencsw.org> References: <890EF0AE-E169-4A84-90C0-DF7A2A74CEAD@opencsw.org> <689E05BB-57B7-488D-BEBD-9BF942FE94EE@opencsw.org> Message-ID: <6B8A88C1-94E1-4D85-84CF-AE124E80CFB0@opencsw.org> Hi Frederic,, Am 27.11.2008 um 11:48 schrieb Frederic Van De Velde: > Very good work. > > I'm trying to add one package to the cpan tree. > I followed the procedure on the wiki ( the one with partial repository > checkout) but can't manage to do it. I guess the docs were a bit misleading. Now I put all in the Makefile in pkg/, should be easier. The docs have been updated accordingly. > Let's take a concrete example, I have a directory /home/fred/mgar > where I downloaded some existing packages into their subdirectories > with this command: > > svn co https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/cpan/My-Perl-Module > > I have then: /home/fred/mgar/My-Perl-Module/[trunk/branches/tags] > > Now I want to add a new perl module, what's the procedure ? Try this: ? svn -N co https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/cpan ? cd cpan ? gmake newpkg-My-New-Module ? cd My-New-Module/trunk ? Edit the Makefile etc. ? svn add for everything valuable in your package ? cd ../.. ? svn -m "cpan/My-New-Module: Initial commit" commit Feedback as always welcome. Best regards -- Dago From phil at bolthole.com Fri Nov 28 00:11:45 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 27 Nov 2008 15:11:45 -0800 Subject: [csw-maintainers] IMPORTANT: Transition to mGAR In-Reply-To: <6B8A88C1-94E1-4D85-84CF-AE124E80CFB0@opencsw.org> References: <890EF0AE-E169-4A84-90C0-DF7A2A74CEAD@opencsw.org> <689E05BB-57B7-488D-BEBD-9BF942FE94EE@opencsw.org> <6B8A88C1-94E1-4D85-84CF-AE124E80CFB0@opencsw.org> Message-ID: <20081127231145.GA80469@bolthole.com> On Thu, Nov 27, 2008 at 11:52:46PM +0100, Dagobert Michelsen wrote: > >... > > Now I want to add a new perl module, what's the procedure ? > > > Try this: > > ? svn -N co https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/cpan > ? cd cpan > ? gmake newpkg-My-New-Module > ? cd My-New-Module/trunk > ? Edit the Makefile etc. > ? svn add for everything valuable in your package > ? cd ../.. > ? svn -m "cpan/My-New-Module: Initial commit" commit > > Feedback as always welcome. It might be nice, if it were possible to make some kind of set of wrappers. something along the lines of $ [makenewproj] (which pulls down a bunch of templates) (or contrariwise, [getmyproj], which pulls down the relevant stuff) $ [savemystuffs] Having to manually do a bunch of svn stuff, seems like kind of a hassle. especialy with typing that longugly(tm) stuff to the svn repository. seems like that should be made transparent somehow. it's extremely ugly, to my eyes. From dam at opencsw.org Fri Nov 28 09:16:31 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 28 Nov 2008 09:16:31 +0100 Subject: [csw-maintainers] BO Buildfarm will be down due to migration In-Reply-To: <1530472E-819B-4A7A-8301-363B1F1768F8@opencsw.org> References: <57E10DB6-126E-4AEC-A222-B2C809D79EBB@opencsw.org> <1530472E-819B-4A7A-8301-363B1F1768F8@opencsw.org> Message-ID: <0E53C46C-2B39-4D4B-8ED4-F35ECB6EB767@opencsw.org> Hi, Am 27.11.2008 um 22:28 schrieb Dagobert Michelsen: > Everything has been migrated to the new machine and should work > as before. Unfortunately build8x has an issue with the boot archive > which I can not fix from home (where I am right now) as it is an old > PC without remote console. This will be fixed tomorrow. build8x is up and running again. The farm should be fully operational again. Please let me know if you encounter anything suspicious. Best regards -- Dago From dam at opencsw.org Fri Nov 28 11:03:37 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 28 Nov 2008 11:03:37 +0100 Subject: [csw-maintainers] IMPORTANT: Transition to mGAR In-Reply-To: <20081127231145.GA80469@bolthole.com> References: <890EF0AE-E169-4A84-90C0-DF7A2A74CEAD@opencsw.org> <689E05BB-57B7-488D-BEBD-9BF942FE94EE@opencsw.org> <6B8A88C1-94E1-4D85-84CF-AE124E80CFB0@opencsw.org> <20081127231145.GA80469@bolthole.com> Message-ID: <75929304-6B62-486F-80D8-25D5ED110717@opencsw.org> Hi Phil, Am 28.11.2008 um 00:11 schrieb Philip Brown: > On Thu, Nov 27, 2008 at 11:52:46PM +0100, Dagobert Michelsen wrote: >>> ... >>> Now I want to add a new perl module, what's the procedure ? >> >> >> Try this: >> >> ? svn -N co https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/cpan >> ? cd cpan >> ? gmake newpkg-My-New-Module >> ? cd My-New-Module/trunk >> ? Edit the Makefile etc. >> ? svn add for everything valuable in your package >> ? cd ../.. >> ? svn -m "cpan/My-New-Module: Initial commit" commit >> >> Feedback as always welcome. > > It might be nice, if it were possible to make some kind of set of > wrappers. > > something along the lines of > > $ [makenewproj] > (which pulls down a bunch of templates) > > (or contrariwise, [getmyproj], which pulls down the relevant > stuff) > > > $ [savemystuffs] > > > > Having to manually do a bunch of svn stuff, seems like kind of a > hassle. > especialy with typing that longugly(tm) stuff to the svn repository. > seems > like that should be made transparent somehow. it's extremely ugly, > to my > eyes. SVN does introduce some complexity, true. But I think it is not that hard. The problem is bootstrapping GAR checkout. Once you have GAR the complexity can be hidden in the Makefiles (which I did with newpkg-*). I don't know if a 3-line shellscript wrapping 'svn co', 'svn add' and 'svn commit' will really help here. At least I can't think of a solution that makes usage easier. Anybody more ideas? Maybe a GAR package that includes some bootstrapping stuff would help? Best regards -- Dago From fred at opencsw.org Fri Nov 28 12:01:55 2008 From: fred at opencsw.org (Frederic Van De Velde) Date: Fri, 28 Nov 2008 12:01:55 +0100 Subject: [csw-maintainers] IMPORTANT: Transition to mGAR In-Reply-To: <6B8A88C1-94E1-4D85-84CF-AE124E80CFB0@opencsw.org> References: <890EF0AE-E169-4A84-90C0-DF7A2A74CEAD@opencsw.org> <689E05BB-57B7-488D-BEBD-9BF942FE94EE@opencsw.org> <6B8A88C1-94E1-4D85-84CF-AE124E80CFB0@opencsw.org> Message-ID: <6248AE2C-7D97-44C5-8217-36465FF5CBE9@opencsw.org> > > Try this: > > ? svn -N co https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/cpan > ? cd cpan > ? gmake newpkg-My-New-Module > ? cd My-New-Module/trunk > ? Edit the Makefile etc. > ? svn add for everything valuable in your package > ? cd ../.. > ? svn -m "cpan/My-New-Module: Initial commit" commit > > Feedback as always welcome. > Many thanks, it's a quite simple procedure now ... > Best regards > -- Dago > Fred. From dam at opencsw.org Fri Nov 28 12:12:06 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 28 Nov 2008 12:12:06 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <4922660D.9070203@opencsw.org> References: <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> <5F994B04-687B-4AC3-91AE-DAAE62F4716B@opencsw.org> <20081117172408.D39788@bolthole.com> <4922660D.9070203@opencsw.org> Message-ID: Hi! (sorry for the HTML mail, but otherwise the long lines are broken). Am 18.11.2008 um 07:51 schrieb Trygve Laugst?l: > I agree with Phil here, we need two packages. I would never use JDK or > JRE package that has been modified by upstream packages, just see the > just that Debian tries deliver with their "java" packages. I am currently looking into the JDK/JRE issue. The idea is to have a CSWjre6 package containing the JRE and a CSWjdk6 package, which depends on CSWjre6 and adds the JDK. So, the layout will look like this: /opt/csw/java/jdk/latest links to ../jdk6 (or jdk7 later) CSWjdk (depends on CSWjdk6) /opt/csw/java/jdk6 links to jdk1.6.0_07 (or _08 later) CSWjdk6 /opt/csw/java/jdk1.6.0_07 contains stuff from archive CSWjdk6 /opt/csw/java/jdk1.6.0_07/jre contains JRE inside JDK CSWjre6 /opt/csw/java/jre/latest links to ../jre6 CSWjre (depends on CSWjre6) /opt/csw/java/jre6 links to jre1.6.0_07 CSWjre6 /opt/csw/java/jre1.6.0_07 links to jdk1.6.0_07/jre CSWjre6 /opt/csw/java/man links to ../jdk/latest/man CSWjre /opt/csw/java/jre6/man links to ../../jdk6/man CSWjre I compared the JRE embedded in the JDK. The following files are only in jdk1.6.0_07/jre: lib/sparc/libsaproc.so lib/sparcv9/libsaproc.so lib/sparc/libattach.so lib/sparcv9/libattach.so What are these for? Just take the JRE from the JDK add them to the CSWjre6? When the permit from Sun arrives I'll give the package a final shot. Best regards -- Dago -------------- next part -------------- An HTML attachment was scrubbed... URL: From dam at opencsw.org Fri Nov 28 13:38:29 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 28 Nov 2008 13:38:29 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: References: <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> <5F994B04-687B-4AC3-91AE-DAAE62F4716B@opencsw.org> <20081117172408.D39788@bolthole.com> <4922660D.9070203@opencsw.org> Message-ID: <4CA4F900-6D7D-49AD-A072-7D15E7A90AB3@opencsw.org> Hi, sorry for the repost, now with corrected pathes. Please ignore previous posting. Best regards -- Dago Am 28.11.2008 um 12:12 schrieb Dagobert Michelsen: > Hi! > > (sorry for the HTML mail, but otherwise the long lines are broken). > > Am 18.11.2008 um 07:51 schrieb Trygve Laugst?l: >> I agree with Phil here, we need two packages. I would never use JDK >> or >> JRE package that has been modified by upstream packages, just see the >> just that Debian tries deliver with their "java" packages. > > I am currently looking into the JDK/JRE issue. The idea is > to have a CSWjre6 package containing the JRE and a CSWjdk6 > package, which depends on CSWjre6 and adds the JDK. > > So, the layout will look like this: > > /opt/csw/java/jdk/latest links to jdk6 (or jdk7 later) CSWjdk > (depends on CSWjdk6) > /opt/csw/java/jdk/jdk6 links to jdk1.6.0_07 (or _08 later) CSWjdk6 > /opt/csw/java/jdk/jdk1.6.0_07 contains stuff from archive CSWjdk6 > /opt/csw/java/jdk/jdk1.6.0_07/jre contains JRE inside JDK CSWjre6 >> > /opt/csw/java/jre/jdk1.6.0_07/jre/man links to ../man CSWjre6 > > /opt/csw/java/jre/latest links to jre6 CSWjre (depends on > CSWjre6) > /opt/csw/java/jre/jre6 links to jre1.6.0_07 CSWjre6 > /opt/csw/java/jre/jre1.6.0_07 links to jdk1.6.0_07/jre CSWjre6 >> > /opt/csw/java/man links to jdk/latest/man CSWjre > > I compared the JRE embedded in the JDK. The following files > are only in jdk1.6.0_07/jre: > > lib/sparc/libsaproc.so > lib/sparcv9/libsaproc.so > lib/sparc/libattach.so > lib/sparcv9/libattach.so > > What are these for? Just take the JRE from the JDK add them to the > CSWjre6? > > When the permit from Sun arrives I'll give the package > a final shot. > > > Best regards > > -- Dago > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers -------------- next part -------------- An HTML attachment was scrubbed... URL: From phil at bolthole.com Fri Nov 28 15:34:15 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 28 Nov 2008 06:34:15 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <4CA4F900-6D7D-49AD-A072-7D15E7A90AB3@opencsw.org> References: <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> <5F994B04-687B-4AC3-91AE-DAAE62F4716B@opencsw.org> <20081117172408.D39788@bolthole.com> <4922660D.9070203@opencsw.org> <4CA4F900-6D7D-49AD-A072-7D15E7A90AB3@opencsw.org> Message-ID: <20081128143415.GB22302@bolthole.com> Sounds good to me. Just one word of warning... On Fri, Nov 28, 2008 at 01:38:29PM +0100, Dagobert Michelsen wrote: > When the permit from Sun arrives I'll give the package > a final shot. we may be waiting for a very LOOOOONG time on that. even when sun is 100% favourable to doing something, getting legal approval for something seems to take a minimum of 3 months :-( From skayser at opencsw.org Fri Nov 28 15:37:28 2008 From: skayser at opencsw.org (Sebastian Kayser) Date: Fri, 28 Nov 2008 15:37:28 +0100 Subject: [csw-maintainers] First packaging efforts (synergy 1.3.1 in testing/). Feedback, someone? Message-ID: <49300228.20206@opencsw.org> Hi *, i just wrapped my first package :) (using the stagepkg/createpkg way) and put it in testing/. http://mirror.opencsw.org/testing/synergy-1.3.1,REV=2008.11.28-SunOS5.8-i386-CSW.pkg.gz http://mirror.opencsw.org/testing/synergy-1.3.1,REV=2008.11.28-SunOS5.8-sparc-CSW.pkg.gz Would be great if someone could give it a spin and have a look whether i missed anything. The only thing that struck me is the increased binary size compared to the version in current/. 1.2.2 from current/: root @ ray2 /opt/csw/bin# ls -l synergy* -rwxr-xr-x 1 root bin 580712 Jan 28 2005 synergyc -rwxr-xr-x 1 root bin 761456 Jan 28 2005 synergys 1.3.1 from testing/: root @ ray1 /opt/csw/bin# ls -l synergy* -rwxr-xr-x 1 root bin 1838776 Nov 28 14:47 synergyc -rwxr-xr-x 1 root bin 2542432 Nov 28 14:47 synergys >From what i see, the current/ package depends on CSWgcc3rt and its binaries are linked against libgcc_s.so.1. Does that mean they were compiled using gcc and that's where the size difference comes from? I did my builds with Sun Studio cc. Cheers Sebastian From phil at bolthole.com Fri Nov 28 15:38:20 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 28 Nov 2008 06:38:20 -0800 Subject: [csw-maintainers] IMPORTANT: Transition to mGAR In-Reply-To: <75929304-6B62-486F-80D8-25D5ED110717@opencsw.org> References: <890EF0AE-E169-4A84-90C0-DF7A2A74CEAD@opencsw.org> <689E05BB-57B7-488D-BEBD-9BF942FE94EE@opencsw.org> <6B8A88C1-94E1-4D85-84CF-AE124E80CFB0@opencsw.org> <20081127231145.GA80469@bolthole.com> <75929304-6B62-486F-80D8-25D5ED110717@opencsw.org> Message-ID: <20081128143820.GC22302@bolthole.com> On Fri, Nov 28, 2008 at 11:03:37AM +0100, Dagobert Michelsen wrote: > Hi Phil, > > Am 28.11.2008 um 00:11 schrieb Philip Brown: > > Having to manually do a bunch of svn stuff, seems like kind of a > > hassle. [....] > > SVN does introduce some complexity, true. But I think it is > not that hard. compiling many of our packages oneself is "not that hard" either. ./configure --prefix=/where/you/like make make install but for some reason, many people seem to appreciate being able to skip those "not hard" steps, into a simpler, single step ;-) having wrappers is a nice thing. From phil at bolthole.com Fri Nov 28 15:48:06 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 28 Nov 2008 06:48:06 -0800 Subject: [csw-maintainers] First packaging efforts (synergy 1.3.1 in testing/). Feedback, someone? In-Reply-To: <49300228.20206@opencsw.org> References: <49300228.20206@opencsw.org> Message-ID: <20081128144806.GD22302@bolthole.com> On Fri, Nov 28, 2008 at 03:37:28PM +0100, Sebastian Kayser wrote: > >From what i see, the current/ package depends on CSWgcc3rt and its > binaries are linked against libgcc_s.so.1. Does that mean they were > compiled using gcc and that's where the size difference comes from? I > did my builds with Sun Studio cc. Yup, most likely If you wanted to spend more time on it, you could recompile and tell sun cc to optimize for size more than speed. It tends to "unroll loops" if you highly optimize. And/Or reduce the optimize level to plain "-O", if you are using -fast, and compare that. Synergy is onlyl a virtual "KVM switch" after all. From skayser at opencsw.org Fri Nov 28 17:58:20 2008 From: skayser at opencsw.org (Sebastian Kayser) Date: Fri, 28 Nov 2008 17:58:20 +0100 Subject: [csw-maintainers] First packaging efforts (synergy 1.3.1 in testing/). Feedback, someone? In-Reply-To: <20081128144806.GD22302@bolthole.com> References: <49300228.20206@opencsw.org> <20081128144806.GD22302@bolthole.com> Message-ID: <4930232C.6050901@opencsw.org> Philip Brown wrote: > On Fri, Nov 28, 2008 at 03:37:28PM +0100, Sebastian Kayser wrote: >> >From what i see, the current/ package depends on CSWgcc3rt and its >> binaries are linked against libgcc_s.so.1. Does that mean they were >> compiled using gcc and that's where the size difference comes from? I >> did my builds with Sun Studio cc. > > Yup, most likely > > If you wanted to spend more time on it, you could recompile and tell sun cc > to optimize for size more than speed. It tends to "unroll loops" if you > highly optimize. > And/Or reduce the optimize level to plain "-O", if you are using -fast, and > compare that. Synergy is onlyl a virtual "KVM switch" after all. Ok, i gave it another try with different optimization levels (-xO2, -xO3, without and without -xspace) and i could squeeze the file size for about 150k each (ended up with -xO3 -xspace). Updated packages are in testing/. As its still the same day, REV and thus the package file names staid the same. How do you differentiate the updated package in such a situation? Right now pkg-get (and pkgutil) won't let me upgrade the package. Cheers Sebastian From phil at bolthole.com Fri Nov 28 18:19:28 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 28 Nov 2008 09:19:28 -0800 Subject: [csw-maintainers] First packaging efforts (synergy 1.3.1 in testing/). Feedback, someone? In-Reply-To: <4930232C.6050901@opencsw.org> References: <49300228.20206@opencsw.org> <20081128144806.GD22302@bolthole.com> <4930232C.6050901@opencsw.org> Message-ID: <20081128171928.GG9759@bolthole.com> On Fri, Nov 28, 2008 at 05:58:20PM +0100, Sebastian Kayser wrote: > Updated packages are in testing/. As its still the same day, REV and > thus the package file names staid the same. How do you differentiate the > updated package in such a situation? > > Right now pkg-get (and pkgutil) won't let me upgrade the package. add a ".2" on the end of REV=YYYY.DD.MM But I would personally suggest that in this SPECIFIC case, since those packages have not been officially released yet, that you manually pkgrm CSWsynergy, and leave the updated package name without the .2, since you are presumably going to just copy what is in /testing, to newpkgs, when you are done. From james at opencsw.org Fri Nov 28 21:16:39 2008 From: james at opencsw.org (James Lee) Date: Fri, 28 Nov 2008 20:16:39 GMT Subject: [csw-maintainers] BO Buildfarm will be down due to migration In-Reply-To: <1530472E-819B-4A7A-8301-363B1F1768F8@opencsw.org> References: <57E10DB6-126E-4AEC-A222-B2C809D79EBB@opencsw.org> <1530472E-819B-4A7A-8301-363B1F1768F8@opencsw.org> Message-ID: <20081128.20163900.560390367@gyor.oxdrove.co.uk> On 27/11/08, 21:28:12, Dagobert Michelsen wrote regarding Re: [csw-maintainers] BO Buildfarm will be down due to migration: > James: Please repeat your benchmark, and the clock should now be > running in sync too. Rerun with local storage on each machine, this is a fairer test of the machines - although the previous was a fair test of those particular installations. pandora V240 2 x 1500MHz US3i: real 7:09.894 user 0.015 sys 0.033 (showing good repeatability, previous was 7:09.891) build8s T5220 32 x 1165MHz UltraSPARC T2: real 10:18.513 user 39:59.926 sys 8:12.902 Extracting elements of build we see the differences, real times: Task US3i T2 ./configure 59 2:54 gmake -j $NCPU 4:46 3:01 gmake -j 16 - 3:03 gmake -j 8 - 3:30 gmake -j 4 - 6:09 Conclusion, the T2 has more overall power but is unable to utilise it as the overall build process is not parallel enough (disclaimer, in this case...). We should see benefits when several people are working concurrently. James. From james at opencsw.org Fri Nov 28 21:22:59 2008 From: james at opencsw.org (James Lee) Date: Fri, 28 Nov 2008 20:22:59 GMT Subject: [csw-maintainers] Popularity statistics In-Reply-To: <625385e30811241245i7cbf0d00j19d05b68e5bf93fc@mail.gmail.com> References: <492B0558.7050605@opencsw.org> <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com> <492B0A01.6070501@opencsw.org> <20081124122759.Q25010@bolthole.com> <625385e30811241245i7cbf0d00j19d05b68e5bf93fc@mail.gmail.com> Message-ID: <20081128.20225900.3487983687@gyor.oxdrove.co.uk> On 24/11/08, 20:45:27, Peter Bonivart wrote regarding Re: [csw-maintainers] Popularity statistics: > Another simple thing would be to use James' package list to find the > oldest packages (with his Last Changed field). A quick review of those > might find us a lot of packages that need updates but are orphaned. "Last Changed" has been superseded by the REV date in version but for a per maintainer summary look at the "Last activity date" on my maintainer pages. Even this isn't a true test as perhaps a package doesn't need rebuild - I have packages where the upstream source hasn't change in over 10 years (http://wwwthep.physik.uni-mainz.de/~plass/gv)/. Another activity measure is the last login dates, run this on login.bo.opencsw.org if you are interested: last | nawk '!/^reboot/&&!/^wtmp/{print $1}' | sort | uniq James. From sebastian at skayser.de Fri Nov 28 17:57:10 2008 From: sebastian at skayser.de (Sebastian Kayser) Date: Fri, 28 Nov 2008 17:57:10 +0100 Subject: [csw-maintainers] First packaging efforts (synergy 1.3.1 in testing/). Feedback, someone? In-Reply-To: <20081128144806.GD22302@bolthole.com> References: <49300228.20206@opencsw.org> <20081128144806.GD22302@bolthole.com> Message-ID: <493022E6.2030002@skayser.de> Philip Brown wrote: > On Fri, Nov 28, 2008 at 03:37:28PM +0100, Sebastian Kayser wrote: >> >From what i see, the current/ package depends on CSWgcc3rt and its >> binaries are linked against libgcc_s.so.1. Does that mean they were >> compiled using gcc and that's where the size difference comes from? I >> did my builds with Sun Studio cc. > > Yup, most likely > > If you wanted to spend more time on it, you could recompile and tell sun cc > to optimize for size more than speed. It tends to "unroll loops" if you > highly optimize. > And/Or reduce the optimize level to plain "-O", if you are using -fast, and > compare that. Synergy is onlyl a virtual "KVM switch" after all. Ok, i gave it another try with different optimization levels (-xO2, -xO3, without and without -xspace) and i could squeeze the file size for about 150k each (ended up with -xO3 -xspace). Updated packages are in testing/. As its still the same day, REV and thus the package file names staid the same. How do you differentiate the updated package in such a situation? Right now pkg-get (and pkgutil) won't let me upgrade the package. Cheers Sebastian From bwalton at opencsw.org Sat Nov 29 02:25:51 2008 From: bwalton at opencsw.org (Ben Walton) Date: Fri, 28 Nov 2008 20:25:51 -0500 Subject: [csw-maintainers] sgmlcommon + xmlcommon Message-ID: <1227921597-sup-8640@ntdws12.chass.utoronto.ca> Hi All, I've just placed 2 new packages in /home/testing. sgmlcommon and xmlcommon are laying the groundwork for bringing in some docbook packages in the near future. While they don't currently do much, if you'll be interested in the docbook stuff when it arrives, you could give these a peek now to make sure I haven't overlooked any hardcoded paths, etc...[these were converted almost verbatim from the rhel5 sgml-common source rpm, with modifications as required for our fhs instead of the lsb] 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 Sat Nov 29 16:12:28 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sat, 29 Nov 2008 16:12:28 +0100 Subject: [csw-maintainers] Hudson Message-ID: <49315BDC.1060902@opencsw.org> Hi The Hudson installation is getting pretty much properly set up now. I've added a few projects to it, but it seems that we have a bunch of outdated builds so that GAR is not able to fetch the sources. As an example build I've added Ben Waldons latest sgml-xml-common package: http://buildfarm.opencsw.org/hudson/job/sgml-xml-common-trunk-sparc-sun-solaris2.8/4/console I'm waiting on a chmod from Dago to get the i386 builder going, but after that it should work on that platform too. 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. -- Trygve From trygvel at opencsw.org Sat Nov 29 18:16:28 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sat, 29 Nov 2008 18:16:28 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <49315BDC.1060902@opencsw.org> References: <49315BDC.1060902@opencsw.org> Message-ID: <493178EC.8060801@opencsw.org> Trygve Laugst?l wrote: > Hi > > The Hudson installation is getting pretty much properly set up now. I've > added a few projects to it, but it seems that we have a bunch of > outdated builds so that GAR is not able to fetch the sources. > > As an example build I've added Ben Waldons latest sgml-xml-common package: > > http://buildfarm.opencsw.org/hudson/job/sgml-xml-common-trunk-sparc-sun-solaris2.8/4/console > > I'm waiting on a chmod from Dago to get the i386 builder going, but > after that it should work on that platform too. > > 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. I just realized that there used to be a /home/hudson and that work just fine for us. So I made a small script that simply runs bldcat in the two directories so if [1] would be exposed to the public people could start to download the packages right away! $ (cd /home/hudson/repository; find hudson) hudson hudson/i386 hudson/i386/5.8 hudson/i386/5.8/catalog hudson/sparc hudson/sparc/5.8 hudson/sparc/5.8/sgmlcommon-0.6.3,REV=2008.11.29-SunOS5.8-all-CSW.pkg.gz hudson/sparc/5.8/xmlcommon-0.6.3,REV=2008.11.29-SunOS5.8-all-CSW.pkg.gz hudson/sparc/5.8/catalog hudson/sparc/5.8/tomcat4-4.1.37,REV=2008.11.29-SunOS5.8-all-CSW.pkg.gz (I called the repository "hudson" to clearly separate it from the other repositories, but I would like a more generic name, perhaps something like "devel") [1]: nfs:/home/hudson/repository/ -- Trygve From bonivart at opencsw.org Sat Nov 29 18:32:31 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Sat, 29 Nov 2008 18:32:31 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <493178EC.8060801@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> Message-ID: <625385e30811290932y17882a3cs2a63bb21bb2c269f@mail.gmail.com> On Sat, Nov 29, 2008 at 6:16 PM, Trygve Laugst?l wrote: > I just realized that there used to be a /home/hudson and that work just > fine for us. So I made a small script that simply runs bldcat in the two > directories so if [1] would be exposed to the public people could start > to download the packages right away! Cool that you use bldcat to create the catalogs. :-) Thanks to Dagobert it will be faster and better in pkgutil 1.3. Pkgutil will work with your repo now but if you want pkg-get to work as well you need to create the descriptions file the new bldcat produces. You still have more work to do for pkg-get to work but it's a start. You can find the new bldcat here: http://www.bonivart.com/pkgutil/bldcat Now I have to find out what Hudson and Maven is... :-) -- /peter From trygvel at opencsw.org Sat Nov 29 18:44:08 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sat, 29 Nov 2008 18:44:08 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <625385e30811290932y17882a3cs2a63bb21bb2c269f@mail.gmail.com> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <625385e30811290932y17882a3cs2a63bb21bb2c269f@mail.gmail.com> Message-ID: <49317F68.10407@opencsw.org> Peter Bonivart wrote: > On Sat, Nov 29, 2008 at 6:16 PM, Trygve Laugst?l wrote: >> I just realized that there used to be a /home/hudson and that work just >> fine for us. So I made a small script that simply runs bldcat in the two >> directories so if [1] would be exposed to the public people could start >> to download the packages right away! > > Cool that you use bldcat to create the catalogs. :-) Thanks to > Dagobert it will be faster and better in pkgutil 1.3. Pkgutil will > work with your repo now but if you want pkg-get to work as well you > need to create the descriptions file the new bldcat produces. You > still have more work to do for pkg-get to work but it's a start. > > You can find the new bldcat here: http://www.bonivart.com/pkgutil/bldcat So if I just replace the one in /opt/csw/bin I should get a working descriptions file too? > Now I have to find out what Hudson and Maven is... :-) Hehe :) Hudson is a continuous integration engine which polls your SCM (subversion in our case) regularly to find if there are changes and of so starts a build. In addition you can get it to notify you when stuff breaks and lots of other features. Maven is "just" another build tool for Java applications. [1]: http://en.wikipedia.org/wiki/Continuous_integration -- Trygve From trygvel at opencsw.org Sat Nov 29 18:55:24 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sat, 29 Nov 2008 18:55:24 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <49317F68.10407@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <625385e30811290932y17882a3cs2a63bb21bb2c269f@mail.gmail.com> <49317F68.10407@opencsw.org> Message-ID: <4931820C.80404@opencsw.org> Trygve Laugst?l wrote: > Peter Bonivart wrote: >> On Sat, Nov 29, 2008 at 6:16 PM, Trygve Laugst?l wrote: >>> I just realized that there used to be a /home/hudson and that work just >>> fine for us. So I made a small script that simply runs bldcat in the two >>> directories so if [1] would be exposed to the public people could start >>> to download the packages right away! >> Cool that you use bldcat to create the catalogs. :-) Thanks to >> Dagobert it will be faster and better in pkgutil 1.3. Pkgutil will >> work with your repo now but if you want pkg-get to work as well you >> need to create the descriptions file the new bldcat produces. You >> still have more work to do for pkg-get to work but it's a start. >> >> You can find the new bldcat here: http://www.bonivart.com/pkgutil/bldcat > > So if I just replace the one in /opt/csw/bin I should get a working > descriptions file too? And we have a proper descriptions file too! $ find /home/hudson/repository /home/hudson/repository /home/hudson/repository/hudson /home/hudson/repository/hudson/i386 /home/hudson/repository/hudson/i386/5.8 /home/hudson/repository/hudson/i386/5.8/descriptions /home/hudson/repository/hudson/i386/5.8/catalog /home/hudson/repository/hudson/sparc /home/hudson/repository/hudson/sparc/5.8 /home/hudson/repository/hudson/sparc/5.8/asciidoc-8.2.7,REV=2008.11.29-SunOS5.8-all-CSW.pkg.gz /home/hudson/repository/hudson/sparc/5.8/sgmlcommon-0.6.3,REV=2008.11.29-SunOS5.8-all-CSW.pkg.gz /home/hudson/repository/hudson/sparc/5.8/xmlcommon-0.6.3,REV=2008.11.29-SunOS5.8-all-CSW.pkg.gz /home/hudson/repository/hudson/sparc/5.8/descriptions /home/hudson/repository/hudson/sparc/5.8/catalog /home/hudson/repository/hudson/sparc/5.8/tomcat4-4.1.37,REV=2008.11.29-SunOS5.8-all-CSW.pkg.gz [snip] -- Trygve From dam at opencsw.org Sat Nov 29 21:39:42 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 29 Nov 2008 21:39:42 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <625385e30811290932y17882a3cs2a63bb21bb2c269f@mail.gmail.com> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <625385e30811290932y17882a3cs2a63bb21bb2c269f@mail.gmail.com> Message-ID: <7CEBB40F-D798-4DC0-9D38-20E7DCF62D11@opencsw.org> Hi, Am 29.11.2008 um 18:32 schrieb Peter Bonivart: > On Sat, Nov 29, 2008 at 6:16 PM, Trygve Laugst?l > wrote: >> > Cool that you use bldcat to create the catalogs. :-) Thanks to > Dagobert it will be faster and better in pkgutil 1.3. Pkgutil will > work with your repo now but if you want pkg-get to work as well you > need to create the descriptions file the new bldcat produces. Hugh? The version I send you builds both catalog and descriptions file. Do you see a problem with this? Trygve: You can pick up a version which does both from /home/dam/bldcat until this gets integrated. Best regards -- Dago From dam at opencsw.org Sat Nov 29 21:44:45 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 29 Nov 2008 21:44:45 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <7CEBB40F-D798-4DC0-9D38-20E7DCF62D11@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <625385e30811290932y17882a3cs2a63bb21bb2c269f@mail.gmail.com> <7CEBB40F-D798-4DC0-9D38-20E7DCF62D11@opencsw.org> Message-ID: <776863EF-F01F-4C18-8BB9-AD55068D2BFC@opencsw.org> Hi Peter, Am 29.11.2008 um 21:39 schrieb Dagobert Michelsen: > Am 29.11.2008 um 18:32 schrieb Peter Bonivart: >> Cool that you use bldcat to create the catalogs. :-) Thanks to >> Dagobert it will be faster and better in pkgutil 1.3. Pkgutil will >> work with your repo now but if you want pkg-get to work as well you >> need to create the descriptions file the new bldcat produces. > > Hugh? The version I send you builds both catalog and descriptions > file. Do you see a problem with this? Sorry folks, the last sentence didn't got to my mind. After a day of grinding wood I'm pretty much worn out :-P Best regards -- Dago From dam at opencsw.org Sat Nov 29 22:06:18 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 29 Nov 2008 22:06:18 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <493178EC.8060801@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> Message-ID: <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> Hi, 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 About setting up projects: Here is an idea of how to deal with releases in the future. - 'gmake release' checks that everything is committed to the repository and makes a copy to tags/-x.y,REV=a.b.c - Hudson makes packages from tags/* with the revision stamp - The URL and SVN revision are annotated inside the package This makes it possible to exactly reproduce any package and reference the build description precisely - Only packages generated in this way will be accepted for release in the future - This way it will be possible to allow "fast-tracking" of emergency bugfixes as the packages could be delivered and catalog build automatically. The details still need to be worked out of course. - Packages from trunk/ and branches/ are also build by Hudson but are put in another location (continoues integration) (/opencsw/testing/-*?) We still need a solution for Solaris 8 x86 packages containing 64 bit code. Best regards -- Dago From bonivart at opencsw.org Sat Nov 29 22:16:53 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Sat, 29 Nov 2008 22:16:53 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <7CEBB40F-D798-4DC0-9D38-20E7DCF62D11@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <625385e30811290932y17882a3cs2a63bb21bb2c269f@mail.gmail.com> <7CEBB40F-D798-4DC0-9D38-20E7DCF62D11@opencsw.org> Message-ID: <625385e30811291316j78f40334kec56e48eb375e962@mail.gmail.com> On Sat, Nov 29, 2008 at 9:39 PM, Dagobert Michelsen wrote: >> Cool that you use bldcat to create the catalogs. :-) Thanks to >> Dagobert it will be faster and better in pkgutil 1.3. Pkgutil will >> work with your repo now but if you want pkg-get to work as well you >> need to create the descriptions file the new bldcat produces. > > Hugh? The version I send you builds both catalog and descriptions > file. Do you see a problem with this? That's the one I'm talking about. :-) I just assumed Trygve was using bldcat from pkgutil 1.2, that is before your additions. -- /peter From trygvel at opencsw.org Sat Nov 29 23:13:20 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sat, 29 Nov 2008 23:13:20 +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: <4931BE80.9060904@opencsw.org> Dagobert Michelsen wrote: > Hi, > > 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 > > > About setting up projects: Here is an idea of how to deal > with releases in the future. > - 'gmake release' checks that everything is committed to the > repository and makes a copy to tags/-x.y,REV=a.b.c This is most likely very useful and something that we should work on. > - Hudson makes packages from tags/* with the revision stamp This might be a bit more pain than what we gain from it. You would have to create a new job for Hudson to build from a tag which would be used only once. I would rather create a script that 1) checks out the code 2) performs gmake clean package to create the package 3) tags the package 4) copies the pkg.gz to new/ > - The URL and SVN revision are annotated inside the package > This makes it possible to exactly reproduce any package and > reference the build description precisely > - Only packages generated in this way will be accepted for > release in the future > - This way it will be possible to allow "fast-tracking" of > emergency bugfixes as the packages could be delivered > and catalog build automatically. The details still need > to be worked out of course. > - Packages from trunk/ and branches/ are also build by Hudson > but are put in another location (continoues integration) > (/opencsw/testing/-*?) This is doable, but I'm not sure if it is worth creating branches for stuff. If you need to maintain two versions concurrently (like you might want to for stuff like apache) it might be as easy to create two directories with their own trunk (like apache/trunk and apache2/trunk). > We still need a solution for Solaris 8 x86 packages containing > 64 bit code. I think having 32 and 64 bit packages is the best, perhaps with some clever logic in pkg-get to fetch the foo_64 package for the foo package. The 64 bit package would have to depend on the 32 bit package. This is definitely a useful subject to talk about in Z?rich over a beer. -- Trygve From pfelecan at opencsw.org Sun Nov 30 11:00:17 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Sun, 30 Nov 2008 11:00:17 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> (Dagobert Michelsen's message of "Sat\, 29 Nov 2008 22\:06\:18 +0100") References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> Message-ID: Dagobert Michelsen writes: > - Only packages generated in this way will be accepted for > release in the future Can you elaborate this please? -- Peter From pfelecan at opencsw.org Sun Nov 30 16:27:18 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Sun, 30 Nov 2008 16:27:18 +0100 Subject: [csw-maintainers] request for CSWtetex installation Message-ID: Is there somebody having the rights to install the CSWtetex package on the build systems? I requested its installation on the buildfarm list but it's Sunday... A day when I can work on building packages... -- Peter From phil at bolthole.com Sun Nov 30 16:54:00 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 30 Nov 2008 07:54:00 -0800 Subject: [csw-maintainers] request for CSWtetex installation In-Reply-To: References: Message-ID: <20081130155400.GA90990@bolthole.com> On Sun, Nov 30, 2008 at 04:27:18PM +0100, Peter FELECAN wrote: > Is there somebody having the rights to install the CSWtetex package on > the build systems? I requested its installation on the buildfarm list > but it's Sunday... A day when I can work on building packages... > -- anyone besides Dagobert have perms to do it? I dont. From phil at bolthole.com Sun Nov 30 17:08:45 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 30 Nov 2008 08:08:45 -0800 Subject: [csw-maintainers] Hudson In-Reply-To: <4931BE80.9060904@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> <4931BE80.9060904@opencsw.org> Message-ID: <20081130160845.GB90990@bolthole.com> On Sat, Nov 29, 2008 at 11:13:20PM +0100, Trygve Laugst?l wrote: > I think having 32 and 64 bit packages is the best, perhaps with some > clever logic in pkg-get to fetch the foo_64 package for the foo package. > The 64 bit package would have to depend on the 32 bit package. This is > definitely a useful subject to talk about in Z?rich over a beer. the trouble is, sometimes you want the 32bit package,a nd sometimes, you want the 64bit package. pkg-get cant read your mind :-} (32bit for speed, 64bit for data space. except for amd64, apparently. then maybe the choice is 64bit for speed, 32bit for conservation of memory) From dam at opencsw.org Sun Nov 30 19:57:30 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 30 Nov 2008 19:57:30 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <4931BE80.9060904@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> <4931BE80.9060904@opencsw.org> Message-ID: <08E11B9D-BFB6-4143-BA6C-43DBC5A4BAA8@opencsw.org> Hi Trygve, Am 29.11.2008 um 23:13 schrieb Trygve Laugst?l: >> - Packages from trunk/ and branches/ are also build by Hudson >> but are put in another location (continoues integration) >> (/opencsw/testing/-*?) > > This is doable, but I'm not sure if it is worth creating branches for > stuff. If you need to maintain two versions concurrently (like you > might > want to for stuff like apache) it might be as easy to create two > directories with their own trunk (like apache/trunk and apache2/ > trunk). It is not for two concurrent versions, more in case of a maintenance when the production version ("stable") is kept in one branch and the development version ("current") in another one. >> We still need a solution for Solaris 8 x86 packages containing >> 64 bit code. > > I think having 32 and 64 bit packages is the best, perhaps with some > clever logic in pkg-get to fetch the foo_64 package for the foo > package. > The 64 bit package would have to depend on the 32 bit package. This is > definitely a useful subject to talk about in Z?rich over a beer. Yes. 32/64 is a tough one, especially on x86. Best regards -- Dago From dam at opencsw.org Sun Nov 30 20:21:37 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 30 Nov 2008 20:21:37 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> Message-ID: <6973508A-DB45-41A9-B5CB-C89EC06F698F@opencsw.org> Hi Peter, Am 30.11.2008 um 11:00 schrieb Peter FELECAN: > Dagobert Michelsen writes: > >> - Only packages generated in this way will be accepted for >> release in the future > > Can you elaborate this please? In the distant future packages to be released will be build in a very defined fashion: Make the manifest, commit it to the repository and let the farm build a distributable package. Theoretically a maintainer could mess around with a package, hand-compile something, let GAR assemble it and than release something unreproducable. But don't worry. This won't come tomorrow. And even not the day after that ;-) It is more a long-term goal. Best regards -- Dago From dam at opencsw.org Sun Nov 30 20:24:10 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 30 Nov 2008 20:24:10 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <20081130160845.GB90990@bolthole.com> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> <4931BE80.9060904@opencsw.org> <20081130160845.GB90990@bolthole.com> Message-ID: Hi Phil, Am 30.11.2008 um 17:08 schrieb Philip Brown: > On Sat, Nov 29, 2008 at 11:13:20PM +0100, Trygve Laugst?l wrote: >> I think having 32 and 64 bit packages is the best, perhaps with some >> clever logic in pkg-get to fetch the foo_64 package for the foo >> package. >> The 64 bit package would have to depend on the 32 bit package. This >> is >> definitely a useful subject to talk about in Z?rich over a beer. > > the trouble is, sometimes you want the 32bit package,a nd sometimes, > you > want the 64bit package. pkg-get cant read your mind :-} > > (32bit for speed, 64bit for data space. except for amd64, apparently. > then maybe the choice is 64bit for speed, 32bit for conservation of > memory) That is not the problem. The problem is, that Hudson can't build a combined package for Solaris 8 x86 with 64 bit amd64 stuff in it. We *may* work around this at some point in time but a discussion which path to follow is welcome. Integration in one package as it is done now is certainly a solution, but it is still only one possible solution among others which I would like to have discussed. The result may very well be that we keep it the way it is, but with Hudson and GAR v2 some preliminaries have changed which may lead to another direction. Best regards -- Dago From dam at opencsw.org Sun Nov 30 20:37:03 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 30 Nov 2008 20:37:03 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081128143415.GB22302@bolthole.com> References: <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> <5F994B04-687B-4AC3-91AE-DAAE62F4716B@opencsw.org> <20081117172408.D39788@bolthole.com> <4922660D.9070203@opencsw.org> <4CA4F900-6D7D-49AD-A072-7D15E7A90AB3@opencsw.org> <20081128143415.GB22302@bolthole.com> Message-ID: Hi Phil, Am 28.11.2008 um 15:34 schrieb Philip Brown: > Sounds good to me. > > Just one word of warning... > > On Fri, Nov 28, 2008 at 01:38:29PM +0100, Dagobert Michelsen wrote: >> When the permit from Sun arrives I'll give the package >> a final shot. > > we may be waiting for a very LOOOOONG time on that. > even when sun is 100% favourable to doing something, getting legal > approval > for something seems to take a minimum of 3 months :-( Maybe, but if I never ask I never get an answer ;-) Best regards -- Dago From ihsan at opencsw.org Sat Nov 1 00:21:41 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Sat, 01 Nov 2008 00:21:41 +0100 Subject: [csw-maintainers] new build sparc: zooommm.... In-Reply-To: <20081031125610.Q95235@bolthole.com> References: <20081031125610.Q95235@bolthole.com> Message-ID: <490B9305.1040207@opencsw.org> Am 31.10.2008 20:56 Uhr, Philip Brown schrieb: > It's a direct-access box, so whoever handles DNS, could put an entry for it. > I'm thinking sparc8s.go.opencsw.org perhaps? That's me. :-) > ("go" for "gore", like "bo" was for "baltic online". I dunno) build8s.go.opencsw.org points now to 157.204.22.39. Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From dam at opencsw.org Sat Nov 1 09:35:26 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 1 Nov 2008 09:35:26 +0100 Subject: [csw-maintainers] new build sparc: zooommm.... In-Reply-To: <20081031143556.V95235@bolthole.com> References: <20081031125610.Q95235@bolthole.com> <1557267B-888A-4D97-8C70-2C7DF6839BFF@opencsw.org> <490B7553.7030602@opencsw.org> <7DE89681-8B96-486F-94A7-3D16066AD67E@opencsw.org> <20081031143556.V95235@bolthole.com> Message-ID: <74ADF476-F62F-4497-A22F-737E1FAA7F25@opencsw.org> Hi, Am 31.10.2008 um 22:35 schrieb Philip Brown: > On Fri, Oct 31, 2008 at 10:24:45PM +0100, Dagobert Michelsen wrote: >>> If anyone has Solaris 8 x86 ISOs it should be possible to set that >>> up in >>> a VMWare instance on any machine. >> >> Unfortunately not, as ESX emulates only SCSI busses and there >> is no driver for it in Solaris 8 x86. > > But perhaps there is a need for a solaris 8 driver for the *specific* > scsi bus controller ESX provides. That's what I meant. It was late yesterday :-P > There certainly seem to be lots of web pages complaining that > solaris 8 > does not run under ESX. Am 31.10.2008 um 23:30 schrieb Trygve Laugst?l: >> Unfortunately not, as ESX emulates only SCSI busses and there >> is no driver for it in Solaris 8 x86. If you have a solution >> for this I'd virtualize it immediately. > > The latest release actually support Solaris 8. Did you manage to run Solaris 8 x86 under VMware ESX 3.0.2 or 3.5? If yes, I would like to know what SCSI driver you used. > As you say, though, probably better to run under solaris 10 if that is > an option. That would only help 50% as library packages for 32 and 64 bit must be compiled under Solaris 8 and 10 - we must have both in one farm or you can't build lots of packages. Best regards -- Dago From glaw at opencsw.org Sat Nov 1 11:33:38 2008 From: glaw at opencsw.org (Gary Law) Date: Sat, 1 Nov 2008 10:33:38 +0000 Subject: [csw-maintainers] Topics for IRL In-Reply-To: <343A2AE3-DFC1-4B14-911F-67161138B3B4@opencsw.org> References: <343A2AE3-DFC1-4B14-911F-67161138B3B4@opencsw.org> Message-ID: 2008/10/31 Dagobert Michelsen > > > * **Source**. > (*) The project should formally adopt GAR for Sol 9 and 10 builds and make use of GAR mandatory for all packages. Future Solaris packaging standards might mean a switch to pkgbuild or something else entirely. Incidentally, not all my packages are in GAR and I don't like it as a tool, however, maintainers having private scripts to build stuff is untransparent and makes taking on the maintenance of an existing package very difficult in some cases. > * **Key**. > (*) The Key should be owned by all of and only the board members. > > * **Board**. > For me this is the most important point. The > nomination/election is one of the keys on the meeting. (*) Can maintainers who don't attend vote? > > * **Release Process**. > You might want to take a look at Hudson, which is a nice Continuous Integration server that I've used for automated builds in the past. > > * **Distributed**. > > I don't know if distribution is really that good +1 > . ... It may be sufficient to replicate the server > backups to different people so the infrastructure can be > rebuild quickly if anything happens. (*) The board members should maintain the infrastructure (delegating to corporations or people as they see fit). Everything should be replicated in two places, ideally I guess one in Europe and one in North America. LDAP, SVN, DNS, web servers, wiki servers... all of these things can be made to work in a fully redundant fashion across a WAN. NFS might be a struggle though. (*) I've got one more, and this is probably going to be a little controversial... we should move out of /opt/csw and into /opt/opencsw. Blastwave Inc is still distributing into /opt/csw and the scope for end user confusion and incompatible software releases is huge. Although this sounds like a lot of work, if everything is in GAR, and everything needs to be rebuilt for Sol 9 in the next six months, it's really not a lot of extra work. I've got big reservations about maintaining stuff through opencsw that installs into /opt/csw. -- Gary Law glaw at opencsw.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From dam at opencsw.org Sat Nov 1 11:54:40 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 1 Nov 2008 11:54:40 +0100 Subject: [csw-maintainers] Topics for IRL In-Reply-To: References: <343A2AE3-DFC1-4B14-911F-67161138B3B4@opencsw.org> Message-ID: <4DE07271-5CBD-4022-B736-9248070EB132@opencsw.org> Hi Gary, Am 01.11.2008 um 11:33 schrieb Gary Law: > 2008/10/31 Dagobert Michelsen > > > * **Source**. > > (*) The project should formally adopt GAR for Sol 9 and 10 builds > and make use of GAR mandatory for all packages. That would be good, yes. However, we have quite a mount of existing packages which are not in GAR and which are currently orphaned. Would you drop them? > Future Solaris packaging standards might mean a switch to pkgbuild > or something else entirely. It will become mandatory when Solaris 10 support is dropped. Until then, we have to produce System V packages, and that will be for quite some years from now. > Incidentally, not all my packages are in GAR and I don't like it as > a tool, however, maintainers having private scripts to build stuff > is untransparent and makes taking on the maintenance of an existing > package very difficult in some cases. If I can help you moving your packages to GAR let me know. Currently I am preparing some more docs and a presentation with an introduction to GAR to be held during IRL. > > * **Key**. > > (*) The Key should be owned by all of and only the board members. That could be a solution and should be discussed during the meeting. > > * **Board**. > For me this is the most important point. The > nomination/election is one of the keys on the meeting. > > (*) Can maintainers who don't attend vote? Not for the board at this time. If I got Ihsan correctly, it is mandatory in Swiss law for the incorporated society to meet in person at least once. After the founding, the board can accept members which have a right to vote. After that "remote-elections" should be possible. > > * **Release Process**. > > You might want to take a look at Hudson, which is a nice Continuous > Integration server that I've used for automated builds in the past. Like this :-) http://buildfarm.opencsw.org/hudson/ It will become fully functional when a package can be checked out individually (without checking out the whole tree). Trygve set this up, thanks! > > * **Distributed**. > > I don't know if distribution is really that good > > +1 > > . ... It may be sufficient to replicate the server > backups to different people so the infrastructure can be > rebuild quickly if anything happens. > > (*) The board members should maintain the infrastructure > (delegating to corporations or people as they see fit). Everything > should be replicated in two places, ideally I guess one in Europe > and one in North America. LDAP, SVN, DNS, web servers, wiki > servers... all of these things can be made to work in a fully > redundant fashion across a WAN. NFS might be a struggle though. > > (*) I've got one more, and this is probably going to be a little > controversial... we should move out of /opt/csw and into /opt/ > opencsw. Blastwave Inc is still distributing into /opt/csw and the > scope for end user confusion and incompatible software releases is > huge. Although this sounds like a lot of work, if everything is in > GAR, and everything needs to be rebuilt for Sol 9 in the next six > months, it's really not a lot of extra work. I've got big > reservations about maintaining stuff through opencsw that installs > into /opt/csw. Difficult. *If* we change the prefix, then there must be a converter for installation to go from csw/ to opencsw/, but personally I would like to postpone that until we see how each project performs. Discussion welcome. Best regards -- Dago -------------- next part -------------- An HTML attachment was scrubbed... URL: From garylaw at garylaw.net Sat Nov 1 13:17:42 2008 From: garylaw at garylaw.net (Gary Law) Date: Sat, 1 Nov 2008 12:17:42 +0000 Subject: [csw-maintainers] Topics for IRL In-Reply-To: <4DE07271-5CBD-4022-B736-9248070EB132@opencsw.org> References: <343A2AE3-DFC1-4B14-911F-67161138B3B4@opencsw.org> <4DE07271-5CBD-4022-B736-9248070EB132@opencsw.org> Message-ID: Hi Dago 2008/11/1 Dagobert Michelsen > Hi Gary, > Am 01.11.2008 um 11:33 schrieb Gary Law: > > 2008/10/31 Dagobert Michelsen > >> >> > * **Source**. >> > > (*) The project should formally adopt GAR for Sol 9 and 10 builds and make > use of GAR mandatory for all packages. > > > That would be good, yes. However, we have quite a mount of existing > packages which are not in GAR and which are currently orphaned. Would > you drop them? > Not immediately. I believe the Solaris 8 end of support is March 2009, so I'd make that the target date for a new system. Everything built on Solaris 9, out of GAR (and with a new install path -- see below). > > If I can help you moving your packages to GAR let me know. > Currently I am preparing some more docs and a presentation > with an introduction to GAR to be held during IRL. > Thanks. I have an absolute pig of a package to deal with. > (*) Can maintainers who don't attend vote? > > Not for the board at this time. If I got Ihsan correctly, > it is mandatory in Swiss law for the incorporated society > to meet in person at least once. After the founding, the > board can accept members which have a right to vote. > After that "remote-elections" should be possible. > Great. Please hold an all-maintainers election ASAP after incorporation. I don't suppose it would be likely to change the composition of the board, but would give maintainers a sense of ownership. > > > * **Release Process**. > > You might want to take a look at Hudson, which is a nice Continuous > Integration server that I've used for automated builds in the past. > > > Like this :-) > http://buildfarm.opencsw.org/hudson/ > Oh fantastic. If you dive deep enough through the links eventually absolute links to: http://hudson:8070 start appearing, which don't work. Still, this is completely the right way to go IMHO. I'll try and get my packages in there. > > > (*) I've got one more, and this is probably going to be a little > controversial... we should move out of /opt/csw and into /opt/opencsw. > Blastwave Inc is still distributing into /opt/csw and the scope for end user > confusion and incompatible software releases is huge. Although this sounds > like a lot of work, if everything is in GAR, and everything needs to be > rebuilt for Sol 9 in the next six months, it's really not a lot of extra > work. I've got big reservations about maintaining stuff through opencsw that > installs into /opt/csw. > > > Difficult. *If* we change the prefix, then there must be a > converter for installation to go from csw/ to opencsw/, but > personally I would like to postpone that until we see how > each project performs. Discussion welcome. > > Like changing to GAR only, it would be impossible overnight. But set a target date six months out, and I think it's realistic to get everything rebuilt, out of version controlled repo, off the new minimum standard (Solaris 9). We might loose a few packages or maintainers along the way, but end up in a much better place for running and maintaining the project long term. Also, what's the alternative? Having two projects targeting the same install path? That is not sustainable going forward and the project's credibility will suffer. Gary -- Gary Law glaw at opencsw.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From dam at opencsw.org Sat Nov 1 13:39:04 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 1 Nov 2008 13:39:04 +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: Hi Gary, Am 01.11.2008 um 13:17 schrieb Gary Law: >> > * **Release Process**. >> >> You might want to take a look at Hudson, which is a nice >> Continuous Integration server that I've used for automated builds >> in the past. > > Like this :-) > http://buildfarm.opencsw.org/hudson/ > > Oh fantastic. If you dive deep enough through the links eventually > absolute links to: > http://hudson:8070 > start appearing, which don't work. Oops. Trygve, any clues how to fix this? > Still, this is completely the right way to go IMHO. I'll try and > get my packages in there. This will be done automatically once we have single package checkout in GAR. Auto-build on commit :-) > >> (*) I've got one more, and this is probably going to be a little >> controversial... we should move out of /opt/csw and into /opt/ >> opencsw. Blastwave Inc is still distributing into /opt/csw and the >> scope for end user confusion and incompatible software releases is >> huge. Although this sounds like a lot of work, if everything is in >> GAR, and everything needs to be rebuilt for Sol 9 in the next six >> months, it's really not a lot of extra work. I've got big >> reservations about maintaining stuff through opencsw that installs >> into /opt/csw. > > Difficult. *If* we change the prefix, then there must be a > converter for installation to go from csw/ to opencsw/, but > personally I would like to postpone that until we see how > each project performs. Discussion welcome. > > > Like changing to GAR only, it would be impossible overnight. But > set a target date six months out, and I think it's realistic to get > everything rebuilt, out of version controlled repo, off the new > minimum standard (Solaris 9). We might loose a few packages or > maintainers along the way, but end up in a much better place for > running and maintaining the project long term. That would imply to also change the package prefix CSW to something else. I completely agree that it is a Bad Thing(TM) to have two projects work on the same prefix. However, the "inheritor" of CSW (Phil, after Alan DuBoff) is at OpenCSW and most of the maintainers too. I don't know how they feel about changing the prefix. Personally, I think OpenCSW has the moral right to stick to /opt/csw, but that is just my opinion and I would accept a majority decision on this of course. Fellow maintainers, what do you think? > Also, what's the alternative? Having two projects targeting the > same install path? That is not sustainable going forward and the > project's credibility will suffer. The question is: will the maintainers here will accept leaving the prefix to Blastwave and start with a new one. Apart from that it would be cool to allow customized package trees with different suffixes (e. g. like optimized trees for T1/T2). However, that would impose quite an extra amount for package maintainers (not for all, but there are nasty ones). Best regards -- Dago -------------- next part -------------- An HTML attachment was scrubbed... URL: From garylaw at garylaw.net Sat Nov 1 14:38:42 2008 From: garylaw at garylaw.net (Gary Law) Date: Sat, 1 Nov 2008 13:38:42 +0000 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: 2008/11/1 Dagobert Michelsen > > Still, this is completely the right way to go IMHO. I'll try and get my > packages in there. > > > This will be done automatically once we have single package > checkout in GAR. Auto-build on commit :-) > Yay! Exactly the way it should be. :) > > Personally, I think OpenCSW has the > moral right to stick to /opt/csw > Having the moral right is all well and good, but it is not pragmatic to use /opt/csw indefinitely. > The question is: will the maintainers here will accept leaving the > prefix to Blastwave and start with a new one. > I could be wrong, but I guess most maintainers want it somewhere in /opt that no-one else is using. > > Apart from that it would be cool to allow customized package trees > with different suffixes (e. g. like optimized trees for T1/T2). > However, that would impose quite an extra amount for package > maintainers (not for all, but there are nasty ones). > If we get everything in GAR, and automated builds, lots of stuff becomes loads easier. Gary -- Gary Law glaw at opencsw.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From bonivart at opencsw.org Sat Nov 1 15:13:53 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Sat, 1 Nov 2008 15:13:53 +0100 Subject: [csw-maintainers] Want to test an alternative to pkg-get? In-Reply-To: References: <625385e30809190604x4c76f8fdsb380ccc9fb00165f@mail.gmail.com> Message-ID: <625385e30811010713u5bfe39cdl761fc488a034c19@mail.gmail.com> This is really weird, I just got this mail and I see that you sent it September 23rd, according to the headers it's been sitting on an opencsw mail server until today. Maybe your gmail account wasn't allowed to post to the list and it has been stuck waiting for approval. I use gmail too but I've set it up to send as my opencsw account. When I forget to change my from address the same thing happens. On Tue, Sep 23, 2008 at 10:57 AM, Gary Law wrote: > (*) the pkgtool installer wants my /opt to be root:bin, not root:sys Version 1.1 has a trimmed prototype that doesn't include /etc/opt, /opt and /var/opt to minimize risk of modifying the attributes of already existing directories. > (*) there's no mention of the configuration file in the man page. How do I > set which mirrors to use? ibiblio seems to be the default mirror which is > hard coded into the tool, and the pkgtool.conf file is referenced by the > code too, but it's format is undocumented. AFAIK ibiblio is mirroring > packages off of Blastwave Inc., not opencsw. I'll look into improving the man page. Please look at http://wiki.opencsw.org/pkgutil for more info, also in 1.1 the conf-file is better documented. I think the mirror issue has finally been settled, ibiblio as an example has chosen to mirror blastwave as blastwave and opencsw as opencsw, the old csw path has been removed. The path should be correct in 1.1. > (*) My gut feel, completely untested, is this is faster than pkg-get. I have done some simple tests and it's usually faster than pkg-get but some may think pkg-get is faster because it gets busy right away downloading and extracting packages so it can find dependencies. Pkgutil may seem slower at the beginning when it's presenting new, updated and current packages but to me that info is really valuable. I haven't optimized the algorithms either yet so there may be better speed in the future. Right now I'm mostly working on features. > (*) how is the gpg signing turned on/off? It should be off by default, you have to turn it on by setting that option (use_gpg=true) in pkgutil.conf. If pkgutil doesn't find gpg support it will tell you which package you need to install. > (*) Functionally, works perfectly during my limited tesing. Excellent! > (*) Love the "I'm going to do this now" option. You mean the --nomod option? I've used it a lot during testing. :-) -- /peter From phil at bolthole.com Sat Nov 1 19:32:17 2008 From: phil at bolthole.com (Philip Brown) Date: Sat, 1 Nov 2008 11:32:17 -0700 Subject: [csw-maintainers] OpenCSW Prefix In-Reply-To: ; from dam@opencsw.org on Sat, Nov 01, 2008 at 01:39:04PM +0100 References: <343A2AE3-DFC1-4B14-911F-67161138B3B4@opencsw.org> <4DE07271-5CBD-4022-B736-9248070EB132@opencsw.org> Message-ID: <20081101113217.A82853@bolthole.com> On Sat, Nov 01, 2008 at 01:39:04PM +0100, Dagobert Michelsen wrote: > That would imply to also change the package prefix CSW to something > else. > I completely agree that it is a Bad Thing(TM) to have two projects work > on the same prefix. However, the "inheritor" of CSW (Phil, after Alan > DuBoff) is at OpenCSW and most of the maintainers too. I don't know how > they feel about changing the prefix. Personally, I think OpenCSW has the > moral right to stick to /opt/csw, but that is just my opinion and I > would accept a majority decision on this of course. > > Fellow maintainers, what do you think? Additionally, someone once said that blastwave maintainers (a few months ago) were supposedly already planning to move THEIR stuff to stop using "CSW". I'm guessing that Dennis decided against that, because he likes to claim he owns everything. But he does NOT own CSW. For us to change, undermines us, in my opinion. From ihsan at opencsw.org Sat Nov 1 21:30:48 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Sat, 01 Nov 2008 21:30:48 +0100 Subject: [csw-maintainers] Want to test an alternative to pkg-get? In-Reply-To: <625385e30811010713u5bfe39cdl761fc488a034c19@mail.gmail.com> References: <625385e30809190604x4c76f8fdsb380ccc9fb00165f@mail.gmail.com> <625385e30811010713u5bfe39cdl761fc488a034c19@mail.gmail.com> Message-ID: <490CBC78.9080300@opencsw.org> Am 1.11.2008 15:13 Uhr, Peter Bonivart schrieb: > This is really weird, I just got this mail and I see that you sent it > September 23rd, according to the headers it's been sitting on an > opencsw mail server until today. Maybe your gmail account wasn't > allowed to post to the list and it has been stuck waiting for > approval. I use gmail too but I've set it up to send as my opencsw > account. When I forget to change my from address the same thing > happens. You have to use your @opencsw.org address to post to this list and his mail was hold by the malinglist software. Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From glaw at opencsw.org Sat Nov 1 21:37:44 2008 From: glaw at opencsw.org (Gary Law) Date: Sat, 1 Nov 2008 20:37:44 +0000 Subject: [csw-maintainers] OpenCSW Prefix In-Reply-To: <20081101113217.A82853@bolthole.com> References: <343A2AE3-DFC1-4B14-911F-67161138B3B4@opencsw.org> <4DE07271-5CBD-4022-B736-9248070EB132@opencsw.org> <20081101113217.A82853@bolthole.com> Message-ID: Hi Phil 2008/11/1 Philip Brown > > > Fellow maintainers, what do you think? > > Additionally, someone once said that blastwave maintainers (a few months > ago) were supposedly already planning to move THEIR stuff to stop using > "CSW". Were it to happen, of course, that would be great. But there is no evidence of this actually happening. > I'm guessing that Dennis decided against that, because he likes to claim he > owns everything. > But he does NOT own CSW. > > > For us to change, undermines us, in my opinion. > I'm not sure in what way a change to a directory path undermines opencsw. I am sure that if both organisations plough on regardless using /opt/csw it will undermine both parties -- it clearly isn't in the best interests of end users. And now I come to think of it, the dependency declarations are also going to be impossible to reliably resolve if two organisations produce software called CSWfoo, CSWbar... Gary -- Gary Law -------------- next part -------------- An HTML attachment was scrubbed... URL: From phil at bolthole.com Sat Nov 1 22:05:42 2008 From: phil at bolthole.com (Philip Brown) Date: Sat, 1 Nov 2008 14:05:42 -0700 Subject: [csw-maintainers] OpenCSW Prefix In-Reply-To: ; from glaw@opencsw.org on Sat, Nov 01, 2008 at 08:37:44PM +0000 References: <343A2AE3-DFC1-4B14-911F-67161138B3B4@opencsw.org> <4DE07271-5CBD-4022-B736-9248070EB132@opencsw.org> <20081101113217.A82853@bolthole.com> Message-ID: <20081101140542.C82853@bolthole.com> On Sat, Nov 01, 2008 at 08:37:44PM +0000, Gary Law wrote: > I am sure that if both organisations plough on regardless using /opt/csw it > will undermine both parties -- it clearly isn't in the best interests of end > users. > > And now I come to think of it, the dependency declarations are also going to > be impossible to reliably resolve if two organisations produce software > called CSWfoo, CSWbar... what is the problem? its not like someone would want to use both sets of packages From glaw at opencsw.org Sat Nov 1 22:52:58 2008 From: glaw at opencsw.org (Gary Law) Date: Sat, 1 Nov 2008 21:52:58 +0000 Subject: [csw-maintainers] OpenCSW Prefix In-Reply-To: <20081101140542.C82853@bolthole.com> References: <343A2AE3-DFC1-4B14-911F-67161138B3B4@opencsw.org> <4DE07271-5CBD-4022-B736-9248070EB132@opencsw.org> <20081101113217.A82853@bolthole.com> <20081101140542.C82853@bolthole.com> Message-ID: 2008/11/1 Philip Brown > > > > And now I come to think of it, the dependency declarations are also going > to > > be impossible to reliably resolve if two organisations produce software > > called CSWfoo, CSWbar... > > what is the problem? > its not like someone would want to use both sets of packages > It's highly likely someone will intentionally want to use both. There are already packages in one and not the other. And versions are different for many things. Equally concerning is that people will accidentally use both. If they change mirror to the wrong upstream things won't work as they should. Users will become annoyed when they find out why, and go back to downloading by hand from Sunfreeware. The whole point of using things like /opt/$NAME for directories and prefixing the package name is to prevent namespace clashes ... I stand by my opinion that both Blastwave and opencsw are going to look very, very foolish if they both distribute into /opt/csw. -- Gary Law glaw at opencsw.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From ihsan at opencsw.org Sun Nov 2 13:44:58 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Sun, 02 Nov 2008 13:44:58 +0100 Subject: [csw-maintainers] IRL Meeting - new date Message-ID: <490DA0CA.1020008@opencsw.org> Hello, I've been talking with Phil about the IRL meeting and for him it would be possible, to attend to the IRL meeting, if it's taking place on 5/6/7 December. As far Phil would come from far way (it's a 12 hours flight for him), I would like to ask, if it's possible for you guys to postpone this date. Please let me know, so we can plan something for this date. Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From ihsan at opencsw.org Sun Nov 2 14:38:47 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Sun, 02 Nov 2008 14:38:47 +0100 Subject: [csw-maintainers] OpenCSW maintainers list now public Message-ID: <490DAD67.60203@opencsw.org> Hello, As already mentioned, all posts after 1st November are public! The mailing list is announced on https://lists.opencsw.org/mailman/listinfo and the archive is readable on http://lists.opencsw.org/pipermail/maintainers/ . Only maintainers can post to the list. Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From trygvel at opencsw.org Sun Nov 2 15:10:39 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sun, 02 Nov 2008 15:10:39 +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: <490DB4DF.1040802@opencsw.org> Dagobert Michelsen wrote: > Hi Gary, > > Am 01.11.2008 um 13:17 schrieb Gary Law: >> >>> > * **Release Process**. >>> >>> You might want to take a look at Hudson, which is a nice >>> Continuous Integration server that I've used for automated builds >>> in the past. >> >> Like this :-) >> http://buildfarm.opencsw.org/hudson/ >> >> >> Oh fantastic. If you dive deep enough through the links eventually >> absolute links to: >> http://hudson:8070 >> start appearing, which don't work. > > Oops. Trygve, any clues how to fix this? Odd. Where did you find that link? >> Still, this is completely the right way to go IMHO. I'll try and get >> my packages in there. > > This will be done automatically once we have single package > checkout in GAR. Auto-build on commit :-) > >> >>> (*) I've got one more, and this is probably going to be a little >>> controversial... we should move out of /opt/csw and into >>> /opt/opencsw. Blastwave Inc is still distributing into /opt/csw >>> and the scope for end user confusion and incompatible software >>> releases is huge. Although this sounds like a lot of work, if >>> everything is in GAR, and everything needs to be rebuilt for Sol >>> 9 in the next six months, it's really not a lot of extra work. >>> I've got big reservations about maintaining stuff through opencsw >>> that installs into /opt/csw. >> >> Difficult. *If* we change the prefix, then there must be a >> converter for installation to go from csw/ to opencsw/, but >> personally I would like to postpone that until we see how >> each project performs. Discussion welcome. >> >> >> Like changing to GAR only, it would be impossible overnight. But set a >> target date six months out, and I think it's realistic to get >> everything rebuilt, out of version controlled repo, off the new >> minimum standard (Solaris 9). We might loose a few packages or >> maintainers along the way, but end up in a much better place for >> running and maintaining the project long term. > > That would imply to also change the package prefix CSW to something else. > I completely agree that it is a Bad Thing(TM) to have two projects work > on the same prefix. However, the "inheritor" of CSW (Phil, after Alan > DuBoff) is at OpenCSW and most of the maintainers too. I don't know how > they feel about changing the prefix. Personally, I think OpenCSW has the > moral right to stick to /opt/csw, but that is just my opinion and I would > accept a majority decision on this of course. > > Fellow maintainers, what do you think? > >> Also, what's the alternative? Having two projects targeting the same >> install path? That is not sustainable going forward and the project's >> credibility will suffer. > > The question is: will the maintainers here will accept leaving the > prefix to Blastwave and start with a new one. > > Apart from that it would be cool to allow customized package trees > with different suffixes (e. g. like optimized trees for T1/T2). > However, that would impose quite an extra amount for package > maintainers (not for all, but there are nasty ones). I don't care what we do as all the packages should be rebuilt for Solaris 9+ anyway, but the only thing that matters is what our consumers need. If we are to move we really need to document how to transition from the Original Blastwave packages to the new OpenCSW packages. Perhaps it is an alternative to use /opt/opencsw for the binary root and use /etc/opt/csw for configuration files? -- Trygve From trygvel at opencsw.org Sun Nov 2 15:13:30 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sun, 02 Nov 2008 15:13:30 +0100 Subject: [csw-maintainers] IRL Meeting - new date In-Reply-To: <490DA0CA.1020008@opencsw.org> References: <490DA0CA.1020008@opencsw.org> Message-ID: <490DB58A.6090000@opencsw.org> Ihsan Dogan wrote: > Hello, > > I've been talking with Phil about the IRL meeting and for him it would > be possible, to attend to the IRL meeting, if it's taking place on 5/6/7 > December. > > As far Phil would come from far way (it's a 12 hours flight for him), I > would like to ask, if it's possible for you guys to postpone this date. > > Please let me know, so we can plan something for this date. Works for me. -- Trygve From Murray.Jensen at csiro.au Sun Nov 2 15:19:14 2008 From: Murray.Jensen at csiro.au (Murray.Jensen at csiro.au) Date: Mon, 3 Nov 2008 01:19:14 +1100 Subject: [csw-maintainers] new packages pymxbase and pypgsql for testing Message-ID: <9085.1225635554@gerd> Unfortunately I don't have access to the testing area so they are sitting in my home directory on www.opencsw.org (/home/mjensen) ... 7ca5cc173202e77c55d0f795b932e5eb pymxbase-3.1.1,REV=2008.10.31-SunOS5.8-i386-CSW.pkg.gz c931403b91add50a0032fee98a03fcd6 pymxbase-3.1.1,REV=2008.10.31-SunOS5.8-sparc-CSW.pkg.gz 81aae9076588e4c1e70aec4e8e4d8c10 pypgsql-2.5.1,REV=2008.11.01-SunOS5.8-i386-CSW.pkg.gz 5c338d5a2dcb414296eff3e2c1fcd53a pypgsql-2.5.1,REV=2008.11.01-SunOS5.8-sparc-CSW.pkg.gz If some kind soul could put them into testing I'd appreciate it. Cheers! Murray... PS: I am not maintainer for these, but I noticed a conflict when using a python script (cvs2svn) and the maintainer was marked as retired so I just went ahead and built them - it was almost trivial anyway, python modules seem to do everything for you. From glaw at opencsw.org Sun Nov 2 15:54:39 2008 From: glaw at opencsw.org (Gary Law) Date: Sun, 2 Nov 2008 14:54:39 +0000 Subject: [csw-maintainers] OpenCSW Prefix In-Reply-To: <490DB4DF.1040802@opencsw.org> References: <343A2AE3-DFC1-4B14-911F-67161138B3B4@opencsw.org> <4DE07271-5CBD-4022-B736-9248070EB132@opencsw.org> <490DB4DF.1040802@opencsw.org> Message-ID: 2008/11/2 Trygve Laugst?l > >> Like this :-) > >> http://buildfarm.opencsw.org/hudson/ > >> > >> > >> Oh fantastic. If you dive deep enough through the links eventually > >> absolute links to: > >> http://hudson:8070 > >> start appearing, which don't work. > > > > Oops. Trygve, any clues how to fix this? > > Odd. Where did you find that link? > go here: http://buildfarm.opencsw.org/hudson/ click new job (top left) takes you here: http://buildfarm.opencsw.org/hudson/newJob job name: test - ignore - 3 select copy job from, and input jetty6 - sparc-solaris2.8 click ok, takes you here: http://hudson:8070/hudson/job/test%202%20--%20ignore/configure > I don't care what we do as all the packages should be rebuilt for > Solaris 9+ anyway, but the only thing that matters is what our consumers > need. > > If we are to move we really need to document how to transition from the > Original Blastwave packages to the new OpenCSW packages. Perhaps it is > an alternative to use /opt/opencsw for the binary root and use > /etc/opt/csw for configuration files? > you'll hit collisions again if you go for /etc/opt/csw ... needs to be /etc/opt/opencsw too... B T W has anyone got a link to the GAR documentation? All the pages on the opencsw site talk about building things the long/difficult/many manual steps way... Thanks Gary -- Gary Law glaw at opencsw.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From william at wbonnet.net Sun Nov 2 17:10:22 2008 From: william at wbonnet.net (William Bonnet) Date: Sun, 02 Nov 2008 16:10:22 +0000 Subject: [csw-maintainers] IRL Meeting - new date In-Reply-To: <490DB58A.6090000@opencsw.org> References: <490DA0CA.1020008@opencsw.org> <490DB58A.6090000@opencsw.org> Message-ID: <490DD0EE.50108@wbonnet.net> Hi >> Hello, >> >> I've been talking with Phil about the IRL meeting and for him it would >> be possible, to attend to the IRL meeting, if it's taking place on 5/6/7 >> December. >> >> As far Phil would come from far way (it's a 12 hours flight for him), I >> would like to ask, if it's possible for you guys to postpone this date. >> >> Please let me know, so we can plan something for this date. >> > > Works for me. > It works for me. I confirm i'll be there. cheers, W. From ihsan at opencsw.org Sun Nov 2 16:43:13 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Sun, 02 Nov 2008 16:43:13 +0100 Subject: [csw-maintainers] new packages pymxbase and pypgsql for testing In-Reply-To: <9085.1225635554@gerd> References: <9085.1225635554@gerd> Message-ID: <490DCA91.2090102@opencsw.org> Am 2.11.2008 15:19 Uhr, Murray.Jensen at csiro.au schrieb: > Unfortunately I don't have access to the testing area so they are sitting > in my home directory on www.opencsw.org (/home/mjensen) ... Oups, there was no /testing. /home/testing is now www.opencsw.org/testing > 7ca5cc173202e77c55d0f795b932e5eb pymxbase-3.1.1,REV=2008.10.31-SunOS5.8-i386-CSW.pkg.gz > c931403b91add50a0032fee98a03fcd6 pymxbase-3.1.1,REV=2008.10.31-SunOS5.8-sparc-CSW.pkg.gz > 81aae9076588e4c1e70aec4e8e4d8c10 pypgsql-2.5.1,REV=2008.11.01-SunOS5.8-i386-CSW.pkg.gz > 5c338d5a2dcb414296eff3e2c1fcd53a pypgsql-2.5.1,REV=2008.11.01-SunOS5.8-sparc-CSW.pkg.gz > > If some kind soul could put them into testing I'd appreciate it. Cheers! Ok, just moved them to /home/testing. Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From trygvel at opencsw.org Sun Nov 2 18:05:46 2008 From: trygvel at opencsw.org (=?UTF-8?B?VHJ5Z3ZlIExhdWdzdMO4bA==?=) Date: Sun, 02 Nov 2008 18:05:46 +0100 Subject: [csw-maintainers] OpenCSW Prefix In-Reply-To: References: <343A2AE3-DFC1-4B14-911F-67161138B3B4@opencsw.org> <4DE07271-5CBD-4022-B736-9248070EB132@opencsw.org> <490DB4DF.1040802@opencsw.org> Message-ID: <490DDDEA.9030305@opencsw.org> Gary Law wrote: > 2008/11/2 Trygve Laugst?l > > > >> Like this :-) > >> http://buildfarm.opencsw.org/hudson/ > >> > >> > >> Oh fantastic. If you dive deep enough through the links eventually > >> absolute links to: > >> http://hudson:8070 > >> start appearing, which don't work. > > > > Oops. Trygve, any clues how to fix this? > > Odd. Where did you find that link? > > > go here: > http://buildfarm.opencsw.org/hudson/ > click new job (top left) > takes you here: > http://buildfarm.opencsw.org/hudson/newJob > job name: test - ignore - 3 > select copy job from, and input > jetty6 - sparc-solaris2.8 > click ok, takes you here: > http://hudson:8070/hudson/job/test%202%20--%20ignore/configure Thanks, I'll take a look once I have some time. -- Trygve From dam at opencsw.org Sun Nov 2 21:20:16 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 2 Nov 2008 21:20:16 +0100 Subject: [csw-maintainers] IRL Meeting - new date In-Reply-To: <490DA0CA.1020008@opencsw.org> References: <490DA0CA.1020008@opencsw.org> Message-ID: <52F94DAC-0BD3-4CB2-8BB1-010FA9B12591@opencsw.org> Hi Ihsan, Am 02.11.2008 um 13:44 schrieb Ihsan Dogan: > I've been talking with Phil about the IRL meeting and for him it would > be possible, to attend to the IRL meeting, if it's taking place on > 5/6/7 > December. > > As far Phil would come from far way (it's a 12 hours flight for > him), I > would like to ask, if it's possible for you guys to postpone this > date. > > Please let me know, so we can plan something for this date. Sure I'll be there. Best regards -- Dago From ihsan at opencsw.org Sun Nov 2 21:34:09 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Sun, 02 Nov 2008 21:34:09 +0100 Subject: [csw-maintainers] IRL Meeting - new date In-Reply-To: <52F94DAC-0BD3-4CB2-8BB1-010FA9B12591@opencsw.org> References: <490DA0CA.1020008@opencsw.org> <52F94DAC-0BD3-4CB2-8BB1-010FA9B12591@opencsw.org> Message-ID: <490E0EC1.6080802@opencsw.org> Am 2.11.2008 21:20 Uhr, Dagobert Michelsen schrieb: >> Please let me know, so we can plan something for this date. > Sure I'll be there. Thanks. I've updated by the way the wiki page: http://wiki.opencsw.org/irl-meeting Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From dam at opencsw.org Sun Nov 2 23:27:19 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 2 Nov 2008 23:27:19 +0100 Subject: [csw-maintainers] OpenCSW Prefix In-Reply-To: References: <343A2AE3-DFC1-4B14-911F-67161138B3B4@opencsw.org> <4DE07271-5CBD-4022-B736-9248070EB132@opencsw.org> <490DB4DF.1040802@opencsw.org> Message-ID: <40984868-1992-4438-9571-F18CA5BBEC8D@opencsw.org> Hi Gary, Am 02.11.2008 um 15:54 schrieb Gary Law: > B T W has anyone got a link to the GAR documentation? All the pages > on the opencsw site talk about building things the long/difficult/ > many manual steps way... I am currently converting / rewriting the GAR documentation to https://apps.sourceforge.net/mediawiki/gar/index.php?title=Main_Page There is not much there yet, but the newer features like dynamic prototypes and modulated builds haven't been documented at all yet, so please stand by for those. Just if anyone asks: I use the SF Wiki because GAR is also at SF, so the GAR project is fully SF-hosted. Best regards -- Dago From dam at opencsw.org Sun Nov 2 23:47:41 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 2 Nov 2008 23:47:41 +0100 Subject: [csw-maintainers] Java... again! Message-ID: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> Hi, I am currently thinking of packaging the JDKs / JREs to CSW packages. There is this license thing that they may be shipped when an application needs them. How about preventing normal installation but allowing installation when they are listed as dependency? Best regards -- Dago From phil at bolthole.com Mon Nov 3 00:21:11 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 2 Nov 2008 15:21:11 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org>; from dam@opencsw.org on Sun, Nov 02, 2008 at 11:47:41PM +0100 References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> Message-ID: <20081102152111.A95853@bolthole.com> On Sun, Nov 02, 2008 at 11:47:41PM +0100, Dagobert Michelsen wrote: > Hi, > > I am currently thinking of packaging the JDKs / JREs to CSW packages. > There is this license thing that they may be shipped when an application > needs them. How about preventing normal installation but allowing > installation when they are listed as dependency? sounds kinda inappropriate. far as I remember, various linxen have methods to distribute a JRE. So try something similar? From jakegoerzen at gmail.com Mon Nov 3 01:45:13 2008 From: jakegoerzen at gmail.com (Jake Goerzen) Date: Sun, 2 Nov 2008 16:45:13 -0800 Subject: [csw-maintainers] updated pkgs in /testing Message-ID: <315c02ae0811021645w76a5127awc99727e77c8f75e@mail.gmail.com> Hello, The following packages have been created at the build farm and placed in /home/testing: bcc519e0391b6bc71a26b4b7350de8ae libsdl-1.2.13,REV=2008.11.02-SunOS5.8-i386-CSW.pkg.gz efebcbf4b20557b5a6148675b797ee1d libsdl-1.2.13,REV=2008.11.02-SunOS5.8-sparc-CSW.pkg.gz e2a65fd3d41f34ce3e256af238a3b56c sdlttf-2.0.9,REV=2008.11.02-SunOS5.8-i386-CSW.pkg.gz 0cb28851f81998041b3fe615f834887c sdlttf-2.0.9,REV=2008.11.02-SunOS5.8-sparc-CSW.pkg.gz BTW, I noticed that http://www.opencsw.org/testing goes to a different place than http://mirror.opencsw.org/testing. Maybe they should both go to the same place for less confusion? Thanks, Jake -------------- next part -------------- An HTML attachment was scrubbed... URL: From dam at opencsw.org Mon Nov 3 15:13:10 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 3 Nov 2008 15:13:10 +0100 Subject: [csw-maintainers] updated pkgs in /testing In-Reply-To: <315c02ae0811021645w76a5127awc99727e77c8f75e@mail.gmail.com> References: <315c02ae0811021645w76a5127awc99727e77c8f75e@mail.gmail.com> Message-ID: Hi, Am 03.11.2008 um 01:45 schrieb Jake Goerzen: > BTW, I noticed that http://www.opencsw.org/testing goes to a > different place than http://mirror.opencsw.org/testing. Maybe they > should both go to the same place for less confusion? Yes. Having two /testing is a bad idea. Am 03.11.2008 um 03:43 schrieb : > On Mon, 3 Nov 2008 07:28:24 +1100, Dagobert Michelsen writes: >> You do have now :-) I set up a buildfarm account for you on >> login.opencsw.org >> and the most frequently used testing is >> http://buildfarm.opencsw.org/testing/ >> which is available from /home/testing/ from there. You should be able >> to login >> from www.opencsw.org with >> ssh mjensen at login.opencsw.org > > OK, thanks Dago - that all works. So this means we have two /testing > areas now - is that a good idea? Cheers! No again. I have copied them to http://buildfarm.opencsw.org/testing. Ihsan, could you please install a redirect from www.opencsw.org/testing to buildfarm.opencsw.org/testing? Best regards -- Dago -------------- next part -------------- An HTML attachment was scrubbed... URL: From trygvel at opencsw.org Mon Nov 3 16:29:29 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Mon, 03 Nov 2008 16:29:29 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> Message-ID: <490F18D9.7090702@opencsw.org> Dagobert Michelsen wrote: > Hi, > > I am currently thinking of packaging the JDKs / JREs to CSW packages. > There is this license thing that they may be shipped when an application > needs them. How about preventing normal installation but allowing > installation when they are listed as dependency? What Debian and Ubuntu (and possibly others) do is that they have a package to create the Java packages. It take the downloaded bundle as input and give you a .deb out with generated dependency information. We (you) could start there as a starting point. -- Trygve From phil at bolthole.com Mon Nov 3 17:50:11 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 3 Nov 2008 08:50:11 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <490F18D9.7090702@opencsw.org>; from trygvel@opencsw.org on Mon, Nov 03, 2008 at 04:29:29PM +0100 References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> Message-ID: <20081103085011.B95235@bolthole.com> On Mon, Nov 03, 2008 at 04:29:29PM +0100, Trygve Laugst?l wrote: > What Debian and Ubuntu (and possibly others) do is that they have a > package to create the Java packages. It take the downloaded bundle as > input and give you a .deb out with generated dependency information. We > (you) could start there as a starting point. Contrariwise... solaris DOES SHIP with a java runtime! So our "java package", could merely be some kind of user-updatable symlink for /opt/csw/java, to point to /usr/java, for example. Ideally, with some comments and hints in our readme about where to get the latest updates, etc, etc. there's a few varients on this. for example we could have /opt/csw/bin/{jre,java} as symlinks or wrappers to somewhere.... etc, etc. From ihsan at opencsw.org Mon Nov 3 20:05:16 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Mon, 03 Nov 2008 20:05:16 +0100 Subject: [csw-maintainers] updated pkgs in /testing In-Reply-To: References: <315c02ae0811021645w76a5127awc99727e77c8f75e@mail.gmail.com> Message-ID: <490F4B6C.3020403@opencsw.org> Am 3.11.2008 15:13 Uhr, Dagobert Michelsen schrieb: > Ihsan, could you please install a redirect from www.opencsw.org/testing > > to buildfarm.opencsw.org/testing? done -- ihsan at dogan.ch http://blog.dogan.ch/ From dam at opencsw.org Tue Nov 4 11:44:30 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 4 Nov 2008 11:44:30 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081103085011.B95235@bolthole.com> References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> Message-ID: Hi Phil, Am 03.11.2008 um 17:50 schrieb Philip Brown: > On Mon, Nov 03, 2008 at 04:29:29PM +0100, Trygve Laugst?l wrote: >> What Debian and Ubuntu (and possibly others) do is that they have a >> package to create the Java packages. It take the downloaded bundle as >> input and give you a .deb out with generated dependency >> information. We >> (you) could start there as a starting point. > > Contrariwise... solaris DOES SHIP with a java runtime! > So our "java package", could merely be some kind of user-updatable > symlink > for /opt/csw/java, to point to /usr/java, for example. > Ideally, with some comments and hints in our readme about where to > get the > latest updates, etc, etc. > > there's a few varients on this. for example we could have > /opt/csw/bin/{jre,java} as symlinks or wrappers to somewhere.... > etc, etc. There are several reasons why I think it would be nice to have JRE and JDK as CSW packages: 1. Installation would be easier Currently you have to download packages for 32 and 64 bit and issue special install commands instead of pkg-get -i jdk13 jre15 2. Updates would be installed automatically The minor version (like the "2" in 1.4.2) are bugfix releases which would be repackaged ASAP and an 3. Certain CSW packages relying on a specific Java version could just depend on it. I am not sure I got your point in linking to /usr. Extrapolating from our policy I would make the CSW Java independent from the system Java. Best regards -- Dago From trygvel at opencsw.org Tue Nov 4 13:36:00 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Tue, 04 Nov 2008 13:36:00 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081103085011.B95235@bolthole.com> References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> Message-ID: <491041B0.5000501@opencsw.org> Philip Brown wrote: > On Mon, Nov 03, 2008 at 04:29:29PM +0100, Trygve Laugst?l wrote: >> What Debian and Ubuntu (and possibly others) do is that they have a >> package to create the Java packages. It take the downloaded bundle as >> input and give you a .deb out with generated dependency information. We >> (you) could start there as a starting point. > > Contrariwise... solaris DOES SHIP with a java runtime! Uhm, Solaris 8 ships like jdk 1.2 or something. > So our "java package", could merely be some kind of user-updatable symlink > for /opt/csw/java, to point to /usr/java, for example. > Ideally, with some comments and hints in our readme about where to get the > latest updates, etc, etc. > > there's a few varients on this. for example we could have > /opt/csw/bin/{jre,java} as symlinks or wrappers to somewhere.... > etc, etc. To me, depending only on our own packages + base Solaris (of whatever version we're currently basing our stuff on) is what we need to do to deliver quality packages. We need this. Maybe only for building packages, but still. -- Trygve From phil at bolthole.com Tue Nov 4 15:05:17 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 4 Nov 2008 06:05:17 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: ; from dam@opencsw.org on Tue, Nov 04, 2008 at 11:44:30AM +0100 References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> Message-ID: <20081104060517.B68247@bolthole.com> On Tue, Nov 04, 2008 at 11:44:30AM +0100, Dagobert Michelsen wrote: > > There are several reasons why I think it would be nice to have > JRE and JDK as CSW packages: > .... I dont disagree. If you find a way to cleanly redistribute, I think it's a good idea. > I am not sure I got your point in linking to /usr. Extrapolating > from our policy I would make the CSW Java independent from the > system Java. Well, I think that there is a benefit in at least having One Standard Place for java. So that our programs that NEED java, can set JAVA_HOME to it and just go, if they dont have any funky requirements. The issue of WHICH java runtime it would point to, I think would be best left to a combination of [our CSW java tzar, TBD], and the customer site admin. From phil at bolthole.com Wed Nov 5 18:13:31 2008 From: phil at bolthole.com (Philip Brown) Date: Wed, 5 Nov 2008 09:13:31 -0800 Subject: [csw-maintainers] cheap flights USA<->europe? Message-ID: <20081105091331.A52830@bolthole.com> So.... before I officially book a flight... anyone know of good ways to get some really good deals for flights from california to switzerland? :-) From mmayer at mmayer.net Wed Nov 5 19:31:30 2008 From: mmayer at mmayer.net (Markus Mayer) Date: Wed, 5 Nov 2008 10:31:30 -0800 Subject: [csw-maintainers] checkpkg error Message-ID: <20081105183129.GA3001@bender.opencsw.org> Hi, Does anybody know where this error is coming from? build8s% checkpkg work/mmayer-build8s.d/libcups-1.3.9,REV\=2008.11.05-SunOS5.8-sparc-CSW.pkg.gz Examining work/mmayer-build8s.d/libcups-1.3.9,REV=2008.11.05-SunOS5.8-sparc-CSW.pkg.gz Looking for bad strings... Extracting files for more detailed inspection... CSWlibcups/pkginfo 2 blocks ERROR: filename missing full version field 1.3.9,REV=2008.11.02 This used to work the very first time I packed up the individual CUPS packages, but no longer such luck. Looking at pkginfo I see this: PKG=CSWlibcups NAME=libcups - Libraries for the Common UNIX Printing System ARCH=sparc VERSION=1.3.9,REV=2008.11.02 CATEGORY=application VENDOR=http://www.cups.org/ packaged for CSW by Unknown EMAIL=Unknown PSTAMP=mmayer at build8s-r2204UNCOMMITTED-20081102210321 CLASSES=none HOTLINE=http://www.opencsw.org/bugtrack/ I obviously still need to modify the VENDOR and EMAIL field, but VERSION seems just fine to me. Thanks, -Markus From ihsan at opencsw.org Wed Nov 5 19:42:42 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Wed, 05 Nov 2008 19:42:42 +0100 Subject: [csw-maintainers] cheap flights USA<->europe? In-Reply-To: <20081105091331.A52830@bolthole.com> References: <20081105091331.A52830@bolthole.com> Message-ID: <4911E922.1030504@opencsw.org> Hi Phil, Am 5.11.2008 18:13 Uhr, Philip Brown schrieb: > So.... before I officially book a flight... anyone know of good ways to get > some really good deals for flights from california to switzerland? :-) Where in California? Los Angeles? The closest airport is Zurich, but Basel/Mulhouse or Stuttgart are also close. Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From phil at bolthole.com Wed Nov 5 19:52:06 2008 From: phil at bolthole.com (Philip Brown) Date: Wed, 5 Nov 2008 10:52:06 -0800 Subject: [csw-maintainers] checkpkg error In-Reply-To: <20081105183129.GA3001@bender.opencsw.org>; from mmayer@mmayer.net on Wed, Nov 05, 2008 at 10:31:30AM -0800 References: <20081105183129.GA3001@bender.opencsw.org> Message-ID: <20081105105206.I95235@bolthole.com> On Wed, Nov 05, 2008 at 10:31:30AM -0800, Markus Mayer wrote: > Hi, > > Does anybody know where this error is coming from? you goofed, that's where :-) > > build8s% checkpkg > work/mmayer-build8s.d/libcups-1.3.9,REV\=2008.11.05 > Looking at pkginfo I see this: > > VERSION=1.3.9,REV=2008.11.02 They dont match! From phil at bolthole.com Wed Nov 5 19:55:34 2008 From: phil at bolthole.com (Philip Brown) Date: Wed, 5 Nov 2008 10:55:34 -0800 Subject: [csw-maintainers] cheap flights USA<->europe? In-Reply-To: <4911E922.1030504@opencsw.org>; from ihsan@opencsw.org on Wed, Nov 05, 2008 at 07:42:42PM +0100 References: <20081105091331.A52830@bolthole.com> <4911E922.1030504@opencsw.org> Message-ID: <20081105105534.J95235@bolthole.com> On Wed, Nov 05, 2008 at 07:42:42PM +0100, Ihsan Dogan wrote: > Hi Phil, > > Am 5.11.2008 18:13 Uhr, Philip Brown schrieb: > > > So.... before I officially book a flight... anyone know of good ways to get > > some really good deals for flights from california to switzerland? :-) > > Where in California? Los Angeles? > > The closest airport is Zurich, but Basel/Mulhouse or Stuttgart are also > close. My closest "major" ones are LAX, and also irvine (SNA) I work by LAX, but live inbetween LAX and SNA. From william at wbonnet.net Wed Nov 5 20:18:14 2008 From: william at wbonnet.net (William Bonnet) Date: Wed, 05 Nov 2008 20:18:14 +0100 Subject: [csw-maintainers] cheap flights USA<->europe? In-Reply-To: <20081105105534.J95235@bolthole.com> References: <20081105091331.A52830@bolthole.com> <4911E922.1030504@opencsw.org> <20081105105534.J95235@bolthole.com> Message-ID: <4911F176.4020306@wbonnet.net> Hi Philip > My closest "major" ones are LAX, and also irvine (SNA) > I work by LAX, but live inbetween LAX and SNA. > You may also consider Paris ? It is about 600 km far from Paris. You can then go by train (about 200? for the two tickets). I can make reservation here for you. I believe that Peter leave from Paris, so do i. So if you choose to come to Paris, maybe we can go by car from Paris to Zurich. It is about 600km, mostly highway. so it will be something like a 6 hours drive we could do together ( i will provide the car ;) ) 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.guses.org French speaking Solaris User Group From mmayer at mmayer.net Wed Nov 5 21:20:52 2008 From: mmayer at mmayer.net (Markus Mayer) Date: Wed, 5 Nov 2008 12:20:52 -0800 Subject: [csw-maintainers] checkpkg error In-Reply-To: <20081105105206.I95235@bolthole.com> References: <20081105183129.GA3001@bender.opencsw.org> <20081105105206.I95235@bolthole.com> Message-ID: <20081105202051.GA6128@bender.opencsw.org> On Wednesday, 05 Nov 2008 10:52 -0800, Philip Brown wrote: >On Wed, Nov 05, 2008 at 10:31:30AM -0800, Markus Mayer wrote: >> Hi, >> >> Does anybody know where this error is coming from? > >you goofed, that's where :-) > >> Looking at pkginfo I see this: >> >> VERSION=1.3.9,REV=2008.11.02 > >They dont match! Okay, that makes sense. But I still see two issues: 1) the error message checkpkg prints is misleading (the full version field is present, there is a mismatch, however). 2) Where are the dates coming from? I didn't specify either one. I was simply testing the packaging by re-packaging a previously compiled CUPS tree. One date is obviously today's, the other one seems to be when the package was built. I don't want to have to rebuild everything simply to get the dates right, if all I want to do is package up the binaries I already have. Regards, -Markus From phil at bolthole.com Wed Nov 5 21:30:12 2008 From: phil at bolthole.com (Philip Brown) Date: Wed, 5 Nov 2008 12:30:12 -0800 Subject: [csw-maintainers] checkpkg error In-Reply-To: <20081105202051.GA6128@bender.opencsw.org>; from mmayer@mmayer.net on Wed, Nov 05, 2008 at 12:20:52PM -0800 References: <20081105183129.GA3001@bender.opencsw.org> <20081105105206.I95235@bolthole.com> <20081105202051.GA6128@bender.opencsw.org> Message-ID: <20081105123012.S95235@bolthole.com> On Wed, Nov 05, 2008 at 12:20:52PM -0800, Markus Mayer wrote: > ... > 2) Where are the dates coming from? I didn't specify either one. I was > simply testing the packaging by re-packaging a previously compiled CUPS > tree. I'm guessing "from GAR", so I see that as a bug in gar. If you do it "the old fashioned way", using my createpkg script, you never have this problem, since it always creates the filename based on the pkginfo ;-) > One date is obviously today's, the other one seems to be when the > package was built. I don't want to have to rebuild everything simply to > get the dates right, if all I want to do is package up the binaries I > already have. Well, you might consider using createpkg then, for this specific rebuild. reminder: if you have valid pkginfo, depend, copyright, prototype files in your current directory, then all you need do is type createpkg -r /path/to/relative-root and it will build the package for you, presuming you have your binaries layed out in some tree like /path/to/relative-root/opt/csw/bin/blahblah If you have them "installed normally", directly to /opt/csw, then you could use createpkg -r / and it would work,as long as you have pkginfo and so on, in your current dir. From dam at opencsw.org Wed Nov 5 22:03:36 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 5 Nov 2008 22:03:36 +0100 Subject: [csw-maintainers] checkpkg error In-Reply-To: <20081105202051.GA6128@bender.opencsw.org> References: <20081105183129.GA3001@bender.opencsw.org> <20081105105206.I95235@bolthole.com> <20081105202051.GA6128@bender.opencsw.org> Message-ID: Hi Markus, Am 05.11.2008 um 21:20 schrieb Markus Mayer: > On Wednesday, 05 Nov 2008 10:52 -0800, Philip Brown wrote: >> On Wed, Nov 05, 2008 at 10:31:30AM -0800, Markus Mayer wrote: >>> Hi, >>> >>> Does anybody know where this error is coming from? >> >> you goofed, that's where :-) > One date is obviously today's, the other one seems to be when the > package was built. I don't want to have to rebuild everything simply > to > get the dates right, if all I want to do is package up the binaries I > already have. This error occurs when building a packages takes more than a day. Just give the whole package a respin (or use "gmake reinstall", "gmake repackage") and it should work. Best regards -- Dago From dam at opencsw.org Wed Nov 5 22:05:53 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 5 Nov 2008 22:05:53 +0100 Subject: [csw-maintainers] checkpkg error In-Reply-To: <20081105123012.S95235@bolthole.com> References: <20081105183129.GA3001@bender.opencsw.org> <20081105105206.I95235@bolthole.com> <20081105202051.GA6128@bender.opencsw.org> <20081105123012.S95235@bolthole.com> Message-ID: <4C0E4B7E-8C8F-4E35-8545-1AB0013351EA@opencsw.org> Hi Phil, Am 05.11.2008 um 21:30 schrieb Philip Brown: > On Wed, Nov 05, 2008 at 12:20:52PM -0800, Markus Mayer wrote: >> ... >> 2) Where are the dates coming from? I didn't specify either one. I >> was >> simply testing the packaging by re-packaging a previously compiled >> CUPS >> tree. > > I'm guessing "from GAR", so I see that as a bug in gar. It sure is. However, if you build a package in one turn you don't run into this and there are nastier things to fix first. Best regards -- Dago From phil at bolthole.com Wed Nov 5 22:35:59 2008 From: phil at bolthole.com (Philip Brown) Date: Wed, 5 Nov 2008 13:35:59 -0800 Subject: [csw-maintainers] checkpkg error In-Reply-To: <4C0E4B7E-8C8F-4E35-8545-1AB0013351EA@opencsw.org>; from dam@opencsw.org on Wed, Nov 05, 2008 at 10:05:53PM +0100 References: <20081105183129.GA3001@bender.opencsw.org> <20081105105206.I95235@bolthole.com> <20081105202051.GA6128@bender.opencsw.org> <20081105123012.S95235@bolthole.com> <4C0E4B7E-8C8F-4E35-8545-1AB0013351EA@opencsw.org> Message-ID: <20081105133559.U95235@bolthole.com> On Wed, Nov 05, 2008 at 10:05:53PM +0100, Dagobert Michelsen wrote: > Hi Phil, *wave* > > I'm guessing "from GAR", so I see that as a bug in gar. > > It sure is. However, if you build a package in one turn > you don't run into this and there are nastier things to > fix first. > of course, if someone else were to look at it and submit a fix for it, I'm sure that would work too... :-D Dagobert doesnt have to be the only one to patch gar.... From dam at opencsw.org Thu Nov 6 09:02:06 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 6 Nov 2008 09:02:06 +0100 Subject: [csw-maintainers] New buildfarm at Gore Message-ID: <6FDDDCA2-502B-4617-ADAF-19E4885CBF86@opencsw.org> Hi, we have a new build server available sponsored by W. L. Gore company (yes, like "Gore-Tex") and organized by Phil. It is a V240 2 x 1.5 GHz 8 GB Ram 2 x 73 GB and 2 x 146 GB Disk Thanks! The server is reachable as build8s.go.opencsw.org (go = Gore) directly from the internet. All accounts from the bo-farm have also been created there and the SSH keys have been transferred, so each maintainer having a login at "bo" should also be able to login to "go". There should be the same set of CSW packages installed on the bo- and go-farm. Please still deliver packages to /home/testing on the bo farm to allow a single download location. Farm access has been documented at Best regards -- Dago From phil at bolthole.com Thu Nov 6 18:24:19 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 6 Nov 2008 09:24:19 -0800 Subject: [csw-maintainers] New buildfarm at Gore In-Reply-To: <6FDDDCA2-502B-4617-ADAF-19E4885CBF86@opencsw.org>; from dam@opencsw.org on Thu, Nov 06, 2008 at 09:02:06AM +0100 References: <6FDDDCA2-502B-4617-ADAF-19E4885CBF86@opencsw.org> Message-ID: <20081106092419.C95235@bolthole.com> On Thu, Nov 06, 2008 at 09:02:06AM +0100, Dagobert Michelsen wrote: > ... > Please still deliver packages to /home/testing > on the bo farm to allow a single download location. clarification: If you want to put packages in a "testing" space, then please put them there. If and when you are satisfied your packages are ready for RELEASE, however,... please still scp them to www.opencsw.org:/home/newpkgs as previously, and as documented in our standards pages. From pfelecan at blastwave.org Thu Nov 6 19:28:07 2008 From: pfelecan at blastwave.org (Peter FELECAN) Date: Thu, 06 Nov 2008 19:28:07 +0100 Subject: [csw-maintainers] cheap flights USA<->europe? In-Reply-To: <4911F176.4020306@wbonnet.net> (William Bonnet's message of "Wed\, 05 Nov 2008 20\:18\:14 +0100") References: <20081105091331.A52830@bolthole.com> <4911E922.1030504@opencsw.org> <20081105105534.J95235@bolthole.com> <4911F176.4020306@wbonnet.net> Message-ID: William Bonnet writes: > I believe that Peter leave from Paris, so do i. So if you choose to come > to Paris, maybe we can go by car from Paris to Zurich. It is about > 600km, mostly highway. so it will be something like a 6 hours drive we > could do together ( i will provide the car ;) ) I'm using for all my trips Lufthansa. They have very cheap inter-city flights, e.g. Paris--Zurich 168 euros for a round trip. A Los Angeles--Zurich trip is around 600 euros (764 USD) and I don't know if that falls in the cheap category... Now, for making the 1200 km by car, why not, we can share the fees --- need to evaluate if they are less than a plane ticket --- but I wonder if it's very green. -- Peter From ihsan at opencsw.org Thu Nov 6 20:27:39 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Thu, 06 Nov 2008 20:27:39 +0100 Subject: [csw-maintainers] cheap flights USA<->europe? In-Reply-To: <20081105105534.J95235@bolthole.com> References: <20081105091331.A52830@bolthole.com> <4911E922.1030504@opencsw.org> <20081105105534.J95235@bolthole.com> Message-ID: <4913452B.3060300@opencsw.org> Am 5.11.2008 19:55 Uhr, Philip Brown schrieb: > My closest "major" ones are LAX, and also irvine (SNA) > I work by LAX, but live inbetween LAX and SNA. With "Swiss International" from LAX to ZRH, direct fligth: 661.- $. I've checked also other airports and airlines and it looks like, that this is the cheapest offer I can find. --> http://www.swiss.com/ Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From phil at bolthole.com Thu Nov 6 20:36:11 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 6 Nov 2008 11:36:11 -0800 Subject: [csw-maintainers] cheap flights USA<->europe? In-Reply-To: <4913452B.3060300@opencsw.org>; from ihsan@opencsw.org on Thu, Nov 06, 2008 at 08:27:39PM +0100 References: <20081105091331.A52830@bolthole.com> <4911E922.1030504@opencsw.org> <20081105105534.J95235@bolthole.com> <4913452B.3060300@opencsw.org> Message-ID: <20081106113611.Q95235@bolthole.com> On Thu, Nov 06, 2008 at 08:27:39PM +0100, Ihsan Dogan wrote: > Am 5.11.2008 19:55 Uhr, Philip Brown schrieb: > > > My closest "major" ones are LAX, and also irvine (SNA) > > I work by LAX, but live inbetween LAX and SNA. > > With "Swiss International" from LAX to ZRH, direct fligth: 661.- $. > > I've checked also other airports and airlines and it looks like, that > this is the cheapest offer I can find. Awesome! thanks From jakegoerzen at gmail.com Fri Nov 7 16:07:36 2008 From: jakegoerzen at gmail.com (Jake Goerzen) Date: Fri, 7 Nov 2008 07:07:36 -0800 Subject: [csw-maintainers] now in /testing: freeciv 2.0.10 Message-ID: <315c02ae0811070707i6973c74akc48d8138c23b3a52@mail.gmail.com> updated freeciv 2.0.10 pkgs are available in /testing: 7f36723348f271a071ae1ed162edafb6 freeciv-2.0.10,REV=2008.11.07-SunOS5.8-i386-CSW.pkg.gz e18a80f6832a4f4247d4fa4e0085b7c4 freeciv-2.0.10,REV=2008.11.07-SunOS5.8-sparc-CSW.pkg.gz Thanks, Jake -------------- next part -------------- An HTML attachment was scrubbed... URL: From dam at opencsw.org Fri Nov 7 20:43:37 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 7 Nov 2008 20:43:37 +0100 Subject: [csw-maintainers] Contents of devel@ list Message-ID: Hi, I am having a little talk with Phil about the contents of the devel@ mailing list: Am 07.11.2008 um 18:06 schrieb Philip Brown: > On Fri, Nov 07, 2008 at 05:06:23PM +0100, Dagobert Michelsen wrote: >> BTW: If the package gets pushed to current there should be also >> a mail to devel at . I am thinking of devel@ as a high frequency >> list to get a detailed understanding of what is going on. > > Hmm.. I think announcing a release of packages as they happen, is > unneccessary spam. If a bunch of people really want that, then > that's fine > with me. but I think you should ask how many people are actually > INTERSTED > in that, before we do that :-) > a reminder: a weekly email to newpkgs mailing list, already happens. For me it is interesting when my packages get processed and are batched to current/. The newpkgs@ list is for users who want to know what is released (BTW: We should provide RSS for released to current/ also. Phil? ;-) Would you consider this useful or noise? Best regards -- Dago From phil at bolthole.com Fri Nov 7 20:50:30 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 7 Nov 2008 11:50:30 -0800 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: ; from dam@opencsw.org on Fri, Nov 07, 2008 at 08:43:37PM +0100 References: Message-ID: <20081107115030.D95235@bolthole.com> On Fri, Nov 07, 2008 at 08:43:37PM +0100, Dagobert Michelsen wrote: > > For me it is interesting when my packages get processed and are batched > to current/. The newpkgs@ list is for users who want to know what is > released (BTW: We should provide RSS for released to current/ also. > Phil? ;-) Hmm.. perhaps I misunderstood what you were asking. I thought when you described "batched to current", you were talking about "when it is released", as the same thing. But you seem to be referring to them as different things now. Perhaps you could clarify? From dam at opencsw.org Fri Nov 7 20:59:32 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 7 Nov 2008 20:59:32 +0100 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: <20081107115030.D95235@bolthole.com> References: <20081107115030.D95235@bolthole.com> Message-ID: <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org> Hi Phil, Am 07.11.2008 um 20:50 schrieb Philip Brown: > On Fri, Nov 07, 2008 at 08:43:37PM +0100, Dagobert Michelsen wrote: >> For me it is interesting when my packages get processed and are >> batched >> to current/. The newpkgs@ list is for users who want to know what is >> released (BTW: We should provide RSS for released to current/ also. >> Phil? ;-) > > Hmm.. perhaps I misunderstood what you were asking. I thought when you > described "batched to current", you were talking about "when it is > released", as the same thing. > But you seem to be referring to them as different things now. > Perhaps you could clarify? When I move a package to www.opencsw.org:/newpkgs I write a mail to the unstable release manager (read: you) and you process it. This usually occurs within a day or two and you usually write back a mail that the package is accepted. The idea is to have this formalized like that when you batch the package for master mirror distribution an email is send automatically to devel@ that this has been done. Best regards -- Dago From phil at bolthole.com Fri Nov 7 21:24:31 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 7 Nov 2008 12:24:31 -0800 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org>; from dam@opencsw.org on Fri, Nov 07, 2008 at 08:59:32PM +0100 References: <20081107115030.D95235@bolthole.com> <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org> Message-ID: <20081107122431.F95235@bolthole.com> On Fri, Nov 07, 2008 at 08:59:32PM +0100, Dagobert Michelsen wrote: > When I move a package to www.opencsw.org:/newpkgs I write a > mail to the unstable release manager (read: you) and you > process it. This usually occurs within a day or two and > you usually write back a mail that the package is accepted. > The idea is to have this formalized like that when you > batch the package for master mirror distribution an email > is send automatically to devel@ that this has been done. Oh.... you are trying to keep an eye on the part between "i copy it into the batching area" vs "it goes public". because in the past, I have sometimes taken a while between the two. As a side note, I anticipate that gap to be much much shorter these days, since the processes runs smoother for me now. Additionally, our front webpage, and the "newpkgs" mailing list, both actually get their information from the internal batching area :-} So we already have an "updated daily" reference of what is in that area. As mentioned previously, I could make the front web page updated hourly, if you like. Unless people really want an actual individual EMAIL to go out somewhere, every time a package hits that area. Do people want to see that? or is the insert on www.opencsw.org enough? (either once a day, or once an hour?) From jgoerzen at opencsw.org Fri Nov 7 22:56:45 2008 From: jgoerzen at opencsw.org (Jake Goerzen) Date: Fri, 7 Nov 2008 13:56:45 -0800 Subject: [csw-maintainers] request pkg(s) installed on buildfarm Message-ID: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> Currently installed SDL libraries on buildfarm: build8s% /opt/csw/bin/pkg-get -c | grep sdl libsdl 1.2.9 SAME sdlimage [Not installed] 1.2.4,REV=2006.05.03 sdlmixer [Not installed] 1.2.6,REV=2007.02.27 sdlnet [Not installed] 1.2.5,REV=2006.05.04 sdlsound [Not installed] 1.0.1,REV=2006.06.17 sdlttf [Not installed] 2.0.6,REV=2006.06.17 Please install "CSWsdlimage, CSWsdlmixer & CSWsdlttf" These are prerequisites for building proper freeciv and wesnoth packages. Thanks, Jake -------------- next part -------------- An HTML attachment was scrubbed... URL: From phil at bolthole.com Sat Nov 8 05:43:14 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 7 Nov 2008 20:43:14 -0800 Subject: [csw-maintainers] cheap flights USA<->europe? In-Reply-To: <20081105091331.A52830@bolthole.com>; from phil@bolthole.com on Wed, Nov 05, 2008 at 09:13:31AM -0800 References: <20081105091331.A52830@bolthole.com> Message-ID: <20081107204314.B22627@bolthole.com> On Wed, Nov 05, 2008 at 09:13:31AM -0800, Philip Brown wrote: > So.... before I officially book a flight... anyone know of good ways to get > some really good deals for flights from california to switzerland? :-) fyi: kayak.com ended up giving me the best amount of choices. and also told me, "go to united.com and book direct, to save yourself even more money!" From dam at opencsw.org Sat Nov 8 07:33:35 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 8 Nov 2008 07:33:35 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> Message-ID: <5A254E01-AD38-40EE-86AD-9823C2026452@opencsw.org> Hi Jake, Am 07.11.2008 um 22:56 schrieb Jake Goerzen: > Please install "CSWsdlimage, CSWsdlmixer & CSWsdlttf" These are > prerequisites for building proper freeciv and wesnoth packages. Done. Best regards -- Dago From dam at opencsw.org Sat Nov 8 10:59:32 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 8 Nov 2008 10:59:32 +0100 Subject: [csw-maintainers] Update on 'login' Message-ID: Hi, I updated today login.opencsw.org to match current/. I hope you didn't experiences any troubles due to removed and reinstaled packages. Thanks! -- Dago From dam at opencsw.org Sat Nov 8 16:40:29 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 8 Nov 2008 16:40:29 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <491041B0.5000501@opencsw.org> References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> Message-ID: Hi, Am 04.11.2008 um 13:36 schrieb Trygve Laugst?l: > To me, depending only on our own packages + base Solaris (of whatever > version we're currently basing our stuff on) is what we need to do to > deliver quality packages. > > We need this. Maybe only for building packages, but still. We have this. Now in testing/: jre13-1.3.1_22,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz jre13-1.3.1_22,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz jre14-1.4.2_17,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz jre14-1.4.2_17,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz jre5-1.5.0_15,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz jre5-1.5.0_15,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz jre6-6u7,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz jre6-6u7,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz jdk13-1.3.1_22,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz jdk13-1.3.1_22,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz jdk14-1.4.2_17,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz jdk14-1.4.2_17,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz jdk5-1.5.0_15,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz jdk5-1.5.0_15,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz jdk6-6u7,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz jdk6-6u7,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz Fellow Java Gurus, please test. Thanks! -- Dago From james at opencsw.org Sat Nov 8 17:06:10 2008 From: james at opencsw.org (James Lee) Date: Sat, 08 Nov 2008 16:06:10 GMT Subject: [csw-maintainers] Java... again! In-Reply-To: References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> Message-ID: <20081108.16061000.3036193704@gyor.oxdrove.co.uk> On 08/11/08, 15:40:29, Dagobert Michelsen wrote regarding Re: [csw-maintainers] Java... again!: > jdk5-1.5.0_15,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz > jdk5-1.5.0_15,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz > jdk6-6u7,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz > jdk6-6u7,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz Latest 1.5 is Update 16 http://java.sun.com/javase/downloads/index_jdk5.jsp The latest 1.6 is Update 10. http://java.sun.com/javase/downloads/index.jsp It identifies itself: $ java -version java version "1.6.0_10" Java(TM) SE Runtime Environment (build 1.6.0_10-b33) Java HotSpot(TM) Server VM (build 11.0-b15, mixed mode) So why use break the pattern of naming, I'd expect the package to be identified similarly as "1.6.0_10". From trygvel at opencsw.org Sun Nov 9 11:32:47 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sun, 09 Nov 2008 11:32:47 +0100 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: <20081107122431.F95235@bolthole.com> References: <20081107115030.D95235@bolthole.com> <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org> <20081107122431.F95235@bolthole.com> Message-ID: <4916BC4F.8010606@opencsw.org> Philip Brown wrote: > On Fri, Nov 07, 2008 at 08:59:32PM +0100, Dagobert Michelsen wrote: >> When I move a package to www.opencsw.org:/newpkgs I write a >> mail to the unstable release manager (read: you) and you >> process it. This usually occurs within a day or two and >> you usually write back a mail that the package is accepted. >> The idea is to have this formalized like that when you >> batch the package for master mirror distribution an email >> is send automatically to devel@ that this has been done. > > Oh.... you are trying to keep an eye on the part between > > "i copy it into the batching area" > vs > "it goes public". > > because in the past, I have sometimes taken a while between the two. > As a side note, I anticipate that gap to be much much shorter these days, > since the processes runs smoother for me now. > > Additionally, our front webpage, and the "newpkgs" mailing list, both > actually get their information from the internal batching area :-} > So we already have an "updated daily" reference of what is in that area. > > As mentioned previously, I could make the front web page updated hourly, if > you like. > Unless people really want an actual individual EMAIL to go out somewhere, > every time a package hits that area. > > Do people want to see that? or is the insert on www.opencsw.org enough? > (either once a day, or once an hour?) I wouldn't mind an email when a packages moves from one state to another. I would also like an Atom feed with new and updated packages so that people can follow the changes. In the future I wouldn't mind including the change log of what's changed. -- Trygve From trygvel at opencsw.org Sun Nov 9 11:34:47 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sun, 09 Nov 2008 11:34:47 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> Message-ID: <4916BCC7.9000104@opencsw.org> Jake Goerzen wrote: > Currently installed SDL libraries on buildfarm: > > build8s% /opt/csw/bin/pkg-get -c | grep sdl > libsdl 1.2.9 SAME > sdlimage [Not installed] 1.2.4,REV=2006.05.03 > sdlmixer [Not installed] 1.2.6,REV=2007.02.27 > sdlnet [Not installed] 1.2.5,REV=2006.05.04 > sdlsound [Not installed] 1.0.1,REV=2006.06.17 > sdlttf [Not installed] 2.0.6,REV=2006.06.17 Would it be possible to run "pkg-get -c|grep -v SAME" and have it spit out an email when stuff is outdated? -- Trygve From dam at opencsw.org Sun Nov 9 11:49:41 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 9 Nov 2008 11:49:41 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <4916BCC7.9000104@opencsw.org> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> Message-ID: <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> Hi Trygve, Am 09.11.2008 um 11:34 schrieb Trygve Laugst?l: > Would it be possible to run "pkg-get -c|grep -v SAME" and have it spit > out an email when stuff is outdated? Do you mean this? pkg-get -c|grep -v SAME|grep -v "Not installed" Should the email go to the farm manager to fix this ASAP or once per day to devel@? Best regards -- Dago From dam at opencsw.org Sun Nov 9 11:57:50 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 9 Nov 2008 11:57:50 +0100 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: <4916BC4F.8010606@opencsw.org> References: <20081107115030.D95235@bolthole.com> <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org> <20081107122431.F95235@bolthole.com> <4916BC4F.8010606@opencsw.org> Message-ID: Hi, Am 09.11.2008 um 11:32 schrieb Trygve Laugst?l: > Philip Brown wrote: >> Oh.... you are trying to keep an eye on the part between >> >> "i copy it into the batching area" >> vs >> "it goes public". >> >> because in the past, I have sometimes taken a while between the two. >> As a side note, I anticipate that gap to be much much shorter these >> days, >> since the processes runs smoother for me now. >> >> Additionally, our front webpage, and the "newpkgs" mailing list, both >> actually get their information from the internal batching area :-} >> So we already have an "updated daily" reference of what is in that >> area. >> >> As mentioned previously, I could make the front web page updated >> hourly, if >> you like. >> Unless people really want an actual individual EMAIL to go out >> somewhere, >> every time a package hits that area. >> >> Do people want to see that? or is the insert on www.opencsw.org >> enough? >> (either once a day, or once an hour?) > > I wouldn't mind an email when a packages moves from one state to > another. Yes, to devel@ please. I guess we should keep maintainers@ free from automated posts. > I would also like an Atom feed with new and updated packages so > that people can follow the changes. Do you mind doing that yourself? Ihsan can set up a file on www.opencsw.org:/var/www/www.opencsw.org/htdocs/ where you can deliver the xml. > In the future I wouldn't mind including the change log of what's > changed. Where should that information come from? Best regards -- Dago From bonivart at opencsw.org Sun Nov 9 12:02:23 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 9 Nov 2008 12:02:23 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <4916BCC7.9000104@opencsw.org> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> Message-ID: <625385e30811090302s4266abf1p784d603a5ea3b59d@mail.gmail.com> On Sun, Nov 9, 2008 at 11:34 AM, Trygve Laugst?l wrote: > Jake Goerzen wrote: >> Currently installed SDL libraries on buildfarm: >> >> build8s% /opt/csw/bin/pkg-get -c | grep sdl >> libsdl 1.2.9 SAME >> sdlimage [Not installed] 1.2.4,REV=2006.05.03 >> sdlmixer [Not installed] 1.2.6,REV=2007.02.27 >> sdlnet [Not installed] 1.2.5,REV=2006.05.04 >> sdlsound [Not installed] 1.0.1,REV=2006.06.17 >> sdlttf [Not installed] 2.0.6,REV=2006.06.17 > > Would it be possible to run "pkg-get -c|grep -v SAME" and have it spit > out an email when stuff is outdated? pkgutil -e somebody at somewhere.com -- /peter From bonivart at opencsw.org Sun Nov 9 12:05:09 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 9 Nov 2008 12:05:09 +0100 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: References: <20081107115030.D95235@bolthole.com> <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org> <20081107122431.F95235@bolthole.com> <4916BC4F.8010606@opencsw.org> Message-ID: <625385e30811090305j6453d39bh89d59f7f7cb641cc@mail.gmail.com> On Sun, Nov 9, 2008 at 11:57 AM, Dagobert Michelsen wrote: > Yes, to devel@ please. I guess we should keep maintainers@ > free from automated posts. Why not to the newpkgs list? -- /peter From dam at opencsw.org Sun Nov 9 13:51:26 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 9 Nov 2008 13:51:26 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081108.16061000.3036193704@gyor.oxdrove.co.uk> References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> Message-ID: Hi James, Am 08.11.2008 um 17:06 schrieb James Lee: > On 08/11/08, 15:40:29, Dagobert Michelsen wrote > regarding > Re: [csw-maintainers] Java... again!: > >> jdk5-1.5.0_15,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz >> jdk5-1.5.0_15,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz >> jdk6-6u7,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz >> jdk6-6u7,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz > > Latest 1.5 is Update 16 > http://java.sun.com/javase/downloads/index_jdk5.jsp > > The latest 1.6 is Update 10. > http://java.sun.com/javase/downloads/index.jsp I got them from the archive page. Who can imagine archived versions would be old? Me??? Oh well... Heres some warmed up Java in : jre13-1.3.1_22,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz jre13-1.3.1_22,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz jre14-1.4.2_17,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz jre14-1.4.2_17,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz jre5-1.5.0_16,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz jre5-1.5.0_16,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz jre6-1.6.0_10,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz jre6-1.6.0_10,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz jdk13-1.3.1_22,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz jdk13-1.3.1_22,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz jdk14-1.4.2_17,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz jdk14-1.4.2_17,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz jdk5-1.5.0_16,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz jdk5-1.5.0_16,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz jdk6-1.6.0_10,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz jdk6-1.6.0_10,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz > It identifies itself: > > $ java -version > java version "1.6.0_10" > Java(TM) SE Runtime Environment (build 1.6.0_10-b33) > Java HotSpot(TM) Server VM (build 11.0-b15, mixed mode) > > So why use break the pattern of naming, I'd expect the package to be > identified similarly as "1.6.0_10". I should never have followed marketing numbers. The package now identified itself with the technical version number. James, do you mind testing these? Best regards -- Dago From phil at bolthole.com Sun Nov 9 16:49:25 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 9 Nov 2008 07:49:25 -0800 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <4916BCC7.9000104@opencsw.org>; from trygvel@opencsw.org on Sun, Nov 09, 2008 at 11:34:47AM +0100 References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> Message-ID: <20081109074925.F84797@bolthole.com> On Sun, Nov 09, 2008 at 11:34:47AM +0100, Trygve Laugst?l wrote: > Would it be possible to run "pkg-get -c|grep -v SAME" and have it spit > out an email when stuff is outdated? > fyi, pkg-get 4.0 "pkg-get -c" automatically skips "SAME". I had a beta version out months ago that did this, but of course it's lost to blastwave nukage now. I had THOUGHT I put a repackaged version up in our "testing" dir though. Hmmm.... From william at wbonnet.net Sun Nov 9 17:09:29 2008 From: william at wbonnet.net (William Bonnet) Date: Sun, 09 Nov 2008 17:09:29 +0100 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: <625385e30811090305j6453d39bh89d59f7f7cb641cc@mail.gmail.com> References: <20081107115030.D95235@bolthole.com> <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org> <20081107122431.F95235@bolthole.com> <4916BC4F.8010606@opencsw.org> <625385e30811090305j6453d39bh89d59f7f7cb641cc@mail.gmail.com> Message-ID: <49170B39.2060607@wbonnet.net> Peter Bonivart a ?crit : > On Sun, Nov 9, 2008 at 11:57 AM, Dagobert Michelsen wrote: > >> Yes, to devel@ please. I guess we should keep maintainers@ >> free from automated posts. >> > > Why not to the newpkgs list? > > newpkgs is supposed to be used only for release announcement ? isn't it ? From william at wbonnet.net Sun Nov 9 17:13:48 2008 From: william at wbonnet.net (William Bonnet) Date: Sun, 09 Nov 2008 17:13:48 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> Message-ID: <49170C3C.8060707@wbonnet.net> Hi > Do you mean this? > pkg-get -c|grep -v SAME|grep -v "Not installed" > > Should the email go to the farm manager to fix this ASAP > or once per day to devel@? > It is a good idea Maybe we should have a set of scripts for monitoring machines in the build farm ? Each machine in the farm would run the same scripts used for monitoring and reporting. Package installed on the build machine are one of the needs. We could also add disk space monitoring. Even if then problem has not yet been encountered it would be useful to report this before it happens :) We could also setup a nagios monitoring this kind of things. There is not yet a plugin used to monitor package installation, but i think it could be done. Cheers, W. From phil at bolthole.com Sun Nov 9 17:22:43 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 9 Nov 2008 08:22:43 -0800 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <49170C3C.8060707@wbonnet.net>; from william@wbonnet.net on Sun, Nov 09, 2008 at 05:13:48PM +0100 References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> <49170C3C.8060707@wbonnet.net> Message-ID: <20081109082243.H84797@bolthole.com> On Sun, Nov 09, 2008 at 05:13:48PM +0100, William Bonnet wrote: > > We could also setup a nagios monitoring this kind of things. There is > not yet a plugin used to monitor package installation, but i think it > could be done. Or... you could enable "email on install" in pkgadd, if you really want an alert sent everytime a package is installed. From bonivart at opencsw.org Sun Nov 9 19:27:20 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 9 Nov 2008 19:27:20 +0100 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: <49170B39.2060607@wbonnet.net> References: <20081107115030.D95235@bolthole.com> <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org> <20081107122431.F95235@bolthole.com> <4916BC4F.8010606@opencsw.org> <625385e30811090305j6453d39bh89d59f7f7cb641cc@mail.gmail.com> <49170B39.2060607@wbonnet.net> Message-ID: <625385e30811091027m3c8c5406pf0019e1e173547ef@mail.gmail.com> On Sun, Nov 9, 2008 at 5:09 PM, William Bonnet wrote: > newpkgs is supposed to be used only for release announcement ? isn't it ? Yes, but isn't this about just that, announcing that a package is being released to unstable? It's described as a weekly mailing list so it wouldn't be that low volume any more but it's more on target than devel to me. But it doesn't matter much where it goes, if someone thinks it's too noisy it's easy to filter out with the mail client. -- /peter From william at wbonnet.net Sun Nov 9 19:28:48 2008 From: william at wbonnet.net (William Bonnet) Date: Sun, 09 Nov 2008 19:28:48 +0100 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: <625385e30811091027m3c8c5406pf0019e1e173547ef@mail.gmail.com> References: <20081107115030.D95235@bolthole.com> <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org> <20081107122431.F95235@bolthole.com> <4916BC4F.8010606@opencsw.org> <625385e30811090305j6453d39bh89d59f7f7cb641cc@mail.gmail.com> <49170B39.2060607@wbonnet.net> <625385e30811091027m3c8c5406pf0019e1e173547ef@mail.gmail.com> Message-ID: <49172BE0.8010108@wbonnet.net> Peter Bonivart a ?crit : > On Sun, Nov 9, 2008 at 5:09 PM, William Bonnet wrote: > >> newpkgs is supposed to be used only for release announcement ? isn't it ? >> > > Yes, but isn't this about just that, announcing that a package is > being released to unstable? It's described as a weekly mailing list so > it wouldn't be that low volume any more but it's more on target than > devel to me. > Sure. I was thinking it was about instaled packages :) Sorry... I think it would be iteresting for users to receive both testing and unstable release. We may also have more users actally "testing" packages and more feedbacks. cheers From dam at opencsw.org Sun Nov 9 19:55:03 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 9 Nov 2008 19:55:03 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <49170C3C.8060707@wbonnet.net> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> <49170C3C.8060707@wbonnet.net> Message-ID: <77C43230-E691-4AFA-876B-0C3A5FB2D19A@opencsw.org> Hi William, Am 09.11.2008 um 17:13 schrieb William Bonnet: > Maybe we should have a set of scripts for monitoring machines in the > build farm ? Each machine in the farm would run the same scripts used > for monitoring and reporting. Package installed on the build machine > are > one of the needs. We could also add disk space monitoring. Even if > then > problem has not yet been encountered it would be useful to report this > before it happens :) I just packages the SE Toolkit and Orca. Good opportunity to eat our own dogfood. > We could also setup a nagios monitoring this kind of things. There is > not yet a plugin used to monitor package installation, but i think it > could be done. Are you volunteering for building an agent for this? ;-) BTW: Nagios was maintained by Alex Moore, who has retired. Making an updated Nagios would be nice too. Best regards -- Dago From dam at opencsw.org Sun Nov 9 20:57:17 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 9 Nov 2008 20:57:17 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <20081109082243.H84797@bolthole.com> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> <49170C3C.8060707@wbonnet.net> <20081109082243.H84797@bolthole.com> Message-ID: <8AB00139-0E57-41EE-9F95-FEEC84641090@opencsw.org> Am 09.11.2008 um 17:22 schrieb Philip Brown: > On Sun, Nov 09, 2008 at 05:13:48PM +0100, William Bonnet wrote: >> >> We could also setup a nagios monitoring this kind of things. There is >> not yet a plugin used to monitor package installation, but i think it >> could be done. > > Or... you could enable "email on install" in pkgadd, if you really > want an > alert sent everytime a package is installed. What feature is this? It doesn't seem to be documented in pkgadd(1m) or admin(4). Do you have a pointer for me? Thanks! -- Dago From bonivart at opencsw.org Sun Nov 9 21:22:30 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 9 Nov 2008 21:22:30 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <8AB00139-0E57-41EE-9F95-FEEC84641090@opencsw.org> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> <49170C3C.8060707@wbonnet.net> <20081109082243.H84797@bolthole.com> <8AB00139-0E57-41EE-9F95-FEEC84641090@opencsw.org> Message-ID: <625385e30811091222q174f2bf4y2b2d16eeb96eee3@mail.gmail.com> On Sun, Nov 9, 2008 at 8:57 PM, Dagobert Michelsen wrote: > What feature is this? It doesn't seem to be documented > in pkgadd(1m) or admin(4). Do you have a pointer for me? This is from the admin(4) page for Solaris 8: "mail Defines a list of users to whom mail should be sent following installation of a package. If the list is empty, no mail is sent. If the parameter is not present in the admin file, the default value of root is used. The ask value cannot be used with this parameter." http://docs.sun.com/app/docs/doc/806-0633/6j9vn6q29?l=en&a=view&q=admin(4)+solaris+8 -- /peter From dam at opencsw.org Sun Nov 9 21:26:48 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 9 Nov 2008 21:26:48 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <625385e30811091222q174f2bf4y2b2d16eeb96eee3@mail.gmail.com> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> <49170C3C.8060707@wbonnet.net> <20081109082243.H84797@bolthole.com> <8AB00139-0E57-41EE-9F95-FEEC84641090@opencsw.org> <625385e30811091222q174f2bf4y2b2d16eeb96eee3@mail.gmail.com> Message-ID: <645DE6F9-38AA-42E7-A634-38C755579B7C@opencsw.org> Hi, Am 09.11.2008 um 21:22 schrieb Peter Bonivart: > On Sun, Nov 9, 2008 at 8:57 PM, Dagobert Michelsen > wrote: >> What feature is this? It doesn't seem to be documented >> in pkgadd(1m) or admin(4). Do you have a pointer for me? > > This is from the admin(4) page for Solaris 8: > > "mail > > Defines a list of users to whom mail should be sent following > installation of a package. If the list is empty, no mail is sent. If > the parameter is not present in the admin file, the default value of > root is used. The ask value cannot be used with this parameter." > > http://docs.sun.com/app/docs/doc/806-0633/6j9vn6q29?l=en&a=view&q=admin(4)+solaris+8 Am 09.11.2008 um 17:22 schrieb Philip Brown: > On Sun, Nov 09, 2008 at 05:13:48PM +0100, William Bonnet wrote: >> >> We could also setup a nagios monitoring this kind of things. There is >> not yet a plugin used to monitor package installation, but i think it >> could be done. > > Or... you could enable "email on install" in pkgadd, if you really > want an > alert sent everytime a package is installed. I see. Does anyone feel the need I activate that on the buildfarms to mail to devel@ or is the versionmatrix enough? Best regards -- Dago From bonivart at opencsw.org Sun Nov 9 21:32:00 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 9 Nov 2008 21:32:00 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <645DE6F9-38AA-42E7-A634-38C755579B7C@opencsw.org> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> <49170C3C.8060707@wbonnet.net> <20081109082243.H84797@bolthole.com> <8AB00139-0E57-41EE-9F95-FEEC84641090@opencsw.org> <625385e30811091222q174f2bf4y2b2d16eeb96eee3@mail.gmail.com> <645DE6F9-38AA-42E7-A634-38C755579B7C@opencsw.org> Message-ID: <625385e30811091232y24e0f7c3l6235250088fb81c0@mail.gmail.com> On Sun, Nov 9, 2008 at 9:26 PM, Dagobert Michelsen wrote: > I see. Does anyone feel the need I activate that on the buildfarms > to mail to devel@ or is the versionmatrix enough? Too much info for me. The version matrix (which is great btw) in combination with "updates available" e-mails are enough for me. -- /peter From william at wbonnet.net Mon Nov 10 10:08:27 2008 From: william at wbonnet.net (William Bonnet) Date: Mon, 10 Nov 2008 10:08:27 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <645DE6F9-38AA-42E7-A634-38C755579B7C@opencsw.org> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> <49170C3C.8060707@wbonnet.net> <20081109082243.H84797@bolthole.com> <8AB00139-0E57-41EE-9F95-FEEC84641090@opencsw.org> <625385e30811091222q174f2bf4y2b2d16eeb96eee3@mail.gmail.com> <645DE6F9-38AA-42E7-A634-38C755579B7C@opencsw.org> Message-ID: <4917FA0B.1050803@wbonnet.net> hi > I see. Does anyone feel the need I activate that on the buildfarms > to mail to devel@ or is the versionmatrix enough? > I think both are interesting. IMHO i think that it would be interesting to have a buildfarm mailing list to which such email would be sent. It would be intersting for people running other builfarm to receive notification email when they have to install a package. Version matrix is a good tool, but i prefer to receive email when i have something to do, instead of going to a web page to see if i have something to do. As i said in a previous email, we could also send to this list notification like host up and down alerts. Next in my todo list is Finish FF3 and its dependencies today give you (Dago) access to the webserver running wordpress install my V240 and nagios. Cheers, W. From dam at opencsw.org Mon Nov 10 11:09:04 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 10 Nov 2008 11:09:04 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <4917FA0B.1050803@wbonnet.net> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> <49170C3C.8060707@wbonnet.net> <20081109082243.H84797@bolthole.com> <8AB00139-0E57-41EE-9F95-FEEC84641090@opencsw.org> <625385e30811091222q174f2bf4y2b2d16eeb96eee3@mail.gmail.com> <645DE6F9-38AA-42E7-A634-38C755579B7C@opencsw.org> <4917FA0B.1050803@wbonnet.net> Message-ID: <3CBD014C-ECC1-4D9A-BEC4-FE166092C33F@opencsw.org> Hi William, Am 10.11.2008 um 10:08 schrieb William Bonnet: >> I see. Does anyone feel the need I activate that on the buildfarms >> to mail to devel@ or is the versionmatrix enough? >> > > I think both are interesting. > > IMHO i think that it would be interesting to have a buildfarm mailing > list to which such email would be sent. It would be intersting for > people running other builfarm to receive notification email when they > have to install a package. There is already a mailing list for buildfarm managers: I don't know if self-subscription is enabled for that list. Otherwise Ihsan can add you to the list. If you are ready with your V240 we can try the emailing service. > Version matrix is a good tool, but i prefer > to receive email when i have something to do, instead of going to a > web > page to see if i have something to do. As i said in a previous > email, we > could also send to this list notification like host up and down > alerts. > > Next in my todo list is > > Finish FF3 and its dependencies today > give you (Dago) access to the webserver running wordpress > install my V240 and nagios. Excellent. Thanks! -- Dago From trygvel at opencsw.org Mon Nov 10 16:58:06 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Mon, 10 Nov 2008 16:58:06 +0100 Subject: [csw-maintainers] request pkg(s) installed on buildfarm In-Reply-To: <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> References: <315c02ae0811071356yde377b4kcb3c6cd86324be4d@mail.gmail.com> <4916BCC7.9000104@opencsw.org> <40F325C7-0094-4783-800A-AA0EDE01362D@opencsw.org> Message-ID: <49185A0E.8040602@opencsw.org> Dagobert Michelsen wrote: > Hi Trygve, > > Am 09.11.2008 um 11:34 schrieb Trygve Laugst?l: >> Would it be possible to run "pkg-get -c|grep -v SAME" and have it spit >> out an email when stuff is outdated? > > Do you mean this? > pkg-get -c|grep -v SAME|grep -v "Not installed" No, all packages should always be installed. > Should the email go to the farm manager to fix this ASAP > or once per day to devel@? To me, mailing the farm managers and the version matrix is sufficient. If stuff is missing I can nag the farm manager by pointing to the matrix. -- Trygve From trygvel at opencsw.org Mon Nov 10 16:59:46 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Mon, 10 Nov 2008 16:59:46 +0100 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: References: <20081107115030.D95235@bolthole.com> <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org> <20081107122431.F95235@bolthole.com> <4916BC4F.8010606@opencsw.org> Message-ID: <49185A72.9040606@opencsw.org> Dagobert Michelsen wrote: > Hi, > > Am 09.11.2008 um 11:32 schrieb Trygve Laugst?l: >> Philip Brown wrote: >>> Oh.... you are trying to keep an eye on the part between >>> >>> "i copy it into the batching area" >>> vs >>> "it goes public". >>> >>> because in the past, I have sometimes taken a while between the two. >>> As a side note, I anticipate that gap to be much much shorter these >>> days, >>> since the processes runs smoother for me now. >>> >>> Additionally, our front webpage, and the "newpkgs" mailing list, both >>> actually get their information from the internal batching area :-} >>> So we already have an "updated daily" reference of what is in that >>> area. >>> >>> As mentioned previously, I could make the front web page updated >>> hourly, if >>> you like. >>> Unless people really want an actual individual EMAIL to go out >>> somewhere, >>> every time a package hits that area. >>> >>> Do people want to see that? or is the insert on www.opencsw.org >>> enough? >>> (either once a day, or once an hour?) >> I wouldn't mind an email when a packages moves from one state to >> another. > > Yes, to devel@ please. I guess we should keep maintainers@ > free from automated posts. > >> I would also like an Atom feed with new and updated packages so >> that people can follow the changes. > > Do you mind doing that yourself? Ihsan can set up a file on > www.opencsw.org:/var/www/www.opencsw.org/htdocs/ where you > can deliver the xml. I can create the Atom XML, but I don't know how to get the data. If the data is in a SQL database I can make a php page that generate the file. >> In the future I wouldn't mind including the change log of what's >> changed. > > Where should that information come from? From the change log file that the maintainer deliver when the .pkg is uploaded :). I know it doesn't exist, but I (as a user) would like to know what has changed when new packages are installed. This is very useful information to browse when looking at the front page and wondering why there is a new package available. In particular for bug fixes. -- Trygve From phil at bolthole.com Mon Nov 10 17:47:05 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 10 Nov 2008 08:47:05 -0800 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: <49185A72.9040606@opencsw.org>; from trygvel@opencsw.org on Mon, Nov 10, 2008 at 04:59:46PM +0100 References: <20081107115030.D95235@bolthole.com> <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org> <20081107122431.F95235@bolthole.com> <4916BC4F.8010606@opencsw.org> <49185A72.9040606@opencsw.org> Message-ID: <20081110084705.A94907@bolthole.com> On Mon, Nov 10, 2008 at 04:59:46PM +0100, Trygve Laugst?l wrote: > >> In the future I wouldn't mind including the change log of what's > >> changed. > > > > Where should that information come from? > > From the change log file that the maintainer deliver when the .pkg is > uploaded :). I know it doesn't exist, but I (as a user) would like to > know what has changed when new packages are installed. This is very > useful information to browse when looking at the front page and > wondering why there is a new package available. In particular for bug fixes. We had this discussion a year or three ago on the maintainers list. Some of the issues were: for one thing, we couldnt agree on whether the "upstream" changes should be in this file or not. I personally would say "not". and as a side comment, the vast majority of "new packages" are simply due to "new version upstream". and the vast majority of csw-side changes, are "oops, I made a mistake". Most of which are not really anything the user would care about, beyond "ok i'm glad you fixed that dumb thing". From trygvel at opencsw.org Mon Nov 10 17:58:27 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Mon, 10 Nov 2008 17:58:27 +0100 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: <20081110084705.A94907@bolthole.com> References: <20081107115030.D95235@bolthole.com> <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org> <20081107122431.F95235@bolthole.com> <4916BC4F.8010606@opencsw.org> <49185A72.9040606@opencsw.org> <20081110084705.A94907@bolthole.com> Message-ID: <49186833.9070802@opencsw.org> Philip Brown wrote: > On Mon, Nov 10, 2008 at 04:59:46PM +0100, Trygve Laugst?l wrote: >>>> In the future I wouldn't mind including the change log of what's >>>> changed. >>> Where should that information come from? >> From the change log file that the maintainer deliver when the .pkg is >> uploaded :). I know it doesn't exist, but I (as a user) would like to >> know what has changed when new packages are installed. This is very >> useful information to browse when looking at the front page and >> wondering why there is a new package available. In particular for bug fixes. > > We had this discussion a year or three ago on the maintainers list. > Some of the issues were: for one thing, we couldnt agree on whether the > "upstream" changes should be in this file or not. > > I personally would say "not". Me too, but I would point to the upstream release notes if available. > and as a side comment, the vast majority of "new packages" are simply due > to "new version upstream". and the vast majority of csw-side changes, are > "oops, I made a mistake". Most of which are not really anything the user > would care about, beyond "ok i'm glad you fixed that dumb thing". Know if it was only because of a upstream change or a packaging bug would be nice to know. I know I've made a few releases because of packaging issues. Most because I'm still new, but I wouldn't mind knowing it. From a PR perspective it will show more precisely what we're doing, but that you can also read from an atom feed. -- Trygve From phil at bolthole.com Mon Nov 10 18:08:42 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 10 Nov 2008 09:08:42 -0800 Subject: [csw-maintainers] pkg-get 4.0beta Message-ID: <20081110090842.B94907@bolthole.com> FYI: I've done a quickie repackage of pkg-get 4.0beta. http://mirror.opencsw.org/testing/pkg_get-4,0,REV=2008.11.10.beta-SunOS5.8-all-CSW.pkg It's not feature-complete, and has a few bugs in it, im sure. But it does have things like: pkg-get -c(compare) only shows installed packages (It DOES show "SAME" though, so my mistake on my prior claim about that) pkg-get -c -a shows remote versions of "all" packages, and compares to installed, if there is a version installed. pkg-get -u -v shows how many bytes would be downloaded, AND shows dependancies that would have to be downloaded. Sample: $ /opt/csw/bin/pkg-get -v -u pidgin DEBUG-ONLY/VERBOSE MODE: level=1 CSWpidgin pidgin 10763591 bytes CSWpng png 587563 bytes There are also a few misc bugfixes here and there. This is actually code I wrote waay back, many months ago, and released as a beta package, that got buried with Dennis's powerplay. January 2008, even. Although I dont remember when I published the prior "beta" package. Now that things have calmed down, I will hopefully be able to bring it up to good enough quality for a full release. Particularly if people show interest and give me a nudge , or some feedback ;-) From phil at bolthole.com Mon Nov 10 18:10:34 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 10 Nov 2008 09:10:34 -0800 Subject: [csw-maintainers] Contents of devel@ list In-Reply-To: <49186833.9070802@opencsw.org>; from trygvel@opencsw.org on Mon, Nov 10, 2008 at 05:58:27PM +0100 References: <20081107115030.D95235@bolthole.com> <5B86A5A9-539D-4B33-ADA1-1396927B59B6@opencsw.org> <20081107122431.F95235@bolthole.com> <4916BC4F.8010606@opencsw.org> <49185A72.9040606@opencsw.org> <20081110084705.A94907@bolthole.com> <49186833.9070802@opencsw.org> Message-ID: <20081110091034.C94907@bolthole.com> On Mon, Nov 10, 2008 at 05:58:27PM +0100, Trygve Laugst?l wrote: > > Know if it was only because of a upstream change or a packaging bug > would be nice to know. Well, that was ONE "nice" thing about the "REV=xxxx" field being optional except for secondary release of the same version :-} If there was no REV field, you could be fairly sure it was a simple upstream update. > From a PR perspective it will show more precisely what we're doing, but > that you can also read from an atom feed. I think it could be nice to support as some kind of optional thing. From phil at bolthole.com Mon Nov 10 20:39:14 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 10 Nov 2008 11:39:14 -0800 Subject: [csw-maintainers] newpkgs notes, on why packages may be held there Message-ID: <20081110113914.G94907@bolthole.com> FYI: Becaue I tend to forget, myself, I have now started to keep notes on why particular packages are being 'held' in newpkgs. I used to keep an old file in my home dir, but it will be /home/newpkgs/00-README from now on. Nice and easy to spot now. and also FYI: I always email people when there are issues with their packages. There is no additional requirement for people to go read that file themselves. This is just so I can delete my old emails safely, without forgetting why a package is sitting there. Or as a reminder to YOU, if you happen to forget the issue with your own package ;-) From phil at bolthole.com Tue Nov 11 16:05:59 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 11 Nov 2008 07:05:59 -0800 Subject: [csw-maintainers] ARCH=all packages Message-ID: <20081111070559.C90125@bolthole.com> Peter B. and I are having a disagreement about the concept of ARCH=all packages, so I thought I would bring the discussion here. The issue is that he wishes to bundle specific binaries for wget in his pkgutil package, AND call it ARCH=all. (he wants to bundle one for sparc and one for x86) I suggested that he either remove the binaries and use pure perl, (either with a full wget replacement, or to use it to download "the appropriate binary") or split it up into two separate packages, with appropriate ARCH settings for the binary he includes in each one. He refuses to take either path, or offer a third one. Our standards pages say, http://www.opencsw.org/standards/build "{ARCH} is usually the output of `uname -p`. But for certain special packages that run on all solaris hardware, or are otherwise architecture-neutral, it may be preferable to have ARCH=all " I say that this means that archtecture specific binaries, should not be in "ARCH=all" packages. Even if you do not agree that the words clearly state that, it was certainly my INTENTION when I wrote the standard. I wanted "ARCH=all" to clearly indicate, "this package will work EVERYWHERE, it will never need recompiling, and it is safe to be shared in some kind of NFS /opt/csw for any and all solaris machines to use." In other words, ARCH=all should be reserved for things like raw arch-neutral data files, docs, java, and shellscripts/perl/python. (I originally intended to use "ARCH=any"... however, I followed sun's lead; sun uses ARCH=all, and does not use ARCH=any, to the best of my knowlege, for this purpose) What are peoples' comments on this? From pfelecan at blastwave.org Tue Nov 11 16:13:58 2008 From: pfelecan at blastwave.org (Peter FELECAN) Date: Tue, 11 Nov 2008 16:13:58 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111070559.C90125@bolthole.com> (Philip Brown's message of "Tue\, 11 Nov 2008 07\:05\:59 -0800") References: <20081111070559.C90125@bolthole.com> Message-ID: Philip Brown writes: > In other words, ARCH=all should be reserved for things like raw > arch-neutral data files, docs, java, and shellscripts/perl/python. +1 -- Peter From james at opencsw.org Tue Nov 11 17:03:21 2008 From: james at opencsw.org (James Lee) Date: Tue, 11 Nov 2008 16:03:21 GMT Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111070559.C90125@bolthole.com> References: <20081111070559.C90125@bolthole.com> Message-ID: <20081111.16032100.3120983528@gyor.oxdrove.co.uk> On 11/11/08, 15:05:59, Philip Brown wrote regarding [csw-maintainers] ARCH=all packages: > The issue is that he wishes to bundle specific binaries for wget in his > pkgutil package, AND call it ARCH=all. > (he wants to bundle one for sparc and one for x86) > I suggested that he either remove the binaries and use pure perl, > (either with a full wget replacement, or to use it to download > "the appropriate binary") > or split it up into two separate packages, with appropriate ARCH settings > for the binary he includes in each one. > Our standards pages say, > http://www.opencsw.org/standards/build > "{ARCH} is usually the output of `uname -p`. But for certain special > packages that run on all solaris hardware, or are otherwise > architecture-neutral, it may be preferable to have ARCH=all " > I say that this means that archtecture specific binaries, should not be > in "ARCH=all" packages. Even if you do not agree that the words clearly > state that, it was certainly my INTENTION when I wrote the standard. > I wanted "ARCH=all" to clearly indicate, "this package will work > EVERYWHERE, it will never need recompiling, and it is safe to be shared > in some kind of NFS /opt/csw for any and all solaris machines to use." We do make arch specific packages that include binaries that don't run on all machines, eg, amd64 files in i386 packages and vis2 files in sparc packages. Therefore if an isaexec like mechanism is used to invoke wget then it meets "this package will work EVERYWHERE". CSWelipse used to be an example of this, from eclipse-3.0-SunOS5.8-all-CSW.pkg.gz: /opt/csw/lib/eclipse/eclipse.i386 /opt/csw/lib/eclipse/eclipse.sparc out of an 80MB package. Unlike eclipse, wget is many times bigger that pkgutil so why not just make each arch specific. We normally split out arch neutral files to save storage space eg, the language files of OpenOffice.org, but here there is only small saving on mirror storage but offset by a large increase user download and user storage. -rwxr-xr-x 1 james staff 164576 Nov 10 17:25 wget-i386* -rwxr-xr-x 1 james staff 224672 Nov 10 17:25 wget-sparc* -rwxr-xr-x 1 james staff 29124 Nov 11 08:41 pkgutil* The gain is what? To offer a single download for pkgutil and so simplify the first step documentation and set up actions. My choice is use perl as the default downloader. Task one for the tool can be to install CSWwget. James. From bonivart at opencsw.org Tue Nov 11 17:09:58 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Tue, 11 Nov 2008 17:09:58 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111070559.C90125@bolthole.com> References: <20081111070559.C90125@bolthole.com> Message-ID: <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com> On Tue, Nov 11, 2008 at 4:05 PM, Philip Brown wrote: > He refuses to take either path, or offer a third one. Because it works fine the way it is and it's easier for the users to not have to make a choice since this is likely to be the first package they download manually to get going. Mac packages often contain code for both PowerPC and x86 so they don't have to choose. It's the same thing. You approved the two first versions of pkgutil with exactly the same design. Not to mention your own pkg-get is incorrectly named without the REV-field which is real easy to read from the standard without any convoluted interpretations. You also chose to not gzip it so it would be easier for your users. This is also for being helpful to the users. But that obviously doesn't mean anything to you when it's not your own package. > In other words, ARCH=all should be reserved for things like raw > arch-neutral data files, docs, java, and shellscripts/perl/python. Which is exactly what pkgutil contains from a user point of view, three perl scripts in bin. -- /peter From bwalton at opencsw.org Tue Nov 11 17:16:59 2008 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 11 Nov 2008 11:16:59 -0500 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111070559.C90125@bolthole.com> References: <20081111070559.C90125@bolthole.com> Message-ID: <1226420167-sup-615@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Tue Nov 11 10:05:59 -0500 2008: > Peter B. and I are having a disagreement about the concept of ARCH=all > packages, so I thought I would bring the discussion here. > > The issue is that he wishes to bundle specific binaries for wget in his > pkgutil package, AND call it ARCH=all. > (he wants to bundle one for sparc and one for x86) > > I suggested that he either remove the binaries and use pure perl, > (either with a full wget replacement, or to use it to download > "the appropriate binary") > or split it up into two separate packages, with appropriate ARCH settings > for the binary he includes in each one. A few ideas: 1. Does the standard perl as shipped on sol8 include Net::HTTP and a checksumming module sufficient for pulling down a wget binary and verifying it? If so, I think that would ultimately be the best solution, as you don't want these 'spare' wget binaries after the system is 'csw bootstrapped' anyway. 2. Alternately, the tool could bootstrap the installation of Net::HTTP from cpan? This treads into territory that could cause problems too, since it will affect things outside of /opt/csw. 3. Include ascii-armored(/clear-signed?) versions of the applicable wget binaries in the share/doc/pkgutil/bootstrap part of the packages' file tree? > I say that this means that architecture specific binaries, should not be in > "ARCH=all" packages. Even if you do not agree that the words clearly state > that, it was certainly my INTENTION when I wrote the standard. > I wanted "ARCH=all" to clearly indicate, "this package will work > EVERYWHERE, it will never need recompiling, and it is safe to be shared in > some kind of NFS /opt/csw for any and all solaris machines to use." I agree with this and think it's best to adhere to it if at all possible. If any package were to be made an exception though, this would be a good candidate in my estimation since it has a pivotal role in getting a system boot-strapped to csw in the first place. > In other words, ARCH=all should be reserved for things like raw > arch-neutral data files, docs, java, and shellscripts/perl/python. If the wget binaries were no longer in binary form (ascii armored), would that skirt the definition enough to appease all? pkgutil would simply treat them as data and use the appropriate one to pull down the CSWwget package initially... The definition of ARCH=all could also be taken to mean that the package will provide equal _functionality_ on all supported machines, which in this case it would. I'm not suggesting that this _should_ be how the definition is read, just that it _could_ be read that way. -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 Nov 11 17:24:49 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 11 Nov 2008 08:24:49 -0800 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <1226420167-sup-615@ntdws12.chass.utoronto.ca>; from bwalton@opencsw.org on Tue, Nov 11, 2008 at 11:16:59AM -0500 References: <20081111070559.C90125@bolthole.com> <1226420167-sup-615@ntdws12.chass.utoronto.ca> Message-ID: <20081111082449.B66221@bolthole.com> On Tue, Nov 11, 2008 at 11:16:59AM -0500, Ben Walton wrote: > A few ideas: > > 1. Does the standard perl as shipped on sol8 include Net::HTTP no. only IO::Socket comes close. I suggested that peter include Net::Ftp and use that. > 3. Include ascii-armored(/clear-signed?) versions of the applicable wget > binaries in the share/doc/pkgutil/bootstrap part of the packages' file > tree? It's not the issue of "binary" so much as it is "arch specific". ascii "arch specific" data is not allowed in "ARCH=all" either. As a side note: At the top level of every mirror is "wget.sparc" and "wget.i386". it is fairly easy to either use perl-ftp, or /bin/ftp, to grab them automatically, if needed. From phil at bolthole.com Tue Nov 11 17:30:44 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 11 Nov 2008 08:30:44 -0800 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com>; from bonivart@opencsw.org on Tue, Nov 11, 2008 at 05:09:58PM +0100 References: <20081111070559.C90125@bolthole.com> <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com> Message-ID: <20081111083044.C66221@bolthole.com> On Tue, Nov 11, 2008 at 05:09:58PM +0100, Peter Bonivart wrote: > > You approved the two first versions of pkgutil with exactly the same > design. I didnt notice the problem earlier. If I did, I wouldnt have let it through then either. > Not to mention your own pkg-get is incorrectly named without > the REV-field I fixed that. > You also chose to not gzip it so it would be easier for your users. As I already pointed out in email, that is a *requirement* for use, since solaris 8 core does not include gzip, and it is logical that they would want to use pkg-get to install gzip. If you had said you wanted to do similarly with yours, I would have said that's fine, for the same reasons. > > In other words, ARCH=all should be reserved for things like raw > > arch-neutral data files, docs, java, and shellscripts/perl/python. > > Which is exactly what pkgutil contains from a user point of view, > three perl scripts in bin. It doesnt matter what the user "sees". It matters that the description/labelling of the package, match the package. The contents of the package, do not match the above description of ARCH=all $ file CSWpkgutil/root/opt/csw/libexec/pkgutil/wget-i386 CSWpkgutil/root/opt/csw/libexec/pkgutil/wget-i386: ELF 32-bit LSB executable 80386 Version 1, dynamically linked, stripped From william at wbonnet.net Tue Nov 11 17:31:18 2008 From: william at wbonnet.net (William Bonnet) Date: Tue, 11 Nov 2008 17:31:18 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: References: <20081111070559.C90125@bolthole.com> Message-ID: <4919B356.6070006@wbonnet.net> Peter FELECAN a ?crit : > Philip Brown writes: > > >> In other words, ARCH=all should be reserved for things like raw >> arch-neutral data files, docs, java, and shellscripts/perl/python. >> > > +1 > +1 From william at wbonnet.net Tue Nov 11 17:33:32 2008 From: william at wbonnet.net (William Bonnet) Date: Tue, 11 Nov 2008 17:33:32 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111.16032100.3120983528@gyor.oxdrove.co.uk> References: <20081111070559.C90125@bolthole.com> <20081111.16032100.3120983528@gyor.oxdrove.co.uk> Message-ID: <4919B3DC.1090301@wbonnet.net> Hi James > Therefore if an isaexec like mechanism is used to invoke wget then it > meets "this package will work EVERYWHERE". CSWelipse used to be an > example of this, from eclipse-3.0-SunOS5.8-all-CSW.pkg.gz: > /opt/csw/lib/eclipse/eclipse.i386 > /opt/csw/lib/eclipse/eclipse.sparc > out of an 80MB package. > Yes but it is an old example ;) Now you have an eclipse common packge which is arch independent, and two arch dependent package. The recent version have more than one binary to provide. Cheers, W. From bwalton at opencsw.org Tue Nov 11 17:56:18 2008 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 11 Nov 2008 11:56:18 -0500 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111082449.B66221@bolthole.com> References: <20081111070559.C90125@bolthole.com> <1226420167-sup-615@ntdws12.chass.utoronto.ca> <20081111082449.B66221@bolthole.com> Message-ID: <1226420869-sup-1782@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Tue Nov 11 11:24:49 -0500 2008: > only IO::Socket comes close. Using IO::Socket to approximate wget would be painful. > > 3. Include ascii-armored(/clear-signed?) versions of the applicable wget > > binaries in the share/doc/pkgutil/bootstrap part of the packages' file > > tree? > > It's not the issue of "binary" so much as it is "arch specific". > ascii "arch specific" data is not allowed in "ARCH=all" either. Taking this stance would mean that shipping asm code examples for different architectures in a doc/$assembler/examples would violate the ARCH=all requirements too, no? > As a side note: > At the top level of every mirror is "wget.sparc" and "wget.i386". > it is fairly easy to either use perl-ftp, or /bin/ftp, to grab them > automatically, if needed. Yes, that would work too...automating /bin/ftp is a pita though. And I don't think it supports PASSIVE ftp, which may be an issue at some sites. HTTP is an easier target protocol from this vantage, although lack of a nice tool by default is why we're having this discussion in the first place! :) I don't really care one way or another how this is eventually handled. Ease of use for the end users should be the key requirement, so any solution that allows them to forgo an extra manual download works for me. 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 Nov 11 18:05:34 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 11 Nov 2008 09:05:34 -0800 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <1226420869-sup-1782@ntdws12.chass.utoronto.ca>; from bwalton@opencsw.org on Tue, Nov 11, 2008 at 11:56:18AM -0500 References: <20081111070559.C90125@bolthole.com> <1226420167-sup-615@ntdws12.chass.utoronto.ca> <20081111082449.B66221@bolthole.com> <1226420869-sup-1782@ntdws12.chass.utoronto.ca> Message-ID: <20081111090534.D66221@bolthole.com> On Tue, Nov 11, 2008 at 11:56:18AM -0500, Ben Walton wrote: > > It's not the issue of "binary" so much as it is "arch specific". > > ascii "arch specific" data is not allowed in "ARCH=all" either. > > Taking this stance would mean that shipping asm code examples for > different architectures in a doc/$assembler/examples would violate the > ARCH=all requirements too, no? oooo... way to dance the line right to the edge :-) Giving "examples", I think is equivalent to "documentation", though. From bwalton at opencsw.org Tue Nov 11 18:11:21 2008 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 11 Nov 2008 12:11:21 -0500 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111090534.D66221@bolthole.com> References: <20081111070559.C90125@bolthole.com> <1226420167-sup-615@ntdws12.chass.utoronto.ca> <20081111082449.B66221@bolthole.com> <1226420869-sup-1782@ntdws12.chass.utoronto.ca> <20081111090534.D66221@bolthole.com> Message-ID: <1226423256-sup-2969@ntdws12.chass.utoronto.ca> Excerpts from Philip Brown's message of Tue Nov 11 12:05:34 -0500 2008: > On Tue, Nov 11, 2008 at 11:56:18AM -0500, Ben Walton wrote: > > > It's not the issue of "binary" so much as it is "arch specific". > > > ascii "arch specific" data is not allowed in "ARCH=all" either. > > > > Taking this stance would mean that shipping asm code examples for > > different architectures in a doc/$assembler/examples would violate the > > ARCH=all requirements too, no? > > oooo... way to dance the line right to the edge :-) > Giving "examples", I think is equivalent to "documentation", though. Nobody said we couldn't have fun here! :) You could look at it as something potentially consumable by the binaries that ship with the package, which would allow wget binaries in ascii form to get through the definition too. Anyway, if there is a reasonable way to acquire wget without bending the definitions, that's clearly better. -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 bonivart at opencsw.org Tue Nov 11 18:33:27 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Tue, 11 Nov 2008 18:33:27 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111083044.C66221@bolthole.com> References: <20081111070559.C90125@bolthole.com> <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com> <20081111083044.C66221@bolthole.com> Message-ID: <625385e30811110933s17a2940fk987fbb6734910f5f@mail.gmail.com> On Tue, Nov 11, 2008 at 5:30 PM, Philip Brown wrote: > It doesnt matter what the user "sees". It matters that the > description/labelling of the package, match the package. > The contents of the package, do not match the above description of ARCH=all That's just your interpretation to make this more complicated than it needs to be. The package runs on all architectures we support and should therefor be delivered as one package, that's a much more reasonable interpretation. There's no harm in it and it's simpler for the user to get going. -- /peter From a.cervellin at acm.org Tue Nov 11 18:55:02 2008 From: a.cervellin at acm.org (Alessio) Date: Tue, 11 Nov 2008 18:55:02 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <625385e30811110933s17a2940fk987fbb6734910f5f@mail.gmail.com> References: <20081111070559.C90125@bolthole.com> <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com> <20081111083044.C66221@bolthole.com> <625385e30811110933s17a2940fk987fbb6734910f5f@mail.gmail.com> Message-ID: <4919C6F6.90404@acm.org> Peter Bonivart wrote: > On Tue, Nov 11, 2008 at 5:30 PM, Philip Brown wrote: >> It doesnt matter what the user "sees". It matters that the >> description/labelling of the package, match the package. >> The contents of the package, do not match the above description of ARCH=all > > That's just your interpretation to make this more complicated than it > needs to be. The package runs on all architectures we support and > should therefor be delivered as one package, that's a much more > reasonable interpretation. > > There's no harm in it and it's simpler for the user to get going. +1 From phil at bolthole.com Tue Nov 11 19:05:30 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 11 Nov 2008 10:05:30 -0800 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <4919C6F6.90404@acm.org>; from a.cervellin@acm.org on Tue, Nov 11, 2008 at 06:55:02PM +0100 References: <20081111070559.C90125@bolthole.com> <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com> <20081111083044.C66221@bolthole.com> <625385e30811110933s17a2940fk987fbb6734910f5f@mail.gmail.com> <4919C6F6.90404@acm.org> Message-ID: <20081111100530.E66221@bolthole.com> On Tue, Nov 11, 2008 at 06:55:02PM +0100, Alessio wrote: > Peter Bonivart wrote: > > On Tue, Nov 11, 2008 at 5:30 PM, Philip Brown wrote: > >> It doesnt matter what the user "sees". It matters that the > >> description/labelling of the package, match the package. > >> The contents of the package, do not match the above description of ARCH=all > > > > That's just your interpretation to make this more complicated than it > > needs to be. The package runs on all architectures we support and > > should therefor be delivered as one package, that's a much more > > reasonable interpretation. > > > > There's no harm in it and it's simpler for the user to get going. > > +1 Are you still a maintainer here Alessio? I thought that you only packaged for blastwave.org now? From a.cervellin at acm.org Tue Nov 11 19:33:13 2008 From: a.cervellin at acm.org (Alessio) Date: Tue, 11 Nov 2008 19:33:13 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111100530.E66221@bolthole.com> References: <20081111070559.C90125@bolthole.com> <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com> <20081111083044.C66221@bolthole.com> <625385e30811110933s17a2940fk987fbb6734910f5f@mail.gmail.com> <4919C6F6.90404@acm.org> <20081111100530.E66221@bolthole.com> Message-ID: <4919CFE9.6040600@acm.org> Philip Brown wrote: > On Tue, Nov 11, 2008 at 06:55:02PM +0100, Alessio wrote: >> Peter Bonivart wrote: >>> On Tue, Nov 11, 2008 at 5:30 PM, Philip Brown wrote: >>>> It doesnt matter what the user "sees". It matters that the >>>> description/labelling of the package, match the package. >>>> The contents of the package, do not match the above description of ARCH=all >>> That's just your interpretation to make this more complicated than it >>> needs to be. The package runs on all architectures we support and >>> should therefor be delivered as one package, that's a much more >>> reasonable interpretation. >>> >>> There's no harm in it and it's simpler for the user to get going. >> +1 > > Are you still a maintainer here Alessio? no, i didn't give up, as i always said - because i like to be clear - i join both the projects waiting to see how things are organized and how much *open* are these projects. and of course, i'm not the only maintainer in this situation. actually, the future does not seem to be clear on blastwave nor on opencsw (maybe after the IRL meeting...) whenever i'll leave this project, i'll just announce that. in the meanwhile if someone wants to take over some of my packages, he's of course free to do so. > I thought that you only packaged for blastwave.org now? the only package i released recently in the blastwave catalog is seamonkey, and i've not yet released it on csw because i still have to learn gar. From phil at bolthole.com Tue Nov 11 19:48:28 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 11 Nov 2008 10:48:28 -0800 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <4919CFE9.6040600@acm.org>; from a.cervellin@acm.org on Tue, Nov 11, 2008 at 07:33:13PM +0100 References: <20081111070559.C90125@bolthole.com> <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com> <20081111083044.C66221@bolthole.com> <625385e30811110933s17a2940fk987fbb6734910f5f@mail.gmail.com> <4919C6F6.90404@acm.org> <20081111100530.E66221@bolthole.com> <4919CFE9.6040600@acm.org> Message-ID: <20081111104828.F66221@bolthole.com> On Tue, Nov 11, 2008 at 07:33:13PM +0100, Alessio wrote: > > I thought that you only packaged for blastwave.org now? > > the only package i released recently in the blastwave catalog is > seamonkey, and i've not yet released it on csw because i still have to > learn gar. "have to" is rather an overstatement. There is still no requirement to put things in gar, before putting a package in newpkgs here. From a.cervellin at acm.org Tue Nov 11 19:51:22 2008 From: a.cervellin at acm.org (Alessio) Date: Tue, 11 Nov 2008 19:51:22 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111104828.F66221@bolthole.com> References: <20081111070559.C90125@bolthole.com> <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com> <20081111083044.C66221@bolthole.com> <625385e30811110933s17a2940fk987fbb6734910f5f@mail.gmail.com> <4919C6F6.90404@acm.org> <20081111100530.E66221@bolthole.com> <4919CFE9.6040600@acm.org> <20081111104828.F66221@bolthole.com> Message-ID: <4919D42A.2060306@acm.org> Philip Brown wrote: > On Tue, Nov 11, 2008 at 07:33:13PM +0100, Alessio wrote: >>> I thought that you only packaged for blastwave.org now? >> the only package i released recently in the blastwave catalog is >> seamonkey, and i've not yet released it on csw because i still have to >> learn gar. > > "have to" is rather an overstatement. There is still no requirement to put > things in gar, before putting a package in newpkgs here. i thought GAR was the standard adopted for opencsw... does this mean we can still package the old way and continue to ignore gar? From dam at opencsw.org Tue Nov 11 19:57:45 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 11 Nov 2008 19:57:45 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <4919D42A.2060306@acm.org> References: <20081111070559.C90125@bolthole.com> <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com> <20081111083044.C66221@bolthole.com> <625385e30811110933s17a2940fk987fbb6734910f5f@mail.gmail.com> <4919C6F6.90404@acm.org> <20081111100530.E66221@bolthole.com> <4919CFE9.6040600@acm.org> <20081111104828.F66221@bolthole.com> <4919D42A.2060306@acm.org> Message-ID: Hi Alessio, Am 11.11.2008 um 19:51 schrieb Alessio: > Philip Brown wrote: >> On Tue, Nov 11, 2008 at 07:33:13PM +0100, Alessio wrote: >> >>> I thought that you only packaged for blastwave.org now? >>> the only package i released recently in the blastwave catalog is >>> seamonkey, and i've not yet released it on csw because i still >>> have to >>> learn gar. >> >> "have to" is rather an overstatement. There is still no requirement >> to put >> things in gar, before putting a package in newpkgs here. > > i thought GAR was the standard adopted for opencsw... does this mean > we > can still package the old way and continue to ignore gar? At this moment it is possible to deliver packages which have no build description in GAR, yes. I am in favor of changing this when we have a usable documentation for GAR which we don't have yet. I have converted some documentation at but especially the tutorial is not finished, the new features are not document and there is no reference section. But yes, as of today you can submit packages built with everything you want. Best regards -- Dago From dam at opencsw.org Tue Nov 11 19:59:31 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 11 Nov 2008 19:59:31 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111100530.E66221@bolthole.com> References: <20081111070559.C90125@bolthole.com> <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com> <20081111083044.C66221@bolthole.com> <625385e30811110933s17a2940fk987fbb6734910f5f@mail.gmail.com> <4919C6F6.90404@acm.org> <20081111100530.E66221@bolthole.com> Message-ID: <2728D8EC-6849-4533-A131-28FF5E4C3C11@opencsw.org> Hi Phil, Am 11.11.2008 um 19:05 schrieb Philip Brown: > On Tue, Nov 11, 2008 at 06:55:02PM +0100, Alessio wrote: >> +1 > > Are you still a maintainer here Alessio? Yes, because he promised to build a new pbzip2 for me which can (finally!) compress streams from stdin :-) Best regards -- Dago From phil at bolthole.com Tue Nov 11 20:00:38 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 11 Nov 2008 11:00:38 -0800 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <4919D42A.2060306@acm.org>; from a.cervellin@acm.org on Tue, Nov 11, 2008 at 07:51:22PM +0100 References: <20081111070559.C90125@bolthole.com> <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com> <20081111083044.C66221@bolthole.com> <625385e30811110933s17a2940fk987fbb6734910f5f@mail.gmail.com> <4919C6F6.90404@acm.org> <20081111100530.E66221@bolthole.com> <4919CFE9.6040600@acm.org> <20081111104828.F66221@bolthole.com> <4919D42A.2060306@acm.org> Message-ID: <20081111110038.G66221@bolthole.com> On Tue, Nov 11, 2008 at 07:51:22PM +0100, Alessio wrote: > i thought GAR was the standard adopted for opencsw... does this mean we > can still package the old way and continue to ignore gar? At this time, yes. From dam at opencsw.org Tue Nov 11 20:35:15 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 11 Nov 2008 20:35:15 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111070559.C90125@bolthole.com> References: <20081111070559.C90125@bolthole.com> Message-ID: <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> Hi, Am 11.11.2008 um 16:05 schrieb Philip Brown: > Our standards pages say, > > http://www.opencsw.org/standards/build > "{ARCH} is usually the output of `uname -p`. But for certain special > packages that run on all solaris hardware, or are otherwise > architecture-neutral, it may be preferable to have ARCH=all " Well, the standard is not clear in this point. It could mean (a) the package doesn't contain data which is interpreted differently on different platforms (b) the package can be used on any platform, irregardless of how this is achieved. > I say that this means that archtecture specific binaries, should not > be in > "ARCH=all" packages. Complying to a standard is not a virtue on its own. When you wrote this you had an idea what you invented it for. The only thing I can think of is to save disk space. We may discuss here "cleanlyness of implementation" or "pureness of packages", but does it really get to the point? IMHO the point is "Does it work?" And providing multiple binaries in one package does work. There was the argument of diskspace when installed. This can be easily solved by putting the different binaries in separate install classes (like 'sparc' and 'i386') and install only the binary needed. > Even if you do not agree that the words clearly state > that, it was certainly my INTENTION when I wrote the standard. That's the nice thing about standards, isn't it? ;-) For myself I maintain the SE Toolkit (RICHPse), which traditionally is a package that contains binaries for sparc and x86 for maximum ease of use. However, I made two packages because having one large package is not easier for the users. But converting the build-infrastructure from the package was hell :-P ...and now please forget all of what I wrote above. Because those were technical arguments. Including binaries for sparc and i386 does work, and having two packages works also. The whole discussion is not technical. So gentlemen, please: Peter: Is it really that important to have one fat package instead of two? An admin usually does know on which platform he is on. Will the package be installed on NFS and would it be run from sparc and i386 at the same time? I guess not. So two packages won't hurt and would fully comply with the OpenCSW standard without further discussion. Phil: The standard is not clear here, regardless of what you intended with it. The package does work and it is usually the responsibility of the maintainer to build the package in the best way he thinks. The release manager (you :-) can give advice on improvements, but if the maintainer is reluctant to implement them the package must be released. Unless, of course, it violates the standard... So, Peter, would you please deliver two packages and you, Phil, then release the combined package? ;-) Best regards -- Dago From a.cervellin at acm.org Tue Nov 11 20:43:03 2008 From: a.cervellin at acm.org (Alessio) Date: Tue, 11 Nov 2008 20:43:03 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <2728D8EC-6849-4533-A131-28FF5E4C3C11@opencsw.org> References: <20081111070559.C90125@bolthole.com> <625385e30811110809s5e96eca2qd45e61cf2018c450@mail.gmail.com> <20081111083044.C66221@bolthole.com> <625385e30811110933s17a2940fk987fbb6734910f5f@mail.gmail.com> <4919C6F6.90404@acm.org> <20081111100530.E66221@bolthole.com> <2728D8EC-6849-4533-A131-28FF5E4C3C11@opencsw.org> Message-ID: <4919E047.5070300@acm.org> Dagobert Michelsen wrote: > Hi Phil, > > Am 11.11.2008 um 19:05 schrieb Philip Brown: >> On Tue, Nov 11, 2008 at 06:55:02PM +0100, Alessio wrote: >>> +1 >> Are you still a maintainer here Alessio? > > Yes, because he promised to build a new pbzip2 for me > which can (finally!) compress streams from stdin :-) and as you could have seen, i have not yet released it even for blastwave. i downloaded the sources and had some minor problems packaging it, but i promise i'll do. From bonivart at opencsw.org Tue Nov 11 22:13:04 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Tue, 11 Nov 2008 22:13:04 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> Message-ID: <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> On Tue, Nov 11, 2008 at 8:35 PM, Dagobert Michelsen wrote: > Peter: Is it really that important to have one fat package > instead of two? An admin usually does know on which platform > he is on. Will the package be installed on NFS and would it > be run from sparc and i386 at the same time? I guess not. > So two packages won't hurt and would fully comply with the > OpenCSW standard without further discussion. I liked your idea with install classes but since that would also provide binaries for both sparc and i386 our self-appointed release dictator would block that too. > Phil: The standard is not clear here, regardless of what you > intended with it. The package does work and it is usually > the responsibility of the maintainer to build the package > in the best way he thinks. The release manager (you :-) can > give advice on improvements, but if the maintainer is > reluctant to implement them the package must be released. > Unless, of course, it violates the standard... Some nice points there. Better yet would be if the release process would be shared between several (active, not spares) people to bring some democracy to this important process. To be voted down by a majority is fine but having one man to write the standard, interpret the standard and even rewrite it to fit his means if necessary, singlehandedly control all releases and ruling in all matters overall is just wrong in a community that calls itself open. It should however be noted that said man of course protested against that name. Dennis used to complain about it and he was right about that. Maybe Z?rich can bring some much needed change. > So, Peter, would you please deliver two packages and > you, Phil, then release the combined package? ;-) I will do that because at this point it's the only way to get it released at all and I won't give Phil the pleasure of not having it released just to prove a point. -- /peter From dam at opencsw.org Tue Nov 11 22:17:16 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 11 Nov 2008 22:17:16 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> Message-ID: <51C0A148-67DA-4121-B3E2-4A107E04CA60@opencsw.org> Hi Peter, Am 11.11.2008 um 22:13 schrieb Peter Bonivart: > Maybe Z?rich can bring some much needed change. So, you're coming then? Best regards -- Dago From bonivart at opencsw.org Tue Nov 11 22:28:25 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Tue, 11 Nov 2008 22:28:25 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <51C0A148-67DA-4121-B3E2-4A107E04CA60@opencsw.org> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <51C0A148-67DA-4121-B3E2-4A107E04CA60@opencsw.org> Message-ID: <625385e30811111328h79e42f9dsad7f772e4ff19583@mail.gmail.com> On Tue, Nov 11, 2008 at 10:17 PM, Dagobert Michelsen wrote: > Am 11.11.2008 um 22:13 schrieb Peter Bonivart: >> Maybe Z?rich can bring some much needed change. > > So, you're coming then? No, I don't want to be in the same country as Phil. Seriously, you, and probably all others who will attend, know where I stand. If I'm alone thinking we need to open up a lot of stuff then I will have to accept that and decide if I want to keep butting heads with Phil or do something else with my time. For reference, here's some suggestions I wrote a while ago: http://wiki.opencsw.org/suggestions -- /peter From phil at bolthole.com Tue Nov 11 22:31:35 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 11 Nov 2008 13:31:35 -0800 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com>; from bonivart@opencsw.org on Tue, Nov 11, 2008 at 10:13:04PM +0100 References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> Message-ID: <20081111133135.M66221@bolthole.com> On Tue, Nov 11, 2008 at 10:13:04PM +0100, Peter Bonivart wrote: > > Some nice points there. Better yet would be if the release process > would be shared between several (active, not spares) people to bring > some democracy to this important process. Meaning, you want to have someone else to push your package though, who wont hold you to standards. You claim you want democracy, when things arent going your way. But here's the thing; Democracy is all about "the majority of people who 'vote'", and the majority of people who "voted" here today on the list, were in favor of keeping ARCH=all free of arch specific binaries. So if you TRUELY respected this democracy you claim you wanted, you would say, "sorry, I was wrong; i'll go with the majority", and strip out the binaries completely. but it seems to be more about "not letting me 'score' a point" with you, even though I dont give a toss about that: > > So, Peter, would you please deliver two packages and > > you, Phil, then release the combined package? ;-) > > I will do that because at this point it's the only way to get it > released at all and I won't give Phil the pleasure of not having it > released just to prove a point. So anyway, I will be happy to push through your package once it no longer violates standards. Now, are you going to be an active opencsw maintainer, and update any of your OTHER packages? Or just the one package that you wrote for the purpose of trying to undermine me? I'll point out that you have over 25 packages under your name, and many of them appear to be out of date. Some are woefully out of date. Some only somewhat out of date. But some of the ones out of date, are important ones: BIND, dhcp, mailscanner Yet you are spending all your time on a package that we dont actually "need" at the moment. From a.cervellin at acm.org Tue Nov 11 22:36:33 2008 From: a.cervellin at acm.org (Alessio) Date: Tue, 11 Nov 2008 22:36:33 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111133135.M66221@bolthole.com> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> Message-ID: <4919FAE1.7000304@acm.org> Philip Brown wrote: > Yet you are spending all your time on a package that we dont actually > "need" at the moment. not really true, many people complained about the lack of an open pkg-fetching tool. From bonivart at opencsw.org Tue Nov 11 23:04:54 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Tue, 11 Nov 2008 23:04:54 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111133135.M66221@bolthole.com> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> Message-ID: <625385e30811111404x2f4b7c51je75b0a0aae27ed87@mail.gmail.com> On Tue, Nov 11, 2008 at 10:31 PM, Philip Brown wrote: > Meaning, you want to have someone else to push your package though, who > wont hold you to standards. No, I wanted this for a long time, long before the fork between BW and OpenCSW actually. But it's typical for you to enlarge a current issue. You did it with the wiki and you do it now for one package. You, and all other who are interested, can take a look at the revision history on the wiki page I linked to if you want to see when I wrote that. Not that long ago but long before the latest issues between you and me. > You claim you want democracy, when things arent going your way. I can live with democracy, how about you? > Now, are you going to be an active opencsw maintainer, and update any of > your OTHER packages? Or just the one package that you wrote for the > purpose of trying to undermine me? Nice of you to let others know in your own words what you think of my effort with pkgutil. Makes a much stronger point than if I had to repeat something you have said before, that could be questioned but this you wrote yourself. > I'll point out that you have over 25 packages under your name, and many of > them appear to be out of date. Some are woefully out of date. Some only > somewhat out of date. But some of the ones out of date, are important ones: > BIND, dhcp, mailscanner > Yet you are spending all your time on a package that we dont actually > "need" at the moment. Again, before you complain/block others you should clean your own house. To make just one example, I requested an update of your antiword to use for my MailScanner. You have 0.33 packaged which I can't even find listed on their site any longer, the latest 0.37 is from 2005, too much to ask for you to have had time to update? You never even replied to me. To mention BIND is kind of an insult since I very quickly had a safe version released when there was a large DNS flaw circulating this summer and I got lots of credit for it. I would again like to thank those who on short notice helped testing the package. You on the other hand wasted a few precious days extra, that was the start of a debate regarding automated release processes. Maybe not the best example for you to choose... Regarding the "need" for something besides pkg-get it has popped up more than once for several reasons, most regarding your closed license and your total unwillingness to listen to your users. I think there's plenty that can be improved upon and I already have. -- /peter From phil at bolthole.com Tue Nov 11 23:28:13 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 11 Nov 2008 14:28:13 -0800 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <4919FAE1.7000304@acm.org>; from a.cervellin@acm.org on Tue, Nov 11, 2008 at 10:36:33PM +0100 References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> Message-ID: <20081111142813.N66221@bolthole.com> On Tue, Nov 11, 2008 at 10:36:33PM +0100, Alessio wrote: > Philip Brown wrote: > > > Yet you are spending all your time on a package that we dont actually > > "need" at the moment. > > not really true, many people complained about the lack of an open > pkg-fetching tool. That is true, multiple people complained about that issue. But it isnt exactly a functional "need", in the sense of, "it doesnt make our packages work better", or keep them up to date any faster, etc. To my mind, the more pressing need, is to update our out-of-date packages. From a.cervellin at acm.org Tue Nov 11 23:38:13 2008 From: a.cervellin at acm.org (Alessio) Date: Tue, 11 Nov 2008 23:38:13 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111142813.N66221@bolthole.com> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> Message-ID: <491A0955.5020806@acm.org> Philip Brown wrote: > On Tue, Nov 11, 2008 at 10:36:33PM +0100, Alessio wrote: >> Philip Brown wrote: >> >>> Yet you are spending all your time on a package that we dont actually >>> "need" at the moment. >> not really true, many people complained about the lack of an open >> pkg-fetching tool. > > That is true, multiple people complained about that issue. But it isnt > exactly a functional "need", in the sense of, "it doesnt make our packages > work better", or keep them up to date any faster, etc. this is not the point: having a direction board, or having a distributed build farms, or having a wiki, or having an open packaging system, and so on don't make packages work better too, but they are priority things to debate before we continue releasing/updating packages, IMHO. > To my mind, the more pressing need, is to update our out-of-date packages. to your mind, to my mind the more pressing needs are the ones i listed in the mail "the real 1st step" of august 11th, and many if you agreed about it (you too). briefly, priorities are the definition of the community, of the rules, of the management, of the direction board, of the pkg-fetching tool "reference implementation", of the catalog format, of the joining rules, and many other things. later, you can update packages... otherwise, this is blastwave. From phil at bolthole.com Tue Nov 11 23:46:38 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 11 Nov 2008 14:46:38 -0800 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <491A0955.5020806@acm.org>; from a.cervellin@acm.org on Tue, Nov 11, 2008 at 11:38:13PM +0100 References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> <491A0955.5020806@acm.org> Message-ID: <20081111144638.O66221@bolthole.com> On Tue, Nov 11, 2008 at 11:38:13PM +0100, Alessio wrote: > > That is true, multiple people complained about that issue. But it isnt > > exactly a functional "need", in the sense of, "it doesnt make our packages > > work better", or keep them up to date any faster, etc. > > this is not the point: having a direction board, or having a distributed > build farms, or having a wiki, or having an open packaging system, and > so on don't make packages work better too, but they are priority things > to debate before we continue releasing/updating packages, IMHO. I think that those things can continue to be worked on in parallel to updating packages. > to your mind, to my mind the more pressing needs are the ones i listed > in the mail "the real 1st step" of august 11th, and many if you agreed > about it (you too). and I believe they are all listed on the wiki page that peter referenced, and some of them have been listed as already being addressed. Progress is being made in the areas you have listed concerns in. Further progress will be made at the IRL meeting. Meantime, lets also continue to meet the needs of our users, rather than bring things to a grinding halt, Dennis-style. From phil at bolthole.com Wed Nov 12 00:07:45 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 11 Nov 2008 15:07:45 -0800 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <625385e30811111404x2f4b7c51je75b0a0aae27ed87@mail.gmail.com>; from bonivart@opencsw.org on Tue, Nov 11, 2008 at 11:04:54PM +0100 References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <625385e30811111404x2f4b7c51je75b0a0aae27ed87@mail.gmail.com> Message-ID: <20081111150745.P66221@bolthole.com> On Tue, Nov 11, 2008 at 11:04:54PM +0100, Peter Bonivart wrote: > Again, before you complain/block others you should clean your own > house. To make just one example, I requested an update of your > antiword to use for my MailScanner. You have 0.33 packaged which I > can't even find listed on their site any longer, the latest 0.37 is > from 2005, too much to ask for you to have had time to update? I apologise for that dropping off my radar. I have now packaged up the latest version. As far as I know, all of my other packages are up to date. From james at opencsw.org Wed Nov 12 10:54:43 2008 From: james at opencsw.org (James Lee) Date: Wed, 12 Nov 2008 09:54:43 GMT Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111070559.C90125@bolthole.com> References: <20081111070559.C90125@bolthole.com> Message-ID: <20081112.9544300.2897156652@gyor.oxdrove.co.uk> On 11/11/08, 15:05:59, Philip Brown wrote regarding [csw-maintainers] ARCH=all packages: > I suggested that he either remove the binaries and use pure perl, > (either with a full wget replacement, or to use it to download > "the appropriate binary") > or split it up into two separate packages, with appropriate ARCH settings > for the binary he includes in each one. > He refuses to take either path, or offer a third one. Third way: The pkgutil package in the CSW collection has no wget and depends on CSWwget and CSWperl (plus anything else needed). It can be installed using pkg-get and update itself. How does a novice user install this using only 17 key strokes? He/she doesn't. For this provide a first time install only package that contains both wget binaries and maybe hobbled options so it runs in a basic Solaris 8 environment. The first time it runs it will install its depends (wget, perl) and update itself to the latest and greatest all-arch standards-friendly slim-line pkgutil. A "How to Begin" text can the have easier instructions and use a web download with simplified naming and a fixed URL - no version needed in file name. James. From dam at opencsw.org Wed Nov 12 12:54:25 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 12 Nov 2008 12:54:25 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081112.9544300.2897156652@gyor.oxdrove.co.uk> References: <20081111070559.C90125@bolthole.com> <20081112.9544300.2897156652@gyor.oxdrove.co.uk> Message-ID: <69B38927-56A5-4646-9465-69ED53C06365@opencsw.org> Hi James, Am 12.11.2008 um 10:54 schrieb James Lee: > Third way: > > The pkgutil package in the CSW collection has no wget and depends on > CSWwget and CSWperl (plus anything else needed). It can be installed > using pkg-get and update itself. > > How does a novice user install this using only 17 key strokes? He/she > doesn't. For this provide a first time install only package that > contains both wget binaries and maybe hobbled options so it runs in a > basic Solaris 8 environment. The first time it runs it will install > its depends (wget, perl) and update itself to the latest and greatest > all-arch standards-friendly slim-line pkgutil. > > A "How to Begin" text can the have easier instructions and use a web > download with simplified naming and a fixed URL - no version needed in > file name. Good solution. That way the repository stays clean and Peter makes his users happy :-) Best regards -- Dago From trygvel at opencsw.org Wed Nov 12 14:06:54 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Wed, 12 Nov 2008 14:06:54 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> Message-ID: <491AD4EE.3010100@opencsw.org> Peter Bonivart wrote: > On Tue, Nov 11, 2008 at 8:35 PM, Dagobert Michelsen wrote: >> Peter: Is it really that important to have one fat package >> instead of two? An admin usually does know on which platform >> he is on. Will the package be installed on NFS and would it >> be run from sparc and i386 at the same time? I guess not. >> So two packages won't hurt and would fully comply with the >> OpenCSW standard without further discussion. > > I liked your idea with install classes but since that would also > provide binaries for both sparc and i386 our self-appointed release > dictator would block that too. > >> Phil: The standard is not clear here, regardless of what you >> intended with it. The package does work and it is usually >> the responsibility of the maintainer to build the package >> in the best way he thinks. The release manager (you :-) can >> give advice on improvements, but if the maintainer is >> reluctant to implement them the package must be released. >> Unless, of course, it violates the standard... > > Some nice points there. Better yet would be if the release process > would be shared between several (active, not spares) people to bring > some democracy to this important process. To be voted down by a > majority is fine but having one man to write the standard, interpret > the standard and even rewrite it to fit his means if necessary, > singlehandedly control all releases and ruling in all matters overall > is just wrong in a community that calls itself open. It should however > be noted that said man of course protested against that name. Come on. While he's still the only one he is at least discussing it in public with the intention to come to a conclusion. One thing that has happened since the fork are more discussions and openness (at least in my opinion). The situation is getting better, slowly. Moving and coordinating a big, distributed crowd like us is a very slow process. Zurich will hopefully define some ground rules, but we still have lots of kinks to work out. -- Trygve From trygvel at opencsw.org Wed Nov 12 14:10:19 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Wed, 12 Nov 2008 14:10:19 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111142813.N66221@bolthole.com> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> Message-ID: <491AD5BB.1010705@opencsw.org> Philip Brown wrote: > On Tue, Nov 11, 2008 at 10:36:33PM +0100, Alessio wrote: >> Philip Brown wrote: >> >>> Yet you are spending all your time on a package that we dont actually >>> "need" at the moment. >> not really true, many people complained about the lack of an open >> pkg-fetching tool. > > That is true, multiple people complained about that issue. But it isnt > exactly a functional "need", in the sense of, "it doesnt make our packages > work better", or keep them up to date any faster, etc. > > To my mind, the more pressing need, is to update our out-of-date packages. As a group of volunteers you really don't have the right to tell people what they should work on. Peter and everyone else has their own right to work on what they feel like. So do you, and if you feel that the packages you mention should be updated, you should feel free to do so. -- Trygve From trygvel at opencsw.org Wed Nov 12 14:14:18 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Wed, 12 Nov 2008 14:14:18 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <20081111070559.C90125@bolthole.com> References: <20081111070559.C90125@bolthole.com> Message-ID: <491AD6AA.8050201@opencsw.org> Philip Brown wrote: > Peter B. and I are having a disagreement about the concept of ARCH=all > packages, so I thought I would bring the discussion here. > > The issue is that he wishes to bundle specific binaries for wget in his > pkgutil package, AND call it ARCH=all. > (he wants to bundle one for sparc and one for x86) > > I suggested that he either remove the binaries and use pure perl, > (either with a full wget replacement, or to use it to download > "the appropriate binary") > or split it up into two separate packages, with appropriate ARCH settings > for the binary he includes in each one. > > He refuses to take either path, or offer a third one. > > Our standards pages say, > > http://www.opencsw.org/standards/build > "{ARCH} is usually the output of `uname -p`. But for certain special > packages that run on all solaris hardware, or are otherwise > architecture-neutral, it may be preferable to have ARCH=all " > > I say that this means that archtecture specific binaries, should not be in > "ARCH=all" packages. Even if you do not agree that the words clearly state > that, it was certainly my INTENTION when I wrote the standard. > I wanted "ARCH=all" to clearly indicate, "this package will work > EVERYWHERE, it will never need recompiling, and it is safe to be shared in > some kind of NFS /opt/csw for any and all solaris machines to use." > > In other words, ARCH=all should be reserved for things like raw > arch-neutral data files, docs, java, and shellscripts/perl/python. > > (I originally intended to use "ARCH=any"... however, I followed sun's > lead; sun uses ARCH=all, and does not use ARCH=any, to the best > of my knowlege, for this purpose) > > > What are peoples' comments on this? Another option: * Let pkgtool depend on the Perl modules required to do HTTP/FTP stuff * Create (if not already) packages for the modules * Create a pkg stream that includes all the packages and make that downloadable from the frontpage as a "getting started" tool like pkg-get. * PROFIT! The added bonus here is that the pkgtool code and package is kept clean, and once the system is bootstrapped it will be updated like any other package. -- Trygve From dam at opencsw.org Thu Nov 13 17:49:59 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 13 Nov 2008 17:49:59 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <491AD5BB.1010705@opencsw.org> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> <491AD5BB.1010705@opencsw.org> Message-ID: <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> Hi Trygve, Am 12.11.2008 um 14:10 schrieb Trygve Laugst?l: > As a group of volunteers you really don't have the right to tell > people > what they should work on. Peter and everyone else has their own > right to > work on what they feel like. So do you, and if you feel that the > packages you mention should be updated, you should feel free to do so. Of course you are free to work on the projects you like. However, when you release a package, you have the responsibility to update it regularly and fix bugs as they are reported. Having major bugs open for a year or more is simply unacceptable. I am working on a webpage to make this more transparent and to make sure that critical bugs are cared for. The tool is not ready yet, but I'll hope to publish something useful before Zurich so we know where we stand. Best regards -- Dago From william at wbonnet.net Thu Nov 13 18:06:55 2008 From: william at wbonnet.net (William Bonnet) Date: Thu, 13 Nov 2008 18:06:55 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> <491AD5BB.1010705@opencsw.org> <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> Message-ID: <491C5EAF.2090903@wbonnet.net> Hi > Of course you are free to work on the projects you like. However, > when you release a package, you have the responsibility to > update it regularly and fix bugs as they are reported. Having > major bugs open for a year or more is simply unacceptable. > I am working on a webpage to make this more transparent > and to make sure that critical bugs are cared for. The tool is > not ready yet, but I'll hope to publish something useful > before Zurich so we know where we stand. > Would it be possible to receive again the mails with the list of openbugs ? Once FF3 is built, I would like to work on an automated procedure that would notify maintainers of updates (ie : I would receive an email notifying me that FF 2.0.0.17 is no longer the latest available, 2.0.0.18 is available). I talked about this with Yann a few monthes ago. It seems something exists in GAR but i never managed to get it working. If you work on ths please let me know, maybe we can effort on this. cheers From yann at pleiades.fr.eu.org Thu Nov 13 18:08:46 2008 From: yann at pleiades.fr.eu.org (Yann Rouillard) Date: Thu, 13 Nov 2008 18:08:46 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <491C5EAF.2090903@wbonnet.net> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> <491AD5BB.1010705@opencsw.org> <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> <491C5EAF.2090903@wbonnet.net> Message-ID: <491C5F1E.1000608@pleiades.fr.eu.org> William Bonnet a ?crit : > Hi > Once FF3 is built, I would like to work on an automated procedure that > would notify maintainers of updates (ie : I would receive an email > notifying me that FF 2.0.0.17 is no longer the latest available, > 2.0.0.18 is available). I talked about this with Yann a few monthes ago. > It seems something exists in GAR but i never managed to get it working. It's currently a ugly hack and I am not sure it still works. Yann From dam at opencsw.org Thu Nov 13 20:26:08 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 13 Nov 2008 20:26:08 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <491C5EAF.2090903@wbonnet.net> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> <491AD5BB.1010705@opencsw.org> <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> <491C5EAF.2090903@wbonnet.net> Message-ID: <30320D83-B4BD-4805-921F-3FAA0CB29E82@opencsw.org> Hi William, Am 13.11.2008 um 18:06 schrieb William Bonnet: >> Of course you are free to work on the projects you like. However, >> when you release a package, you have the responsibility to >> update it regularly and fix bugs as they are reported. Having >> major bugs open for a year or more is simply unacceptable. >> I am working on a webpage to make this more transparent >> and to make sure that critical bugs are cared for. The tool is >> not ready yet, but I'll hope to publish something useful >> before Zurich so we know where we stand. >> > > Would it be possible to receive again the mails with the list of > openbugs ? Do you mean when a new bug is entered? Don't know. Phil? > Once FF3 is built, I would like to work on an automated procedure that > would notify maintainers of updates (ie : I would receive an email > notifying me that FF 2.0.0.17 is no longer the latest available, > 2.0.0.18 is available). I talked about this with Yann a few monthes > ago. > It seems something exists in GAR but i never managed to get it > working. > > If you work on ths please let me know, maybe we can effort on this. I am thinking of tailoring UFILES_REGEX (the GAR update mechanism) to Mantis to automatically generate an UPDATE request for that package which then gets mailed to the maintainer via Mantis. That way it is clearly visible through bug workflow tools what needs to be done. Best regards -- Dago From phil at bolthole.com Thu Nov 13 20:37:23 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 13 Nov 2008 11:37:23 -0800 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <30320D83-B4BD-4805-921F-3FAA0CB29E82@opencsw.org>; from dam@opencsw.org on Thu, Nov 13, 2008 at 08:26:08PM +0100 References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> <491AD5BB.1010705@opencsw.org> <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> <491C5EAF.2090903@wbonnet.net> <30320D83-B4BD-4805-921F-3FAA0CB29E82@opencsw.org> Message-ID: <20081113113723.A72975@bolthole.com> On Thu, Nov 13, 2008 at 08:26:08PM +0100, Dagobert Michelsen wrote: > > Would it be possible to receive again the mails with the list of > > openbugs ? > > Do you mean when a new bug is entered? Don't know. Phil? no, the "new bug" thing should be working again. perhaps what he was referring to, was what James did during "freeze" cycles. From dam at opencsw.org Thu Nov 13 21:32:52 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 13 Nov 2008 21:32:52 +0100 Subject: [csw-maintainers] build8s at Gore buildfarm down Message-ID: <4027EF7F-041A-4954-A653-0F617CB992AB@opencsw.org> Hi, I am currently moving /home to a bigger disk on build8s.go.opencsw.org on user request. This may take some time. I'll post when the operation is finished. Best regards -- Dago From william at wbonnet.net Thu Nov 13 22:10:18 2008 From: william at wbonnet.net (William Bonnet) Date: Thu, 13 Nov 2008 22:10:18 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <30320D83-B4BD-4805-921F-3FAA0CB29E82@opencsw.org> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> <491AD5BB.1010705@opencsw.org> <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> <491C5EAF.2090903@wbonnet.net> <30320D83-B4BD-4805-921F-3FAA0CB29E82@opencsw.org> Message-ID: <491C97BA.50501@wbonnet.net> Hi > Do you mean when a new bug is entered? Don't know. Phil? > Yes, and also the weekly reminder. > I am thinking of tailoring UFILES_REGEX (the GAR update mechanism) > to Mantis to automatically generate an UPDATE request for that > package which then gets mailed to the maintainer via Mantis. > That way it is clearly visible through bug workflow tools what needs > to be done. > If think it is what i was asking for, even better :) Tell me if you need a tester or some help to set it up. There is a lot of packages to process... 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 phil at bolthole.com Thu Nov 13 22:13:38 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 13 Nov 2008 13:13:38 -0800 Subject: [csw-maintainers] mantis, email notifications In-Reply-To: <20081113113723.A72975@bolthole.com>; from phil@bolthole.com on Thu, Nov 13, 2008 at 11:37:23AM -0800 References: <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> <491AD5BB.1010705@opencsw.org> <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> <491C5EAF.2090903@wbonnet.net> <30320D83-B4BD-4805-921F-3FAA0CB29E82@opencsw.org> <20081113113723.A72975@bolthole.com> Message-ID: <20081113131338.B72975@bolthole.com> On Thu, Nov 13, 2008 at 11:37:23AM -0800, Philip Brown wrote: > no, the "new bug" thing should be working again. Buuuttt, apaprently it isnt. I did not get email notification, when a bug was filed yesterday or so against one of my packages. arg. From trygvel at opencsw.org Fri Nov 14 00:14:04 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Fri, 14 Nov 2008 00:14:04 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> <491AD5BB.1010705@opencsw.org> <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> Message-ID: <491CB4BC.9010504@opencsw.org> Dagobert Michelsen wrote: > Hi Trygve, > > Am 12.11.2008 um 14:10 schrieb Trygve Laugst?l: >> As a group of volunteers you really don't have the right to tell >> people >> what they should work on. Peter and everyone else has their own >> right to >> work on what they feel like. So do you, and if you feel that the >> packages you mention should be updated, you should feel free to do so. > > Of course you are free to work on the projects you like. However, > when you release a package, you have the responsibility to > update it regularly and fix bugs as they are reported. Having > major bugs open for a year or more is simply unacceptable. > I am working on a webpage to make this more transparent > and to make sure that critical bugs are cared for. The tool is > not ready yet, but I'll hope to publish something useful > before Zurich so we know where we stand. Well, this is something that we have to talk about in Zurich. I really can't be expected to update my packages within a certain number of days after a new release/bug/whatever. It is not that I'm going to do it if I have the time, but I don't want to be know as a "bad" maintainer if I don't. I really don't like the fact that we talk about "mine" and "your" packages all the time, they are *our* packages! Having a primary maintainer is probably wise (though it could also be a set of primary maintainers) as those are most likely to know how to fix bugs. If a primary maintainer fails to update the package within reasonable time, I would *hope* that someone can pick up the pieces and publish it. To help supporting a process like that I hope that we can focus on re-producible builds and a better validation framework with Hudson. -- Trygve From william at wbonnet.net Fri Nov 14 00:26:39 2008 From: william at wbonnet.net (William Bonnet) Date: Fri, 14 Nov 2008 00:26:39 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <491CB4BC.9010504@opencsw.org> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> <491AD5BB.1010705@opencsw.org> <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> <491CB4BC.9010504@opencsw.org> Message-ID: <491CB7AF.5070309@wbonnet.net> Hi > I really don't like the fact that we talk about "mine" and "your" > packages all the time, they are *our* packages! Having a primary > maintainer is probably wise (though it could also be a set of primary > maintainers) as those are most likely to know how to fix bugs. If a > primary maintainer fails to update the package within reasonable time, I > would *hope* that someone can pick up the pieces and publish it. > Once again i suggest to create team for set of packages. This has certainly to be discussed in zurich. Basically the idea is that key packages (Mozilla's spawns (FF TB SM), Apache, ssh, foo) or set of packages likke desktop environment (kde, gnome, xfce) should be handle by a team. Organisation has to be defined, but it could be composed of a leader and contributors who can alsoupdate and release things or a "main maintainer" and a "backup maintainer". IMHO we clearly have to define an organization which can handle the problem of releasing security updates when main packager is unavailable for a reasonnable time. 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 phil at bolthole.com Fri Nov 14 00:27:02 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 13 Nov 2008 15:27:02 -0800 Subject: [csw-maintainers] Anyone interested in taking on a NEW package? Message-ID: <20081113152702.H72975@bolthole.com> FYI: there has been a request on our "requested packages" page, for packaging up "inkscape. it is touted as somewhat like adobe illustrator, and outputs in SVG (vector) format. If anyone feels included to take on something spiffy... That would be a cool thing for us to have a package of. http://www.inkscape.org/ From william at wbonnet.net Fri Nov 14 07:50:37 2008 From: william at wbonnet.net (William Bonnet) Date: Fri, 14 Nov 2008 07:50:37 +0100 Subject: [csw-maintainers] Firefox 2.0.0.18 is available Message-ID: <491D1FBD.1010802@wbonnet.net> Hi, The latest update of Firefox (version 2.0.0.18) is now available from testing. This release includes several security fixes ( http://www.mozilla.org/security/known-vulnerabilities/firefox20.html#firefox2.0.0.18 ). The release notes are availables from this place ( http://www.mozilla-europe.org/en/products/firefox/2.0.0.18/releasenotes/ ). This update should be pushed to unstable soon. Thanks for your feedbacks if you experience any problem with this testing version. Best regards, -- William http://www.wbonnet.net http://www.sunwizard.net Le site fran?ais des amateurs de stations Unix http://www.opencsw.org Community SoftWare for Solaris http://www.guses.org French speaking Solaris User Group From dam at opencsw.org Fri Nov 14 10:25:20 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 14 Nov 2008 10:25:20 +0100 Subject: [csw-maintainers] build8s at Gore buildfarm up again In-Reply-To: <4027EF7F-041A-4954-A653-0F617CB992AB@opencsw.org> References: <4027EF7F-041A-4954-A653-0F617CB992AB@opencsw.org> Message-ID: Hi, Am 13.11.2008 um 21:32 schrieb Dagobert Michelsen: > I am currently moving /home to a bigger disk on > build8s.go.opencsw.org > on user request. This may take some time. I'll > post when the operation is finished. The machine is available again and there are now ca. 135 GB free in /home. Best regards -- Dago From dam at opencsw.org Fri Nov 14 10:41:51 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 14 Nov 2008 10:41:51 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <491C97BA.50501@wbonnet.net> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> <491AD5BB.1010705@opencsw.org> <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> <491C5EAF.2090903@wbonnet.net> <30320D83-B4BD-4805-921F-3FAA0CB29E82@opencsw.org> <491C97BA.50501@wbonnet.net> Message-ID: Hi, Am 13.11.2008 um 18:08 schrieb Yann Rouillard: > William Bonnet a ?crit : >> Once FF3 is built, I would like to work on an automated procedure >> that >> would notify maintainers of updates (ie : I would receive an email >> notifying me that FF 2.0.0.17 is no longer the latest available, >> 2.0.0.18 is available). I talked about this with Yann a few monthes >> ago. >> It seems something exists in GAR but i never managed to get it >> working. > > It's currently a ugly hack and I am not sure it still works. Yann, would you be willing to take a look at it? Am 13.11.2008 um 22:10 schrieb William Bonnet: >> I am thinking of tailoring UFILES_REGEX (the GAR update mechanism) >> to Mantis to automatically generate an UPDATE request for that >> package which then gets mailed to the maintainer via Mantis. >> That way it is clearly visible through bug workflow tools what needs >> to be done. >> > > If think it is what i was asking for, even better :) > > Tell me if you need a tester or some help to set it up. There is a lot > of packages to process... William, what is needed after the mechanism in general works is updating all Makefile with UFILES_REGEX to actually look for updated versions. If you could help updating all the Makefile would be great. After that we can integrate the found results in Mantis. Best regards -- Dago From dam at opencsw.org Fri Nov 14 11:18:53 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 14 Nov 2008 11:18:53 +0100 Subject: [csw-maintainers] Topics on IRL meeting In-Reply-To: <491CB7AF.5070309@wbonnet.net> References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <20081111133135.M66221@bolthole.com> <4919FAE1.7000304@acm.org> <20081111142813.N66221@bolthole.com> <491AD5BB.1010705@opencsw.org> <8B131E50-B1EB-40AC-97D1-6580FD4497B7@opencsw.org> <491CB4BC.9010504@opencsw.org> <491CB7AF.5070309@wbonnet.net> Message-ID: Hi, Am 14.11.2008 um 00:26 schrieb William Bonnet: > Basically the idea is that key packages (Mozilla's spawns (FF TB > SM), Apache, ssh, foo) or set of packages likke desktop environment > (kde, gnome, xfce) should be handle by a team. Organisation has to > be defined, but it could be composed of a leader and contributors > who can alsoupdate and release things or a "main maintainer" and a > "backup maintainer". I added this to as a lists of topics to talk about. After collecting issues we should group similar items, define a timeframe for discussion and define a chairman for each discussion. I suggest we keep the collections of topics to talk about open for another week until 21.11.08, then group the items. It is not that we can not talk about other items, but because of the vast amount of things to take care of we may get lost in discussion without results without tight structure for the main Saturday. So, feel free to add topics to that page. Best regards -- Dago From mmayer at mmayer.net Fri Nov 14 19:57:17 2008 From: mmayer at mmayer.net (Markus Mayer) Date: Fri, 14 Nov 2008 10:57:17 -0800 Subject: [csw-maintainers] Ouchies Message-ID: <20081114185716.GA13988@bender.opencsw.org> http://biz.yahoo.com/ap/081114/sun_microsystems_layoffs.html I don't know how accurate this assessment is, but it doesn't sound too good: "[...]Sun's latest woes have ramped up speculation that one of the most storied names in computing could be snapped up dirt-cheap by a bigger rival. Hewlett-Packard Co., IBM Corp., and Dell Inc. are all possible suitors." ... "Sun's share price gives the company a market value of roughly $3 billion. Yet at the end of September, Sun had $3.1 billion in cash on hand. The gap indicates extreme pessimism about the company's prospects." Regards, -Markus From phil at bolthole.com Fri Nov 14 20:12:15 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 14 Nov 2008 11:12:15 -0800 Subject: [csw-maintainers] Ouchies In-Reply-To: <20081114185716.GA13988@bender.opencsw.org>; from mmayer@mmayer.net on Fri, Nov 14, 2008 at 10:57:17AM -0800 References: <20081114185716.GA13988@bender.opencsw.org> Message-ID: <20081114111215.K21898@bolthole.com> On Fri, Nov 14, 2008 at 10:57:17AM -0800, Markus Mayer wrote: > > http://biz.yahoo.com/ap/081114/sun_microsystems_layoffs.html > > I don't know how accurate this assessment is, but it doesn't sound > too good: > > "[...]Sun's latest woes have ramped up speculation that one of the most > storied names in computing could be snapped up dirt-cheap by a bigger > rival. Hewlett-Packard Co., IBM Corp., and Dell Inc. are all possible > suitors." Ugh. well, it's not too surprising, when they are wasting time trying to make [Solaris next] "Just like linux", instead of just taking "the good bits" from it, and combining it with what makes people like Sun/Solaris over linux. Arg. From phil at bolthole.com Fri Nov 14 20:23:46 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 14 Nov 2008 11:23:46 -0800 Subject: [csw-maintainers] Ouchies In-Reply-To: <20081114111215.K21898@bolthole.com>; from phil@bolthole.com on Fri, Nov 14, 2008 at 11:12:15AM -0800 References: <20081114185716.GA13988@bender.opencsw.org> <20081114111215.K21898@bolthole.com> Message-ID: <20081114112346.M21898@bolthole.com> On Fri, Nov 14, 2008 at 11:12:15AM -0800, Philip Brown wrote: > On Fri, Nov 14, 2008 at 10:57:17AM -0800, Markus Mayer wrote: > > > > http://biz.yahoo.com/ap/081114/sun_microsystems_layoffs.html Hmph. more from this. Looks like Schwartz fancies himself has a hachet man. "The company has done several rounds of big layoffs in the last three years. Sun has cut 2,700 jobs since August of last year in two separate restructurings. The company had previously cut about 4,000 jobs after Schwartz took over as CEO from co-founder Scott McNealy in 2006." one piece of potential "good" news, is that they are splitting off OS into a separate division once again. We'll see if there's anyone sane left at sun to do a good job of heading it up. sigh. From ihsan at opencsw.org Fri Nov 14 20:42:39 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Fri, 14 Nov 2008 20:42:39 +0100 Subject: [csw-maintainers] Ouchies In-Reply-To: <20081114185716.GA13988@bender.opencsw.org> References: <20081114185716.GA13988@bender.opencsw.org> Message-ID: <491DD4AF.5000000@opencsw.org> Am 14.11.2008 19:57 Uhr, Markus Mayer schrieb: > I don't know how accurate this assessment is, but it doesn't sound > too good: > > "[...]Sun's latest woes have ramped up speculation that one of the most > storied names in computing could be snapped up dirt-cheap by a bigger > rival. Hewlett-Packard Co., IBM Corp., and Dell Inc. are all possible > suitors." > ... > "Sun's share price gives the company a market value of roughly $3 > billion. Yet at the end of September, Sun had $3.1 billion in cash on > hand. The gap indicates extreme pessimism about the company's > prospects." Sun's stock is now at 4.23. It was never that low since 1994! Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ -------------- next part -------------- A non-text attachment was scrubbed... Name: chart_V_3548367_67_1Y.gif Type: image/gif Size: 6669 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: chart_V_3548367_67_1994-04-23_1994-12-31.gif Type: image/gif Size: 6232 bytes Desc: not available URL: From buysse at umn.edu Fri Nov 14 20:44:55 2008 From: buysse at umn.edu (Joshua Buysse) Date: Fri, 14 Nov 2008 13:44:55 -0600 Subject: [csw-maintainers] Ouchies In-Reply-To: <491DD4AF.5000000@opencsw.org> References: <20081114185716.GA13988@bender.opencsw.org> <491DD4AF.5000000@opencsw.org> Message-ID: <62E40CD3-E9E6-4E15-BC75-4222A2B55477@umn.edu> On Nov 14, 2008, at 1:42 PM, Ihsan Dogan wrote: > Am 14.11.2008 19:57 Uhr, Markus Mayer schrieb: >> ... >> "Sun's share price gives the company a market value of roughly $3 >> billion. Yet at the end of September, Sun had $3.1 billion in cash on >> hand. The gap indicates extreme pessimism about the company's >> prospects." > > Sun's stock is now at 4.23. It was never that low since 1994! Are you factoring in that they reverse-split the stock at least once, last couple of years? -J -- Joshua Buysse, System Engineer College of Liberal Arts, Office of Information Technology University of Minnesota "The First Amendment is often inconvenient. But that is besides the point. Inconvenience does not absolve the government of its obligation to tolerate speech." -- Justice Anthony M. Kennedy -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL: From phil at bolthole.com Fri Nov 14 20:57:44 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 14 Nov 2008 11:57:44 -0800 Subject: [csw-maintainers] mantis email.. working....? Message-ID: <20081114115744.P21898@bolthole.com> It appears that Ihsan(?) has managed to unstick something, and I see a flood of old mantis-related emails coming through now :-) I was also trying to just look at things at the same time though. In theory, my "looking" should not have unstuck anything. i only used mailx locally. So, confirmation would be nice, on what was done...? From buysse at cla.umn.edu Fri Nov 14 20:26:41 2008 From: buysse at cla.umn.edu (Joshua Buysse) Date: Fri, 14 Nov 2008 13:26:41 -0600 Subject: [csw-maintainers] Ouchies In-Reply-To: <20081114111215.K21898@bolthole.com> References: <20081114185716.GA13988@bender.opencsw.org> <20081114111215.K21898@bolthole.com> Message-ID: <6A7D9D60-B8AA-4FC3-9AAA-810E0E379AA3@cla.umn.edu> >> http://biz.yahoo.com/ap/081114/sun_microsystems_layoffs.html >> >> I don't know how accurate this assessment is, but it doesn't sound >> too good: >> >> "[...]Sun's latest woes have ramped up speculation that one of the >> most >> storied names in computing could be snapped up dirt-cheap by a bigger >> rival. Hewlett-Packard Co., IBM Corp., and Dell Inc. are all possible >> suitors Hmm. Market cap == cash on hand. Why not go private? Sun should buy itself out and be done with it. Then, focus on long-term stability instead of bloody quarterly earnings. > well, it's not too surprising, when they are wasting time trying to > make > [Solaris next] "Just like linux", instead of just taking > "the good bits" from it, and combining it with what makes people like > Sun/Solaris over linux. -- Joshua Buysse, System Engineer College of Liberal Arts, Office of Information Technology University of Minnesota "A good programmer is someone who looks both ways before crossing a one-way street." -- Doug Linder -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL: From ihsan at opencsw.org Fri Nov 14 22:34:26 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Fri, 14 Nov 2008 22:34:26 +0100 Subject: [csw-maintainers] Ouchies In-Reply-To: <6A7D9D60-B8AA-4FC3-9AAA-810E0E379AA3@cla.umn.edu> References: <20081114185716.GA13988@bender.opencsw.org> <20081114111215.K21898@bolthole.com> <6A7D9D60-B8AA-4FC3-9AAA-810E0E379AA3@cla.umn.edu> Message-ID: <491DEEE2.4060302@opencsw.org> Am 14.11.2008 20:26 Uhr, Joshua Buysse schrieb: >>> "[...]Sun's latest woes have ramped up speculation that one of the most >>> storied names in computing could be snapped up dirt-cheap by a bigger >>> rival. Hewlett-Packard Co., IBM Corp., and Dell Inc. are all possible >>> suitors > Hmm. Market cap == cash on hand. Why not go private? Sun should buy > itself out and be done with it. Then, focus on long-term stability > instead of bloody quarterly earnings. A few years ago, I've read a report about Toyota. The journalist asked, what is the secret of Toyota to be that successful. The answer was, that Toyota is not focused on quarterly earnings. Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From ihsan at opencsw.org Fri Nov 14 22:36:29 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Fri, 14 Nov 2008 22:36:29 +0100 Subject: [csw-maintainers] Ouchies In-Reply-To: <62E40CD3-E9E6-4E15-BC75-4222A2B55477@umn.edu> References: <20081114185716.GA13988@bender.opencsw.org> <491DD4AF.5000000@opencsw.org> <62E40CD3-E9E6-4E15-BC75-4222A2B55477@umn.edu> Message-ID: <491DEF5D.1030008@opencsw.org> Am 14.11.2008 20:44 Uhr, Joshua Buysse schrieb: >> Sun's stock is now at 4.23. It was never that low since 1994! > Are you factoring in that they reverse-split the stock at least once, > last couple of years? After I read that the stock is on 4 $, I was only wondering when it was that low the last time. Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From ihsan at opencsw.org Fri Nov 14 22:38:04 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Fri, 14 Nov 2008 22:38:04 +0100 Subject: [csw-maintainers] mantis email.. working....? In-Reply-To: <20081114115744.P21898@bolthole.com> References: <20081114115744.P21898@bolthole.com> Message-ID: <491DEFBC.2040206@opencsw.org> Am 14.11.2008 20:57 Uhr, Philip Brown schrieb: > It appears that Ihsan(?) has managed to unstick something, and I see a > flood of old mantis-related emails coming through now :-) Well, I just copied the database to the new machine. I hope you don't need anything from the old machine, because it's turned off. Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From phil at bolthole.com Fri Nov 14 22:48:07 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 14 Nov 2008 13:48:07 -0800 Subject: [csw-maintainers] mantis email.. working....? In-Reply-To: <491DEFBC.2040206@opencsw.org>; from ihsan@opencsw.org on Fri, Nov 14, 2008 at 10:38:04PM +0100 References: <20081114115744.P21898@bolthole.com> <491DEFBC.2040206@opencsw.org> Message-ID: <20081114134807.V21898@bolthole.com> On Fri, Nov 14, 2008 at 10:38:04PM +0100, Ihsan Dogan wrote: > Am 14.11.2008 20:57 Uhr, Philip Brown schrieb: > > > It appears that Ihsan(?) has managed to unstick something, and I see a > > flood of old mantis-related emails coming through now :-) > > Well, I just copied the database to the new machine. I hope you don't > need anything from the old machine, because it's turned off. Urrrr... that sounds like, "you didnt do anything". all i did, was run "mailx -v". so maybe that somehow unstuck email. on www.opencsw.org Soo... I'm going to permenantly change the way mantis sends email, to use "connect via SMTP to localhost" and hope that makes things behave better. From phil at bolthole.com Fri Nov 14 22:54:55 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 14 Nov 2008 13:54:55 -0800 Subject: [csw-maintainers] mantis email.. working....? In-Reply-To: <20081114134807.V21898@bolthole.com>; from phil@bolthole.com on Fri, Nov 14, 2008 at 01:48:07PM -0800 References: <20081114115744.P21898@bolthole.com> <491DEFBC.2040206@opencsw.org> <20081114134807.V21898@bolthole.com> Message-ID: <20081114135455.W21898@bolthole.com> On Fri, Nov 14, 2008 at 01:48:07PM -0800, Philip Brown wrote: > Soo... I'm going to permenantly change the way mantis sends email, to use > "connect via SMTP to localhost" and hope that makes things behave better. > that didnt help either??? really odd. email worked when mantis was first set up. From bonivart at opencsw.org Fri Nov 14 23:29:13 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Fri, 14 Nov 2008 23:29:13 +0100 Subject: [csw-maintainers] Class Action Scripts package described on the wiki Message-ID: <625385e30811141429m3e0505f5p321540c14931f443@mail.gmail.com> I have written some about how to support SMF in your packages by using our CSWcswclassutils package that contains class action scripts. It's real easy to add support for SMF in your new and existing packages and it only takes about a minute. Read more here: http://wiki.opencsw.org/cswclassutils The package also contains two scripts from Phil that helps with preserving config files during upgrades. Those have yet to be documented on the wiki. If you read this Phil, feel free to edit those parts of the page. -- /peter From phil at bolthole.com Fri Nov 14 23:48:37 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 14 Nov 2008 14:48:37 -0800 Subject: [csw-maintainers] Class Action Scripts package described on the wiki In-Reply-To: <625385e30811141429m3e0505f5p321540c14931f443@mail.gmail.com>; from bonivart@opencsw.org on Fri, Nov 14, 2008 at 11:29:13PM +0100 References: <625385e30811141429m3e0505f5p321540c14931f443@mail.gmail.com> Message-ID: <20081114144837.Y21898@bolthole.com> On Fri, Nov 14, 2008 at 11:29:13PM +0100, Peter Bonivart wrote: > I have written some about how to support SMF in your packages by using > our CSWcswclassutils package that contains class action scripts. It's > real easy to add support for SMF in your new and existing packages and > it only takes about a minute. > > Read more here: http://wiki.opencsw.org/cswclassutils > Thanks for writing web docs for it. I've made a link to that page from our main smf page. As a reminder to folks: there are TWO big gain from using SMF support from CSWcswclassutils: 1. You may be able to eliminate any postinstall/preremove scripts from your package 2. If we figure out a way later on, to improve the way we handle SMF; you dont have to repackage your package to take advantage of it! The cswclassutils package will get updated once, so everyone else using it, wont have to repackage as well. From phil at bolthole.com Sat Nov 15 00:01:47 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 14 Nov 2008 15:01:47 -0800 Subject: [csw-maintainers] Class Action Scripts package described on the wiki In-Reply-To: <625385e30811141429m3e0505f5p321540c14931f443@mail.gmail.com>; from bonivart@opencsw.org on Fri, Nov 14, 2008 at 11:29:13PM +0100 References: <625385e30811141429m3e0505f5p321540c14931f443@mail.gmail.com> Message-ID: <20081114150147.Z21898@bolthole.com> Hmmm... a side note, after reading your docs, and looking through the latest script again; If someone defines f cswinitsmf /etc/opt/csw/init.d/cswfoo 0755 root bin and the normal default FMRI will be svc:/network/cswfoo:default It appears that using the #FMRI xyz allows you to override the /network part, but "cswfoo" will be preserved, reguardless of anything you put in. Is that correct? I think that probably is the best behaviour overall, but it's been a long time since we discussed it, so I dont remmeber any more :-} Just wanted to first make sure that the above is true, and then update the docs to be completely clear about that. From bonivart at opencsw.org Sat Nov 15 00:14:15 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Sat, 15 Nov 2008 00:14:15 +0100 Subject: [csw-maintainers] Class Action Scripts package described on the wiki In-Reply-To: <20081114150147.Z21898@bolthole.com> References: <625385e30811141429m3e0505f5p321540c14931f443@mail.gmail.com> <20081114150147.Z21898@bolthole.com> Message-ID: <625385e30811141514r1e1587d6sa990dd0db2694be2@mail.gmail.com> On Sat, Nov 15, 2008 at 12:01 AM, Philip Brown wrote: > Hmmm... a side note, after reading your docs, and looking through the latest > script again; > > If someone defines > > f cswinitsmf /etc/opt/csw/init.d/cswfoo 0755 root bin > > and the normal default FMRI will be > > svc:/network/cswfoo:default > > It appears that using the > > #FMRI xyz > > allows you to override the /network part, but "cswfoo" will be preserved, > reguardless of anything you put in. > > Is that correct? Yes, that is correct. It's only the path that can be affected, the name will always come from the init script name. That is, FMRI can change the default "network" into something else, e.g. "network/smtp", but the init script name will always be appended to it. -- /peter From pfelecan at opencsw.org Sat Nov 15 12:10:35 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Sat, 15 Nov 2008 12:10:35 +0100 Subject: [csw-maintainers] ARCH=all packages In-Reply-To: <625385e30811111328h79e42f9dsad7f772e4ff19583@mail.gmail.com> (Peter Bonivart's message of "Tue\, 11 Nov 2008 22\:28\:25 +0100") References: <20081111070559.C90125@bolthole.com> <95A2B05A-8BAE-47F0-9F26-570178B2F813@opencsw.org> <625385e30811111313w5a8ec92cgb2b8e361ef40c8a5@mail.gmail.com> <51C0A148-67DA-4121-B3E2-4A107E04CA60@opencsw.org> <625385e30811111328h79e42f9dsad7f772e4ff19583@mail.gmail.com> Message-ID: "Peter Bonivart" writes: > On Tue, Nov 11, 2008 at 10:17 PM, Dagobert Michelsen wrote: >> Am 11.11.2008 um 22:13 schrieb Peter Bonivart: >>> Maybe Z?rich can bring some much needed change. > If I'm alone thinking we need to open up a lot of stuff then I You're not alone. > For reference, here's some suggestions I wrote a while ago: > http://wiki.opencsw.org/suggestions A very good basis for parts of the bylaws of the organization. -- Peter From pfelecan at opencsw.org Sat Nov 15 18:43:14 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Sat, 15 Nov 2008 18:43:14 +0100 Subject: [csw-maintainers] "contact maintainer" facility doesn't work Message-ID: The following link: http://www.opencsw.org/eml.php doesn't work; after entering the sender's address and the message, I see: "SERVER ERROR: Cannot submit form.Please try again later." Can this be corrected please? Also, can we have a single page form, i.e. all the information and the submit button on the same page --- currently we have 3 pages... -- Peter From pfelecan at opencsw.org Sat Nov 15 18:47:56 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Sat, 15 Nov 2008 18:47:56 +0100 Subject: [csw-maintainers] mantis access Message-ID: I'm trying to access mantis with the old user name/password couple. It doesn't work. Is the user pfelecan still valid/existing? If yes, I would like my password reset to a known value. BTW, who's in charge with the administration of mantis? -- Peter From trygvel at opencsw.org Sat Nov 15 19:42:40 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sat, 15 Nov 2008 19:42:40 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> Message-ID: <491F1820.6080608@opencsw.org> Dagobert Michelsen wrote: > Hi James, > > Am 08.11.2008 um 17:06 schrieb James Lee: >> On 08/11/08, 15:40:29, Dagobert Michelsen wrote >> regarding >> Re: [csw-maintainers] Java... again!: >> >>> jdk5-1.5.0_15,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz >>> jdk5-1.5.0_15,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz >>> jdk6-6u7,REV=2008.11.08-SunOS5.8-i386-CSW.pkg.gz >>> jdk6-6u7,REV=2008.11.08-SunOS5.8-sparc-CSW.pkg.gz >> Latest 1.5 is Update 16 >> http://java.sun.com/javase/downloads/index_jdk5.jsp >> >> The latest 1.6 is Update 10. >> http://java.sun.com/javase/downloads/index.jsp > > I got them from the archive page. Who can imagine > archived versions would be old? Me??? Oh well... > Heres some warmed up Java in > : > > jre13-1.3.1_22,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz > jre13-1.3.1_22,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz > jre14-1.4.2_17,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz > jre14-1.4.2_17,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz > jre5-1.5.0_16,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz > jre5-1.5.0_16,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz > jre6-1.6.0_10,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz > jre6-1.6.0_10,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz > > jdk13-1.3.1_22,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz > jdk13-1.3.1_22,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz > jdk14-1.4.2_17,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz > jdk14-1.4.2_17,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz > jdk5-1.5.0_16,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz > jdk5-1.5.0_16,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz > jdk6-1.6.0_10,REV=2008.11.09-SunOS5.8-i386-CSW.pkg.gz > jdk6-1.6.0_10,REV=2008.11.09-SunOS5.8-sparc-CSW.pkg.gz > >> It identifies itself: >> >> $ java -version >> java version "1.6.0_10" >> Java(TM) SE Runtime Environment (build 1.6.0_10-b33) >> Java HotSpot(TM) Server VM (build 11.0-b15, mixed mode) >> >> So why use break the pattern of naming, I'd expect the package to be >> identified similarly as "1.6.0_10". > > I should never have followed marketing numbers. The package > now identified itself with the technical version number. > > James, do you mind testing these? Some comments: * Can the JDKs be installed under /opt/csw/jdk to reduce the /opt/csw clutter. That also more similar to how it is installed under /usr * I like the way Sun does it with their "instances". If my package depend on Java 5 or 6 I would like to default the JDK path to /opt/csw/jdk/instance/jdk1.5.0. $ ls -l /usr/jdk /usr/jdk/instances/ /usr/jdk: total 10 drwxr-xr-x 4 root bin 512 Feb 29 2008 instances lrwxrwxrwx 1 root other 18 Nov 5 16:30 jdk1.5.0_16 -> instances/jdk1.5.0 lrwxrwxrwx 1 root other 18 Nov 5 16:43 jdk1.6.0_10 -> instances/jdk1.6.0 lrwxrwxrwx 1 root other 11 Nov 5 16:43 latest -> jdk1.6.0_10 drwxr-xr-x 7 root bin 512 Nov 5 16:46 packages /usr/jdk/instances/: total 4 drwxr-xr-x 9 root bin 512 Nov 5 16:49 jdk1.5.0 drwxr-xr-x 9 root bin 512 Nov 5 16:51 jdk1.6.0 -- Trygve From ihsan at opencsw.org Sat Nov 15 21:45:55 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Sat, 15 Nov 2008 21:45:55 +0100 Subject: [csw-maintainers] "contact maintainer" facility doesn't work In-Reply-To: References: Message-ID: <491F3503.3070200@opencsw.org> Hello Peter, On 11/15/08 18:43, Peter FELECAN wrote: > The following link: http://www.opencsw.org/eml.php doesn't work; after > entering the sender's address and the message, I see: > > "SERVER ERROR: Cannot submit form.Please try again later." I just fixed that. The problem was, that PHP was not using /usr/lib/sendmail. Ihsan -- http://blog.dogan.ch/ http://ihsan.dogan.ch/ From phil at bolthole.com Sat Nov 15 21:48:08 2008 From: phil at bolthole.com (Philip Brown) Date: Sat, 15 Nov 2008 12:48:08 -0800 Subject: [csw-maintainers] mantis access In-Reply-To: ; from pfelecan@opencsw.org on Sat, Nov 15, 2008 at 06:47:56PM +0100 References: Message-ID: <20081115124808.B40283@bolthole.com> On Sat, Nov 15, 2008 at 06:47:56PM +0100, Peter FELECAN wrote: > I'm trying to access mantis with the old user name/password couple. It > doesn't work. > > Is the user pfelecan still valid/existing? If yes, I would like my > password reset to a known value. > > BTW, who's in charge with the administration of mantis? i'd rather not be. but effectly, I am :-} i just reset it. course, that wouldht actually HELP you, if email isnt working. but hopefully, Ihsan's fix has it working again now. From dam at opencsw.org Sat Nov 15 23:52:11 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 15 Nov 2008 23:52:11 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <491F1820.6080608@opencsw.org> References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> Message-ID: Hi Trygve, Am 15.11.2008 um 19:42 schrieb Trygve Laugst?l: > Some comments: > > * Can the JDKs be installed under /opt/csw/jdk to reduce the /opt/csw > clutter. That also more similar to how it is installed under /usr Sure. > * I like the way Sun does it with their "instances". If my package > depend on Java 5 or 6 I would like to default the JDK path to > /opt/csw/jdk/instance/jdk1.5.0. > > $ ls -l /usr/jdk /usr/jdk/instances/ > /usr/jdk: > total 10 > drwxr-xr-x 4 root bin 512 Feb 29 2008 instances > lrwxrwxrwx 1 root other 18 Nov 5 16:30 jdk1.5.0_16 -> > instances/jdk1.5.0 > lrwxrwxrwx 1 root other 18 Nov 5 16:43 jdk1.6.0_10 -> > instances/jdk1.6.0 > lrwxrwxrwx 1 root other 11 Nov 5 16:43 latest -> > jdk1.6.0_10 > drwxr-xr-x 7 root bin 512 Nov 5 16:46 packages > > /usr/jdk/instances/: > total 4 > drwxr-xr-x 9 root bin 512 Nov 5 16:49 jdk1.5.0 > drwxr-xr-x 9 root bin 512 Nov 5 16:51 jdk1.6.0 But why /usr/jdk/instances/jdkxxx instead of /usr/jdk/jdkxxxx? Why is there the symlink? And: Should this also be true for JREs? Best regards -- Dago From william at wbonnet.net Sun Nov 16 00:48:39 2008 From: william at wbonnet.net (William Bonnet) Date: Sun, 16 Nov 2008 00:48:39 +0100 Subject: [csw-maintainers] Installing new package on the farm Message-ID: <491F5FD7.3010107@wbonnet.net> Hi Please Dago could you install some new package on the farm ? The packages are "proto" from Xorg which are missing from Solaris. I created these packages to build the dependencies of Firefox. I will have more installation request in the next hours/days. Dependencies will be built step by step... Thanks in advance 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 phil at bolthole.com Sun Nov 16 02:54:48 2008 From: phil at bolthole.com (Philip Brown) Date: Sat, 15 Nov 2008 17:54:48 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: ; from dam@opencsw.org on Sat, Nov 15, 2008 at 11:52:11PM +0100 References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> Message-ID: <20081115175448.A45790@bolthole.com> On Sat, Nov 15, 2008 at 11:52:11PM +0100, Dagobert Michelsen wrote: > Hi Trygve, > > Am 15.11.2008 um 19:42 schrieb Trygve Laugst?l: > > Some comments: > > > > * Can the JDKs be installed under /opt/csw/jdk to reduce the /opt/csw > > clutter. That also more similar to how it is installed under /usr > > Sure. waitaminit.. what about if they only want runtimes? seems like perhaps /opt/csw/java might be better. soo... /opt/csw/java/1.5.0 and under 1.5.0 would be both runtime and jdk executables? From frederic.vandevelde at paradigmo.com Sun Nov 16 10:02:20 2008 From: frederic.vandevelde at paradigmo.com (frederic.vandevelde at paradigmo.com) Date: Sun, 16 Nov 2008 10:02:20 +0100 Subject: [csw-maintainers] newpkgs notes, on why packages may be held there In-Reply-To: <20081110113914.G94907@bolthole.com> References: <20081110113914.G94907@bolthole.com> Message-ID: Hi, Stupid question but where is newpkgs located now ? Frederic. On 10 Nov 2008, at 20:39, Philip Brown wrote: > FYI: Becaue I tend to forget, myself, I have now started to keep > notes on why > particular packages are being 'held' in newpkgs. > > I used to keep an old file in my home dir, but it will be > /home/newpkgs/00-README > from now on. > Nice and easy to spot now. > > > and also FYI: I always email people when there are issues with their > packages. There is no additional requirement for people to go read > that > file themselves. This is just so I can delete my old emails safely, > without forgetting why a package is sitting there. Or as a reminder > to YOU, > if you happen to forget the issue with your own package ;-) > > > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers From bonivart at opencsw.org Sun Nov 16 10:05:26 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Sun, 16 Nov 2008 10:05:26 +0100 Subject: [csw-maintainers] newpkgs notes, on why packages may be held there In-Reply-To: References: <20081110113914.G94907@bolthole.com> Message-ID: <625385e30811160105n6adc703am7347a4013a5a103a@mail.gmail.com> On Sun, Nov 16, 2008 at 10:02 AM, wrote: > Hi, > > Stupid question but where is newpkgs located now ? Use scp from the build farm to transfer your packages to www.opencsw.org:/home/newpkgs. -- /peter From fred at opencsw.org Sun Nov 16 10:20:40 2008 From: fred at opencsw.org (Frederic Van De Velde) Date: Sun, 16 Nov 2008 10:20:40 +0100 Subject: [csw-maintainers] newpkgs notes, on why packages may be held there In-Reply-To: <625385e30811160105n6adc703am7347a4013a5a103a@mail.gmail.com> References: <20081110113914.G94907@bolthole.com> <625385e30811160105n6adc703am7347a4013a5a103a@mail.gmail.com> Message-ID: <52DB87A1-3B0F-4C11-AE55-C7DE23098914@opencsw.org> Seems my ssh key isn't there: fred at login [login]:/home/fred/staging/build-16.Nov.2008 > scp * www.opencsw.org :/home/newpkgs/ Password: Fred. On 16 Nov 2008, at 10:05, Peter Bonivart wrote: > On Sun, Nov 16, 2008 at 10:02 AM, > wrote: >> Hi, >> >> Stupid question but where is newpkgs located now ? > > Use scp from the build farm to transfer your packages to > www.opencsw.org:/home/newpkgs. > > -- > /peter > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers From pfelecan at opencsw.org Sun Nov 16 10:24:58 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Sun, 16 Nov 2008 10:24:58 +0100 Subject: [csw-maintainers] "contact maintainer" facility doesn't work References: <491F3503.3070200@opencsw.org> Message-ID: Ihsan Dogan writes: > Hello Peter, > > On 11/15/08 18:43, Peter FELECAN wrote: > >> The following link: http://www.opencsw.org/eml.php doesn't work; after >> entering the sender's address and the message, I see: >> >> "SERVER ERROR: Cannot submit form.Please try again later." > > I just fixed that. The problem was, that PHP was not using > /usr/lib/sendmail. Thank you Ihsan. It works now. -- Peter From pfelecan at opencsw.org Sun Nov 16 10:28:12 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Sun, 16 Nov 2008 10:28:12 +0100 Subject: [csw-maintainers] mantis access In-Reply-To: <20081115124808.B40283@bolthole.com> (Philip Brown's message of "Sat\, 15 Nov 2008 12\:48\:08 -0800") References: <20081115124808.B40283@bolthole.com> Message-ID: Philip Brown writes: > On Sat, Nov 15, 2008 at 06:47:56PM +0100, Peter FELECAN wrote: >> I'm trying to access mantis with the old user name/password couple. It >> doesn't work. >> >> Is the user pfelecan still valid/existing? If yes, I would like my >> password reset to a known value. >> >> BTW, who's in charge with the administration of mantis? > > i'd rather not be. but effectly, I am :-} Please add this topic int the Wiki for discussion at IRL --- I think that under the heading "people" should be alright. > i just reset it. course, that wouldht actually HELP you, if email isnt > working. but hopefully, Ihsan's fix has it working again now. It works and I succeeded resetting my Mantis password. Thank you. -- Peter From frederic.vandevelde at paradigmo.com Sun Nov 16 10:00:28 2008 From: frederic.vandevelde at paradigmo.com (frederic.vandevelde at paradigmo.com) Date: Sun, 16 Nov 2008 10:00:28 +0100 Subject: [csw-maintainers] newpkgs notes, on why packages may be held there In-Reply-To: <20081110113914.G94907@bolthole.com> References: <20081110113914.G94907@bolthole.com> Message-ID: Hi, Stupid question but where is newpkgs located now ? Frederic. On 10 Nov 2008, at 20:39, Philip Brown wrote: > FYI: Becaue I tend to forget, myself, I have now started to keep > notes on why > particular packages are being 'held' in newpkgs. > > I used to keep an old file in my home dir, but it will be > /home/newpkgs/00-README > from now on. > Nice and easy to spot now. > > > and also FYI: I always email people when there are issues with their > packages. There is no additional requirement for people to go read > that > file themselves. This is just so I can delete my old emails safely, > without forgetting why a package is sitting there. Or as a reminder > to YOU, > if you happen to forget the issue with your own package ;-) > > > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers From trygvel at opencsw.org Sun Nov 16 12:21:32 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sun, 16 Nov 2008 12:21:32 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> Message-ID: <4920023C.3030701@opencsw.org> Dagobert Michelsen wrote: > Hi Trygve, > > Am 15.11.2008 um 19:42 schrieb Trygve Laugst?l: >> Some comments: >> >> * Can the JDKs be installed under /opt/csw/jdk to reduce the /opt/csw >> clutter. That also more similar to how it is installed under /usr > > Sure. > >> * I like the way Sun does it with their "instances". If my package >> depend on Java 5 or 6 I would like to default the JDK path to >> /opt/csw/jdk/instance/jdk1.5.0. >> >> $ ls -l /usr/jdk /usr/jdk/instances/ >> /usr/jdk: >> total 10 >> drwxr-xr-x 4 root bin 512 Feb 29 2008 instances >> lrwxrwxrwx 1 root other 18 Nov 5 16:30 jdk1.5.0_16 -> >> instances/jdk1.5.0 >> lrwxrwxrwx 1 root other 18 Nov 5 16:43 jdk1.6.0_10 -> >> instances/jdk1.6.0 >> lrwxrwxrwx 1 root other 11 Nov 5 16:43 latest -> >> jdk1.6.0_10 >> drwxr-xr-x 7 root bin 512 Nov 5 16:46 packages >> >> /usr/jdk/instances/: >> total 4 >> drwxr-xr-x 9 root bin 512 Nov 5 16:49 jdk1.5.0 >> drwxr-xr-x 9 root bin 512 Nov 5 16:51 jdk1.6.0 > > But why /usr/jdk/instances/jdkxxx instead of /usr/jdk/jdkxxxx? Dunno, got to ask Sun about that :) > Why is there the symlink? > > And: Should this also be true for JREs?\ IMO yes, but I just tried to download all the 1.4, 1.5 and 1.6 JREs and they don't have pkg installers for any of them. Phil asked if the directory should be "java" and that what what I originally wanted too, but Sun uses /usr/java as a symlink to the latest java, just like /usr/jdk/latest. So this is what I want: /opt/csw/jdk/jdk1.5.0_16 /opt/csw/jdk/instances/jdk1.5.0 -> ../jdk1.5.0_16 /opt/csw/jdk/jdk1.6.0_10 /opt/csw/jdk/instances/jdk1.6.0 -> ../jdk1.5.0_10 And for the JREs: /opt/csw/jre/jdk1.5.0_16 /opt/csw/jre/instances/jdk1.5.0 -> ../jdk1.5.0_16 /opt/csw/jre/jdk1.6.0_10 /opt/csw/jre/instances/jdk1.6.0 -> ../jdk1.5.0_10 I wouldn't mind having a "latest" symlink too, but then we need a way to figure out if a package is "newer" than another (like, if I install CSWjdk6 and then CSWjdk5, I don't want the symlink to be overwritten). -- Trygve From ihsan at opencsw.org Sun Nov 16 12:26:33 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Sun, 16 Nov 2008 12:26:33 +0100 Subject: [csw-maintainers] newpkgs notes, on why packages may be held there In-Reply-To: <52DB87A1-3B0F-4C11-AE55-C7DE23098914@opencsw.org> References: <20081110113914.G94907@bolthole.com> <625385e30811160105n6adc703am7347a4013a5a103a@mail.gmail.com> <52DB87A1-3B0F-4C11-AE55-C7DE23098914@opencsw.org> Message-ID: <49200369.3060700@opencsw.org> Am 16.11.2008 10:20 Uhr, Frederic Van De Velde schrieb: > Seems my ssh key isn't there: > > fred at login [login]:/home/fred/staging/build-16.Nov.2008 > scp * www.opencsw.org > :/home/newpkgs/ > Password: Could you please send me you ssh public key? I'll add it to your account. Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From dam at opencsw.org Sun Nov 16 14:41:23 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 16 Nov 2008 14:41:23 +0100 Subject: [csw-maintainers] Installing new package on the farm In-Reply-To: <491F5FD7.3010107@wbonnet.net> References: <491F5FD7.3010107@wbonnet.net> Message-ID: <4F938ABC-5CB0-4E20-B671-BF8A439BA7F4@opencsw.org> Hi William, Am 16.11.2008 um 00:48 schrieb William Bonnet: > Please Dago could you install some new package on the farm ? The > packages are "proto" from Xorg which are missing from Solaris. I > created > these packages to build the dependencies of Firefox. The following packages have been installed on build8s build8x on the Baltic Online buildfarm: application CSWinputproto inputproto - inputproto application CSWkbproto kbproto - kbproto application CSWrenderproto renderproto - renderproto application CSWxcbproto xcbproto - xcb-proto application CSWxextproto xextproto - xextproto application CSWxproto xproto - xproto There is a conflict on /opt/csw/include/X11/extensions/render.h /opt/csw/include/X11/extensions/renderproto.h between the old CSWrenderdev and the new CSWrenderproto. And a conflict on /opt/csw/include/X11/Xfuncproto.h between the old CSWlibxcomposite and the new CSWxproto. I overwrote the existing files with the new ones. > I will have more installation request in the next hours/days. > Dependencies will be built step by step... Sure. Just let me know. Best regards -- Dago From william at wbonnet.net Sun Nov 16 21:11:42 2008 From: william at wbonnet.net (William Bonnet) Date: Sun, 16 Nov 2008 21:11:42 +0100 Subject: [csw-maintainers] Installing new package on the farm In-Reply-To: <4F938ABC-5CB0-4E20-B671-BF8A439BA7F4@opencsw.org> References: <491F5FD7.3010107@wbonnet.net> <4F938ABC-5CB0-4E20-B671-BF8A439BA7F4@opencsw.org> Message-ID: <49207E7E.9090504@wbonnet.net> Hi Dagobert Thanks > There is a conflict on > /opt/csw/include/X11/extensions/render.h > /opt/csw/include/X11/extensions/renderproto.h > between the old CSWrenderdev and the new CSWrenderproto. > > And a conflict on > /opt/csw/include/X11/Xfuncproto.h > between the old CSWlibxcomposite and the new CSWxproto. > I will update this two packages in the next updates. Conflicts will be solved. > Sure. Just let me know. > I continue the compilation and will ask you more maybe tonight or tomorrow. 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 dam at opencsw.org Sun Nov 16 21:29:07 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 16 Nov 2008 21:29:07 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <4920023C.3030701@opencsw.org> References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> Message-ID: Hi Trygve, Am 16.11.2008 um 12:21 schrieb Trygve Laugst?l: > Dagobert Michelsen wrote: >> Why is there the symlink? >> >> And: Should this also be true for JREs?\ > > IMO yes, but I just tried to download all the 1.4, 1.5 and 1.6 JREs > and > they don't have pkg installers for any of them. > > Phil asked if the directory should be "java" and that what what I > originally wanted too, but Sun uses /usr/java as a symlink to the > latest > java, just like /usr/jdk/latest. > > So this is what I want: > > /opt/csw/jdk/jdk1.5.0_16 > /opt/csw/jdk/instances/jdk1.5.0 -> ../jdk1.5.0_16 > > /opt/csw/jdk/jdk1.6.0_10 > /opt/csw/jdk/instances/jdk1.6.0 -> ../jdk1.5.0_10 > > And for the JREs: > > /opt/csw/jre/jdk1.5.0_16 > /opt/csw/jre/instances/jdk1.5.0 -> ../jdk1.5.0_16 > > /opt/csw/jre/jdk1.6.0_10 > /opt/csw/jre/instances/jdk1.6.0 -> ../jdk1.5.0_10 Sun does it just opposite: root at csw [global]:/usr/jdk > ls -la total 14 drwxr-xr-x 4 root bin 512 Aug 18 18:09 . drwxr-xr-x 39 root sys 1024 Aug 19 11:29 .. drwxr-xr-x 3 root bin 512 Aug 18 17:07 instances lrwxrwxrwx 1 root other 7 Aug 18 17:07 j2sdk1.4.2_16 - > ../j2se lrwxrwxrwx 1 root other 18 Aug 18 18:09 jdk1.5.0_16 -> instances/jdk1.5.0 lrwxrwxrwx 1 root other 11 Aug 18 18:09 latest -> jdk1.5.0_16 drwxr-xr-x 8 root bin 512 Aug 18 17:19 packages The files in instances/ and links in jdk/. > I wouldn't mind having a "latest" symlink too, but then we need a > way to > figure out if a package is "newer" than another (like, if I install > CSWjdk6 and then CSWjdk5, I don't want the symlink to be overwritten). Is it really useful to have a just-the-latest-I-don't-care-Java? I would imagine it would be best to have an apache-like configuration: The Java software maintainers (e. g. Tomcat) chooses the build jre and depends on that. The version is now 1.4.2, should that be jdk14 or jdk142? James, any advice? Best regards -- Dago From phil at bolthole.com Sun Nov 16 22:19:59 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 16 Nov 2008 13:19:59 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: ; from dam@opencsw.org on Sun, Nov 16, 2008 at 09:29:07PM +0100 References: <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> Message-ID: <20081116131959.D99438@bolthole.com> On Sun, Nov 16, 2008 at 09:29:07PM +0100, Dagobert Michelsen wrote: > Is it really useful to have a just-the-latest-I-don't-care-Java? *yes*. Perhaps we could handle it, by having a top level CSWjava, that made symlinks directly /opt/csw/bin/java -> whereever. or, be a shellscript wrapper would probably be better. From james at opencsw.org Mon Nov 17 10:59:25 2008 From: james at opencsw.org (James Lee) Date: Mon, 17 Nov 2008 09:59:25 GMT Subject: [csw-maintainers] Java... again! In-Reply-To: <20081116131959.D99438@bolthole.com> References: <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081116131959.D99438@bolthole.com> Message-ID: <20081117.9592500.3837896452@gyor.oxdrove.co.uk> On 16/11/08, 21:19:59, Philip Brown wrote regarding Re: [csw-maintainers] Java... again!: > > Is it really useful to have a just-the-latest-I-don't-care-Java? > *yes*. > Perhaps we could handle it, by having a top level CSWjava, that made > symlinks directly > /opt/csw/bin/java -> whereever. > or, be a shellscript wrapper would probably be better. An /opt/csw/bin/java link would work. It's possible for java to work out where the jre is from System.getProperty("java.home"); There are a lot of other files in ${JAVA_HOME}/bin that would need to be in /opt/csw/bin too. James. From james at opencsw.org Mon Nov 17 10:59:26 2008 From: james at opencsw.org (James Lee) Date: Mon, 17 Nov 2008 09:59:26 GMT Subject: [csw-maintainers] Java... again! In-Reply-To: References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> Message-ID: <20081117.9592600.991638692@gyor.oxdrove.co.uk> On 16/11/08, 20:29:07, Dagobert Michelsen wrote regarding Re: [csw-maintainers] Java... again!: > > I wouldn't mind having a "latest" symlink too, but then we need a > > way to > > figure out if a package is "newer" than another (like, if I install > > CSWjdk6 and then CSWjdk5, I don't want the symlink to be overwritten). > Is it really useful to have a just-the-latest-I-don't-care-Java? I've yet to find anything that didn't work with the latest - and work better. (Not counting certification issues.) It's possible to build low version compatibility with "-source" and "-target". > I would imagine it would be best to have an apache-like configuration: > The Java software maintainers (e. g. Tomcat) chooses the build jre > and depends on that. In fact Tomcat will need a JDK because it uses tools.jar. If we have packages that depend on both the JRE and JDK we end up with 2 JREs. A JDK packs a JRE so the CSW dependency based delivery model should follow this: JDK requires JRE. We have a fundamental problem with update and Java. As Java is an "environment", dependent packages that run as servers need restarting when java is updated. (This is also affects libraries that are updated and (fail to) support running servers.) James. From phil at bolthole.com Mon Nov 17 18:03:49 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 17 Nov 2008 09:03:49 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081117.9592500.3837896452@gyor.oxdrove.co.uk>; from james@opencsw.org on Mon, Nov 17, 2008 at 09:59:25AM +0000 References: <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081116131959.D99438@bolthole.com> <20081117.9592500.3837896452@gyor.oxdrove.co.uk> Message-ID: <20081117090349.G21898@bolthole.com> On Mon, Nov 17, 2008 at 09:59:25AM +0000, James Lee wrote: > > An /opt/csw/bin/java link would work. It's possible for java to work > out where the jre is from System.getProperty("java.home"); too bad that most things dont USE that. there's lot of badly written java code. you're lucky if it even pays attention to JAVA_HOME. > There are a lot of other files in ${JAVA_HOME}/bin that would need to > be in /opt/csw/bin too. ugh. i hope not "lots". But that would be a reason why it wouuld be better as a wrapper than a symlink. Because a wrapper could set JAVA_HOME appropriately, to where it "really" is. From buysse at umn.edu Mon Nov 17 18:06:20 2008 From: buysse at umn.edu (Joshua Buysse) Date: Mon, 17 Nov 2008 11:06:20 -0600 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081117090349.G21898@bolthole.com> References: <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081116131959.D99438@bolthole.com> <20081117.9592500.3837896452@gyor.oxdrove.co.uk> <20081117090349.G21898@bolthole.com> Message-ID: >> There are a lot of other files in ${JAVA_HOME}/bin that would need to >> be in /opt/csw/bin too. > > ugh. i hope not "lots". > But that would be a reason why it wouuld be better as a wrapper than a > symlink. > Because a wrapper could set JAVA_HOME appropriately, to where it > "really" > is. Would it be worth considering debian's alternatives system? There are other places it could be used as well (multiple versions of perl, python, ruby, etc.) -- Joshua Buysse, System Engineer University of Minnesota, College of Liberal Arts "Daleks do not accept apologies! EXTERMINATE!" -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL: From phil at bolthole.com Mon Nov 17 18:15:56 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 17 Nov 2008 09:15:56 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: ; from buysse@umn.edu on Mon, Nov 17, 2008 at 11:06:20AM -0600 References: <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081116131959.D99438@bolthole.com> <20081117.9592500.3837896452@gyor.oxdrove.co.uk> <20081117090349.G21898@bolthole.com> Message-ID: <20081117091556.J21898@bolthole.com> On Mon, Nov 17, 2008 at 11:06:20AM -0600, Joshua Buysse wrote: > Would it be worth considering debian's alternatives system? There are > other places it could be used as well (multiple versions of perl, > python, ruby, etc.) > it might be. My personal philosophy when comparing things to "how debian does it", is to write up a top level abstract of "what it does", [being as specific as possible, while explicitly NOT including implementation details] Then consider whether we need/want it Then, IF the answer is yes, consider what implementations might be like. From phil at bolthole.com Mon Nov 17 18:37:02 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 17 Nov 2008 09:37:02 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <4920023C.3030701@opencsw.org>; from trygvel@opencsw.org on Sun, Nov 16, 2008 at 12:21:32PM +0100 References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> Message-ID: <20081117093702.Q21898@bolthole.com> On Sun, Nov 16, 2008 at 12:21:32PM +0100, Trygve Laugst?l wrote: > Phil asked if the directory should be "java" and that what what I > originally wanted too, but Sun uses /usr/java as a symlink to the latest > java, just like /usr/jdk/latest. > > So this is what I want: > > /opt/csw/jdk/jdk1.5.0_16 > /opt/csw/jdk/instances/jdk1.5.0 -> ../jdk1.5.0_16 > > /opt/csw/jdk/jdk1.6.0_10 > /opt/csw/jdk/instances/jdk1.6.0 -> ../jdk1.5.0_10 Hmm. I dont think it is nice to "burn" two top-level directories, one for jdk and one for kre. Why dont you like having a combined directory, /opt/csw/java/1.5.0_16 that has both the jre and jdk of that version under it? From buysse at umn.edu Mon Nov 17 18:59:02 2008 From: buysse at umn.edu (Joshua Buysse) Date: Mon, 17 Nov 2008 11:59:02 -0600 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081117093702.Q21898@bolthole.com> References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> Message-ID: On Nov 17, 2008, at 11:37 AM, Philip Brown wrote: > On Sun, Nov 16, 2008 at 12:21:32PM +0100, Trygve Laugst?l wrote: >> Phil asked if the directory should be "java" and that what what I >> originally wanted too, but Sun uses /usr/java as a symlink to the >> latest >> java, just like /usr/jdk/latest. >> >> So this is what I want: >> >> /opt/csw/jdk/jdk1.5.0_16 >> /opt/csw/jdk/instances/jdk1.5.0 -> ../jdk1.5.0_16 >> >> /opt/csw/jdk/jdk1.6.0_10 >> /opt/csw/jdk/instances/jdk1.6.0 -> ../jdk1.5.0_10 > > Hmm. I dont think it is nice to "burn" two top-level directories, > one for > jdk and one for kre. > > Why dont you like having a combined directory, > > /opt/csw/java/1.5.0_16 > > that has both the jre and jdk of that version under it? Compromise: /opt/csw/java/bin/java -> ../instances/jre/bin/java /opt/csw/java/bin/javac -> ../instances/jdk/bin/javac /opt/csw/java/bin/keytool -> ../instances/jdk/bin/keytool ... /opt/csw/java/instances/jdk-1.5.0_16 /opt/csw/java/instances/jdk -> jdk-1.5.0_16 /opt/csw/java/instances/jre -> jdk-1.5.0_16 ? -- Joshua Buysse, System Engineer University of Minnesota, College of Liberal Arts We must not confuse dissent with disloyalty. -Edward R. Murrow -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL: From phil at bolthole.com Mon Nov 17 19:09:28 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 17 Nov 2008 10:09:28 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: ; from buysse@umn.edu on Mon, Nov 17, 2008 at 11:59:02AM -0600 References: <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> Message-ID: <20081117100928.U21898@bolthole.com> On Mon, Nov 17, 2008 at 11:59:02AM -0600, Joshua Buysse wrote: > > On Nov 17, 2008, at 11:37 AM, Philip Brown wrote: > > Why dont you like having a combined directory, > > > > /opt/csw/java/1.5.0_16 > > > > that has both the jre and jdk of that version under it? > > > Compromise: > > /opt/csw/java/bin/java -> ../instances/jre/bin/java > /opt/csw/java/bin/javac -> ../instances/jdk/bin/javac > /opt/csw/java/bin/keytool -> ../instances/jdk/bin/keytool > ... > /opt/csw/java/instances/jdk-1.5.0_16 > /opt/csw/java/instances/jdk -> jdk-1.5.0_16 > /opt/csw/java/instances/jre -> jdk-1.5.0_16 > > ? Hmm. interesting. I'll ask again , though, because I'm not understanding: why dont you like the top level directory as "java"? What are you envisioning being in /opt/csw/java, besides the single directory "instances"? (I'll mention that currently, we already have documented, and in use, a standard for jar files, to live in /opt/csw/share/java http://www.opencsw.org/standards/layout mentions this) From buysse at cla.umn.edu Mon Nov 17 19:16:03 2008 From: buysse at cla.umn.edu (Joshua Buysse) Date: Mon, 17 Nov 2008 12:16:03 -0600 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081117100928.U21898@bolthole.com> References: <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <20081117100928.U21898@bolthole.com> Message-ID: <35B1F1AD-0544-4B87-B2FE-414470AEE7FD@cla.umn.edu> On Nov 17, 2008, at 12:09 PM, Philip Brown wrote: >> /opt/csw/java/bin/java -> ../instances/jre/bin/java >> /opt/csw/java/bin/javac -> ../instances/jdk/bin/javac >> /opt/csw/java/bin/keytool -> ../instances/jdk/bin/keytool >> ... >> /opt/csw/java/instances/jdk-1.5.0_16 >> /opt/csw/java/instances/jdk -> jdk-1.5.0_16 >> /opt/csw/java/instances/jre -> jdk-1.5.0_16 >> >> ? > > Hmm. interesting. I'll ask again , though, because I'm not > understanding: > why dont you like the top level directory as "java"? > What are you envisioning being in /opt/csw/java, besides the single > directory "instances"? Directories for bin, lib, man, and include that point through to the "active" instance (jdk/jre symlinks in instances). That way, a currently selected java version can always be found if PATH includes / opt/csw/java/bin, and MANPATH includes /opt/csw/java/man (or /opt/csw/ java/share/man, but that's not how Sun packages it). > (I'll mention that currently, we already have documented, and in use, > a standard for jar files, to live in /opt/csw/share/java > > http://www.opencsw.org/standards/layout > mentions this) > > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers -- Joshua Buysse, System Engineer University of Minnesota, College of Liberal Arts "I was such a geek that if I could go back in time, I would kick my own ass." -- Wil Wheaton -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL: From phil at bolthole.com Mon Nov 17 19:23:45 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 17 Nov 2008 10:23:45 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <35B1F1AD-0544-4B87-B2FE-414470AEE7FD@cla.umn.edu>; from buysse@cla.umn.edu on Mon, Nov 17, 2008 at 12:16:03PM -0600 References: <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <20081117100928.U21898@bolthole.com> <35B1F1AD-0544-4B87-B2FE-414470AEE7FD@cla.umn.edu> Message-ID: <20081117102345.V21898@bolthole.com> On Mon, Nov 17, 2008 at 12:16:03PM -0600, Joshua Buysse wrote: > > What are you envisioning being in /opt/csw/java, besides the single > > directory "instances"? > > Directories for bin, lib, man, and include that point through to the > "active" instance (jdk/jre symlinks in instances). That way, a > currently selected java version can always be found if PATH includes / > opt/csw/java/bin, and MANPATH includes /opt/csw/java/man (or /opt/csw/ > java/share/man, but that's not how Sun packages it). What about /opt/csw/java/bin, lib, man, being symlinks to ./{VERSION}/bin, instead of ./instances/{VERSION}/bin ? I personally think that is a little cleaner; shorter paths are usually nicer, in my opinion :-) From buysse at umn.edu Mon Nov 17 19:45:13 2008 From: buysse at umn.edu (Joshua Buysse) Date: Mon, 17 Nov 2008 12:45:13 -0600 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081117102345.V21898@bolthole.com> References: <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <20081117100928.U21898@bolthole.com> <35B1F1AD-0544-4B87-B2FE-414470AEE7FD@cla.umn.edu> <20081117102345.V21898@bolthole.com> Message-ID: On Nov 17, 2008, at 12:23 PM, Philip Brown wrote: > On Mon, Nov 17, 2008 at 12:16:03PM -0600, Joshua Buysse wrote: >>> What are you envisioning being in /opt/csw/java, besides the single >>> directory "instances"? >> >> Directories for bin, lib, man, and include that point through to the >> "active" instance (jdk/jre symlinks in instances). That way, a >> currently selected java version can always be found if PATH >> includes / >> opt/csw/java/bin, and MANPATH includes /opt/csw/java/man (or /opt/ >> csw/ >> java/share/man, but that's not how Sun packages it). > > What about /opt/csw/java/bin, lib, man, being symlinks to ./ > {VERSION}/bin, > instead of ./instances/{VERSION}/bin ? > > I personally think that is a little cleaner; shorter paths are usually > nicer, in my opinion :-) No real difference, as long as a current/active symlink is used -- the key is that only one symlink needs to be changed to switch the default version of java. (ie, in /opt/csw/java, current -> jdk-1.5.0_16, or jdk -> jdk-1.4.2_xx, etc.) The java plugin for firefox should probably symlink to /opt/csw/java/ current/... as well. -- Joshua Buysse, System Engineer University of Minnesota, College of Liberal Arts We must not confuse dissent with disloyalty. -Edward R. Murrow -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL: From phil at bolthole.com Mon Nov 17 19:52:15 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 17 Nov 2008 10:52:15 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081117102345.V21898@bolthole.com>; from phil@bolthole.com on Mon, Nov 17, 2008 at 10:23:45AM -0800 References: <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <20081117100928.U21898@bolthole.com> <35B1F1AD-0544-4B87-B2FE-414470AEE7FD@cla.umn.edu> <20081117102345.V21898@bolthole.com> Message-ID: <20081117105215.W21898@bolthole.com> On Mon, Nov 17, 2008 at 10:23:45AM -0800, Philip Brown wrote: > > What about /opt/csw/java/bin, lib, man, being symlinks to ./{VERSION}/bin, > instead of ./instances/{VERSION}/bin ? or, if we wanted to be completely consistent, by a user setting JAVA_HOME, PATH, etc to /opt/csw/java/someversion perhaps have /opt/csw/java/default/bin -> ../{VERSION}/bin and so forth, so that /opt/csw/java only contains version subdirectories directly or having /opt/csw/java/default itself be a symlink to a specific version dir. (That's actually what they do at USC a lot. Seems to be appropriate in this case, maybe ) From phil at bolthole.com Mon Nov 17 19:54:18 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 17 Nov 2008 10:54:18 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: ; from buysse@umn.edu on Mon, Nov 17, 2008 at 12:45:13PM -0600 References: <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <20081117100928.U21898@bolthole.com> <35B1F1AD-0544-4B87-B2FE-414470AEE7FD@cla.umn.edu> <20081117102345.V21898@bolthole.com> Message-ID: <20081117105418.X21898@bolthole.com> On Mon, Nov 17, 2008 at 12:45:13PM -0600, Joshua Buysse wrote: > No real difference, as long as a current/active symlink is used -- the > key is that only one symlink needs to be changed to switch the default > version of java. (ie, in /opt/csw/java, current -> jdk-1.5.0_16, or > jdk -> jdk-1.4.2_xx, etc.) > > The java plugin for firefox should probably symlink to /opt/csw/java/ > current/... as well. so then we get to quibble about whether that symlink should be called "current", "default", "stable", "latest", ...... :-) I think that "default" seems to most closely fit the purpose of the thing. From trygvel at opencsw.org Mon Nov 17 19:44:45 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Mon, 17 Nov 2008 19:44:45 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081117093702.Q21898@bolthole.com> References: <636587E5-2EAF-460F-AD03-9C3C9DFD9BAA@opencsw.org> <490F18D9.7090702@opencsw.org> <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> Message-ID: <4921BB9D.4030403@opencsw.org> Philip Brown wrote: > On Sun, Nov 16, 2008 at 12:21:32PM +0100, Trygve Laugst?l wrote: >> Phil asked if the directory should be "java" and that what what I >> originally wanted too, but Sun uses /usr/java as a symlink to the latest >> java, just like /usr/jdk/latest. >> >> So this is what I want: >> >> /opt/csw/jdk/jdk1.5.0_16 >> /opt/csw/jdk/instances/jdk1.5.0 -> ../jdk1.5.0_16 >> >> /opt/csw/jdk/jdk1.6.0_10 >> /opt/csw/jdk/instances/jdk1.6.0 -> ../jdk1.5.0_10 > > Hmm. I dont think it is nice to "burn" two top-level directories, one for > jdk and one for kre. > > Why dont you like having a combined directory, > > /opt/csw/java/1.5.0_16 > > that has both the jre and jdk of that version under it? Because Sun uses /usr/java as a complete JDK isntallation (or was it JRE?..) -- Trygve From phil at bolthole.com Mon Nov 17 20:17:30 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 17 Nov 2008 11:17:30 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <4921BB9D.4030403@opencsw.org>; from trygvel@opencsw.org on Mon, Nov 17, 2008 at 07:44:45PM +0100 References: <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> Message-ID: <20081117111730.B21898@bolthole.com> On Mon, Nov 17, 2008 at 07:44:45PM +0100, Trygve Laugst?l wrote: > Philip Brown wrote: > > Why dont you like having a combined directory, > > > > /opt/csw/java/1.5.0_16 > > > > that has both the jre and jdk of that version under it? > > Because Sun uses /usr/java as a complete JDK isntallation (or was it JRE?..) Hmm... I'm not sure what you are disliking here. Are you going with the principle that "anything with java as the last component of its name, should be a full runtime", usable as JAVA_HOME? Just becuase sun does it that way? Do you not think that JAVA_HOME=/opt/csw/java/default would be just as appropriate? And, given that sun seems to give users a choice of JAVA_HOME=/usr/java JAVA_HOME=/usr/js2e JAVA_HOME=/usr/jdk/j2sdk1.4.2.16 JAVA_HOME=/usr/jdk/jdk1.5.0_16 JAVA_HOME=/usr/jdk/instances/jdk1.5.0 JAVA_HOME=/usr/jdk/latest # oh look!! looks like /opt/csw/java/default :) I think that in this case, we should toss out what sun does, and start with our own CONSISTENT naming, that can stay consistent pretty much from now until forever :-) (JAVA_HOME=/opt/csw/java/{pick-your-version}, where version can also be "default") From trygvel at opencsw.org Mon Nov 17 20:26:25 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Mon, 17 Nov 2008 20:26:25 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081117111730.B21898@bolthole.com> References: <20081103085011.B95235@bolthole.com> <491041B0.5000501@opencsw.org> <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> Message-ID: <4921C561.5030406@opencsw.org> Philip Brown wrote: > On Mon, Nov 17, 2008 at 07:44:45PM +0100, Trygve Laugst?l wrote: >> Philip Brown wrote: >>> Why dont you like having a combined directory, >>> >>> /opt/csw/java/1.5.0_16 >>> >>> that has both the jre and jdk of that version under it? >> Because Sun uses /usr/java as a complete JDK isntallation (or was it JRE?..) > > Hmm... I'm not sure what you are disliking here. > Are you going with the principle that "anything with java as the last > component of its name, should be a full runtime", usable as JAVA_HOME? > Just becuase sun does it that way? > > Do you not think that JAVA_HOME=/opt/csw/java/default > would be just as appropriate? > > And, given that sun seems to give users a choice of > JAVA_HOME=/usr/java > JAVA_HOME=/usr/js2e > JAVA_HOME=/usr/jdk/j2sdk1.4.2.16 > JAVA_HOME=/usr/jdk/jdk1.5.0_16 > JAVA_HOME=/usr/jdk/instances/jdk1.5.0 > JAVA_HOME=/usr/jdk/latest # oh look!! looks like /opt/csw/java/default :) > > I think that in this case, we should toss out what sun does, and start with > our own CONSISTENT naming, that can stay consistent pretty much from now > until forever :-) > > (JAVA_HOME=/opt/csw/java/{pick-your-version}, where version can > also be "default") I'm all for consistency and my point was really "just because sun does it". By not inventing *yet* another way to find the Java runtime we're saving some brain cells. As long as it is doable. /opt/csw is already a pretty decent mess if you ask mere. Stuff is no where near self consistent or similar to /etc, either Solaris or other distros. -- Trygve From phil at bolthole.com Mon Nov 17 20:46:08 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 17 Nov 2008 11:46:08 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <4921C561.5030406@opencsw.org>; from trygvel@opencsw.org on Mon, Nov 17, 2008 at 08:26:25PM +0100 References: <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> Message-ID: <20081117114608.C21898@bolthole.com> On Mon, Nov 17, 2008 at 08:26:25PM +0100, Trygve Laugst?l wrote: > Philip Brown wrote: > > I think that in this case, we should toss out what sun does, and start with > > our own CONSISTENT naming, that can stay consistent pretty much from now > > until forever :-) > > > > (JAVA_HOME=/opt/csw/java/{pick-your-version}, where version can > > also be "default") > > I'm all for consistency and my point was really "just because sun does > it". By not inventing *yet* another way to find the Java runtime we're > saving some brain cells. ok... I think you're saying that you're ok with the above "consistent" strategy, so I think I am counting 3 "votes" in favour of the above, and none opposed so far. > /opt/csw is already a > pretty decent mess if you ask mere. Stuff is no where near self > consistent or similar to /etc, either Solaris or other distros. I do agree that in certain areas, our packages are inconsistent. and I think that we should all be 'encouraged',and encourage one another, to clean things up. I for one, will be "cleaning up" my very old and ugly apache1 package, to finally adhere to the proper standards, of "writable stuff belongs in /var/opt/csw/pkgname, NOT /opt/csw/var" and so on. But that will take a large amount of work, so it's waiting for next weekend :-/ From dam at opencsw.org Mon Nov 17 21:15:27 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 17 Nov 2008 21:15:27 +0100 Subject: [csw-maintainers] Maintainer buglisting available Message-ID: <682C3E40-526A-4D19-9F36-D1DD00AB47C9@opencsw.org> Fellow maintainers, as you all know there is the Mantis bugtracking system at However, some research showed that there is quite an amount of reported bugs. Some new, some old, some already fixed but not acknowledged or closed. I can say for myself that tracking bugs in Mantis was not that straightforward as it could be. To make open bugs more prominent I added a link to the bottom of each maintainer page which shows all bugs for packages the maintainer is responsible for needing attention. So please see what you have missed in the past ;-) Additionally, there are three packages orphaned which are not associated to a maintainer: These are * dsniff * netsnmp * ntop It would be very nice if a maintainer would be willing to adopt them as those packages are all quite prominent. Best regards -- Dago From phil at bolthole.com Mon Nov 17 22:43:20 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 17 Nov 2008 13:43:20 -0800 Subject: [csw-maintainers] bio pages Message-ID: <20081117134320.I21898@bolthole.com> FYI: I bumped over the php code that handles the "bio" inclusion, for your maintainer page. It has not been working since the move, up until now. So, http://www.opencsw.org/maintainers/yourlogin will once again include $HOME/public_html/bio.html if you create it and make it publically readable. From dam at opencsw.org Mon Nov 17 22:45:25 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 17 Nov 2008 22:45:25 +0100 Subject: [csw-maintainers] Experimental Atom Feed for testing/ Message-ID: Fellow maintainers, tonight I hacked a rudimentary atom feed for testing/. Please subscribe to Maybe someone has a link for me on how to integrate this to the testing.html webpage. Feed-back :-) as always welcome. Best regards -- Dago From dam at opencsw.org Mon Nov 17 22:56:40 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 17 Nov 2008 22:56:40 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081117114608.C21898@bolthole.com> References: <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> Message-ID: <5F994B04-687B-4AC3-91AE-DAAE62F4716B@opencsw.org> Hi, Am 17.11.2008 um 20:46 schrieb Philip Brown: > ok... I think you're saying that you're ok with the above "consistent" > strategy, so I think I am counting 3 "votes" in favour of the above, > and > none opposed so far. Is this an agreeable solution or is there still need for discussion? If everyone on this list can live with this I'll repackage after this spec. But not before as it takes forever to pack 100+ MB :-P What about JDK/JRE separation? JDK includes a JRE but essentially I don't want to extract the JRE from there as this is mainly asking for trouble. Should we just distribute the JDK then? Best regards -- Dago From phil at bolthole.com Tue Nov 18 02:24:08 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 17 Nov 2008 17:24:08 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <5F994B04-687B-4AC3-91AE-DAAE62F4716B@opencsw.org>; from dam@opencsw.org on Mon, Nov 17, 2008 at 10:56:40PM +0100 References: <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> <5F994B04-687B-4AC3-91AE-DAAE62F4716B@opencsw.org> Message-ID: <20081117172408.D39788@bolthole.com> On Mon, Nov 17, 2008 at 10:56:40PM +0100, Dagobert Michelsen wrote: > ... > What about JDK/JRE separation? JDK includes a JRE but > essentially I don't want to extract the JRE from there > as this is mainly asking for trouble. Should we just > distribute the JDK then? ?!?!?!? Personally, I think we serve our users well, by splitting out jre. I would guess that a vast majority of people who "need java", actualy just specifically need the JRE. Unless the jdk addds only a trivial amount of extra bytes (and I'm pretty sure it's not trivial! :-) seems like the best thing to do is split em. I dont see what this "trouble" would be that you reference. Perhaps you could explain further. From trygvel at opencsw.org Tue Nov 18 07:51:57 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Tue, 18 Nov 2008 07:51:57 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081117172408.D39788@bolthole.com> References: <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> <5F994B04-687B-4AC3-91AE-DAAE62F4716B@opencsw.org> <20081117172408.D39788@bolthole.com> Message-ID: <4922660D.9070203@opencsw.org> Philip Brown wrote: > On Mon, Nov 17, 2008 at 10:56:40PM +0100, Dagobert Michelsen wrote: >> ... >> What about JDK/JRE separation? JDK includes a JRE but >> essentially I don't want to extract the JRE from there >> as this is mainly asking for trouble. Should we just >> distribute the JDK then? > > ?!?!?!? > > Personally, I think we serve our users well, by splitting out jre. > > I would guess that a vast majority of people who "need java", actualy > just specifically need the JRE. > > > Unless the jdk addds only a trivial amount of extra bytes (and I'm pretty > sure it's not trivial! :-) seems like the best thing to do is split em. > I dont see what this "trouble" would be that you reference. Perhaps you > could explain further. I agree with Phil here, we need two packages. I would never use JDK or JRE package that has been modified by upstream packages, just see the just that Debian tries deliver with their "java" packages. -- Trygve From trygvel at opencsw.org Tue Nov 18 07:54:09 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Tue, 18 Nov 2008 07:54:09 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081117114608.C21898@bolthole.com> References: <20081108.16061000.3036193704@gyor.oxdrove.co.uk> <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> Message-ID: <49226691.1040706@opencsw.org> Philip Brown wrote: > On Mon, Nov 17, 2008 at 08:26:25PM +0100, Trygve Laugst?l wrote: >> Philip Brown wrote: >>> I think that in this case, we should toss out what sun does, and start with >>> our own CONSISTENT naming, that can stay consistent pretty much from now >>> until forever :-) >>> >>> (JAVA_HOME=/opt/csw/java/{pick-your-version}, where version can >>> also be "default") >> I'm all for consistency and my point was really "just because sun does >> it". By not inventing *yet* another way to find the Java runtime we're >> saving some brain cells. > > ok... I think you're saying that you're ok with the above "consistent" > strategy, so I think I am counting 3 "votes" in favour of the above, and > none opposed so far. I would vote +1 for /opt/csw/jdk and /opt/csw/jdk, because that is nearer to what Sun does, but I won't try to veto a hiearchy with more consistency under /opt/csw/java :) >> /opt/csw is already a >> pretty decent mess if you ask mere. Stuff is no where near self >> consistent or similar to /etc, either Solaris or other distros. > > I do agree that in certain areas, our packages are inconsistent. and I > think that we should all be 'encouraged',and encourage one another, to > clean things up. > > I for one, will be "cleaning up" my very old and ugly apache1 package, to > finally adhere to the proper standards, of > "writable stuff belongs in /var/opt/csw/pkgname, NOT /opt/csw/var" > and so on. > > > But that will take a large amount of work, so it's waiting for next weekend > :-/ Great! How about configuration files? Are they going under /etc/opt/csw to? -- Trygve From trygvel at opencsw.org Tue Nov 18 08:01:07 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Tue, 18 Nov 2008 08:01:07 +0100 Subject: [csw-maintainers] Experimental Atom Feed for testing/ In-Reply-To: References: Message-ID: <49226833.8030606@opencsw.org> Dagobert Michelsen wrote: > Fellow maintainers, > > tonight I hacked a rudimentary atom feed for testing/. Woho! > Please subscribe to > The feed work just fine in my Atom reader (Bloglines.com) and in Opera. Not sure why you put feed:// instead of http:// in the link, Atom feeds tent to be transported over HTTP. > Maybe someone has a link for me on how to integrate this to > the testing.html webpage. For the HTML integration you can follow nearly any blog, but [1] one had lots of examples in it's tags: So I think if you put this in it should work: billion. Yet at the end of September, Sun had $3.1 billion in cash on > hand. The gap indicates extreme pessimism about the company's > prospects." Did Sun know this in advance? Without the 1:4 join, the price of a share would be < 1 $ J?rg -- EMail:joerg at schily.isdn.cs.tu-berlin.de (home) J?rg Schilling D-13353 Berlin js at cs.tu-berlin.de (uni) schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily From phil at bolthole.com Tue Nov 18 15:50:14 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 18 Nov 2008 06:50:14 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <49226691.1040706@opencsw.org>; from trygvel@opencsw.org on Tue, Nov 18, 2008 at 07:54:09AM +0100 References: <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> <49226691.1040706@opencsw.org> Message-ID: <20081118065014.B46481@bolthole.com> On Tue, Nov 18, 2008 at 07:54:09AM +0100, Trygve Laugst?l wrote: > > I for one, will be "cleaning up" my very old and ugly apache1 package, to > > finally adhere to the proper standards, of > > "writable stuff belongs in /var/opt/csw/pkgname, NOT /opt/csw/var" > > and so on. > > > > > > But that will take a large amount of work, so it's waiting for next weekend > > :-/ > > Great! > > How about configuration files? Are they going under /etc/opt/csw to? Yeah. and so on, and so forth. hence the "a lot of work" :-/ From trygvel at opencsw.org Tue Nov 18 22:36:39 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Tue, 18 Nov 2008 22:36:39 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081118065014.B46481@bolthole.com> References: <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> <49226691.1040706@opencsw.org> <20081118065014.B46481@bolthole.com> Message-ID: <49233567.7030101@opencsw.org> Philip Brown wrote: > On Tue, Nov 18, 2008 at 07:54:09AM +0100, Trygve Laugst?l wrote: >>> I for one, will be "cleaning up" my very old and ugly apache1 package, to >>> finally adhere to the proper standards, of >>> "writable stuff belongs in /var/opt/csw/pkgname, NOT /opt/csw/var" >>> and so on. >>> >>> >>> But that will take a large amount of work, so it's waiting for next weekend >>> :-/ >> Great! >> >> How about configuration files? Are they going under /etc/opt/csw to? > > Yeah. and so on, and so forth. hence the "a lot of work" :-/ :) Is that something that is a part of the standards and something that your script is checking for? -- Trygve From phil at bolthole.com Tue Nov 18 23:42:16 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 18 Nov 2008 14:42:16 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <49233567.7030101@opencsw.org>; from trygvel@opencsw.org on Tue, Nov 18, 2008 at 10:36:39PM +0100 References: <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> <49226691.1040706@opencsw.org> <20081118065014.B46481@bolthole.com> <49233567.7030101@opencsw.org> Message-ID: <20081118144216.A72261@bolthole.com> On Tue, Nov 18, 2008 at 10:36:39PM +0100, Trygve Laugst?l wrote: > > Is that something that is a part of the standards and something that > your script is checking for? yes it is part of the standards. No, it isnt something you can really progamatically check for. From trygvel at opencsw.org Wed Nov 19 01:29:39 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Wed, 19 Nov 2008 01:29:39 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081118144216.A72261@bolthole.com> References: <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> <49226691.1040706@opencsw.org> <20081118065014.B46481@bolthole.com> <49233567.7030101@opencsw.org> <20081118144216.A72261@bolthole.com> Message-ID: <49235DF3.3020601@opencsw.org> Philip Brown wrote: > On Tue, Nov 18, 2008 at 10:36:39PM +0100, Trygve Laugst?l wrote: >> Is that something that is a part of the standards and something that >> your script is checking for? > > yes it is part of the standards. No, it isnt something you can really > progamatically check for. I was just wondering, since just about every CSW package that I've installed has config files under /opt/csw/etc. Wouldn't it be possible to just check the prototype for files under /opt/csw/etc? -- Trygve From phil at bolthole.com Wed Nov 19 02:31:01 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 18 Nov 2008 17:31:01 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <49235DF3.3020601@opencsw.org>; from trygvel@opencsw.org on Wed, Nov 19, 2008 at 01:29:39AM +0100 References: <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> <49226691.1040706@opencsw.org> <20081118065014.B46481@bolthole.com> <49233567.7030101@opencsw.org> <20081118144216.A72261@bolthole.com> <49235DF3.3020601@opencsw.org> Message-ID: <20081118173101.A14182@bolthole.com> On Wed, Nov 19, 2008 at 01:29:39AM +0100, Trygve Laugst?l wrote: > > yes it is part of the standards. No, it isnt something you can really > > progamatically check for. > > I was just wondering, since just about every CSW package that I've > installed has config files under /opt/csw/etc. > > Wouldn't it be possible to just check the prototype for files under > /opt/csw/etc? well, i actually plan to put in a check for /opt/csw/var. since that should pretty much never exist any more. However, /opt/csw/etc is different. Some programs, SHOULD have global configs in /opt/csw/etc. Some should have local configs in /etc/opt/csw It is impossible for an automated check to "know" which type of program it is checking :-} From jgoerzen at opencsw.org Wed Nov 19 07:16:57 2008 From: jgoerzen at opencsw.org (Jake Goerzen) Date: Tue, 18 Nov 2008 22:16:57 -0800 Subject: [csw-maintainers] now in /testing: freeciv 2.1.6 Message-ID: <315c02ae0811182216w11ca1004r92f7b0f43d207c3d@mail.gmail.com> updated packages of freeciv version 2.1.6 are available in /testing http://buildfarm.opencsw.org/testing/freeciv-2.1.6,REV=2008.11.19-SunOS5.8-i386-CSW.pkg.gz http://buildfarm.opencsw.org/testing/freeciv-2.1.6,REV=2008.11.19-SunOS5.8-sparc-CSW.pkg.gz -------------- next part -------------- An HTML attachment was scrubbed... URL: From bonivart at opencsw.org Wed Nov 19 22:12:17 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Wed, 19 Nov 2008 22:12:17 +0100 Subject: [csw-maintainers] /testing - BIND 9.4.2-P2, MailScanner 4.71, SpamAssassin 3.2.5, TNEF 1.4.5 Message-ID: <625385e30811191312j6f385203mb1d3ea95d72f1c38@mail.gmail.com> I have a few updated packages in testing and would like some help if possible. Bind is a small update from the very important one this summer but it could still be very interesting since the security fix is now a more permanent one that should consume less resources. Many of us noticed that Bind used more resources to do the same job so it will be interesting to see if that is now better again. http://mirror.opencsw.org/testing/bind-9.4.2,REV=2008.11.19_rev=P2-SunOS5.8-i386-CSW.pkg.gz http://mirror.opencsw.org/testing/bind-9.4.2,REV=2008.11.19_rev=P2-SunOS5.8-sparc-CSW.pkg.gz The second one is MailScanner, 4.72 has just been released but only supports ClamAV 0.94 which we don't yet have here so I'm going to release 4.71 instead and keep working on ClamAV. I have included SMF support in the package now. http://mirror.opencsw.org/testing/mailscanner-4.71.10.1,REV=2008.11.18-SunOS5.8-all-CSW.pkg.gz This one may interest many of you. I took over the package from Alex Moore and didn't find much documentation but I have tried to package it exactly as he did so not to cause any problems. The only intended change is that "local state dir" (where sa-update downloads rules) is changed from /opt/csw/var to /var/opt/csw/spamassassin. http://mirror.opencsw.org/testing/spamassassin-3.2.5,REV=2008.11.19-SunOS5.8-i386-CSW.pkg.gz http://mirror.opencsw.org/testing/spamassassin-3.2.5,REV=2008.11.19-SunOS5.8-sparc-CSW.pkg.gz Last one is a small utility to decode Microsoft's intrusion into the mail world. They couldn't use HTML to format mail like everyone else but had to invent their own format and happily sends it over the internet even though only Outlook (Lookout?) can parse it. When you get a winmail.dat file you know you have been TNEF:ed. :-) This utility can decode that file and is used by e.g. MailScanner to automatically replace TNEF in a transparent fashion. http://mirror.opencsw.org/testing/tnef-1.4.5,REV=2008.11.18-SunOS5.8-i386-CSW.pkg.gz http://mirror.opencsw.org/testing/tnef-1.4.5,REV=2008.11.18-SunOS5.8-sparc-CSW.pkg.gz -- /peter From jgoerzen at opencsw.org Thu Nov 20 02:29:59 2008 From: jgoerzen at opencsw.org (Jake Goerzen) Date: Wed, 19 Nov 2008 17:29:59 -0800 Subject: [csw-maintainers] updated freeciv 2.1.6 pkgs in /testing Message-ID: <315c02ae0811191729p11a7b9bfw7c5bef8501b84b19@mail.gmail.com> I have built new freeciv 2.1.6 packages and placed them in /testing: http://buildfarm.opencsw.org/testing/freeciv-2.1.6,REV=2008.11.20-SunOS5.8-i386-CSW.pkg.gz http://buildfarm.opencsw.org/testing/freeciv-2.1.6,REV=2008.11.20-SunOS5.8-sparc-CSW.pkg.gz I don't have any x86 host to test the x86 pkg but the sparc pkg works great. Please someone test the x86 pkg and let me know. Thanks, Jake -------------- next part -------------- An HTML attachment was scrubbed... URL: From fred at opencsw.org Thu Nov 20 12:52:24 2008 From: fred at opencsw.org (Frederic Van De Velde) Date: Thu, 20 Nov 2008 12:52:24 +0100 Subject: [csw-maintainers] where is testing ? Message-ID: How do I put files in buildfarm.opencsw.org/testing ? Fred. From bonivart at opencsw.org Thu Nov 20 13:35:10 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Thu, 20 Nov 2008 13:35:10 +0100 Subject: [csw-maintainers] where is testing ? In-Reply-To: References: Message-ID: <625385e30811200435l3916ca1cr37224515e32538a7@mail.gmail.com> On Thu, Nov 20, 2008 at 12:52 PM, Frederic Van De Velde wrote: > > How do I put files in buildfarm.opencsw.org/testing ? Copy them to /home/testing. -- /peter From dam at opencsw.org Thu Nov 20 13:36:26 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 20 Nov 2008 13:36:26 +0100 Subject: [csw-maintainers] where is testing ? In-Reply-To: References: Message-ID: <40266351-3F85-438D-B569-FDA4C07C95C6@opencsw.org> Hi Frederic, Am 20.11.2008 um 12:52 schrieb Frederic Van De Velde: > How do I put files in buildfarm.opencsw.org/testing ? You copy them to /home/testing/ :-) Don't get yourself distracted by not seeing it as it is wildcard-automounted. Best regards -- Dago From william at wbonnet.net Thu Nov 20 13:53:52 2008 From: william at wbonnet.net (William Bonnet) Date: Thu, 20 Nov 2008 13:53:52 +0100 Subject: [csw-maintainers] where is testing ? In-Reply-To: <40266351-3F85-438D-B569-FDA4C07C95C6@opencsw.org> References: <40266351-3F85-438D-B569-FDA4C07C95C6@opencsw.org> Message-ID: <49255DE0.3010401@wbonnet.net> Dagobert Michelsen a ?crit : > Hi Frederic, > > Am 20.11.2008 um 12:52 schrieb Frederic Van De Velde: > >> How do I put files in buildfarm.opencsw.org/testing ? >> > > You copy them to /home/testing/ :-) Don't get yourself > distracted by not seeing it as it is wildcard-automounted. > > And where is newpkgs ? :) I haven't checked, but are these information availables from the website ? cheers W. From bonivart at opencsw.org Thu Nov 20 14:09:12 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Thu, 20 Nov 2008 14:09:12 +0100 Subject: [csw-maintainers] where is testing ? In-Reply-To: <49255DE0.3010401@wbonnet.net> References: <40266351-3F85-438D-B569-FDA4C07C95C6@opencsw.org> <49255DE0.3010401@wbonnet.net> Message-ID: <625385e30811200509w5b60b270r36a447e1a2aee58b@mail.gmail.com> On Thu, Nov 20, 2008 at 1:53 PM, William Bonnet wrote: > And where is newpkgs ? :) > > I haven't checked, but are these information availables from the website ? Scp your packages to www.opencsw.org:/home/newpkgs. http://www.opencsw.org/standards/pkg-walkthrough "When you're satisfied that the package is worthy of public release, copy your finished packages to /home/newpkgs on www.opencsw.org and let Phil know they are ready. (remove them from /testing at this time, if they are there)" -- /peter From dam at opencsw.org Thu Nov 20 14:09:43 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 20 Nov 2008 14:09:43 +0100 Subject: [csw-maintainers] where is testing ? In-Reply-To: <49255DE0.3010401@wbonnet.net> References: <40266351-3F85-438D-B569-FDA4C07C95C6@opencsw.org> <49255DE0.3010401@wbonnet.net> Message-ID: Hi William, Am 20.11.2008 um 13:53 schrieb William Bonnet: > Dagobert Michelsen a ?crit : >> Am 20.11.2008 um 12:52 schrieb Frederic Van De Velde: >>> How do I put files in buildfarm.opencsw.org/testing ? >> >> You copy them to /home/testing/ :-) Don't get yourself >> distracted by not seeing it as it is wildcard-automounted. >> > > And where is newpkgs ? :) > > I haven't checked, but are these information availables from the > website ? Yes, but somewhat hidden: When you're satisfied that the package is worthy of public release, copy your finished packages to /home/newpkgs on www.opencsw.org and let Phil know they are ready. (remove them from /testing at this time, if they are there) I guess it would be good to have a wiki page which summarizes all the info needed for a new maintainer, written by a new maintainer. Volunteers? Best regards -- Dago From bonivart at opencsw.org Thu Nov 20 14:12:59 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Thu, 20 Nov 2008 14:12:59 +0100 Subject: [csw-maintainers] where is testing ? In-Reply-To: References: <40266351-3F85-438D-B569-FDA4C07C95C6@opencsw.org> <49255DE0.3010401@wbonnet.net> Message-ID: <625385e30811200512l331744efkee5c2ac40ad12427@mail.gmail.com> On Thu, Nov 20, 2008 at 2:09 PM, Dagobert Michelsen wrote: > I guess it would be good to have a wiki page which summarizes all the > info needed for a new maintainer, written by a new maintainer. > Volunteers? Yes, a simple page documenting the steps involved without going into detail, it could instead link to the official documentation (which is a mess). -- /peter From phil at bolthole.com Thu Nov 20 18:28:44 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 20 Nov 2008 09:28:44 -0800 Subject: [csw-maintainers] where is testing ? In-Reply-To: ; from dam@opencsw.org on Thu, Nov 20, 2008 at 02:09:43PM +0100 References: <40266351-3F85-438D-B569-FDA4C07C95C6@opencsw.org> <49255DE0.3010401@wbonnet.net> Message-ID: <20081120092844.C23285@bolthole.com> On Thu, Nov 20, 2008 at 02:09:43PM +0100, Dagobert Michelsen wrote: > > I haven't checked, but are these information availables from the > > website ? > > Yes, but somewhat hidden: > > "When you're satisfied that the package is worthy of public release, copy > your finished packages to /home/newpkgs on www.opencsw.org and let > Phil know...." It is ALSO mentioned on the TOP level page. http://www.opencsw.org/standards/ near the bottom, in the "pkg file creation" section From dam at opencsw.org Fri Nov 21 10:26:41 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 21 Nov 2008 10:26:41 +0100 Subject: [csw-maintainers] Upgrade of build8x today! Message-ID: <019753DE-449D-414D-BB68-E519E7AD5144@opencsw.org> Hi, the server build8x will be changed to new hardware from 867 MHz, 384 MB to 2400 MHz, 512 MB Not great, but better. For this there will be a downtime within the next 8 hours where the old host gets synced over and the new server will be put in place. I'll keep you informed. Best regards -- Dago From bonivart at opencsw.org Fri Nov 21 11:20:54 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Fri, 21 Nov 2008 11:20:54 +0100 Subject: [csw-maintainers] Anyone want to update libxml2? Message-ID: <625385e30811210220t3fa1d4fbvc919abe90b069f41@mail.gmail.com> The libxml2 package we have is both outdated and broken (build machine paths in it). Would any one be interested in updating it? I don't think Ken Mays will. http://www.opencsw.org/packages/libxml2 The source link is not updated any more, go to ftp://xmlsoft.org/libxml2/ instead. -- /peter From dam at opencsw.org Fri Nov 21 12:24:32 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 21 Nov 2008 12:24:32 +0100 Subject: [csw-maintainers] Anyone want to update libxml2? In-Reply-To: <625385e30811210220t3fa1d4fbvc919abe90b069f41@mail.gmail.com> References: <625385e30811210220t3fa1d4fbvc919abe90b069f41@mail.gmail.com> Message-ID: <5FB12541-2DA5-4FF7-BC53-D06B8EABD1DE@opencsw.org> Hi Peter, Am 21.11.2008 um 11:20 schrieb Peter Bonivart: > The libxml2 package we have is both outdated and broken (build machine > paths in it). Would any one be interested in updating it? I don't > think Ken Mays will. > > http://www.opencsw.org/packages/libxml2 > > The source link is not updated any more, go to > ftp://xmlsoft.org/libxml2/ instead. I did libxml2 as example for multi-isa-builds. The repackage already runs and 2.6.30 will hopefully be ready this evening. BTW: Anyone want to update python and make a 64 bit version? Best regards -- Dago From dam at opencsw.org Fri Nov 21 13:21:12 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 21 Nov 2008 13:21:12 +0100 Subject: [csw-maintainers] build8x is now down Message-ID: <9AD4CC7E-6DE2-4D79-98E5-23A88EABBDF5@opencsw.org> Hi, the server build8x will now be down. Please standby... -- Dago From phil at bolthole.com Fri Nov 21 15:34:19 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 21 Nov 2008 06:34:19 -0800 Subject: [csw-maintainers] Upgrade of build8x today! In-Reply-To: <019753DE-449D-414D-BB68-E519E7AD5144@opencsw.org>; from dam@opencsw.org on Fri, Nov 21, 2008 at 10:26:41AM +0100 References: <019753DE-449D-414D-BB68-E519E7AD5144@opencsw.org> Message-ID: <20081121063419.B35332@bolthole.com> On Fri, Nov 21, 2008 at 10:26:41AM +0100, Dagobert Michelsen wrote: > Hi, > > the server build8x will be changed to new hardware from > 867 MHz, 384 MB > to > 2400 MHz, 512 MB > Not great, but better. wow.. well, I'd call it great! :-) From phil at bolthole.com Fri Nov 21 15:38:45 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 21 Nov 2008 06:38:45 -0800 Subject: [csw-maintainers] 64-bit python In-Reply-To: <5FB12541-2DA5-4FF7-BC53-D06B8EABD1DE@opencsw.org>; from dam@opencsw.org on Fri, Nov 21, 2008 at 12:24:32PM +0100 References: <625385e30811210220t3fa1d4fbvc919abe90b069f41@mail.gmail.com> <5FB12541-2DA5-4FF7-BC53-D06B8EABD1DE@opencsw.org> Message-ID: <20081121063845.C35332@bolthole.com> On Fri, Nov 21, 2008 at 12:24:32PM +0100, Dagobert Michelsen wrote: > > BTW: Anyone want to update python and make a 64 bit version? > yikes. Do you know if "compiled" python will run equally well with the 64bit runtime, as from the regular 32bit one? I'm guessing not. if not, then this might be a good reason to deviate from our usual practice of "ship 64bit with 32bit package", and make a separate "python64" package. From dam at opencsw.org Fri Nov 21 15:44:57 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 21 Nov 2008 15:44:57 +0100 Subject: [csw-maintainers] build8x is up again In-Reply-To: <9AD4CC7E-6DE2-4D79-98E5-23A88EABBDF5@opencsw.org> References: <9AD4CC7E-6DE2-4D79-98E5-23A88EABBDF5@opencsw.org> Message-ID: <23ADFDC4-D6F4-43AF-820C-3A71F278CD8A@opencsw.org> Hi, Am 21.11.2008 um 13:21 schrieb Dagobert Michelsen: > the server build8x will now be down. The server build8x is now migrated to a new machine and can be used again. Please let me know if you encounter something unusual. Best regards -- Dago From dam at opencsw.org Fri Nov 21 16:42:51 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 21 Nov 2008 16:42:51 +0100 Subject: [csw-maintainers] libxml2 2.7.2 available In-Reply-To: <625385e30811210220t3fa1d4fbvc919abe90b069f41@mail.gmail.com> References: <625385e30811210220t3fa1d4fbvc919abe90b069f41@mail.gmail.com> Message-ID: <572D2121-9990-4497-A70D-2C58D83A45BC@opencsw.org> Hi Peter, Am 21.11.2008 um 11:20 schrieb Peter Bonivart: > The libxml2 package we have is both outdated and broken (build machine > paths in it). Would any one be interested in updating it? I don't > think Ken Mays will. > > http://www.opencsw.org/packages/libxml2 > > The source link is not updated any more, go to > ftp://xmlsoft.org/libxml2/ instead. libxml2 and related packages have been updated and are ready for testing/: libxml2-2.7.2,REV=2008.11.21-SunOS5.8-i386-CSW.pkg.gz libxml2-2.7.2,REV=2008.11.21-SunOS5.8-sparc-CSW.pkg.gz libxml2_devel-2.7.2,REV=2008.11.21-SunOS5.8-i386-CSW.pkg.gz libxml2_devel-2.7.2,REV=2008.11.21-SunOS5.8-sparc-CSW.pkg.gz pylibxml2-2.7.2,REV=2008.11.21-SunOS5.8-sparc-CSW.pkg.gz pylibxml2-2.7.2,REV=2008.11.21-SunOS5.8-i386-CSW.pkg.gz Feedback as always welcome! Best regards -- Dago From dam at opencsw.org Fri Nov 21 17:46:25 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 21 Nov 2008 17:46:25 +0100 Subject: [csw-maintainers] mGAR will arrive soon Message-ID: Hi, as you may have noticed I have begun transforming GAR to the new mGAR (=modularized GAR) structure. This will allow - building for multiple ISAs easily (like 32 and 64 bit) - building packages with legacy libraries easily (several versions in one package) - continous integration with Hudson - easier transition between major GAR updates as this can be done on a per-package basis. - dynamic prototypes to automatically split a software in multiple packages by rules - later "source packages" At some time in the near future the current trunk will be deleted and from that point on work should be done against the new mgar-tree. Feel free to work on trunk/ until then, the changes should be easily mergable. I'll write up some docs which explain how the old and new versions differ. Best regards -- Dago From bwalton at opencsw.org Fri Nov 21 18:09:28 2008 From: bwalton at opencsw.org (Ben Walton) Date: Fri, 21 Nov 2008 12:09:28 -0500 Subject: [csw-maintainers] git? Message-ID: <1227287196-sup-2976@ntdws12.chass.utoronto.ca> Hi All, I notice that there is a GAR build description for git, but there doesn't seem to be a released package for it. Is anyone working on this? If not, I'd be willing to give it a crack. I think my group will be standardizing on git in the near future, so having it for our solaris boxes in addition to our linux machines would be very helpful. -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 Nov 22 17:06:28 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 22 Nov 2008 17:06:28 +0100 Subject: [csw-maintainers] git? In-Reply-To: <1227287196-sup-2976@ntdws12.chass.utoronto.ca> References: <1227287196-sup-2976@ntdws12.chass.utoronto.ca> Message-ID: <875C8A1F-F3F6-4D57-AEC7-1D1DFB3F04F7@opencsw.org> Hi Ben, Am 21.11.2008 um 18:09 schrieb Ben Walton: > I notice that there is a GAR build description for git, but there > doesn't seem to be a released package for it. Is anyone working on > this? If not, I'd be willing to give it a crack. I did a start at trunk/devel/git. However, you need asciidoc for that. I packaged 8.2.5 some time ago but the package seems to have gotten lost during the split. I'll repackage 8.2.7 ASAP and keep you informed. If I recall correctly there were dependencies on XML catalogs which I was unable to fix. Anyway, feel free to take it over. > I think my group > will be standardizing on git in the near future, so having it for our > solaris boxes in addition to our linux machines would be very helpful. Best maintainers are the ones who actually use their packages :-) Best regards -- Dago From bwalton at opencsw.org Sat Nov 22 17:29:20 2008 From: bwalton at opencsw.org (Ben Walton) Date: Sat, 22 Nov 2008 11:29:20 -0500 Subject: [csw-maintainers] git? In-Reply-To: <875C8A1F-F3F6-4D57-AEC7-1D1DFB3F04F7@opencsw.org> References: <1227287196-sup-2976@ntdws12.chass.utoronto.ca> <875C8A1F-F3F6-4D57-AEC7-1D1DFB3F04F7@opencsw.org> Message-ID: <1227370964-sup-8443@ntdws12.chass.utoronto.ca> Excerpts from Dagobert Michelsen's message of Sat Nov 22 11:06:28 -0500 2008: > I did a start at trunk/devel/git. However, you need asciidoc for > that. I packaged 8.2.5 some time ago but the package seems to > have gotten lost during the split. I'll repackage 8.2.7 ASAP > and keep you informed. I started on this package yesterday too. I installed it locally to build git, but figured a package is better so that the GAR description was not dependent on my 'special' PATH. I'm almost done writing a configure.ac and Makefile.in for it (which I'll kick upstream) so that building the package is doable. > If I recall correctly there were dependencies on XML catalogs > which I was unable to fix. I believe that the git folks did some workaround so that the 8.x series could be used to build the docs for git. This was the source of my proxy question yesterday too. The git build currently stops because one of the xml/xslt tools can't pull down a file from sourceforge to validate the xml domain. > Anyway, feel free to take it over. Sure, I can do that. Maybe I'll have better luck with this than with ruby! :) [I've kicked a report up to ruby-core at ruby-lang, but haven't gotten any nibbles yet. I did discover that solaris 8 is, at best, minimally supported only because it's a POSIX environment...] > Best maintainers are the ones who actually use their packages :-) Eating ones own dogfood is always a good thing. Have a good weekend. -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 dam at opencsw.org Sat Nov 22 23:34:50 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 22 Nov 2008 23:34:50 +0100 Subject: [csw-maintainers] git? In-Reply-To: <1227370964-sup-8443@ntdws12.chass.utoronto.ca> References: <1227287196-sup-2976@ntdws12.chass.utoronto.ca> <875C8A1F-F3F6-4D57-AEC7-1D1DFB3F04F7@opencsw.org> <1227370964-sup-8443@ntdws12.chass.utoronto.ca> Message-ID: <7987A90D-9749-4F3C-9933-31C688A44915@opencsw.org> Hi Ben, Am 22.11.2008 um 17:29 schrieb Ben Walton: > Excerpts from Dagobert Michelsen's message of Sat Nov 22 11:06:28 > -0500 2008: > >> I did a start at trunk/devel/git. However, you need asciidoc for >> that. I packaged 8.2.5 some time ago but the package seems to >> have gotten lost during the split. I'll repackage 8.2.7 ASAP >> and keep you informed. > > I started on this package yesterday too. I installed it locally to > build git, but figured a package is better so that the GAR > description was not dependent on my 'special' PATH. I'm almost done > writing a configure.ac and Makefile.in for it (which I'll kick > upstream) so that building the package is doable. Very good! Feel free to take over asciidoc too. >> If I recall correctly there were dependencies on XML catalogs >> which I was unable to fix. > > I believe that the git folks did some workaround so that the 8.x > series could be used to build the docs for git. This was the source > of my proxy question yesterday too. The git build currently stops > because one of the xml/xslt tools can't pull down a file from > sourceforge to validate the xml domain. Yes, and I couldn't get it to validate even with internet access. Best regards -- Dago From dam at opencsw.org Sun Nov 23 21:49:46 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 23 Nov 2008 21:49:46 +0100 Subject: [csw-maintainers] Merry christmas! Message-ID: <55BD3712-DF63-45FD-8FF2-2974AF1FD505@opencsw.org> Fellow maintainers! I know it is not christmas yet, but I am happy to announce a new Sparc machine for package building. The current machine is a SF280R with 1 x 750 MHz, 2 GB Ram and 7 x 250 GB SCSI-IDE The new machine is a T5220, 4 x 1.2 GHz Cores (32 Strands), 8 GB Ram, 8 x 146 GB SAS It will be available for Solaris 10 Sparc package building, Solaris 8 Sparc package building (via Solaris 8 Branded Zones), Hudson Continous Integration and LDAP. For the transition I will need to temporarily disable some functions on the current machine as services will move over to the new machine one at a time. I will announce downtimes when needed. ...and theres more good news: There will be temporarily an additional x86 machine available. It is a X4440 with 4 x AMD 8356 2.3 GHz (16 cores total), 16 GB Ram for Solaris 10 x86 package building. I'll announce when it is ready to use. So, when you're idling along now is the time to start some big packages like qt4 or gcc. Best regards -- Dago From dam at opencsw.org Sun Nov 23 22:57:10 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 23 Nov 2008 22:57:10 +0100 Subject: [csw-maintainers] 64-bit python In-Reply-To: <20081121063845.C35332@bolthole.com> References: <625385e30811210220t3fa1d4fbvc919abe90b069f41@mail.gmail.com> <5FB12541-2DA5-4FF7-BC53-D06B8EABD1DE@opencsw.org> <20081121063845.C35332@bolthole.com> Message-ID: <00576986-F170-40A9-B3D6-0D27AB001CE1@opencsw.org> HI PHIL, Am 21.11.2008 um 15:38 schrieb Philip Brown: > On Fri, Nov 21, 2008 at 12:24:32PM +0100, Dagobert Michelsen wrote: >> >> BTW: Anyone want to update python and make a 64 bit version? > > yikes. > > Do you know if "compiled" python will run equally well with the 64bit > runtime, as from the regular 32bit one? > I'm guessing not. > > if not, then this might be a good reason to deviate from our usual > practice > of "ship 64bit with 32bit package", and make a separate "python64" > package. This goes equally well for Perl. And the binary packages must then be build for 32/64 bit Perl also :-P And for Perl with ithreads :-P== Best regards -- Dago From william at wbonnet.net Sun Nov 23 23:10:40 2008 From: william at wbonnet.net (William Bonnet) Date: Sun, 23 Nov 2008 23:10:40 +0100 Subject: [csw-maintainers] where is testing ? In-Reply-To: References: <40266351-3F85-438D-B569-FDA4C07C95C6@opencsw.org> <49255DE0.3010401@wbonnet.net> Message-ID: <4929D4E0.4060500@wbonnet.net> Hi > When you're satisfied that the package is worthy of public release, copy > > your finished packages to /home/newpkgs on www.opencsw.org and let > Phil know > > Could you please check that i have write access to this place ? or maybe i am not using the good scp argument ? scp firefox-2.0.0.18,REV\=2008.11.14-SunOS5.8-* www.opencsw.org:/home/newpkgs ssh: Could not resolve hostname www.opencsw.org: host/servname not known scp firefox-2.0.0.18,REV\=2008.11.14-SunOS5.8-* www:/home/newpkgs ssh: Could not resolve hostname www: host/servname not known 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 Sun Nov 23 23:16:25 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 23 Nov 2008 23:16:25 +0100 Subject: [csw-maintainers] where is testing ? In-Reply-To: <4929D4E0.4060500@wbonnet.net> References: <40266351-3F85-438D-B569-FDA4C07C95C6@opencsw.org> <49255DE0.3010401@wbonnet.net> <4929D4E0.4060500@wbonnet.net> Message-ID: Hi William, Am 23.11.2008 um 23:10 schrieb William Bonnet: >> When you're satisfied that the package is worthy of public release, >> copy >> >> your finished packages to /home/newpkgs on www.opencsw.org and let >> Phil know >> >> > Could you please check that i have write access to this place ? or > maybe > i am not using the good scp argument ? > > scp firefox-2.0.0.18,REV\=2008.11.14-SunOS5.8-* > www.opencsw.org:/home/newpkgs > ssh: Could not resolve hostname www.opencsw.org: host/servname not > known > > scp firefox-2.0.0.18,REV\=2008.11.14-SunOS5.8-* www:/home/newpkgs > ssh: Could not resolve hostname www: host/servname not known You must do this from 'login.bo.opencsw.org', the build-machines are not directly connected to the internet. Best regards -- Dago From william at wbonnet.net Sun Nov 23 23:22:51 2008 From: william at wbonnet.net (William Bonnet) Date: Sun, 23 Nov 2008 23:22:51 +0100 Subject: [csw-maintainers] where is testing ? In-Reply-To: References: <40266351-3F85-438D-B569-FDA4C07C95C6@opencsw.org> <49255DE0.3010401@wbonnet.net> <4929D4E0.4060500@wbonnet.net> Message-ID: <4929D7BB.8030309@wbonnet.net> Hi > You must do this from 'login.bo.opencsw.org', the build-machines > are not directly connected to the internet. > I forgot that... :) It's now prompting me for a password. Would it be possible to setup my ssh key ? because it seems that if one day i had this password, then i also forgot it. 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 phil at bolthole.com Mon Nov 24 02:41:28 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 23 Nov 2008 17:41:28 -0800 Subject: [csw-maintainers] 64-bit python In-Reply-To: <00576986-F170-40A9-B3D6-0D27AB001CE1@opencsw.org>; from dam@opencsw.org on Sun, Nov 23, 2008 at 10:57:10PM +0100 References: <625385e30811210220t3fa1d4fbvc919abe90b069f41@mail.gmail.com> <5FB12541-2DA5-4FF7-BC53-D06B8EABD1DE@opencsw.org> <20081121063845.C35332@bolthole.com> <00576986-F170-40A9-B3D6-0D27AB001CE1@opencsw.org> Message-ID: <20081123174128.B76485@bolthole.com> On Sun, Nov 23, 2008 at 10:57:10PM +0100, Dagobert Michelsen wrote: > HI PHIL, :-D > > Am 21.11.2008 um 15:38 schrieb Philip Brown: > > if not, then this might be a good reason to deviate from our usual > > practice of "ship 64bit with 32bit package", and make a separate > > "python64" package. > > This goes equally well for Perl. *gag* *choke*... 64bit perl??? as if perl wasnt bloated enough?!!! :-} Actually, i'm not exactly sure why someone would want 64bit python either. could someone enlighten us? From buysse at cla.umn.edu Mon Nov 24 03:21:32 2008 From: buysse at cla.umn.edu (Joshua Buysse) Date: Sun, 23 Nov 2008 20:21:32 -0600 Subject: [csw-maintainers] 64-bit python In-Reply-To: <20081123174128.B76485@bolthole.com> References: <625385e30811210220t3fa1d4fbvc919abe90b069f41@mail.gmail.com> <5FB12541-2DA5-4FF7-BC53-D06B8EABD1DE@opencsw.org> <20081121063845.C35332@bolthole.com> <00576986-F170-40A9-B3D6-0D27AB001CE1@opencsw.org> <20081123174128.B76485@bolthole.com> Message-ID: >> Am 21.11.2008 um 15:38 schrieb Philip Brown: >>> if not, then this might be a good reason to deviate from our usual >>> practice of "ship 64bit with 32bit package", and make a separate >>> "python64" package. >> >> This goes equally well for Perl. > > *gag* *choke*... 64bit perl??? as if perl wasnt bloated enough?!!! :-} > > Actually, i'm not exactly sure why someone would want 64bit python > either. > could someone enlighten us? Sadly, I had to build a 64-bit python internally a while back. Researchers using bioinformatics toolkits (for purposes other than what was intended, but cool idea). The code was written in Python, using FEBRL (http://datamining.anu.edu.au/projects/linkage.html). They were linking individual census records between different years, and the datafiles are in the tens or hundreds of gigs. Damn thing needed to load the entire set into memory, and even using MPI, it was a beast. Researchers do use scripting languages with huge data sets, especially in the biosciences. -- Joshua Buysse, System Engineer University of Minnesota, College of Liberal Arts "When fascism comes to America, it will be wrapped in an American flag and carrying a cross." -- Sinclair Lewis -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL: From ihsan at opencsw.org Mon Nov 24 09:07:11 2008 From: ihsan at opencsw.org (Ihsan Dogan) Date: Mon, 24 Nov 2008 09:07:11 +0100 Subject: [csw-maintainers] where is testing ? In-Reply-To: <4929D7BB.8030309@wbonnet.net> References: <40266351-3F85-438D-B569-FDA4C07C95C6@opencsw.org> <49255DE0.3010401@wbonnet.net> <4929D4E0.4060500@wbonnet.net> <4929D7BB.8030309@wbonnet.net> Message-ID: <492A60AF.1080706@opencsw.org> Good morning, Am 23.11.2008 23:22 Uhr, William Bonnet schrieb: >> You must do this from 'login.bo.opencsw.org', the build-machines >> are not directly connected to the internet. >> > I forgot that... :) > > It's now prompting me for a password. Would it be possible to setup my > ssh key ? because it seems that if one day i had this password, then i > also forgot it. I copied your public key from the build machines now. Can you please try again? Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/ From william at wbonnet.net Mon Nov 24 13:26:55 2008 From: william at wbonnet.net (William Bonnet) Date: Mon, 24 Nov 2008 13:26:55 +0100 Subject: [csw-maintainers] where is testing ? In-Reply-To: <492A60AF.1080706@opencsw.org> References: <40266351-3F85-438D-B569-FDA4C07C95C6@opencsw.org> <49255DE0.3010401@wbonnet.net> <4929D4E0.4060500@wbonnet.net> <4929D7BB.8030309@wbonnet.net> <492A60AF.1080706@opencsw.org> Message-ID: <492A9D8F.7040204@wbonnet.net> Ihsan Dogan a ?crit : > Good morning, > > Am 23.11.2008 23:22 Uhr, William Bonnet schrieb: > > >>> You must do this from 'login.bo.opencsw.org', the build-machines >>> are not directly connected to the internet. >>> >>> >> I forgot that... :) >> >> It's now prompting me for a password. Would it be possible to setup my >> ssh key ? because it seems that if one day i had this password, then i >> also forgot it. >> > > I copied your public key from the build machines now. Can you please try > again? > It works. Thanks Firfox 2.0.0.18 has been pushed to unstable and removed from testing. cheers From dam at opencsw.org Mon Nov 24 14:11:26 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 24 Nov 2008 14:11:26 +0100 Subject: [csw-maintainers] 64-bit python In-Reply-To: <20081123174128.B76485@bolthole.com> References: <625385e30811210220t3fa1d4fbvc919abe90b069f41@mail.gmail.com> <5FB12541-2DA5-4FF7-BC53-D06B8EABD1DE@opencsw.org> <20081121063845.C35332@bolthole.com> <00576986-F170-40A9-B3D6-0D27AB001CE1@opencsw.org> <20081123174128.B76485@bolthole.com> Message-ID: <9903E2B3-DB76-4DE7-B86C-A9E5F85C827F@opencsw.org> Hi Phil, Am 24.11.2008 um 02:41 schrieb Philip Brown: >> Am 21.11.2008 um 15:38 schrieb Philip Brown: >>> if not, then this might be a good reason to deviate from our usual >>> practice of "ship 64bit with 32bit package", and make a separate >>> "python64" package. >> >> This goes equally well for Perl. > > *gag* *choke*... 64bit perl??? as if perl wasnt bloated enough?!!! :-} > > Actually, i'm not exactly sure why someone would want 64bit python > either. > could someone enlighten us? Features of 64 bit Perl: - >256 filedescriptors - >2GB Ram I needed both of them for an OpenLDAP Perl backend. Building a full 64 bit chain is not that hard and would give us some extra merits ==*:-) Best regards -- Dago From dam at opencsw.org Mon Nov 24 14:57:26 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 24 Nov 2008 14:57:26 +0100 Subject: [csw-maintainers] 64-bit python In-Reply-To: References: <625385e30811210220t3fa1d4fbvc919abe90b069f41@mail.gmail.com> <5FB12541-2DA5-4FF7-BC53-D06B8EABD1DE@opencsw.org> <20081121063845.C35332@bolthole.com> <00576986-F170-40A9-B3D6-0D27AB001CE1@opencsw.org> <20081123174128.B76485@bolthole.com> Message-ID: <5670D8CE-A3D8-495E-8B4F-61DA35ED2F21@opencsw.org> Hi Joshua, Am 24.11.2008 um 03:21 schrieb Joshua Buysse: >>> Am 21.11.2008 um 15:38 schrieb Philip Brown: >>>> if not, then this might be a good reason to deviate from our usual >>>> practice of "ship 64bit with 32bit package", and make a separate >>>> "python64" package. >>> >>> This goes equally well for Perl. >> >> *gag* *choke*... 64bit perl??? as if perl wasnt bloated >> enough?!!! :-} >> >> Actually, i'm not exactly sure why someone would want 64bit python >> either. >> could someone enlighten us? > > Sadly, I had to build a 64-bit python internally a while back. > Researchers using bioinformatics toolkits (for purposes other than > what was intended, but cool idea). The code was written in Python, > using FEBRL (http://datamining.anu.edu.au/projects/linkage.html). > They were linking individual census records between different years, > and the datafiles are in the tens or hundreds of gigs. Damn thing > needed to load the entire set into memory, and even using MPI, it > was a beast. > > Researchers do use scripting languages with huge data sets, > especially in the biosciences. IIRC Python is currently orphaned. As you seem to be quite qualified: do you like to take over Python and make a 64 bit version? I guess we will need some discussion on how to handle this in general for Python/Perl/OpenLDAP. Best regards -- Dago From bwalton at opencsw.org Mon Nov 24 17:52:12 2008 From: bwalton at opencsw.org (Ben Walton) Date: Mon, 24 Nov 2008 11:52:12 -0500 Subject: [csw-maintainers] asciidoc in testing/ Message-ID: <1227545407-sup-9703@ntdws12.chass.utoronto.ca> Hi All, If you're looking for YADGTg (yet another documentation generation tool ), you can give asciidoc a try. It's in testing/ now. I've installed it locally and it seems generally ok at this point (I've run a bunch of the git documentation through it so far). Comments are welcome. 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 Nov 24 20:49:44 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Mon, 24 Nov 2008 20:49:44 +0100 Subject: [csw-maintainers] Popularity statistics Message-ID: <492B0558.7050605@opencsw.org> Hi I was wondering if there are any download statistics available for the packages? -- Trygve From bonivart at opencsw.org Mon Nov 24 20:58:21 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Mon, 24 Nov 2008 20:58:21 +0100 Subject: [csw-maintainers] Popularity statistics In-Reply-To: <492B0558.7050605@opencsw.org> References: <492B0558.7050605@opencsw.org> Message-ID: <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com> On Mon, Nov 24, 2008 at 8:49 PM, Trygve Laugst?l wrote: > Hi > > I was wondering if there are any download statistics available for the > packages? That would be interesting, even just from a single mirror. We could also see which arch and release is most popular. Does any of the mirrors offer such service or let us fix it ourselves? -- /peter From phil at bolthole.com Mon Nov 24 21:05:35 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 24 Nov 2008 12:05:35 -0800 Subject: [csw-maintainers] Popularity statistics In-Reply-To: <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com>; from bonivart@opencsw.org on Mon, Nov 24, 2008 at 08:58:21PM +0100 References: <492B0558.7050605@opencsw.org> <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com> Message-ID: <20081124120535.O25010@bolthole.com> On Mon, Nov 24, 2008 at 08:58:21PM +0100, Peter Bonivart wrote: > On Mon, Nov 24, 2008 at 8:49 PM, Trygve Laugst?l wrote: > > Hi > > > > I was wondering if there are any download statistics available for the > > packages? > > That would be interesting, even just from a single mirror. > > We could also see which arch and release is most popular. > > Does any of the mirrors offer such service or let us fix it ourselves? ibiblio Stats were published previously on the maintainers list based on ibiblio stats. From trygvel at opencsw.org Mon Nov 24 21:09:37 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Mon, 24 Nov 2008 21:09:37 +0100 Subject: [csw-maintainers] Popularity statistics In-Reply-To: <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com> References: <492B0558.7050605@opencsw.org> <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com> Message-ID: <492B0A01.6070501@opencsw.org> Peter Bonivart wrote: > On Mon, Nov 24, 2008 at 8:49 PM, Trygve Laugst?l wrote: >> Hi >> >> I was wondering if there are any download statistics available for the >> packages? > > That would be interesting, even just from a single mirror. Yeah, that should be sufficient to show the distribution. > We could also see which arch and release is most popular. My idea was to use the data to prioritize our work for those who want to contribute to the project as a "whole" and help out with getting packages for the most popular packages. -- Trygve From william at wbonnet.net Mon Nov 24 21:10:33 2008 From: william at wbonnet.net (William Bonnet) Date: Mon, 24 Nov 2008 21:10:33 +0100 Subject: [csw-maintainers] Popularity statistics In-Reply-To: <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com> References: <492B0558.7050605@opencsw.org> <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com> Message-ID: <492B0A39.9060501@wbonnet.net> Hi > Does any of the mirrors offer such service or let us fix it ourselves? > It would certainly be easy to install something like awstats and parse mirror logs ? It's added to my todo list. -- 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 william at wbonnet.net Mon Nov 24 21:10:39 2008 From: william at wbonnet.net (William Bonnet) Date: Mon, 24 Nov 2008 21:10:39 +0100 Subject: [csw-maintainers] Popularity statistics In-Reply-To: <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com> References: <492B0558.7050605@opencsw.org> <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com> Message-ID: <492B0A3F.40708@wbonnet.net> Hi > Does any of the mirrors offer such service or let us fix it ourselves? > It would certainly be easy to install something like awstats and parse mirror logs ? It's added to my todo list. 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 phil at bolthole.com Mon Nov 24 21:27:59 2008 From: phil at bolthole.com (Philip Brown) Date: Mon, 24 Nov 2008 12:27:59 -0800 Subject: [csw-maintainers] Popularity statistics In-Reply-To: <492B0A01.6070501@opencsw.org>; from trygvel@opencsw.org on Mon, Nov 24, 2008 at 09:09:37PM +0100 References: <492B0558.7050605@opencsw.org> <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com> <492B0A01.6070501@opencsw.org> Message-ID: <20081124122759.Q25010@bolthole.com> On Mon, Nov 24, 2008 at 09:09:37PM +0100, Trygve Laugst?l wrote: > > My idea was to use the data to prioritize our work for those who want to > contribute to the project as a "whole" and help out with getting > packages for the most popular packages. In some ways, seems like that is non-productive at the start. Wouldnt the "most popular packages" naturally get the most help anyway? Contrariwise, the ones that "need the most help", might be the ones that no-one uses, becuase they are too out of date for people to use any more. I think Dagobert's buglist would probably be the most targetted way to identify "packages that need the most help.". And then there's stuff like samba. sigh. I made a gigantic test package a while back, and put it in testing. but have had zero feedback. Since I dont use samba myself, I really need SOMEONE to give me feedback about it before I put more work into splitting it up n stuff. (or, someone else is very welcome to take it over and I'll give them what notes I have) From bonivart at opencsw.org Mon Nov 24 21:45:27 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Mon, 24 Nov 2008 21:45:27 +0100 Subject: [csw-maintainers] Popularity statistics In-Reply-To: <20081124122759.Q25010@bolthole.com> References: <492B0558.7050605@opencsw.org> <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com> <492B0A01.6070501@opencsw.org> <20081124122759.Q25010@bolthole.com> Message-ID: <625385e30811241245i7cbf0d00j19d05b68e5bf93fc@mail.gmail.com> On Mon, Nov 24, 2008 at 9:27 PM, Philip Brown wrote: > I think Dagobert's buglist would probably be the most targetted way to > identify "packages that need the most help.". Another simple thing would be to use James' package list to find the oldest packages (with his Last Changed field). A quick review of those might find us a lot of packages that need updates but are orphaned. -- /peter From dam at opencsw.org Mon Nov 24 22:54:13 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 24 Nov 2008 22:54:13 +0100 Subject: [csw-maintainers] Popularity statistics In-Reply-To: <20081124122759.Q25010@bolthole.com> References: <492B0558.7050605@opencsw.org> <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com> <492B0A01.6070501@opencsw.org> <20081124122759.Q25010@bolthole.com> Message-ID: <26525A94-F51C-498B-8A6B-A0662945D58A@opencsw.org> Hi, Am 24.11.2008 um 21:27 schrieb Philip Brown: > I think Dagobert's buglist would probably be the most targetted way to > identify "packages that need the most help.". If someone has some spare cycles: there is another buglist sorted by number of reported bugs without maintainer distinction: Feel free to take over any orphaned or sabbatical packages if you have spare cycles. Best regards -- Dago From trygvel at opencsw.org Tue Nov 25 00:31:00 2008 From: trygvel at opencsw.org (=?UTF-8?B?VHJ5Z3ZlIExhdWdzdMO4bA==?=) Date: Tue, 25 Nov 2008 00:31:00 +0100 Subject: [csw-maintainers] asciidoc in testing/ In-Reply-To: <1227545407-sup-9703@ntdws12.chass.utoronto.ca> References: <1227545407-sup-9703@ntdws12.chass.utoronto.ca> Message-ID: <492B3934.6090909@opencsw.org> Ben Walton wrote: > Hi All, > > If you're looking for YADGTg (yet another documentation generation tool > ), you can give asciidoc a try. It's in testing/ now. I've > installed it locally and it seems generally ok at this point (I've run > a bunch of the git documentation through it so far). Is it not in GAR yet? I was using your package as a test package for Hudson [1] but it failed because it is still trying to download 8.2.5 instead of .7 that you've built. [1]: http://buildfarm.opencsw.org/hudson/job/asciidoc-solaris-8-sparc [2]: http://buildfarm.opencsw.org/hudson/job/asciidoc-solaris-8-sparc/2/console -- Trygve From bwalton at opencsw.org Tue Nov 25 14:41:54 2008 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 25 Nov 2008 08:41:54 -0500 Subject: [csw-maintainers] asciidoc in testing/ In-Reply-To: <492B3934.6090909@opencsw.org> References: <1227545407-sup-9703@ntdws12.chass.utoronto.ca> <492B3934.6090909@opencsw.org> Message-ID: <1227620493-sup-7116@ntdws12.chass.utoronto.ca> Excerpts from Trygve Laugst?l's message of Mon Nov 24 18:31:00 -0500 2008: > Is it not in GAR yet? I was using your package as a test package for > Hudson [1] but it failed because it is still trying to download 8.2.5 > instead of .7 that you've built. It should be checked into GAR...commits 2349 and 2350. -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 dam at opencsw.org Tue Nov 25 15:20:31 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 25 Nov 2008 15:20:31 +0100 Subject: [csw-maintainers] Server build8s will be unavailable for upgrade Message-ID: Hi, I will take build8s down in the next hour for snapshotting and migration to the T5220. A notification will be send when the server is up again. Sorry for the inconvenience -- Dago From bwalton at artsci.utoronto.ca Tue Nov 25 15:42:09 2008 From: bwalton at artsci.utoronto.ca (Ben Walton) Date: Tue, 25 Nov 2008 09:42:09 -0500 Subject: [csw-maintainers] asciidoc in testing/ In-Reply-To: <492B3934.6090909@opencsw.org> References: <1227545407-sup-9703@ntdws12.chass.utoronto.ca> <492B3934.6090909@opencsw.org> Message-ID: <1227623972-sup-2920@ntdws12.chass.utoronto.ca> Excerpts from Trygve Laugst?l's message of Mon Nov 24 18:31:00 -0500 2008: Hi Trygve, > Is it not in GAR yet? I was using your package as a test package for > Hudson [1] but it failed because it is still trying to download 8.2.5 > instead of .7 that you've built. You likely pointed Hudson at apps/asciidoc. I rolled my asciidoc from utils/asciidoc, as I'd created that workspace before seeing Dago's old apps/ version. I just checked in the svn rm of apps/asciidoc...hadn't planned to do that until my version was accepted and hadn't planned on anyone else looking at it!. Sorry for the confusion. -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 bwalton at opencsw.org Tue Nov 25 15:50:31 2008 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 25 Nov 2008 09:50:31 -0500 Subject: [csw-maintainers] asciidoc in testing/ In-Reply-To: <492B3934.6090909@opencsw.org> References: <1227545407-sup-9703@ntdws12.chass.utoronto.ca> <492B3934.6090909@opencsw.org> Message-ID: <1227624553-sup-361@ntdws12.chass.utoronto.ca> Excerpts from Trygve Laugst?l's message of Mon Nov 24 18:31:00 -0500 2008: Hi Trygve, > Is it not in GAR yet? I was using your package as a test package for > Hudson [1] but it failed because it is still trying to download 8.2.5 > instead of .7 that you've built. You likely pointed Hudson at apps/asciidoc. I rolled my asciidoc from utils/asciidoc, as I'd created that workspace before seeing Dago's old apps/ version. I just checked in the svn rm of apps/asciidoc...hadn't planned to do that until my version accepted and hadn't planned on anyone else looking at it!. Sorry for the confusion. 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. From dam at opencsw.org Tue Nov 25 16:52:34 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 25 Nov 2008 16:52:34 +0100 Subject: [csw-maintainers] Server build8s is available again In-Reply-To: References: Message-ID: <4EAB5D17-FEB9-4A5E-80E1-7CCB38D9CBA4@opencsw.org> Hi, Am 25.11.2008 um 15:20 schrieb Dagobert Michelsen: > I will take build8s down in the next hour for snapshotting > and migration to the T5220. A notification will be send when > the server is up again. The server build8s is up and running again. Feel free to continue your packaging work. Best regards -- Dago From dam at opencsw.org Tue Nov 25 17:31:21 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 25 Nov 2008 17:31:21 +0100 Subject: [csw-maintainers] build10s will be migrated today Message-ID: Hi, I will also migrate build10s today to the new machine. The server will be shut down in a couple of minutes. I'll post when it is ready again. Best regards -- Dago From dam at opencsw.org Tue Nov 25 18:28:09 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 25 Nov 2008 18:28:09 +0100 Subject: [csw-maintainers] build10s will be migrated today In-Reply-To: References: Message-ID: <16EA62EF-567F-4D2D-83F0-CC2EEE9A515D@opencsw.org> Hi, Am 25.11.2008 um 17:31 schrieb Dagobert Michelsen: > I will also migrate build10s today to the new machine. > The server will be shut down in a couple of minutes. I'll post > when it is ready again. The server build10s is available again. Happy packaging -- Dago From debertin at opencsw.org Tue Nov 25 20:29:07 2008 From: debertin at opencsw.org (debertin at opencsw.org) Date: Tue, 25 Nov 2008 13:29:07 -0600 Subject: [csw-maintainers] Forcing use of GNU binutils Message-ID: <18732.20995.799922.766973@autumn.msi.umn.edu> I know, use of GNU binutils on Solaris is usually not recommended, but I'm building a LISP compiler that produces assembly that only GNU "as" can parse, so there is no way around it. I've been using a locally-built GCC out of my homedir that I compiled with --with-as= and --with-gnu-as, but if there is a runtime GCC flag that does the same thing then it will make my job a lot easier. Thanks -- -Dan -- Dan Debertin Unix Systems Administrator Minnesota Supercomputing Institute University of Minnesota 541 Walter 117 Pleasant Street SE Minneapolis, MN 55455 debertin at msi.umn.edu 612.626.8926 From phil at bolthole.com Tue Nov 25 20:36:45 2008 From: phil at bolthole.com (Philip Brown) Date: Tue, 25 Nov 2008 11:36:45 -0800 Subject: [csw-maintainers] Forcing use of GNU binutils In-Reply-To: <18732.20995.799922.766973@autumn.msi.umn.edu>; from debertin@opencsw.org on Tue, Nov 25, 2008 at 01:29:07PM -0600 References: <18732.20995.799922.766973@autumn.msi.umn.edu> Message-ID: <20081125113645.U25010@bolthole.com> On Tue, Nov 25, 2008 at 01:29:07PM -0600, debertin at opencsw.org wrote: > I know, use of GNU binutils on Solaris is usually not recommended, but > I'm building a LISP compiler that produces assembly that only GNU "as" > can parse, so there is no way around it. > > I've been using a locally-built GCC out of my homedir that I compiled > with --with-as= and --with-gnu-as, but if there is a runtime GCC flag > that does the same thing then it will make my job a lot easier. there is also the option, in some more sanely suported source code, to explicitly define an assembler. you might look for that option also. From james at opencsw.org Tue Nov 25 20:58:08 2008 From: james at opencsw.org (James Lee) Date: Tue, 25 Nov 2008 19:58:08 GMT Subject: [csw-maintainers] Merry christmas! In-Reply-To: <55BD3712-DF63-45FD-8FF2-2974AF1FD505@opencsw.org> References: <55BD3712-DF63-45FD-8FF2-2974AF1FD505@opencsw.org> Message-ID: <20081125.19580800.154957751@gyor.oxdrove.co.uk> On 23/11/08, 20:49:46, Dagobert Michelsen wrote regarding [csw-maintainers] Merry christmas!: > I know it is not christmas yet, but I am happy to announce > a new Sparc machine for package building. May we ask, have Santa's Elves fashioned this from moss and reindeer antler or do we have someone else to thank? James. From james at opencsw.org Tue Nov 25 20:58:09 2008 From: james at opencsw.org (James Lee) Date: Tue, 25 Nov 2008 19:58:09 GMT Subject: [csw-maintainers] Server build8s is available again In-Reply-To: <4EAB5D17-FEB9-4A5E-80E1-7CCB38D9CBA4@opencsw.org> References: <4EAB5D17-FEB9-4A5E-80E1-7CCB38D9CBA4@opencsw.org> Message-ID: <20081125.19580900.1221328234@gyor.oxdrove.co.uk> On 25/11/08, 15:52:34, Dagobert Michelsen wrote regarding Re: [csw-maintainers] Server build8s is available again: > > and migration to the T5220. A notification will be send when > > the server is up again. > The server build8s is up and running again. Feel free > to continue your packaging work. gmake[3]: warning: Clock skew detected. Your build may be incomplete. ... gmake[3]: Warning: File `Makefile' has modification time 1.9e+02 s in the future ... It would be rude not do do a timing test, so I did a test build of GraphicsMagick-1.3.1: pandora V240 2 x 1500MHz US3i: real 7:09.891 user 0.033 sys 0.070 build8s T5220 32 x 1165MHz UltraSPARC T2: real 11:41.853 user 39:13.994 sys 7:57.193 "gmake -j 32" should test the robustness of the Makefiles although it appeared not to use that many jobs. A lot of build time is spent (needlessly) running ./configure in one-at-a-time mode - do I really need to discover if f77 takes -g? James. From dam at opencsw.org Wed Nov 26 12:57:03 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 26 Nov 2008 12:57:03 +0100 Subject: [csw-maintainers] asciidoc in testing/ In-Reply-To: <1227545407-sup-9703@ntdws12.chass.utoronto.ca> References: <1227545407-sup-9703@ntdws12.chass.utoronto.ca> Message-ID: <028F5059-6A2F-4621-BE5A-C3BF71E4E369@opencsw.org> Hi Ben, Am 24.11.2008 um 17:52 schrieb Ben Walton: > If you're looking for YADGTg (yet another documentation generation > tool > ), you can give asciidoc a try. It's in testing/ now. I've > installed it locally and it seems generally ok at this point (I've run > a bunch of the git documentation through it so far). The file in testing/ had 640 permissions. Please make sure that the files are 644 as the catalog builder cannot read it otherwise. I fixed that for now. Best regards -- Dago From dam at opencsw.org Wed Nov 26 13:09:25 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 26 Nov 2008 13:09:25 +0100 Subject: [csw-maintainers] Merry christmas! In-Reply-To: <20081125.19580800.154957751@gyor.oxdrove.co.uk> References: <55BD3712-DF63-45FD-8FF2-2974AF1FD505@opencsw.org> <20081125.19580800.154957751@gyor.oxdrove.co.uk> Message-ID: <7B6DD977-049F-4E02-9B9D-9E2F67F5CA1B@opencsw.org> Hi James, Am 25.11.2008 um 20:58 schrieb James Lee: > On 23/11/08, 20:49:46, Dagobert Michelsen wrote > regarding > [csw-maintainers] Merry christmas!: > >> I know it is not christmas yet, but I am happy to announce >> a new Sparc machine for package building. > > May we ask, have Santa's Elves fashioned this from moss and > reindeer antler or do we have someone else to thank? The machine was previously used for testing LDOMs in our lab. As we also have a T1000 these tests can also be done on that machine. So, thank my colleagues and my boss. Best regards -- Dago From dam at opencsw.org Wed Nov 26 13:11:31 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 26 Nov 2008 13:11:31 +0100 Subject: [csw-maintainers] Server build8s is available again In-Reply-To: <20081125.19580900.1221328234@gyor.oxdrove.co.uk> References: <4EAB5D17-FEB9-4A5E-80E1-7CCB38D9CBA4@opencsw.org> <20081125.19580900.1221328234@gyor.oxdrove.co.uk> Message-ID: <62A953D6-B7E1-487D-B4D9-4F66BF73A470@opencsw.org> Hi James, Am 25.11.2008 um 20:58 schrieb James Lee: > gmake[3]: warning: Clock skew detected. Your build may be > incomplete. > ... > gmake[3]: Warning: File `Makefile' has modification time 1.9e+02 s > in the > future > ... There was a glitch in the network configuration which prevented xntpd from synchronizing. Should be fixed now. > It would be rude not do do a timing test, so I did a test build of > GraphicsMagick-1.3.1: > > pandora V240 2 x 1500MHz US3i: > > real 7:09.891 > user 0.033 > sys 0.070 > > > build8s T5220 32 x 1165MHz UltraSPARC T2: > > real 11:41.853 > user 39:13.994 > sys 7:57.193 > > > > "gmake -j 32" should test the robustness of the Makefiles although it > appeared not to use that many jobs. A lot of build time is spent > (needlessly) running ./configure in one-at-a-time mode - do I really > need to discover if f77 takes -g? I presume you did the build tests from your homedir? That is still NFS-mounted from the 750 MHz 280R at BO. Please retest after that has been migrated also. Thanks for testing! -- Dago From bwalton at opencsw.org Wed Nov 26 15:13:44 2008 From: bwalton at opencsw.org (Ben Walton) Date: Wed, 26 Nov 2008 09:13:44 -0500 Subject: [csw-maintainers] mktemp on build farm Message-ID: <1227708770-sup-3685@ntdws12.chass.utoronto.ca> Hi Dago, Could you pop mktemp onto the BO machines? 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 Nov 26 15:33:05 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 26 Nov 2008 15:33:05 +0100 Subject: [csw-maintainers] mktemp on build farm In-Reply-To: <1227708770-sup-3685@ntdws12.chass.utoronto.ca> References: <1227708770-sup-3685@ntdws12.chass.utoronto.ca> Message-ID: <2CFB3D50-9805-4B6E-872F-E1AB9D74D94A@opencsw.org> Hi Ben, Am 26.11.2008 um 15:13 schrieb Ben Walton: > Could you pop mktemp onto the BO machines? Done. Best regards -- Dago From dam at opencsw.org Wed Nov 26 16:05:46 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 26 Nov 2008 16:05:46 +0100 Subject: [csw-maintainers] IMPORTANT: Transition to mGAR Message-ID: <890EF0AE-E169-4A84-90C0-DF7A2A74CEAD@opencsw.org> Hi, the transition to mGAR is almost finished. The documentation is linked from Please read it. I have already merged commits after r2333 to mGAR. The directories csw/trunk csw/tags csw/branches/dam csw/branches/joyent csw/branches/modularpkg csw/branches/yann will be deleted as experimental GAR implementations can now be done on a per-package basis. The deletion will occur at the end of the week. Please make sure to migrate all your modified checkouts to mGAR by then. (For maintainers not yet familiar with Subversion: a deletions means it is no longer visible. By using the revision number it will always be possible to get everything back, even if it is deleted in the current revision). Best regards -- Dago From fred at opencsw.org Thu Nov 27 11:48:55 2008 From: fred at opencsw.org (Frederic Van De Velde) Date: Thu, 27 Nov 2008 11:48:55 +0100 Subject: [csw-maintainers] IMPORTANT: Transition to mGAR In-Reply-To: <890EF0AE-E169-4A84-90C0-DF7A2A74CEAD@opencsw.org> References: <890EF0AE-E169-4A84-90C0-DF7A2A74CEAD@opencsw.org> Message-ID: <689E05BB-57B7-488D-BEBD-9BF942FE94EE@opencsw.org> Hi, Very good work. I'm trying to add one package to the cpan tree. I followed the procedure on the wiki ( the one with partial repository checkout) but can't manage to do it. Let's take a concrete example, I have a directory /home/fred/mgar where I downloaded some existing packages into their subdirectories with this command: svn co https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/cpan/My-Perl-Module I have then: /home/fred/mgar/My-Perl-Module/[trunk/branches/tags] Now I want to add a new perl module, what's the procedure ? Regards, Frederic. On 26 Nov 2008, at 16:05, Dagobert Michelsen wrote: > Hi, > > the transition to mGAR is almost finished. The documentation > is linked from > title=Main_Page> > Please read it. > > I have already merged commits after r2333 to mGAR. > > The directories > csw/trunk > csw/tags > csw/branches/dam > csw/branches/joyent > csw/branches/modularpkg > csw/branches/yann > will be deleted as experimental GAR implementations can now be done > on a per-package basis. The deletion will occur at the end of the > week. Please make sure to migrate all your modified checkouts > to mGAR by then. (For maintainers not yet familiar with Subversion: > a deletions means it is no longer visible. By using the revision > number > it will always be possible to get everything back, even if it is > deleted > in the current revision). > > > Best regards > > -- Dago > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers From dam at opencsw.org Thu Nov 27 13:20:03 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 27 Nov 2008 13:20:03 +0100 Subject: [csw-maintainers] BO Buildfarm will be down due to migration Message-ID: <57E10DB6-126E-4AEC-A222-B2C809D79EBB@opencsw.org> Hi, today I will migrate the remaining parts "login", NFS and Web to the T5220. The machine will be unavailable during this time. I'll post when the migration is finished. Best regards -- Dago From dam at opencsw.org Thu Nov 27 22:28:12 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 27 Nov 2008 22:28:12 +0100 Subject: [csw-maintainers] BO Buildfarm will be down due to migration In-Reply-To: <57E10DB6-126E-4AEC-A222-B2C809D79EBB@opencsw.org> References: <57E10DB6-126E-4AEC-A222-B2C809D79EBB@opencsw.org> Message-ID: <1530472E-819B-4A7A-8301-363B1F1768F8@opencsw.org> Hi, Am 27.11.2008 um 13:20 schrieb Dagobert Michelsen: > today I will migrate the remaining parts "login", NFS and Web > to the T5220. The machine will be unavailable during this time. > I'll post when the migration is finished. Everything has been migrated to the new machine and should work as before. Unfortunately build8x has an issue with the boot archive which I can not fix from home (where I am right now) as it is an old PC without remote console. This will be fixed tomorrow. Please let me know if you encounter anything else suspicious. James: Please repeat your benchmark, and the clock should now be running in sync too. Best regards -- Dago From dam at opencsw.org Thu Nov 27 23:52:46 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 27 Nov 2008 23:52:46 +0100 Subject: [csw-maintainers] IMPORTANT: Transition to mGAR In-Reply-To: <689E05BB-57B7-488D-BEBD-9BF942FE94EE@opencsw.org> References: <890EF0AE-E169-4A84-90C0-DF7A2A74CEAD@opencsw.org> <689E05BB-57B7-488D-BEBD-9BF942FE94EE@opencsw.org> Message-ID: <6B8A88C1-94E1-4D85-84CF-AE124E80CFB0@opencsw.org> Hi Frederic,, Am 27.11.2008 um 11:48 schrieb Frederic Van De Velde: > Very good work. > > I'm trying to add one package to the cpan tree. > I followed the procedure on the wiki ( the one with partial repository > checkout) but can't manage to do it. I guess the docs were a bit misleading. Now I put all in the Makefile in pkg/, should be easier. The docs have been updated accordingly. > Let's take a concrete example, I have a directory /home/fred/mgar > where I downloaded some existing packages into their subdirectories > with this command: > > svn co https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/cpan/My-Perl-Module > > I have then: /home/fred/mgar/My-Perl-Module/[trunk/branches/tags] > > Now I want to add a new perl module, what's the procedure ? Try this: ? svn -N co https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/cpan ? cd cpan ? gmake newpkg-My-New-Module ? cd My-New-Module/trunk ? Edit the Makefile etc. ? svn add for everything valuable in your package ? cd ../.. ? svn -m "cpan/My-New-Module: Initial commit" commit Feedback as always welcome. Best regards -- Dago From phil at bolthole.com Fri Nov 28 00:11:45 2008 From: phil at bolthole.com (Philip Brown) Date: Thu, 27 Nov 2008 15:11:45 -0800 Subject: [csw-maintainers] IMPORTANT: Transition to mGAR In-Reply-To: <6B8A88C1-94E1-4D85-84CF-AE124E80CFB0@opencsw.org> References: <890EF0AE-E169-4A84-90C0-DF7A2A74CEAD@opencsw.org> <689E05BB-57B7-488D-BEBD-9BF942FE94EE@opencsw.org> <6B8A88C1-94E1-4D85-84CF-AE124E80CFB0@opencsw.org> Message-ID: <20081127231145.GA80469@bolthole.com> On Thu, Nov 27, 2008 at 11:52:46PM +0100, Dagobert Michelsen wrote: > >... > > Now I want to add a new perl module, what's the procedure ? > > > Try this: > > ? svn -N co https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/cpan > ? cd cpan > ? gmake newpkg-My-New-Module > ? cd My-New-Module/trunk > ? Edit the Makefile etc. > ? svn add for everything valuable in your package > ? cd ../.. > ? svn -m "cpan/My-New-Module: Initial commit" commit > > Feedback as always welcome. It might be nice, if it were possible to make some kind of set of wrappers. something along the lines of $ [makenewproj] (which pulls down a bunch of templates) (or contrariwise, [getmyproj], which pulls down the relevant stuff) $ [savemystuffs] Having to manually do a bunch of svn stuff, seems like kind of a hassle. especialy with typing that longugly(tm) stuff to the svn repository. seems like that should be made transparent somehow. it's extremely ugly, to my eyes. From dam at opencsw.org Fri Nov 28 09:16:31 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 28 Nov 2008 09:16:31 +0100 Subject: [csw-maintainers] BO Buildfarm will be down due to migration In-Reply-To: <1530472E-819B-4A7A-8301-363B1F1768F8@opencsw.org> References: <57E10DB6-126E-4AEC-A222-B2C809D79EBB@opencsw.org> <1530472E-819B-4A7A-8301-363B1F1768F8@opencsw.org> Message-ID: <0E53C46C-2B39-4D4B-8ED4-F35ECB6EB767@opencsw.org> Hi, Am 27.11.2008 um 22:28 schrieb Dagobert Michelsen: > Everything has been migrated to the new machine and should work > as before. Unfortunately build8x has an issue with the boot archive > which I can not fix from home (where I am right now) as it is an old > PC without remote console. This will be fixed tomorrow. build8x is up and running again. The farm should be fully operational again. Please let me know if you encounter anything suspicious. Best regards -- Dago From dam at opencsw.org Fri Nov 28 11:03:37 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 28 Nov 2008 11:03:37 +0100 Subject: [csw-maintainers] IMPORTANT: Transition to mGAR In-Reply-To: <20081127231145.GA80469@bolthole.com> References: <890EF0AE-E169-4A84-90C0-DF7A2A74CEAD@opencsw.org> <689E05BB-57B7-488D-BEBD-9BF942FE94EE@opencsw.org> <6B8A88C1-94E1-4D85-84CF-AE124E80CFB0@opencsw.org> <20081127231145.GA80469@bolthole.com> Message-ID: <75929304-6B62-486F-80D8-25D5ED110717@opencsw.org> Hi Phil, Am 28.11.2008 um 00:11 schrieb Philip Brown: > On Thu, Nov 27, 2008 at 11:52:46PM +0100, Dagobert Michelsen wrote: >>> ... >>> Now I want to add a new perl module, what's the procedure ? >> >> >> Try this: >> >> ? svn -N co https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/cpan >> ? cd cpan >> ? gmake newpkg-My-New-Module >> ? cd My-New-Module/trunk >> ? Edit the Makefile etc. >> ? svn add for everything valuable in your package >> ? cd ../.. >> ? svn -m "cpan/My-New-Module: Initial commit" commit >> >> Feedback as always welcome. > > It might be nice, if it were possible to make some kind of set of > wrappers. > > something along the lines of > > $ [makenewproj] > (which pulls down a bunch of templates) > > (or contrariwise, [getmyproj], which pulls down the relevant > stuff) > > > $ [savemystuffs] > > > > Having to manually do a bunch of svn stuff, seems like kind of a > hassle. > especialy with typing that longugly(tm) stuff to the svn repository. > seems > like that should be made transparent somehow. it's extremely ugly, > to my > eyes. SVN does introduce some complexity, true. But I think it is not that hard. The problem is bootstrapping GAR checkout. Once you have GAR the complexity can be hidden in the Makefiles (which I did with newpkg-*). I don't know if a 3-line shellscript wrapping 'svn co', 'svn add' and 'svn commit' will really help here. At least I can't think of a solution that makes usage easier. Anybody more ideas? Maybe a GAR package that includes some bootstrapping stuff would help? Best regards -- Dago From fred at opencsw.org Fri Nov 28 12:01:55 2008 From: fred at opencsw.org (Frederic Van De Velde) Date: Fri, 28 Nov 2008 12:01:55 +0100 Subject: [csw-maintainers] IMPORTANT: Transition to mGAR In-Reply-To: <6B8A88C1-94E1-4D85-84CF-AE124E80CFB0@opencsw.org> References: <890EF0AE-E169-4A84-90C0-DF7A2A74CEAD@opencsw.org> <689E05BB-57B7-488D-BEBD-9BF942FE94EE@opencsw.org> <6B8A88C1-94E1-4D85-84CF-AE124E80CFB0@opencsw.org> Message-ID: <6248AE2C-7D97-44C5-8217-36465FF5CBE9@opencsw.org> > > Try this: > > ? svn -N co https://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/cpan > ? cd cpan > ? gmake newpkg-My-New-Module > ? cd My-New-Module/trunk > ? Edit the Makefile etc. > ? svn add for everything valuable in your package > ? cd ../.. > ? svn -m "cpan/My-New-Module: Initial commit" commit > > Feedback as always welcome. > Many thanks, it's a quite simple procedure now ... > Best regards > -- Dago > Fred. From dam at opencsw.org Fri Nov 28 12:12:06 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 28 Nov 2008 12:12:06 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <4922660D.9070203@opencsw.org> References: <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> <5F994B04-687B-4AC3-91AE-DAAE62F4716B@opencsw.org> <20081117172408.D39788@bolthole.com> <4922660D.9070203@opencsw.org> Message-ID: Hi! (sorry for the HTML mail, but otherwise the long lines are broken). Am 18.11.2008 um 07:51 schrieb Trygve Laugst?l: > I agree with Phil here, we need two packages. I would never use JDK or > JRE package that has been modified by upstream packages, just see the > just that Debian tries deliver with their "java" packages. I am currently looking into the JDK/JRE issue. The idea is to have a CSWjre6 package containing the JRE and a CSWjdk6 package, which depends on CSWjre6 and adds the JDK. So, the layout will look like this: /opt/csw/java/jdk/latest links to ../jdk6 (or jdk7 later) CSWjdk (depends on CSWjdk6) /opt/csw/java/jdk6 links to jdk1.6.0_07 (or _08 later) CSWjdk6 /opt/csw/java/jdk1.6.0_07 contains stuff from archive CSWjdk6 /opt/csw/java/jdk1.6.0_07/jre contains JRE inside JDK CSWjre6 /opt/csw/java/jre/latest links to ../jre6 CSWjre (depends on CSWjre6) /opt/csw/java/jre6 links to jre1.6.0_07 CSWjre6 /opt/csw/java/jre1.6.0_07 links to jdk1.6.0_07/jre CSWjre6 /opt/csw/java/man links to ../jdk/latest/man CSWjre /opt/csw/java/jre6/man links to ../../jdk6/man CSWjre I compared the JRE embedded in the JDK. The following files are only in jdk1.6.0_07/jre: lib/sparc/libsaproc.so lib/sparcv9/libsaproc.so lib/sparc/libattach.so lib/sparcv9/libattach.so What are these for? Just take the JRE from the JDK add them to the CSWjre6? When the permit from Sun arrives I'll give the package a final shot. Best regards -- Dago -------------- next part -------------- An HTML attachment was scrubbed... URL: From dam at opencsw.org Fri Nov 28 13:38:29 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 28 Nov 2008 13:38:29 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: References: <491F1820.6080608@opencsw.org> <4920023C.3030701@opencsw.org> <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> <5F994B04-687B-4AC3-91AE-DAAE62F4716B@opencsw.org> <20081117172408.D39788@bolthole.com> <4922660D.9070203@opencsw.org> Message-ID: <4CA4F900-6D7D-49AD-A072-7D15E7A90AB3@opencsw.org> Hi, sorry for the repost, now with corrected pathes. Please ignore previous posting. Best regards -- Dago Am 28.11.2008 um 12:12 schrieb Dagobert Michelsen: > Hi! > > (sorry for the HTML mail, but otherwise the long lines are broken). > > Am 18.11.2008 um 07:51 schrieb Trygve Laugst?l: >> I agree with Phil here, we need two packages. I would never use JDK >> or >> JRE package that has been modified by upstream packages, just see the >> just that Debian tries deliver with their "java" packages. > > I am currently looking into the JDK/JRE issue. The idea is > to have a CSWjre6 package containing the JRE and a CSWjdk6 > package, which depends on CSWjre6 and adds the JDK. > > So, the layout will look like this: > > /opt/csw/java/jdk/latest links to jdk6 (or jdk7 later) CSWjdk > (depends on CSWjdk6) > /opt/csw/java/jdk/jdk6 links to jdk1.6.0_07 (or _08 later) CSWjdk6 > /opt/csw/java/jdk/jdk1.6.0_07 contains stuff from archive CSWjdk6 > /opt/csw/java/jdk/jdk1.6.0_07/jre contains JRE inside JDK CSWjre6 >> > /opt/csw/java/jre/jdk1.6.0_07/jre/man links to ../man CSWjre6 > > /opt/csw/java/jre/latest links to jre6 CSWjre (depends on > CSWjre6) > /opt/csw/java/jre/jre6 links to jre1.6.0_07 CSWjre6 > /opt/csw/java/jre/jre1.6.0_07 links to jdk1.6.0_07/jre CSWjre6 >> > /opt/csw/java/man links to jdk/latest/man CSWjre > > I compared the JRE embedded in the JDK. The following files > are only in jdk1.6.0_07/jre: > > lib/sparc/libsaproc.so > lib/sparcv9/libsaproc.so > lib/sparc/libattach.so > lib/sparcv9/libattach.so > > What are these for? Just take the JRE from the JDK add them to the > CSWjre6? > > When the permit from Sun arrives I'll give the package > a final shot. > > > Best regards > > -- Dago > _______________________________________________ > maintainers mailing list > maintainers at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/maintainers -------------- next part -------------- An HTML attachment was scrubbed... URL: From phil at bolthole.com Fri Nov 28 15:34:15 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 28 Nov 2008 06:34:15 -0800 Subject: [csw-maintainers] Java... again! In-Reply-To: <4CA4F900-6D7D-49AD-A072-7D15E7A90AB3@opencsw.org> References: <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> <5F994B04-687B-4AC3-91AE-DAAE62F4716B@opencsw.org> <20081117172408.D39788@bolthole.com> <4922660D.9070203@opencsw.org> <4CA4F900-6D7D-49AD-A072-7D15E7A90AB3@opencsw.org> Message-ID: <20081128143415.GB22302@bolthole.com> Sounds good to me. Just one word of warning... On Fri, Nov 28, 2008 at 01:38:29PM +0100, Dagobert Michelsen wrote: > When the permit from Sun arrives I'll give the package > a final shot. we may be waiting for a very LOOOOONG time on that. even when sun is 100% favourable to doing something, getting legal approval for something seems to take a minimum of 3 months :-( From skayser at opencsw.org Fri Nov 28 15:37:28 2008 From: skayser at opencsw.org (Sebastian Kayser) Date: Fri, 28 Nov 2008 15:37:28 +0100 Subject: [csw-maintainers] First packaging efforts (synergy 1.3.1 in testing/). Feedback, someone? Message-ID: <49300228.20206@opencsw.org> Hi *, i just wrapped my first package :) (using the stagepkg/createpkg way) and put it in testing/. http://mirror.opencsw.org/testing/synergy-1.3.1,REV=2008.11.28-SunOS5.8-i386-CSW.pkg.gz http://mirror.opencsw.org/testing/synergy-1.3.1,REV=2008.11.28-SunOS5.8-sparc-CSW.pkg.gz Would be great if someone could give it a spin and have a look whether i missed anything. The only thing that struck me is the increased binary size compared to the version in current/. 1.2.2 from current/: root @ ray2 /opt/csw/bin# ls -l synergy* -rwxr-xr-x 1 root bin 580712 Jan 28 2005 synergyc -rwxr-xr-x 1 root bin 761456 Jan 28 2005 synergys 1.3.1 from testing/: root @ ray1 /opt/csw/bin# ls -l synergy* -rwxr-xr-x 1 root bin 1838776 Nov 28 14:47 synergyc -rwxr-xr-x 1 root bin 2542432 Nov 28 14:47 synergys >From what i see, the current/ package depends on CSWgcc3rt and its binaries are linked against libgcc_s.so.1. Does that mean they were compiled using gcc and that's where the size difference comes from? I did my builds with Sun Studio cc. Cheers Sebastian From phil at bolthole.com Fri Nov 28 15:38:20 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 28 Nov 2008 06:38:20 -0800 Subject: [csw-maintainers] IMPORTANT: Transition to mGAR In-Reply-To: <75929304-6B62-486F-80D8-25D5ED110717@opencsw.org> References: <890EF0AE-E169-4A84-90C0-DF7A2A74CEAD@opencsw.org> <689E05BB-57B7-488D-BEBD-9BF942FE94EE@opencsw.org> <6B8A88C1-94E1-4D85-84CF-AE124E80CFB0@opencsw.org> <20081127231145.GA80469@bolthole.com> <75929304-6B62-486F-80D8-25D5ED110717@opencsw.org> Message-ID: <20081128143820.GC22302@bolthole.com> On Fri, Nov 28, 2008 at 11:03:37AM +0100, Dagobert Michelsen wrote: > Hi Phil, > > Am 28.11.2008 um 00:11 schrieb Philip Brown: > > Having to manually do a bunch of svn stuff, seems like kind of a > > hassle. [....] > > SVN does introduce some complexity, true. But I think it is > not that hard. compiling many of our packages oneself is "not that hard" either. ./configure --prefix=/where/you/like make make install but for some reason, many people seem to appreciate being able to skip those "not hard" steps, into a simpler, single step ;-) having wrappers is a nice thing. From phil at bolthole.com Fri Nov 28 15:48:06 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 28 Nov 2008 06:48:06 -0800 Subject: [csw-maintainers] First packaging efforts (synergy 1.3.1 in testing/). Feedback, someone? In-Reply-To: <49300228.20206@opencsw.org> References: <49300228.20206@opencsw.org> Message-ID: <20081128144806.GD22302@bolthole.com> On Fri, Nov 28, 2008 at 03:37:28PM +0100, Sebastian Kayser wrote: > >From what i see, the current/ package depends on CSWgcc3rt and its > binaries are linked against libgcc_s.so.1. Does that mean they were > compiled using gcc and that's where the size difference comes from? I > did my builds with Sun Studio cc. Yup, most likely If you wanted to spend more time on it, you could recompile and tell sun cc to optimize for size more than speed. It tends to "unroll loops" if you highly optimize. And/Or reduce the optimize level to plain "-O", if you are using -fast, and compare that. Synergy is onlyl a virtual "KVM switch" after all. From skayser at opencsw.org Fri Nov 28 17:58:20 2008 From: skayser at opencsw.org (Sebastian Kayser) Date: Fri, 28 Nov 2008 17:58:20 +0100 Subject: [csw-maintainers] First packaging efforts (synergy 1.3.1 in testing/). Feedback, someone? In-Reply-To: <20081128144806.GD22302@bolthole.com> References: <49300228.20206@opencsw.org> <20081128144806.GD22302@bolthole.com> Message-ID: <4930232C.6050901@opencsw.org> Philip Brown wrote: > On Fri, Nov 28, 2008 at 03:37:28PM +0100, Sebastian Kayser wrote: >> >From what i see, the current/ package depends on CSWgcc3rt and its >> binaries are linked against libgcc_s.so.1. Does that mean they were >> compiled using gcc and that's where the size difference comes from? I >> did my builds with Sun Studio cc. > > Yup, most likely > > If you wanted to spend more time on it, you could recompile and tell sun cc > to optimize for size more than speed. It tends to "unroll loops" if you > highly optimize. > And/Or reduce the optimize level to plain "-O", if you are using -fast, and > compare that. Synergy is onlyl a virtual "KVM switch" after all. Ok, i gave it another try with different optimization levels (-xO2, -xO3, without and without -xspace) and i could squeeze the file size for about 150k each (ended up with -xO3 -xspace). Updated packages are in testing/. As its still the same day, REV and thus the package file names staid the same. How do you differentiate the updated package in such a situation? Right now pkg-get (and pkgutil) won't let me upgrade the package. Cheers Sebastian From phil at bolthole.com Fri Nov 28 18:19:28 2008 From: phil at bolthole.com (Philip Brown) Date: Fri, 28 Nov 2008 09:19:28 -0800 Subject: [csw-maintainers] First packaging efforts (synergy 1.3.1 in testing/). Feedback, someone? In-Reply-To: <4930232C.6050901@opencsw.org> References: <49300228.20206@opencsw.org> <20081128144806.GD22302@bolthole.com> <4930232C.6050901@opencsw.org> Message-ID: <20081128171928.GG9759@bolthole.com> On Fri, Nov 28, 2008 at 05:58:20PM +0100, Sebastian Kayser wrote: > Updated packages are in testing/. As its still the same day, REV and > thus the package file names staid the same. How do you differentiate the > updated package in such a situation? > > Right now pkg-get (and pkgutil) won't let me upgrade the package. add a ".2" on the end of REV=YYYY.DD.MM But I would personally suggest that in this SPECIFIC case, since those packages have not been officially released yet, that you manually pkgrm CSWsynergy, and leave the updated package name without the .2, since you are presumably going to just copy what is in /testing, to newpkgs, when you are done. From james at opencsw.org Fri Nov 28 21:16:39 2008 From: james at opencsw.org (James Lee) Date: Fri, 28 Nov 2008 20:16:39 GMT Subject: [csw-maintainers] BO Buildfarm will be down due to migration In-Reply-To: <1530472E-819B-4A7A-8301-363B1F1768F8@opencsw.org> References: <57E10DB6-126E-4AEC-A222-B2C809D79EBB@opencsw.org> <1530472E-819B-4A7A-8301-363B1F1768F8@opencsw.org> Message-ID: <20081128.20163900.560390367@gyor.oxdrove.co.uk> On 27/11/08, 21:28:12, Dagobert Michelsen wrote regarding Re: [csw-maintainers] BO Buildfarm will be down due to migration: > James: Please repeat your benchmark, and the clock should now be > running in sync too. Rerun with local storage on each machine, this is a fairer test of the machines - although the previous was a fair test of those particular installations. pandora V240 2 x 1500MHz US3i: real 7:09.894 user 0.015 sys 0.033 (showing good repeatability, previous was 7:09.891) build8s T5220 32 x 1165MHz UltraSPARC T2: real 10:18.513 user 39:59.926 sys 8:12.902 Extracting elements of build we see the differences, real times: Task US3i T2 ./configure 59 2:54 gmake -j $NCPU 4:46 3:01 gmake -j 16 - 3:03 gmake -j 8 - 3:30 gmake -j 4 - 6:09 Conclusion, the T2 has more overall power but is unable to utilise it as the overall build process is not parallel enough (disclaimer, in this case...). We should see benefits when several people are working concurrently. James. From james at opencsw.org Fri Nov 28 21:22:59 2008 From: james at opencsw.org (James Lee) Date: Fri, 28 Nov 2008 20:22:59 GMT Subject: [csw-maintainers] Popularity statistics In-Reply-To: <625385e30811241245i7cbf0d00j19d05b68e5bf93fc@mail.gmail.com> References: <492B0558.7050605@opencsw.org> <625385e30811241158y4a73fd4ep132f3335dc980581@mail.gmail.com> <492B0A01.6070501@opencsw.org> <20081124122759.Q25010@bolthole.com> <625385e30811241245i7cbf0d00j19d05b68e5bf93fc@mail.gmail.com> Message-ID: <20081128.20225900.3487983687@gyor.oxdrove.co.uk> On 24/11/08, 20:45:27, Peter Bonivart wrote regarding Re: [csw-maintainers] Popularity statistics: > Another simple thing would be to use James' package list to find the > oldest packages (with his Last Changed field). A quick review of those > might find us a lot of packages that need updates but are orphaned. "Last Changed" has been superseded by the REV date in version but for a per maintainer summary look at the "Last activity date" on my maintainer pages. Even this isn't a true test as perhaps a package doesn't need rebuild - I have packages where the upstream source hasn't change in over 10 years (http://wwwthep.physik.uni-mainz.de/~plass/gv)/. Another activity measure is the last login dates, run this on login.bo.opencsw.org if you are interested: last | nawk '!/^reboot/&&!/^wtmp/{print $1}' | sort | uniq James. From sebastian at skayser.de Fri Nov 28 17:57:10 2008 From: sebastian at skayser.de (Sebastian Kayser) Date: Fri, 28 Nov 2008 17:57:10 +0100 Subject: [csw-maintainers] First packaging efforts (synergy 1.3.1 in testing/). Feedback, someone? In-Reply-To: <20081128144806.GD22302@bolthole.com> References: <49300228.20206@opencsw.org> <20081128144806.GD22302@bolthole.com> Message-ID: <493022E6.2030002@skayser.de> Philip Brown wrote: > On Fri, Nov 28, 2008 at 03:37:28PM +0100, Sebastian Kayser wrote: >> >From what i see, the current/ package depends on CSWgcc3rt and its >> binaries are linked against libgcc_s.so.1. Does that mean they were >> compiled using gcc and that's where the size difference comes from? I >> did my builds with Sun Studio cc. > > Yup, most likely > > If you wanted to spend more time on it, you could recompile and tell sun cc > to optimize for size more than speed. It tends to "unroll loops" if you > highly optimize. > And/Or reduce the optimize level to plain "-O", if you are using -fast, and > compare that. Synergy is onlyl a virtual "KVM switch" after all. Ok, i gave it another try with different optimization levels (-xO2, -xO3, without and without -xspace) and i could squeeze the file size for about 150k each (ended up with -xO3 -xspace). Updated packages are in testing/. As its still the same day, REV and thus the package file names staid the same. How do you differentiate the updated package in such a situation? Right now pkg-get (and pkgutil) won't let me upgrade the package. Cheers Sebastian From bwalton at opencsw.org Sat Nov 29 02:25:51 2008 From: bwalton at opencsw.org (Ben Walton) Date: Fri, 28 Nov 2008 20:25:51 -0500 Subject: [csw-maintainers] sgmlcommon + xmlcommon Message-ID: <1227921597-sup-8640@ntdws12.chass.utoronto.ca> Hi All, I've just placed 2 new packages in /home/testing. sgmlcommon and xmlcommon are laying the groundwork for bringing in some docbook packages in the near future. While they don't currently do much, if you'll be interested in the docbook stuff when it arrives, you could give these a peek now to make sure I haven't overlooked any hardcoded paths, etc...[these were converted almost verbatim from the rhel5 sgml-common source rpm, with modifications as required for our fhs instead of the lsb] 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 Sat Nov 29 16:12:28 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sat, 29 Nov 2008 16:12:28 +0100 Subject: [csw-maintainers] Hudson Message-ID: <49315BDC.1060902@opencsw.org> Hi The Hudson installation is getting pretty much properly set up now. I've added a few projects to it, but it seems that we have a bunch of outdated builds so that GAR is not able to fetch the sources. As an example build I've added Ben Waldons latest sgml-xml-common package: http://buildfarm.opencsw.org/hudson/job/sgml-xml-common-trunk-sparc-sun-solaris2.8/4/console I'm waiting on a chmod from Dago to get the i386 builder going, but after that it should work on that platform too. 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. -- Trygve From trygvel at opencsw.org Sat Nov 29 18:16:28 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sat, 29 Nov 2008 18:16:28 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <49315BDC.1060902@opencsw.org> References: <49315BDC.1060902@opencsw.org> Message-ID: <493178EC.8060801@opencsw.org> Trygve Laugst?l wrote: > Hi > > The Hudson installation is getting pretty much properly set up now. I've > added a few projects to it, but it seems that we have a bunch of > outdated builds so that GAR is not able to fetch the sources. > > As an example build I've added Ben Waldons latest sgml-xml-common package: > > http://buildfarm.opencsw.org/hudson/job/sgml-xml-common-trunk-sparc-sun-solaris2.8/4/console > > I'm waiting on a chmod from Dago to get the i386 builder going, but > after that it should work on that platform too. > > 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. I just realized that there used to be a /home/hudson and that work just fine for us. So I made a small script that simply runs bldcat in the two directories so if [1] would be exposed to the public people could start to download the packages right away! $ (cd /home/hudson/repository; find hudson) hudson hudson/i386 hudson/i386/5.8 hudson/i386/5.8/catalog hudson/sparc hudson/sparc/5.8 hudson/sparc/5.8/sgmlcommon-0.6.3,REV=2008.11.29-SunOS5.8-all-CSW.pkg.gz hudson/sparc/5.8/xmlcommon-0.6.3,REV=2008.11.29-SunOS5.8-all-CSW.pkg.gz hudson/sparc/5.8/catalog hudson/sparc/5.8/tomcat4-4.1.37,REV=2008.11.29-SunOS5.8-all-CSW.pkg.gz (I called the repository "hudson" to clearly separate it from the other repositories, but I would like a more generic name, perhaps something like "devel") [1]: nfs:/home/hudson/repository/ -- Trygve From bonivart at opencsw.org Sat Nov 29 18:32:31 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Sat, 29 Nov 2008 18:32:31 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <493178EC.8060801@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> Message-ID: <625385e30811290932y17882a3cs2a63bb21bb2c269f@mail.gmail.com> On Sat, Nov 29, 2008 at 6:16 PM, Trygve Laugst?l wrote: > I just realized that there used to be a /home/hudson and that work just > fine for us. So I made a small script that simply runs bldcat in the two > directories so if [1] would be exposed to the public people could start > to download the packages right away! Cool that you use bldcat to create the catalogs. :-) Thanks to Dagobert it will be faster and better in pkgutil 1.3. Pkgutil will work with your repo now but if you want pkg-get to work as well you need to create the descriptions file the new bldcat produces. You still have more work to do for pkg-get to work but it's a start. You can find the new bldcat here: http://www.bonivart.com/pkgutil/bldcat Now I have to find out what Hudson and Maven is... :-) -- /peter From trygvel at opencsw.org Sat Nov 29 18:44:08 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sat, 29 Nov 2008 18:44:08 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <625385e30811290932y17882a3cs2a63bb21bb2c269f@mail.gmail.com> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <625385e30811290932y17882a3cs2a63bb21bb2c269f@mail.gmail.com> Message-ID: <49317F68.10407@opencsw.org> Peter Bonivart wrote: > On Sat, Nov 29, 2008 at 6:16 PM, Trygve Laugst?l wrote: >> I just realized that there used to be a /home/hudson and that work just >> fine for us. So I made a small script that simply runs bldcat in the two >> directories so if [1] would be exposed to the public people could start >> to download the packages right away! > > Cool that you use bldcat to create the catalogs. :-) Thanks to > Dagobert it will be faster and better in pkgutil 1.3. Pkgutil will > work with your repo now but if you want pkg-get to work as well you > need to create the descriptions file the new bldcat produces. You > still have more work to do for pkg-get to work but it's a start. > > You can find the new bldcat here: http://www.bonivart.com/pkgutil/bldcat So if I just replace the one in /opt/csw/bin I should get a working descriptions file too? > Now I have to find out what Hudson and Maven is... :-) Hehe :) Hudson is a continuous integration engine which polls your SCM (subversion in our case) regularly to find if there are changes and of so starts a build. In addition you can get it to notify you when stuff breaks and lots of other features. Maven is "just" another build tool for Java applications. [1]: http://en.wikipedia.org/wiki/Continuous_integration -- Trygve From trygvel at opencsw.org Sat Nov 29 18:55:24 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sat, 29 Nov 2008 18:55:24 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <49317F68.10407@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <625385e30811290932y17882a3cs2a63bb21bb2c269f@mail.gmail.com> <49317F68.10407@opencsw.org> Message-ID: <4931820C.80404@opencsw.org> Trygve Laugst?l wrote: > Peter Bonivart wrote: >> On Sat, Nov 29, 2008 at 6:16 PM, Trygve Laugst?l wrote: >>> I just realized that there used to be a /home/hudson and that work just >>> fine for us. So I made a small script that simply runs bldcat in the two >>> directories so if [1] would be exposed to the public people could start >>> to download the packages right away! >> Cool that you use bldcat to create the catalogs. :-) Thanks to >> Dagobert it will be faster and better in pkgutil 1.3. Pkgutil will >> work with your repo now but if you want pkg-get to work as well you >> need to create the descriptions file the new bldcat produces. You >> still have more work to do for pkg-get to work but it's a start. >> >> You can find the new bldcat here: http://www.bonivart.com/pkgutil/bldcat > > So if I just replace the one in /opt/csw/bin I should get a working > descriptions file too? And we have a proper descriptions file too! $ find /home/hudson/repository /home/hudson/repository /home/hudson/repository/hudson /home/hudson/repository/hudson/i386 /home/hudson/repository/hudson/i386/5.8 /home/hudson/repository/hudson/i386/5.8/descriptions /home/hudson/repository/hudson/i386/5.8/catalog /home/hudson/repository/hudson/sparc /home/hudson/repository/hudson/sparc/5.8 /home/hudson/repository/hudson/sparc/5.8/asciidoc-8.2.7,REV=2008.11.29-SunOS5.8-all-CSW.pkg.gz /home/hudson/repository/hudson/sparc/5.8/sgmlcommon-0.6.3,REV=2008.11.29-SunOS5.8-all-CSW.pkg.gz /home/hudson/repository/hudson/sparc/5.8/xmlcommon-0.6.3,REV=2008.11.29-SunOS5.8-all-CSW.pkg.gz /home/hudson/repository/hudson/sparc/5.8/descriptions /home/hudson/repository/hudson/sparc/5.8/catalog /home/hudson/repository/hudson/sparc/5.8/tomcat4-4.1.37,REV=2008.11.29-SunOS5.8-all-CSW.pkg.gz [snip] -- Trygve From dam at opencsw.org Sat Nov 29 21:39:42 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 29 Nov 2008 21:39:42 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <625385e30811290932y17882a3cs2a63bb21bb2c269f@mail.gmail.com> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <625385e30811290932y17882a3cs2a63bb21bb2c269f@mail.gmail.com> Message-ID: <7CEBB40F-D798-4DC0-9D38-20E7DCF62D11@opencsw.org> Hi, Am 29.11.2008 um 18:32 schrieb Peter Bonivart: > On Sat, Nov 29, 2008 at 6:16 PM, Trygve Laugst?l > wrote: >> > Cool that you use bldcat to create the catalogs. :-) Thanks to > Dagobert it will be faster and better in pkgutil 1.3. Pkgutil will > work with your repo now but if you want pkg-get to work as well you > need to create the descriptions file the new bldcat produces. Hugh? The version I send you builds both catalog and descriptions file. Do you see a problem with this? Trygve: You can pick up a version which does both from /home/dam/bldcat until this gets integrated. Best regards -- Dago From dam at opencsw.org Sat Nov 29 21:44:45 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 29 Nov 2008 21:44:45 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <7CEBB40F-D798-4DC0-9D38-20E7DCF62D11@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <625385e30811290932y17882a3cs2a63bb21bb2c269f@mail.gmail.com> <7CEBB40F-D798-4DC0-9D38-20E7DCF62D11@opencsw.org> Message-ID: <776863EF-F01F-4C18-8BB9-AD55068D2BFC@opencsw.org> Hi Peter, Am 29.11.2008 um 21:39 schrieb Dagobert Michelsen: > Am 29.11.2008 um 18:32 schrieb Peter Bonivart: >> Cool that you use bldcat to create the catalogs. :-) Thanks to >> Dagobert it will be faster and better in pkgutil 1.3. Pkgutil will >> work with your repo now but if you want pkg-get to work as well you >> need to create the descriptions file the new bldcat produces. > > Hugh? The version I send you builds both catalog and descriptions > file. Do you see a problem with this? Sorry folks, the last sentence didn't got to my mind. After a day of grinding wood I'm pretty much worn out :-P Best regards -- Dago From dam at opencsw.org Sat Nov 29 22:06:18 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 29 Nov 2008 22:06:18 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <493178EC.8060801@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> Message-ID: <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> Hi, 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 About setting up projects: Here is an idea of how to deal with releases in the future. - 'gmake release' checks that everything is committed to the repository and makes a copy to tags/-x.y,REV=a.b.c - Hudson makes packages from tags/* with the revision stamp - The URL and SVN revision are annotated inside the package This makes it possible to exactly reproduce any package and reference the build description precisely - Only packages generated in this way will be accepted for release in the future - This way it will be possible to allow "fast-tracking" of emergency bugfixes as the packages could be delivered and catalog build automatically. The details still need to be worked out of course. - Packages from trunk/ and branches/ are also build by Hudson but are put in another location (continoues integration) (/opencsw/testing/-*?) We still need a solution for Solaris 8 x86 packages containing 64 bit code. Best regards -- Dago From bonivart at opencsw.org Sat Nov 29 22:16:53 2008 From: bonivart at opencsw.org (Peter Bonivart) Date: Sat, 29 Nov 2008 22:16:53 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <7CEBB40F-D798-4DC0-9D38-20E7DCF62D11@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <625385e30811290932y17882a3cs2a63bb21bb2c269f@mail.gmail.com> <7CEBB40F-D798-4DC0-9D38-20E7DCF62D11@opencsw.org> Message-ID: <625385e30811291316j78f40334kec56e48eb375e962@mail.gmail.com> On Sat, Nov 29, 2008 at 9:39 PM, Dagobert Michelsen wrote: >> Cool that you use bldcat to create the catalogs. :-) Thanks to >> Dagobert it will be faster and better in pkgutil 1.3. Pkgutil will >> work with your repo now but if you want pkg-get to work as well you >> need to create the descriptions file the new bldcat produces. > > Hugh? The version I send you builds both catalog and descriptions > file. Do you see a problem with this? That's the one I'm talking about. :-) I just assumed Trygve was using bldcat from pkgutil 1.2, that is before your additions. -- /peter From trygvel at opencsw.org Sat Nov 29 23:13:20 2008 From: trygvel at opencsw.org (=?ISO-8859-1?Q?Trygve_Laugst=F8l?=) Date: Sat, 29 Nov 2008 23:13:20 +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: <4931BE80.9060904@opencsw.org> Dagobert Michelsen wrote: > Hi, > > 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 > > > About setting up projects: Here is an idea of how to deal > with releases in the future. > - 'gmake release' checks that everything is committed to the > repository and makes a copy to tags/-x.y,REV=a.b.c This is most likely very useful and something that we should work on. > - Hudson makes packages from tags/* with the revision stamp This might be a bit more pain than what we gain from it. You would have to create a new job for Hudson to build from a tag which would be used only once. I would rather create a script that 1) checks out the code 2) performs gmake clean package to create the package 3) tags the package 4) copies the pkg.gz to new/ > - The URL and SVN revision are annotated inside the package > This makes it possible to exactly reproduce any package and > reference the build description precisely > - Only packages generated in this way will be accepted for > release in the future > - This way it will be possible to allow "fast-tracking" of > emergency bugfixes as the packages could be delivered > and catalog build automatically. The details still need > to be worked out of course. > - Packages from trunk/ and branches/ are also build by Hudson > but are put in another location (continoues integration) > (/opencsw/testing/-*?) This is doable, but I'm not sure if it is worth creating branches for stuff. If you need to maintain two versions concurrently (like you might want to for stuff like apache) it might be as easy to create two directories with their own trunk (like apache/trunk and apache2/trunk). > We still need a solution for Solaris 8 x86 packages containing > 64 bit code. I think having 32 and 64 bit packages is the best, perhaps with some clever logic in pkg-get to fetch the foo_64 package for the foo package. The 64 bit package would have to depend on the 32 bit package. This is definitely a useful subject to talk about in Z?rich over a beer. -- Trygve From pfelecan at opencsw.org Sun Nov 30 11:00:17 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Sun, 30 Nov 2008 11:00:17 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> (Dagobert Michelsen's message of "Sat\, 29 Nov 2008 22\:06\:18 +0100") References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> Message-ID: Dagobert Michelsen writes: > - Only packages generated in this way will be accepted for > release in the future Can you elaborate this please? -- Peter From pfelecan at opencsw.org Sun Nov 30 16:27:18 2008 From: pfelecan at opencsw.org (Peter FELECAN) Date: Sun, 30 Nov 2008 16:27:18 +0100 Subject: [csw-maintainers] request for CSWtetex installation Message-ID: Is there somebody having the rights to install the CSWtetex package on the build systems? I requested its installation on the buildfarm list but it's Sunday... A day when I can work on building packages... -- Peter From phil at bolthole.com Sun Nov 30 16:54:00 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 30 Nov 2008 07:54:00 -0800 Subject: [csw-maintainers] request for CSWtetex installation In-Reply-To: References: Message-ID: <20081130155400.GA90990@bolthole.com> On Sun, Nov 30, 2008 at 04:27:18PM +0100, Peter FELECAN wrote: > Is there somebody having the rights to install the CSWtetex package on > the build systems? I requested its installation on the buildfarm list > but it's Sunday... A day when I can work on building packages... > -- anyone besides Dagobert have perms to do it? I dont. From phil at bolthole.com Sun Nov 30 17:08:45 2008 From: phil at bolthole.com (Philip Brown) Date: Sun, 30 Nov 2008 08:08:45 -0800 Subject: [csw-maintainers] Hudson In-Reply-To: <4931BE80.9060904@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> <4931BE80.9060904@opencsw.org> Message-ID: <20081130160845.GB90990@bolthole.com> On Sat, Nov 29, 2008 at 11:13:20PM +0100, Trygve Laugst?l wrote: > I think having 32 and 64 bit packages is the best, perhaps with some > clever logic in pkg-get to fetch the foo_64 package for the foo package. > The 64 bit package would have to depend on the 32 bit package. This is > definitely a useful subject to talk about in Z?rich over a beer. the trouble is, sometimes you want the 32bit package,a nd sometimes, you want the 64bit package. pkg-get cant read your mind :-} (32bit for speed, 64bit for data space. except for amd64, apparently. then maybe the choice is 64bit for speed, 32bit for conservation of memory) From dam at opencsw.org Sun Nov 30 19:57:30 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 30 Nov 2008 19:57:30 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <4931BE80.9060904@opencsw.org> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> <4931BE80.9060904@opencsw.org> Message-ID: <08E11B9D-BFB6-4143-BA6C-43DBC5A4BAA8@opencsw.org> Hi Trygve, Am 29.11.2008 um 23:13 schrieb Trygve Laugst?l: >> - Packages from trunk/ and branches/ are also build by Hudson >> but are put in another location (continoues integration) >> (/opencsw/testing/-*?) > > This is doable, but I'm not sure if it is worth creating branches for > stuff. If you need to maintain two versions concurrently (like you > might > want to for stuff like apache) it might be as easy to create two > directories with their own trunk (like apache/trunk and apache2/ > trunk). It is not for two concurrent versions, more in case of a maintenance when the production version ("stable") is kept in one branch and the development version ("current") in another one. >> We still need a solution for Solaris 8 x86 packages containing >> 64 bit code. > > I think having 32 and 64 bit packages is the best, perhaps with some > clever logic in pkg-get to fetch the foo_64 package for the foo > package. > The 64 bit package would have to depend on the 32 bit package. This is > definitely a useful subject to talk about in Z?rich over a beer. Yes. 32/64 is a tough one, especially on x86. Best regards -- Dago From dam at opencsw.org Sun Nov 30 20:21:37 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 30 Nov 2008 20:21:37 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> Message-ID: <6973508A-DB45-41A9-B5CB-C89EC06F698F@opencsw.org> Hi Peter, Am 30.11.2008 um 11:00 schrieb Peter FELECAN: > Dagobert Michelsen writes: > >> - Only packages generated in this way will be accepted for >> release in the future > > Can you elaborate this please? In the distant future packages to be released will be build in a very defined fashion: Make the manifest, commit it to the repository and let the farm build a distributable package. Theoretically a maintainer could mess around with a package, hand-compile something, let GAR assemble it and than release something unreproducable. But don't worry. This won't come tomorrow. And even not the day after that ;-) It is more a long-term goal. Best regards -- Dago From dam at opencsw.org Sun Nov 30 20:24:10 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 30 Nov 2008 20:24:10 +0100 Subject: [csw-maintainers] Hudson In-Reply-To: <20081130160845.GB90990@bolthole.com> References: <49315BDC.1060902@opencsw.org> <493178EC.8060801@opencsw.org> <68A31D39-85E7-451C-BDE6-9601CCAC10F2@opencsw.org> <4931BE80.9060904@opencsw.org> <20081130160845.GB90990@bolthole.com> Message-ID: Hi Phil, Am 30.11.2008 um 17:08 schrieb Philip Brown: > On Sat, Nov 29, 2008 at 11:13:20PM +0100, Trygve Laugst?l wrote: >> I think having 32 and 64 bit packages is the best, perhaps with some >> clever logic in pkg-get to fetch the foo_64 package for the foo >> package. >> The 64 bit package would have to depend on the 32 bit package. This >> is >> definitely a useful subject to talk about in Z?rich over a beer. > > the trouble is, sometimes you want the 32bit package,a nd sometimes, > you > want the 64bit package. pkg-get cant read your mind :-} > > (32bit for speed, 64bit for data space. except for amd64, apparently. > then maybe the choice is 64bit for speed, 32bit for conservation of > memory) That is not the problem. The problem is, that Hudson can't build a combined package for Solaris 8 x86 with 64 bit amd64 stuff in it. We *may* work around this at some point in time but a discussion which path to follow is welcome. Integration in one package as it is done now is certainly a solution, but it is still only one possible solution among others which I would like to have discussed. The result may very well be that we keep it the way it is, but with Hudson and GAR v2 some preliminaries have changed which may lead to another direction. Best regards -- Dago From dam at opencsw.org Sun Nov 30 20:37:03 2008 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 30 Nov 2008 20:37:03 +0100 Subject: [csw-maintainers] Java... again! In-Reply-To: <20081128143415.GB22302@bolthole.com> References: <20081117093702.Q21898@bolthole.com> <4921BB9D.4030403@opencsw.org> <20081117111730.B21898@bolthole.com> <4921C561.5030406@opencsw.org> <20081117114608.C21898@bolthole.com> <5F994B04-687B-4AC3-91AE-DAAE62F4716B@opencsw.org> <20081117172408.D39788@bolthole.com> <4922660D.9070203@opencsw.org> <4CA4F900-6D7D-49AD-A072-7D15E7A90AB3@opencsw.org> <20081128143415.GB22302@bolthole.com> Message-ID: Hi Phil, Am 28.11.2008 um 15:34 schrieb Philip Brown: > Sounds good to me. > > Just one word of warning... > > On Fri, Nov 28, 2008 at 01:38:29PM +0100, Dagobert Michelsen wrote: >> When the permit from Sun arrives I'll give the package >> a final shot. > > we may be waiting for a very LOOOOONG time on that. > even when sun is 100% favourable to doing something, getting legal > approval > for something seems to take a minimum of 3 months :-( Maybe, but if I never ask I never get an answer ;-) Best regards -- Dago