FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Build System

 
 
LinkBack Thread Tools
 
Old 12-08-2007, 10:08 AM
Paul Howarth
 
Default Pathname-based buildreqs not working?

Yesterday I noticed that mock/yum seem to be having trouble finding
pathname-based buildreqs.

For example, buildreqs of /usr/include/tcpd.h and /usr/include/pcap.h
aren't getting found. I use these to maintain spec compatibility across
various releases, where these files can be found in either tcp_wrappers
or tcp_wrappers-devel, or libpcap or libpcap-devel packages
respectively.

I've tried upgrading to mock 0.8.15 from CVS (F-8 branch) and it hasn't
helped.

Is this intentional behaviour (not getting/reading the filelists
metadata) for speed purposes?

Paul.

--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
 
Old 12-08-2007, 10:29 AM
Jos Vos
 
Default Pathname-based buildreqs not working?

On Sat, Dec 08, 2007 at 11:08:02AM +0000, Paul Howarth wrote:

> Yesterday I noticed that mock/yum seem to be having trouble finding
> pathname-based buildreqs.

I had this problem with RHEL5, mock 0.7.4 and yum 3.0.x, but not
with yum 3.2.x. Is this maybe a yum problem? Did you directly
query yum to search for these files as a test?

--
-- Jos Vos <jos@xos.nl>
-- X/OS Experts in Open Systems BV | Phone: +31 20 6938364
-- Amsterdam, The Netherlands | Fax: +31 20 6948204

--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
 
Old 12-08-2007, 02:03 PM
Paul Howarth
 
Default Pathname-based buildreqs not working?

On Sat, 8 Dec 2007 12:29:07 +0100
Jos Vos <jos@xos.nl> wrote:

> On Sat, Dec 08, 2007 at 11:08:02AM +0000, Paul Howarth wrote:
>
> > Yesterday I noticed that mock/yum seem to be having trouble finding
> > pathname-based buildreqs.
>
> I had this problem with RHEL5, mock 0.7.4 and yum 3.0.x, but not
> with yum 3.2.x. Is this maybe a yum problem? Did you directly
> query yum to search for these files as a test?

Worked fine:

# yum install /usr/include/pcap.h
Setting up Install Process
Parsing package install arguments
Importing additional filelist information
filelists.sqlite.bz2 100% |=========================| 70 kB
00:00 filelists.sqlite.bz2 100% |=========================| 94
kB 00:00 filelists.sqlite.bz2 100% |=========================|
1.8 MB 00:13 filelists.sqlite.bz2 100%
|=========================| 762 kB 00:00 Resolving Dependencies
--> Running transaction check
---> Package libpcap-devel.x86_64 14:0.9.7-3.fc8 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

================================================== ===========================
Package Arch Version Repository
Size
================================================== ===========================
Installing: libpcap-devel x86_64 14:0.9.7-3.fc8
fedora 28 k

Transaction Summary
================================================== ===========================
Install 1 Package(s)
Update 0 Package(s)
Remove 0 Package(s)

Total download size: 28 k
Is this ok [y/N]: n
Exiting on user Command
Complete!
# rpm -q yum
yum-3.2.7-2.fc8

I noticed though that in the failed mock run, the yum_cache for the
target didn't include the filelists metadata...

Paul.

--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
 
Old 12-10-2007, 10:52 AM
Paul Howarth
 
Default Pathname-based buildreqs not working?

Jos Vos wrote:

On Sat, Dec 08, 2007 at 11:08:02AM +0000, Paul Howarth wrote:


Yesterday I noticed that mock/yum seem to be having trouble finding
pathname-based buildreqs.


I had this problem with RHEL5, mock 0.7.4 and yum 3.0.x, but not
with yum 3.2.x. Is this maybe a yum problem? Did you directly
query yum to search for these files as a test?


Looking at the code in mock, it appears to use this command:

yum --installroot=/var/lib/mock/fedora-devel-i386/root resolvedep
<list-of-buildreqs>


But even that works when run manually:
# yum --installroot=/var/lib/mock/fedora-devel-i386/root resolvedep
openssl-devel /usr/include/tcpd.h openldap-devel

Yum Version: 3.2.8
COMMAND: yum --installroot=/var/lib/mock/fedora-devel-i386/root
resolvedep openssl-devel /usr/include/tcpd.h openldap-devel

Installroot: /var/lib/mock/fedora-devel-i386/root
Ext Commands:

openssl-devel
/usr/include/tcpd.h
openldap-devel
Reading Local RPMDB
Setting up Package Sacks
kludge 100% |=========================| 951 B
00:00
primary.xml.gz 100% |=========================| 199 B
00:00
city-fan.org 100% |=========================| 1.9 kB
00:00
primary.sqlite.bz2 100% |=========================| 86 kB
00:00
fedora 100% |=========================| 2.1 kB
00:00
primary.sqlite.bz2 100% |=========================| 5.5 MB
00:00

Searching pkgSack for dep: openssl-devel
skipping reposetup, pkgsack exists
Potential match for openssl-devel from openssl-devel - 0.9.8g-2.fc9.i386
Matched openssl-devel - 0.9.8g-2.fc9.i386 to require for openssl-devel
0penssl-devel-0.9.8g-2.fc9.i386
Searching pkgSack for dep: /usr/include/tcpd.h
skipping reposetup, pkgsack exists
Importing additional filelist information
filelists.xml.gz 100% |=========================| 192 B
00:00
filelists.sqlite.bz2 100% |=========================| 93 kB
00:00
filelists.sqlite.bz2 100% |=========================| 9.2 MB
00:00

skipping reposetup, pkgsack exists
Potential match for /usr/include/tcpd.h from tcp_wrappers-devel -
7.6-50.fc8.i386

0:tcp_wrappers-devel-7.6-50.fc8.i386
Searching pkgSack for dep: openldap-devel
skipping reposetup, pkgsack exists
Potential match for openldap-devel from openldap-devel - 2.4.6-1.fc9.i386
Matched openldap-devel - 2.4.6-1.fc9.i386 to require for openldap-devel
0penldap-devel-2.4.6-1.fc9.i386

It's really strange that this doesn't work from within mock.

Paul.

--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
 
Old 12-10-2007, 10:13 PM
Michael E Brown
 
Default Pathname-based buildreqs not working?

On Mon, Dec 10, 2007 at 11:52:04AM +0000, Paul Howarth wrote:
> Jos Vos wrote:
> >On Sat, Dec 08, 2007 at 11:08:02AM +0000, Paul Howarth wrote:
> >
> >>Yesterday I noticed that mock/yum seem to be having trouble finding
> >>pathname-based buildreqs.
> >
> >I had this problem with RHEL5, mock 0.7.4 and yum 3.0.x, but not
> >with yum 3.2.x. Is this maybe a yum problem? Did you directly
> >query yum to search for these files as a test?
>
> Looking at the code in mock, it appears to use this command:
>
> yum --installroot=/var/lib/mock/fedora-devel-i386/root resolvedep
> <list-of-buildreqs>

Can you look in the root.log for this resolvedep command and check out
what is going on?

There isnt anything specifically in mock to disallow this. It should
work, afaict.

Send a pastebin link to the root.log, if possible, or a URL to an SRPM
with this problem.
--
Michael

--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
 
Old 12-10-2007, 11:37 PM
Paul Howarth
 
Default Pathname-based buildreqs not working?

On Mon, 10 Dec 2007 17:13:38 -0600
Michael E Brown <Michael_E_Brown@dell.com> wrote:

> On Mon, Dec 10, 2007 at 11:52:04AM +0000, Paul Howarth wrote:
> > Jos Vos wrote:
> > >On Sat, Dec 08, 2007 at 11:08:02AM +0000, Paul Howarth wrote:
> > >
> > >>Yesterday I noticed that mock/yum seem to be having trouble
> > >>finding pathname-based buildreqs.
> > >
> > >I had this problem with RHEL5, mock 0.7.4 and yum 3.0.x, but not
> > >with yum 3.2.x. Is this maybe a yum problem? Did you directly
> > >query yum to search for these files as a test?
> >
> > Looking at the code in mock, it appears to use this command:
> >
> > yum --installroot=/var/lib/mock/fedora-devel-i386/root resolvedep
> > <list-of-buildreqs>
>
> Can you look in the root.log for this resolvedep command and check out
> what is going on?
>
> There isnt anything specifically in mock to disallow this. It should
> work, afaict.
>
> Send a pastebin link to the root.log, if possible, or a URL to an SRPM
> with this problem.

Root log: http://www.city-fan.org/~paul/ntop-3.3-2.fc8.CF-root.log

SRPM: http://www.city-fan.org/~paul/ntop-3.3-2.fc8.CF.src.rpm

Cheers, Paul.

--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
 
Old 12-11-2007, 05:16 PM
Michael E Brown
 
Default Pathname-based buildreqs not working?

On Tue, Dec 11, 2007 at 12:37:24AM +0000, Paul Howarth wrote:
> On Mon, 10 Dec 2007 17:13:38 -0600
> Michael E Brown <Michael_E_Brown@dell.com> wrote:
> > Can you look in the root.log for this resolvedep command and check out
> > what is going on?
> >
> > There isnt anything specifically in mock to disallow this. It should
> > work, afaict.
> >
> > Send a pastebin link to the root.log, if possible, or a URL to an SRPM
> > with this problem.
>
> Root log: http://www.city-fan.org/~paul/ntop-3.3-2.fc8.CF-root.log
>
> SRPM: http://www.city-fan.org/~paul/ntop-3.3-2.fc8.CF.src.rpm

Paul,
First, you enabled yum debugging. How did you do that, in the yum
config file? This may throw off mock because atm mock parses stdout
from yum. (this isnt the case here, though, just pointing it out, also
want to know how you did it for my own debugging purposes later.

Next:

$ yum resolvedep ccache mysql-devel pcre-devel groff gd-devel
net-snmp-devel pkgconfig openssl-devel automake lm_sensors-devel
rrdtool-devel >= 1.2.0 libtool /usr/include/tcpd.h /usr/include/pcap.h
autoconf gdbm-devel
No Package Found for 1.2.0
No Package Found for /usr/include/tcpd.h
No Package Found for /usr/include/pcap.h

I get the exact same error here on my F-8 box that you are getting. Yum
problem?

Need some input from yum folks.
--
Michael

--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
 
Old 12-11-2007, 05:24 PM
Paul Howarth
 
Default Pathname-based buildreqs not working?

Michael E Brown wrote:

Paul,
First, you enabled yum debugging. How did you do that, in the yum
config file? This may throw off mock because atm mock parses stdout
from yum. (this isnt the case here, though, just pointing it out, also
want to know how you did it for my own debugging purposes later.


debuglevel=10 in the yum.conf part of the mock config.


Next:

$ yum resolvedep ccache mysql-devel pcre-devel groff gd-devel
net-snmp-devel pkgconfig openssl-devel automake lm_sensors-devel
rrdtool-devel >= 1.2.0 libtool /usr/include/tcpd.h /usr/include/pcap.h
autoconf gdbm-devel
No Package Found for 1.2.0


Perhaps this one is a quoting issue; it should be looking for
"rrdtool-devel >= 1.2.0" rather than "rrdtool-devel" ">=" "1.2.0"?



No Package Found for /usr/include/tcpd.h
No Package Found for /usr/include/pcap.h


These are the ones I've been having trouble with.


I get the exact same error here on my F-8 box that you are getting. Yum
problem?

Need some input from yum folks.


Ah good, it's not just me then.

Paul.

--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
 
Old 12-11-2007, 05:31 PM
seth vidal
 
Default Pathname-based buildreqs not working?

On Tue, 2007-12-11 at 18:24 +0000, Paul Howarth wrote:
> Michael E Brown wrote:
> > Paul,
> > First, you enabled yum debugging. How did you do that, in the yum
> > config file? This may throw off mock because atm mock parses stdout
> > from yum. (this isnt the case here, though, just pointing it out, also
> > want to know how you did it for my own debugging purposes later.
>
> debuglevel=10 in the yum.conf part of the mock config.
>
> > Next:
> >
> > $ yum resolvedep ccache mysql-devel pcre-devel groff gd-devel
> > net-snmp-devel pkgconfig openssl-devel automake lm_sensors-devel
> > rrdtool-devel >= 1.2.0 libtool /usr/include/tcpd.h /usr/include/pcap.h
> > autoconf gdbm-devel
> > No Package Found for 1.2.0
>
> Perhaps this one is a quoting issue; it should be looking for
> "rrdtool-devel >= 1.2.0" rather than "rrdtool-devel" ">=" "1.2.0"?
>
> > No Package Found for /usr/include/tcpd.h
> > No Package Found for /usr/include/pcap.h
>
> These are the ones I've been having trouble with.
>
> > I get the exact same error here on my F-8 box that you are getting. Yum
> > problem?
> >
> > Need some input from yum folks.
>
> Ah good, it's not just me then.
>

yum resolvedep /usr/include/tcpd.h works for me on f8 with 3.2.8 and
3.2.7 - confirmed with other folks on irc, too.
-sv


--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
 
Old 12-11-2007, 05:58 PM
Paul Howarth
 
Default Pathname-based buildreqs not working?

seth vidal wrote:

On Tue, 2007-12-11 at 18:24 +0000, Paul Howarth wrote:

Michael E Brown wrote:

Paul,
First, you enabled yum debugging. How did you do that, in the yum
config file? This may throw off mock because atm mock parses stdout
from yum. (this isnt the case here, though, just pointing it out, also
want to know how you did it for my own debugging purposes later.

debuglevel=10 in the yum.conf part of the mock config.


Next:

$ yum resolvedep ccache mysql-devel pcre-devel groff gd-devel
net-snmp-devel pkgconfig openssl-devel automake lm_sensors-devel
rrdtool-devel >= 1.2.0 libtool /usr/include/tcpd.h /usr/include/pcap.h
autoconf gdbm-devel
No Package Found for 1.2.0
Perhaps this one is a quoting issue; it should be looking for
"rrdtool-devel >= 1.2.0" rather than "rrdtool-devel" ">=" "1.2.0"?



No Package Found for /usr/include/tcpd.h
No Package Found for /usr/include/pcap.h

These are the ones I've been having trouble with.


I get the exact same error here on my F-8 box that you are getting. Yum
problem?

Need some input from yum folks.

Ah good, it's not just me then.



yum resolvedep /usr/include/tcpd.h works for me on f8 with 3.2.8 and
3.2.7 - confirmed with other folks on irc, too.


It works for me too from the command line, but not from within mock.

Paul.

--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
 

Thread Tools




All times are GMT. The time now is 10:16 AM.

VBulletin, Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org