July 2017 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Advise for cleanup the situation with postgresql-plr
by Bruno Friedmann 25 Jul '17

25 Jul '17

Hi All, first if there's one person to blame it's me :-) In this repository https://build.opensuse.org/package/show/server:database:postgresql I maintain postgresql-plr package which was building with pre_checking.sh script for all version of postgresql from 91 to 96. As Factory as only 93 to 96 I wasn't able to submit directly the package and then create a messy situation. Later I discovered that for Leap 42.2 pg95 and pg96 becames available in oss- update repository see my questions below. Now as we don't have any target for postgresql < 93 I've clean up the postgresql-plr package to only generate .spec file for valid postgresql version. I also just finished to backport all changes needed to make it pure high class package for factory. So now I would like to resubmit the whole postgresql-plr to factory cleaning any kind of strange devel link (for example s:d:p/postgresql96-plr is a link to openSUSE:Factory/postgresql96-plr) For me, actually my brain would understand it if: s:d:p/postgresqlXX-plr is a link to s:d:p/postgresql-plr and in factory and postgresqlXX-plr will become a link to factory postgresql- plr and s:d:p/postgresql-plr is the devel package for Factory. Perhaps in this part, I'm not 100% clear the way obs/factory work ? So now the subtil path. In 42.1, 42.2, 42.3 I have a postgresql93,94-plr package (in oss, or oss- update) In Factory I also have a postgresql93,94,95,96-plr I would like to change the devel package (would an appropriate submit request do the job ?), and then the XX version will become back a link to the main package. Will this take a new «eternal legal check» (no offense) ? Leap update : My bad, that I didn't realize before that 95, and 96 will be on update or oss for 42.3 and 42.2. So what's my best option (I know that I have to start a Maintenance Request) but how to do that on non existing package ? Thanks for the brave soul that would like to help me to cleanup the mess ;-) -- 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

1 0

[opensuse-packaging] Python singlespec and %lang macros
by Luigi Baldoni 24 Jul '17

24 Jul '17

Hi, I've tried using them but I've encountered immediate duplicate package errors. Am I doing something wrong or more likely the python macros don't support this setup just yet? Regards -- View this message in context: http://opensuse.14.x6.nabble.com/Python-singlespec-and-lang-macros-tp509102… Sent from the opensuse-packaging mailing list archive at Nabble.com. -- 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] how to not skip a version when upgrading
by Jordi Massaguer Pla 17 Jul '17

17 Jul '17

Hi, so I have this question: If I have package foo with different version, as foo-1.0, foo-2.0 and foo-3.0, my understanding is that, if I have foo-1.0 installed and run "*zypper dup*", I will get foo-3.0 installed, skipping foo-2.0. Is this correct? Is there a way to force the installation of foo-2.0 and afterwards foo-3.0? I can only think of having foo-3.0 on a different repo and adding this repo after installing foo-2.0, but sounds a bit hacky. The problem I am trying to address is the case that I have multiple machines with foo-1.0 and need to go to foo-2.0 and then to foo-3.0 because the API or file format may be only compatible between foo-1.0 and foo-2.0, foo-2.0 and foo-3.0, but not between foo-1.0 and foo-3.0. This sounds like it should be a "typical" problem on a rolling release as Tumbleweed ... right? Any ideas/experience? thanks in advance jordi

4 4

[opensuse-packaging] Fwd: openSUSE-OU-2017:1858-1: Initial release of python-rpm-macros
by Greg Freemyer 14 Jul '17

14 Jul '17

The below is about a new package being released for 42.2. I have a several security related bugs in won't fix state because I can only fix them via adding a new package to 42.2 and 42.3 will be the same. How do I do it? ---------- Forwarded message ---------- From: <maintenance(a)opensuse.org> Date: Fri, Jul 14, 2017 at 6:09 AM Subject: openSUSE-OU-2017:1858-1: Initial release of python-rpm-macros To: opensuse-updates(a)opensuse.org openSUSE Optional Update: Initial release of python-rpm-macros ______________________________________________________________________________ Announcement ID: openSUSE-OU-2017:1858-1 Rating: low References: #1039368 Affected Products: openSUSE Leap 42.2 ______________________________________________________________________________ An update that has one optional fix can now be installed. Description: This update adds python-rpm-macros to the distribution. This package contains RPM macros that ease packaging and building of Python singlespec packages. This update was imported from the SUSE:SLE-12:Update update project. Patch Instructions: To install this openSUSE Optional Update use YaST online_update. Alternatively you can run the command listed for your product: - openSUSE Leap 42.2: zypper in -t patch openSUSE-2017-812=1 To bring your system up-to-date, use "zypper patch". Package List: - openSUSE Leap 42.2 (noarch): python-rpm-macros-2017.05.09.fc237de-2.1 References: https://bugzilla.suse.com/1039368 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 2

Re: [opensuse-packaging] building -32bit library rpms...
by Marcus Meissner 13 Jul '17

13 Jul '17

Hi, it needs a i586 build target.... But it looks good currently. Ciao, Marcus On Tue, Jul 11, 2017 at 08:55:15PM -0400, Darin Perusich wrote: > See > https://build.opensuse.org/package/show/security/pam-google-authenticator > for an example. > > -- > Later, > Darin > > On Tue, Jul 11, 2017 at 5:07 PM, Marcus Meissner <meissner(a)suse.de> wrote: > > > On Tue, Jul 11, 2017 at 07:04:30PM +0200, Mathias Homann wrote: > > > hi, > > > > > > > > > is there a way to build -32bit packages for libraries without having a > > i586 > > > build target? > > > > Not really... what do you have? > > > > osc build on x86_64 would switch to the 32bit personality if needed. > > > > Ciao, Marcus > > -- > > To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org > > To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org > > > > -- Marcus Meissner,SUSE LINUX GmbH; Maxfeldstrasse 5; D-90409 Nuernberg; Zi. 3.1-33,+49-911-740 53-432,,serv=loki,mail=wotan,type=real <meissner(a)suse.de> -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 2

[opensuse-packaging] Packaging Font for Latex
by Sascha Manns 12 Jul '17

12 Jul '17

Hello List, i have build some Latex-Fonts from a TTF. Now i would like to package that stuff. Has anyone seen a Specfile for packaging fonts? Greetings Sascha -- Sascha Manns openSUSE member -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 6

[opensuse-packaging] building -32bit library rpms...
by Mathias Homann 12 Jul '17

12 Jul '17

hi, is there a way to build -32bit packages for libraries without having a i586 build target? Cheers MH -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 3

Re: [opensuse-packaging] building -32bit library rpms...
by Mathias Homann 12 Jul '17

12 Jul '17

Am Mittwoch, 12. Juli 2017, 02:55:15 CEST schrieb Darin Perusich: > See > https://build.opensuse.org/package/show/security/pam-google-authenticator > for an example. hmmm that one looks exactly how I wouldn't want to solve it... I don't want to have to have a i586 target for Leap 42.2. Is there anoother way, other than actually enabling building for i586? Cheers Mathias > > -- > Later, > Darin > > On Tue, Jul 11, 2017 at 5:07 PM, Marcus Meissner <meissner(a)suse.de> wrote: > > On Tue, Jul 11, 2017 at 07:04:30PM +0200, Mathias Homann wrote: > > > hi, > > > > > > > > > is there a way to build -32bit packages for libraries without having a > > > > i586 > > > > > build target? > > > > Not really... what do you have? > > > > osc build on x86_64 would switch to the 32bit personality if needed. > > > > Ciao, Marcus > > -- > > To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org > > To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org -- gpg key fingerprint: 5F64 4C92 9B77 DE37 D184 C5F9 B013 44E7 27BD 763C

1 0

[opensuse-packaging] Missing Ruby dependency
by Axel Braun 11 Jul '17

11 Jul '17

Hi, I ran into problems with one nodejs package using nodejs-packaging. https://build.opensuse.org/package/show/Application:ERP:Tryton:4.2/tryton-s… It cant resolve the requirement rubygem(ruby:2.1.0:mini_portile2:2.2) >= 2.2 needed by ruby2.1-rubygem- nokogiri I find a rubygem-mini_portile e.g. in Factory but this is Version 0.6.2.... Any idea where to look for? Thanks Axel -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 2

[opensuse-packaging] Issue with SONAME
by Pierre de Villemereuil 10 Jul '17

10 Jul '17

Dear all, I am not super skilled with compilation/packaging, but I'm trying to update a package to a newer version for the science repo: https://build.opensuse.org/package/show/home:flyos:branches:science/libhts This library is needed for the SAMtools/BCFtools software for bioinformatics. Details aside, OBS is not happy with this new version because the make install is creating a libhts.so.2: ln -sf libhts.so.1.5 /home/abuild/rpmbuild/BUILDROOT/libhts1-1.5-14.1.x86_64/usr/lib64/libhts.so.2 I don't get why the MAKEFILE is doing this... The problem is that this creates an error at the end because the package is named libhts1 (the version is 1.5...): [ 58s] libhts1.x86_64: E: shlib-policy-name-error (Badness: 10000) libhts2 [ 58s] Your package contains a single shared library but is not named after its [ 58s] SONAME. Any idea on how to correct this? I tried to create a sub-package libhts2 but ended more with even more of a mess... Any help would be very welcome! Cheers, Pierre -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 14