I'd like to stabilize app-misc/rpick-0.5.1. I've been using it for more than 30 days and it works well.
amd64 stable
Hi Agostino! I am confident that the test failure is only a problem in the tests and not a problem in the code that users use. I fixed this issue upstream a month ago or so: https://gitlab.com/bowlofeggs/rpick/-/commit/9d3e9b704e48b9dedb3612f40735f24dfc94f598 You can see that that patch only touches the tests. How shall we proceed? I could make a new upstream release, or I could make a new -r1 ebuild that brings that patch in? Or is it acceptable to stabilize this version given that it is only the test suite that fails?
(In reply to Randy Barlow from comment #2) > Hi Agostino! > > I am confident that the test failure is only a problem in the tests and not > a problem in the code that users use. I fixed this issue upstream a month > ago or so: > > https://gitlab.com/bowlofeggs/rpick/-/commit/ > 9d3e9b704e48b9dedb3612f40735f24dfc94f598 > > You can see that that patch only touches the tests. > > How shall we proceed? I could make a new upstream release, or I could make a > new -r1 ebuild that brings that patch in? Or is it acceptable to stabilize > this version given that it is only the test suite that fails? Hello Randy, I guess that make an r1 is fine.
ppc64 stable
Hi Agostino! I decided to tag a new rpick release upstream because I have a new feature and this way that fix for 32-bit arches should be included: https://crates.io/crates/rpick/0.6.1 https://github.com/gentoo/gentoo/pull/15706 Thus, I think we can probably just close this ticket, and I'll open a new one in a few weeks once the new release has had some testing time. Thanks for testing!
