The latest stable/testing version gets pulled in during my updates instead of the live version. Changed the version number should fix this. Thanks!
I am using neomutt-9999 as well, but for me an update is not pulling in any other version. What did you add to package.accept_keywords?
(In reply to Nicolas Bock from comment #1) > I am using neomutt-9999 as well, but for me an update is not pulling in any > other version. What did you add to package.accept_keywords? I have the following in that file: mail-client/neomutt **
Try this: =mail-client/neomutt-9999 **
(In reply to Nicolas Bock from comment #3) > Try this: > > =mail-client/neomutt-9999 ** That seems to have the same outcome for me. A world update "emerge -avuND @world" still tries to pull in the non-live version. Shouldn't this live version be named 99999999 regardless? From my discussion on IRC, that was what I was told.
Could you make sure that you have only _one_ entry in package.accept_keywords for neomutt? Regarding your question: According to https://devmanual.gentoo.org/ebuild-writing/file-format/index.html our policy is to name live ebuilds ${PN}-9999. I am not opposed to renaming it, but that would go against policy and is unusual. Could you first make sure that you have only one entry for neomutt in /etc/portage?
mail-client/neomutt-9999 is obviously wrong. For packages which uses yyyymmdd as version, the live ebuild needs to have an equal amount of 9s, otherwise the normal versions will be seen as newer. If you're on an ~arch system, the only way to get the live version is to actively mask anything >9999, which is not how this is supposed to work.
Ok, I was able to track down my issue. I am using ~amd64 on two of my machines and when I install neomutt using "emerge -av neomutt", it still does not work. On my stable machines, this DOES work, when including the version in my package.accept_keywords. On my Testing machines, however, it does not work as expected. I brought this up in the IRC channel again and had more people saying the maintainer should make the live version 99999999 in cases such as these. I see there are 48 packages in the Portage tree that also follow this convention.
Thanks for the additional information @rypervenche. I hadn't tested this on an unstable system. I'll fix it. Thanks!
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4bf6c2fec88af9e8ed9e380733eccb02b66d17e3 commit 4bf6c2fec88af9e8ed9e380733eccb02b66d17e3 Author: Nicolas Bock <nicolasbock@gentoo.org> AuthorDate: 2018-04-04 22:15:49 +0000 Commit: Nicolas Bock <nicolasbock@gentoo.org> CommitDate: 2018-04-04 22:16:51 +0000 mail-client/neomutt: Bump live ebuild version On unstable systems (or once a regular version of neomutt is made stable) the live ebuild version of '9999' will not be the latest version and a user will not be able to easily install the live ebuild. This change renames it to `99999999`. Thanks to contact@ryper.org for pointing this out! Closes: https://bugs.gentoo.org/650434 Package-Manager: Portage-2.3.24, Repoman-2.3.6 mail-client/neomutt/{neomutt-9999.ebuild => neomutt-99999999.ebuild} | 0 1 file changed, 0 insertions(+), 0 deletions(-)
