There are several independent discussions about it. As one mentioned fontconfig I looked at M17. Well, indeed
https://build.opensuse.org/package/binaries/M17N/fontconfig?repository=openS...:
::import::i586::fontconfig-32bit-2.12.0-153.1.x86_64.rpm ::import::i586::fontconfig-devel-32bit-2.12.0-153.1.x86_64.rpm _buildenv fontconfig-2.12.1-155.2.src.rpm fontconfig-2.12.1-155.2.x86_64.rpm fontconfig-devel-2.12.1-155.2.x86_64.rpm
https://build.opensuse.org/package/binaries/M17N/fontconfig?repository=openS...
_buildenv fontconfig-2.12.1-155.3.src.rpm fontconfig-2.12.1-155.3.x86_64.rpm fontconfig-devel-2.12.1-155.3.x86_64.rpm
This is the same package having the same baslibs.conf. What's the difference? Note that in Leap 42.2 itself those packages *are* built.
On 08.01.2017 19:01, Andrei Borzenkov wrote:
There are several independent discussions about it. As one mentioned fontconfig I looked at M17. Well, indeed
https://build.opensuse.org/package/binaries/M17N/fontconfig?repository=openS...:
::import::i586::fontconfig-32bit-2.12.0-153.1.x86_64.rpm ::import::i586::fontconfig-devel-32bit-2.12.0-153.1.x86_64.rpm _buildenv fontconfig-2.12.1-155.2.src.rpm fontconfig-2.12.1-155.2.x86_64.rpm fontconfig-devel-2.12.1-155.2.x86_64.rpm
https://build.opensuse.org/package/binaries/M17N/fontconfig?repository=openS...
_buildenv fontconfig-2.12.1-155.3.src.rpm fontconfig-2.12.1-155.3.x86_64.rpm fontconfig-devel-2.12.1-155.3.x86_64.rpm
This is the same package having the same baslibs.conf. What's the difference? Note that in Leap 42.2 itself those packages *are* built.
Well you have to enable building for i586 Leap if you want baselibs.conf to have some effect (note that it was enabled for Leap 42.1 in past, thus import succeeded, but as i586 build target was removed old version of 32bit fontconfig is present (2.12.0-153.1 vs 2.12.1-155.2)).
Hope this answers your question.
Martin
Am 08.01.2017 um 19:01 schrieb Andrei Borzenkov:
There are several independent discussions about it. As one mentioned fontconfig I looked at M17. Well, indeed
This is the same package having the same baslibs.conf. What's the difference? Note that in Leap 42.2 itself those packages *are* built.
hmm, I never found out how to get i586 baselibs packages _at all_ within OBS repositories for Leap. I think no single of my packages get baselib packages even if they are built and delivered correctly from the official Leap repositories.
So what is the magic to get baselibs packages in arbitrary OBS projects?
Wolfgang
On Sunday 2017-01-08 19:15, Wolfgang Rosenauer wrote:
Am 08.01.2017 um 19:01 schrieb Andrei Borzenkov:
There are several independent discussions about it. As one mentioned fontconfig I looked at M17. Well, indeed
This is the same package having the same baslibs.conf. What's the difference? Note that in Leap 42.2 itself those packages *are* built.
hmm, I never found out how to get i586 baselibs packages _at all_ within OBS repositories for Leap.
i586 baselibs are, of course, built by a i586 worker. If you do not have i586 in `osc meta prj`, you won't get em obviously.
08.01.2017 21:18, Jan Engelhardt пишет:
On Sunday 2017-01-08 19:15, Wolfgang Rosenauer wrote:
Am 08.01.2017 um 19:01 schrieb Andrei Borzenkov:
There are several independent discussions about it. As one mentioned fontconfig I looked at M17. Well, indeed
This is the same package having the same baslibs.conf. What's the difference? Note that in Leap 42.2 itself those packages *are* built.
hmm, I never found out how to get i586 baselibs packages _at all_ within OBS repositories for Leap.
i586 baselibs are, of course, built by a i586 worker. If you do not have i586 in `osc meta prj`, you won't get em obviously.
So could you explain to us, uninitiated, how to add it? And also explain why it is built for 42.1 and not built for 42.2 while both have
<repository name="openSUSE_Leap_42.2"> <path project="openSUSE:Leap:42.2" repository="standard"/> <arch>x86_64</arch> </repository> <repository name="openSUSE_Leap_42.1"> <path project="openSUSE:Leap:42.1" repository="standard"/> <arch>x86_64</arch> </repository>
and nothing more specific configuration (osc meta prj M17N)?
08.01.2017 21:12, Martin Pluskal пишет:
Well you have to enable building for i586 Leap if you want baselibs.conf to have some effect (note that it was enabled for Leap 42.1 in past, thus import succeeded, but as i586 build target was removed old version of 32bit fontconfig is present (2.12.0-153.1 vs 2.12.1-155.2)).
Yes, I missed that versions are different. Does it mean adding <arch>i586</arch> explicitly?
On 08.01.2017 19:23, Andrei Borzenkov wrote:
08.01.2017 21:12, Martin Pluskal пишет:
Well you have to enable building for i586 Leap if you want baselibs.conf to have some effect (note that it was enabled for Leap 42.1 in past, thus import succeeded, but as i586 build target was removed old version of 32bit fontconfig is present (2.12.0-153.1 vs 2.12.1-155.2)).
Yes, I missed that versions are different. Does it mean adding <arch>i586</arch> explicitly?
yep
On Sun, Jan 08, 2017 at 09:21:01PM +0300, Andrei Borzenkov wrote:
08.01.2017 21:18, Jan Engelhardt пишет:
On Sunday 2017-01-08 19:15, Wolfgang Rosenauer wrote:
Am 08.01.2017 um 19:01 schrieb Andrei Borzenkov:
There are several independent discussions about it. As one mentioned fontconfig I looked at M17. Well, indeed
This is the same package having the same baslibs.conf. What's the difference? Note that in Leap 42.2 itself those packages *are* built.
hmm, I never found out how to get i586 baselibs packages _at all_ within OBS repositories for Leap.
i586 baselibs are, of course, built by a i586 worker. If you do not have i586 in `osc meta prj`, you won't get em obviously.
So could you explain to us, uninitiated, how to add it? And also explain why it is built for 42.1 and not built for 42.2 while both have
<repository name="openSUSE_Leap_42.2"> <path project="openSUSE:Leap:42.2" repository="standard"/> <arch>x86_64</arch>
insert: <arch>i586</arch> here
</repository> <repository name="openSUSE_Leap_42.1"> <path project="openSUSE:Leap:42.1" repository="standard"/> <arch>x86_64</arch>
insert: <arch>i586</arch> here
</repository>
and nothing more specific configuration (osc meta prj M17N)?
Ciao, Marcus