On Dec 31, 2011, at 7:25 AM, Henrik Ingo wrote: > Hi BJ, all > > 1) Updated RPM packaging scripts: > > There were several things that needed to be updated in our RPM builds > (and I'm sure in DEBs too, but one thing at a time). I've pushed a > branch with updates at: > > https://code.launchpad.net/~hingo/pkg-drizzle/drizzle7-dev.rpm > > As BJ has been doing a good job keeping the RPM build scripts up to > date, I didn't want to step on your toes, so didn't push directly into > pkg-drizzle/drizzle7-dev.rpm, but feel free to do it if you approve of > changes. >
Some things to note: --- - Turns out --user and --daemon don't work well together, so have to use sudo -u drizzle /usr/sbin/drizzled --daemon instead. We previously used sudo and had other issues which I can't recall now. Changes like this should be noted very clearly that the change was made due to a specific bug (with link to bug) … so that the change can be reverted once the bug is fixed. --- - Remove 2>&1 so that errors are shown to user. Currently all auth and policy plugins will break drizzled due to installing broken stuff into /etc/drizzle/conf.d/ so let's at least not silently fail. Init script should never output anything to console. If there init script is failing to start a process, it is assumed the admin would attempt to run the daemon manually to see whats happening. You have to remember, that in general init scripts start processes on boot up … in which case you don't want any output to console… so I think this should be reverted. --- - Upstream: libdrizzle-2.0 is no longer there. Package libdrizzle* now contains libdrizzle-1.0. It was my understanding that 'libdrizzle' is version 2.0 … and libdrizzle-1.0 is obviously only for backward compat… so I think that libdrizzle-1.0 should be a separate package… along with libdrizzle-1.0-devel > > 2) Where do you publish RPMs? > > lp:~drizzle-developers/pkg-drizzle/drizzle7-dev.rpm says: > > * Tue Nov 15 2011 BJ Dierkes <[email protected]> - 2011.11.29-1 > - Latest sources from upstream. Release notes available at: > https://launchpad.net/drizzle/fremont/2011-11-13 > > BJ: Where are these RPMs actually available??? They are not on > rpm.drizzle.org. > When a build actually completes (for all distros) then I would rsync the repos to rpm.drizzle.org … that said, due to bugs and build failures on different OS versions… I've not had a solid build in a while which is why the repos are not up to date. FWIW, I'm currently using our internal build system (Rackspace) to build across all RPM distros (RHEL, Fedora). This made sense when the majority of the Drizzle team were employed by Rackspace… but not so much anymore. We may need to discuss how to handle this moving forward so that nobody is relying on me solely for packaging RPMs. If we want to continue to use the same system, its called MonkeyFarm and its Open Source .. http://github.com/rackspace/monkeyfarm …. but I'd need at least two systems to get it all setup and running. If we get hudson setup to do RPM builds and tests for all RHEL/Fedora releases… then we can also just copy the built RPMs from there and sync them to a repo to kill two birds with one stone. --- derks _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
