Mailinglist Archive: zypp-devel (83 mails)

[Jan Kupec <jkupec@xxxxxxx>]

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@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx