From maciej at opencsw.org Mon Aug 1 13:50:14 2011 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=) Date: Mon, 1 Aug 2011 12:50:14 +0100 Subject: [csw-maintainers] Technical Summercamp in Kiel 2011 In-Reply-To: <958B6EC9-5CE1-4B2E-BE39-2C85617D3EDD@opencsw.org> References: <958B6EC9-5CE1-4B2E-BE39-2C85617D3EDD@opencsw.org> Message-ID: 2011/7/6 Dagobert Michelsen : > Hi folks, > > time is passing and I would like to invite everybody to add their available time slots > to the doodle poll: > ?http://doodle.com/ewfzuze75afweueq > > I removed the early dates within holidays as there were anyway nobody interested and > added September. Please update soon as about 4 weeks in advance is needed for hotel > booking etc. >From the current state of the poll it looks like the optimal date is the weekend of 17-18 September 2011. So far, 7 people responded to the poll. I thought we could personally invite some maintainers to the summercamp. There might be people who just didn't think about coming. At the same time, our project is at relatively large changes (the automatic process), so the more people are there to discuss the future direction, the better. To extend the appeal to all maintainers - if you are an OpenCSW package maintainer, please consider coming over to the OpenCSW Summercamp in Kiel! Even if you maintain only a couple of packages, or you're a new maintainer, come and meet others! Knowing other maintainers will make your participation in the project easier and more fun! Just by osmosis, you will learn a lot about our build system, infrastructure, and things you didn't know existed. More importantly, you'll get to know personally other maintainers. While it might not seem that significant, it is! Email is inherently very low bandwidth; getting to know people lays the shared background necessary for effective day to day email communication. Lastly, other maintainers want to get to know you. I am coming to Kiel, and I want to meet you! I'm sure that other maintainers want the same. So, get to know others, come to Kiel! I'm looking forward to seeing you there! To get started, look at the doodle poll above and select the dates that fit you. Maciej From bwalton at opencsw.org Mon Aug 1 15:59:48 2011 From: bwalton at opencsw.org (Ben Walton) Date: Mon, 01 Aug 2011 09:59:48 -0400 Subject: [csw-maintainers] how the catalog signing works In-Reply-To: References: <1311439323-sup-2576@pinkfloyd.chass.utoronto.ca> Message-ID: <1312207128-sup-4900@pinkfloyd.chass.utoronto.ca> Excerpts from Maciej Blizi?ski's message of Sun Jul 24 17:14:24 -0400 2011: Hi Maciej, > If it could send email, where would you plan to send it to? Perhaps > a mail alias with a bunch of interested people? Something like a > mailing list, but with no archives (not necessary). Yes, a simple alias exploder should suffice for this. Something like gpgagent@ would work. The recipients should be those that can take action to reset the passphrase. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 From maciej at opencsw.org Tue Aug 2 01:09:20 2011 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=) Date: Tue, 2 Aug 2011 00:09:20 +0100 Subject: [csw-maintainers] gar and php question In-Reply-To: References: <4DEBB025.6010702@opencsw.org> <1307325421-sup-8953@pinkfloyd.chass.utoronto.ca> <1307365421-sup-6666@pinkfloyd.chass.utoronto.ca> <1307382737-sup-3595@pinkfloyd.chass.utoronto.ca> Message-ID: 2011/6/6 Philip Brown : > So, please go ahead and announce , that we plan to remove it within > [insert timeframe here]. > (and to holler if this for some reason is a problem for someone, and why) > > And then after that time, we can remove it. > Since this is by definition extreme legacy software, the people may > not keep up to date with announcements, etc :-} so we may want to set > a somewhat longer timeframe than would otherwise be fine. > > July 1st? To continue the topic, the deprecation has been announced on the 8th of June: http://lists.opencsw.org/pipermail/users/2011-June/008917.html We're now at the beginning of August, so should we go ahead and drop php4 from unstable? Maciej From bwalton at opencsw.org Tue Aug 2 01:24:19 2011 From: bwalton at opencsw.org (Ben Walton) Date: Mon, 01 Aug 2011 19:24:19 -0400 Subject: [csw-maintainers] gar and php question In-Reply-To: References: <4DEBB025.6010702@opencsw.org> <1307325421-sup-8953@pinkfloyd.chass.utoronto.ca> <1307365421-sup-6666@pinkfloyd.chass.utoronto.ca> <1307382737-sup-3595@pinkfloyd.chass.utoronto.ca>

Message-ID: No hesitations here. I'm ready to push the php5 update to unstable too...I just need to update the deps to fit mysql changes. Thanks -Ben "Maciej Blizi?ski" wrote: 2011/6/6 Philip Brown : > So, please go ahead and announce , that we plan to remove it within > [insert timeframe here]. > (and to holler if this for some reason is a problem for someone, and why) > > And then after that time, we can remove it. > Since this is by definition extreme legacy software, the people may > not keep up to date with announcements, etc :-} so we may want to set > a somewhat longer timeframe than would otherwise be fine. > > July 1st? To continue the topic, the deprecation has been announced on the 8th of June: http://lists.opencsw.org/pipermail/users/2011-June/008917.html We're now at the beginning of August, so should we go ahead and drop php4 from unstable? Maciej _____________________________________________ maintainers mailing list maintainers at lists.opencsw.org https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwalton at opencsw.org Tue Aug 2 02:39:56 2011 From: bwalton at opencsw.org (Ben Walton) Date: Mon, 01 Aug 2011 20:39:56 -0400 Subject: [csw-maintainers] moving along... Message-ID: <1312245431-sup-5389@pinkfloyd.chass.utoronto.ca> Hi All, I'm back from a nice cottage vacation and ready to tackle another chunk of the automation process. We have two large (user visible) chunks remaining: 1. Mantis integration. 2. www/packages browsing interface. I think I'd like to work on 2 first. Can someone with access to www-mockup point me in the right direction for how we're doing our development there? I'll then proceed to check out the wordpress code and poke around our browser and the various databases to see how this should best be handled. Maciej, off the top of your head, how easy would it be to browse the same database that generates the catalogs? It's likely not carrying the svn url info presently, but would it be missing anything else? Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 From maciej at opencsw.org Tue Aug 2 08:39:15 2011 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=) Date: Tue, 2 Aug 2011 07:39:15 +0100 Subject: [csw-maintainers] moving along... In-Reply-To: <1312245431-sup-5389@pinkfloyd.chass.utoronto.ca> References: <1312245431-sup-5389@pinkfloyd.chass.utoronto.ca> Message-ID: 2011/8/2 Ben Walton : > Maciej, off the top of your head, how easy would it be to browse the > same database that generates the catalogs? ?It's likely not carrying > the svn url info presently, but would it be missing anything else? >From the top of my head, it's also missing dependency information. A bit more information: Everything is in the pickled data structure, but not everything is also in database tables. Here's an example of the data structure: http://buildfarm.opencsw.org/pkgdb/srv4/071d260b87a06ff3339c1c2b89da1b02/ It has all the information about the package, but it's not as easily accessible. I had a git branch in the works with the data structure update. I haven't worked on it for a while now, but I can get back to it. Maciej From maciej at opencsw.org Tue Aug 2 15:57:20 2011 From: maciej at opencsw.org (Maciej (Matchek) Blizinski) Date: Tue, 2 Aug 2011 14:57:20 +0100 Subject: [csw-maintainers] Checking for ".so" in shared library file names Message-ID: Based on mantis bug #4811[1], here's an idea for a new check: all shared library must have the ".so" component in the file names. It can be in the middle (libfoo.so.1) or at the end (libfoo-1.so), but it must be present. The check would be limited to regular files, symlinks would not be checked - it's harder to implement reliably. Thoughts? Maciej [1] https://www.opencsw.org/mantis/view.php?id=4811 From maciej at opencsw.org Tue Aug 2 17:11:58 2011 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=) Date: Tue, 2 Aug 2011 16:11:58 +0100 Subject: [csw-maintainers] Buildfarm is inaccessible Message-ID: Our buildfarm seems inaccessible. Commands (e.g. uptime) started to hang on some hosts, and eventually ssh access to login.opencsw.org stopped working. The buildfarm database is inaccessible too. I've already notified buildfarm@, but got no answer so far, so I'm sending a message to a wider audience. Is anyone on the list able to investigate the issue? Maciej From bwalton at opencsw.org Tue Aug 2 17:24:09 2011 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 02 Aug 2011 11:24:09 -0400 Subject: [csw-maintainers] [csw-buildfarm] Buildfarm is inaccessible In-Reply-To: References: Message-ID: <1312298236-sup-4347@pinkfloyd.chass.utoronto.ca> Excerpts from Maciej Blizi?ski's message of Tue Aug 02 11:11:58 -0400 2011: > Is anyone on the list able to investigate the issue? I can confirm your findings but can't do anything about it. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 From bwalton at opencsw.org Wed Aug 3 04:59:24 2011 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 02 Aug 2011 22:59:24 -0400 Subject: [csw-maintainers] Checking for ".so" in shared library file names In-Reply-To: References: Message-ID: <1312340272-sup-1773@pinkfloyd.chass.utoronto.ca> Excerpts from Maciej (Matchek) Blizinski's message of Tue Aug 02 09:57:20 -0400 2011: > Based on mantis bug #4811[1], here's an idea for a new check: all > shared library must have the ".so" component in the file names. It can > be in the middle (libfoo.so.1) or at the end (libfoo-1.so), but it > must be present. The check would be limited to regular files, > symlinks would not be checked - it's harder to implement reliably. It's a reasonable test I think. For symlinks, you'd need to do a full resolution and if the target is supposed to end in .so, so should the link. Likely a pile of (mostly unnecessary) work for that though. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 From bwalton at opencsw.org Wed Aug 3 05:51:42 2011 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 02 Aug 2011 23:51:42 -0400 Subject: [csw-maintainers] libxml2 broken In-Reply-To: <1307407557-sup-3296@pinkfloyd.chass.utoronto.ca> References: <4DEBD2F3.8070808@opencsw.org> <4DEC251C.5060106@opencsw.org> <4DEC2D37.2010809@opencsw.org> <65D204EA-6681-4CAD-87C7-D383CD6E1875@opencsw.org> <1307407557-sup-3296@pinkfloyd.chass.utoronto.ca> Message-ID: <1312343279-sup-6076@pinkfloyd.chass.utoronto.ca> Excerpts from Ben Walton's message of Mon Jun 06 20:46:20 -0400 2011: > > Always good to keep the eyes open. I just looked at the libiconv recipe and > > "NOTES" from libiconv-1.13.1 says > > > > Q: Support EBCDIC ? > > A: No! > > > > However, the packaged and released libxml2 2.7.8 does also not pass this test. > > > > Ben: Do you want to report this upstream? > > Sure. Let me get a good set of info together to shoot up there and > I'll do so. Picking up an old thread that got lost in my mailbox... This is a known bug that also affects (at least) OSX[1]. I'm determining how much tampering is required to produce the requisite fix. The other option is to patch out the troublesome test file. Time availability may decide the outcome. I've got a test build running right now that will hopefully strip out the ebcdic handling support. If that works, I'll build the autoconf support next. Thanks -Ben [1] https://bugzilla.gnome.org/show_bug.cgi?id=603432 -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 From jesse at opencsw.org Wed Aug 3 06:13:24 2011 From: jesse at opencsw.org (Jesse Reynolds) Date: Wed, 3 Aug 2011 13:43:24 +0930 Subject: [csw-maintainers] [csw-buildfarm] Buildfarm is inaccessible In-Reply-To: <1312298236-sup-4347@pinkfloyd.chass.utoronto.ca> References: <1312298236-sup-4347@pinkfloyd.chass.utoronto.ca> Message-ID: 2011/8/3 Ben Walton > Excerpts from Maciej Blizi?ski's message of Tue Aug 02 11:11:58 -0400 2011 > : > > > Is anyone on the list able to investigate the issue? > > I can confirm your findings but can't do anything about it. > > Seems OK now. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jesse at opencsw.org Wed Aug 3 06:59:37 2011 From: jesse at opencsw.org (Jesse Reynolds) Date: Wed, 3 Aug 2011 14:29:37 +0930 Subject: [csw-maintainers] Help for newbie creating a new package Message-ID: Hello Please forgive my dumbass newbie questions... I understand that I should use 'mgar newpkg' to create a new package definition, but it looks like I first need to have created a Makefile, or some other type of definitions file, for it says; unstable10x:~/opencsw/rbgems $ mgar newpkg mysql ERROR: No package build description found in the current directory (I am trying to create a package for the mysql ruby gem.) Where should I get a template 'package build description' from, and where should I place it, before running 'mgar newpkg mysql'? And then what happens? Note that so far all I've done is: - copied ben?s .garrc and modified paths to reference my home dir rather than his - run ?mgar init? - initialise the opencsw build dir (~/opencsw) - run ?mgar up --all? - fetch the package build descriptions - takes a good while (many hours!) - run ?mgar index? to create (update) the index of the package build tree Thank you Jesse -------------- next part -------------- An HTML attachment was scrubbed... URL: From jesse at opencsw.org Wed Aug 3 07:43:02 2011 From: jesse at opencsw.org (Jesse Reynolds) Date: Wed, 3 Aug 2011 15:13:02 +0930 Subject: [csw-maintainers] Where to report bugs for mgar ? Message-ID: Hello Do bugs in the mgar command get reported in the gar_devel project in Mantis? (There's also a gar_dev). In this case it's a minor thing - the usage output doesn't include the 'newpkg' command. The man page says: REPORTING BUGS Please report bugs at http://www.opencsw.org/mantis/. But not which project. ... Thank you Jesse -------------- next part -------------- An HTML attachment was scrubbed... URL: From jesse at opencsw.org Wed Aug 3 09:06:45 2011 From: jesse at opencsw.org (Jesse Reynolds) Date: Wed, 3 Aug 2011 16:36:45 +0930 Subject: [csw-maintainers] Help for newbie creating a new package In-Reply-To: References: Message-ID: On 3 August 2011 14:29, Jesse Reynolds wrote: > Hello > > Please forgive my dumbass newbie questions... > > I understand that I should use 'mgar newpkg' to create a new package > definition, but it looks like I first need to have created a Makefile, or > some other type of definitions file, for it says; > > unstable10x:~/opencsw/rbgems $ mgar newpkg mysql > ERROR: No package build description found in the current directory > > (I am trying to create a package for the mysql ruby gem.) > > Where should I get a template 'package build description' from, and where > should I place it, before running 'mgar newpkg mysql'? > > And then what happens? > In my wanderings I've found the following wiki page: http://wiki.opencsw.org/project-rubygems Which says the sqlite gem Makefile is a good staring point for other gem package Makefiles: http://sourceforge.net/apps/trac/gar/browser/csw/mgar/pkg/rbgems/sqlite3-ruby/trunk/Makefile And these are part of the rbgems category which has it's Makefile here: http://sourceforge.net/apps/trac/gar/browser/csw/mgar/gar/v2/categories/rbgems/category.mk But yes, I don't quite get what to do. I tried creating a Makefile and running 'mgar newpkg gperf' as per one of the examples in the wiki but it complained ... unstable9s:~/test/gperf $ mgar fetch svn: '.' is not a working copy ERROR: No build system found at /home/jesse/opencsw/.buildsys/ Clearly I'm missing something basic about how, or where, to run mgar. tia. > > Note that so far all I've done is: > > - copied ben?s .garrc and modified paths to reference my home dir rather > than his > - run ?mgar init? - initialise the opencsw build dir (~/opencsw) > - run ?mgar up --all? - fetch the package build descriptions - takes a good > while (many hours!) > - run ?mgar index? to create (update) the index of the package build tree > > Thank you > Jesse > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jesse at opencsw.org Wed Aug 3 09:10:36 2011 From: jesse at opencsw.org (Jesse Reynolds) Date: Wed, 3 Aug 2011 16:40:36 +0930 Subject: [csw-maintainers] [csw-buildfarm] Buildfarm is inaccessible In-Reply-To: References: <1312298236-sup-4347@pinkfloyd.chass.utoronto.ca> Message-ID: On 3 August 2011 13:43, Jesse Reynolds wrote: > > > 2011/8/3 Ben Walton > >> Excerpts from Maciej Blizi?ski's message of Tue Aug 02 11:11:58 -0400 >> 2011: >> >> > Is anyone on the list able to investigate the issue? >> >> I can confirm your findings but can't do anything about it. >> >> > Seems OK now. > Er, the VSphere machines seem to have gone away again. I was logged into unstable9x and unstable10x earlier but now they've frozen up. I can still log in to unstable9s and the other sparc build machines. But I can't ping or ssh to any of the x86 build machines that are VMs on vsphere right now. Jesse -------------- next part -------------- An HTML attachment was scrubbed... URL: From maciej at opencsw.org Wed Aug 3 09:24:59 2011 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=) Date: Wed, 3 Aug 2011 08:24:59 +0100 Subject: [csw-maintainers] Where to report bugs for mgar ? In-Reply-To: References: Message-ID: 2011/8/3 Jesse Reynolds : > Do bugs in the mgar command get reported in the gar_devel project in Mantis? > (There's also a gar_dev). > In this case it's a minor thing - the usage output doesn't include the > 'newpkg' command. > The man page says: > REPORTING BUGS > ? ? ?Please report bugs at http://www.opencsw.org/mantis/. > But not which project. ... It looks like mgar is not registered in mantis. Mantis integration is one of the missing bits which we haven't solved since the former release manager's departure. We're working on it. [1] For now, you can file a bug against gar_dev, and Ben will route the bug to Sebastian, or you can send Sebastian (skayser@) an email. Another thing you can do is checking out mgar sources[2], editing them and sending a patch to devel at . Maciej [1] http://lists.opencsw.org/pipermail/maintainers/2011-August/015087.html [2] https://opencsw.svn.sourceforge.net/svnroot/opencsw/gar-wrapper/ From maciej at opencsw.org Wed Aug 3 09:38:31 2011 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=) Date: Wed, 3 Aug 2011 08:38:31 +0100 Subject: [csw-maintainers] Help for newbie creating a new package In-Reply-To: References:

Message-ID: 2011/8/3 Jesse Reynolds : > I tried creating a Makefile and running 'mgar newpkg gperf' as per one of > the examples in the wiki but it complained ... > unstable9s:~/test/gperf $ mgar fetch > svn: '.' is not a working copy > ERROR: No build system found at /home/jesse/opencsw/.buildsys/ > Clearly I'm missing something basic about how, or where, to run mgar. The error you're seeing is the one that shows when the GARTYPE setting is missing from the Makefile you're attempting to build. This setting tells mgar which branch of mgar (v1, v2, perhaps another one) to use. You can also debug mgar. It is written in shell, so you can run the following command: /opt/csw/bin/bash -x /opt/csw/bin/mgar (...) If the debug output doesn't help you, please post it here (or on IRC via a paste service), it should shed more light on what's going on. Maciej From maciej at opencsw.org Wed Aug 3 09:44:35 2011 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=) Date: Wed, 3 Aug 2011 08:44:35 +0100 Subject: [csw-maintainers] Checking for ".so" in shared library file names In-Reply-To: <1312340272-sup-1773@pinkfloyd.chass.utoronto.ca> References: <1312340272-sup-1773@pinkfloyd.chass.utoronto.ca> Message-ID: 2011/8/3 Ben Walton : > It's a reasonable test I think. ?For symlinks, you'd need to do a full > resolution and if the target is supposed to end in .so, so should the > link. To be more precise, if the target is a shared library as indicated by libmagic, there needs to be an ".so" somewhere in the file name. At times, you have 2 or 3 levels of symlinks before you reach the regular file. >?Likely a pile of (mostly unnecessary) work for that though. One of the problems might be that the symlink target is not available, e.g. it's not in the package set that checkpkg is examining. In such case, checkpkg could reach and fetch that information from the database, but mime metadata are currently not cached in MySQL tables. It's something I intend to change, but it'll require time, and we have more urgent problems to solve. The regular file / shared library check, is easy to implement. Maciej From jesse at opencsw.org Wed Aug 3 10:02:31 2011 From: jesse at opencsw.org (Jesse Reynolds) Date: Wed, 3 Aug 2011 17:32:31 +0930 Subject: [csw-maintainers] Help for newbie creating a new package In-Reply-To: References:

Message-ID: 2011/8/3 Maciej Blizi?ski > 2011/8/3 Jesse Reynolds : > > I tried creating a Makefile and running 'mgar newpkg gperf' as per one of > > the examples in the wiki but it complained ... > > unstable9s:~/test/gperf $ mgar fetch > > svn: '.' is not a working copy > > ERROR: No build system found at /home/jesse/opencsw/.buildsys/ > > Clearly I'm missing something basic about how, or where, to run mgar. > > The error you're seeing is the one that shows when the GARTYPE setting > is missing from the Makefile you're attempting to build. This setting > tells mgar which branch of mgar (v1, v2, perhaps another one) to use. > You can also debug mgar. It is written in shell, so you can run the > following command: > > /opt/csw/bin/bash -x /opt/csw/bin/mgar (...) > > If the debug output doesn't help you, please post it here (or on IRC > via a paste service), it should shed more light on what's going on. > > Thanks Maciej. I've added the following to the Makefile: GARTYPE = v2 And how it seems happy. I've now done the following for the gperf example: mgar fetch mgar makesum mgar checksum mgar extract mgar configure mgar build mgar test Yay! However: mgar package runs into some errors. Here's the tail end of the output: CSWgperf: If any of the reported errors were false positives, you can override them pasting the lines below to the GAR recipe. CHECKPKG_OVERRIDES_CSWgperf += bad-rpath-entry|/opt/SUNWspro/lib/v8|opt/csw/bin/gperf CHECKPKG_OVERRIDES_CSWgperf += bad-rpath-entry|/lib|opt/csw/bin/gperf CHECKPKG_OVERRIDES_CSWgperf += bad-rpath-entry|/opt/SUNWspro/lib|opt/csw/bin/gperf CHECKPKG_OVERRIDES_CSWgperf += bad-rpath-entry|/opt/SUNWspro/lib/rw7|opt/csw/bin/gperf Please note that checkpkg isn't suggesting you should simply add these overrides do the Makefile. It only informs what the overrides could look like. You need to understand what are the reported issues about and use your best judgement to decide whether to fix the underlying problems or override them. For more information, scroll up and read the detailed messages. gmake: *** [pkgcheck] Error 2 Getting much closer though, thank you. Jesse -------------- next part -------------- An HTML attachment was scrubbed... URL: From maciej at opencsw.org Wed Aug 3 10:10:25 2011 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=) Date: Wed, 3 Aug 2011 09:10:25 +0100 Subject: [csw-maintainers] Help for newbie creating a new package In-Reply-To: References:

Message-ID: 2011/8/3 Jesse Reynolds : > CHECKPKG_OVERRIDES_CSWgperf += > bad-rpath-entry|/opt/SUNWspro/lib/v8|opt/csw/bin/gperf > CHECKPKG_OVERRIDES_CSWgperf += bad-rpath-entry|/lib|opt/csw/bin/gperf > CHECKPKG_OVERRIDES_CSWgperf += > bad-rpath-entry|/opt/SUNWspro/lib|opt/csw/bin/gperf > CHECKPKG_OVERRIDES_CSWgperf += > bad-rpath-entry|/opt/SUNWspro/lib/rw7|opt/csw/bin/gperf This check deals with the RPATH setting in the resulting binaries. Sun Studio by default adds extra RPATH entries, e.g. "/opt/SUNWspro/lib/v8". To fix this, you need to tell Sun Studio to stop doing that: EXTRA_CFLAGS = -xnorunpath The EXTRA_CFLAGS variable value will be put by GAR into the right places for autotools to pick up. Maciej From jesse at opencsw.org Wed Aug 3 10:33:04 2011 From: jesse at opencsw.org (Jesse Reynolds) Date: Wed, 3 Aug 2011 18:03:04 +0930 Subject: [csw-maintainers] Help for newbie creating a new package In-Reply-To: References:

Message-ID: 2011/8/3 Maciej Blizi?ski > 2011/8/3 Jesse Reynolds : > > CHECKPKG_OVERRIDES_CSWgperf += > > bad-rpath-entry|/opt/SUNWspro/lib/v8|opt/csw/bin/gperf > > CHECKPKG_OVERRIDES_CSWgperf += bad-rpath-entry|/lib|opt/csw/bin/gperf > > CHECKPKG_OVERRIDES_CSWgperf += > > bad-rpath-entry|/opt/SUNWspro/lib|opt/csw/bin/gperf > > CHECKPKG_OVERRIDES_CSWgperf += > > bad-rpath-entry|/opt/SUNWspro/lib/rw7|opt/csw/bin/gperf > > This check deals with the RPATH setting in the resulting binaries. > Sun Studio by default adds extra RPATH entries, e.g. > "/opt/SUNWspro/lib/v8". To fix this, you need to tell Sun Studio to > stop doing that: > > EXTRA_CFLAGS = -xnorunpath > > The EXTRA_CFLAGS variable value will be put by GAR into the right > places for autotools to pick up. > Thanks. So I put that line into gperf/Makefile and ran 'mgar clean', 'mgar package' and it ends up with the same errors again (though in a different order): CHECKPKG_OVERRIDES_CSWgperf += bad-rpath-entry|/opt/SUNWspro/lib|opt/csw/bin/gperf CHECKPKG_OVERRIDES_CSWgperf += bad-rpath-entry|/opt/SUNWspro/lib/rw7|opt/csw/bin/gperf CHECKPKG_OVERRIDES_CSWgperf += bad-rpath-entry|/opt/SUNWspro/lib/v8|opt/csw/bin/gperf CHECKPKG_OVERRIDES_CSWgperf += bad-rpath-entry|/lib|opt/csw/bin/gperf This is on unstable9s, I think I ran it last time on one of the other sparc machines in the build farm. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jesse at opencsw.org Wed Aug 3 10:41:16 2011 From: jesse at opencsw.org (Jesse Reynolds) Date: Wed, 3 Aug 2011 18:11:16 +0930 Subject: [csw-maintainers] Help for newbie creating a new package In-Reply-To: References:

Message-ID: On 3 August 2011 18:03, Jesse Reynolds wrote: > > > 2011/8/3 Maciej Blizi?ski > >> 2011/8/3 Jesse Reynolds : >> > CHECKPKG_OVERRIDES_CSWgperf += >> > bad-rpath-entry|/opt/SUNWspro/lib/v8|opt/csw/bin/gperf >> > CHECKPKG_OVERRIDES_CSWgperf += bad-rpath-entry|/lib|opt/csw/bin/gperf >> > CHECKPKG_OVERRIDES_CSWgperf += >> > bad-rpath-entry|/opt/SUNWspro/lib|opt/csw/bin/gperf >> > CHECKPKG_OVERRIDES_CSWgperf += >> > bad-rpath-entry|/opt/SUNWspro/lib/rw7|opt/csw/bin/gperf >> >> This check deals with the RPATH setting in the resulting binaries. >> Sun Studio by default adds extra RPATH entries, e.g. >> "/opt/SUNWspro/lib/v8". To fix this, you need to tell Sun Studio to >> stop doing that: >> >> EXTRA_CFLAGS = -xnorunpath >> >> The EXTRA_CFLAGS variable value will be put by GAR into the right >> places for autotools to pick up. >> > > Thanks. So I put that line into gperf/Makefile and ran 'mgar clean', 'mgar > package' and it ends up with the same errors again (though in a different > order): > > CHECKPKG_OVERRIDES_CSWgperf += > bad-rpath-entry|/opt/SUNWspro/lib|opt/csw/bin/gperf > CHECKPKG_OVERRIDES_CSWgperf += > bad-rpath-entry|/opt/SUNWspro/lib/rw7|opt/csw/bin/gperf > CHECKPKG_OVERRIDES_CSWgperf += > bad-rpath-entry|/opt/SUNWspro/lib/v8|opt/csw/bin/gperf > CHECKPKG_OVERRIDES_CSWgperf += bad-rpath-entry|/lib|opt/csw/bin/gperf > > This is on unstable9s, I think I ran it last time on one of the other sparc > machines in the build farm. > My Makefile is currently looking like this: unstable9s:~/test/gperf $ cat Makefile NAME = gperf VERSION = 3.0.3 CATEGORIES = devel DESCRIPTION = A perfect hash function generator define BLURB GNU gperf is a perfect hash function generator. For a given list of strings, it produces a hash function and hash table, in form of C or C++ code, for looking up a value depending on the input string. The hash function is perfect, which means that the hash table has no collisions, and the hash table lookup needs a single string comparison only. endef MASTER_SITES = $(GNU_MIRROR) DISTFILES = $(NAME)-$(VERSION).tar.gz GARTYPE = v2 TEST_TARGET = check EXTRA_CFLAGS = -xnorunpath include gar/category.mk -------------- next part -------------- An HTML attachment was scrubbed... URL: From maciej at opencsw.org Wed Aug 3 10:53:43 2011 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=) Date: Wed, 3 Aug 2011 09:53:43 +0100 Subject: [csw-maintainers] Help for newbie creating a new package In-Reply-To: References:

Message-ID: 2011/8/3 Jesse Reynolds : > EXTRA_CFLAGS = -xnorunpath This was under the assumption that it's a C (not C++) code. To enable the same thing for C++ binaries, set: EXTRA_CXXFLAGS = -norunpath (I'm not sure if this is what the problem is, it's a guess that it's a C++ binary.) Maciej From maciej at opencsw.org Wed Aug 3 11:15:44 2011 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=) Date: Wed, 3 Aug 2011 10:15:44 +0100 Subject: [csw-maintainers] Checking for ".so" in shared library file names In-Reply-To: References: <1312340272-sup-1773@pinkfloyd.chass.utoronto.ca> Message-ID: Committed in r15249. Also, run against libdnet which now shows the error tags. http://sourceforge.net/apps/trac/gar/changeset/15249 http://buildfarm.opencsw.org/pkgdb/srv4/c3becaf3633bfdbc0f315b73bc1d798c/ http://buildfarm.opencsw.org/pkgdb/srv4/cbf909119bdfed1a7c07a147741ff511/ Maciej From jesse at opencsw.org Wed Aug 3 11:17:07 2011 From: jesse at opencsw.org (Jesse Reynolds) Date: Wed, 3 Aug 2011 18:47:07 +0930 Subject: [csw-maintainers] Help for newbie creating a new package In-Reply-To: References:

Message-ID: 2011/8/3 Maciej Blizi?ski > 2011/8/3 Jesse Reynolds : > > EXTRA_CFLAGS = -xnorunpath > > This was under the assumption that it's a C (not C++) code. To enable > the same thing for C++ binaries, set: > > EXTRA_CXXFLAGS = -norunpath > > (I'm not sure if this is what the problem is, it's a guess that it's a > C++ binary.) > Thanks. Alas now I get a syntax error on ld - doesn't like -xn... /opt/SUNWspro/bin/CC -xO3 -m32 -xarch=v8 -xnorunpath -m32 -xarch=v8 -L/opt/csw/lib -o gperf version.o positions.o options.o keyword.o keyword-list.o input.o bool-array.o hash-table.o search.o output.o main.o ../lib/libgp.a -lm CC: Warning: Option -xnorunpath passed to ld, if ld is invoked, ignored otherwise /usr/ccs/bin/ld: illegal option -- x /usr/ccs/bin/ld: illegal option -- n ld: warning: option -o appears more than once, first setting taken usage: ld [-6:abc:d:e:f:h:il:mo:p:rstu:z:B:CD:F:GI:L:M:N:P:Q:R:S:VY:?] file(s) -------------- next part -------------- An HTML attachment was scrubbed... URL: From maciej at opencsw.org Wed Aug 3 11:34:53 2011 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=) Date: Wed, 3 Aug 2011 10:34:53 +0100 Subject: [csw-maintainers] Help for newbie creating a new package In-Reply-To: References:

Message-ID: 2011/8/3 Jesse Reynolds : > Thanks. Alas now I get a syntax error on ld - doesn't like -xn... This happens when CFLAGS get passed to the C++ compiler. If you set the flags correctly and it happens, then might be a bug in gperf. Maciej From jesse at opencsw.org Wed Aug 3 15:10:40 2011 From: jesse at opencsw.org (Jesse Reynolds) Date: Wed, 3 Aug 2011 22:40:40 +0930 Subject: [csw-maintainers] Help for newbie creating a new package In-Reply-To: References:

Message-ID: 2011/8/3 Maciej Blizi?ski > 2011/8/3 Jesse Reynolds : > > Thanks. Alas now I get a syntax error on ld - doesn't like -xn... > > This happens when CFLAGS get passed to the C++ compiler. If you set > the flags correctly and it happens, then might be a bug in gperf. > Right. But this is from the GAR example on the wiki, version 3.0.3 of gperf which presumably used to work at some point. http://sourceforge.net/apps/trac/gar/wiki/ExplainedGperf -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwalton at opencsw.org Wed Aug 3 15:22:11 2011 From: bwalton at opencsw.org (Ben Walton) Date: Wed, 03 Aug 2011 09:22:11 -0400 Subject: [csw-maintainers] Where to report bugs for mgar ? In-Reply-To: References:

Message-ID: <1312377656-sup-2607@pinkfloyd.chass.utoronto.ca> Excerpts from Maciej Blizi?ski's message of Wed Aug 03 03:24:59 -0400 2011: > For now, you can file a bug against gar_dev, and Ben will route the > bug to Sebastian, or you can send Sebastian (skayser@) an email. > Another thing you can do is checking out mgar sources[2], editing them > and sending a patch to devel at . Yes, I'll handle routing that to Sebastian, but sending a patch to devel@ is definitely the best option as Sebastian can simply integrate and release an update. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 From maciej at opencsw.org Wed Aug 3 15:27:13 2011 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=) Date: Wed, 3 Aug 2011 14:27:13 +0100 Subject: [csw-maintainers] Help for newbie creating a new package In-Reply-To: References:

Message-ID: 2011/8/3 Jesse Reynolds : > > > 2011/8/3 Maciej Blizi?ski >> >> 2011/8/3 Jesse Reynolds : >> > Thanks. Alas now I get a syntax error on ld - doesn't like -xn... >> >> This happens when CFLAGS get passed to the C++ compiler. ?If you set >> the flags correctly and it happens, then might be a bug in gperf. > > Right. But this is from the GAR example on the wiki, version 3.0.3 of gperf > which presumably used to work at some > point.?http://sourceforge.net/apps/trac/gar/wiki/ExplainedGperf The check set in checkpkg is continuously updated, and build recipes that looked good so far, might start triggering errors. This particular error is not serious, you could override it. However, if you set a variable and it doesn't propagate well, it means that either there's something wrong with the gperf build system and it doesn't process the environment properly, or you don't have the full understanding of how the build works. Just to double-check: did you notice the difference between -norunpath and -xnorunpath? Maciej Maciej From jesse at opencsw.org Wed Aug 3 15:51:38 2011 From: jesse at opencsw.org (Jesse Reynolds) Date: Wed, 3 Aug 2011 23:21:38 +0930 Subject: [csw-maintainers] Help for newbie creating a new package In-Reply-To: References:

Message-ID: 2011/8/3 Maciej Blizi?ski > 2011/8/3 Jesse Reynolds : > > > > > > 2011/8/3 Maciej Blizi?ski > >> > >> 2011/8/3 Jesse Reynolds : > >> > Thanks. Alas now I get a syntax error on ld - doesn't like -xn... > >> > >> This happens when CFLAGS get passed to the C++ compiler. If you set > >> the flags correctly and it happens, then might be a bug in gperf. > > > > Right. But this is from the GAR example on the wiki, version 3.0.3 of > gperf > > which presumably used to work at some > > point. http://sourceforge.net/apps/trac/gar/wiki/ExplainedGperf > > The check set in checkpkg is continuously updated, and build recipes > that looked good so far, might start triggering errors. > Right, OK. > > This particular error is not serious, you could override it. However, > if you set a variable and it doesn't propagate well, it means that > either there's something wrong with the gperf build system and it > doesn't process the environment properly, or you don't have the full > understanding of how the build works. > OK right. I'm just trying to get a feel for the system by following an example. > > Just to double-check: did you notice the difference between -norunpath > and -xnorunpath? > Ack! No! Apologies. Trying that now ... Perfect. The following packages have been built: CSWgperf /home/jesse/staging/gperf-3.0.3,REV=2011.08.03-SunOS5.9-sparc-NOTVERSIONED.pkg.gz [package] complete for gperf. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jesse at opencsw.org Wed Aug 3 15:58:16 2011 From: jesse at opencsw.org (Jesse Reynolds) Date: Wed, 3 Aug 2011 23:28:16 +0930 Subject: [csw-maintainers] Where to report bugs for mgar ? In-Reply-To: <1312377656-sup-2607@pinkfloyd.chass.utoronto.ca> References:

<1312377656-sup-2607@pinkfloyd.chass.utoronto.ca> Message-ID: On 3 August 2011 22:52, Ben Walton wrote: > Excerpts from Maciej Blizi?ski's message of Wed Aug 03 03:24:59 -0400 2011: > > > For now, you can file a bug against gar_dev, and Ben will route the > > bug to Sebastian, or you can send Sebastian (skayser@) an email. > > Another thing you can do is checking out mgar sources[2], editing them > > and sending a patch to devel at . > > Yes, I'll handle routing that to Sebastian, but sending a patch to > devel@ is definitely the best option as Sebastian can simply integrate > and release an update. > > OK, so what's the best one line description of what 'mgar newpkg' does? Perhaps: newpkg - initialises a package build directory, requires a Makefile with package build description As I'm still getting my head around this stuff .. -------------- next part -------------- An HTML attachment was scrubbed... URL: From maciej at opencsw.org Wed Aug 3 16:19:37 2011 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=) Date: Wed, 3 Aug 2011 15:19:37 +0100 Subject: [csw-maintainers] Issues with libdnet Message-ID: [cc:spikey] Hello maintainers, There is a problem with our libdnet package: shared libraries are missing the .so suffix. I've already implemented a check to prevent this from going unnoticed in the future, but we need to fix the existing libdnet package. It is necessary for Spikey (cc'd) to port ArpON to Solaris. I have replicated the issue on our buildfarm, and it looks like it's a bug in the libdnet build scripts. I haven't got the bandwidth to further investigate and fix this. Could any of you jump in and figure out what's wrong? Maciej [1] https://www.opencsw.org/mantis/view.php?id=4811 From bonivart at opencsw.org Wed Aug 3 16:46:49 2011 From: bonivart at opencsw.org (Peter Bonivart) Date: Wed, 3 Aug 2011 16:46:49 +0200 Subject: [csw-maintainers] Where to report bugs for mgar ? In-Reply-To: References:

<1312377656-sup-2607@pinkfloyd.chass.utoronto.ca> Message-ID: On Wed, Aug 3, 2011 at 3:58 PM, Jesse Reynolds wrote: > OK, so what's the best one line description of what 'mgar newpkg' does? Are you sure you're running the latest version? bonivart at unstable9s[~]$ which mgar /home/bonivart/bin/mgar bonivart at unstable9s[~]$ mgar version 380 bonivart at unstable9s[~]$ mgar Wrapper around the GAR build system. Usage: mgar [options] Main actions: init [dir] Initialize package build tree, defaults to ~/opencsw/ index Build/update the package build tree index locate Search a package within the package build tree index up [--all] Update current (or all) package build descriptions newpkg [ver] Create new package build directory Package build actions (to be called from a package build directory): fetch Download the package source makesum Generate a checksum for the package source extract Extract the packages source configure Configure the packages source build Build the package source package Assemble the package platforms Assemble packages for all platforms clean Reset current directory working files (current platform) spotless Reset the package build directory (all platforms) commit -m Commit build recipe (prefixes msg with package path) show-srcdir Show the location of the extracted package source show-stagedir Show the location of the package staging directory find-file Find a file within the extracted package source edit-file Edit a file within the extracted package source Other actions: modenv Display employed compiler options scm Pass a command to the underlying SCM (currently: svn) show-buildsys Display the location and version of the build system show-pkgtree Show the location of the package build tree version Display mgar version information Note that it does indeed mention newpkg. /peter From bwalton at opencsw.org Wed Aug 3 19:53:55 2011 From: bwalton at opencsw.org (Ben Walton) Date: Wed, 03 Aug 2011 13:53:55 -0400 Subject: [csw-maintainers] [csw-buildfarm] vsphere vms for opencsw build farm inaccessable Message-ID: <1312394016-sup-2972@pinkfloyd.chass.utoronto.ca> Excerpts from Jan Holzhueter's message of Wed Aug 03 13:44:17 -0400 2011: [+maintainers] > The x86 build servers should be up again I hope. Thanks for the update Jan. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 From bonivart at opencsw.org Wed Aug 3 19:56:22 2011 From: bonivart at opencsw.org (Peter Bonivart) Date: Wed, 3 Aug 2011 19:56:22 +0200 Subject: [csw-maintainers] [csw-buildfarm] vsphere vms for opencsw build farm inaccessable In-Reply-To: <4E3988F1.3040408@baltic-online.de> References: <4E394195.3050001@baltic-online.de> <4E3988F1.3040408@baltic-online.de> Message-ID: On Wed, Aug 3, 2011 at 7:44 PM, Jan Holzhueter wrote: > Am 03.08.11 14:39, schrieb Jan Holzhueter: > >> Hi, >> we did have some network Problems. >> Should be fixed now though. >> But it looks like it killed the X build Servers. >> I can't restart them atm. Will try to reach someone who can. > > The x86 build servers should be up again I hope. Yes, they are. Thanks for helping out with this on your vacation! :) /peter From jesse at opencsw.org Thu Aug 4 00:22:22 2011 From: jesse at opencsw.org (Jesse Reynolds) Date: Thu, 4 Aug 2011 07:52:22 +0930 Subject: [csw-maintainers] Where to report bugs for mgar ? In-Reply-To: References:

<1312377656-sup-2607@pinkfloyd.chass.utoronto.ca> Message-ID: On 4 August 2011 00:16, Peter Bonivart wrote: > On Wed, Aug 3, 2011 at 3:58 PM, Jesse Reynolds wrote: > > OK, so what's the best one line description of what 'mgar newpkg' does? > > Are you sure you're running the latest version? > Ah, No, I'm running the version installed on unstable9s: unstable9s:~ $ which mgar /opt/csw/bin/mgar unstable9s:~ $ mgar version 360 So it's best practice to checkout mgar into ~/bin/ ? What other utilities / libraries fall into this category? > bonivart at unstable9s[~]$ which mgar > /home/bonivart/bin/mgar > bonivart at unstable9s[~]$ mgar version > 380 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From maciej at opencsw.org Thu Aug 4 00:29:47 2011 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=) Date: Wed, 3 Aug 2011 23:29:47 +0100 Subject: [csw-maintainers] Where to report bugs for mgar ? In-Reply-To: References: