On November 28, 2014 3:21:39 PM EST, Gour wrote:

Hello,

after many years I'm back to Suse and would like to create new package which is based on some existing one, iow. take existing one, rename it and modify.

What is the best way to accomplish it?

I was reading 'tutorial' but not sure whether 'branch' command is the way to go?

Sincerely, Gour

I see no value in branching. I would just: osc copypac <old project> <old package> <new project> <new package> In general osc has a thousand options, so it can do most anything you need done related to managing OBS. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Sat, 29 Nov 2014 08:52:33 +0100 Johannes Kastl wrote: Thank you all for the help.

If you want to modify a package (e.g. do a version update) and want to get these changes into the repository/project where the package is from, then branch is your friend.

Otherwise, as the others said, osc copypac creates a completely independent package, that has the same state and history as the package you copy from.

I want(ed) to create new package bogofilter-sqlite which is based on bogofilter but uses Sqlite3 database as storage back-end instead of default 'db' one. I did as advised and here is the package which works for me - I'm using it with Claws-mail with its bogofilter plugin. Result is here: https://build.opensuse.org/package/show/home:gour/bogofilter-sqlite First I was changing spec file and submitting via web, then I did build package locally and commit. Please, advice/correct me!! No need to tell, but I'd like that bogofilter ends up in openSUSE since I was using the same package in FreeBSD (http://www.freshports.org/mail/bogofilter-sqlite/), in Arch Linux (https://aur.archlinux.org/packages/bogofilter-sqlite/) as well in Debian Sid (https://packages.debian.org/sid/bogofilter-sqlite) from where did I migrate to SUSE. Sincerely, Gour -- An intelligent person does not take part in the sources of misery, which are due to contact with the material senses. O son of Kuntī, such pleasures have a beginning and an end, and so the wise man does not delight in them.

On November 29, 2014 6:49:21 AM EST, Gour wrote:

On Sat, 29 Nov 2014 08:52:33 +0100 Johannes Kastl wrote:

Thank you all for the help.

...

If you want to modify a package (e.g. do a version update) and want to get these changes into the repository/project where the package is from, then branch is your friend.

Otherwise, as the others said, osc copypac creates a completely independent package, that has the same state and history as the package you copy from.

I want(ed) to create new package bogofilter-sqlite which is based on bogofilter but uses Sqlite3 database as storage back-end instead of default 'db' one.

I did as advised and here is the package which works for me - I'm using it with Claws-mail with its bogofilter plugin.

Result is here:

https://build.opensuse.org/package/show/home:gour/bogofilter-sqlite

=> "Opensuse-factory" is no longer the preferred testing repo name. Drop it and add opensuse-tumbleweed. (Only announced a couple weeks ago, so most projects still use opensuse-factory, including mine, but you might as well start off with the new nomenclature). => On the WebUI near the build results you will find rpmlint results. The first 2 complaints you should fix before moving on. - change *.changes and *.spec to be named after the new package name. mv ... ... osc ar osc commit - do you really need to include "install" in the doc set? Fyi: just because the old package has rpmlint errors doesn't mean your new package should duplicate them.

First I was changing spec file and submitting via web, then I did build package locally and commit.

I try to do a local build of everything before I commit. I only locally build for opensuse-factory (I mean opensuse-tumbleweed) typically, then I commit working changes to OBS to verify the other distros I care about build correctly.

Please, advice/correct me!!

No need to tell, but I'd like that bogofilter ends up in openSUSE since I was using the same package in FreeBSD (http://www.freshports.org/mail/bogofilter-sqlite/), in Arch Linux (https://aur.archlinux.org/packages/bogofilter-sqlite/) as well in Debian Sid (https://packages.debian.org/sid/bogofilter-sqlite) from where did I migrate to SUSE.

Opensuse is a do-apoly - those that do decide. If you are willing to do the packaging work and commit to maintaining a package for the lifecycle of a release, then there are only 3 hurdles to overcome: - technical: does the packaging meet the opensuse guidelines? Does the package itself work? - legal: is the licensing either open source? If not, can a legal right to distribute be arranged? Also, is the package legal to distribute under both US and German law. German law prohibits pure hacking tools, so somethings legal in most countries are not allowed in opensuse. An example is metasploit; it would be a difficult sell to the release team to include it in factory, but it is legally distributed in the US. - security - some packages require a security review. I don't know when this is required/not required but I've got a package going through a security review now (my first). It won't be submitted to factory until that is complete. < http://bugzilla.opensuse.org/show_bug.cgi?id=900460>. Probably needed because it reaches out to Google during setup. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Gour writes:

I want(ed) to create new package bogofilter-sqlite which is based on bogofilter but uses Sqlite3 database as storage back-end instead of default 'db' one.

It would make much more sense to add a subpackage to the bogofilter package, since you are using identical sources just with a different configuration. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Sun, Nov 30, 2014 at 09:49:47AM +0100, Gour wrote:

Greg Freemyer wrote: I did some rpm-related reading about subpackages and not being sure whether I understood properly visited #rpm.org when I was told that one cannot have %build section per subpackage.

Moreover, I was suggested to create a new package and use 'Conflicts' in each one.

Remember, bogofilter and bogofilter-sqlite are actually *two different* and conflicting packages despite using the same source since both produce single executable, one uses (Berkeley) DB back-end and the other one uses Sqlite3.

So, considering the above do you still consider that subpackage is the appropriate solution and if yes, can you give some hint how to have different invocation of ./configure for main and subpackage?

Look at the php5 package. Subpackages will not work, if two (sub-)packages need to ship different content for one path. In that case, you could put two spec files in one OBS packages (see binutils/gcc). Regards, Martin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Sun, 30 Nov 2014 09:29:19 -0500 Greg Freemyer wrote: Hello Greg, excuse me for not replying earlier...I hit some btrfs bug, lost my parition, had to re-install, restore (older) backup from tapes, re-configure eveything etc.

The trick with that approach as it relates to bogofilter/bogofilter-sqlite is you have to have a separate package for each, but the packages should be linked, not standalone.

OK. That's clear.

In this case bogofilter and bogofilter-sqlite would be linked packages.

I did the above - linkpac and checkout stuff into my folder @localhost.

You would have 2 spec files: bogofilter.spec and bogofilter-sqlite.spec

Now some questions: 1) is it required to use 'linkpac -C copy' when doing linkpac? 2) when I do linkpac, I end up with bogofilter.spec in the bogofilter-sqlite folder, so I wonder how should I create bogofilter-sqlite.spec, iow. is it actually just modified spec file incorporating required changes to build it? 3) does bogofilter-sqlite folder contain both spec files?

The bogofilter package will automatically ignore the bogofilter-sqlite.spec file and vice versa. (just be sure to name the spec files after the project names; obs knows what to do from that point.)

4) how should one do the build, by running 'osc build bogofilter.spec' ?

The packages share the tarball, patches, and changes file so no extra maintenance is needed to maintain both. And it becomes obvious to people modifying one of the spec files they need to modify both.

It sounds good. Otoh, I was looking for help in IRC today (#opensuse-buildservice) and I was suggested (darix provided example) to use update-alternatives mechanism in order so that different users can use different packages installed simultenaously and in that case binary would be bogofilter-sqlite instead of default bogofilter? Please, advice! Sincerely, Gour -- -- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Tue, Dec 9, 2014 at 1:46 PM, Gour wrote:

On Sun, 30 Nov 2014 09:29:19 -0500 Greg Freemyer wrote:

Hello Greg,

excuse me for not replying earlier...I hit some btrfs bug, lost my parition, had to re-install, restore (older) backup from tapes, re-configure eveything etc.

...

The trick with that approach as it relates to bogofilter/bogofilter-sqlite is you have to have a separate package for each, but the packages should be linked, not standalone.

OK. That's clear.

...

In this case bogofilter and bogofilter-sqlite would be linked packages.

I did the above - linkpac and checkout stuff into my folder @localhost.

...

You would have 2 spec files: bogofilter.spec and bogofilter-sqlite.spec

Now some questions:

1) is it required to use 'linkpac -C copy' when doing linkpac?

I'm not positive

2) when I do linkpac, I end up with bogofilter.spec in the bogofilter-sqlite folder, so I wonder how should I create bogofilter-sqlite.spec, iow. is it actually just modified spec file incorporating required changes to build it?

Yes, the second one is just a copy of the first with modifications.

3) does bogofilter-sqlite folder contain both spec files?

Yes, both packages will contain both spec files. the package "bogofilter" will use spec file "bogofilter.spec" the package "bogofilter-sqlite" will use spec file "bogfilter-sqlite.spec" That will happen automatically if you have 2 projects and the spec files are named after the projects.

...

The bogofilter package will automatically ignore the bogofilter-sqlite.spec file and vice versa. (just be sure to name the spec files after the project names; obs knows what to do from that point.)

4) how should one do the build, by running 'osc build bogofilter.spec' ?

"osc build" is fine. osc knows what project you are trying to build and will select the matching spec file automatically.

...

The packages share the tarball, patches, and changes file so no extra maintenance is needed to maintain both. And it becomes obvious to people modifying one of the spec files they need to modify both.

It sounds good.

Otoh, I was looking for help in IRC today (#opensuse-buildservice) and I was suggested (darix provided example) to use update-alternatives mechanism in order so that different users can use different packages installed simultenaously and in that case binary would be bogofilter-sqlite instead of default bogofilter?

Please, advice!

Above my pay grade. I've never setup an update-alternatives situation.

Sincerely, Gour

Greg -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Tue, Dec 9, 2014 at 6:02 PM, Gour wrote:

On Tue, 9 Dec 2014 17:22:23 -0500 Greg Freemyer wrote:

...

Yes, the second one is just a copy of the first with modifications.

OK.

...

Yes, both packages will contain both spec files.

So, considering that after I linkpac-ed bogofilter to bogofilter-sqlite and then checkout out it locally, and that there is already bogofilter.spec in the checkout out sources, it means that I have to add bogofilter-sqlite.spec file to both packages?

...

"osc build" is fine. osc knows what project you are trying to build and will select the matching spec file automatically.

That's still a magic for me, but I believe you. ;)

...

Above my pay grade. I've never setup an update-alternatives situation.

OK. I'll postpone it for later then. This setup looks seems to be simpler.

Here you can see result of my attempts:

https://build.opensuse.org/project/show/home:gour

Does it look good in regard to main package with the linked one?

Almost: Look at https://build.opensuse.org/package/show/home:gour/bogofilter-sqlite In the upper right corner it says there is a "link diff" between the 2 packages. We don't want that, but you MUST solve it via a SR. To create a SR from the WebUI, click on the blue "link diff" text. When the new page comes up, first review it and make sure you want to submit those changes to "bogofilter". If so, scroll down to the bottom and click "Submit to home:gour / bogofilter" Since you are the maintainer of "home:gour / bogofilter" you will receive a notification that a SR (submit request) has been sent to relative to bogofilter. You will need to accept that SR. Hope that makes sense, Greg -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Gour writes:

3) does bogofilter-sqlite folder contain both spec files?

Forget about the bogofilter-sqlite directory once you've created the link. All edits go to the original package directory. Also, you need to create bogofilter-sqlite.changes which records the changes for the bogofilter-sqlite package. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Wed, 10 Dec 2014 09:02:13 +0100 Andreas Schwab wrote:

Forget about the bogofilter-sqlite directory once you've created the link. All edits go to the original package directory.

Does it mean that after I do linkpac, I need only top checkout bogofilter and there add bogofilter-sqlite.spec?

Also, you need to create bogofilter-sqlite.changes which records the changes for the bogofilter-sqlite package.

That one also goes just in bogofilter directory? Sincerely, Gour -- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org