| 1 |
On Wednesday 01 November 2006 16:03, Neil Bothwick wrote: |
| 2 |
> On Wed, 1 Nov 2006 14:54:29 +0100, Bo Ørsted Andresen wrote: |
| 3 |
> > > > emerge -v java-config java-config-wrapper |
| 4 |
> > > |
| 5 |
> > > That will only update the highest slotted java-config package [...]. |
| 6 |
> > |
| 7 |
> > Just wanted to point out that while this is true for the latest stable |
| 8 |
> > portage it is no longer true for the latest ~arch portage. The relevant |
| 9 |
> > bugs are: |
| 10 |
> > |
| 11 |
> > https://bugs.gentoo.org/show_bug.cgi?id=150361 |
| 12 |
> > https://bugs.gentoo.org/show_bug.cgi?id=152175 |
| 13 |
> |
| 14 |
> A quick glance at those gives the impression that this only applies to |
| 15 |
> updates. My problem with updating cyrus-sasl required re-emerging the |
| 16 |
> same versions of java-config, in which case "emerge -1a java-config" only |
| 17 |
> offers to re-emerge java-config-2. This is with portage-2.1.2_rc1-r1 |
| 18 |
|
| 19 |
You're right, sorry. `emerge -1a java-config:{0,2}` would work with |
| 20 |
portage-2.1.2 though. |
| 21 |
|
| 22 |
-- |
| 23 |
Bo Andresen |
Archives