SquidAnalyzer: Minor Trouble Building RPM

Home » CentOS » SquidAnalyzer: Minor Trouble Building RPM
CentOS 6 Comments

Hi,

I’m using the SquidAnalyzer network analysis tool in combination with Squid. Up until now, I’ve been running Slackware Linux on my servers. I
built a custom package that installs SquidAnalyzer to
/var/www/vhosts/squidreport/html. Then I setup an Apache virtual host for SquidAnalyzer’s pages.

Since I’m migrating my servers from Slackware to CentOS, I’d like to build a corresponding RPM package for SquidAnalyzer. I downloaded the sources here:

http://squidanalyzer.darold.net/download.html

Then I set up a local build environment as described in the CentOS wiki.

The source tarball already contains a squidanalyzer.spec file in the packaging/RPM subdirectory. So I copied that spec file over to
~/rpmbuild/SPECS and the source tarball to ~/rpmbuild/SOURCES. The version information in the spec file is wrong, it indicates 6.2, but the version of SquidAnalyzer is 6.2-1.

Unfortunately when I insert the correct version in the spec file, I get this:

$ rpmbuild -ba –clean squidanalyzer.spec error: line 5: Illegal char ‘-‘ in: Version: 6.2-1

What can I do now?

Niki
—
Microlinux – Solutions informatiques 100% Linux et logiciels libres
7, place de l’église – 30730 Montpezat Web : http://www.microlinux.fr Mail : info@microlinux.fr Tél. : 04 66 63 10 32

6 thoughts on - SquidAnalyzer: Minor Trouble Building RPM

  • Le 11/03/2015 09:40, Niki Kovacs a écrit :

    I’ll answer that myself, since I just found the culprit. There’s a version mismatch between the tarball and the extracted source directory. Simply renaming the tarball to version 6.2 fixed it.

    Cheers,

    Niki

    —
    Microlinux – Solutions informatiques 100% Linux et logiciels libres
    7, place de l’église – 30730 Montpezat Web : http://www.microlinux.fr Mail : info@microlinux.fr Tél. : 04 66 63 10 32

  • Le 11/03/2015 12:52, Joseph L. Brunner a écrit :

    Yes. As much as I appreciate Slackware’s bone-headed philosophy, the installer, the simple startup scripts, the general Keep-It-Simple approach and the overall robustness, the absence of PAM has been a real showstopper for me.

    Until now the only way to setup centralized authentication and roaming profiles is to use a combination of NIS and NFS, which is far from ideal in terms of security.

    I suggested the inclusion of PAM in a public poll in the Slackware forum on LinuxQuestions.org, which got mixed results. About half of the Slackware users welcomed the idea, the other half got pretty angry, and the result turned into a flamefest.

    The idea had been to somewhat open up Slackware to the enterprise world, but as far as I can reckon, the word “enterprise” curiously enough seems to have a bad taste for a significant portion of Slackware’s user base.

    After this heated exchange, I decided to take a pragmatic approach and choose a more appropriate tool as a base for my business. So here I am.

    Cheers,

    Niki

    PS: after a few years on LQ, the general tone on the CentOS mailing list seems like the Alban Berg Quartet after Slayer@Hellfest. :o)
    —
    Microlinux – Solutions informatiques 100% Linux et logiciels libres
    7, place de l’église – 30730 Montpezat Web : http://www.microlinux.fr Mail : info@microlinux.fr Tél. : 04 66 63 10 32

  • Also, you can’t use a – in the Version tag in the rpm spec file. A
    mismatch between the tarball name and the extracted source directory would be a different error.

  • Yeah, businesses have this weird idea that if something works right, it should just keep working for the life of the business…

    By the way – if you are new to CentOS and RH-style in general, you might want to look at how much of the local configuration settings are abstracted into files under /etc/sysconfig/. I’m not sure if slackware used that at all since it is a SysVinit concept – or how it will evolve with the change do systemd, but generally for the packages that pick up option settings there you can avoid editing the main config files and setting up conflicts with future rpm updates. It’s not perfect but it helps.