Bug 957994 - build has wrong default confiig setup
Summary: build has wrong default confiig setup
Status: RESOLVED DUPLICATE of bug 953782
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: Development (show other bugs)
Version: Leap 42.1
Hardware: PC openSUSE 42.1
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-04 15:56 UTC by Giacomo Comes
Modified: 2015-12-05 12:37 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Giacomo Comes 2015-12-04 15:56:27 UTC
The package build contains in /usr/lib/build/configs the build configurations for all the current and past suse releases. sl42.1.conf is missing (but a sl13.3.conf is there which I assume should be renamed sl42.1.conf), even worst is that the link default.conf points to sl13.1.conf which is clearly wrong.

I did try to build locally the package build itself but it stops with:
[    5s] expansion error
[    5s]   nothing provides config(filelight) = 15.08.1-1.2 needed by filesystem

I changed the link default.conf to point to sl13.3.conf and restarted build but now the error is:
[    5s] expansion error
[    5s]   nothing provides config(filelight) = 15.08.1-1.2 needed by filesystem
[    5s]   nothing provides liblua5_3

I think we really need an updated sl42.1.conf file in the build package.
Comment 1 Bernhard Wiedemann 2015-12-04 19:45:41 UTC
There is a running update for bug 953782 which you can get from
http://download.opensuse.org/repositories/openSUSE:/Maintenance:/4323/openSUSE_Leap_42.1_Update/noarch/build-20151105-3.1.noarch.rpm

does that help for your problem?
Comment 2 Giacomo Comes 2015-12-04 23:27:19 UTC
Yes, the new update works properly. I have build locally a couple of packages without problem.
Comment 3 Bernhard Wiedemann 2015-12-05 12:37:03 UTC
OK. marking as duplicate then.

*** This bug has been marked as a duplicate of bug 953782 ***