[opensuse-factory] factory iptables: wants libiptables.so.9, but links with generic?
I put the new iptables from factory on my system along with the new libtiptables10. I get a message: iptables: target "standard" has version "libxtables.so.10", but "libxtables.so.9" is required. I put libxtables.so.0 on my system to so it could link to it but it still links to #10. It seems it requires 9, but doesn't link to 9 -- but to target generic. If a product requires version "x", shouldn't it link to libxxxx.so.x and not libxxxx.so (generic) This isn't the first time I've run into this -- where a product requires a specific .so version, but then at run time links to the "generic" name. Why wouldn't a product requiring version "x.y.z, link to the version it requires, then products with multiple requirements could live side-by-side rather than causing version hell? You can't have multiple versions of a lib all named XXXX.so, -- how would the system know which one to load? But if they were named xxxx.so.1, xxxx.so.2, etc... why couldn't they be loaded by the products that need them? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 2013-05-01 05:49, Linda Walsh wrote:
I put the new iptables from factory on my system along with the new libtiptables10.
I get a message:
When?
iptables: target "standard" has version "libxtables.so.10", but "libxtables.so.9" is required.
So, you are mixing the packages iptables-1.4.17 (requires .so.9) with iptables-1.4.18/xtables-plugins-1.4.18 (requires .so.10). That is not a supported combination, however.
It seems it requires 9, but doesn't link to 9 -- but to target generic. If a product requires version "x", shouldn't it link to libxxxx.so.x and not libxxxx.so (generic) This isn't the first time I've run into this -- where a product requires a specific .so version, but then at run time links to the "generic" name. Why wouldn't a product requiring version "x.y.z, link to the version it requires, then products with multiple requirements could live side-by-side rather than causing version hell?
It is in the very nature of plugins to have arbitrary names and/or to have the executing program take plugins of arbitrary name. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Jan Engelhardt wrote:
On Wednesday 2013-05-01 05:49, Linda Walsh wrote:
It is in the very nature of plugins to have arbitrary names and/or to have the executing program take plugins of arbitrary name.
--- Hmm...I wonder how got mixed... Recompiling iptables and installing from that seems to have sync them. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Linda Walsh wrote:
I put the new iptables from factory on my system along with the new libtiptables10.
I get a message: iptables: target "standard" has version "libxtables.so.10", but "libxtables.so.9" is required.
---- I ran into this again today after doing more system cleanup... I figured out why -- factory has an iptables that needs libxtables9, but only libxtables10 is available in factory!? I.e. -- it appears that the iptables on factory and the libxtables available are not compatible? Anyone else see this? I think I got around it by recompiling from source, but in system cleanup was looking for packages that didn't match or requirements that didn't (rpm -V)... and I think I fixed it back to the factory version -- which doesn't work.... (I so brilliant at times! :->>>>> (*doh!)).... Guess I'll go rebuild from source again...?? Am I not seeing the package on factory? Sure looks like I have latest versions -- and they appear not to match: libxtables10-1.4.18-2.1 is on factory -- but the iptables2 package on factory needs lib9. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday 2013-05-07 21:21, Linda Walsh wrote:
Linda Walsh wrote:
I put the new iptables from factory on my system along with the new libtiptables10.
I get a message: iptables: target "standard" has version "libxtables.so.10", but "libxtables.so.9" is required.
---- I ran into this again today after doing more system cleanup... I figured out why --
factory has an iptables that needs libxtables9, but only libxtables10 is available in factory!?
rpm -qRp iptables-1.4.18-2.1.x86_64.rpm /bin/bash
rpm -qRp xtables-plugins-1.4.18-2.1.x86_64.rpm
As I told you before, factory iptables requires libxtables10. You are not running factory iptables. libc.so.6()(64bit) libc.so.6(GLIBC_2.14)(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.3)(64bit) libc.so.6(GLIBC_2.3.4)(64bit) libc.so.6(GLIBC_2.4)(64bit) libc.so.6(GLIBC_2.7)(64bit) libip4tc.so.0()(64bit) libip6tc.so.0()(64bit) libxtables.so.10()(64bit) rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 xtables-plugins = 1.4.18 rpmlib(PayloadIsLzma) <= 4.4.6-1 libc.so.6()(64bit) libc.so.6(GLIBC_2.14)(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.3)(64bit) libc.so.6(GLIBC_2.3.4)(64bit) libc.so.6(GLIBC_2.4)(64bit) libc.so.6(GLIBC_2.7)(64bit) libm.so.6()(64bit) libm.so.6(GLIBC_2.2.5)(64bit) libnfnetlink.so.0()(64bit) libxtables.so.10()(64bit) rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(PayloadIsLzma) <= 4.4.6-1
libxtables10-1.4.18-2.1 is on factory -- but the iptables2 package on factory needs lib9.
There is no "iptables2" package. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Jan Engelhardt wrote:
---- I ran into this again today after doing more system cleanup... I figured out why --
factory has an iptables that needs libxtables9, but only libxtables10 is available in factory!?
As I told you before, factory iptables requires libxtables10. You are not running factory iptables.
I found that out -- I had downloaded both the iptables and libxtables at the same time, but I must have got caught when one was updated and not the other. I made sure the versions agreed and d/l source -- it matches up.. so hopefully that one is put to bed. It is not, BTW, the only product I've found out of sync with its libraries -- though I'm sure it gets corrected 'soon' -- would be nice if dependent products were released to servers at the same time... maybe that's the plan, but just things falling through the cracks...? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, May 8, 2013 at 11:44 AM, Linda Walsh
Jan Engelhardt wrote:
---- I ran into this again today after doing more system cleanup... I figured out why --
factory has an iptables that needs libxtables9, but only libxtables10 is available in factory!?
As I told you before, factory iptables requires libxtables10. You are not running factory iptables.
I found that out -- I had downloaded both the iptables and libxtables at the same time, but I must have got caught when one was updated and not the other.
I made sure the versions agreed and d/l source -- it matches up.. so hopefully that one is put to bed.
It is not, BTW, the only product I've found out of sync with its libraries -- though I'm sure it gets corrected 'soon' -- would be nice if dependent products were released to servers at the same time... maybe that's the plan, but just things falling through the cracks...?
Linda, Although I only use factory snapshots, I believe there are 3 flavors of factory. The best known 2 are raw factory where things hit whenever they hit and factory snapshots where true milestones and RCs are released from. Snapshots are manually created based on a schedule and when things appear stable No snapshots have been produced since 12.3 was released almost 2 months ago, so you may find it too slow to update. The middle ground is factory-tested: https://en.opensuse.org/openSUSE:Factory-tested Factory-tested is more likely to have coordinated package releases so they are safer to run. Factory tested updates come out at random intervals based on what is hitting factory and what it's quality is. An automated tool checks for basic package consistency and pulls a "tested" release when things look good. (See the wiki for a better description of the process). I believe coordinated package release like you mention would go into the release of Factory-tested packages, not the release of raw factory packages. For core packages, I believe that already happens because the openQA install would fail if the packages were not in sync. For packages not tested by OpenQA, even in factory-tested there is no automated coordination that I know of. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Greg Freemyer wrote:
I believe coordinated package release like you mention would go into the release of Factory-tested packages, not the release of raw factory packages. For core packages, I believe that already happens because the openQA install would fail if the packages were not in sync. For packages not tested by OpenQA, even in factory-tested there is no automated coordination that I know of.
Greg
--- Thanks! Another package repo to pull and store locally! ;-) Are sources and debug packages also available there (I guess I'll find out) -- like to have sources sometimes so I can find out why something is working the way I thought it should... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Greg Freemyer wrote: . The best known 2 are raw factory where things hit
whenever they hit and factory snapshots where true milestones and RCs are released from. Snapshots are manually created based on a schedule and when things appear stable No snapshots have been produced since 12.3 was released almost 2 months ago, so you may find it too slow to update.
Don't know I know about the snapshots... generally just been going to : declare -xl server_url_root="http://download.opensuse.org" factory=factory/repo/{debug,oss,src-oss}/suse/{x86_64,noarch,src}/ (expand, combine...d/l, merge...etc..)
The middle ground is factory-tested: https://en.opensuse.org/openSUSE:Factory-tested
---- How long after do things end up there? Have been trying to sit on the edge of heck, as that's as reasonable as I can be if I am going to complain about changes... (longer you wait, the less chance anything will get done... not that much seems to happen by sitting on the edge, but at least won't get asked "where were you when this was being released and why didn't you say anything then?" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Linda Walsh
Greg Freemyer wrote: . The best known 2 are raw factory where things hit
whenever they hit and factory snapshots where true milestones and RCs are released from. Snapshots are manually created based on a schedule and when things appear stable No snapshots have been produced since 12.3 was released almost 2 months ago, so you may find it too slow to update.
Don't know I know about the snapshots.
The 13.1 set were just announced: http://markmail.org/message/qqhylyhawc7vkt5v If you build things in obs, you have to add the repo factory-snapshots to build against the most recent of those. Downloadable iso files are also created for the snapshots. It gives well defined points at which to report bugs against. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Greg Freemyer -
Jan Engelhardt -
Linda Walsh