Bugzilla Bug 89663

There's a new version of libirman, that specifically adds 2.6 kernel support.

Reproducible: Always
Steps to Reproduce:

Created an attachment (id=56664) [details]
PICShared patch for libirman 0.4.3

Created an attachment (id=56665) [details]
destination dir patch for libirman 0.4.3

These patches together with a version number bump of the ebuild work for me.

*** Bug 128643 has been marked as a duplicate of this bug. ***

Node's updated patch files work fine for me, on amd64 with GCC 4 as long as I
comment out the format patch in the ebuild and bump the gcc4 patch's number.

The gcc4 patch shouldn't be needed anymore, according to the announcement of
libirman 0.4.4 it incorporates these already.  Haven't tested it though.

unfortunatly the masking broke dependencies of lcdproc:



markus@powerbook ~/gentoo-x86/app-misc/lcdproc $ repoman scan

Setting paths:
PORTDIR = "/home/markus/gentoo-x86"
PORTDIR_OVERLAY = ""

RepoMan scours the neighborhood...

  DEPEND.bad                     4
   app-misc/lcdproc/lcdproc-0.5.0.ebuild: ~x86(default-linux/x86/2006.1)
['media-libs/libirman']
   app-misc/lcdproc/lcdproc-0.5.0.ebuild: ~x86(default-linux/x86/no-nptl)
['media-libs/libirman']
   app-misc/lcdproc/lcdproc-0.5.0.ebuild:
~x86(default-linux/x86/2006.1/desktop) ['media-libs/libirman']
   app-misc/lcdproc/lcdproc-0.5.0.ebuild: ~x86(hardened/x86/2.6)
['media-libs/libirman']
  RDEPEND.bad                    4
   app-misc/lcdproc/lcdproc-0.5.0.ebuild: ~x86(default-linux/x86/2006.1)
['media-libs/libirman']
   app-misc/lcdproc/lcdproc-0.5.0.ebuild: ~x86(default-linux/x86/no-nptl)
['media-libs/libirman']
   app-misc/lcdproc/lcdproc-0.5.0.ebuild:
~x86(default-linux/x86/2006.1/desktop) ['media-libs/libirman']
   app-misc/lcdproc/lcdproc-0.5.0.ebuild: ~x86(hardened/x86/2.6)
['media-libs/libirman']
  digest.assumed                 2
   digest-lcdproc-0.4.5::lcdproc-0.4.5.tar.bz2
   digest-lcdproc-0.5.0::lcdproc-0.5.0.tar.gz

markus@powerbook ~/gentoo-x86/app-misc/lcdproc $

app-misc/lirc-0.8.0-r5
dev-python/irman-python-0.1

have broken dependencies as well...

(In reply to comment #7)
> app-misc/lirc-0.8.0-r5
> dev-python/irman-python-0.1
> 
> have broken dependencies as well...
> 

All deps fixed (2 extra maskings + 1 use.mask for zzam).

Could you please remove the package mask for app-misc/lcdproc and put it irman
on use mask?
I don't think there's any reason for removing the package completely just
because a new version has the possibility of using irman.

Unfortunately, the masking breaks me since I'm using an irman with lirc.  If
the only reason libirman is being deleted from the tree is because it's lacking
a maintainer, I'd be happy to take it up.  Anyone have pointers on how to do
this?  My brief searching didn't turn up anything obvious.

Created an attachment (id=97431) [details]
ebuild for libirman-0.4.4

Created an attachment (id=97432) [details]
destination dir patch for libirman 0.4.4

The mask on lcdproc breaks my MythTV computer/personal video recorder. Will
lcdproc be unmasked again?

(In reply to comment #9)
> Could you please remove the package mask for app-misc/lcdproc and put it irman
> on use mask?
> I don't think there's any reason for removing the package completely just
> because a new version has the possibility of using irman.
> 

done.  I had misread my dep report earlier :x

If I understood right: libirman is scheduled for going away on Oct 19th.

So, what is the suggested replacement for libirman ?

(In reply to comment #15)
> If I understood right: libirman is scheduled for going away on Oct 19th.
> 
> So, what is the suggested replacement for libirman ?
> 

There isn't a suggested replacement; this bug has been open for 1.5 years.

Hmm so as one of my (proxy)maintained packages is affected, I'll take it if
there are no objections

(In reply to comment #17)
> Hmm so as one of my (proxy)maintained packages is affected, I'll take it if
> there are no objections

Nothing at all, but please make sure to fix the outstanding bugs ! :-)

Took it, bumped it, should be fine now :)