Tech on C&P » RPM

dns2tcp-client-0.5-1

RPMs — Sun, 02 May 2010 20:19:45 +0000

Dns2tcp is a tool for relaying TCP connections over DNS. There is no authentications nor encryption mecanisms : DNS encapsulation must be considered as an unsecure and anonymous transport layer. Ressources should be public external services like ssh, ssltunnel ... This package contains the client part.

file: http://repos.chickenandporn.com/CentOS5.4/RPMS.3rdparty/x86_64/dns2tcp-client-0.5-1.x86_64.rpm
license: GPLv2+
built: 2010-05-02 20:19:45 (Sun, 02 May 2010 20:19:45 +0000)
size (bytes): 38320

dns2tcp-server-0.5-1

RPMs — Sun, 02 May 2010 20:19:45 +0000

file: http://repos.chickenandporn.com/CentOS5.4/RPMS.3rdparty/x86_64/dns2tcp-server-0.5-1.x86_64.rpm
license: GPLv2+
built: 2010-05-02 20:19:45 (Sun, 02 May 2010 20:19:45 +0000)
size (bytes): 37613

Don’t Use Epoch

allanc — Wed, 10 Feb 2010 01:32:01 +0000

Epoch is the “our company in incapable of managing a version” admission; it’s the single most evil thing added to RPM, only to address a vendor’s internal issues with version numbers that always increase. With an actual plan for version numbers, epoch is never necessary. Now that it’s there, it’s a bonehead “easy way out” of having to solve a problem.

How logical is this:

$ sudo rpm -Uvh /home/repos/kludge/doxygen-1.6.0-1.i386.rpm Preparing... ########################################### [100%] package doxygen-1.4.7-1.1.i386 (which is newer than doxygen-1.6.0-1.i386) is already installed

Version 1.4.7 newer than version 1.6.0? It’s not logical. I’m assuming it’s because of Epoch, but Epoch data doesn’t show. Epoch is hidden, secret, and causes confusion like the confusion above.

…and really, once an epoch is set, it’s too easy just to bump it up, and that causes a complete scramble in the orderly, logical increase of version numbers.

The only way to cripple this is to choose the highest epoch number possible. That’s why my Epochs are maxint.

Vixy.Net-0.1 (SVN r3) for CentOS

allanc — Mon, 31 Aug 2009 22:42:47 +0000

Did a quick automake/autoconf on vixynet, and fixed a segfault. Not sure how well it works, but it builds and runs without failing on a segmentation fault, so I’ve added some value. And a trivial man page for kicks. Maybe it needs a self-test suite

If you want to play further, here it is:

vixynet-0.1-1.i386.rpm (85k de106d64e11cd5171620487f2dc1283a)
vixynet-0.1-1.src.rpm (150k d28d596ebb3d7114234915aa18e23ef3)

Affects bug #1712160
Includes submitted patch #1814075

You can grab the patch using rpm2cpio vixynet-0.1-1.src.rpm|cpio -idumB

Freepops-0.2.9 on CentOS-5.3

allanc — Wed, 26 Aug 2009 00:07:39 +0000

I got annoyed by the IMs from Yahoo saying “you have mail” — and it’s junk. Nearly-junk. So I turned off the new-mail warning on my Openfire gateway, found that Freepops was broken and not ported recently, and did a brain-dead port. There were changes needed from the supplied RPM (including a buildsystem that tries hard to fix 1/3 of the portability issues that autotools nails like a carpenter).

The RPM Specfile is still a bit trashed, and you can see I nullified the epoch (never should have been invented)

Installed, configured, and POPping mail from gmail already.

Gmail accepts only a few ports for POP (109, 110, 143, 220, 993, 995, 1110, 2221) so I changed my config from the default port 2000 to 2221:
/etc/sysconfig/freepops
#BIND_IP=127.0.0.1 BIND_PORT=2221 LP_OPTIONS="-v -d -l /var/log/freepopsd"

Assuming my own server with freepops installed is y.example.com, and my username on yahoo is chickenandporn@yahoo.com, my config in Gmail looks like:

gmail POP config with FreePOPs

http://r.chickenandporn.com/freepops-0.2.9-1.src.rpm (2.0M 53e475d6ce051b68111e845542eca23a)
http://r.chickenandporn.com/freepops-0.2.9-1.i386.rpm (1.5M 6f9482fde5bdae2a299a876c914655bc)

Wordpress-mu-2.8.4a-9

allanc — Sun, 23 Aug 2009 22:58:15 +0000

A quick update to Wordpress-mu-2.8.4a-8 due to a recurrence of a bug I locally fixed but should have permanently fixed: “namespace” is now a reserved word, but used in magpie-rss updated into wp-includes by feedwordpress-2009.0707.

Changes: version bumps:

bump wordpress-mu to 2.8.4a
bump wp-bar wp-bar from 0.5.7 to 0.5.8
fixed Magpie-RSS due to “namespace” suddenly being a reserved word in PHP (resulting in a blank page displayed)

Changes: added items: (none)

added google analytics
added a favicon.ico default for the themes that don’t provide (reduces errorlog spam)

The build is available here:

wordpress-mu-2.8.4a-9.noarch.rpm (7.1M adc9e3a01dd3a5c1595fc9de34aecfb5)
wordpress-mu-2.8.4a-9.src.rpm (8.0M b30472658e7c5ede4b7c479992480bd3)

Doxygen-1.6.0 for CentOS

allanc — Thu, 20 Aug 2009 19:07:54 +0000

I just cut a copy of mscgen-0.17 for CentOS, but wanted to use it in Doxygen. My Doxygen is circa-stone-age, so I updated it to offer the “@msc” markup. There was a slight change needed to the build environment, but on the whole, it built, and should offer the “msc” capability as inline markups in code.

Update 2009-08-20 21:09Z: My patch for Doxygen was accepted

This is an SVN build, so may differ slightly from the canonical v1.6.0 release.

Changes:

Correction to specfile and root-level Makefile to match pathnames

The build is available here:

doxygen-1.6.0-1.i386.rpm (3.1M 675ec48a8423afa46da25b81304fc29b)
doxygen-1.6.0-1.src.rpm (3.0M 800cb50b846c6d631cbb31c734564d36)

My patch looks like this

doxygen-1.6.0-svn-build.patch (1.3k 660b0f72c4168dc2b757d82e53a91ae8)

mscgen-0.17 for CentOS

allanc — Thu, 20 Aug 2009 17:15:25 +0000

For some diagrams, I was so happy to find mscgen, a Message Sequence Chart Generator tool that Michael McTernan maintains on his site. It’s designed to act similar to Graphviz, and apparently can be slotted into Doxygen.

examples/simple_prog_desc

Changes:

back out the required autoconf from 2.63 to 2.59 (created $(docdir) problems)
version info is in configure.ac only (specfile imports)
specfile in root directory, allowing smooth “rpmbuild -ta mscgen-0.17.tar.gz”
add a AC_SEARCH_LIBS to ensure -lgd is in the link line

My deliverable is a bit unclean in that I didn’t bump the release from #1, and left a tainted build source rather than pristine+patch. My bad.

The build is available here:

mscgen-0.17-1.i386.rpm (42k 8db2ed6e1811c996be4ddbee96b95b68)
mscgen-0.17-1.src.rpm (164k 23c32e21611dd457552bff96274691c8)

Wordpress-mu-2.8.4a-8

allanc — Tue, 18 Aug 2009 21:13:45 +0000

A minor upgrade to Wordpress-mu-2.8.2-7, I have repackaged wordpress-mu with the common modules I use.

Changes: version bumps:

bump wordpress-mu to 2.8.4a
bump add-to-any-subscribe from 0.9.6.5 to 0.9.7

Changes: added items: (none)

The build is available here:

wordpress-mu-2.8.4a-8.noarch.rpm (6.3M d599ad6bbb3f86e139795e9d6f3fa77a)
wordpress-mu-2.8.4a-8.src.rpm (7.2M 7e8d8fcdc6ff6ec068c7a78ef8e29b8e)

tzdata-2009K-1

allanc — Tue, 18 Aug 2009 21:05:00 +0000

It was noted in InfoSecurity that Oracle Updates Enterprise Linux, modifying tzdata in response to RedHat Errata RHEA-2009-1214, so I packed it over to CentOS. No big thing, it’s a brainless repack, here it is:

tzdata-2009k-1.el5.noarch.rpm (833k be76118b5e1b532e8c520999ec57ce32)
tzdata-2009k-1.el5.src.rpm (388k 4346044105d31ff9f5c6030180e031f5)

The original work is by Petr Machata:

Upstream 2009j
- DST switch for Bangladesh will occur an hour earlier than was thought (we can drop Bangladesh patch).
Upstream 2009k
- Mauritius will not continue to observe DST the coming summer
- Arbitrarily end DST at the end of 2009 so that a POSIX-style time zone string can appear in the Dhaka binary file
Egypt starts winter time on August 21.
Resolves: #517009

Nagios-LDAP-3.2.0 Updated

allanc — Sat, 15 Aug 2009 01:14:47 +0000

despite a slooooow connection to a buildserver (and no, I don’t want to spend another 5 hours to setup a VM, just wanted to get it done), I finally updated my Nagios/LDAP work to a “cvs update” of this weekend which includes v3.2.0. I also edited the deliverable specfile so that the schemas for LDAP are included.

These schema files are the ones I use in actual testing.

Changes: version bumps:

bump nagios to 3.2.0

Changes: added items:

added dhcp.schema
added dnszone.schema
added nagios.schema

The build may have a slew of warnings still, I have some cruft in the code just while I was looking for buy-in. I was initilly shot-down, apparently the core config inside Nagios is somewhat hallowed-ground, and it might be wrong to edit that code. Instead, I should try to do it in a plugin, but in the plugin, I would need to completely redefine the existing configuration code — and maintain it in parallel — or I lose the existing configuration.

I want to emphasize: this adds capability, not replace. Without the ldap_server config, Nagios acts like normal. Undefining the build option means Nagios cleanly stops understanding LDAP. Maybe if it’s written here as well, someone will read it.

The build is available here: (20090814 refers to the CVS update date)

Raw sources:

Wordpress-mu-2.8.2-7

allanc — Sun, 02 Aug 2009 13:53:29 +0000

An update of Wordpress-mu-2.7.0-5, I’ve packaged wordpress-mu-2.8.2-7. I have no added value to this aggregation beyond packaging.

Changes: version bumps:

bump wordpress-mu to 2.8.2
bump feedwordpress from 2009.0618 to 2009.0707
bump nextgen-gallery from 1.3.3 to 1.3.5
- dishonourable mention for the non-versioned URL for nextgen-gallery — manually renamed

Changes: added items:

added wp-bar-0.5.7
- dishonourable mention for the non-versioned URL for wp-bar — manually renamed

The build is available here:

HeaderDoc-7.4.8-1

allanc — Wed, 22 Jul 2009 15:37:39 +0000

Although I prefer Doxygen, I’ve packaged up HeaderDoc for RPM systems so that it can be exploited by others. For me, I see generating a documentation cross-reference after an automated build, just as I did with Smallfoot so many years ago (Smallfoot Linux, coincidentally canceled May 17, 2003)

The Linux toolkit had automatic build/doc-gen/self-test on checkins, which is the kind of thing I’d do with a HeaderDoc RPM.

Without further Adieu, the HeaderDoc RPMs:

MySQLfs: 0.4.0

allanc — Mon, 13 Jul 2009 01:40:04 +0000

Released MySQLfs: 0.4.0. Two days early so that I can do some commits of what I’m working on.

MySQLfs: 0.4.0 ETA 2009-07-15

allanc — Mon, 06 Jul 2009 17:47:50 +0000

I’ve been working on MySQLfs as a replacement for the decade or so of meandering work into the SantaSack. Currently, in this release-candidate that’s been waiting as a version X.Y.Z-rcA-preB-alpha-mchammer for quite a while. (OK, that’s not the version, but nearly)

In order to close a few bugs, address a feature-request, and get this ready for a release 0.4.0 (ie 0.4), I added code documentation (my benefit), regression-testing (including start/stop the daemon), and a few tests to confirm proper behavior.

The idea behind SantaSack was to toss things at a storage device, and have it figure out how it should be found. OK, I know that’s vague, but it’s a response to the ever-increasing size of storage and the “hoarding” that we’re doing more and more on that massive storage. For that reason, I’m going with plugins post-0.4.

While I’m working, I push the Doxygen docs out to Sourceforge: http://mysqlfs.sourceforge.net/html/

The simplified version 0.3.99.2 is available for download:

Wordpress-mu-2.7.0-5

allanc — Mon, 06 Jul 2009 00:10:45 +0000

In resurrecting my blogs, I used my old cut of Wordpress-mu, but intend to update the build.

In the meantime, the build is available here: