Hi, I’m trying to create packages with obs, but near the end of the procedure it fails with this error:
104s] /var/tmp/rpm-tmp.OkIvYC: line 28: fg: no job control
104s] error: Bad exit status from /var/tmp/rpm-tmp.OkIvYC (%install)
I can’t get what it means, so here I am asking for your precious help.
This is the log:
while this is my spec file:
Any idea where I’m wrong? Thanks for your help.
On Thu 21 Mar 2013 11:56:01 PM CDT, gcala wrote:
Hi, I’m trying to create packages with obs, but near the end of the
procedure it fails with this error:
Code:
104s] /var/tmp/rpm-tmp.OkIvYC: line 28: fg: no job control
104s] error: Bad exit status from /var/tmp/rpm-tmp.OkIvYC
(%install) --------------------
I can’t get what it means, so here I am asking for your precious help.
This is the log:
‘SUSE Paste’ (http://paste.opensuse.org/69694292)
while this is my spec file:
‘SUSE Paste’ (http://paste.opensuse.org/66497283)
Any idea where I’m wrong? Thanks for your help.
Hi
No build requires on update-desktop-files for the %suse_update_file
macro;
Also you %post/%postun are incorrect;
http://en.opensuse.org/openSUSE:Packaging_Conventions_RPM_Macros#.25desktop_database_post_.2F_.25desktop_database_postun
You only need the new %desktop_database_X macro
You might want to peruse;
http://en.opensuse.org/openSUSE:Build_Service_cross_distribution_howto
Some good rpm housekeeping; put each individual build requires on a
separate entry as well as in alphabetical order 
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 12.3 (x86_64) Kernel 3.7.10-1.1-desktop
up 22:22, 3 users, load average: 0.14, 0.16, 0.12
CPU Intel® i5 CPU M520@2.40GHz | GPU Intel® Ironlake Mobile
I used %suse_update_desktop_file since without it I got this error:
ERROR: No sufficient Category definition: /home/abuild/rpmbuild/BUILDROOT/grooveoff-0.1-35.1.x86_64//usr/share/applications/grooveoff.desktop
I have this in my desktop file:
Categories=AudioVideo;Audio;Network;
On Fri 22 Mar 2013 09:26:01 AM CDT, gcala wrote:
malcolmlewis;2539258 Wrote:
> No build requires on update-desktop-files for the %suse_update_file
> macro;
I used %suse_update_desktop_file since without it I got this error:
Code:
ERROR: No sufficient Category
definition: /home/abuild/rpmbuild/BUILDROOT/grooveoff-0.1-35.1.x86_64//usr/share/applications/grooveoff.desktop
I have this in my desktop file:
Code:
Categories=AudioVideo;Audio;Network;
Hi
Yes, but the macro is in the update-desktop-files package, it’s just a
matter of adding;
BuildRequires: update-desktop-files
to your spec file.
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 12.3 (x86_64) Kernel 3.7.10-1.1-desktop
up 1:13, 4 users, load average: 0.10, 0.10, 0.11
CPU Intel® i5 CPU M520@2.40GHz | GPU Intel® Ironlake Mobile
Thanks malcolmlewis, that fixed the issue.
Well ****.
-edit-
Ha ha! All I said was c r a p, and it edited that out?
Makes it look like I’m guilty of much worse than I am.
Thanks for that too suse, on top of the original complaint of this post.
No wonder I never use the forums, just the mail lists.
-edit-
I am trying to google the same error, but those suse paste links are now empty, making this entire thread useless for anyone else who comes along later like this.
We can not see the actual log, and I can not compare my build log to yours, and we can not even guess at why the desktop files macro was suggested as a fix.
If I were to try adding that macro to my .spec, it would just be a totally blind guess with no idea if that even makes any sense in my case. The package in my case is just “tmux”, and only fails on the older opensuse build targets like 11.1, but builds fine on 11.3 and later (after I fixed another problem by providing a newer libevent in the same obs project). I don’t know if it even HAS any desktop files so I’m guessing I don’t actually have the same error as you. I just have some other problem that just happens to result in “fg no job control”. fg and job control are generic shell features, nothing specific to desktop files.
Seeing this thread, but not seeing what this thread is talking about, is pretty frustrating.
So, whoever is responsible for the suse paste site, here is why the pastes should not be deleted.
To everyone else who might use suse paste, here is why you should mostly not use it.
–
bkw