http://bugzilla.suse.com/show_bug.cgi?id=1168077 http://bugzilla.suse.com/show_bug.cgi?id=1168077#c8 Ladislav Slezák <lslezak@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(lslezak@suse.com) | --- Comment #8 from Ladislav Slezák <lslezak@suse.com> ---

Yast::Package.Installed(whatever_pkg)

This uses "rpm -q" internally, that cannot trigger any repository refresh, see https://github.com/yast/yast-yast2/blob/master/library/packages/src/modules/...

Yast::Package.DoInstall(@pkg_list)

https://github.com/yast/yast-yast2/blob/ada0fd3aac9f05eb0261f7085cd94645c768... That calls EnsureSourceInit https://github.com/yast/yast-yast2/blob/ada0fd3aac9f05eb0261f7085cd94645c768... Which calls Pkg.SourceStartCache which can refresh the repositories.

And doing only a partial refresh when you want to install a new package or upgrade an already installed one doesn't sound like a sane approach to me. It may be ok for manual operation of a system administrator that knows very well the repositories on the system and what is he/she doing, but not for YaST.

The reason for the refresh is to ensure that the latest package is selected. You can skip the refresh if you know what you are doing, but YaST needs to be on the safe side, it cannot do that... IMHO not a bug but a good and safe behavior. -- You are receiving this mail because: You are on the CC list for the bug.