HI David
when trying that on my laptop it is giving me errors about no more
space on the device: I will reinstall the Sailfish SDK tomorrow.
But it just so happens that apple-pip (my Macbook-air) has a much
bigger brother Butschgi - a Mac Tower ..
So on Butschgi, with project Demo4 again. (C++ style comments added
afterwards to explain what I am doing).
MacPro-4:~ chrislamb$ ssh -p 2222 -i ~/.ssh/mer-qt-creator-rsa
mersdk@localhost
/* first following your initial instructions, probably will go wrong
(oh ye of little faith) */
-bash-3.2$ cd /
-bash-3.2$ export PKG=Demo4
-bash-3.2$ cd /home/mersdk/SailfishProjects/Demo4/Demo4/
-bash-3.2$ cd rpm
-bash-3.2$ pwd
/home/mersdk/SailfishProjects/Demo4/Demo4/rpm
-bash-3.2$ ls -l
total 4
-rwx------ 1 mersdk mersdk 701 Apr 22 22:03 Demo4.yaml
-bash-3.2$ (cd ..; make distclean 2>/dev/null; tar cf - --exclude /rpm
--exclude .git/ --transform "s_./_${PKG}-0.1/_" ./) | bzip2 >
${PKG}-0.1.tar.bz2
-bash-3.2$ ls -l
total 12
-rwx------ 1 mersdk mersdk 5252 Apr 22 22:14 Demo4-0.1.tar.bz2
-rwx------ 1 mersdk mersdk 701 Apr 22 22:03 Demo4.yaml
-bash-3.2$ specify
Warning: NEW spec file created: Demo4.spec, maybe customized spec
content is needed!
-bash-3.2$ ls -l
total 16
-rwx------ 1 mersdk mersdk 5252 Apr 22 22:14 Demo4-0.1.tar.bz2
-rwx------ 1 mersdk mersdk 770 Apr 22 22:15 Demo4.spec
-rwx------ 1 mersdk mersdk 701 Apr 22 22:03 Demo4.yaml
-bash-3.2$ cd ..
-bash-3.2$ mb build -t SailfishOS-i486-x86 rpm/Demo4.spec
Building rpm/Demo4.spec for SailfishOS-i486-x86
Checking dependencies...
Loading repository data...
Reading installed packages...
'pkgconfig(QtCore)=4.8.0' not found in package names. Trying capabilities.
No provider of 'pkgconfig(QtCore) = 4.8.0' found.
'rpm-build' is already installed.
No update candidate for 'rpm-build-4.9.1.2-1.21.i486'. The highest
available version is already installed.
Resolving package dependencies...
Nothing to do.
Setting up temporary specfile for Demo4 from rpm/Demo4.spec
rsyncing source...
run rpmbuild
error: Bad owner/group: /home/mersdk/rpmbuild/SOURCES/Demo4.tar.bz2
/* went wrong as expected, now about to try the fix from your latest mail */
/* initial contents of /srv/mer/targets/SailfishOS-i486-x86/etc/passwd */
-bash-3.2$ head -n 50 /srv/mer/targets/SailfishOS-i486-x86/etc/passwd
root:x:0:0:root:/root:/bin/bash
bin:x:1:1:bin:/bin:/sbin/nologin
daemon:x:2:2:daemon:/sbin:/sbin/nologin
adm:x:3:4:adm:/var/adm:/sbin/nologin
lp:x:4:7:lp:/var/spool/lpd:/sbin/nologin
sync:x:5:0:sync:/sbin:/bin/sync
shutdown:x:6:0:shutdown:/sbin:/sbin/shutdown
halt:x:7:0:halt:/sbin:/sbin/halt
mail:x:8:12:mail:/var/spool/mail:/sbin/nologin
uucp:x:10:14:uucp:/var/spool/uucp:/sbin/nologin
operator:x:11:0:operator:/root:/sbin/nologin
games:x:12:100:games:/usr/games:/sbin/nologin
gopher:x:13:30:gopher:/var/gopher:/sbin/nologin
ftp:x:14:50:FTP User:/var/ftp:/sbin/nologin
nobody:x:99:99:Nobody:/:/sbin/nologin
dbus:x:81:81:System message bus:/:/sbin/nologin
nemo:x:1000:1000::/home/nemo:/bin/bash
-bash-3.2$
/* now running your fix, adding mersdk password */
-bash-3.2$ grep mersdk /etc/passwd >>
/srv/mer/targets/SailfishOS-i486-x86/etc/passwd
-bash-3.2$
/* mersdk entry is added, see last line */
-bash-3.2$ head -n 50 /srv/mer/targets/SailfishOS-i486-x86/etc/passwd
root:x:0:0:root:/root:/bin/bash
bin:x:1:1:bin:/bin:/sbin/nologin
daemon:x:2:2:daemon:/sbin:/sbin/nologin
adm:x:3:4:adm:/var/adm:/sbin/nologin
lp:x:4:7:lp:/var/spool/lpd:/sbin/nologin
sync:x:5:0:sync:/sbin:/bin/sync
shutdown:x:6:0:shutdown:/sbin:/sbin/shutdown
halt:x:7:0:halt:/sbin:/sbin/halt
mail:x:8:12:mail:/var/spool/mail:/sbin/nologin
uucp:x:10:14:uucp:/var/spool/uucp:/sbin/nologin
operator:x:11:0:operator:/root:/sbin/nologin
games:x:12:100:games:/usr/games:/sbin/nologin
gopher:x:13:30:gopher:/var/gopher:/sbin/nologin
ftp:x:14:50:FTP User:/var/ftp:/sbin/nologin
nobody:x:99:99:Nobody:/:/sbin/nologin
dbus:x:81:81:System message bus:/:/sbin/nologin
nemo:x:1000:1000::/home/nemo:/bin/bash
mersdk:x:1001:1001::/home/mersdk:/bin/bash
/* ruing mb build again .... fingers in ears ...*/
-bash-3.2$ mb build -t SailfishOS-i486-x86 rpm/Demo4.spec
Building rpm/Demo4.spec for SailfishOS-i486-x86
Checking dependencies...
Loading repository data...
Reading installed packages...
'pkgconfig(QtCore)=4.8.0' not found in package names. Trying capabilities.
No provider of 'pkgconfig(QtCore) = 4.8.0' found.
'rpm-build' is already installed.
No update candidate for 'rpm-build-4.9.1.2-1.21.i486'. The highest
available version is already installed.
Resolving package dependencies...
Nothing to do.
Setting up temporary specfile for Demo4 from rpm/Demo4.spec
rsyncing source...
run rpmbuild
error: Bad owner/group: /home/mersdk/rpmbuild/SOURCES/Demo4.tar.bz2
-bash-3.2$
/* bummer ...*/
Perhaps when your QA machine is up and running you can test this. I
think the best thing I can do tonight is go to bed ...
Thanks so far
Chris
p.s. Am I the only one out there who can't build / deploy?
Zitat von "David Greaves" <david.grea...@jollamobile.com>:
On 22/04/13 21:46, christopher.l...@thurweb.ch wrote:
Hi David
thanks for your stoic patience: unfortunately that did not work either ...
No problem - cc'ing the list for others who may be following.
To the basics - my host is OSX (but I get the same results on a Win
7 machine)
Always good to know and sensible to report. Hopefully not an issue
in this case.
With yet another new project - Demo4, with the only changes being
those that you
suggest to the .yarl file.
No attempt to build from Qt Creator
Logging on to the SDK as mersdk:
Here is a copy of my shell:
Looks 100% correct
...
run rpmbuild
error: Bad owner/group: /home/mersdk/rpmbuild/SOURCES/Demo4.tar.bz2
Try this:
grep mersdk /etc/passwd >> /srv/mer/targets/SailfishOS-i486-x86/etc/passwd
and try the mb command again:
mb build -t SailfishOS-i486-x86 rpm/Demo4.spec
Sorry I can't test this properly as I'm rebuilding my QA machine tonight - I
just panicked because I thought I'd lost my OS-X partition! Luckily not :)
David
As I am connected with mersdk, and mersdk is the owner and group I
am more than
a little lost as to what is wrong ...
It's a little complicated but not rocket science :)
Your build is happening on a virtual machine which is the build-engine - you
know this part. The build engine contains the development tools and
compilers etc.
However, inside that build engine are what we call 'targets'. A target is a
very, very light almost-VM. We will have targets for the emulator and for
different devices (including ARM ones). It is the passwd file inside the
*target* that does not understand the username.
It's an annoying one - happily I think I fixed it this weekend.
Chris
Zitat von "David Greaves" <david.grea...@jollamobile.com>:
On 22/04/13 20:18, christopher.l...@thurweb.ch wrote:
Hi David
I am a microstep further ...8-)
logged as mersdk, and with a freshly backed Demo3 project I now
get this far:
Building rpm/Demo3.spec for SailfishOS-i486-x86
Checking dependencies...
Loading repository data...
Reading installed packages...
'pkgconfig(QtCore)>=4.8.0' not found in package names. Trying
capabilities.
That confused me too.
Rather unhelpfully it does *not* say "never mind, found
pkgconfig(QtCore)>=4.8.0
in capabilities; all is well" :)
As a test, I changed it to 4.9.0 and got:
'pkgconfig(QtCore)>=4.9.0' not found in package names. Trying capabilities.
No provider of 'pkgconfig(QtCore) >= 4.9.0' found.
So that's what it would say if it had a problem.
error: Bad owner/group: /home/mersdk/rpmbuild/SOURCES/Demo3.tar.bz2
Lets try cleaning up:
cd <your app dir>
Then:
rm -rf /home/mersdk/rpmbuild/*
sudo chown -R mersdk:mersdk .
And build:
mb build -t SailfishOS-i486-x86 rpm/Demo3.spec
David
_______________________________________________
SailfishOS.org Devel mailing list
