[opensuse-buildservice] Problems with Ubuntu Dapper (6.06) on local buildservice installation
Good morning colleagues, yesterday I played around with configuring Ubuntu Distros on a local installed opensuse buildservice. I imported all packages for Ubuntu Dapper into /srv/obs/build/UBUNTU:DAPPER/standard/{x86_64,i586}/:full (*_all.debs are in both directories available). I pushed all packages, means from Ubuntus Repositories named main, restricted, universe multiverse). Now I get a message which tells me that "nothing provides libasound2 > 1.0.10 needed by libesd-alsa0" Which is somehow strange. libasound2 is there in version 1.0.10-2ubuntu4. Reading the binary package description on http://packages.ubuntu.com/dapper/libs/libesd-alsa0 it needs libasound2 (>> 1.0.10) The operator >> means >= so, 1.0.10-2ubuntu4 (the version in the repositories for dapper) is definitly greater then 1.0.10. How can someone fix this? Thx for you help in advance :) \sh -- Stephan Hermann eMail: sh@sourcecode.de Blog: http://linux.blogweb.de/ JID: sh@linux-server.org OSS-Developer and Admin
On Wed, Jul 11, 2007 at 08:43:25AM +0200, Stephan Hermann wrote:
yesterday I played around with configuring Ubuntu Distros on a local installed opensuse buildservice. I imported all packages for Ubuntu Dapper into /srv/obs/build/UBUNTU:DAPPER/standard/{x86_64,i586}/:full (*_all.debs are in both directories available). I pushed all packages, means from Ubuntus Repositories named main, restricted, universe multiverse).
Now I get a message which tells me that
"nothing provides libasound2 > 1.0.10 needed by libesd-alsa0"
Which is somehow strange. libasound2 is there in version 1.0.10-2ubuntu4. Reading the binary package description on http://packages.ubuntu.com/dapper/libs/libesd-alsa0 it needs libasound2 (>> 1.0.10) The operator >> means >= so, 1.0.10-2ubuntu4 (the version in the repositories for dapper) is definitly greater then 1.0.10.
No '>>' means '>', not '>='. Looks like you're either using an old version of the build service (the line containing 'verscmp' in build/Build.pm should read my $vv = Build::Rpm::verscmp($pv, $rv, $config->{'type'} eq 'spec' ? 1 : 0); ), or you have the 'rpm' package in the preinstall list of your ubuntu configuration. What's happening is that the build service uses rpm comparison rules for your deb package. For rpm, libasound2 > 1.0.10 is *not* true for 1.0.10-2ubuntu4. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi Michael, Am Mittwoch, den 11.07.2007, 11:34 +0200 schrieb Michael Schroeder:
On Wed, Jul 11, 2007 at 08:43:25AM +0200, Stephan Hermann wrote:
yesterday I played around with configuring Ubuntu Distros on a local installed opensuse buildservice. I imported all packages for Ubuntu Dapper into /srv/obs/build/UBUNTU:DAPPER/standard/{x86_64,i586}/:full (*_all.debs are in both directories available). I pushed all packages, means from Ubuntus Repositories named main, restricted, universe multiverse).
Now I get a message which tells me that
"nothing provides libasound2 > 1.0.10 needed by libesd-alsa0"
Which is somehow strange. libasound2 is there in version 1.0.10-2ubuntu4. Reading the binary package description on http://packages.ubuntu.com/dapper/libs/libesd-alsa0 it needs libasound2 (>> 1.0.10) The operator >> means >= so, 1.0.10-2ubuntu4 (the version in the repositories for dapper) is definitly greater then 1.0.10.
No '>>' means '>', not '>='. Looks like you're either using an old version of the build service (the line containing 'verscmp' in build/Build.pm should read
Well, even if ">>" is ">" 1.0.10-2ubuntu4 is greater then 1.0.10 (I just talked to an debian maintainer, who told me >> means >=, but I was unsure, because I thought as well, ">>" means ">"). but regarding the buildservice: combots-buildserver:/usr/lib/obs/server/build # rpm -qa|grep obs obs-server-0.1.1-29.1 obs-worker-0.1.1-29.1 obs-api-0.1.1-29.1 That's what came in yesterday ;) But you are right, the /usr/lib/obs/server/build/* is old (strange, because the build.rpm under /usr/lib/build/ is correct...) Can I just copy the content of /usr/lib/build directory to /usr/lib/obs/server/build/? Regards, \sh -- Stephan Hermann eMail: sh@sourcecode.de Blog: http://linux.blogweb.de/ JID: sh@linux-server.org OSS-Developer and Admin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, Jul 11, 2007 at 12:26:04PM +0200, Stephan Hermann wrote:
Well, even if ">>" is ">" 1.0.10-2ubuntu4 is greater then 1.0.10 (I just talked to an debian maintainer, who told me >> means >=, but I was unsure, because I thought as well, ">>" means ">").
In some old debian versions '>' meant 'greater or equal', so they introduced '>>' for 'greater' and discouraged the use of '>'.
but regarding the buildservice:
combots-buildserver:/usr/lib/obs/server/build # rpm -qa|grep obs obs-server-0.1.1-29.1 obs-worker-0.1.1-29.1 obs-api-0.1.1-29.1
That's what came in yesterday ;) But you are right, the /usr/lib/obs/server/build/* is old (strange, because the build.rpm under /usr/lib/build/ is correct...)
Can I just copy the content of /usr/lib/build directory to /usr/lib/obs/server/build/?
Yes, that should work. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
HI, Am Mittwoch, den 11.07.2007, 13:10 +0200 schrieb Michael Schroeder:
On Wed, Jul 11, 2007 at 12:26:04PM +0200, Stephan Hermann wrote:
Well, even if ">>" is ">" 1.0.10-2ubuntu4 is greater then 1.0.10 (I just talked to an debian maintainer, who told me >> means >=, but I was unsure, because I thought as well, ">>" means ">").
In some old debian versions '>' meant 'greater or equal', so they introduced '>>' for 'greater' and discouraged the use of '>'.
but regarding the buildservice:
combots-buildserver:/usr/lib/obs/server/build # rpm -qa|grep obs obs-server-0.1.1-29.1 obs-worker-0.1.1-29.1 obs-api-0.1.1-29.1
That's what came in yesterday ;) But you are right, the /usr/lib/obs/server/build/* is old (strange, because the build.rpm under /usr/lib/build/ is correct...)
Can I just copy the content of /usr/lib/build directory to /usr/lib/obs/server/build/?
Yes, that should work.
Worked :) But now in the logfiles I can see an "apt-ftparchive permission denied" ... and after the build of the debian packages the Packages and Packages.gz are not build (0 bytes). What could be the cause? \ßh -- Stephan Hermann eMail: sh@sourcecode.de Blog: http://linux.blogweb.de/ JID: sh@linux-server.org OSS-Developer and Admin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, Jul 11, 2007 at 05:16:27PM +0200, Stephan Hermann wrote:
But now in the logfiles I can see an "apt-ftparchive permission denied" ... and after the build of the debian packages the Packages and Packages.gz are not build (0 bytes).
What could be the cause?
Dunno, maybe your apt-ftparchive is not executable for user bsrun? M. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (2)
-
Michael Schroeder -
Stephan Hermann