Bug 402821

Certainly an extra ':' ... :)

Spec URL: http://dmitry.butskoy.name/phpwapmail/phpwapmail.spec
SRPM URL: http://dmitry.butskoy.name/phpwapmail/phpwapmail-0.9.2-0.src.rpm

rpmlint:
phpwapmail.src: W: mixed-use-of-spaces-and-tabs (spaces: line 81, tab: line 52)
The specfile mixes use of spaces and tabs for indentation, which is a
cosmetic annoyance.  Use either spaces or tabs for indentation, not both.

Minor

phpwapmail.noarch: E: non-standard-gid /etc/phpwapmail/config.php apache
A file in this package is owned by a non standard group.
Standard groups are:
root, bin, daemon, sys, adm, tty, disk, lp, mem, kmem, wheel, mail,
news, uucp, man, games, gopher, dip, ftp, lock, nobody, users

phpwapmail.noarch: E: non-readable /etc/phpwapmail/config.php 0640
The file can't be read by everybody. If this is expected (for security
reasons), contact your rpmlint distributor to get it added to the list of
exceptions for your distro (or add it to your local configuration if you
installed rpmlint from the source tarball).

Probably fine.

More to follow.

On install attempt:
[root@fawkes SPECS]# rpm -ivh ../RPMS/noarch/phpwapmail-0.9.2-0.fc8.noarch.rpm 
Preparing...                ########################################### [100%]
   1:phpwapmail             ########################################### [100%]
sed: -e expression #1, char 34: unknown option to `s'
error: %post(phpwapmail-0.9.2-0.fc8.noarch) scriptlet failed, exit status 1

> either spaces or tabs for indentation

It seems some kind of too extra requirement... :)  I prefer to not follow it,
because I try to create .spec files "good readable" under uncient Linux console
or even a dumb terminal. Using 4-space steps for indentation is good for this
purpose. And then I prefer to use "one tab" instead of "8 spaces" for the
"two-step" indentation... 

> non-standard-gid /etc/phpwapmail/config.php apache
> A file in this package is owned by a non standard group.

This package is intended for using under Apache and mod_php, i.e. "httpd"+"php"
Try rpmlint for the current "httpd" package. Your comments?... :)

> non-readable /etc/phpwapmail/config.php 0640

Yep, it is for security.


> sed: -e expression #1, char 34: unknown option to `s'

I cannot reproduce this... Could you obtain a full "sed" command string? (For
example, re-build the package under your environment, adding "echo" before the
"sed" command. This way the full "sed" command string will be just printed, not
executed, and we'll see whats going on...)

> It seems some kind of too extra requirement... :)  I prefer to not follow it,
> because I try to create .spec files "good readable" under uncient Linux console
> or even a dumb terminal. Using 4-space steps for indentation is good for this
> purpose. And then I prefer to use "one tab" instead of "8 spaces" for the
> "two-step" indentation... 

It's not telling you which to use, it wants you to use 1 or the other.  The
error tells you the first place you have a tab if the first part has spaces, or
vice versa.  Very helpful in fixing it, actually.

> This package is intended for using under Apache and mod_php, i.e. "httpd"+"php"
> Try rpmlint for the current "httpd" package. Your comments?... :)

Agreed.  I say leave it alone, like I did in some of my packages for webapps. :)

> Yep, it is for security.

Agreed.

> I cannot reproduce this... Could you obtain a full "sed" command string? (For
> example, re-build the package under your environment, adding "echo" before the
> "sed" command. This way the full "sed" command string will be just printed, not
> executed, and we'll see whats going on...)

On the second install, it didn't occur, so I commented out the if block.  I got
this:
sed -i -e /$SECRET = "";/ s/"";/"Mb0j4md+4azjZMCB";  # Autogenerated for
fawkes.local/ /etc/phpwapmail/config.php

Afterward, I uncommented and tried again and it's fine.


Tried it on another machine in case it was a fresh install issue, no luck. 
Never mind.  I'll proceed. . .

Did a complete review, and it checks out. Fix the tab/spaces issue and you're
set.  Just change the tabs that start lines 52 and 54 to spaces.

Well,

update it for tab/space issue, see in the same location (I didn't bump release
for a while...)

> Tried it on another machine in case it was a fresh install issue, no luck.

No luck in what? :)

In other words, can you reproduce the issue mentioned in the comment #3 ?

> In other words, can you reproduce the issue mentioned in the comment #3 ?

I was not able to reproduce it.  I suspect it might have been some sort of sh
syntax error caused by the hash generated by the %post script.  On each run, it
could be different.  If that is the cause, then it's not likely to happen too
often and isn't a blocker.  It could also have been oddness on my machine.

Either way, as everything else looks good, 

APPROVED.

Oh, I've understood -- besides the [0-9a-zA-Z], base64 use "+" and "/", and this
"/" spoils the sed command. I'll use "|" for sed instead.

Thought it might be something like that.

New Package CVS Request
=======================
Package Name: phpwapmail
Short Description: WAP-based e-mail client
Owners: buc
Branches: F-7 F-8
InitialCC:
Cvsextras Commits: yes

cvs done.

Package Change Request
======================
Package Name: phpwapmail
New Branches: el5 el6
Owners: buc

Git done (by process-git-requests).