-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 18.10.2010 08:46, Adrian Schröter wrote:

Am Samstag, 16. Oktober 2010, 04:34:32 schrieb Fritz Elfert:

...

Hi,

Just a shot question: Are there any plans to add Ubuntu 10.10 to the list of available repositories?

Download is running now.

(I have not noticed the new release so far).

Great, thanks!

However trying to build a package seems to fail during the basic build setup:

Processing triggers for man-db ... installing procps update-alternatives: using /usr/bin/w.procps to provide /usr/bin/w (w)  in auto mode. start: Unable to connect to Upstart: Failed to connect to socket  /com/ubuntu/upstart: Connection refused dpkg: error processing procps (--install):  subprocess installed post-installation script returned error exit status 1 Processing triggers for man-db ... Errors were encountered while processing:  procps exit ... System halted.

See the full log at:

https://build.opensuse.org/package/live_build_log?arch=i586&package=libj...

Anything I can do about that?

Cheers -Fritz

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 10/19/2010 08:18 PM, Adrian Schröter wrote: [...]

...

However trying to build a package seems to fail during the basic build setup:

Processing triggers for man-db ... installing procps update-alternatives: using /usr/bin/w.procps to provide /usr/bin/w (w)  in auto mode. start: Unable to connect to Upstart: Failed to connect to socket  /com/ubuntu/upstart: Connection refused dpkg: error processing procps (--install):  subprocess installed post-installation script returned error exit status 1 Processing triggers for man-db ... Errors were encountered while processing:  procps exit ... System halted.

See the full log at:

https://build.opensuse.org/package/live_build_log?arch=i586&package=libj...

Anything I can do about that?

Actually yes.

Debug it (via a local build, jumping inside the buildroot and check why the script is failing). I suppose it is a missing package, so you can test by adding this missing one to your prjconf for testing:

osc meta prjconf -e $YOUR_PROJECT

add a line like

Require: missing-package

and tell me which one it was. I simply had no time yet to look inside. By everybody should be able to do the debugging as I would do it ;)

thanks adrian

Well, i'm afraid i'm stuck. (FYI: I'm on FC13, trying a local build for the first time now ...)

What i've done so far:

- - Installed the build rpm (previously, I used osc remotely only)

- - Tried a local build using the default setup (chrooted build) Of course, (FC13 uses upstart itself) this gave me completely different failures, because - even from within the chrooted env - the Ubuntu upstart binaries seem to connect to the *real* init on my Fedora.

- - Then I tried a kvm type build (FC13 supports kvm out of the box), stumbled over missing kernel/initrd and tried my regular FC13 kernel/initrd which - almost expected - failed as well. I suspect missing Fedora specific stuff in the root-FS (got a plymouthd exception).

- - Finally I examined the actual /etc/init/procps.cfg in the buildroot of the chrooted build and found out, that it merely performs the usual processing of /etc/sysctl.d/*. Given the facts, that

a) sysctl processing in a chrooted env is quite useless - if not dangerous for the real system. b) Most other postinstall scripts silently ignore start failures. (the cmd in the postinstall usually reads: "start <service> || :") c) My packages don't need any procps stuff anyway.

I then modified my local _buildinfo-Ubuntu_10.10_standard-i586.xml, removed the procps dependency and tried a chrooted build again using the - -o (offline) flag. This time, it successfully built my package.

So, this leaves a few questions:

1. Is it possible to ignore postinstall exit codes for specific packages in OBS? 2. Is there any chance to get a virtualized build done on any other host distro than OpenSuSE (In this case: FC13)? If so: any hints.

If 1 == yes, this probably would be the easiest workaround - unless some build actually requires upstart/sysctl functionality. If 2 == yes, this would enable me to actually do proper debugging ;)

Cheers -Fritz

Is xUbuntu 10.10 publicly available on build.opensuse.org? I can't see it in my project home:pstavirs

Srivats

On Wed, Oct 20, 2010 at 8:12 PM, Ludwig Nussel ludwig.nussel@suse.de wrote:

Fritz Elfert wrote:

...

a) sysctl processing in a chrooted env is quite useless - if not     dangerous for the real system.  b) Most other postinstall scripts silently ignore start failures.     (the cmd in the postinstall usually reads: "start <service> || :")

So bad behavior of the Ubuntu package.

...

So, this leaves a few questions:

1. Is it possible to ignore postinstall exit codes for specific     packages in OBS?

Not in general. SUSE packages simply avoid certain actions that are dangerous or will fail in a chroot if YAST_IS_RUNNING is set to 'instsys', which is what the build script uses. On other distros you can only BuildIgnore or Substitute problematic packages atm. It wouldn't be hard to introduce extra prjconf options to make the build script pass e.g. --noscripts to rpm (and whatever else is needed for dpkg) though.

...

2. Is there any chance to get a virtualized build done on any other     host distro than OpenSuSE (In this case: FC13)? If so: any hints.

Sure, why not? I don't know how to help though. UTSL :-) Maybe you just need to prepare your initrd in a special way, like e.g. including the correct storage drivers (virtio!?).

cu Ludwig

--  (o_   Ludwig Nussel  //\  V_/_  http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Any news on Ubuntu 10.10?

Is any one working on it or are their plans to do soß

Ralf

Am 25.10.10 11:34, schrieb Adrian Schröter:

Am Sonntag, 24. Oktober 2010, 14:22:19 schrieb Srivats P:

...

Is xUbuntu 10.10 publicly available on build.opensuse.org? I can't see it in my project home:pstavirs

it is not yet working