Discussion:
yum repos in chroot
Barry R Cisna
2013-06-11 19:45:50 UTC
Permalink
Hello All,

ltsp-server-5.4.5 (latest ltsp iteration)

Have an odd one.
Have added the adobe, repoforge and rpmfusion repos to the client chroot
via the usual chrooting process,,and used the rpm install for each.
Looking in /opt/ltsp/i386/etc/yum.repos.d they are in fact there. They
are both enabled and permissions look correct.

When I try and add a package that either of these repos provide i always
get "Nothing to do".message. If i try and add a package from the default
repos that come with ltsp-server-x.x.x the add works as expected. So it
is not a proxy hang up.I even disabled gpgcheck,,and that made no
difference. It is as though the new repos are not being read?

I tried running with the -v switch with yum and simply says 'not
available'.
The verbosity when yumming from the client chroot is very minimal ,looks
much different than a conventional linux yum process for some reason.
Of course have rebooted just to say i did do it.
I done a Meld compare on server and client chroot repo.repo files and
all are identical for completeness.
This seems 'too simple'?...:)
Anyone have this happen?

Thanks,
Barry
Enslaver
2013-06-11 20:27:35 UTC
Permalink
Hello barry. The way mock sets up the yum.conf doesnt support the repos.d
style. To fix this, over write the yum.conf in /etc with the one from
/etc/yum inside the chroot
Post by Barry R Cisna
Hello All,
ltsp-server-5.4.5 (latest ltsp iteration)
Have an odd one.
Have added the adobe, repoforge and rpmfusion repos to the client chroot
via the usual chrooting process,,and used the rpm install for each.
Looking in /opt/ltsp/i386/etc/yum.repos.d they are in fact there. They
are both enabled and permissions look correct.
When I try and add a package that either of these repos provide i always
get "Nothing to do".message. If i try and add a package from the default
repos that come with ltsp-server-x.x.x the add works as expected. So it
is not a proxy hang up.I even disabled gpgcheck,,and that made no
difference. It is as though the new repos are not being read?
I tried running with the -v switch with yum and simply says 'not
available'.
The verbosity when yumming from the client chroot is very minimal ,looks
much different than a conventional linux yum process for some reason.
Of course have rebooted just to say i did do it.
I done a Meld compare on server and client chroot repo.repo files and
all are identical for completeness.
This seems 'too simple'?...:)
Anyone have this happen?
Thanks,
Barry
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>
Barry Cisna
2013-06-12 12:45:09 UTC
Permalink
Hello All,

Copied yum.conf.rpmnew from chroot/ ,,to /opt/ltsp/i386/etc/yum,,,
renamed to yum.conf ,,yum recogonizes added repos now.

Thank You,
Barry

Loading...