{"action":"created","issue":{"url":"https://api.github.com/repos/projectatomic/rpm-ostree/issues/415","repository_url":"https://api.github.com/repos/projectatomic/rpm-ostree","labels_url":"https://api.github.com/repos/projectatomic/rpm-ostree/issues/415/labels{/name}","comments_url":"https://api.github.com/repos/projectatomic/rpm-ostree/issues/415/comments","events_url":"https://api.github.com/repos/projectatomic/rpm-ostree/issues/415/events","html_url":"https://github.com/projectatomic/rpm-ostree/issues/415","id":168701037,"number":415,"title":"split base/layered versionlocked package problem (krb5-workstation)","user":{"login":"cgwalters","id":244096,"avatar_url":"https://avatars.githubusercontent.com/u/244096?v=3","gravatar_id":"","url":"https://api.github.com/users/cgwalters","html_url":"https://github.com/cgwalters","followers_url":"https://api.github.com/users/cgwalters/followers","following_url":"https://api.github.com/users/cgwalters/following{/other_user}","gists_url":"https://api.github.com/users/cgwalters/gists{/gist_id}","starred_url":"https://api.github.com/users/cgwalters/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cgwalters/subscriptions","organizations_url":"https://api.github.com/users/cgwalters/orgs","repos_url":"https://api.github.com/users/cgwalters/repos","events_url":"https://api.github.com/users/cgwalters/events{/privacy}","received_events_url":"https://api.github.com/users/cgwalters/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/projectatomic/rpm-ostree/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-08-01T17:41:10Z","updated_at":"2016-10-07T13:07:39Z","closed_at":null,"body":"In [wstree](https://pagure.io/fork/walters/workstation-ostree-config/commits/f24-continuous) right now `krb5-libs` is a dependency of various things in the base OS.  `krb5-workstation` is an app that uses it - however, it's version locked.\r\n\r\nThis introduces a problem with package layering, since if the compose server picks up a newer version from package mirror A, but the client only has an older version from mirror B, upgrades break.  (Or if it's not installed, it can't be).\r\n\r\nThere are obviously a few solutions to this...likely krb5-workstation should be more flexible, and only introduce a hard requirement on the `-libs` package version if it needs it.  Second, we may need to consider a way to retrieve rpm-md data from the same place as the ostree commit, or vice versa.   Basically having unified metadata/data management.\r\n"},"comment":{"url":"https://api.github.com/repos/projectatomic/rpm-ostree/issues/comments/252247316","html_url":"https://github.com/projectatomic/rpm-ostree/issues/415#issuecomment-252247316","issue_url":"https://api.github.com/repos/projectatomic/rpm-ostree/issues/415","id":252247316,"user":{"login":"cgwalters","id":244096,"avatar_url":"https://avatars.githubusercontent.com/u/244096?v=3","gravatar_id":"","url":"https://api.github.com/users/cgwalters","html_url":"https://github.com/cgwalters","followers_url":"https://api.github.com/users/cgwalters/followers","following_url":"https://api.github.com/users/cgwalters/following{/other_user}","gists_url":"https://api.github.com/users/cgwalters/gists{/gist_id}","starred_url":"https://api.github.com/users/cgwalters/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cgwalters/subscriptions","organizations_url":"https://api.github.com/users/cgwalters/orgs","repos_url":"https://api.github.com/users/cgwalters/repos","events_url":"https://api.github.com/users/cgwalters/events{/privacy}","received_events_url":"https://api.github.com/users/cgwalters/received_events","type":"User","site_admin":false},"created_at":"2016-10-07T13:07:38Z","updated_at":"2016-10-07T13:07:38Z","body":"I think if we provided the infrastructure to link to the rpm-md repos from the ostree commit, infra providers could use that.  We basically have all the data already from the treecompose side.  The infra provider would need to retain multiple versions of the rpm-md repo data though.\r\n\r\nThat said I think the general solution to this is to relax the strict version requirements.\r\n"}}
{"actor":{"display_login":"cgwalters"}}