Assignee: Gentoo VMWare Bug Squashers ------------------------------------------- REFERENCE: Bug 634770 - app-emulation/vmware-workstation-14.0.0 version bump (??) has to be checked / replaced according to "versioning of vmware-modules" : . . . https://github.com/gentoo/vmware/issues/18
(In reply to Manfred Knick from comment #0) > (??) has to be checked / replaced according to - Run the official installer - tar -xf /usr/lib64/vmware/modules/source/vmmon.tar - $ grep VMMON_VERSION vmmon-only/include/iocontrols.h #define VMMON_VERSION (329 << 16 | 0) <--- #define VMMON_VERSION_MAJOR(v) ((uint32) (v) >> 16) #define VMMON_VERSION_MINOR(v) ((uint16) (v))
Created attachment 502692 [details] vmware-modules-329.0.0.ebuild /usr/local/portage/local-overlay/app-emulation/vmware-modules/vmware-modules-329.0.0.ebuild adapted from OVERLAY: app-emulation/vmware-modules-308.5.7:0::vmware
Created attachment 502780 [details] vmware-modules-329.0.0.ebuild 3 old patches don't apply any more
Cross-reference, concerning kernel version 4.14 : https://bugs.gentoo.org/619392#c5 ff.
Bug 634770 , comments #c44 and #c45 belong here: . . . ERROR: could not insert ... : Exec format error https://bugs.gentoo.org/634770#c44 https://bugs.gentoo.org/634770#c45
Ștefan Talpalaru 2017-11-25 14:45:41 UTC answered : https://bugs.gentoo.org/634770#c47
@ Stefan : In your overlay, -workstation already contains a "Manifest" file. Would you like to add one for -modules too?
No need. "Thin" manifests only store hashes for dist files not under version control. There is no such file for this package, because it uses sources already installed by vmware-workstation. More details: https://wiki.gentoo.org/wiki/Repository_format/package/Manifest#Thin_Manifest
(In reply to Ștefan Talpalaru from comment #8) > No need. Sorry, Stefan, but - once again - I'm _not_ testing your complete overlay. $ grep -i "thin" /var/lib/layman/vmware/metadata/layout.conf # Use thin manifests thin-manifests = true # Dont sign thin manifests. There is no current policy for git commit signing So I agree it definitely makes sense not to include it into your overlay - meanwhile, I will manage myself locally. Thanks for your hint.
(In reply to Manfred Knick from comment #9) > Sorry, Stefan, > but - once again - I'm _not_ testing your complete overlay. I don't mean no disrespect, but that's your problem, not mine. I take great care to run repoman in my overlay before publishing any modification to GitHub, so you won't catch me with broken or missing manifests. I also prefer the use of GitHub issues for bug reporting. Now, I'm very grateful for your help in significantly improving the ebuild, but let's not pretend that anyone besides us cares about these Bugzilla comments and attachments. Most of Gentoo development moved outside Gentoo, in personal or project overlays. The only time you'll see a core developer do a version bump is when they need it themselves. Reporting bugs here is still useful for regular users, but expecting them to be fixed in a promptly matter by core devs is nothing but a cargo cult - the planes won't land just because we built runways, the ebuilds won't reach the main tree just because you attach them.
(In reply to Ștefan Talpalaru from comment #10) > (In reply to Manfred Knick from comment #9) > > but - once again - I'm _not_ testing your complete overlay. This was only meant as an explanation. > I don't mean no disrespect, but that's your problem, not mine. 'til one minute ago, I assumed your goal would be to gain integration of exactly these two packages into official vmware overlay? My goal is, after - unfortunately and not really necessary; almost carelessly - VMware as a professional solution had to be removed from Main Portage Tree, to help at least re-establish the official [VMWARE] overlay into a state that professional customers re-gain confidence in using it for professional purposes. Those people will definitely - neither care about multiple private GitHub repositories - nor about GitHub issues. Thus I get strongly urged to make sure that - plain Gentoo plus - official [VMWARE] overlay are sufficient and reliable. Just my 2 cents of thought ... If I'm travelling headless roads, I prefer to learn my mis-understandings. If you intend to re-integrate VMware into Main Portage Tree via your Overlay, I'll be the first to applaud - then please, let me know in which way I can help / assist best. Kind regards Manfred
(In reply to Manfred Knick from comment #11) > 'til one minute ago, > I assumed your goal would be > to gain integration of exactly these two packages > into official vmware overlay? No, that's an exercise in futility. Look at what people are working on in that overlay - https://cgit.gentoo.org/proj/vmware.git/log/ : "Added latest version 12.5.8.7098237" - 8 days ago They obviously have other priorities. > to help at least re-establish the official [VMWARE] overlay > into a state that professional customers re-gain confidence > in using it for professional purposes. You can try, but I wouldn't hold my breath. Your best bet is that at some point in the future Fabio Rossi will need to run VMWare 14 so he'll stumble upon our work, cripple it in some horrible way and upstream that :-)
(In reply to Ștefan Talpalaru from comment #12) I deeply disgust disrespect.
REFERENCE: https://bugs.gentoo.org/634770#c56 ff. Thanks again to Ștefan Talpalaru.
(In reply to Manfred Knick from comment #14) These have obsoleted former ebuild attachments.
Obsolete: Multiple CVE --> Bug 644950 - [vmware] app-emulation/vmware-modules-329.1.1: version bump
