As seen at https://github.com/mattermost/desktop/releases/tag/v4.1.2
Ping. What's the progress?
There's actually a well working source ebuild at https://gitlab.com/chaoslab/chaoslab-overlay/tree/master/net-im/mattermost-desktop also, if someone's up for adopting it. @ianmoone seems to have dropped off the radar for a couple of months, I hope he's OK.
This is now a security issue I think https://github.com/mattermost/desktop/releases/tag/v4.2.2
Looks like 4.2.2 wasn't announced with a full description or something, but shows up as a simple tag in https://github.com/mattermost/desktop/releases/ There is a 4.2.3 now that details security affect. Converting to a security bug, albeit this is precompiled source with security details withheld for 30 days.
Proxied maintainer retired. @monsieurp, now you're the primary maintainer.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f96f304103ad89cbc4e1529a1b1c068eabbfa1f7 commit f96f304103ad89cbc4e1529a1b1c068eabbfa1f7 Author: Patrice Clement <monsieurp@gentoo.org> AuthorDate: 2019-08-11 08:50:54 +0000 Commit: Patrice Clement <monsieurp@gentoo.org> CommitDate: 2019-08-11 08:50:54 +0000 net-im/mattermost-desktop-bin: drop maintainership. Bug: https://bugs.gentoo.org/662978 Signed-off-by: Patrice Clement <monsieurp@gentoo.org> Package-Manager: Portage-2.3.62, Repoman-2.3.11 net-im/mattermost-desktop-bin/metadata.xml | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-)
(In reply to Michał Górny from comment #5) > Proxied maintainer retired. @monsieurp, now you're the primary maintainer. Not anymore.
(In reply to Patrice Clement from comment #7) > (In reply to Michał Górny from comment #5) > > Proxied maintainer retired. @monsieurp, now you're the primary maintainer. > > Not anymore. Where is the 'up for grabs' mail?
I bumped it, but should not be considered the maintainer
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=55a5981b722635a755ce9ea012666a735cddc4ff commit 55a5981b722635a755ce9ea012666a735cddc4ff Author: Matthew Thode <prometheanfire@gentoo.org> AuthorDate: 2019-08-11 18:53:16 +0000 Commit: Matthew Thode <prometheanfire@gentoo.org> CommitDate: 2019-08-11 18:53:32 +0000 net-im/mattermost-desktop-bin: 4.0.0 removal Bug: https://bugs.gentoo.org/662978 Package-Manager: Portage-2.3.69, Repoman-2.3.17 Signed-off-by: Matthew Thode <prometheanfire@gentoo.org> net-im/mattermost-desktop-bin/Manifest | 3 - .../mattermost-desktop-bin-4.0.0.ebuild | 89 ---------------------- 2 files changed, 92 deletions(-) https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=db390b19d8a74991ac44c81b8c900fac528aed61 commit db390b19d8a74991ac44c81b8c900fac528aed61 Author: Matthew Thode <prometheanfire@gentoo.org> AuthorDate: 2019-08-11 18:52:43 +0000 Commit: Matthew Thode <prometheanfire@gentoo.org> CommitDate: 2019-08-11 18:53:31 +0000 net-im/mattermost-desktop-bin: 4.2.3 bump Bug: https://bugs.gentoo.org/662978 Package-Manager: Portage-2.3.69, Repoman-2.3.17 Signed-off-by: Matthew Thode <prometheanfire@gentoo.org> net-im/mattermost-desktop-bin/Manifest | 3 + .../mattermost-desktop-bin-4.2.3.ebuild | 93 ++++++++++++++++++++++ 2 files changed, 96 insertions(+)
I missed that this wasn't a stable package. So perhaps I shouldn't have bothered with the security@ loop?
(In reply to Mart Raudsepp from comment #11) > I missed that this wasn't a stable package. So perhaps I shouldn't have > bothered with the security@ loop? Mart, we can still track it for cleanup etc. It just will not receive a GLSA. Overall, meh. No CVE references upstream. etc. Tree is clean.
