1 |
Thanks for the quick response Richard:) |
2 |
|
3 |
I did see that note, but i wasn't sure what they meant by |
4 |
'foomatic-db-old block'. On that note, looking at it again I see my |
5 |
brain farted. |
6 |
|
7 |
I know I can force installs if so desired. To answer your question, |
8 |
portage will update to 20050910 without complaint, however, I was |
9 |
looking for a good explaination of why it was blocked. I want to |
10 |
determine if updating and forcing/ignoring foomatic-filters in an update |
11 |
word would result in another weekend of cups debugging. If |
12 |
'foomatic-db-old block' means that I just have to remerge one of them |
13 |
again, like in that old bug report I found, then great. No problem. |
14 |
I've just read too many forum posts with 'I upgraded with stable package |
15 |
X and now everythings borked.' |
16 |
|
17 |
Equeries tell me that filters are required by the foomatic-db and |
18 |
db-engine - effectively foomatic/printing. |
19 |
|
20 |
Has anyone done a recent printing system upgrade? Any reported trouble |
21 |
running filters 3.0.2-r1 with db 20050910? Are the filters identical |
22 |
between 3.0.2 and 3.0.2-r1? |
23 |
|
24 |
-nick |
25 |
|
26 |
|
27 |
Richard Fish wrote: |
28 |
> On 9/29/06, Nick Geron <ngeron@×××××××.com> wrote: |
29 |
> |
30 |
>> Anyone know why the 3.0.2-r1 ebuild is blocking the current, stable |
31 |
>> foomatic-db? |
32 |
>> |
33 |
>> [blocks B ] <net-print/foomatic-db-20050910 (is blocking |
34 |
>> net-print/foomatic-filters-3.0.2-r1) |
35 |
>> |
36 |
>> I discovered this just before I did an update world. I can't find any |
37 |
>> reference to a bug, there are no notes in the Changelog or within the |
38 |
>> ebuild to suggest why it's blocking. The block wasn't in 3.0.2.ebuild |
39 |
>> which I'm currently running with db-20050606. The closest reference I |
40 |
>> could find had to do with filters and db overwriting each others files, |
41 |
>> but that bug's resolution was a remerge of db (and that particular bug |
42 |
>> is a year old). |
43 |
> |
44 |
> |
45 |
>> From /usr/portage/foomatic-filters/ChangeLog: |
46 |
> |
47 |
> |
48 |
> *foomatic-filters-3.0.2-r1 (05 May 2006) |
49 |
> |
50 |
> 05 May 2006; Stefan Schweizer <genstef@g.o> |
51 |
> +foomatic-filters-3.0.2-r1.ebuild: |
52 |
> rev-bump foomatic-filters to force remerge, no changes apart from the |
53 |
> foomatic-db-old block, stable from the beginning, bug 131533 |
54 |
> |
55 |
> Also, the block is on foomatic-db versions less than 20050910, which |
56 |
> is currently stable. So if you have 20050910 installed, you should be |
57 |
> ok. What does "emerge -pv foomatic-db" report? |
58 |
> |
59 |
> You might also add the --tree option to see what is pulling in |
60 |
> foomatic-filters, what is going to be upgraded, or installed new, etc. |
61 |
> |
62 |
> -Richard |
63 |
-- |
64 |
gentoo-user@g.o mailing list |