[opensuse-buildservice] How to build deb packages
Hi, I have successfully build packages for my project "inkomstenbelasting" for openSUSE, fedora, mandrake and centos. I now would like to extent this to the debian based distributions. I would like to know how this should be done. I have read the wiki page http://en.opensuse.org/Build_Service/Deb_builds, but after reading it, it was still not clear :( Neither does the email that the wiki page refers to (http://lists.opensuse.org/opensuse- buildservice/2007-03/msg00067.html) make things clearer, perhaps the contrary :( The rpm that I would like to debianize is this one: http://download.opensuse.org/repositories/home:/rbos:/ib/openSUSE_11.1/repod... It seems like a simply package and it consist of only a few files: # rpm -ql inkomstenbelasting /usr/share/belastingdienst.nl /usr/share/doc/packages/inkomstenbelasting /usr/share/doc/packages/inkomstenbelasting/Aandachtspunten /usr/share/doc/packages/inkomstenbelasting/README /usr/share/doc/packages/inkomstenbelasting/TODO /usr/share/icons/hicolor/16x16/apps/inkomstenbelasting.png .... /usr/share/icons/hicolor/128x128/apps/inkomstenbelasting.png There is no debian package for it. The build server work directory holds the following files: inkomstenbelasting-2008.tar.bz2 inkomstenbelasting.changes inkomstenbelasting.spec The changes file is in the spec file format. What do I need to add to the spec file? Should I use the DebTransformTar tag to refer to inkomstenbelasting-2008.tar.bz2 file? Is there a .dsc file required or is this created from the spec file by the build service? What to do with the changes files, must it be renamed to e.g debian.changes, must the format be adjusted or will this be taken care of by the build service? Looking forward to your advice. -- Richard -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
The peless package is a package that builds debian and ubuntu versions. I did not follow the method described in: http://en.opensuse.org/Build_Service/Deb_builds according to that document I needed to create: Minimum set of files required to create .deb In order to create a .deb package successfully, you have to create at least these files: packageName.dsc debian.changelog debian.control debian.rules Instead I used the debian method of creating a debian source package. I uploaded the 3 debian files X.dsc, X.diff.gx, and X.orig.tar.gz and build. To make it work I had to add build-essential to the Build-Depends: line. According to the debian policy manual I should not have to do this, but I had to to make it build under the build-service. I created a bug in bugzilla because of this. -- Paul Elliott 1(512)837-1096 pelliott@BlackPatchPanel.com PMB 181, 11900 Metric Blvd Suite J http://www.io.com/~pelliott/pme/ Austin TX 78758-3117
Op zondag 29 maart 2009 23:54:44 schreef Paul Elliott:
I uploaded the 3 debian files X.dsc, X.diff.gx, and X.orig.tar.gz and build.
According to this email: http://lists.opensuse.org/opensuse-buildservice/2007-03/msg00067.html only one source file is needed "the pristine tarball (no need to put .orig in the name, it'll get renamed to the "canonical" debian tar name automatically)" /me still wondering how to build .deb pkgs with the build service. -- Richard -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, Mar 30, Richard Bos wrote:
I uploaded the 3 debian files X.dsc, X.diff.gx, and X.orig.tar.gz and build.
According to this email: http://lists.opensuse.org/opensuse-buildservice/2007-03/msg00067.html only one source file is needed "the pristine tarball (no need to put .orig in the name, it'll get renamed to the "canonical" debian tar name automatically)"
/me still wondering how to build .deb pkgs with the build service.
You still need Debian package meta information. http://en.opensuse.org/Build_Service/Deb_builds [...] The build service also uses some magic, some extra information can be given in the .dsc file in the form of 'debtransform' tags. Those are documented in this mail: http://lists.opensuse.org/opensuse-buildservice/2007-03/msg00067.html and the source code can be found here: https://forgesvn1.novell.com/svn/opensuse/trunk/buildservice/src/build/debtr... By looking at it you can see that it accepts three tags: [...] -- With best regards, Carsten Hoeger
Op maandag 30 maart 2009 09:38:09 schreef Carsten Hoeger:
On Mon, Mar 30, Richard Bos wrote:
I uploaded the 3 debian files X.dsc, X.diff.gx, and X.orig.tar.gz and build.
According to this email: http://lists.opensuse.org/opensuse-buildservice/2007-03/msg00067.html only one source file is needed "the pristine tarball (no need to put .orig in the name, it'll get renamed to the "canonical" debian tar name automatically)"
/me still wondering how to build .deb pkgs with the build service.
You still need Debian package meta information.
http://en.opensuse.org/Build_Service/Deb_builds
[...]
The build service also uses some magic, some extra information can be given in the .dsc file in the form of 'debtransform' tags. Those are documented in this mail: http://lists.opensuse.org/opensuse-buildservice/2007-03/msg00067.html and the source code can be found here: https://forgesvn1.novell.com/svn/opensuse/trunk/buildservice/src/build/debt ransform By looking at it you can see that it accepts three tags:
[...]
I read that page (see my initial post), but it did not make it clear to me what is needed. :( What Deb* tags are to be used in the spec file? Are there tools around to convert a osc work directory to a .dsc file? The .dsc file contains a Files section, should that be included? As the packageName_5.6.orig.tar.gz and packageName_5.6-1.diff.tar.gz can be created by the build service, it does not seem to be necessary to include those in the .dsc file. -- Richard -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, Mar 30, Richard Bos wrote:
I uploaded the 3 debian files X.dsc, X.diff.gx, and X.orig.tar.gz and build.
According to this email: http://lists.opensuse.org/opensuse-buildservice/2007-03/msg00067.html only one source file is needed "the pristine tarball (no need to put .orig in the name, it'll get renamed to the "canonical" debian tar name automatically)"
/me still wondering how to build .deb pkgs with the build service.
You still need Debian package meta information.
http://en.opensuse.org/Build_Service/Deb_builds
[...]
The build service also uses some magic, some extra information can be given in the .dsc file in the form of 'debtransform' tags. Those are documented in this mail: http://lists.opensuse.org/opensuse-buildservice/2007-03/msg00067.html and the source code can be found here: https://forgesvn1.novell.com/svn/opensuse/trunk/buildservice/src/build/debt ransform By looking at it you can see that it accepts three tags:
[...]
I read that page (see my initial post), but it did not make it clear to me what is needed. :( What Deb* tags are to be used in the spec file? Are there tools around to convert a osc work directory to a .dsc file?
There are no Deb tags to be used in spec files. At least not that I know.
The .dsc file contains a Files section, should that be included? As the packageName_5.6.orig.tar.gz and packageName_5.6-1.diff.tar.gz can be created by the build service, it does not seem to be necessary to include those in the .dsc file.
I'm quite sure, that you still have to submit Debian Package information (debian/control, debian/rules, debian/changelog, ...) separately. I'd use the common Debian tools to generated them (dpkg-source). There's a deb rpm package available on openSUSE, SLE, ..., which can be used to do that. -- With best regards, Carsten Hoeger
On Mon, Mar 30, 2009 at 01:20:19PM +0200, Carsten Hoeger wrote:
I'm quite sure, that you still have to submit Debian Package information (debian/control, debian/rules, debian/changelog, ...) separately.
That is indeed what the "Build Service/Deb builds" http://en.opensuse.org/Build_Service/Deb_builds documentation seems to say. deb> Minimum set of files required to create .deb In order to create a deb> .deb package successfully, you have to create at least these files: deb> packageName.dsc deb> debian.changelog deb> debian.control deb> debian.rules deb> And of course a tarball (tar.bz2) that contains the package source deb> code to compile. But it is not true. To see this look at the peless project: https://build.opensuse.org/package/show?package=peless&project=home%3Apelliott11 In the files section, no debian.changelog, debian.control, debian.rules. But of course, equivlents of these files are hiding in "peless_1.193-1.diff.gz". But the peless project builds Debian_5.0, Debian_Etch, and xUbuntu_8.10 successfully. The peless.dsc, peless_1.193-1.diff.gz, and peless_1.193.orig.tar.gz were created with uupdate as described in the Debian New Maintainers' Guide. http://www.debian.org/doc/maint-guide/ch-update.en.html These 3 files are a "debian source package" as defined by the debian people. By the way, it would be nice if someone could create a version of uupdate that runs on opensuse, that way people would not have to go to a debian system for this step. When you create your .debs this way, and they build on the build service, you know you can take your source package to a native debian build system, and it will build there.
I'd use the common Debian tools to generated them (dpkg-source). There's a deb rpm package available on openSUSE, SLE, ..., which can be used to do that.
-- With best regards,
Carsten Hoeger
-- Paul Elliott 1(512)837-1096 pelliott@BlackPatchPanel.com PMB 181, 11900 Metric Blvd Suite J http://www.io.com/~pelliott/pme/ Austin TX 78758-3117
On Mon, Mar 30, Paul Elliott wrote:
I'm quite sure, that you still have to submit Debian Package information (debian/control, debian/rules, debian/changelog, ...) separately.
That is indeed what the "Build Service/Deb builds" http://en.opensuse.org/Build_Service/Deb_builds documentation seems to say.
deb> Minimum set of files required to create .deb In order to create a deb> .deb package successfully, you have to create at least these files: deb> packageName.dsc deb> debian.changelog deb> debian.control deb> debian.rules
deb> And of course a tarball (tar.bz2) that contains the package source deb> code to compile.
But it is not true. To see this look at the peless project: https://build.opensuse.org/package/show?package=peless&project=home%3Apelliott11
It IS true. It's just that the debian package metadata is contained in the *.diff and *.dsc file(s). It's NOT contained in the *.spec file(s). That's what I wanted to make clear. -- With best regards, Carsten Hoeger
Carsten and Paul, Op dinsdag 31 maart 2009 11:13:11 schreef Carsten Hoeger:
On Mon, Mar 30, Paul Elliott wrote:
I'm quite sure, that you still have to submit Debian Package information (debian/control, debian/rules, debian/changelog, ...) separately.
That is indeed what the "Build Service/Deb builds" http://en.opensuse.org/Build_Service/Deb_builds documentation seems to say.
deb> Minimum set of files required to create .deb In order to create a deb> .deb package successfully, you have to create at least these files: deb> packageName.dsc deb> debian.changelog deb> debian.control deb> debian.rules
deb> And of course a tarball (tar.bz2) that contains the package source deb> code to compile.
But it is not true. To see this look at the peless project: https://build.opensuse.org/package/show?package=peless&project=home%3Apel liott11
It IS true. It's just that the debian package metadata is contained in the *.diff and *.dsc file(s). It's NOT contained in the *.spec file(s). That's what I wanted to make clear.
You got me going :) I can now run 'osc build xUbuntu_8.04 i586 <pkg>' :) To accomplish this, I needed the following files: debian.control debian.rules inkomstenbelasting-2008.tar.bz2 inkomstenbelasting.changes inkomstenbelasting.dsc The files are almost the same as Paul stated, but it is not debian.changelog, but packageName.changes in debian format. The build service will than take care that the changelog is included in as well the debian packages as well as the rpms. The files sectio in dsc file may remain empty as it is populated by the debtransformer, like: Format: 1.0 ....... Files: It is not needed to specify the Debtransform-Tar as the pristine source tarbal is figured out by the tools :) A debian.control file is required otherwise the following and confusing error is reported: dpkg-source: warning: extracting unsigned source package (/usr/src/packages/SOURCES/inkomstenbelasting.dsc) dpkg-source: error: Files field contains invalid filename `inkomstenbelasting-2008.tar.gz' The next step is now to include the commands that I have in the rpm spec file into the debian pkg build. The commands are the following ones: %prep %setup -q %build %install %__install -d -m 755 %{buildroot}%{_bindir} %__install -d -m 755 %{buildroot}%{_datadir}/belastingdienst.nl # %__install -d -m 755 %{buildroot}%{_datadir}/applications # sed s/@JAAR@/%{year}/ ib.desktop > %{buildroot}%{_datadir}/applications/inkomstenbelasting.desktop %__install -d -m 755 %{buildroot}%{_datadir}/icons/hicolor for D in 16x16 22x22 32x32 48x48 64x64 128x128; do %__install -d -m 755 %{buildroot}%{_datadir}/icons/hicolor/$D/apps %__install -m 644 icons/$D/inkomstenbelasting.png %{buildroot}%{_datadir}/icons/hicolor/$D/apps done Is there any debian pkg guru out there, who can tell how the above command sequence should look like in a debian.rules file? TIA! -- Regards, Richard -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Richard Bos writes: Hi!
You got me going :) I can now run 'osc build xUbuntu_8.04 i586 <pkg>' :) To accomplish this, I needed the following files: debian.control debian.rules inkomstenbelasting-2008.tar.bz2
Use tar.gz upstream tarballs. You shouldn't have problems with Debian Lenny and Ubuntu 8.10.
%install %__install -d -m 755 %{buildroot}%{_bindir} %__install -d -m 755 %{buildroot}%{_datadir}/belastingdienst.nl # %__install -d -m 755 %{buildroot}%{_datadir}/applications # sed s/@JAAR@/%{year}/ ib.desktop > %{buildroot}%{_datadir}/applications/inkomstenbelasting.desktop %__install -d -m 755 %{buildroot}%{_datadir}/icons/hicolor for D in 16x16 22x22 32x32 48x48 64x64 128x128; do %__install -d -m 755 %{buildroot}%{_datadir}/icons/hicolor/$D/apps %__install -m 644 icons/$D/inkomstenbelasting.png %{buildroot}%{_datadir}/icons/hicolor/$D/apps
Create debian.PACKAGENAME.install file if those are provided by upstream. Piotras -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Op dinsdag 31 maart 2009 22:54:26 schreef Piotr Pokora:
Hi!
same to you :)
You got me going :) I can now run 'osc build xUbuntu_8.04 i586 <pkg>' :) To accomplish this, I needed the following files: debian.control debian.rules inkomstenbelasting-2008.tar.bz2
Use tar.gz upstream tarballs. You shouldn't have problems with Debian Lenny and Ubuntu 8.10.
That's the problem, there are no upstream tarballs hence I need to come with the code.
%install %__install -d -m 755 %{buildroot}%{_bindir} %__install -d -m 755 %{buildroot}%{_datadir}/belastingdienst.nl # %__install -d -m 755 %{buildroot}%{_datadir}/applications # sed s/@JAAR@/%{year}/ ib.desktop > %{buildroot}%{_datadir}/applications/inkomstenbelasting.desktop %__install -d -m 755 %{buildroot}%{_datadir}/icons/hicolor for D in 16x16 22x22 32x32 48x48 64x64 128x128; do %__install -d -m 755 %{buildroot}%{_datadir}/icons/hicolor/$D/apps %__install -m 644 icons/$D/inkomstenbelasting.png %{buildroot}%{_datadir}/icons/hicolor/$D/apps
Create debian.PACKAGENAME.install file if those are provided by upstream.
What will this do? -- TIA, Richard -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Richard Bos writes: Hi!
inkomstenbelasting-2008.tar.bz2 Use tar.gz upstream tarballs. You shouldn't have problems with Debian Lenny and Ubuntu 8.10.
That's the problem, there are no upstream tarballs hence I need to come with the code.
I wonder, maybe this is even better? You can create directories and subdirectories and tar.gz'em all.
%__install -m 644 icons/$D/inkomstenbelasting.png %{buildroot}%{_datadir}/icons/hicolor/$D/apps Create debian.PACKAGENAME.install file if those are provided by upstream.
What will this do?
dh_install command installs all files which are listed in PACKAGENAME.install file. So, all you have to do, is to add dh_install to rules file. *If* you want to use .install routines. In rules file (it's only Makefile anyway): install: belastingdienst.nl debian/PACKAGENAME/usr/share/PACKAGENAME/belastingdienst.nl in debian.PACKAGENAME.install: usr/share/PACKAGENAME/belastingdienst.nl Or you can just copy all files in `debian/rules install`. Take a look how PHP (and extensions) packages are built for example. Piotras -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hello Piotr, thanks a lot for your advice, it helped me a lot. Op woensdag 01 april 2009 00:12:42 schreef Piotr Pokora:
Richard Bos writes:
Hi!
inkomstenbelasting-2008.tar.bz2
Use tar.gz upstream tarballs. You shouldn't have problems with Debian Lenny and Ubuntu 8.10.
That's the problem, there are no upstream tarballs hence I need to come with the code.
I wonder, maybe this is even better? You can create directories and subdirectories and tar.gz'em all.
That's not the way to go I think; the package build process should be used to create the directory structure.
%__install -m 644 icons/$D/inkomstenbelasting.png %{buildroot}%{_datadir}/icons/hicolor/$D/apps
Create debian.PACKAGENAME.install file if those are provided by upstream.
What will this do?
dh_install command installs all files which are listed in PACKAGENAME.install file. So, all you have to do, is to add dh_install to rules file. *If* you want to use .install routines.
In rules file (it's only Makefile anyway):
install: belastingdienst.nl debian/PACKAGENAME/usr/share/PACKAGENAME/belastingdienst.nl
in debian.PACKAGENAME.install:
usr/share/PACKAGENAME/belastingdienst.nl
Or you can just copy all files in `debian/rules install`.
That's what I did.
Take a look how PHP (and extensions) packages are built for example.
I had a look at a php package that copied the files in the debian/rules files and that helped a lot. In the meantime I have successfully build a deb package :) Thank you Piotr, Carsten and Paul! -- Richard -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Op woensdag 01 april 2009 23:27:29 schreef Richard Bos:
In the meantime I have successfully build a deb package
But only for older Deb based releases. For the newer ones I get the following error: "unrecognized file for a v1.0 source package" Which seems to be known one, it was reported 2 months ago: http://lists.opensuse.org/opensuse-buildservice/2009-01/msg00067.html http://lists.opensuse.org/opensuse-buildservice/2009-01/msg00070.html Would it be possible to adapt the Debtransformer and have tar.bz2 files be repackaged into tar.gz files? For rpms bz2 is required, and to have multiple tar files of the same version for 1 project seems to be against the philosophy of the build service... Has this bug already been reported in bugzilla?? -- Richard -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Richard Bos writes: Hi!
Op woensdag 01 april 2009 23:27:29 schreef Richard Bos:
In the meantime I have successfully build a deb package
But only for older Deb based releases. For the newer ones I get the following error: "unrecognized file for a v1.0 source package"
That's why I mentioned tar.gz file few days ago :)
Which seems to be known one, it was reported 2 months ago: http://lists.opensuse.org/opensuse-buildservice/2009-01/msg00067.html http://lists.opensuse.org/opensuse-buildservice/2009-01/msg00070.html
Would it be possible to adapt the Debtransformer and have tar.bz2 files be repackaged into tar.gz files? For rpms bz2 is required,
tar.gz also works fine for rpms. At least, we have such in spec file: Source: PKGNAME-%{version}.tar.gz Piotras -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Piotr and Michael, Op donderdag 02 april 2009 08:15:08 schreef Piotr Pokora:
But only for older Deb based releases. For the newer ones I get the following error: "unrecognized file for a v1.0 source package"
That's why I mentioned tar.gz file few days ago :)
Which seems to be known one, it was reported 2 months ago: http://lists.opensuse.org/opensuse-buildservice/2009-01/msg00067.html http://lists.opensuse.org/opensuse-buildservice/2009-01/msg00070.html
Would it be possible to adapt the Debtransformer and have tar.bz2 files be repackaged into tar.gz files? For rpms bz2 is required,
tar.gz also works fine for rpms. At least, we have such in spec file:
Source: PKGNAME-%{version}.tar.gz
I know, see below: Op donderdag 02 april 2009 09:56:11 schreef Michael Schroeder:
No, rpm doesn't require bz2 (why should it). Just use a gzipped tarball if you also want to build debs.
Because of this warning: ib2008.src: W: source-or-patch-not-bzipped ib2008_linux.tar.gz A source archive or patch in your package is not bzipped (doesn't have the .bz2 extension). Files bigger than 100k should be bzip2'ed in order to save space. To bzip2 a patch, use bzip2. To bzip2 a source tarball, use bznew -- Richard -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Thu, Apr 02, 2009 at 12:45:29PM +0200, Richard Bos wrote:
Because of this warning: ib2008.src: W: source-or-patch-not-bzipped ib2008_linux.tar.gz A source archive or patch in your package is not bzipped (doesn't have the .bz2 extension). Files bigger than 100k should be bzip2'ed in order to save space. To bzip2 a patch, use bzip2. To bzip2 a source tarball, use bznew
That's a warning. Just ignore it... 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 Wed, Apr 01, 2009 at 11:52:10PM +0200, Richard Bos wrote:
Which seems to be known one, it was reported 2 months ago: http://lists.opensuse.org/opensuse-buildservice/2009-01/msg00067.html http://lists.opensuse.org/opensuse-buildservice/2009-01/msg00070.html
Would it be possible to adapt the Debtransformer and have tar.bz2 files be repackaged into tar.gz files? For rpms bz2 is required, and to have multiple tar files of the same version for 1 project seems to be against the philosophy of the build service...
No, rpm doesn't require bz2 (why should it). Just use a gzipped tarball if you also want to build debs. 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
Op donderdag 02 april 2009 09:56:11 schreef Michael Schroeder:
On Wed, Apr 01, 2009 at 11:52:10PM +0200, Richard Bos wrote:
Which seems to be known one, it was reported 2 months ago: http://lists.opensuse.org/opensuse-buildservice/2009-01/msg00067.html http://lists.opensuse.org/opensuse-buildservice/2009-01/msg00070.html
Would it be possible to adapt the Debtransformer and have tar.bz2 files be repackaged into tar.gz files? For rpms bz2 is required, and to have multiple tar files of the same version for 1 project seems to be against the philosophy of the build service...
No, rpm doesn't require bz2 (why should it). Just use a gzipped tarball if you also want to build debs.
I changed to gz and tried to build for Ubuntu-8.10. I now get: ib2008> osc build xUbuntu_8.10 i586 *dsc /usr/lib/python2.6/site-packages/osc/conf.py:324: DeprecationWarning: Use of the 'scheme' or 'apisrv' config option is deprecated! DeprecationWarning) Building ib2008.dsc for xUbuntu_8.10/i586 Getting buildinfo from server Updating cache of required packages Writing build configuration Getting buildconfig from server Running build sudo /usr/bin/build --root=/var/tmp/build-root-xUbuntu_8.10-i586 --rpmlist=/tmp/rpmlist.D7paBa --dist=/tmp/buildconfig.b3fDuP --arch=i586 ib2008.dsc --norootforbuild --changelog --debug logging output to /var/tmp/build-root-xUbuntu_8.10-i586/.build.log... Memory limit set to 2049976KB Using BUILD_ROOT=/var/tmp/build-root-xUbuntu_8.10-i586 Using BUILD_ARCH=i586:i486:i386 med111 started "build ib2008.dsc" at Thu Apr 2 12:58:53 CEST 2009. processing specfile /home...../ib2008/ib2008.dsc... running changelog2spec --target debian --file /home......./ib2008/ib2008.dsc init_buildsystem --rpmlist /tmp/rpmlist.D7paBa /home/...../ib2008/ib2008.dsc ... preinstalling bash... preinstalling perl-base... preinstalling sed... preinstalling grep... preinstalling coreutils... preinstalling debianutils... preinstalling libc6... preinstalling libncurses5... preinstalling libacl1... preinstalling libattr1... preinstalling libreadline5... preinstalling tar... preinstalling gawk... preinstalling dpkg... preinstalling sysv-rc... preinstalling gzip... preinstalling base-files... preinstalling readline-common... ar: /var/tmp/build-root-xUbuntu_8.10-i586/.init_b_cache/rpms/readline-common.deb: File format not recognized tar: control.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now tar: Child returned status 2 tar: Error exit delayed from previous errors tar: data.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now tar: Child returned status 2 tar: Error exit delayed from previous errors preinstalling libselinux1... preinstalling libsepol1... preinstalling belocs-locales-bin... preinstalling util-linux... running base-files preinstall script running base-files postinstall script chown: invalid user: `root:root' reordering.../var/tmp/build-root-xUbuntu_8.10-i586/.init_b_cache/rpms/readline-common.deb: not a debian package bad binary: readline-common.deb done removing nis flags from /var/tmp/build-root-xUbuntu_8.10-i586/etc/nsswitch.conf... now finalizing build dir... running debian transformer... chroot: cannot run command `su': No such file or directory ----------------------------------------------------------------- ----- building ib2008.dsc (user abuild) ----------------------------------------------------------------- ----------------------------------------------------------------- chroot: cannot run command `su': No such file or directory The buildroot was: /var/tmp/build-root-xUbuntu_8.10-i586 Does it have something to do with the restart of the build service today between 10 and 12? -- Richard -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Thu, Apr 02, 2009 at 01:05:06PM +0200, Richard Bos wrote:
ar: /var/tmp/build-root-xUbuntu_8.10-i586/.init_b_cache/rpms/readline-common.deb: File format not recognized
Your readline-common.deb doesn't seem to be a 'deb' package. What's the output of: file /var/tmp/build-root-xUbuntu_8.10-i586/.init_b_cache/rpms/readline-common.deb 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
Op donderdag 02 april 2009 14:18:53 schreef Michael Schroeder:
On Thu, Apr 02, 2009 at 01:05:06PM +0200, Richard Bos wrote:
ar: /var/tmp/build-root-xUbuntu_8.10-i586/.init_b_cache/rpms/readline-common. deb: File format not recognized
Your readline-common.deb doesn't seem to be a 'deb' package. What's the output of:
file /var/tmp/build-root-xUbuntu_8.10-i586/.init_b_cache/rpms/readline-common.de b
The .init_b_cache directory is not present: med111:~ # cd /var/tmp/build-root-xUbuntu_8.10-i586/.init_b_cache -bash: cd: /var/tmp/build-root-xUbuntu_8.10-i586/.init_b_cache: No such file or directory med111:~ # ls -l /var/tmp/build-root-xUbuntu_8.10-i586/ total 76 -rw-r--r-- 1 root root 338 Apr 2 17:35 .build-changelog -rw-r--r-- 1 root root 2382 Apr 2 17:35 .build.log lrwxrwxrwx 1 root root 16 Apr 2 17:35 .build.packages -> usr/src/packages -rw-r--r-- 1 root root 20 Apr 2 17:35 .buildenv -rw-r--r-- 1 root root 8 Apr 2 17:35 .guessed_dist drwxr-xr-x 2 root root 4096 Sep 25 2008 bin ....... That's after "osc build --clean xUbuntu_8.10 i586 *dsc" The cache contains: med111:/var/tmp/osbuild-packagecache/Ubuntu:8.10/standard # file ./all/readline-common-5.2-3build1.all.deb ./all/readline-common-5.2-3build1.all.deb: empty I removed that version. This resulted in "osc build" retrieving a new version and now the build finished successfully :) -- Richard -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, Mar 31, 2009 at 11:13:11AM +0200, Carsten Hoeger wrote:
On Mon, Mar 30, Paul Elliott wrote:
But it is not true. To see this look at the peless project:
+https://build.opensuse.org/package/show?package=peless&project=home%3Apelliott1 +1
It IS true. It's just that the debian package metadata is contained in the *.diff and *.dsc file(s). It's NOT contained in the *.spec file(s). That's what I wanted to make clear.
Well the way I read it, it is giving the impression that you must have files of the form debian.control, debian.rules, ect in the Files section. Now the info in these files has to be there somehow, directly or directly, but it can be concealed. In the .diff.gz file. For some people it is more convenient to work with true debian source packages. For example, I am the upstream source for the peless package. It is actually a package maintained by others in the official debian repository. If I want to check that my upstream changes I have made to the source do not require any changes to the debian files, I install the existing debian source package, and then do a "uupdate" with my new upstream source. That is what the debian people will do when I tell them about my upstream changes. I then upload the resulting debian source package to the build service and check that it builds correctly. When this happens I know that my package does not require any changes to the debian build files, or I know what those changes are. I then can report to the debian people what changes my new release will require if any to the debian build files. I never mess with files of the form debian.rules ect on the build service. Instead I always deal in true debian source packages. The documentation does not make it clear that this is an option unless you read it with a microscope. -- Paul Elliott 1(512)837-1096 pelliott@BlackPatchPanel.com PMB 181, 11900 Metric Blvd Suite J http://www.io.com/~pelliott/pme/ Austin TX 78758-3117
participants (6)
-
Carsten Hoeger -
Michael Schroeder -
Paul Elliott -
Paul Elliott
-
Piotr Pokora -
Richard Bos