openSUSE Packaging September 2017

packaging@lists.opensuse.org

28 participants
18 discussions

[opensuse-packaging] Updated rationales for specfile guidelines

by Jan Engelhardt

Parts of the specfile guidelines have been just amended by me. It might just be considered a redactional (linguistic) edit, but it feels too much on either side of the fence, so here is an explicit notification to those who care. 1. The section about $RPM_BUILD_ROOT was expanded/edited to list the shell vars (few and far) and reminding the reader that using them leads to disagreement with a sentence that was previously there: that mixing the styles should be avoided. https://en.opensuse.org/index.php?title=openSUSE:Specfile_guidelines&diff=p… 2. Rationale for rpm's offering of %__blah was updated, which leads to more emphasis avoiding %__ in openSUSE altogether: https://en.opensuse.org/index.php?title=openSUSE%3ASpecfile_guidelines&type… -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 years

[opensuse-packaging] Random "Job seems to be stuck here" build failures

by Michal Srb

Hi, I am working with llvm4 package, which is usually building very long time: https://build.opensuse.org/package/show/devel:tools:compiler/llvm4 https://build.opensuse.org/package/show/ home:michalsrb:branches:devel:tools:compiler/llvm4 I am seeing random but frequent build failures where the build log simply ends (sometimes even in the middle of a line) and after long wait the build is terminated. For example: > ... > [14840s] -- Installing: /home/abuild/rpmbuild/BUILDROOT/ llvm4-4.0.1-38.5.i386/usr/include/llvm/Transforms/Utils/CtorUtils.h > [14840s] -- Installing: /home/abuild/rpmbuild/BUILDROOT/ llvm4-4.0.1-38.5.i386/usr/include/llvm/Transforms/Utils/EscapeEnumerator.h > [14840s] -- Installing: /home/abuild/rpmbuild/BUILDROOT/ llvm4-4.0.1-38.5.i386/usr/include/llvm/Transf > > Job seems to be stuck here, killed. (after 28800 seconds of inactivity) It never happened in local build. In build service it happens randomly and in different parts of the build. For example in the middle of "make install" in %install section, or in the middle of running tests in %check section, or in the middle of debuginfo extraction. That makes me think that the problem is not in the package, but something is wrong in build service. Could there be something broken in the package? If it is problem in buildservice, can I do something to reduce the chance of it happening? Thanks, Michal Srb -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 years

[opensuse-packaging] Waiting for server side source service run

by Axel Braun

Morning all, I wanted to check in a file using osc, but the 'server-side service run' seems to run forever...on my machine just a second. Anything wrong with OBS? Cheers Axel -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 years

[opensuse-packaging] shadow - autoconf wizards needed

by Michael Vetter

Hi, I am looking for some autoconf and maybe docbook wizards. The shadow package ships with pre built man pages. However the content of the manpages depends on compile options, which is why I want to built them myself. However once I remove all the existing man pages, and build with `--enable-man` it stops like this: ``` [ 53s] Making all in cs [ 53s] make[3]: Entering directory '/home/abuild/rpmbuild/BUILD/shadow-4.5/man/cs' [ 53s] make[3]: *** No rule to make target 'man1/expiry.1', needed by 'all-am'. Stop. ``` For complete log and package see: https://build.opensuse.org/package/live_build_log/home:jubalh:branches:Base… I looked at all the involved Makefiles but didn't find the reason for this. https://github.com/shadow-maint/shadow/blob/master/man/Makefile.am https://github.com/shadow-maint/shadow/blob/master/man/generate_mans.mak Probably https://github.com/shadow-maint/shadow/blob/master/man/generate_translation… is more interesting since it only seems to happen for translated ones. On this note, I saw that https://github.com/shadow-maint/shadow/tree/master/man/po actually only has few translations present. But looking at generate_translations.mak I still think it shouldn't matter. Not sure I understand it well enough though. Maybe some autoconf guru can help? cheers, Michael -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 years

[opensuse-packaging] How does obs rpmlint detect illegal binary in noarch packages

by Dave Plater

Hi, I just split off 3d symbols from kicad-library into a sub package. After this rpmlint picks up "arch-independent-package-contains-binary-or-object" Nothing changed in the package just the directory containing the 3d symbols moved to the sub package. I moved it because it is very large and optional. I've created an rpmlintrc but I wonder why rpmlint never picked up what it thought was an executable binary before. The files start with #! but scripts aren't arch dependent. I can vaguely remember having a problem similar to this years ago with data files in rosegarden which had shebangs but AFAIR I filed a bug and it was fixed. Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 years

[opensuse-packaging] How strong a language does the wiki need

by Jan Engelhardt

Think back to when Greg KH had to switch his Linux kernel release announcements from "users should upgrade" to "all users must upgrade". It would appear that the number of people that read and take texts the literal RFC way is on the rise, and that the same s/SHOULD/MUST/g; operation might be necessary for the openSUSE wiki concerning package submissions. The texts would then be less ambiguous when it comes to disputed positions, though also change to a stricter atmosphere, which might be an impediment for new-time users. Like public places getting their "please clean up after your pet" signs replaced by "$100 fine, you idiot". That hardly sounds like a solution. Seeking comments for $wiki.. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 years

[opensuse-packaging] RPM groups: Dev/Libraries or Dev/Languages or both

by Jan Engelhardt

Currently, more than one category is in circulation for a particular language environment provided by the distribution, specifically I noticed this with factory# grep Development/Languages/Python *spec | wc -l 1215 factory# grep Development/Libraries/Python *spec | wc -l 399 (It also happens for some others like Perl, Haskell, ...) There was a little discussion off the side previously, psimons made a comment, if I understood it right, is that one could be used for tooling and the other for modules. https://github.com/openSUSE/spec-cleaner/pull/198#issuecomment-320931621 His comment seems valid to me in principle, as we do make the difference for C and C++, where the tooling usually lands in Development/Tools/* and modules in Development/Libraries/C and C++. However, the difference between "Languages/Py" and "Libraries/Py" seems too small that it could make a difference - or stating the problem differently: "would the user know the difference between the two?" Should we preferably just use a single RPM group? Reaching out to see what people think.. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 years

Re: [opensuse-packaging] New packaging guidelines for PHP7 pacakges

by Johannes Weberhofer

Am 01.09.2017 um 01:21 schrieb Andrew Daugherity: >> Leap seems to be 1330 at the moment; I'll update this. > > Not in 42.x. Looks like Tumbleweed is currently 1330 (according to https://en.opensuse.org/openSUSE:Packaging_for_Leap#RPM_Distro_Version_Macr…, but footnoted as "never rely on this version, it may change"). > I meant Tumbleweed but wrote Leap... -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 years

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging September 2017