I wonder why we have some Samba-like versioned ebuild, instead following the versioning scheme upstream¹. Versioning isn't trivial, as e.g. in case of a security issue and a later need to downgrade the version, the relevant GLSA is suddenly wrong, causing us and moreso our users even more hassles. So, unless I'm missing something, I request to change to upstream's versioning ASAP.
*** This bug has been marked as a duplicate of bug 201992 ***
Because it's grabbed from samba tarball and packaged manually, not using anything from the link you've posted. Please take your questions out of bugzilla, completely improper place for this.
*** Bug 201992 has been marked as a duplicate of this bug. ***
(In reply to comment #2)
> Because it's ...
...the referenced homepage in the ebuild. I'm pretty sure you don't have any insight in the development process of this package, so let the samba team resolve the bug, o.k!
OMG, kindly check the source tarball before wasting other people's time. What you've linked doesn't ship mount-cifs but cifs-vfs.
(In reply to comment #5)
> ...the referenced homepage in the ebuild. I'm pretty sure you don't have any
> insight in the development process of this package, so let the samba team
> resolve the bug, o.k!
And yeah, I've just packaged this and written this ebuild and got it into portage. SIGFAIL.
Uh, indeed the module. Sorry.