{"action":"created","issue":{"url":"https://api.github.com/repos/OpenMandrivaAssociation/rpm/issues/1","repository_url":"https://api.github.com/repos/OpenMandrivaAssociation/rpm","labels_url":"https://api.github.com/repos/OpenMandrivaAssociation/rpm/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/OpenMandrivaAssociation/rpm/issues/1/comments","events_url":"https://api.github.com/repos/OpenMandrivaAssociation/rpm/issues/1/events","html_url":"https://github.com/OpenMandrivaAssociation/rpm/issues/1","id":205643877,"number":1,"title":"Upgrade to 5.4.17","user":{"login":"n3npq","id":643926,"avatar_url":"https://avatars.githubusercontent.com/u/643926?v=3","gravatar_id":"","url":"https://api.github.com/users/n3npq","html_url":"https://github.com/n3npq","followers_url":"https://api.github.com/users/n3npq/followers","following_url":"https://api.github.com/users/n3npq/following{/other_user}","gists_url":"https://api.github.com/users/n3npq/gists{/gist_id}","starred_url":"https://api.github.com/users/n3npq/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/n3npq/subscriptions","organizations_url":"https://api.github.com/users/n3npq/orgs","repos_url":"https://api.github.com/users/n3npq/repos","events_url":"https://api.github.com/users/n3npq/events{/privacy}","received_events_url":"https://api.github.com/users/n3npq/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":15,"created_at":"2017-02-06T16:50:58Z","updated_at":"2017-02-13T22:51:27Z","closed_at":null,"body":"OK, I have a procedure that will eventually permit an rpm upgrade in spite of 100's of patches.\r\n\r\n0) CVS checkout on the rpm-5_4_15-release tag. Build and fix issues with newer prereqs.\r\n1) Manually extract all the patches (and order of application) in a script. Apply, build, and fix.\r\n2) Upgrade to the rpm-5_4_16-release tag. Fix merge conflicts and build.\r\n3) Upgrade to the rpm-5_4_17-release tag. Fix merge conflicts and build.\r\n\r\nI've done a preliminary pass and succeeded in building RPM to the point where I can't at least run tests to identify issues.\r\n\r\nQ0: I see no point in carrying 300+ RPM patches separately, as its quite difficult to find WTF for any issue. Is a single coagulated patch acceptable or not?\r\n\r\nQ1: Should I continue to rpm-5.4.18? There is nothing in rpm-5.4.18 that is going to hurt you afaik,\r\n(and I can release a reference tarball for rpm-5.4.18 any time I wish). In fact, I believe OMA rpm-5.4.15 is based on a snapshot 5.4.15 tarball (but I could be wrong).\r\n\r\nQ2: OMA is reverting changes from more than a decade ago, including\r\n   * reading rpm v3 packaging (obsolete and unused since 2001)\r\n   * using per-platform macros (abandoned in 2007)\r\n   * changing header data type for epoch from uint32 -> int32 (2007) because POK didn't \"like\"\r\n     the already implemented/supported functionality (2009)  to deprecate/remove EPOCH.\r\n   * carrying lots of EVRD hacks (instead of fixes) that have been pointed out repeatedly (since 2011) and never prioritized because of \"No time, release is more important.\" I think this ancient hysteria needs to go away or be fixed properly.\r\n\r\nQ3: OMA (i.e. POK) have implemented bleeding edge functionality that has never been properly discussed. One change is the addition of 2 triggers for pre/post transactions that fundamentally changes the RPM state machine for no reason I understand. Are you using pre/post transaction triggers? Another change is loadable embedded interpreter modules, which has huge legacy implications if/when added to RPM. Both of these changes need wider public discussion and thought before consideration in RPM imho.\r\n\r\nQ4: RPM5 upstream is carrying lots of #ifdef RPM_VENDOR_MANDRIVA code that is waiting to be pushed back to OMA largely because I cannot support code that isn't compiled/tested. Now is likely the time to sort out who is responsible for what changes. If I continue releasing upstream code with RPM_VENDOR_MANDRIVA patches, it creates a false hope that the code \"works\" and \"compiles\" and is \"supported\", and there are many examples of \"Me too.\" enabling changes that are mostly reversions to development.\r\n\r\nQ5: In order to build \"officially\", I need agreement on what build options are to be used. The de facto rpm.spec file isn't good enough because it depends on implicit AutoFu behavior detecting what is installed rather than explicit options that fail if a build prereq is missing. There are far too many options\r\nto handle RPM functionality implicitly imho.\r\n\r\nI need some indication of what is permitted before attempting another, more careful, upgrade pass to integrate."},"comment":{"url":"https://api.github.com/repos/OpenMandrivaAssociation/rpm/issues/comments/279549699","html_url":"https://github.com/OpenMandrivaAssociation/rpm/issues/1#issuecomment-279549699","issue_url":"https://api.github.com/repos/OpenMandrivaAssociation/rpm/issues/1","id":279549699,"user":{"login":"n3npq","id":643926,"avatar_url":"https://avatars.githubusercontent.com/u/643926?v=3","gravatar_id":"","url":"https://api.github.com/users/n3npq","html_url":"https://github.com/n3npq","followers_url":"https://api.github.com/users/n3npq/followers","following_url":"https://api.github.com/users/n3npq/following{/other_user}","gists_url":"https://api.github.com/users/n3npq/gists{/gist_id}","starred_url":"https://api.github.com/users/n3npq/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/n3npq/subscriptions","organizations_url":"https://api.github.com/users/n3npq/orgs","repos_url":"https://api.github.com/users/n3npq/repos","events_url":"https://api.github.com/users/n3npq/events{/privacy}","received_events_url":"https://api.github.com/users/n3npq/received_events","type":"User","site_admin":false},"created_at":"2017-02-13T22:51:27Z","updated_at":"2017-02-13T22:51:27Z","body":"Below is the raw patch after applying OMA patches and then upgrading to rpm-5_4_17-release using CVS for reference.\r\n\r\nSeveral patches that got in the way (again) like loadable embedded interpreters have been partially reverted. I have also resolved some issues by using rpm-5.4.18 files.\r\n\r\nI will plot out other issues for discussion while cleaning up the raw patch as needed, an then provide a rpm-5.4.17 tar ball that might have a chance of compiling,\r\n\r\n[oma+wdj-5.4.17.patch.0.gz](https://github.com/OpenMandrivaAssociation/rpm/files/772623/oma.wdj-5.4.17.patch.0.gz)\r\n"}}
{"actor":{"display_login":"n3npq"}}