2014-07-05 6:44 GMT+09:00 1xx :

2. Request For Comments! I am thinking whether I should divide a package into three. That is ... (etckeeper - The package that three packages were gathered up in one.) etckeeper-common - etckeepr main function. etckeeper-cron - cron function. etckeeper-packagemanager-collabo - collabolation with package manager.

By dividing it into three, users can choose the functions A problem is that .spec is complicated. Which package do you prefer?

I divided etckeeper package into 3. etckeeper - etckeepr main function. etckeeper-cron - cron function. etckeeper-pkgmanager-collabo - collabolation with package manager. https://build.opensuse.org/package/show/home:Mitsutoshi:branches:home:Mitsut... I am testing it now. -- 1xx https://twitter.com/ItSANgo Mitsutoshi NAKANO http://d.hatena.ne.jp/Itisango/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Le 09/07/2014 00:58, 1xx a écrit :

2014-07-07 8:53 GMT+09:00 1xx :

...

2014-07-05 6:44 GMT+09:00 1xx :

I divided etckeeper package into 3.

etckeeper - etckeepr main function. etckeeper-cron - cron function. etckeeper-pkgmanager-collabo - collabolation with package manager. I am testing it now. My test was finished.

Test report is https://docs.google.com/spreadsheets/d/1kmtjqvCnqNMmuFHRLh0-xh1iBdjhxnvKoYgR...

The package is https://build.opensuse.org/package/show/home:Mitsutoshi:branches:utilities/e...

Changes: - modified etckeeper.spec style by "osc service run format_spec_file". - removed lint code 'rm -rf "{buildroot}{_prefix}/lib"/python*'. This line does not work. - removed "Requires: git". users can select VCS. - divide etckeeper package into 3. + etckeeper: main function. + etckeeper-cron: cron function. + etckeeper-pkgmanager-collabo: collaboration with package manager. - fix (bnc#884154): forgot to reqire zypp-plugin-python.

I will submitrequest to utilities/etckeeper.

Please review it, and accept or decline it.

The correct stuff for python is rm -rf "{buildroot}%{python_sitelib}" rm -rf "{buildroot}{_prefix}/lib"/python -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

denisart benjamin2 wrote:

The correct stuff for python is rm -rf "{buildroot}%{python_sitelib}"

Thanks. But I think it is not necessary with etckeeper. 2014-07-09 9:05 GMT+09:00 Christian Boltz :

Am Mittwoch, 9. Juli 2014 schrieb 1xx:

...

- removed "Requires: git". users can select VCS.

Too bad that rpm doesn't support "or" in the Requires: tag ;-)

Nevertheless, you should add a "Recommends: git" - that's the most likely choice nowadays.

Thanks. I will rewrite so etckeeper.spec.

Just a little detail - I assume you mean integration with zypp (libzypp, zypper, YaST), right? A packagename like etckeeper-zypp-integration might be a better choice ;-)

I think that etckeeper-zypp-plugin is better. Because already snapper-zypp-plugin exists.

After reading the spec, I see that you package a yum plugin if suse_version is not set. The funny thing is that yum is also available for openSUSE [1], so you should also provide a package etckeeper-yum- integration for openSUSE ;-)

Hurm... The upstream can choose with both yum and ZYpp. But both can not choose. If we want it, we must make a big patch. I want time to think it. I think that better package name is etckeeper-yum-plugin. Thanks Christian, Denisart, and all!

[1] zypper in yum # and probably some subpackages, see zypper se yum (I just noticed it's available, but never used it.)

-- 1xx https://twitter.com/ItSANgo Mitsutoshi NAKANO http://d.hatena.ne.jp/Itisango/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

2014-07-10 1:14 GMT+09:00 1xx :

I will write test-specification tomorrow.

I found some problems. So I rebuild etckeeper again. etckeeper.changes: https://build.opensuse.org/package/view_file/home:Mitsutoshi:branches:utilit... https://build.opensuse.org/package/show/home:Mitsutoshi:branches:utilities/e... https://build.opensuse.org/package/view_file/home:Mitsutoshi:branches:utilit... I wrote the test-specification. https://docs.google.com/spreadsheets/d/1kmtjqvCnqNMmuFHRLh0-xh1iBdjhxnvKoYgR... Please review the etckeeer and test-specification. You can write comments in the test-specification. And if you want to test the etckeeper, I welcome you. Thanks. -- 1xx https://twitter.com/ItSANgo Mitsutoshi NAKANO http://d.hatena.ne.jp/Itisango/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

2014-07-13 12:58 GMT+09:00 1xx :

I will rebuild the etckeeper, please wait it. https://build.opensuse.org/package/show/home:Mitsutoshi:branches:utilities/e...

I rebuilt it. I wrote the test-specification. https://docs.google.com/spreadsheets/d/1kmtjqvCnqNMmuFHRLh0-xh1iBdjhxnvKoYgR... Please review the etckeeer and test-specification. You can write comments in the test-specification. And if you want to test the etckeeper, I welcome you. -- 1xx https://twitter.com/ItSANgo Mitsutoshi NAKANO http://d.hatena.ne.jp/Itisango/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Hello, Am Donnerstag, 10. Juli 2014 schrieb 1xx:

2014-07-09 12:30 GMT+09:00 1xx :

...

2014-07-09 9:05 GMT+09:00 Christian Boltz :

...

...

Just a little detail - I assume you mean integration with zypp (libzypp, zypper, YaST), right? A packagename like etckeeper-zypp-integration might be a better choice ;-)

I think that etckeeper-zypp-plugin is better. Because already snapper-zypp-plugin exists.

Indeed, that's even better than my proposal :-)

...

...

After reading the spec, I see that you package a yum plugin if suse_version is not set. The funny thing is that yum is also available for openSUSE [1], so you should also provide a package etckeeper-yum- integration for openSUSE ;-)

Hurm...

The upstream can choose with both yum and ZYpp. But both can not choose. If we want it, we must make a big patch.

I assume you tested this already, but let me ask nevertheless. What about this: (from the spec, marked line added) %if 0%{?suse_version} ... BuildRequires: libzypp BuildRequires: yum # <----- try adding this line %define HPM zypper %else BuildRequires: yum ... %define HPM yum %endif The config file (where the HPM variable is used) will/should be hardcoded to zypp, but besides that it could work. (Needless to say that I didn't test this ;-) Anyway - zypp integration is the most important on openSUSE. yum is just "nice to have", and I wonder if people use yum if they have zypper ;-) Regards, Christian Boltz -- Ich habe ein update für 2.0.1 released, welches die Änderung im Makefile auf die alte Version zurück"portiert" (Was für ein großes Wort für zwei Anführungsstriche). [Ratti in fontlinge-devel - nach Änderung von zwei »'« zu »"« in einem Makefile] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Hello, (sorry for the delay!) Am Montag, 14. Juli 2014 schrieb 1xx:

2014-07-14 1:25 GMT+09:00 Christian Boltz :

...

What about this: (from the spec, marked line added)

%if 0%{?suse_version} ... BuildRequires: libzypp BuildRequires: yum # <----- try adding this line

Thank you for being interested in etckeeper.

I added it.

But upstream Makefile supports only 1 HIGHLEVEL_PACKAGE_MANAGER. http://git.kitenet.net/?p=etckeeper.git;a=blob;f=Makefile;h=cf034a2d50 98ec6d1b2c405c916d5aeb5b1f35be;hb=52582f72a50502bc467abf679618b7c10159 2e74

And /etc/etckeeper/etckeeper.conf have to write only 1 HIGHLEVEL_PACKAGE_MANAGER. http://git.kitenet.net/?p=etckeeper.git;a=blob;f=etckeeper.conf;h=f988 c10e4d27427727572853cc2d2066193045b6;hb=52582f72a50502bc467abf679618b7 c101592e74

For building yum-plugin in openSUSE, I called "make" and "make install" twice for YUM and ZYpper in spec_file. https://build.opensuse.org/package/view_file/home:Mitsutoshi:branches :utilities/etckeeper/etckeeper.spec?expand=1 (I will rollback this package soon.)

Sounds like a funny workaround ;-)

I culd build yum-plugin on openSUSE. Now openSUSE users may be able to choose YUM or zypper. (I do not test yet.)

But we have 2 problems.

1. We have a bug.

At present, it seems that etckeeper use $HIGHLEVEL_PACKAGE_MANAGER only for logging messages . But if we use double package-managers, We have a bug. For example, when HIGHLEVEL_PACKAGE_MANAGER=zypper in etckeeper.conf, if we type "yum erase package", then VCS log says "zypper run".

Oh, how nice. You can configure the log message in the config file ;-) I wonder what happens if you set HIGHLEVEL_PACKAGE_MANAGER="grin, duck and" *g,d&r* Please open a bugreport for this upstream and ask them to let the zypp/yum plugins specify the log message. Those plugins should know who/what called them ;-)

2. It is very tricky. The upstream do not think that users use 2 package-managers.

In spite of it, if we use 2 package-managers, I am afraid we have troubles.

Well, at least it needs some testing ;-) (but in theory it shouldn't cause major problems)

If we want to use both ZYypper and YUM, we must modify many source files. We need to talk with upstream.

I think that openSUSE's etckeeper should support only zypper, and I think that supporting YUM is future study.

Yes, I agree. If upstream doesn't support using two package managers, then it doesn't make sense to implement this for openSUSE only. Talking with upstream is the way to go - and when upstream supports using more than one packagemanager one day, it's easy to add to the openSUSE package. Regards, Christian Boltz -- No, you are wrong here. Typical user does not even know how to start command line, and of course is not aware of "zypper" or how to understand "zypper ps" output. Subscribers to -devel lists are in no way typical users. [Andrey Borzenkov in opensuse-factory] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Christian Boltz Wed, 09 Jul 2014 03:05:44 +0300:

Hello,

Am Mittwoch, 9. Juli 2014 schrieb 1xx:

...

- removed "Requires: git". users can select VCS.

Too bad that rpm doesn't support "or" in the Requires: tag ;-)

Nevertheless, you should add a "Recommends: git" - that's the most likely choice nowadays.

Blank subpackages can be used to resolve it: name-git that requires git and name-hg that requires mercury. Both should provide name-cvs and main package should require it. -- Best regards, Dmitriy DA(P).DarkneSS Perlow @ Linux x64 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

1xx writes:

Does it mean the following ?

-------- main.spec -------- Name: main Requires: name-vcs

%package name-git

That should be written as "%package git", otherwise the name of the package will be name-name-git. 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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

1xx Wed, 09 Jul 2014 13:41:03 +0300:

Thanks Dmitriy, Andreas, and all.

2014-07-09 14:20 GMT+09:00 1xx :

...

2014-07-09 13:10 GMT+09:00 Dmitriy Perlow :

...

Christian Boltz Wed, 09 Jul 2014 03:05:44 +0300:

...

Am Mittwoch, 9. Juli 2014 schrieb 1xx:

...

- removed "Requires: git". users can select VCS.

...

...

...

Too bad that rpm doesn't support "or" in the Requires: tag ;-)

Nevertheless, you should add a "Recommends: git" - that's the most likely choice nowadays.

Blank subpackages can be used to resolve it: name-git that requires git and name-hg that requires mercury. Both should provide name-cvs and main package should require it.

Does it mean the following ?

...

I will check it on my PC.

I am checking "blank subpackages".

https://build.opensuse.org/package/show/home:Mitsutoshi:spectest/spectest https://build.opensuse.org/package/view_file/home:Mitsutoshi:spectest/specte...

-------- in spectest.spec -------- Name: spectest (snip) Requires: %{name}-vc

%package git Summary: The git stub Group: System/Management Requires: git Provides: %{name}-vc (snip)

%package bzr Summary: The bzr stub Group: System/Management Requires: bzr Provides: %{name}-vc

--------

When I do not install any VCS, zypper shows spectest-git.

--------

...

LANG=C sudo zypper install spectest Loading repository data... Reading installed packages... Resolving package dependencies...

The following 3 NEW packages are going to be installed: git spectest spectest-git

3 new packages to install. Overall download size: 61.8 KiB. After the operation, additional 2.6 KiB will be used. Continue? [y/n/? shows all options] (y): --------

And when I installed bzr, zypper shows spectest-bzr.

--------

...

LANG=C sudo zypper install spectest Loading repository data... Reading installed packages... Resolving package dependencies...

The following 2 NEW packages are going to be installed: spectest spectest-bzr

2 new packages to install. Overall download size: 5.5 KiB. After the operation, additional 44.0 B will be used. Continue? [y/n/? shows all options] (y): --------

It is interesting. But I think it is too tricky. Users may be confused.

And when building, rpmlint says "W: suse-filelist-empty packages without any files are discouraged in SUSE."

I prefer "Recommends: git".

If I am mistaken, please tell me it.

By default the first item in alphabetical list will be installed. You could use Suggests to switch the default to another subpackage. Also if name and name-hg is installed name-git will not be installed. No another rpm/zypper magic, sorry. -- Best regards, Dmitriy DA(P).DarkneSS Perlow @ Linux x64 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org