Who screwed up ClamAV in F18?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ok...  (Before anyone tells me I need to) I will be filing a bugzilla
report on this later today but someone did a bad thing in ClamAV.

If you install the latest packages from the update repositories, they
url chunks unable to create the clamupdate user and group.  Problem
appears to be in the clamav-update package.

During the yum install of the clamav packages...

-- 
 groupadd [options] GROUP

Options:
  -f, --force                   exit successfully if the group already exists,
                                and cancel -g if the GID is already used
  -g, --gid GID                 use GID for the new group
  -h, --help                    display this help message and exit
  -K, --key KEY=VALUE           override /etc/login.defs defaults
  -o, --non-unique              allow to create groups with duplicate
                                (non-unique) GID
  -p, --password PASSWORD       use this encrypted password for the new group
  -r, --system                  create a system account
  -R, --root CHROOT_DIR         directory to chroot into

useradd: group 'clamupdate' does not exist
warning: user clamupdate does not exist - using root
warning: group clamupdate does not exist - using root
 
  Installing: clamav-filesystem            ################### [1522/2490] 
  Installing: clamav-update                ################### [1523/2490]/usr/bin/chown: invalid group: ‘root:clamupdate’
No such file or directory
warning: %post(clamav-update-0.97.8-1.fc18.x86_64) scriptlet failed, exit status 1
 
--

I've had to add that user and group by hand on some of my real systems
but that's not possible in building the NST (Network Security Toolkit)
<http://www.networksecuritytoolkit.org/nst/index.html> respins of F18
since those are building bootable iso images.

Obviously, it only affects fresh installs where someone installs ClamAV
on a new system (or, at least, one that hasn't had it on there before).
If the UID and GID already exist on the system, there's not a problem.

Regards,
Mike
-- 
Michael H. Warfield (AI4NB) | (770) 985-6132 |  mhw@xxxxxxxxxxxx
   /\/\|=mhw=|\/\/          | (678) 463-0932 |  http://www.wittsend.com/mhw/
   NIC whois: MHW9          | An optimist believes we live in the best of all
 PGP Key: 0x674627FF        | possible worlds.  A pessimist is sure of it!

-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org




[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux