March 2017 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] python singlespec for only existing in d:l:p3
by Bruno Friedmann 13 Mar '17

13 Mar '17

Hi there, today I receive the first changes for an only existing in python3 (d:l:p3) package to be converted to singlespec. Now I wonder if we should start the conversion into d:l:p3 like in the sr. Once build in d:l:p3 we submit it to python-singlespec repo and then back to d:l:p ? Or what is the best workflow we can choose, to first not loose the work done in d:l:p3 and get them all to factory in the end. Thanks for your ideas. Example https://build.opensuse.org/request/show/478944 -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 5

[opensuse-packaging] Re: [sle-desktop] Autotools version mismatch in GNOME on SLE12-SP2 and Leap 42.2
by Felix Zhang 13 Mar '17

13 Mar '17

Hi Yifan, Thanks very much for this advice. On a second thought, this issue potentially affects an amount of packages on Leap 42.2. So cross-posting to opensuse-packaging(a)opensuse.org. Thanks, Felix On 2017/3/7 11:36, Yifan Jiang wrote: > Hi Felix, > > I guess "research" is also a good place to append the question, making it > visible to OBS and toolchain guys :-) > > - Yifan > > > On Mon, Mar 06, 2017 at 09:20:10PM +0800, Felix Zhang wrote: >> Hi all, >> >> I noticed that the autotools files in our GNOME packages are generated >> by autotools 1.15. As I didn't find these files included in the upstream >> repos. I guess they come from openSUSE:Factory at the time we >> constructed SLE12-SP2 and Leap 42.2. >> >> However, on SP2 and 42.2 we kept autotools 1.13 from updating to 1.15. >> >> This mismatch hit me when I was trying to backport CVE patches for >> gtk-vnc (bsc#1024266, bsc#1024268) which have modifications on a >> Makefile.am thus automake is required to regenerate Makefile.in - a >> build time error complained that automake-1.15 is not found: >> >> https://build.suse.de/package/live_build_log/home:zhangxiaofei:branches:Dev… >> >> I understand there must be good reasons not updating autotools. So my >> question is, what's a good way to get around such failures please? >> >> Thanks very much in advance for your tips. :-) >> >> >> Best regards, >> >> Felix >> >> > > > >

5 7

[opensuse-packaging] python singlespec: wiki page
by jan matejek 13 Mar '17

13 Mar '17

Hello all, I have created a page on the openSUSE wiki, listing the conversion steps and explaining some things. I will try to keep it up to date with new developments. This also supersedes the "how to convert your package" e-mail. https://en.opensuse.org/openSUSE:Packaging_Python_Singlespec Also, at some point the content should be merged into Packaging:Python, but this turned out to be a bigger task :) So for now I'll place a link to it and leave it at that. Please let me know if you think that something should be added, removed, changed, etc. Also it would be nice if someone could look at the CSS for the wiki, and ensure that <code> and <pre> tags are more readable -- for me, the monospace font is about half the size of the regular font. regards m.

4 9

[opensuse-packaging] Announcing golang-packaging version 15.0.0
by Thomas Hipp 13 Mar '17

13 Mar '17

Hi, I'd like to announce the new version of golang-packaging[0]. This is a complete rewrite using only Bash instead of Ruby. Except for the rewrite, there are no major changes, so packaging works (almost) just like before. The changes include: * static libraries (*.a files) are not shipped; only source files * macro %{go_filelist} -> %{gofilelist}, to be consistent * removed previously deprecated macros The wiki[1] page has been updated to reflect the recent changes. There you can also find an updated spec file template. Also, all packages in devel:languages:go[2] have been updated, and are now using the new golang-packaging version. Happy packaging! Best wishes Thomas [0] https://github.com/openSUSE/golang-packaging/ [1] https://en.opensuse.org/openSUSE:Packaging_Go [2] https://build.opensuse.org/project/show/devel:languages:go -- Thomas Hipp Docker Developer SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) PGP fingerprint: 48D6 A5F4 2D60 57BF 9A37 8004 5DE8 949A 899C 8D99

1 0

[opensuse-packaging] status report jmatejek 2017-03-03 (week 09)
by jan matejek 11 Mar '17

11 Mar '17

[green] - singlespec * looking into SLE11 situation * converting packages * talking to people * fixing problems * developing a macro to automate creation of update-alternatives - updating pythons for SLE12 (2.7.13, 3.4.6, bsc#1027282) - bsc#1026174 - Python 3.6 broke pylint which sits rather low on the dep tree, so looking into that, converting packages to singlespec while doing it, and preparing astroid/pylint packages from unreleased github checkouts [workload] 9 [outlook] - cleaning up singlespec repo - mass autoconversion - finishing the update-alternatives macro - maybe work on python-rpm-macros-compat for SLE11 - !! writing conversion guidelines, with usual mistakes !! * mistake #1: using %python_module in Requires [good] This is, very surprisingly, very painless. [bad] setuptools_scm

2 1

[opensuse-packaging] Unsubscribe
by Marko Denda 11 Mar '17

11 Mar '17

-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] Can't build packages locally - what's going on?
by Greg Freemyer 08 Mar '17

08 Mar '17

I'm confused. I've tried to build 3 packages and none are working. The complaint I notice is about permissions for /dev/null. Three examples of what is failing right now: osc co /home:gregfreemyer:Tools-for-forensic-boot-cd calc cd /home:gregfreemyer:Tools-for-forensic-boot-cd/calc osc build osc co security:forensics dc3dd cd security:forensics/dc3dd osc build osc co openSUSE:Leap:42.1:Update libewf cd openSUSE:Leap:42.1:Update/libewf osc build --local Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 3

[opensuse-packaging] Kernel tools packaging for Factory
by Andreas Färber 07 Mar '17

07 Mar '17

Hello, For v4.7, the kvm_stat utility was removed from QEMU and added to the kernel. We therefore had to adapt qemu packaging, and Bruce added a Virtualization/kvm_stat package built from kernel-source. https://build.opensuse.org/package/show/Virtualization/kvm_stat As part of the Factory submission review, although it was accepted, it was suggested that we add it as sub-package to devel:tools/linux-tools instead. I have done that now. https://build.opensuse.org/package/show/devel:tools/linux-tools However, linux-tools is not in Factory. Therefore we can't drop our kvm_stat package yet, which was the intended purpose of the submission. Are there any plans to submit linux-tools to Factory, or what is holding it up? Should this rather be integrated with kernel-source somehow, like dtb-source recently, so that it rebuilds with kernel updates and can take build breakages like for v4.10 into account? Thanks, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 3

[opensuse-packaging] New packages: libtwaindsm2 and libopenusb
by Erico Mendonca 06 Mar '17

06 Mar '17

Hello all, I ported two new packages to OBS: https://build.opensuse.org/package/show/home:emendonca/libtwaindsm2 https://build.opensuse.org/package/show/home:emendonca/libopenusb - libtwaindsm2: this is the official TWAIN Group stack for Linux. It's used for implementing the TWAIN protocol for scanner/camera applications. The code resides on SourceForge. - libopenusb: it's a MT-safe version of libusb. Also resides on SourceForge. I wrote the SPECs from scratch. I made a few patches to fix GCC 4.8+ compiler errors. The reason I ported these was because they are necessary for some proprietary scanner drivers for Linux, which I had to repackage for a customer. I submitted these to the "hardware" repository a couple of weeks ago, but the requests never got reviewed. Could someone take a look if everything's alright? -- Erico -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 4

[opensuse-packaging] New packages: libtwaindsm2 and libopenusb
by Erico Mendonca 06 Mar '17

06 Mar '17

Hello all, I ported two new packages to OBS: https://build.opensuse.org/package/show/home:emendonca/libtwaindsm2 https://build.opensuse.org/package/show/home:emendonca/libopenusb - libtwaindsm2: this is the official TWAIN Group stack for Linux. It's used for implementing the TWAIN protocol for scanner/camera applications. The code resides on SourceForge. - libopenusb: it's a MT-safe version of libusb. Also resides on SourceForge. I wrote the SPECs from scratch. I made a few patches to fix GCC 4.8+ compiler errors. The reason I ported these was because they are necessary for some proprietary scanner drivers for Linux, which I had to repackage for a customer. I submitted these to the "hardware" repository a couple of weeks ago, but the requests never got reviewed. Could someone take a look if everything's alright? Erico Mendonça Dedicated Support Engineer SUSE Rua Joaquim Floriano, 466 12° andar Itaim Bibi Tel: +55 11 3627-0970 Cel: +55 61 8594-9557 erico.mendonca(a)suse.com

3 2