Adrian Schröter wrote:

On Tuesday 12 June 2007 08:27:21 wrote Adrian Schröter:

...

I have just added a Fedora:7/standard repository. It seems to work so far but needs some more testing ...

Fedora:Extras6 got updated to the current state.

Mandriva:2007 got imported already a while ago, but it is not working yet. If someone has time to find out why the glibc %post fails on build setup ... ;)

and Ubuntu:7.04 got added as well ...

Much appreciated. Thanks. Will there be a distinction between Fedora Core and Extras like we have with 5 and 6?

They will appear on the "simple add target" with next deploy.

Under what names? (so I can chose the same names when doing it manually) +Thomas -- Thomas Anders (thomas.anders at blue-cable.de) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Well, the errors continue there: On Tuesday 12 June 2007 11:07:37 Adrian Schröter wrote:

Fedora_7 have choice for kernel >= 2.6.20-1.3087.fc7 needed by libraw1394: kernel-debug kernel-PAE-debug kernel-PAE kernel kernel-xen

Mandriva_2007 have choice for devel(libneon) needed by subversion-devel: libneon0.26-devel libneon0.24-devel, have choice for kde-config-file needed by kdelibs-common: powerpackplus-kde-config [...]

xUbuntu_7.04 dpkg-source: error: Files field contains invalid filename `kdevelop_4:3.4.1.orig.tar.bz2'

-- Amilcar Lucas Webmaster The KDevelop project --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Thanks for the fixes Michael, now only one remanins: now finalizing build dir...running debian transformer... package contains more than one tar file: kdevelop-3.4.1.tar.bz2 xUbuntu_6.06.tar.gzd pkg-source: error: cannot open .dsc file /usr/src/packages/SOURCES.DEB/*.dsc: No such file or directory -- Amilcar Lucas Webmaster The KDevelop project --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Hi Michael, Am Freitag, den 15.06.2007, 12:20 +0200 schrieb Michael Schroeder:

On Thu, Jun 14, 2007 at 08:12:26PM +0200, Amilcar do Carmo Lucas wrote:

...

Thanks for the fixes Michael, now only one remanins:

now finalizing build dir...running debian transformer... package contains more than one tar file: kdevelop-3.4.1.tar.bz2 xUbuntu_6.06.tar.gzd pkg-source: error: cannot open .dsc file /usr/src/packages/SOURCES.DEB/*.dsc: No such file or directory

Yes, but that's a bug in your package: you can't have multiple tar balls in a debian package.

you can have multiple tar balls in a package. But it's working like this: <source>_<version>.orig.tar.gz consists of tarball1.tar.gz tarball2.tar.gz you create then something like this (speaking of real debian packages): <source>-<version>/ tarball1.tar.gz tarball1.tar.gz debian/ control changelog rules in the debian/rules file you take care of untarring the files etc. Then it's possible to provide more then one tarball in a source package. Regards, \sh --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Hi, Am Freitag, den 15.06.2007, 13:50 +0200 schrieb Amilcar do Carmo Lucas:

...

Hi Michael,

Am Freitag, den 15.06.2007, 12:20 +0200 schrieb Michael Schroeder:

...

On Thu, Jun 14, 2007 at 08:12:26PM +0200, Amilcar do Carmo Lucas wrote:

...

Thanks for the fixes Michael, now only one remanins:

now finalizing build dir...running debian transformer... package contains more than one tar file: kdevelop-3.4.1.tar.bz2 xUbuntu_6.06.tar.gzd pkg-source: error: cannot open .dsc file /usr/src/packages/SOURCES.DEB/*.dsc: No such file or directory

Yes, but that's a bug in your package: you can't have multiple tar balls in a debian package. I do not want to have multiple tar files in a debian, I want it to only use

On Friday 15 June 2007 12:48:23 Stephan Hermann wrote: the kdevelop.tar.bz2 file that I provide in the .dsc file and ignore all others. That is why the .dsc file exists, right ? To tell what files should be used.

The .dsc file is generated, when you normally debuild your debianized tar ball, means kdevelop-x.y.z/debian/ exists with all necessary files (which you have to do in the first step). Having a kdevelop_x.y.z.orig.tar.gz and calling debuild in the debianized source tree, gives you the .dsc file and the diff.gz file, which includes all changes against the upstream orig tarball. The .dsc file gives you a proper description of the debian source package. (Maintainer, source package name, arch etc.) It includes as well a files section, e.g. Files: ebe8fe526c7c9c3e7c543645b383612c 9594 asoundconf-gtk_1.5.1.orig.tar.gz 5e2786bc429c1f27c017bcfb7edee2d7 2935 asoundconf-gtk_1.5.1-0ubuntu2.diff.gz To give the build service the clue about what files are belonging to this source package and if the md5 sums are matching with the uploaded files. So, if you want to create a source debian package you need to create your .dsc file with the usual debian development utils. debuild will check for the tar.gz file (if you have a <source>-<version>.tar.gz it will symlink it to <source>_<verion>.orig.tar.gz) and will create your .dsc file. You can test your build of debian source package e.g. on debian with pbuilder, which is the debian brother to "build" on suse. Actually I'm working on building debian packages on the opensuse build service, but when Adrian and the others implemented the correct behaviour they will check against all this. 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 Friday 15 June 2007 15:37:53 Michael Schroeder wrote:

On Fri, Jun 15, 2007 at 01:50:29PM +0200, Amilcar do Carmo Lucas wrote:

...

I do not want to have multiple tar files in a debian, I want it to only use the kdevelop.tar.bz2 file that I provide in the .dsc file and ignore all others. That is why the .dsc file exists, right ? To tell what files should be used.

Yeah, but the "debtransform" utility rewrites the file list. So either don't use debtransform (delete debian.tar.gz and use standard debian package layout) or have just one tarball. Currently there's no way to tell debtransform which tarball to use. well, I still think this is a bug, debtransform should ignore all debian-*.tar.* files:

package contains more than one tar file: kdevelop-3.4.1.tar.bz2 debian-xUbuntu_6.06.tar.gz dpkg-source: error: cannot open .dsc file /usr/src/packages/SOURCES.DEB/*.dsc: No such file or directory -- Amilcar Lucas Webmaster The KDevelop project --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Hi Michael, Am Freitag, den 15.06.2007, 20:29 +0200 schrieb Michael Schroeder:

On Fri, Jun 15, 2007 at 05:11:32PM +0200, Amilcar do Carmo Lucas wrote:

...

well, I still think this is a bug, debtransform should ignore all debian-*.tar.* files:

What's the point of having those tar files then?

There is no point, more then one debian dir is useless. But I think I know why Amilcar put them there. Backporting applications to different debian/ubuntu releases. But this is done in using correct values in debian/control for build and/or install dependencies. Example: wine in ubuntu feisty and new dev release gutsy. It will use two different versions of libstdc++, to make it easier for the ubuntu backporting guys, you use the following notation: libstdc++4.2-dev | libstdc++4.1-dev | libstdc++-dev in the Build-Dependency section. The build environment of debian/ubuntu (e.g. the sbuild or pbuilder) is reading those dependencies correctly. It reads from left to right: if libstdc++4.2-dev is availbale, use it first if libstdc++4.2-dev is not there, check for libstdc++4.1 and use it when it's available if the first two are not available use the last version. there is no need for different debian.tar.gzs or better to say different debian/ directories.

...

package contains more than one tar file: kdevelop-3.4.1.tar.bz2 debian-xUbuntu_6.06.tar.gz dpkg-source: error: cannot open .dsc file /usr/src/packages/SOURCES.DEB/*.dsc: No such file or directory

I have added support for some configuration options to debtransform. You can now override the default matches with some .dsc file attributes:

Debtransform-Tar: <pristine-tar-ball> Debtransform-Series: <quilt-series-file> Debtransform-Files-Tar: <tar-ball-containing-debian directory files>

How do you use them with dpkg-source? I don't think this is a good idea to go far away from the default debian standard. Regards, \sh -- Stephan Hermann eMail: sh@sourcecode.de Blog: http://linux.blogweb.de/ JID: sh@linux-server.org OSS-Developer and Admin

Hi Amilcar, Am Samstag, 16. Juni 2007 02:51 schrieb Amilcar do Carmo Lucas:

On Saturday 16 June 2007 01:09:31 Stephan Hermann wrote:

...

Hi Michael,

Am Freitag, den 15.06.2007, 20:29 +0200 schrieb Michael Schroeder:

...

On Fri, Jun 15, 2007 at 05:11:32PM +0200, Amilcar do Carmo Lucas wrote:

...

well, I still think this is a bug, debtransform should ignore all debian-*.tar.* files:

What's the point of having those tar files then?

There is no point, more then one debian dir is useless. But I think I know why Amilcar put them there. Backporting applications to different debian/ubuntu releases.

Exactly, that was the point, diferent ubuntu versions need diferent "debian/control" files.

Well, the good thing about debian, it's canonical ;) You don't need two or more debian dirs for different releases. The "stableness" of debian is set, just because you can "reuse" many things from old versions and even new versions can be compiled on old releases. You just have to use the techniques, which are already there. That's why the debian maintainers are telling you always this: "Please, if you want to package for debian, please read the Debian new maintainer guide". TBH, it's important that you know what you are doing.

...

But this is done in using correct values in debian/control for build and/or install dependencies. Example: wine in ubuntu feisty and new dev release gutsy. It will use two different versions of libstdc++, to make it easier for the ubuntu backporting guys, you use the following notation:

libstdc++4.2-dev | libstdc++4.1-dev | libstdc++-dev

in the Build-Dependency section. The build environment of debian/ubuntu (e.g. the sbuild or pbuilder) is reading those dependencies correctly. It reads from left to right:

if libstdc++4.2-dev is availbale, use it first if libstdc++4.2-dev is not there, check for libstdc++4.1 and use it when it's available if the first two are not available use the last version.

I did not know that !!! thanks for the tip!!!

You're welcome. But don't expect too much from it. This notation and the interpretation of it can be different from the build system you are using. e.g. on an workstation at home, you are using on debian/ubuntu normally the pbuilder package to have a cool and easy build environment. I think, you can compare it with the build .rpm from your favorite distro. It gives you a chroot with the distro you want to build for, and it installs all build deps the package, you are building, is needing. But, pbuilder was reading the build deps in the "or" notation from left to right, whereas sbuild, mostly used on the debian and ubuntu build server, for automatic building, is ( or was, in the past there was a change) reading this notation from right to left. So, this is the pitfall. The tools are there, but sometimes are not always speaking the right language. Depending on how the opensuse buildservice is reading the debian/control file, you can have luck and it works flawlessly, but if not, well, we have to find a solution. Regards, \sh -- Stephan Hermann eMail: sh@sourcecode.de         Blog: http://linux.blogweb.de/ JID: sh@linux-server.org         OSS-Developer and Admin

On Sat, Jun 16, 2007 at 01:09:31AM +0200, Stephan Hermann wrote:

...

Debtransform-Tar: <pristine-tar-ball> Debtransform-Series: <quilt-series-file> Debtransform-Files-Tar: <tar-ball-containing-debian directory files>

How do you use them with dpkg-source?

"Debtransform" removes those tags.

I don't think this is a good idea to go far away from the default debian standard.

That's the whole point of "debtransform", to create a debian conforming package from multiple patches and files. 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, Jun 18, 2007 at 10:45:07AM +0200, Stephan Hermann wrote:

Am Montag, den 18.06.2007, 09:53 +0200 schrieb Michael Schroeder:

...

"Debtransform" removes those tags.

Well, where do you put them?

In the .dsc file.

To have some of those tags you normally add them to debian/control. dpkg-source checks the debian/control file, and add some of those tags to the resulting .dsc file.

The build service works a bit different, as it already expects a .dsc file. It needs it to calculate the build dependencies. The control file would also have worked, but it is normally hidden in some big patch... (It works like this for rpm, too: you need a spec file for the build, but the build also creates a .src.rpm, which includes the spec file again.) 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, Jun 18, 2007 at 11:27:05AM +0200, Stephan Hermann wrote:

Well, yeah. But normally when you create the .dsc file, you just have the debianized source tree and the orig.tar.gz file. You call then dpkg-source -b <debianized source directory> and the .dsc file is created. So, it has to be, before the dpkg-source call, in the debian/control file (normally the .dsc file is signed, so it's a bad idea to add some tags to the already signed .dsc file)

Yes, understood, but the build service actually offers two ways to build debian packages: 1) standard debian way: provide a (signed) .dsc file, a pristine _orig tarball and a .diff file. 2) debtransform way: provide a .dsc file, a tar ball, some patches, and some debian files (optionally in a tar archive). It transforms those file into a standard debian package and builds a .deb. Currently the build service doesn't put the resulting .dsc and .diff file in the debian repository, but this will change. 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