Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 476204 - >=app-text/libmspub-9999 fails to unpack
Summary: >=app-text/libmspub-9999 fails to unpack
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Office Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-08 17:16 UTC by henny.coenen
Modified: 2013-07-09 07:01 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (emergeinfo,6.27 KB, text/plain)
2013-07-08 17:16 UTC, henny.coenen
Details
friggin build log for whoever may care (build.log,1.48 KB, text/plain)
2013-07-08 20:37 UTC, henny.coenen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description henny.coenen 2013-07-08 17:16:59 UTC
Created attachment 352874 [details]
emerge --info

emerging libreoffice >=4 (at least trying to) portage fails with the following message:

 * Messages for package app-text/libmspub-9999:

 * ERROR: app-text/libmspub-9999 failed (prepare phase):
 *   The source directory '/var/tmp/portage/app-text/libmspub-9999/work/libmspub-9999' doesn't exist
 * 
 * Call stack:
 *            ebuild.sh, line 718:  Called __ebuild_main 'prepare'
 *   phase-functions.sh, line 954:  Called __dyn_prepare
 *   phase-functions.sh, line 368:  Called die
 * The specific snippet of code:
 *   		die "The source directory '${S}' doesn't exist"
 * 
 * If you need support, post the output of `emerge --info '=app-text/libmspub-9999'`,
 * the complete build log and the output of `emerge -pqv '=app-text/libmspub-9999'`.
 * The complete build log is located at '/var/tmp/portage/app-text/libmspub-9999/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-text/libmspub-9999/temp/environment'.
 * Working directory: '/usr/lib64/portage/pym'
 * S: '/var/tmp/portage/app-text/libmspub-9999/work/libmspub-9999'

Expected behavior: clean build
Reproducible: always
Comment 1 Rafał Mużyło 2013-07-08 18:40:44 UTC
:roll:

First of all, why libmspub-*9999* ? Live ebuilds are of extremely low stability.

Second, attach full build of app-text/libmspub-9999.
Comment 2 henny.coenen 2013-07-08 20:37:21 UTC
Created attachment 352880 [details]
friggin build log for whoever may care
Comment 3 henny.coenen 2013-07-08 20:38:02 UTC
Sigh...

You just couldn't take the extra second to ask "could you", now could you?
Let me explain this the same way you did:

First, libmspub-9999 gets pulled in by libreoffice >=4

Second, I know things may be unstable. However putting an unexisting source directory in an ebuild has nothing to do with instability. It's just a plain simple bug and an even easier fix.

If you would take the time to look at the build.log i just attached you might just see that. Might, if you're not to busy being annoyed and in that process, pissing me off.

And after your "words of wisdom" i can't even care if this gets fixed or not. You might as well close the bug report. I'll fix my "problem" myself.
Comment 4 Rafał Mużyło 2013-07-09 02:21:53 UTC
Bah, semantics...

Anyway, a couple things:

- neither 4.0.4.2 nor 4.1.0.1 pull the *live* ebuild of libmspub, so it seems somebody went postal on keywords file (perhaps even unmask)
- that build log looks as if a part of it was missing or something odd happened, as fetch didn't fail, yet the sources were *not* checked out (which *might* even be an eclass bug); on the other hand, EGIT_REPO_URI might be a little off

I'd add a thing or two, but if you don't care, neither do I.
Comment 5 Tomáš Chvátal (RETIRED) gentoo-dev 2013-07-09 06:23:18 UTC
Dear user,

next time please spent time reading what developers are telling you.

You are not needed to use any git ebuilds in order to merge something that is in stable tree. So you went mad when unmasking libreoffice or something among the line.

Note that if you report any bugs with live ebuilds in it you won't get support, because we can't ensure same test environment and fixing bugs that way is just simply insane.

Wrt your isssue with the libmspub there was wrong inherintance order that was now fixed in cvs. So in ~1 hour it will be propagated to mirrors.

Next time when filling bugs please try to avoid your feelings like "friggin build log" which actually shows the issue and helps developer to fix the problem. Or insulting other developers who simply ask about your setup to ensure you didn't put anything insane into it, which in this case you really did.
Comment 6 henny.coenen 2013-07-09 07:01:47 UTC
Tomáš,

Thank you for your clarity, but let's set this last thing straight.

I didn't get mad because i was asked to do something, neither did i get mad because someone tells me i have some insanity in my setup.

I got mad because of not what was said, but the way it was said. Come on, if i start a conversation with my eye rolling i can expect some reaction. Ok i admit that my second post was out of line but let's be fair.....

If you start your conversation with a could you provide some more info or sorry, i cannot / will not help you because you use some insane setting. Check this or that you've got a whole different kind of interaction.

Anyway, i think my point is clear. Thank you again for your clarity, it's appreciated.