On Saturday 25 February 2012, Jan Engelhardt wrote:

On Saturday 2012-02-25 11:32, Ruediger Meier wrote:

...

Hi,

is there a macro to get the current build project? I'd like to have a string like "SLE_11_SP1" available within spec file.

What exactly for? The answer would depend on that :)

I need it within %install and %files, something like %install cp xyz.tar.xz %{buildroot}/releases/SLE_11_SP1/ %files release-tarball /releases/SLE_11_SP1/xyz.tar.xz Of course I will not use it for official distributed rpms. I want to build "make dist" tar balls on OBS and ship them within sub-package "*-release-tarball". unrpm should sort the tarballs from different projects into meaningful subdirs. I found that %distribution is amlost what I need but I need to sed it to make it a nice path. cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Sunday 26 February 2012, Jan Engelhardt wrote:

On Saturday 2012-02-25 14:05, Ruediger Meier wrote:

...

On Saturday 25 February 2012, Jan Engelhardt wrote:

...

On Saturday 2012-02-25 11:32, Ruediger Meier wrote:

...

Hi,

is there a macro to get the current build project? I'd like to have a string like "SLE_11_SP1" available within spec file.

What exactly for? The answer would depend on that :)

I need it within %install and %files, something like

I think "%_repository" it is, but I still advise against using it, as the result is "unpredictable". Some people call their repo part SLE_11_SP1. Some SLE_11 (implying SP1). And whatever else.

Thx, I'll give it a go.

...

%install cp xyz.tar.xz %{buildroot}/releases/SLE_11_SP1/

As such, the user of your weird rpm would have to go into a directory whose name does not remain constant.

Yep, I force the "user" to use unrpm only. Requires: do_not_install_this_but_unrpm :) I only want to have different paths to not always overwrite tarballs when unrpm'ing them from different distros.

...

%files release-tarball /releases/SLE_11_SP1/xyz.tar.xz

Of course I will not use it for official distributed rpms. I want to build "make dist" tar balls on OBS and ship them within sub-package "*-release-tarball".

I feel that is quite pointless, since the tarball is already provided within the .src.rpm.

No, in my case the src tarball is a "git export" (with lots of build requires) and the destination tarball is a "make dist" tar ball to be used by endusers. I'm doing all this to release upstream projects doing autoreconf, make check, make distcheck etc. on clean OBS hosted distros. Its really nice. Maybe you want to see our dateutils package https://build.opensuse.org/package/files?package=dateutils&project=home%3Arudi_m%3Adevel-snap The package is automatically updated from git repo using this script https://gist.github.com/1200424 After upstream tags a new release then the resulting tarball (from a preferred distro) will be published (by upstream) to be finally used to make rpms for the endusers, e.g. here in OBS utilities repo: https://build.opensuse.org/package/show?package=dateutils&project=utilities cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Sunday 26 February 2012, Jan Engelhardt wrote:

On Sunday 2012-02-26 15:10, Ruediger Meier wrote:

...

Yep, I force the "user" to use unrpm only. Requires: do_not_install_this_but_unrpm No, in my case the src tarball is a "git export" (with lots of build requires) and the destination tarball is a "make dist" tar ball to be used by endusers.

I'm doing all this to release upstream projects doing autoreconf, make check, make distcheck etc. on clean OBS hosted distros.

Noble attempt, but you are leaving the user with more than one distified tarball, whose contents are also dependent upon a particular distro. That reeks of release mismanagement.

Hehe, the only "user" here is the release manager himself. He can compare and test all the distified tarballs to elect exactly one (or none) for the official download site. However maybe it would be better to not publish these tarball rpms. It's a bit pity that you cant't unpublish just a sub-package or is this possible nowadays? BTW the funny thing is that upstream developers usually never use their own tar releases at all except for publishing it one time (hopefully after tesing it).

...

[...] The package is automatically updated from git repo using this script https://gist.github.com/1200424

OBS can automatically pull git snapshots, you do not strictly have to push them yourself. (I do however prefer explicit pushs myself.)

Good to know, but I think it can't be possible to get the same comfort (selecting branches/commits/origins quickly at the command line). In my use case I even have to push because the origin git must be a private one. The release tag will be only pushed to a public repo after all that OBS stuff above has been finished successfully. cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Quoting Jan Engelhardt :

On Sunday 2012-02-26 17:46, Ruediger Meier wrote:

...

On Sunday 26 February 2012, Jan Engelhardt wrote: However maybe it would be better to not publish these tarball rpms. It's a bit pity that you cant't unpublish just a sub-package or is this possible nowadays?

Wasn't it <publish><disable/></publish> combined with `osc wipebinaries`?

Unpublishing a sub package only is not possible. It's all binaries of the package that get wiped. BUT: you can create a project filter to not have packages published at all. osc meta -e prjconf <yourProject> then add something like this to the config: ExportFilter: ^MyNiftyPackage-.*\.rpm$ . This is a simply regexp matching what you do not want published, all other packages will get published (if so enabled). Hope that helps, Dominique -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Sunday 26 February 2012, Marcus Hüwe wrote:

On 2012-02-26 13:05:54 -0500, Dominique Leuenberger a.k.a DimStar wrote:

...

Quoting Jan Engelhardt :

...

On Sunday 2012-02-26 17:46, Ruediger Meier wrote:

...

On Sunday 26 February 2012, Jan Engelhardt wrote: However maybe it would be better to not publish these tarball rpms. It's a bit pity that you cant't unpublish just a sub-package or is this possible nowadays?

Wasn't it <publish><disable/></publish> combined with `osc wipebinaries`?

Unpublishing a sub package only is not possible. It's all binaries of the package that get wiped. BUT: you can create a project filter to not have packages published at all.

osc meta -e prjconf <yourProject> then add something like this to the config:

ExportFilter: ^MyNiftyPackage-.*\.rpm$ .

This is a simply regexp matching what you do not want published, all other packages will get published (if so enabled).

It should be "PublishFilter" instead of "ExportFilter".

Thanks both of you for the hints. Actually I'am trying ExportFilter: ^.*-release-tarball.*\.rpm$ . It will take a while before seeing the result so I wonder if I should better use PublishFilter: ^.*-release-tarball.*\.rpm$ . with or without trailing dot? BTW is it possible to browse /srv/obs/repos somehow without waiting for the mirror sync? cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Sunday 2012-02-26 19:51, Ruediger Meier wrote:

BTW is it possible to browse /srv/obs/repos somehow without waiting for the mirror sync?

osc ls -b osc getbinaries -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org