On Thu, Nov 21, 2013 at 10:30 AM, Greg KH wrote:

On Wed, Nov 20, 2013 at 02:06:22PM -0500, Greg Freemyer wrote:

...

I have several packages in security that just started failing for the tumbleweed repo, but they are building fine against 13.1

One example is libpff: https://build.opensuse.org/package/show/security/libpff

The build log concludes with: ==== [ 52s] + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --nosignature --define '_build_create_debug 1' --define 'disturl obs://build.opensuse.org/security/openSUSE_Tumbleweed/a69d3b9f16bf88cb09e4f67eadec27ad-libpff' /home/abuild/rpmbuild/SOURCES/libpff.spec [ 52s] error: Failed build dependencies: [ 52s] pkgconfig(libcsplit) >= 20130609 is needed by libpff-0~20130722-6.2.i586 [ 52s] pkgconfig(libcfile) >= 20130609 is needed by libpff-0~20130722-6.2.i586 [ 52s] pkgconfig(libcpath) >= 20130609 is needed by libpff-0~20130722-6.2.i586 [ 52s] pkgconfig(libclocale) >= 20130609 is needed by libpff-0~20130722-6.2.i586 [ 52s] pkgconfig(libbfio) >= 20130721 is needed by libpff-0~20130722-6.2.i586 [ 54s] /.build/build: line 373: 213 Killed background_monitor_process [ 56s] [ 38.418151] SysRq : Power Off [ 57s] [ 38.564151] Power down. [ 58s] ===

Those libraries are in 13.1, so they should be in Tumbleweed? Why the failures?

Is this still happening? Tumbleweed should be based on 13.1 now, so it "should" work, unless I've messed something up?

greg k-h

Greg, First, this is a low priority for me. I can just disable the tumbleweed repo for builds and no one will complain. === details I just triggered a rebuild of libewf inside the security repo: https://build.opensuse.org/package/show/security/libewf It still fails tumbleweed builds with: [ 39s] error: Failed build dependencies: [ 39s] pkgconfig(libcnotify) >= 20120425 is needed by libewf-0~20130416-24.2.x86_64 [ 39s] pkgconfig(libcpath) >= 20120701 is needed by libewf-0~20130416-24.2.x86_64 [ 39s] pkgconfig(libcsplit) >= 20120701 is needed by libewf-0~20130416-24.2.x86_64 I have this in the specfile, but I don't see why it would be a problem for tumbleweed: BuildRequires: pkgconfig(libcaes) >= 20120425 %if 0%{?suse_version} > 1230 BuildRequires: pkgconfig(libcnotify) >= 20120425 BuildRequires: pkgconfig(libcpath) >= 20120701 BuildRequires: pkgconfig(libcsplit) >= 20120701 %endif The above works fine for 13.1 and factory since the suse version for both is greater than 12.3 and packages at or above those version numbers are available. I assume tumbleweed sets "suse_version" to 1310? One potential weirdness is that BuildRequres packages are actually versioned as 0~20130609 etc. I've found that for normal OBS builds I have to leave off the 0~ in the BuildRequires line. Even in tumbleweed it seems to work fine for libcaes above, so why is it failing for libcnotify, libcpath, and libcsplit? FYI: I have 3 other packages in the security repo (libpff, libhmac, libolecf) that are also failing for the same basic reason, so I don't think it is a package config issue, but it maybe something with how the security repo as a project is setup. Greg -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org