http://bugzilla.novell.com/show_bug.cgi?id=607482 http://bugzilla.novell.com/show_bug.cgi?id=607482#c2 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Status|NEW |ASSIGNED --- Comment #2 from Ján Kupec 2010-05-20 12:09:00 UTC --- Thanx, i see the cause of the segfault, i'll also take a look at the weird messages. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=607482 http://bugzilla.novell.com/show_bug.cgi?id=607482#c3 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P3 - Medium Status|ASSIGNED |NEW AssignedTo|jkupec@novell.com |zypp-maintainers@forge.prov | |o.novell.com Summary|zypper segfault: |zypper in package.arch |intrusive_ptr.hpp:166: T* |yields senseless result |boost::intrusive_ptr<T>::op | |erator->() | Severity|Critical |Major --- Comment #3 from Ján Kupec 2010-05-20 13:22:10 UTC --- Oh, i recall now what's the problem with the architecture. Currently PoolQuery with architecture ORs the arch with the rest of the conditions, so the result are all packages with that arch plus something more. Michael, can you please take care of that? (i'll take care of the segfault) Tobias, in the meantime, if you need to install different architecture, use the -C switch (install by capability): $ zypper in -C package.arch -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=607482 http://bugzilla.novell.com/show_bug.cgi?id=607482#c5 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ma@novell.com --- Comment #5 from Michael Andres 2010-05-20 16:08:08 CEST --- You always need to be prepared to have multiple installed items, either by accident or because the package has 'multiversion' set (which might sometimes need special treatment). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=607482 http://bugzilla.novell.com/show_bug.cgi?id=607482#c7 --- Comment #7 from Ján Kupec 2010-05-20 15:47:56 UTC --- (In reply to comment #6)

That's the nature of PoolQuery. All conditions, you add are OR'ed.

I'm not sure why it did before, but now it does not make sense to me. IMO, only several values of the same property should be ORed, different properties should be ANDed: (kind1 OR kind2) AND (arch1 OR arch2) AND (name1 AND/OR name2) AND (repo1 OR repo2) AND (dep1 AND/OR dep2) ... (in the case of name, description, summary, deps, etc, both AND and OR make sense of course)

I thought you use guessPackageSpec?

I do, but from it i make a PoolQuery (also adding repos), and pick the best with PoolItemBest. This deals nicely with most of the cases, including globs. (BTW, i'm aware of the suggestion you made about the globs in the other bug, i still need to think about it a bit).

Anyway it would be consequent to add some additional addDependency overloads, so you can also restrict the arch, not just edition:

q.addDependency( sat::SolvAttr::name, "ker*", Rel::GT, Edition("2.6.31"), Arch_x86_64 );

q.addDependency( sat::SolvAttr::name, "ker*", Arch_x86_64 );

Would this fit your needs?

Hmm, yes, but not in this particular case - we're not dealing with deps here. We just want to select package named X with arch Y here. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=607482 http://bugzilla.novell.com/show_bug.cgi?id=607482#c9 --- Comment #9 from Michael Andres 2010-05-20 18:52:31 CEST --- (In reply to comment #7)

...

Would this fit your needs?

Hmm, yes, but not in this particular case - we're not dealing with deps here. We just want to select package named X with arch Y here.

It was originally added to deal with deps, but in fact it's of common use. For non-dependency attributes it behaves like addAttr PLUS an additional constraint on the edition range. vvvv

...

q.addDependency( sat::SolvAttr::name, "ker*", Rel::GT, Edition("2.6.31"), Arch_x86_64 );

So this is (would be) name matches "ker*" AND edition > "2.6.31" AND arch == "x86_64" -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=607482 http://bugzilla.novell.com/show_bug.cgi?id=607482#c11 --- Comment #11 from Michael Andres 2010-05-21 18:14:31 CEST --- (In reply to comment #10)

(That's name/edition of a provides, right?

No.

We don't support "package name only" dependencies yet.)

Yes, but this is a pool query, not a dependency. It would look for all sat::SolvAttr::name (packagenames) matching "ker*". And from the result the ones with edition > "2.6.31" and arch == "x86_64" are taken. Ideally we'd pass the result to the solver to install (the best) one out of the result list. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.