On Wed, Sep 18, 2013 at 12:27:07PM -0500, Alexander Graf wrote:

Am 18.09.2013 um 06:48 schrieb Guillaume Gardet :

...

Hi,

raspberrypi-gfx and mesa provide openGL ES libs and devel files. So, there are file conflicts. Should we add a "Conflicts:" line in raspberrypi-gfx spec file?

Or is there a better way to avoid problems?

Let's ask someone with a clue :). Stefan, do you have any ideas here?

Where can I find the sources for the raspberrypi-gfx package? Stefan Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany -------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -------------------------------------------------------------- -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Le 19/09/2013 15:28, Guillaume Gardet a écrit :

Le 19/09/2013 15:21, Stefan Dirsch a écrit :

...

On Wed, Sep 18, 2013 at 12:27:07PM -0500, Alexander Graf wrote:

...

Am 18.09.2013 um 06:48 schrieb Guillaume Gardet :

...

Hi,

raspberrypi-gfx and mesa provide openGL ES libs and devel files. So, there are file conflicts. Should we add a "Conflicts:" line in raspberrypi-gfx spec file?

Or is there a better way to avoid problems? Let's ask someone with a clue :). Stefan, do you have any ideas here?

ping Guillaume

...

Where can I find the sources for the raspberrypi-gfx package? In raspberrypi-firmware package since it is the same sources.

I think we should split raspberrypi-gfx in subpackages (*-libGLESv2, *-libEGL, etc.) as in Mesa.

Guillaume

...

Stefan

Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany -------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) --------------------------------------------------------------

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Le 10/10/2013 14:03, Stefan Dirsch a écrit :

On Wed, Oct 09, 2013 at 04:43:59PM +0200, Guillaume Gardet wrote:

...

...

Le 19/09/2013 15:21, Stefan Dirsch a écrit :

...

On Wed, Sep 18, 2013 at 12:27:07PM -0500, Alexander Graf wrote:

...

Am 18.09.2013 um 06:48 schrieb Guillaume Gardet :

...

Hi,

raspberrypi-gfx and mesa provide openGL ES libs and devel files. So, there are file conflicts. Should we add a "Conflicts:" line in raspberrypi-gfx spec file?

Or is there a better way to avoid problems? Let's ask someone with a clue :). Stefan, do you have any ideas here?

Le 19/09/2013 15:28, Guillaume Gardet a écrit : ping Guillaume

...

...

Where can I find the sources for the raspberrypi-gfx package? In raspberrypi-firmware package since it is the same sources.

I think we should split raspberrypi-gfx in subpackages (*-libGLESv2, *-libEGL, etc.) as in Mesa. I didn't receive this reply. Most likely, because it has only been addressed to the ML, which I'm not subscribed to.

But, yes. Splitting the package up like it is done in Mesa would be the first step. BTW, I still can't find that package anywhere. Apparently it isn't on the openSUSE buildservice.

You can find it here and there for Factory and 13.1 : https://build.opensuse.org/package/show/devel:ARM:Factory:Contrib:RaspberryP... https://build.opensuse.org/package/show/devel:ARM:13.1:Contrib:RaspberryPi/r... Guillaume

Thanks, Stefan

Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany -------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) --------------------------------------------------------------

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Le 17/10/2013 11:51, Stefan Dirsch a écrit :

On Thu, Oct 10, 2013 at 03:24:39PM +0200, Guillaume Gardet wrote:

...

Le 10/10/2013 14:03, Stefan Dirsch a écrit :

...

On Wed, Oct 09, 2013 at 04:43:59PM +0200, Guillaume Gardet wrote:

...

...

Le 19/09/2013 15:21, Stefan Dirsch a écrit :

...

On Wed, Sep 18, 2013 at 12:27:07PM -0500, Alexander Graf wrote: > Am 18.09.2013 um 06:48 schrieb Guillaume Gardet : > >> Hi, >> >> raspberrypi-gfx and mesa provide openGL ES libs and devel files. So, there are file conflicts. Should we add a "Conflicts:" line in raspberrypi-gfx spec file? >> >> Or is there a better way to avoid problems? > Let's ask someone with a clue :). Stefan, do you have any ideas here?

Le 19/09/2013 15:28, Guillaume Gardet a écrit : ping Guillaume

...

...

Where can I find the sources for the raspberrypi-gfx package? In raspberrypi-firmware package since it is the same sources.

I think we should split raspberrypi-gfx in subpackages (*-libGLESv2, *-libEGL, etc.) as in Mesa. I didn't receive this reply. Most likely, because it has only been addressed to the ML, which I'm not subscribed to.

But, yes. Splitting the package up like it is done in Mesa would be the first step. BTW, I still can't find that package anywhere. Apparently it isn't on the openSUSE buildservice. You can find it here and there for Factory and 13.1 : https://build.opensuse.org/package/show/devel:ARM:Factory:Contrib:RaspberryP... https://build.opensuse.org/package/show/devel:ARM:13.1:Contrib:RaspberryPi/r... Thanks!

Did you have some time to have a look at it? Guillaume

Stefan

Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany -------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) --------------------------------------------------------------

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Le 29/10/2013 15:48, Stefan Dirsch a écrit :

...

Le 17/10/2013 11:51, Stefan Dirsch a écrit :

...

On Thu, Oct 10, 2013 at 03:24:39PM +0200, Guillaume Gardet wrote:

...

Le 10/10/2013 14:03, Stefan Dirsch a écrit :

...

On Wed, Oct 09, 2013 at 04:43:59PM +0200, Guillaume Gardet wrote:

...

Le 19/09/2013 15:28, Guillaume Gardet a écrit : > Le 19/09/2013 15:21, Stefan Dirsch a écrit : >> On Wed, Sep 18, 2013 at 12:27:07PM -0500, Alexander Graf wrote: >>> Am 18.09.2013 um 06:48 schrieb Guillaume Gardet : >>> >>>> Hi, >>>> >>>> raspberrypi-gfx and mesa provide openGL ES libs and devel files. So, there are file conflicts. Should we add a "Conflicts:" line in raspberrypi-gfx spec file? >>>> >>>> Or is there a better way to avoid problems? >>> Let's ask someone with a clue :). Stefan, do you have any ideas here? ping Guillaume

>> Where can I find the sources for the raspberrypi-gfx package? > In raspberrypi-firmware package since it is the same sources. > > I think we should split raspberrypi-gfx in subpackages (*-libGLESv2, *-libEGL, etc.) as in Mesa. I didn't receive this reply. Most likely, because it has only been addressed to the ML, which I'm not subscribed to.

But, yes. Splitting the package up like it is done in Mesa would be the first step. BTW, I still can't find that package anywhere. Apparently it isn't on the openSUSE buildservice. You can find it here and there for Factory and 13.1 : https://build.opensuse.org/package/show/devel:ARM:Factory:Contrib:RaspberryP... https://build.opensuse.org/package/show/devel:ARM:13.1:Contrib:RaspberryPi/r... Thanks! Did you have some time to have a look at it? Not at all. I won't before my vacation either. But why do I need? Just make sure you have some special package selection for the raspberrypi distribution (no idea how this is handled though) and let the raspberrypi packages

On Tue, Oct 29, 2013 at 03:40:09PM +0100, Guillaume Gardet wrote: provide/obsolete the appropriate Mesa packages, so you don't have conflicts.

Ok. This is where I am not sure how to handle it correctly. How should I use "provide" and/or "obsolete" here? Is there any other package which provides same libs as Mesa, so that I take it as a template? Or any other packages providing libraries with the same names. Something like: Provides: Mesa-libGLESv2 is enough to not have install/deps conflicts? Should I add: Obsoletes: Mesa-libGLESv2 ? Is there any problem to provide and obsolete the same package? Guillaume

I hope there won't be any changes needed for Mesa packaging.

Thanks, Stefan

Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany -------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) --------------------------------------------------------------

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Le 29/10/2013 16:35, Stefan Dirsch a écrit :

On Tue, Oct 29, 2013 at 04:04:26PM +0100, Guillaume Gardet wrote:

...

Ok. This is where I am not sure how to handle it correctly. How should I use "provide" and/or "obsolete" here? Is there any other package which provides same libs as Mesa, so that I take it as a template? Or any other packages providing libraries with the same names.

Something like: Provides: Mesa-libGLESv2 is enough to not have install/deps conflicts?

Should I add: Obsoletes: Mesa-libGLESv2 ? Is there any problem to provide and obsolete the same package? No, just use both, i.e.

Provides: Mesa-libGLESv2 Obsoletes: Mesa-libGLESv2

Ok, I will try that. Thanks. Guillaume

Thanks, Stefan

Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany -------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) --------------------------------------------------------------

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On Tue, Oct 29, 2013 at 07:57:25PM +0100, Guillaume Gardet wrote:

Le 29/10/2013 16:37, Guillaume Gardet a écrit :

...

Le 29/10/2013 16:35, Stefan Dirsch a écrit :

...

On Tue, Oct 29, 2013 at 04:04:26PM +0100, Guillaume Gardet wrote:

...

Ok. This is where I am not sure how to handle it correctly. How should I use "provide" and/or "obsolete" here? Is there any other package which provides same libs as Mesa, so that I take it as a template? Or any other packages providing libraries with the same names.

Something like: Provides: Mesa-libGLESv2 is enough to not have install/deps conflicts?

Should I add: Obsoletes: Mesa-libGLESv2 ? Is there any problem to provide and obsolete the same package? No, just use both, i.e.

Provides: Mesa-libGLESv2 Obsoletes: Mesa-libGLESv2

Now, for a package, I have this error: conflict for provider of libEGL.so.1 needed by Mesa, (provider Mesa-libEGL1 is obsoleted by installed raspberrypi-gfx), conflict for provider of libEGL.so.1 needed by libcairo2, (provider Mesa-libEGL1 is obsoleted by installed raspberrypi-gfx).

Any idea how to solve that?

# rpm -qplv raspberrypi-gfx-2013.10.18-1.1.armv6hl.rpm|grep -i -e egl -e gles -rw-r--r-- 1 root root 202534 Okt 29 19:19 /usr/lib/libEGL.so lrwxrwxrwx 1 root root 9 Okt 29 19:19 /usr/lib/libEGL.so.1 -> libEGL.so -rw-r--r-- 2 root root 104606 Okt 29 19:19 /usr/lib/libGLESv1_CM.so lrwxrwxrwx 1 root root 15 Okt 29 19:19 /usr/lib/libGLESv1_CM.so.1 -> libGLESv1_CM.so -rw-r--r-- 2 root root 104606 Okt 29 19:19 /usr/lib/libGLESv2.so lrwxrwxrwx 1 root root 12 Okt 29 19:19 /usr/lib/libGLESv2.so.2 -> libGLESv2.so This looks broken to me. In case you can't fix that (binary only crap I guess) try to provide the lib itself. Provides: libEGL.so.1 Provides: libGLESv1_CM.so.1 Provides: libGLESv2.so.2 Hope this helps somewhat. Thanks, Stefan Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany -------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -------------------------------------------------------------- -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Le 30/10/2013 09:30, Stefan Seyfried a écrit :

Am 29.10.2013 15:40, schrieb Guillaume Gardet:

...

...

...

You can find it here and there for Factory and 13.1 : https://build.opensuse.org/package/show/devel:ARM:Factory:Contrib:RaspberryP... https://build.opensuse.org/package/show/devel:ARM:13.1:Contrib:RaspberryPi/r... Thanks! Did you have some time to have a look at it? we should not use the binary thing from raspberry-firmware but instead just build it from the userland git repo. Source code is available.

Last time I checked, some parts were missing there. Guillaume

I'll try to look into that once I'm home from vacation and managed to get a crosscompile obs setup ready (qemu is just too slow).

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org