Discord now shows an upgrade prompt when running <0.0.7
Discord won't let you on until you upgrade. I successfully installed the upgrade with the following steps. If you don't understand how ti set up a local tree, do not try this at home. All risks are your own. I have /usr/local/portage already set up for situations like this. When you get the upgrade prompt from discord, select the Ubuntu (deb) version to download. In a terminal at root: # mv /from/path/you/saved/discord-0.0.7.deb /usr/portage/distfiles/ # mkdir -p /usr/local/portage/net-im/discord-bin # rsync -vas /usr/portage/net-im/discord-bin/ /usr/local/portage/net-im/discord-bin # cd /usr/local/portage/net-im/discord-bin # cp discord-bin-0.0.5.ebuild discord-bin-0.0.7.ebuild # ebuild /usr/local/portage/net-im/discord-bin/discord-bin-0.0.7.ebuild manifest # cd ~ --- confirm you did the above properly. I did inspect the ebuild for gotchas but it's really very simple. # emerge -pv net-im/discord-bin These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] net-im/discord-bin-0.0.7::local [0.0.5::gentoo] 0 KiB Total: 1 package (1 upgrade), Size of downloads: 0 KiB --- If all is good - emerge # emerge net-im/discord-bin Calculating dependencies... done! >>> Verifying ebuild manifests >>> Emerging (1 of 1) net-im/discord-bin-0.0.7::local >>> Installing (1 of 1) net-im/discord-bin-0.0.7::local >>> Jobs: 1 of 1 complete Load avg: 4.93, 3.41, 2.75 >>> Auto-cleaning packages... >>> No outdated packages were found on your system. * GNU info directory index is up-to-date. Easy-peasy - worked for me. I was able to log back onto discord.
I get an update prompt now that wants to download version 0.0.8
The 0.0.5 client now no longer allows you to sign in, showing only the update prompt. I've raised a PR to bump it to 0.0.8 at https://github.com/gentoo/gentoo/pull/10848.
Copying the old 0.0.5 ebuild and renaming seems to work for me. Any other notable changes required?
Just the version change worked for me as well, for the time being I therefore added that to my darkelf overlay, though I hope the pull request wont take long.
After less than a week, version 0.0.8 appears. The header here should be changed to '...version 0.0.8 bump' The sames steps I noted above still apply as a work-around.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fedf87c94bd1c080e014a2ac2da35f4458d26a3e commit fedf87c94bd1c080e014a2ac2da35f4458d26a3e Author: Thomas Deutschmann <whissi@gentoo.org> AuthorDate: 2019-01-19 05:42:02 +0000 Commit: Thomas Deutschmann <whissi@gentoo.org> CommitDate: 2019-01-19 05:42:02 +0000 net-im/discord-bin: bump to v0.0.8 Closes: https://bugs.gentoo.org/675674 Closes: https://bugs.gentoo.org/675554 Package-Manager: Portage-2.3.56, Repoman-2.3.12 Signed-off-by: Thomas Deutschmann <whissi@gentoo.org> net-im/discord-bin/Manifest | 2 +- ...in-0.0.5-r1.ebuild => discord-bin-0.0.8.ebuild} | 31 ++++++++++++---------- net-im/discord-bin/metadata.xml | 3 +++ 3 files changed, 21 insertions(+), 15 deletions(-)
