| Summary: | gaim-2.0.0_beta1 emerge fails at "Applying gaim-0.76-xinput.patch" | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Tony Skraba <tonyskraba> |
| Component: | Current packages | Assignee: | Gentoo Net-im project <net-im> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | r0bertz, tonyskraba, xoen.gnu |
| Priority: | High | ||
| Version: | 2005.1 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | the file requested to be included | ||
Created attachment 75172 [details]
the file requested to be included
My apologies if this is completely incorrect. I typically do not unmask things (only sun-jdk besides this, and that works fine.) Hopefully this is useful information. Again, my apologies if I'm going about this all wrong. Same bug here... There are 2 "solutions" : 1) USE="-cjk" 2) Modify the ebuild to prevent to use that patch CJK USE flag stands for Cinese/Japanise/Korean and it is no useful for everyone. *** Bug 116182 has been marked as a duplicate of this bug. *** The patch is removed from -r1 ebuild |
As per the summary, gaim-2.0.0_beta1 emerge fails at the point where it the emerge tries to use the gaim-0.76-xinput.patch file. To file "/etc/portage/package.keywords" I added the line: net-im/gaim ~x86 To file "/etc/portage/package.unmask" I added the line: net-im/gaim Did an "emerge --sync" then "emerge --deep --update --newuse gaim". Results? After the md5 check (and warning message about plugins,) >>> Unpacking source... >>> Unpacking gaim-2.0.0beta1.tar.bz2 to /var/tmp/portage/gaim-2.0.0_beta1/work * Applying gaim-0.76-xinput.patch ... * Failed Patch: gaim-0.76-xinput.patch ! * ( /usr/portage/net-im/gaim/files/gaim-0.76-xinput.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/gaim-2.0.0_beta1/temp/gaim-0.76-xinput.patch-3159.out !!! ERROR: net-im/gaim-2.0.0_beta1 failed. !!! Function epatch, Line 350, Exitcode 0 !!! Failed Patch: gaim-0.76-xinput.patch! !!! If you need support, post the topmost build error, NOT this status message. Including the file as an attachment.