On Mon, May 07, 2007 at 12:59:58PM +0200, Michael Schroeder wrote:
On Mon, May 07, 2007 at 12:51:45PM +0200, Dr. Peter Poeml wrote:
I have a Buildrequires on zlib-devel:
Name: stunnel BuildRequires: openssl openssl-devel zlib-devel %if 0%{?suse_version:1} BuildRequires: tcpd-devel %else BuildRequires: gcc-c++ tcp_wrappers %endif
The buildinfo does swallow the "zlib-devel" somehow:
% osc buildinfo SUSE_Linux_Factory x86_64 | grep zlib <dep>zlib</dep> <bdep name="zlib" preinstall="1" version="1.2.3" release="48" arch="x86_64" project="SUSE:Factory" repository="standard" /> <pdep>zlib</pdep>
This looks like a bug to me.
Dunno, I assume you're talking about the security:Stunnel/stunnel package? The uploaded spec file doesn't contain a zlib-devel BuildRequires, so maybe you're using the wrong variant of 'osc buildinfo'?
Hm, it could be a Monday morning problem (of myself). At least in the above snippet I forgot to send the specfile, and I in fact wasn't aware that my working copy has modifications. Anyway, if I send the specfile (containing the buildrequires on zlib-devel), I also get a buildinfo back which doesn't contain it. Something seems to be wrong therefore. Looking at what travels over HTTP, it looks right (spec is posted). The buildinfo handler is not yet expecting the cpio format we talked about... or is it? Peter -- Allen Gewalten zum Trutz sich erhalten. SUSE LINUX Products GmbH Research & Development