[opensuse-packaging] slv2 is still missing from factory although lv2core is in it's nearly useless without slv2 and I cannot enable LV2 support in anything.
Hello all, openSUSE 11.4 RC 2 will be released next week, on Friday 25 February 2011. Please submit your packages before Friday afternoon (UTC time) to make sure they will get included in this release. Leaf packages submitted during the week-end might also get accepted on Monday. For a quick overview of the openSUSE Roadmap, please see: http://en.opensuse.org/Roadmap Thanks, Package slv2 is stuck somewhere : 60049 State:new By:plater When:2011-02-04T12:40:37 submit: multimedia:libs/slv2 -> openSUSE:Factory Descr: Add slv2-0.6.6-licencefix.patch to remove file with conflicting GPLv2 statement in the header. See bnc#669117 and slv upstream drobillad #630 The bug is sitting at #NEEDINFO set by me. Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 2011-02-16 11:37:47 +0200, Dave Plater wrote:
Please submit your packages before Friday afternoon (UTC time) to make sure they will get included in this release. Leaf packages submitted during the week-end might also get accepted on Monday.
For a quick overview of the openSUSE Roadmap, please see: http://en.opensuse.org/Roadmap
Thanks,
Package slv2 is stuck somewhere : 60049 State:new By:plater When:2011-02-04T12:40:37 submit: multimedia:libs/slv2 -> openSUSE:Factory Descr: Add slv2-0.6.6-licencefix.patch to remove file with conflicting GPLv2 statement in the header. See bnc#669117 and slv upstream drobillad #630 The bug is sitting at #NEEDINFO set by me.
the package is on hold because your package generates a different soversion than the packman package although you say both have the same version. 1. why not join the work with the packman team instead of duplicating the package? 2. if you have to duplicate it, why do the soversions differ? darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 02/17/2011 06:16 PM, Marcus Rueckert wrote:
On 2011-02-16 11:37:47 +0200, Dave Plater wrote:
Please submit your packages before Friday afternoon (UTC time) to make sure they will get included in this release. Leaf packages submitted during the week-end might also get accepted on Monday.
For a quick overview of the openSUSE Roadmap, please see: http://en.opensuse.org/Roadmap
Thanks,
Package slv2 is stuck somewhere : 60049 State:new By:plater When:2011-02-04T12:40:37 submit: multimedia:libs/slv2 -> openSUSE:Factory Descr: Add slv2-0.6.6-licencefix.patch to remove file with conflicting GPLv2 statement in the header. See bnc#669117 and slv upstream drobillad #630 The bug is sitting at #NEEDINFO set by me.
the package is on hold because your package generates a different soversion than the packman package although you say both have the same version.
1. why not join the work with the packman team instead of duplicating the package?
2. if you have to duplicate it, why do the soversions differ?
darix
I was only aware of the packman package after creating slv2 and unfortunately the build service can't build against packman packages otherwise I wouldn't have to go to all this trouble. I'll sort out the so number, the packman package is either older or was updated after I made slv2. The user who originally requested LV2 wanted it for ardour which isn't in packman. Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 2011-02-18 15:04:36 +0200, Dave Plater wrote:
I was only aware of the packman package after creating slv2 and unfortunately the build service can't build against packman packages otherwise I wouldn't have to go to all this trouble.
but what you can do is maintaining a package in the obs and reusing the same package in the packman buildservice. we do it for a number of packages already.
I'll sort out the so number, the packman package is either older or was updated after I made slv2. The user who originally requested LV2 wanted it for ardour which isn't in packman.
sure. but having conflicting packages for no reason, is not acceptable. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 02/17/2011 06:16 PM, Marcus Rueckert wrote:
On 2011-02-16 11:37:47 +0200, Dave Plater wrote:
Please submit your packages before Friday afternoon (UTC time) to make sure they will get included in this release. Leaf packages submitted during the week-end might also get accepted on Monday.
For a quick overview of the openSUSE Roadmap, please see: http://en.opensuse.org/Roadmap
Thanks,
Package slv2 is stuck somewhere : 60049 State:new By:plater When:2011-02-04T12:40:37 submit: multimedia:libs/slv2 -> openSUSE:Factory Descr: Add slv2-0.6.6-licencefix.patch to remove file with conflicting GPLv2 statement in the header. See bnc#669117 and slv upstream drobillad #630 The bug is sitting at #NEEDINFO set by me.
the package is on hold because your package generates a different soversion than the packman package although you say both have the same version.
1. why not join the work with the packman team instead of duplicating the package?
2. if you have to duplicate it, why do the soversions differ?
darix
I'm now confused, the packman package has the same name libslv2-9 now I remember, I looked at the packman package and it provided libslv2-8 so I used the conflict to cause the openSUSE version to be installed with the openSUSE devel package after I discovered that the packman package remained installed when I installed the slv2 devel package. Of course for building purposes only the openSUSE version will be installed but even though 99% of the time it won't cause a problem the package that was built against a particular library should use that library at runtime. The installation system gets confused by the pm in the packman release number sometimes. Regards Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 2011-02-18 15:23:11 +0200, Dave Plater wrote:
I'm now confused, the packman package has the same name libslv2-9 now I remember, I looked at the packman package and it provided libslv2-8 so I used the conflict to cause the openSUSE version to be installed with the openSUSE devel package after I discovered that the packman package remained installed when I installed the slv2 devel package. Of course for building purposes only the openSUSE version will be installed but even though 99% of the time it won't cause a problem the package that was built against a particular library should use that library at runtime.
The installation system gets confused by the pm in the packman release number sometimes.
that is actually the reason why we have the shared library packaging policy. so old libraries can remain installed so conflicts between shared library packages are a no go in general. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 02/18/2011 03:29 PM, Marcus Rueckert wrote:
On 2011-02-18 15:23:11 +0200, Dave Plater wrote:
I'm now confused, the packman package has the same name libslv2-9 now I remember, I looked at the packman package and it provided libslv2-8 so I used the conflict to cause the openSUSE version to be installed with the openSUSE devel package after I discovered that the packman package remained installed when I installed the slv2 devel package. Of course for building purposes only the openSUSE version will be installed but even though 99% of the time it won't cause a problem the package that was built against a particular library should use that library at runtime.
The installation system gets confused by the pm in the packman release number sometimes.
that is actually the reason why we have the shared library packaging policy. so old libraries can remain installed so conflicts between shared library packages are a no go in general.
darix
In this case the packman library is the same as the openSUSE library they are both libslv2-9 and they both have the same contents except the packman package also provides libslv2-8 so to prevent a mix of packman and openSUSE libslv2-9 packages I have obsoleted libslv2-8. If the packman libslv2-9 provides libslv2-8 then it is in conflict with the shared library packaging policy. I will happily remove it though because as I stated before it is only a slight possibility that it will cause a problem in which case if it does then I can close the bug as wontfix and refer the reporter to packman. Shall I remove the obsoletes and resubmit? Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 02/18/2011 03:29 PM, Marcus Rueckert wrote:
On 2011-02-18 15:23:11 +0200, Dave Plater wrote:
I'm now confused, the packman package has the same name libslv2-9 now I remember, I looked at the packman package and it provided libslv2-8 so I used the conflict to cause the openSUSE version to be installed with the openSUSE devel package after I discovered that the packman package remained installed when I installed the slv2 devel package. Of course for building purposes only the openSUSE version will be installed but even though 99% of the time it won't cause a problem the package that was built against a particular library should use that library at runtime.
The installation system gets confused by the pm in the packman release number sometimes.
that is actually the reason why we have the shared library packaging policy. so old libraries can remain installed so conflicts between shared library packages are a no go in general.
darix
In this case the packman library is the same as the openSUSE library they are both libslv2-9 and they both have the same contents except the packman package also provides libslv2-8
Am Freitag, 18. Februar 2011 schrieb Dave Plater: that is totally wrong :) my libslv2 package provides: libslv2-0 = 0.3.0 libslv2-4 = 0.3.2 libslv2-6 = 0.4.3 libslv2-8 = 0.5.0 libslv2.so.9 libslv2-9 = 0.6.6-1.pm.2.1 libslv2-9(x86-32) = 0.6.6-1.pm.2.1 the "old" versions are also obsoleted: libslv2-0 libslv2-4 libslv2-6 libslv2-8
so to prevent a mix of packman and openSUSE libslv2-9 packages I have obsoleted libslv2-8. If the packman libslv2-9 provides libslv2-8 then it is in conflict with the shared library packaging policy. I will happily remove it though because as I stated before it is only a slight possibility that it will cause a problem in which case if it does then I can close the bug as wontfix and refer the reporter to packman.
nothing to to from my side ...
Shall I remove the obsoletes and resubmit?
Dave P
-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 02/18/2011 05:39 PM, oc2pus@arcor.de wrote:
Am Freitag, 18. Februar 2011 schrieb Dave Plater:
On 02/18/2011 03:29 PM, Marcus Rueckert wrote:
On 2011-02-18 15:23:11 +0200, Dave Plater wrote:
I'm now confused, the packman package has the same name libslv2-9 now I remember, I looked at the packman package and it provided libslv2-8 so I used the conflict to cause the openSUSE version to be installed with the openSUSE devel package after I discovered that the packman package remained installed when I installed the slv2 devel package. Of course for building purposes only the openSUSE version will be installed but even though 99% of the time it won't cause a problem the package that was built against a particular library should use that library at runtime.
The installation system gets confused by the pm in the packman release number sometimes.
that is actually the reason why we have the shared library packaging policy. so old libraries can remain installed so conflicts between shared library packages are a no go in general.
darix
In this case the packman library is the same as the openSUSE library they are both libslv2-9 and they both have the same contents except the packman package also provides libslv2-8
that is totally wrong :)
my libslv2 package provides: libslv2-0 = 0.3.0 libslv2-4 = 0.3.2 libslv2-6 = 0.4.3 libslv2-8 = 0.5.0 libslv2.so.9 libslv2-9 = 0.6.6-1.pm.2.1 libslv2-9(x86-32) = 0.6.6-1.pm.2.1
the "old" versions are also obsoleted: libslv2-0 libslv2-4 libslv2-6 libslv2-8
so to prevent a mix of packman and openSUSE libslv2-9 packages I have obsoleted libslv2-8. If the packman libslv2-9 provides libslv2-8 then it is in conflict with the shared library packaging policy. I will happily remove it though because as I stated before it is only a slight possibility that it will cause a problem in which case if it does then I can close the bug as wontfix and refer the reporter to packman.
nothing to to from my side ...
Shall I remove the obsoletes and resubmit?
Dave P
I was simply trying to remove an unknown quantity with a packman libslv2-9 and an openSUSE slv2-devel I'm busy trying to build cinelerra-4.2 and have encountered problems with the same versions of videolan and packman devel and lib mixes and had to physically install the matching devel and library packages. Regards Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
now what i got you both in the thread: how about we just have one slv2 package in the obs and link it to the packman buildservice for building there? Toni, Dave: yes or no? If yes, which package should we use as base and which project in the obs? darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 02/18/2011 05:34 PM, Marcus Rueckert wrote:
now what i got you both in the thread:
how about we just have one slv2 package in the obs and link it to the packman buildservice for building there?
Toni, Dave: yes or no? If yes, which package should we use as base and which project in the obs?
darix
The packman lv2core package has lv2config missing and a different makeup to the one in factory, I would prefer a matching slv2 package to go with it seeing that I'm the bug owner. I don't quite know what we are trying to achieve here but I do know that it's getting more and more difficult for me to contribute to openSUSE. Maybe somebody else can shed some light on this problem, meanwhile I have paying work to do. Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Freitag, 18. Februar 2011 schrieb Dave Plater:
On 02/18/2011 05:34 PM, Marcus Rueckert wrote:
now what i got you both in the thread:
how about we just have one slv2 package in the obs and link it to the packman buildservice for building there?
Toni, Dave: yes or no? If yes, which package should we use as base and which project in the obs?
darix
The packman lv2core package has lv2config missing and a different makeup to the one in factory, I would prefer a matching slv2 package to go with it seeing that I'm the bug owner. I don't quite know what we are trying to achieve here but I do know that it's getting more and more difficult for me to contribute to openSUSE. Maybe somebody else can shed some light on this problem, meanwhile I have paying work to do.
lv2config ? did you mean the this file: /usr/lib/pkgconfig/lv2core.pc This file is packaged, and all packman packages related to slv2-support are build against our libslv2-* packages. So I don't see the problem of you. If you want to be the bugowner, feel free to create the needed packages in your private repositories. I'll forward all questions according different layouts and user-problems depending on the mixture of your and the packman packages then to you :) As a side note: Why not asking BEFORE you create "millions" of duplicates from already packaged programs in the packman repository ? And why reinventing every time a new layout for your packages ... Perhaps thats the reason of your problem, that it get "more and more difficult" for you to contribute. just my two cent :)
Dave P
Toni -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (4)
-
Dave Plater -
Dave Plater -
Marcus Rueckert -
oc2pus＠arcor.de