| 1 |
On Tue, 17 May 2016 08:50:25 +0200 |
| 2 |
Marcin Mirosław <marcin@×××××.pl> wrote: |
| 3 |
|
| 4 |
> W dniu 16.05.2016 o 10:45, Dirkjan Ochtman pisze: |
| 5 |
> > On Mon, May 16, 2016 at 3:39 AM, Brian Dolbec <dolsen@g.o> |
| 6 |
> > wrote: |
| 7 |
> >> repoman-2.3.0_rc1 is the stage2 rewrite code. The checks are now |
| 8 |
> >> modular, and using the portage plugin system. The system is not yet |
| 9 |
> >> fully plug and play. Those changes will take place in the stage3 |
| 10 |
> >> re-writes. |
| 11 |
> > |
| 12 |
> > Thanks for working on this, it sounds great! |
| 13 |
> |
| 14 |
> But it doesn't sounds so great for every every user;) |
| 15 |
> https://bugs.gentoo.org/show_bug.cgi?id=583252 |
| 16 |
> |
| 17 |
> |
| 18 |
> |
| 19 |
|
| 20 |
There was a reason it was released as _rc1, And it was fixed real |
| 21 |
quick with _rc1-r1, it was a small easy fix. Incidentally , the error |
| 22 |
was in the portage code, not the new repoman code which your reply |
| 23 |
above seems to indicate. For those of you that might have installed |
| 24 |
_rc1, the easy fix is install repoman, then upgrade to _rc1-r1, then |
| 25 |
unmerge repoman if you don't want it. |
| 26 |
|
| 27 |
For those that may not know, _rc stands for release candidate, when |
| 28 |
major changes are done. Code is often released as a release candidate to |
| 29 |
shake out any missed change that might be needed but missed due to |
| 30 |
configuration and other conditions on the developers systems. |
| 31 |
|
| 32 |
Thank you to those that tested it quite thoroughly after I released it. |
| 33 |
Including finding the fix right away :D |
| 34 |
|
| 35 |
-- |
| 36 |
Brian Dolbec <dolsen> |
Archives