[zypp-devel] addRequire("foo", ResKind::patch) not working?
Hi, does somebody have some insight on this?: -------------------------------------------------------------------------- Selectable & s; Capability c(s.name(), s.kind()); God->resolver()->addRequire(c); DBG << s << " install: adding requirement " << c << endl; ---> log: [zypper] zypper-misc.cc(mark_selectable):453 [patch]grep: S_NoInst (I 0) (A 2)UB_s_(43008)patch:grep-19.noarch(you11) install: adding requirement patch:grep ---> output: zypper in -t patch grep Reading installed packages... Problem: nothing provides requested patch:grep Have you enabled all requested repositories ? Solution 1: do not ask to install a solvable providing patch:grep Choose the above solution using '1' or cancel using 'c' [1/C]: -------------------------------------------------------------------------- I think it worked before. And it works with patterns and products. AND it seems to be alright also in deptestomatic (but i don't know how does deptestomatic add such requirement). Any idea? I'm quite clueless. Don't the patches provide themselves in our pool? Should i use poolitem.status().setToBeInstalled(zypp::ResStatus::USER) for patches? But if it addRequries() works for patterns (and newly also for srcpackages), it should also for patches. BTW: what is the difference between setToBeInstalled and setTransact()? cheers, jano -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On Wed, Jun 04, Jan Kupec wrote:
I think it worked before. And it works with patterns and products. AND it seems to be alright also in deptestomatic (but i don't know how does deptestomatic add such requirement).
Any idea? I'm quite clueless. Don't the patches provide themselves in our pool? Should i use
IMO they should. You can cd /var/cache/zypp/solv/<alias of the repo> dumpsolv solv | less -then search to '^name: patch:grep' -below you find the 'provides:' What's the repo you're using?
poolitem.status().setToBeInstalled(zypp::ResStatus::USER) for patches? But if it addRequries() works for patterns (and newly also for srcpackages), it should also for patches.
yes.
BTW: what is the difference between setToBeInstalled and setTransact()?
setTransact sets the transact bit, causing an uninstalled item to be installed, or an installed item to be removed. setToBeInstalled sets the transact bit only if it is an uninstalled item, and returns false for installed items. bool setToBeInstalled (TransactByValue causer) { if (isInstalled()) return false; return setTransact (true, causer); } -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On Wed, Jun 04, Michael Andres wrote:
On Wed, Jun 04, Jan Kupec wrote:
I think it worked before. And it works with patterns and products. AND it seems to be alright also in deptestomatic (but i don't know how does deptestomatic add such requirement).
Any idea? I'm quite clueless. Don't the patches provide themselves in our pool? Should i use
IMO they should. You can
Looks like I'm wrong: http://download.opensuse.org/update/11.0/ name: patch:grep 18 noarch vendor: maint-coord@suse.de conflicts: grep.i586 < 2.5.2-70 grep.ppc < 2.5.2-70 grep.x86_64 < 2.5.2-70 solvable:patchcategory: recommended Hopefully not a feature. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On Wed, Jun 04, Michael Andres wrote:
On Wed, Jun 04, Michael Andres wrote:
On Wed, Jun 04, Jan Kupec wrote:
I think it worked before. And it works with patterns and products. AND it seems to be alright also in deptestomatic (but i don't know how does deptestomatic add such requirement).
Any idea? I'm quite clueless. Don't the patches provide themselves in our pool? Should i use
IMO they should. You can
Looks like I'm wrong: http://download.opensuse.org/update/11.0/
name: patch:grep 18 noarch vendor: maint-coord@suse.de conflicts: grep.i586 < 2.5.2-70 grep.ppc < 2.5.2-70 grep.x86_64 < 2.5.2-70 solvable:patchcategory: recommended
Hopefully not a feature.
https://bugzilla.novell.com/show_bug.cgi?id=397132 -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
participants (2)
-
Jan Kupec -
Michael Andres