[opensuse-buildservice] build 2009.07.27 doesn't detect pre-existing Ubuntu installs
When building against xUbuntu_9.10 using build-2009.07.27, it keeps reinstall all the .debs. Do .deb based workareas not have detection that packages are already installed in the chroot like .rpm based chroots do? Or do I need to upgrade to a newer build? We're still using OBS 1.5 for the server, so I didn't want to upgrade build if it might break compatibility. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Montag, 9. November 2009 17:47:11 schrieb Luke Imhoff:
When building against xUbuntu_9.10 using build-2009.07.27, it keeps reinstall all the .debs. Do .deb based workareas not have detection that packages are already installed in the chroot like .rpm based chroots do? Or do I need to upgrade to a newer build? We're still using OBS 1.5 for the server, so I didn't want to upgrade build if it might break compatibility.
It worked latetly for me. You may try to upgrade osc and esp. the build script first on your workstation to test again. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Montag, 9. November 2009 18:52:11 schrieb Adrian Schröter:
Am Montag, 9. November 2009 17:47:11 schrieb Luke Imhoff:
When building against xUbuntu_9.10 using build-2009.07.27, it keeps reinstall all the .debs. Do .deb based workareas not have detection that packages are already installed in the chroot like .rpm based chroots do? Or do I need to upgrade to a newer build? We're still using OBS 1.5 for the server, so I didn't want to upgrade build if it might break compatibility.
It worked latetly for me. You may try to upgrade osc and esp. the build script first on your workstation to test again.
okay, I was wrong here. This is currently not supported by the build script. A partial fix is in svn now, but it is not complete. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Is there a fix for this: user abuild has an entry in /etc/shadow, but its password field in /etc/passwd is not set to 'x' pwck: no changes Please correct the error and rerun `/sbin/shadowconfig on' dpkg: error processing passwd (--install): subprocess installed post-installation script returned error exit status 1 Processing triggers for man-db ... Errors were encountered while processing: passwd ? It means I have to run with --clean every time. On Mon, 2009-11-09 at 12:16 -0600, Adrian Schröter wrote:
Am Montag, 9. November 2009 18:52:11 schrieb Adrian Schröter:
Am Montag, 9. November 2009 17:47:11 schrieb Luke Imhoff:
When building against xUbuntu_9.10 using build-2009.07.27, it keeps reinstall all the .debs. Do .deb based workareas not have detection that packages are already installed in the chroot like .rpm based chroots do? Or do I need to upgrade to a newer build? We're still using OBS 1.5 for the server, so I didn't want to upgrade build if it might break compatibility.
It worked latetly for me. You may try to upgrade osc and esp. the build script first on your workstation to test again.
okay, I was wrong here. This is currently not supported by the build script. A partial fix is in svn now, but it is not complete.
bye adrian
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
I've got a patch so that a Ubuntu chroot can be reused without a clean being needed: Index: build =================================================================== --- build (revision 2041) +++ build (working copy) @@ -1176,10 +1176,10 @@ if test $BUILD_USER = abuild ; then # add abuild user if it doesn't exist if ! egrep '^abuild:' >/dev/null <$BUILD_ROOT/etc/passwd ; then - echo "abuild::${ABUILD_UID}: ${ABUILD_GID}:Autobuild:/home/abuild:/bin/bash" >>$BUILD_ROOT/etc/passwd + echo "abuild:x:${ABUILD_UID}: ${ABUILD_GID}:Autobuild:/home/abuild:/bin/bash" >>$BUILD_ROOT/etc/passwd echo 'abuild:*:::::::' >>$BUILD_ROOT/etc/shadow # This is needed on Mandriva 2009 - echo 'abuild:*:::::::' >>$BUILD_ROOT/etc/gshadow # This is needed on Ubuntu 8.10 - echo "abuild::${ABUILD_GID}:" >>$BUILD_ROOT/etc/group + echo 'abuild:*::' >>$BUILD_ROOT/etc/gshadow # This is needed on Ubuntu 8.10 + echo "abuild:x:${ABUILD_GID}:" >>$BUILD_ROOT/etc/group mkdir -p $BUILD_ROOT/home/abuild chown ${ABUILD_UID}:${ABUILD_GID} $BUILD_ROOT/home/abuild # grab previous abuild UID and GID to maintain compatibility On Mon, 2009-11-09 at 12:19 -0600, Luke Imhoff wrote:
Is there a fix for this:
user abuild has an entry in /etc/shadow, but its password field in /etc/passwd is not set to 'x' pwck: no changes Please correct the error and rerun `/sbin/shadowconfig on' dpkg: error processing passwd (--install): subprocess installed post-installation script returned error exit status 1 Processing triggers for man-db ... Errors were encountered while processing: passwd
? It means I have to run with --clean every time.
On Mon, 2009-11-09 at 12:16 -0600, Adrian Schröter wrote:
Am Montag, 9. November 2009 18:52:11 schrieb Adrian Schröter:
Am Montag, 9. November 2009 17:47:11 schrieb Luke Imhoff:
When building against xUbuntu_9.10 using build-2009.07.27, it keeps reinstall all the .debs. Do .deb based workareas not have detection that packages are already installed in the chroot like .rpm based chroots do? Or do I need to upgrade to a newer build? We're still using OBS 1.5 for the server, so I didn't want to upgrade build if it might break compatibility.
It worked latetly for me. You may try to upgrade osc and esp. the build script first on your workstation to test again.
okay, I was wrong here. This is currently not supported by the build script. A partial fix is in svn now, but it is not complete.
bye adrian
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Montag, 9. November 2009 20:59:39 schrieb Luke Imhoff:
I've got a patch so that a Ubuntu chroot can be reused without a clean being needed:
hm, something similar, but not identical is in our svn trunk. Can you try if that works for you ? bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
https://forgesvn1.novell.com/svn/opensuse/trunk/buildservice/src/build/build has echo 'abuild:*:::::::' >>$BUILD_ROOT/etc/gshadow # This is needed on Ubuntu 8.10 That's too many :'s in there. group and gshadow can only have 3 :'s for Ubuntu 9.10 to be happy. On Mon, 2009-11-09 at 14:11 -0600, Adrian Schröter wrote:
Am Montag, 9. November 2009 20:59:39 schrieb Luke Imhoff:
I've got a patch so that a Ubuntu chroot can be reused without a clean being needed:
hm, something similar, but not identical is in our svn trunk. Can you try if that works for you ?
bye adrian
--
Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Montag, 9. November 2009 21:20:20 schrieb Luke Imhoff:
https://forgesvn1.novell.com/svn/opensuse/trunk/buildservice/src/build/buil d
has
echo 'abuild:*:::::::' >>$BUILD_ROOT/etc/gshadow # This is needed on Ubuntu 8.10
That's too many :'s in there. group and gshadow can only have 3 :'s for Ubuntu 9.10 to be happy.
okay, removed the other ones on svn. thanks a lot adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Montag, 9. November 2009 19:16:32 schrieb Adrian Schröter:
Am Montag, 9. November 2009 18:52:11 schrieb Adrian Schröter:
Am Montag, 9. November 2009 17:47:11 schrieb Luke Imhoff:
When building against xUbuntu_9.10 using build-2009.07.27, it keeps reinstall all the .debs. Do .deb based workareas not have detection that packages are already installed in the chroot like .rpm based chroots do? Or do I need to upgrade to a newer build? We're still using OBS 1.5 for the server, so I didn't want to upgrade build if it might break compatibility.
It worked latetly for me. You may try to upgrade osc and esp. the build script first on your workstation to test again.
okay, I was wrong here. This is currently not supported by the build script. A partial fix is in svn now, but it is not complete.
And another sorry, there is currently to much missing to make this cleanly working. This is not that easy to fix for me, because I have not enough clue about debs. If you like to implement support for this, have a look into the init_buildsystem script of build package. You need to extend the validate_cache_file funcaiton in first place, to generate also .id files from the deb meta data. I dunno what makes sense as unique identifier for debs repositories. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, Nov 09, 2009 at 07:47:38PM +0100, Adrian Schröter wrote:
If you like to implement support for this, have a look into the init_buildsystem script of build package.
You need to extend the validate_cache_file funcaiton in first place, to generate also .id files from the deb meta data. I dunno what makes sense as unique identifier for debs repositories.
validate_cache_file isn't called in the build service case as $RPMLIST is set. 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
On Mon, 2009-11-09 at 12:47 -0600, Adrian Schröter wrote:
Am Montag, 9. November 2009 19:16:32 schrieb Adrian Schröter:
Am Montag, 9. November 2009 18:52:11 schrieb Adrian Schröter:
Am Montag, 9. November 2009 17:47:11 schrieb Luke Imhoff:
When building against xUbuntu_9.10 using build-2009.07.27, it keeps reinstall all the .debs. Do .deb based workareas not have detection that packages are already installed in the chroot like .rpm based chroots do? Or do I need to upgrade to a newer build? We're still using OBS 1.5 for the server, so I didn't want to upgrade build if it might break compatibility.
It worked latetly for me. You may try to upgrade osc and esp. the build script first on your workstation to test again.
okay, I was wrong here. This is currently not supported by the build script. A partial fix is in svn now, but it is not complete.
And another sorry, there is currently to much missing to make this cleanly working. This is not that easy to fix for me, because I have not enough clue about debs.
If you like to implement support for this, have a look into the init_buildsystem script of build package.
You need to extend the validate_cache_file funcaiton in first place, to generate also .id files from the deb meta data. I dunno what makes sense as unique identifier for debs repositories.
As far as I can tell, there is no way to query the build time or some other information that is guaranteed to change with a new build of a deb. I can replicate the %{NAME} key with ${Package} and %{VERSION}-%{RELEASE} with ${Version}, but I'm at a lost for an identifier that will distinguish debs that have had changes that result in the same version and size, but are actually distinct. (I can see this happening if a transposition error is corrected in some file, in which case the size would remain constant.)
bye adrian
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, 2009-11-09 at 12:47 -0600, Adrian Schröter wrote:
Am Montag, 9. November 2009 19:16:32 schrieb Adrian Schröter:
Am Montag, 9. November 2009 18:52:11 schrieb Adrian Schröter:
Am Montag, 9. November 2009 17:47:11 schrieb Luke Imhoff:
When building against xUbuntu_9.10 using build-2009.07.27, it keeps reinstall all the .debs. Do .deb based workareas not have detection that packages are already installed in the chroot like .rpm based chroots do? Or do I need to upgrade to a newer build? We're still using OBS 1.5 for the server, so I didn't want to upgrade build if it might break compatibility.
It worked latetly for me. You may try to upgrade osc and esp. the build script first on your workstation to test again.
okay, I was wrong here. This is currently not supported by the build script. A partial fix is in svn now, but it is not complete.
And another sorry, there is currently to much missing to make this cleanly working. This is not that easy to fix for me, because I have not enough clue about debs.
If you like to implement support for this, have a look into the init_buildsystem script of build package.
You need to extend the validate_cache_file funcaiton in first place, to generate also .id files from the deb meta data. I dunno what makes sense as unique identifier for debs repositories.
As far as I can tell, there is no way to query the build time or some other information that is guaranteed to change with a new build of a deb. I can replicate the %{NAME} key with ${Package} and %{VERSION}-%{RELEASE} with ${Version}, but I'm at a lost for an identifier that will distinguish debs that have had changes that result in the same version and size, but are actually distinct. (I can see this happening if a transposition error is corrected in some file, in which case the size would remain constant.) The package verification in osc.fetch.verify_pacs only verifies based on
On Thu, 2009-11-12 at 14:27 -0600, Luke Imhoff wrote: the package name, so since the package cacher doesn't care about the build time, I see no reason to distinguish based on it for installing debs in the chroot. I'm actually curious how build time matters for rpms, for the same reason.
bye adrian
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
I've modified our local copy of init_buildsystem to detect debs that are already installed. It is based on the 2009.07.27 version of the build rpm. The patch is attached. I've tried to match up the dpkg/dpkg-query/debsums commands as closely to the equivalent rpm commands as I could, but I'm not that familiar with using any of them since I use Synaptic and apt-get to handle package management on Ubuntu. debsums is not part of the preinstalls in the Ubuntu:9.10 prjconf, so you'll need to add that for the rpm --verify equivalent (debsums) to work. On Mon, 2009-11-09 at 12:47 -0600, Adrian Schröter wrote:
Am Montag, 9. November 2009 19:16:32 schrieb Adrian Schröter:
Am Montag, 9. November 2009 18:52:11 schrieb Adrian Schröter:
Am Montag, 9. November 2009 17:47:11 schrieb Luke Imhoff:
When building against xUbuntu_9.10 using build-2009.07.27, it keeps reinstall all the .debs. Do .deb based workareas not have detection that packages are already installed in the chroot like .rpm based chroots do? Or do I need to upgrade to a newer build? We're still using OBS 1.5 for the server, so I didn't want to upgrade build if it might break compatibility.
It worked latetly for me. You may try to upgrade osc and esp. the build script first on your workstation to test again.
okay, I was wrong here. This is currently not supported by the build script. A partial fix is in svn now, but it is not complete.
And another sorry, there is currently to much missing to make this cleanly working. This is not that easy to fix for me, because I have not enough clue about debs.
If you like to implement support for this, have a look into the init_buildsystem script of build package.
You need to extend the validate_cache_file funcaiton in first place, to generate also .id files from the deb meta data. I dunno what makes sense as unique identifier for debs repositories.
bye adrian
participants (3)
-
Adrian Schröter -
Luke Imhoff -
Michael Schroeder