Re: [gentoo-user] new foomatic-filters ebuild

[Nick Geron]

Thanks for the quick response Richard:)

I did see that note, but i wasn't sure what they meant by 
'foomatic-db-old block'.  On that note, looking at it again I see my 
brain farted.

I know I can force installs if so desired.  To answer your question, 
portage will update to 20050910 without complaint, however, I was 
looking for a good explaination of why it was blocked. I want to 
determine if updating and forcing/ignoring foomatic-filters in an update 
word would result in another weekend of cups debugging.  If 
'foomatic-db-old block' means that I just have to remerge one of them 
again, like in that old bug report I found, then great.  No problem. 
I've just read too many forum posts with 'I upgraded with stable package 
X and now everythings borked.'

Equeries tell me that filters are required by the foomatic-db and 
db-engine - effectively foomatic/printing.

Has anyone done a recent printing system upgrade?  Any reported trouble 
running filters 3.0.2-r1 with db 20050910?  Are the filters identical 
between 3.0.2 and 3.0.2-r1?

-nick


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