September 2012 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Re: [opensuse-factory] Moving forward with systemd
by Cristian Rodríguez 20 Sep '12

20 Sep '12

El 20/09/12 10:02, Frederic Crozat escribió: > build kernel with autofs4 built-in (systemd will modprobe it anyway, but > we could save some boot time by not having to do so). Ok, we need to bug kernel developers with this.. ;) >> Related to this : daemons must run with PrivateTemp set to true and see >> a way to provide exclusive temporary directories to users in a sensible >> manner such as pam_mktemp (?) or similar. > > Must is a bit hard for PrivateTmp, I'd suggest "should". Yeah, we probably need an script that checks the binary AND the linked libraries for usage of mkstemp(3) mkdtemp(3), mktemp(3), tempnam(3), tmpfile(3), tmpnam(3) functions and tell us if we really need that. -- 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] Question about release numbers in branched packages
by Andrey Borzenkov 19 Sep '12

19 Sep '12

I am new to openSUSE packaging workflow so please bear with me. When I branch some package, it gets release number based on revision of parent package; later release number is incremented with each commit/rebuild, so if I install branched package it will come newer than parent. Is it correct? Now after I submit changes to parent package and it is accepted - will release number of parent package automatically compare newer than my local branch once it is available from official repository? On other systems I had to locally extend release number to make sure it will update "upstream" package it is based on, but will be overwritten if upstream gets updated. How does it work in openSUSE? Related question is for package version bump. If I update package branch to new version and submit it - is it ensure that package from official repository will come newer than my local build? Thank you! -andrey -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] Building a package with older version
by openSUSE user 19 Sep '12

19 Sep '12

Hi, all. Tell me, please, how can I build locally a package with an older version of build dependent package (older than in the repository) with "osc"? Interest options: a) The old version of a depended package is available in some repository, b) The old version of a depended package is available only locally, on HDD. Best regards. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 3

[opensuse-packaging]
by Nelson Marques 18 Sep '12

18 Sep '12

Hi, I'm trying to integrate MATE with openSUSE, and I believe most of the stuff is actually done; I'm just struggling with mate-screensaver (keyring and PAM ?) which fails big time... I've taken a look at the GNOME 2 packages and made actually some advancemente, but I'm still getting no results... /var/log/messages spits out the following : Sep 18 19:55:37 mantis mate-screensaver-dialog: gkr-pam: unlocked login keyring Sep 18 19:55:37 mantis mate-screensaver-dialog: pam_unix2(mate-screensaver:auth): conversation failed Sep 18 19:55:39 mantis mate-screensaver-dialog: gkr-pam: unlocked login keyring Sep 18 19:55:39 mantis mate-screensaver-dialog: pam_unix2(mate-screensaver:auth): conversation failed The packages are on X11:MATE. by any means, can someone help me? I don't really understand much of PAM and there's something here I can't beat all by myself :/ NM -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 2

[opensuse-packaging] ncurses maintainers please help fix "presage" package.
by Marguerite Su 18 Sep '12

18 Sep '12

Hi, packagers, I'm preparing for fcitx 4.2.6 updates in home:csslayer:fcitx repository. And I found something unbelievable about ncurses-devel: https://build.opensuse.org/package/show?package=presage&project=home%3Acssl… In this "presage" package, I can't build "presage-demo" package for openSUSE: [ 62s] [137/306] preinstalled libncurses5-5.9-12.5.1 [ 62s] [138/306] installing libncurses6-5.9-12.5.1 [ 78s] [267/306] installing ncurses-devel-5.9-12.5.1 [ 111s] checking for initscr in -lcurses... no [ 111s] configure: WARNING: curses library not found. curses demo programs will not be built. [ 111s] checking curses.h usability... yes [ 111s] checking curses.h presence... yes [ 111s] checking for curses.h... yes But the same BuildRequires works in Fedora. The related presage code in src/tools/presageDemo.cpp 129:3 is: // curses initscr(); noecho(); cbreak(); keypad(stdscr, TRUE); clear(); refresh(); disclaimer(); So where's "initscr" function goes in our ncurses? Thanks in advance Marguerite -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 16

[opensuse-packaging] local package does not override global package
by Olaf Hering 18 Sep '12

18 Sep '12

In devel:languages:ocaml I changed the BuildRequires in the ocaml-findlib package from 'ocaml-camlp4-devel' to 'camlp4' to make it compatible with the binary names within sles11*. The new ocaml-camlp4-devel package provides and obsoletes camlp4. Now the buildservice has trouble to understand that ocaml-camlp4-devel from the same project provides camlp4.rpm, instead it wants to use the older standalone camlp4.rpm as shipped with 11.4 and 12.1. obs/devel:languages:ocaml/ocaml-findlib $ obs r -v openSUSE_11.4 i586 unresolvable: nothing provides ocaml = 3.12.0-2.1 needed by camlp4 openSUSE_11.4 x86_64 unresolvable: nothing provides ocaml = 3.12.0-2.1 needed by camlp4 openSUSE_12.1 i586 unresolvable: nothing provides ocaml = 3.12.0-11.1.2 needed by camlp4 nothing provides ocaml(Arg) = 877340141c0babb58b3aaef2f5b70fc9 needed by camlp4 openSUSE_12.1 x86_64 unresolvable: nothing provides ocaml = 3.12.0-11.1.2 needed by camlp4 nothing provides ocaml(Arg) = 877340141c0babb58b3aaef2f5b70fc9 needed by camlp4 I can certainly add a conditional BuildRequires, but: How can this be fixed properly? Olaf -- 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] No upstream changelog available
by Nelson Marques 18 Sep '12

18 Sep '12

One of the crap things about Cinnamon is that there's no changelog available from upstream; The Debian packages from upstream have no changelog also beyond the 'update to version x.y.z'... what should I write in the changelog ? NM --- Artigo 21 - Direito à Resistência Todos têm o direito de resistir a qualquer ordem que ofensa os seus direitos, liberdades e garantias e de repelir pela força qualquer agressão, quando não seja possível recorrer à autoridade pública. Constituição da Républica Portuguesa -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 7

[opensuse-packaging] Marketing Jur�dico | Newsletter Inrise Consultoria | Edi��o 27 | Ano 05
by Inrise RH 18 Sep '12

18 Sep '12

1 0

[opensuse-packaging] package versioning
by Nelson Marques 18 Sep '12

18 Sep '12

Dear all, I have a simple question; Let's imagine we have a package 'foobar'; which the latest stable release is 1.0. Someone decides to to update to git snapshot and uses a version based on the date, for example: 20121017, where the NEVRA goes into something like: Name: foobar Epoch: 0 Version: 20121017 Release: 0 Arch: noarch Now after two years of git snapshotting we get an official release, lets say, 1.1; Would it normal to suppose that version wise: 20121017 > 1.1 Eventually my guess was that we should enforce Epoch to get back into track and make sure 1.1 would replace the former packages; If I understood correctly it is not wise to use Epoch within openSUSE and it should be banned... So... How do we get this update going ? This is just an hipotetical case, though I can remember of few examples currently in production, which don't for this case; I'm mainly interesting in knowing how to deal with this in openSUSE. Thanks. NM -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 5

[opensuse-packaging] required perl modules not included in package Requires
by Olaf Hering 17 Sep '12

17 Sep '12

Is there a reason why the required modules of a perl script are not encoded in the Requires of a package? In the example below I would expect a Requires: perl(Data::Dumper) to be included in inst-source-utils to pull in all required packages to actually run the script. Olaf root@carron:~/X # sed -n '/^[[:blank:]]*use[[:blank:]].*::/p' /usr/bin/createpatch use Data::Dumper; use File::stat; use File::Temp qw/ tempdir /; use Time::localtime; use Getopt::Long; root@carron:~/X # rpm -qf /usr/bin/createpatch inst-source-utils-2012.2.3-0.5.1 root@carron:~/X # rpm -qf --requires /usr/bin/createpatch gpg2 recode rpmlib(VersionedDependencies) <= 3.0.3-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 /bin/bash /bin/sh /usr/bin/perl rpmlib(PayloadIsLzma) <= 4.4.6-1 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

7 8