From dam at opencsw.org Mon Jan 6 20:43:34 2014 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 6 Jan 2014 20:43:34 +0100 Subject: Low traffic on maintainers@ In-Reply-To: References:

<20131229134913.GA13628@quince>

Message-ID: <06268E94-A2E3-4460-B552-D3A7877825F4@opencsw.org> Hi Jon, Am 06.01.2014 um 19:31 schrieb Jonathan Craig : > On Sun, Jan 5, 2014 at 10:30 AM, Ben Walton via buildfarm >> I was recently surprised when a user declined becoming a maintainer >> because even after watching the video they thought it was still dark >> magic. I don't have a way to gauge the skills of this person, so I >> can't measure the person against the problem, but it was still >> noteworthy. >> > > I must admit that my interaction with the build environment leaves me 1) amazed > at the flexibility and power included, 2) frustrated that every time I use it > I find myself relearning and/or struggling to figure out the process > as it seems > to subtly change in ways that you'll only know if you follow the dev > list closely and > commit the stuff mentioned on there to memory. That is not good. However, I have the impression that we don?t have the manpower to bring it to a ?stable? state. > I'm also faced with moving past Solaris 10 and the only viable pkg repo is > unixpackages.com, the commercial follow-on to sunfreeware. The pricing is > reasonable enough and my past experience with sunfreeware leads me to > believe the packaging quality will be good. Do you think there would be more users if we were to offer an IPS repo? > My preference is for a community supported repository solution as the > attention span of corporations can be limited. My worst nightmare would be > to have my eggs in a blastwave type basket and have it fold underneath me. Do you mean by Blastwave-type a project where only binary packages are offered (like unixpackages now) ? Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2351 bytes Desc: not available URL: From jcraig at opencsw.org Mon Jan 6 22:57:02 2014 From: jcraig at opencsw.org (Jonathan Craig) Date: Mon, 6 Jan 2014 16:57:02 -0500 Subject: Low traffic on maintainers@ In-Reply-To: <06268E94-A2E3-4460-B552-D3A7877825F4@opencsw.org> References:

<20131229134913.GA13628@quince>

<06268E94-A2E3-4460-B552-D3A7877825F4@opencsw.org> Message-ID: Hi Dago, On Mon, Jan 6, 2014 at 2:43 PM, Dagobert Michelsen wrote: > Hi Jon, > > Am 06.01.2014 um 19:31 schrieb Jonathan Craig : >> On Sun, Jan 5, 2014 at 10:30 AM, Ben Walton via buildfarm >>> I was recently surprised when a user declined becoming a maintainer >>> because even after watching the video they thought it was still dark >>> magic. I don't have a way to gauge the skills of this person, so I >>> can't measure the person against the problem, but it was still >>> noteworthy. >>> >> >> I must admit that my interaction with the build environment leaves me 1) amazed >> at the flexibility and power included, 2) frustrated that every time I use it >> I find myself relearning and/or struggling to figure out the process >> as it seems >> to subtly change in ways that you'll only know if you follow the dev >> list closely and >> commit the stuff mentioned on there to memory. > > That is not good. However, I have the impression that we don?t have the manpower > to bring it to a ?stable? state. Unfortunately I don't have the developer chops or sufficient time to really dig into the build environment and help out on stabilizing and/or documenting. Its a fantastically cool infrastructure but remains fairly opaque to me. >> I'm also faced with moving past Solaris 10 and the only viable pkg repo is >> unixpackages.com, the commercial follow-on to sunfreeware. The pricing is >> reasonable enough and my past experience with sunfreeware leads me to >> believe the packaging quality will be good. > > Do you think there would be more users if we were to offer an IPS repo? In my opinion Solaris 10 is dead, long live Solaris 11. SVR packaging on Solaris 10 makes patching and upgrading a nightmare in our shop. This is in contrast to my experience with Solaris 11, which is not all sunshine and rainbows, but light years improvement over Solaris 10. I deeply desire an IPS style repo for a number of reasons; 1) it makes upgrades and patching a breeze, 2) I'm struggling with wrapping my mind around how to best navigate 3 packaging solutions in puppet for Solaris (SVR, IPS, pkgutil), 3) it multiples my work when writing any sort of inventory / compliance scripts as I have to take into account naming in pkgutil vs SVR vs IPS. Although I do have to wonder if my obsession with IPS is my lack of vision because while talking with the folks at unixpackages.com the salesperson indicated that they only have about 30 packages in IPS and this is largely due to lack of demand. Now, maybe if they had a full IPS repo then their demand would be higher. The other thing to tackle is the lack of integration between OpenCSW packages and native OS packages. An example of this is when using rsync to communicate between OpenCSW systems and non-OpenCSW systems. The rsync command can't find its counterpart on the off side unless you explicitly specify it on the command line. This is also true of libraries and the need to build for an OpenCSW system by specifying library locations. On the other hand, Linux distro's manage this in a more sane fashion and installing things from the fedora EPEL don't collide with the stuff in the standard RHEL repository. This is accomplished by actively managing the EPEL catalog to ensure it doesn't include any RHEL packages. The OpenCSW solution is kinda like a chroot solution. Build everything in a self contained world so dependencies only need to be considered within that world. Given the lack of a true package repository and the headaches of the patching process this was required, but is it still required in an IPS world? >> My preference is for a community supported repository solution as the >> attention span of corporations can be limited. My worst nightmare would be >> to have my eggs in a blastwave type basket and have it fold underneath me. > > Do you mean by Blastwave-type a project where only binary packages are offered > (like unixpackages now) ? My blastwave comment was more about how blastwave ceased to exist almost overnight and left people struggling to support their systems. If the folks at unixpackages.com can no longer feed their families on providing packages could they disappear as quickly? At least with a reasonable community based project (which I didn't consider blastwave to be one) you have some insight into the viability of the community. Also, having a full replica of the repository locally means that even if the community goes away you have a frozen point in time available. Jon Craig From grzemba at contac-dt.de Tue Jan 7 11:26:18 2014 From: grzemba at contac-dt.de (Carsten Grzemba) Date: Tue, 07 Jan 2014 11:26:18 +0100 Subject: missing directory 'test' in package In-Reply-To: References:

Message-ID: Hi, I have packaged py-django 1.6.1 but django apps fail because a directory called test is missing in the package. Is there a magic which prevents to package a directoy called test? in: ?~/opencsw/lang-python/django/trunk/work/solaris10-i386/install-isa-pentium_pro-python_version-2_6/opt/csw/lib/python2.6/site-packages/django the directory test exist, but in: ~/opencsw/lang-python/django/trunk/work/solaris10-i386/pkgroot/opt/csw/lib/python2.6/site-packages/django it is missing. THX Carsten -------------- next part -------------- An HTML attachment was scrubbed... URL: From dam at opencsw.org Tue Jan 7 11:29:54 2014 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 7 Jan 2014 11:29:54 +0100 Subject: missing directory 'test' in package In-Reply-To: References:

Message-ID: Hi Carsten, Am 07.01.2014 um 11:26 schrieb Carsten Grzemba : > I have packaged py-django 1.6.1 but django apps fail because a directory called test is missing in the package. > Is there a magic which prevents to package a directoy called test? > in: > ~/opencsw/lang-python/django/trunk/work/solaris10-i386/install-isa-pentium_pro-python_version-2_6/opt/csw/lib/python2.6/site-packages/django > the directory test exist, > but in: > ~/opencsw/lang-python/django/trunk/work/solaris10-i386/pkgroot/opt/csw/lib/python2.6/site-packages/django > it is missing. It should be included, please try DEBUG_MERGING=1 mgar remerge and see which and how the files are copied. Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2351 bytes Desc: not available URL: From grzemba at contac-dt.de Tue Jan 7 12:46:12 2014 From: grzemba at contac-dt.de (Carsten Grzemba) Date: Tue, 07 Jan 2014 12:46:12 +0100 Subject: missing directory 'test' in package In-Reply-To: References:

Message-ID: Ok, I have found in ~/opencsw/.buildsys/v2/categories/python/category.mk directory test is excluded for merging python related packages. and MERGE_EXCLUDE_CATEGORY = helps to prevent this. the primary reason for the problem is addressed here: https://code.djangoproject.com/ticket/20349 Am 07.01.14 schrieb Dagobert Michelsen : > > > > > Hi Carsten, > > Am 07.01.2014 um 11:26 schrieb Carsten Grzemba : > > > I have packaged py-django 1.6.1 but django apps fail because a directory called test is missing in the package. > > Is there a magic which prevents to package a directoy called test? > > in: > > ?~/opencsw/lang-python/django/trunk/work/solaris10-i386/install-isa-pentium_pro-python_version-2_6/opt/csw/lib/python2.6/site-packages/django > > the directory test exist, > > but in: > > ~/opencsw/lang-python/django/trunk/work/solaris10-i386/pkgroot/opt/csw/lib/python2.6/site-packages/django > > it is missing. > > > > > > It should be included, please try > DEBUG_MERGING=1 mgar remerge > and see which and how the files are copied. > > > > > Best regards > > > ? Dago > > -- > "You don't become great by trying to be great, you become great by wanting to do something, > and then doing it so hard that you become great in the process." - xkcd #896 > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dam at opencsw.org Thu Jan 9 17:40:22 2014 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 9 Jan 2014 17:40:22 +0100 Subject: New mgar on the buildfarm Message-ID: Hi folks, I have just updated the CSWmgar package providing /opt/csw/bin/mgar to use the new subversion repository URLs. Please let me know if you find anything suspicious. Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2351 bytes Desc: not available URL: From grzemba at contac-dt.de Mon Jan 13 15:42:26 2014 From: grzemba at contac-dt.de (Carsten Grzemba) Date: Mon, 13 Jan 2014 15:42:26 +0100 Subject: OpenCSW Wintercamp In-Reply-To: References:

<20131229134913.GA13628@quince>