Bug 1009745

Can reproduce in Tumbleweed snapshot 20161112 -- after installing KDE Discover, no apps are shown unless I do "zypper refresh --force".

Michael, the plugin hooks into the repo refresh. So it can only see repos that got refreshed after the plugin is installed. Is there a way to have the plugin called for all repos that existed before the plugin installation already?

Actually this is something the package should be able to handle, if it gets initially installed. But problem with the DVD install might be, that YAST has not yet copied the repos into the system. On a chroot-install, we probably need to have a trigger at first boot.

The problem is that the pluggin, as it is now, gets a list of the active repos, their type and cache location passed as parameter;

going to just scan /var/cache/zypp sounds error prone and would match also possible disabled repo.

Hence, I don't think the plugin on its own has the sufficient information without zypp

Then trigger a 'zypper ref -f' collectiong the initial appdata once 
 on 1st boot (if chroot install)
 or from %posttrans after initial install

Ping!

From the comments it's not entirely clear what the current state of this issue is.

It doesn'(In reply to Michael Andres from comment #5)
> Then trigger a 'zypper ref -f' collectiong the initial appdata once 
>  on 1st boot (if chroot install)
>  or from %posttrans after initial install

Triggering a refresh of repo data within a zypper run doesn't sound like a good idea to me. Isn't it possible to just run the appdata collector?

Question is WHO runs such a collector? 

If it is called from within the plugin packages %post, then it will most probably not work if the package is installed using the DVD install (using any offline install/update). AFAIK yast does not transfer the repos into the system before the installation has ended. So a collector won't see the repos in use. 


Installing the package in a running system however it would be possible to call e.g.
>   ZYPP_PLUGIN_APPDATA_FORCE_COLLECT=1 zypper -n lr >/dev/null 2>&1
from within the plugin packages %post(if initial install: $1==1). 'zypper lr' is readonly, so you can call it even from within a zypper install. 

The appdata plugin package could provide a shell script called e.g. zypper-appdatarefresh, executing the above line (maybe supporting 'zypper-appdatarefresh --force' executing 'zypper -n ref -f' instead). Then you can call 'zypper-appdatarefresh' in your %post($1==1).

People can easily call 'zypper-appdatarefresh' manually (as root!) if the initial install did not collect the data. If it's installed in $PATH, it'll be available as 'zypper appdatarefresh' too, 'zypper help appdatarefresh' will display the manpage for 'zypper-appdatarefresh' (if you provide one).


If that's ok, I'd adapt libzypp to evaluate $ZYPP_PLUGIN_APPDATA_FORCE_COLLECT.

JFYI: ZYPP_PLUGIN_APPDATA_FORCE_COLLECT is supported in libzypp-16.13.1

SUSE-SU-2017:2040-1: An update that solves three vulnerabilities and has 6 fixes is now available.

Category: security (important)
Bug References: 1009745,1031756,1033236,1038132,1038984,1043218,1045735,1047785,1048315
CVE References: CVE-2017-7435,CVE-2017-7436,CVE-2017-9269
Sources used:
SUSE Linux Enterprise Software Development Kit 12-SP2 (src):    libzypp-16.15.2-27.21.1
SUSE Linux Enterprise Server for Raspberry Pi 12-SP2 (src):    libzypp-16.15.2-27.21.1, zypper-1.13.30-18.13.3
SUSE Linux Enterprise Server 12-SP2 (src):    libzypp-16.15.2-27.21.1, zypper-1.13.30-18.13.3
SUSE Linux Enterprise Desktop 12-SP2 (src):    libzypp-16.15.2-27.21.1, zypper-1.13.30-18.13.3
OpenStack Cloud Magnum Orchestration 7 (src):    libzypp-16.15.2-27.21.1, zypper-1.13.30-18.13.3

openSUSE-SU-2017:2111-1: An update that solves three vulnerabilities and has 6 fixes is now available.

Category: security (important)
Bug References: 1009745,1031756,1033236,1038132,1038984,1043218,1045735,1047785,1048315
CVE References: CVE-2017-7435,CVE-2017-7436,CVE-2017-9269
Sources used:
openSUSE Leap 42.2 (src):    libzypp-16.15.2-5.9.1, zypper-1.13.30-5.9.1

SUSE-SU-2017:2264-1: An update that solves three vulnerabilities and has 5 fixes is now available.

Category: security (important)
Bug References: 1009745,1036659,1038984,1043218,1045735,1046417,1047785,1048315
CVE References: CVE-2017-7435,CVE-2017-7436,CVE-2017-9269
Sources used:
SUSE Linux Enterprise Software Development Kit 12-SP3 (src):    libzypp-16.15.3-2.3.1, yast2-pkg-bindings-devel-doc-3.2.4-2.3.1
SUSE Linux Enterprise Server 12-SP3 (src):    libzypp-16.15.3-2.3.1, yast2-pkg-bindings-3.2.4-2.3.1
SUSE Linux Enterprise Desktop 12-SP3 (src):    libzypp-16.15.3-2.3.1, yast2-pkg-bindings-3.2.4-2.3.1

openSUSE-SU-2017:2335-1: An update that solves three vulnerabilities and has 5 fixes is now available.

Category: security (important)
Bug References: 1009745,1036659,1038984,1043218,1045735,1046417,1047785,1048315
CVE References: CVE-2017-7435,CVE-2017-7436,CVE-2017-9269
Sources used:
openSUSE Leap 42.3 (src):    libzypp-16.15.3-9.1, yast2-pkg-bindings-3.2.4-4.1, yast2-pkg-bindings-devel-doc-3.2.4-4.1

SUSE-SU-2017:2470-1: An update that solves 18 vulnerabilities and has 46 fixes is now available.

Category: security (important)
Bug References: 1004995,1009745,1014471,1017420,1019637,1026825,1027079,1027688,1027908,1028281,1028723,1029523,1031756,1032706,1033236,1035062,1036659,1038132,1038444,1038984,1042392,1043218,1043333,1044095,1044107,1044175,1044840,1045384,1045735,1045987,1046268,1046417,1046659,1046853,1046858,1047008,1047236,1047240,1047310,1047379,1047785,1047964,1047965,1048315,1048483,1048605,1048679,1048715,1049344,1050396,1050484,1051626,1051643,1051644,1052030,1052759,1053409,874665,902364,938657,944903,954661,960820,963041
CVE References: CVE-2013-7459,CVE-2016-9063,CVE-2017-1000100,CVE-2017-1000101,CVE-2017-10684,CVE-2017-10685,CVE-2017-11112,CVE-2017-11113,CVE-2017-3308,CVE-2017-3309,CVE-2017-3453,CVE-2017-3456,CVE-2017-3464,CVE-2017-7435,CVE-2017-7436,CVE-2017-8872,CVE-2017-9233,CVE-2017-9269
Sources used:
SUSE Container as a Service Platform ALL (src):    caasp-container-manifests-0.0.0+git_r155_93e40ab-2.3.3, container-feeder-0.0.0+20170901.git_r55_17ecbd3-2.3.3, sles12-mariadb-docker-image-1.1.0-2.3.10, sles12-pause-docker-image-1.1.0-2.3.11, sles12-pv-recycler-node-docker-image-1.1.0-2.3.10, sles12-salt-api-docker-image-1.1.0-2.3.9, sles12-salt-master-docker-image-1.1.0-4.3.10, sles12-salt-minion-docker-image-1.1.0-2.3.8, sles12-velum-docker-image-1.1.0-4.3.9

This is an autogenerated message for OBS integration:
This bug (1009745) was mentioned in
https://build.opensuse.org/request/show/592378 Factory / libzypp-plugin-appdata

This is an autogenerated message for OBS integration:
This bug (1009745) was mentioned in
https://build.opensuse.org/request/show/592387 Factory / libzypp-plugin-appdata

This is an autogenerated message for OBS integration:
This bug (1009745) was mentioned in
https://build.opensuse.org/request/show/600294 Factory / libzypp-plugin-appdata

This is an autogenerated message for OBS integration:
This bug (1009745) was mentioned in
https://build.opensuse.org/request/show/601527 Factory / libzypp-plugin-appdata

*** Bug 1093032 has been marked as a duplicate of this bug. ***

This is an autogenerated message for OBS integration:
This bug (1009745) was mentioned in
https://build.opensuse.org/request/show/607084 15.0 / libzypp-plugin-appdata

(In reply to Swamp Workflow Management from comment #21)
> This is an autogenerated message for OBS integration:
> This bug (1009745) was mentioned in
> https://build.opensuse.org/request/show/607084 15.0 / libzypp-plugin-appdata

With this, together with systemd-present-branding merged, that issue should (finally) be resolved

*** Bug 1095011 has been marked as a duplicate of this bug. ***