July 2022 - openSUSE Packaging - openSUSE Mailing Lists

Handling transition from python3-docker-compose v1 to docker-compose v2
by Johannes Kastl 01 Aug '22

01 Aug '22

TL;DR: Which package should get Obsoletes and Requires? Hi all, I have packaged the latest updates for the python-based python-docker-compose as well as the newer v2 that is written in golang. https://build.opensuse.org/request/show/986041 https://build.opensuse.org/request/show/986039 I also prepared the docker-compose-switch package that upstream created to ease the transition from v1 to v2, as the latter is only a cli-plugin for docker and does not longer have a docker-compose binary. https://github.com/docker/compose-switch > Compose Switch is a replacement to the Compose V1 docker-compose (python) executable. It translates the command line into Compose V2 docker compose then run the latter. The python package already used update-alternatives to manage packages built for different python versions being installed simultaneously. I am not sure if anybody is still relying on features from v1, I do not think so. So I would put a "Obsoletes: ... <2.0.0" into one of the new golang-based packages. This would hopefully lead to the deinstallation of the python-based v1 package. The question is, which package should get this "Obsoletes"? I think it should go into the docker-compose-switch one, which has a Requires for docker-compose v2. This way I can only install docker-compose v2 and use "docker compose ..." (space instead of hyphen!), i.e. if I do not need the compatibility docker-compose binary. If I rely on a binary called docker-compose, I can install the docker-compose-switch package. Or I would get it automatically together with the v2 golang package, if I have the python-based one installed. Would that work? Any flaws that I missed? Better ideas? Thanks for your input. Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

2 16

Enable Leap 15.4 build for server:http
by Fusion Future 01 Aug '22

01 Aug '22

Hi dear maintainers: openSUSE Leap 15.4 has been released, but server:http still doesn't have builds for 15.4. Could you enable it? Thanks in advance.

2 1

Will 'prepare' unzip nested .zip files?
by David C. Rankin 31 Jul '22

31 Jul '22

All, Looking to package Agner Fog's objconv: https://www.agner.org/optimize/objconv.zip However, the source contains nested zip files, e.g. $ unzip -l objconv.zip Archive: objconv.zip Length Date Time Name --------- ---------- ----- ---- 867840 2022-05-21 04:37 objconv.exe 334623 2022-04-28 03:29 objconv-instructions.pdf 369303 2022-05-21 04:37 source.zip 9588 2013-09-01 12:24 extras.zip 2710 2022-04-28 03:35 changelog.txt --------- ------- 1584064 5 files The only set of files needed are the source files in source.zip. Will this be handled by prepare, or in this case will we need to manually extract the sources.zip and unzip it before calling prepare? (odd way to distribute sources, but to each his own) Too bad the sources are not available independently. -- David C. Rankin, J.D.,P.E.

2 2

Messed up google-noto-{sans,serif}-cjk-fonts package on openSUSE:Factory
by Takashi Iwai 23 Jul '22

23 Jul '22

Hi, I noticed that the google-noto-serif-cjk-fonts package on openSUSE:Factory is a link from openSUSE:Factory/google-noto-sans-cjk-fonts, but it still contains the old contents instead of the linked target. That made Tumbleweed keeping the old packages (that had a higher package number "2017xxx" than the current "2.00x"). How can I fix this mess? When I do osc branch, it'll branch off from the develproject M17N:fonts/google-noto-sans-cjk-fonts from the target link, which is of course nonsense for cleaning up the openSUSE:Factory repo. Ideally speaking, I'd like to separate again those packages into individual repos instead of link, as they have no direct relations at all. But, when I tried to remove google-noto-serif-cjk-fonts.{spec,changes} from *-sans-* repo in the local branch, it resulted in a bad state, so I gave up. If anyone gives a hint how to go further, it'd be appreciated. thanks, Takashi

1 1

Call for testing: Ansible 6.x (ansible-core 2.13.1 with community collections) and ansible-lint 6.x
by Johannes Kastl 22 Jul '22

22 Jul '22

TL;DR: ansible > 2.9 needs testing, as does ansible-lint 6.x (Please reply to the factory list) > https://build.opensuse.org/project/show/systemsmanagement:ansible Hi all, in the last couple of weeks I spent some time on getting ansible > 2.9 packaged and running on openSUSE. As you may or may not be aware, 2.9 is EOL since ansible-core 2.13 got released. What, what? ansible-what? WTF? Basically the ansible package you will install is a package only containing community maintained collections, that were removed from what you know as ansible 2.9. The remaining parts are what is now called ansible-core. This means that collections can be maintained separately, and you do not need to wait for a release of ansible to get a fix in your collection. Having a recent ansible/ansible-core package allows the use of ansible-lint 6.x, which requires ansible-core > 2.12. The version numbers are very ...ahem... funny, so don't get confused. ansible-core keeps the 2.x versioning for now, but the ansible package (think of it as ansible-community) is currently at 6.1.x, Details can be found here: > https://docs.ansible.com/ansible/latest/reference_appendices/release_and_ma… The packages seem to be working for me, so I put them into systemsmanagement:ansible and would be glad for feedback. > https://build.opensuse.org/project/show/systemsmanagement:ansible Something like that should do the trick: sudo zypper ar -p 80 -f -r \ https://download.opensuse.org/repositories/systemsmanagement:/ansible/openS… sudo zypper ref sudo zypper dup --from systemsmanagement_ansible or sudo zypper in ansible ansible-lint Unless there are flaws, I would submit them to Factory in a couple of weeks, ask for a change of the devel project and move all other ansible-related things into this subproject. Having more maintainers would of course be very nice, so please don't be shy. python-jsonschema and python-hatch_vcs are already in dlp and on their way to Factory, so those will be dropped from the project once they are no longer needed. Unfortunately backporting this to Leap 15 / SLES15 is not (easily) possible, as it needs a rather new python to get this to build and work properly... :-( Any hints, comments, tipps, tricks or feedback are highly welcome. Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

1 0

Re: Handling transition from python3-docker-compose v1 to docker-compose v2
by Johannes Kastl 21 Jul '22

21 Jul '22

Hi Dirk, On 19.07.22 at 16:35 Dirk Müller wrote: > Am Freitag, 1. Juli 2022, 13:29:17 CEST schrieb Johannes Kastl: >> I also prepared the docker-compose-switch package that upstream created to >> ease > the transition from v1 to v2, as the latter is only a cli-plugin for >> docker and does not longer have a docker-compose binary. > > It does sounds like this one (compose-switch) should have the provides/ > obsoletes then. > >> So I would put a "Obsoletes: ... <2.0.0" into one of the new golang-based >> packages. This would hopefully lead to the deinstallation of the >> python-based v1 package. > > Yes, but only if it is getting installed. In order to make it automatically > installed, it needs to provide a higher version of the old package name (to > make it an update candidate of the existing installed package). The solution that seemed to work (and is reflected in the SRs) was: **docker-compose-switch** Requires: docker Requires: docker-compose >= 2.0 Requires(post): update-alternatives Requires(postun):update-alternatives # Docker Compose V2 is a major version bump release of Docker Compose. # It has been completely rewritten from scratch in Golang (V1 was in Python). Obsoletes: python2-docker-compose < 2.0.0 Obsoletes: python3-docker-compose < 2.0.0 Obsoletes: python36-docker-compose < 2.0.0 Obsoletes: python37-docker-compose < 2.0.0 Obsoletes: python38-docker-compose < 2.0.0 Obsoletes: python39-docker-compose < 2.0.0 Obsoletes: python310-docker-compose < 2.0.0 **docker-compose** Requires: docker This makes sure that both docker-compose-switch and docker-compose 2.x are being installed when replacing the python-based v1.x version. But the user can still only install docker-compose without the compatibility package. -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

1 0

Easy way to fix python deprecation warnings for distutils and "setup.py install"?
by Johannes Kastl 20 Jul '22

20 Jul '22

Hi all, is there a proper/recommended way to build python packages and not run into the deprecation warning for using distutils or setup.py install? e.g. https://build.opensuse.org/build/systemsmanagement/openSUSE_Tumbleweed/x86_…: > [ 88s] /home/abuild/rpmbuild/BUILD/ansible-2.9.27/setup.py:12: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives > [ 88s] from distutils.command.build_scripts import build_scripts as BuildScripts > [ 402s] /usr/lib/python3.10/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools. > [ 402s] warnings.warn( Does not seem to be a pressing issue, but if there is an easy way to fix this (in the package, not upstream) then I could do this while touching the python packages I need to touch currently... Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

2 1

Disable building of "test" subpackages / multibuild packages
by Johannes Kastl 18 Jul '22

18 Jul '22

Hi all, is there a way to disable building of test subpackages (or multibuild packages or whatever the proper term is) on a per-project base? Like e.g. python-setuptools which has a test "multibuild": > https://build.opensuse.org/package/show/devel:languages:python/python-setup… I think I could modify each and every _multibuild file or remove the test spec files from the packages, but I would rather like to avoid that and just set some flag on the project itself. In my case I am just linking together several packages that are being tested somewhere else and would like to avoid having to link in all the test dependencies and their dependencies and dependency hell etc. Thanks in advance! Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

4 7

Seeking clarification on how submit official packages
by Mark E. Fuller 17 Jul '22

17 Jul '22

Hi all, I am currently an active packager with Fedora Linux and I would like to familiarize myself and work on submitting and maintaining packages officially in openSUSE as well. I've been struggling a bit reading through the documentation to get started with doing more than simply using OBS for my own unofficial packages, e.g. https://build.opensuse.org/package/show/home:fuller/cantera Is there anyone who could help me get started with the process and transitioning a first package to review for inclusion in the official repositories? (Falls hilfreich, ich kann auch Deutsch) Thanks, fuller -- Mark E. Fuller, Ph.D. fuller(a)fedoraproject.org mark.e.fuller(a)gmail.com @fuller:fedora.im @fuller:one.ems.host https://www.stossrohr.net PGP Fingerprint: 73F1 A30C BDF4 DB4B C75F FD0F D599 E76C FFCA BF60

3 3

How to get a new package into openSUSE:Backports:SLE-12-SP5?
by Johannes Kastl 14 Jul '22

14 Jul '22

Hi all, what is the correct way to get an additional package into openSUSE:Backports:SLE-12-SP5? One of our customers needed apache2-mod_auth_gssapi for SLES12 SP5, so I tried to build that against the Backports, and it worked. > https://build.opensuse.org/project/show/home:ojkastl_buildservice:Backports… As this might be of use to others, I wanted to add it to the Backports aka Packagehub. Is there any easy way to submit it to the Backports aka PackageHub? Or is the fun described in the wiki still the way to go? > https://en.opensuse.org/openSUSE:Backports_Package_Submission_Process#Intro… Thanks in advance? Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

2 2