| 1 |
On 9/29/06, Nick Geron <ngeron@×××××××.com> wrote: |
| 2 |
> Anyone know why the 3.0.2-r1 ebuild is blocking the current, stable |
| 3 |
> foomatic-db? |
| 4 |
> |
| 5 |
> [blocks B ] <net-print/foomatic-db-20050910 (is blocking |
| 6 |
> net-print/foomatic-filters-3.0.2-r1) |
| 7 |
> |
| 8 |
> I discovered this just before I did an update world. I can't find any |
| 9 |
> reference to a bug, there are no notes in the Changelog or within the |
| 10 |
> ebuild to suggest why it's blocking. The block wasn't in 3.0.2.ebuild |
| 11 |
> which I'm currently running with db-20050606. The closest reference I |
| 12 |
> could find had to do with filters and db overwriting each others files, |
| 13 |
> but that bug's resolution was a remerge of db (and that particular bug |
| 14 |
> is a year old). |
| 15 |
|
| 16 |
>From /usr/portage/foomatic-filters/ChangeLog: |
| 17 |
|
| 18 |
*foomatic-filters-3.0.2-r1 (05 May 2006) |
| 19 |
|
| 20 |
05 May 2006; Stefan Schweizer <genstef@g.o> |
| 21 |
+foomatic-filters-3.0.2-r1.ebuild: |
| 22 |
rev-bump foomatic-filters to force remerge, no changes apart from the |
| 23 |
foomatic-db-old block, stable from the beginning, bug 131533 |
| 24 |
|
| 25 |
Also, the block is on foomatic-db versions less than 20050910, which |
| 26 |
is currently stable. So if you have 20050910 installed, you should be |
| 27 |
ok. What does "emerge -pv foomatic-db" report? |
| 28 |
|
| 29 |
You might also add the --tree option to see what is pulling in |
| 30 |
foomatic-filters, what is going to be upgraded, or installed new, etc. |
| 31 |
|
| 32 |
-Richard |
| 33 |
-- |
| 34 |
gentoo-user@g.o mailing list |
Archives