Re: yum repos in chroot

Enslaver <[email protected]>
Newsgroups gmane.linux.redhat.k12osn
Message-ID <CAEk3EHC8xonNhL=mOQZo0gFbJBkeiWgMePOQhoc4z6yVAjY55g@mail.gmail.com>
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
On Jun 11, 2013 3:49 PM, "Barry R Cisna" <[email protected]> wrote:

> 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
> [email protected]
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>
>

_______________________________________________
K12OSN mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.