| 1 |
On Wed, Oct 17 2012, Neil Bothwick wrote: |
| 2 |
|
| 3 |
> On Wed, 17 Oct 2012 16:18:50 -0400, Allan Gottlieb wrote: |
| 4 |
> |
| 5 |
>> A few months ago a procedure was given for converting from testing to |
| 6 |
>> stable (e.g. ~amd64-->~amd) by essentially waiting for stable to catch |
| 7 |
>> up. |
| 8 |
>> |
| 9 |
>> I believe the basic idea was to unmask a bunch of packages and then as |
| 10 |
>> stable catches up, remove the unmasks. I also believe there was some |
| 11 |
>> automated way to generate the unmasks and maybe a way to see when each |
| 12 |
>> is not needed. |
| 13 |
>> |
| 14 |
>> Can someone repost this msg? |
| 15 |
>> I foolishly did not save it and now want to convert a system to stable |
| 16 |
>> and can afford to do so slowly. |
| 17 |
> |
| 18 |
> You can generate the list with |
| 19 |
> |
| 20 |
> qlist -ICv | sed -e 's/^/~/' -e 's/-r[1-9]$//' |
| 21 |
>>/etc/portage/package.mask/goingstable |
| 22 |
> |
| 23 |
> This allows revision updates, which is useful as they usually contain bug |
| 24 |
> or security fixes, but doesn't allow any higher versions. |
| 25 |
> |
| 26 |
> Occasionally running eix-test-obsolete will let you know which entries |
| 27 |
> have become redundant because stable has caught up with them. |
| 28 |
|
| 29 |
Thanks you both (I incorporated the .use-->.mask) change). |
| 30 |
allan |
Archives