Looks like the latest update for the second dvd didn't have the
.discinfo file that tells anaconda which disc you have inserted.
I updated the iso file on the mirror, please try downloading again now
and see if that fixes it for you.
New file size:
1267554304 puias-6.2-i386-DVD-2.iso
Thanks for letting us know.
Thomas.
(This is mostly likely my fault :-( )
All,
Are there any packages that require yum-cron and yum-cron-puias?
They got installed on our PUIAS6 servers and I can't figure out which
other package depended on them being installed.
There's got to be a better way to do this, but I ran:
# rpm -qa | while read i; do rpm -qR $i | grep -q yum-cron && echo $i;
done
It doesn't return any packages other than yum-cron and
yum-cron-puias, so I'm not sure which package required it.
Our kickstart only installs these packages:
puppet
htop
strace
lsof
mailx
nfs-utils
And then relies on puppet to install the rest of the packages. We
aren't installing anything that I can find that would require yum-cron
and yum-cron-puias in our puppet config.
We aren't installing any RPM groups, either, just specifying each
package manually. Is this in some PUIAS base build that I'm missing?
Thanks,
ep
- --
Brian Epstein <beps...@ias.edu> +1 609-734-8179
Manager, Network and Security Institute for Advanced Study
Key fingerprint = 128A 38F4 4CFA 5EDB 99CE 4734 6117 4C25 0371 C12A
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk9s68gACgkQYRdMJQNxwSrhBACgnYDRYnthMsL5JYS+mNVfQIF9
dTIAoJv3DXkXmmgrmTmfOfASOVXIGF/Z
=SRyK
-----END PGP SIGNATURE-----
first of all sorry about the delay. Now as far as
yum-cron/yum-cron-puias you will find that those two are marked as
default in base group of comps file:
/data/puias/6/x86_64/os/PUIAS/repodata/comps-puias6.xml
so unless you add
-yum-cron
-yum-cron-puias
in %packages section of your kickstart file - they will get installed.
Hope this helps,
Josko P.
%packages --nobase
in your kickstart. This is a bit riskier for most applications, so use
with caution! But, this may be exactly what you're looking for, as it
will skip the base group (where these two packages are defined to be
installed) and install only the packages you have explicitly defined
(and their dependencies).
brose
On 03/26/2012 10:19 AM, JP wrote:
> Hi Brian,
>
> first of all sorry about the delay. Now as far as
> yum-cron/yum-cron-puias you will find that those two are marked as
> default in base group of comps file:
>
> /data/puias/6/x86_64/os/PUIAS/repodata/comps-puias6.xml
>
> so unless you add
>
> -yum-cron
> -yum-cron-puias
>
> in %packages section of your kickstart file - they will get installed.
>
> Hope this helps,
>
> Josko P.
>
> On Fri, Mar 23, 2012 at 17:31, Brian Epstein<beps...@ias.edu> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> All,
>>
>> Are there any packages that require yum-cron and yum-cron-puias?
>> They got installed on our PUIAS6 servers and I can't figure out which
>> other package depended on them being installed.
>>
>> There's got to be a better way to do this, but I ran:
>>
>> # rpm -qa | while read i; do rpm -qR $i | grep -q yum-cron&& echo $i;
On 03/26/2012 10:19 AM, JP wrote:
> first of all sorry about the delay. Now as far as
> yum-cron/yum-cron-puias you will find that those two are marked as
> default in base group of comps file:
>
> /data/puias/6/x86_64/os/PUIAS/repodata/comps-puias6.xml
Gotcha. I don't see this in our RHEL6.2 builds. Is it something that
is different in PUIAS6 from RHEL6?
> -yum-cron -yum-cron-puias
>
> in %packages section of your kickstart file - they will get
> installed.
Added it to our %packages section.
Thanks for your help,
ep
- --
Brian Epstein <beps...@ias.edu> +1 609-734-8179
Manager, Network and Security Institute for Advanced Study
Key fingerprint = 128A 38F4 4CFA 5EDB 99CE 4734 6117 4C25 0371 C12A
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk9wuNMACgkQYRdMJQNxwSql8wCgwrrwLqVx4bV4LXvT1QCyE5/4
kjYAnR53LYj8EYJeg83EeCLQOipYc7Ed
=i5jA
-----END PGP SIGNATURE-----
On 03/26/2012 11:54 AM, Benjamin Rose wrote:
> In addition, you can skip the installation of the base group by
> doing
>
> %packages --nobase
>
> in your kickstart. This is a bit riskier for most applications, so
> use with caution! But, this may be exactly what you're looking for,
> as it will skip the base group (where these two packages are
> defined to be installed) and install only the packages you have
> explicitly defined (and their dependencies).
Hey, it's Ben Rose!
Thanks for the suggestion Ben. I think we'll heed on the side of
safety and not include the --nobase option. But it does give me
pause. We haven't actually done an analysis from our RHEL5 or RHEL6
kickstarts to figure out the package differences for our hardened
build, yet.
Looks like we'll do that sooner rather than later.
Thanks for the help, and nice hearing from you,
ep
- --
Brian Epstein <beps...@ias.edu> +1 609-734-8179
Manager, Network and Security Institute for Advanced Study
Key fingerprint = 128A 38F4 4CFA 5EDB 99CE 4734 6117 4C25 0371 C12A
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk9wuVcACgkQYRdMJQNxwSp0TwCggdxgSUO52or2wVLQPjoKDmEe
B9MAnieZQCRXYh2obWieoq+vfQB6PVzb
=x8B3
-----END PGP SIGNATURE-----
Why not just do
yum remove <package>
Yum will prompt you before removing a package, and if there are
dependencies, it will list them, too, when it prompts you to continue.
Prentice