April 2013 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] erlang packaging II
by Matwey V. Kornilov 23 Apr '13

23 Apr '13

Hi All, I've just accepted one request and declined the other. And I would like to discuss following thing: why do you name -src packages as -devel? Is there strong underlying reason to do that? I am not insist on -src at all, but It may lead to misconception, because you do not need src/*.erl files to develop application that uses function from this module. Also, maybe there you will find answers to some questions and further links: https://en.opensuse.org/User:Matwey/Erlang_guidelines_draft#Further_informa… -- With best regards, Matwey V. Kornilov http://0x2207.blogspot.com xmpp:0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 6

[opensuse-packaging] erlang autoreqprovs
by Matwey V. Kornilov 22 Apr '13

22 Apr '13

Hi, This mail is to highlight current status of my find-requires-provides-for-erlang story. I've experimented at home:matwey:erlang and I've used new rpm fileattrs interface to run modified Lemekov's scripts. The first issue is that I had to broke erlang-wx (see http://lists.opensuse.org/opensuse-packaging/2013-03/msg00079.html ) The second is more sophisticated. As you know, you can compile in a link to any module and any function (ever not existing at all). Until the code want to call this function, you never know that. This opportunity is used quite often. Let us take a look at erlang-rfc4672. It has interfaces to different http servers: cowboy, mochiweb, inets. The scripts are able to extract all symbols after package built, but... We don't have at all packages for cowboy and mochi, no package provides the modules required by erlang-rfc4672. So, some packages built with auto-requires are not installable. (and formally they are inconsistent, they may potentially have bugs) And I don't know how to gracefully track this. In C, you need library to be installed at compile-time in order to link your exe with it. In Erlang, you do not. Maybe we need some lint-checker to reject package if we found that it requires module not installed at our build-host. More interesting that even from this code: Mod = list_to_atom("demo"), %% Fool xref tests case file:set_cwd(Demo) of ok -> apply(Mod, start, []), I was able to extract erlang:mod(demo) with R15/16. :) -- With best regards, Matwey V. Kornilov http://0x2207.blogspot.com xmpp:0x2207@jabber.ru -- 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] Multiple spec files checked now
by Stephan Kulow 21 Apr '13

21 Apr '13

Hi, I added one more check to the automatic tests: If a package has multiple spec files, it's actually not one package submitted but two or more. But so far I only checked the package the submission came from. I changed this now and this has 2 consequences: if you have a python-foo/python-foo.spec and a python-foo/python3-foo.spec you now also need a python3-foo package in your project linking to the python-foo package *and* both packages have to be succeeded. This also means that both packages are checked for file conflicts and broken dependencies. I did a rather large rewrite of the way the checking works due to support of group requests that I wrote last week (and I will announce in more detail once I have some user interface for it, for now let me refer to my hackweek page[¹] :) Greetings, Stephan [1] https://github.com/SUSE/hackweek/wiki/Improved-Factory-devel-project-submis… -- 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] find-lang.sh fails for paths containing colons
by Andrey Borzenkov 19 Apr '13

19 Apr '13

I tried to quickly build package locally and got bor@opensuse:~/obs/home:arvidjaar:grub2-next/grub2/foo/BUILD/grub-2.00> LC_ALL=C /usr/lib/rpm/find-lang.sh /home/bor/obs/home:arvidjaar:grub2-next/grub2/foo/BUILDROOT/grub2-2.00-0.x86_64 grub2 sed: -e expression #1, char 33: unknown option to `s' sed: -e expression #1, char 33: unknown option to `s' Well, find-lang.sh is using s:$PATH:: and that of course breaks if path itself contains ':'. Not sure how common it is, nor how to make it more robust. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 4

[opensuse-packaging] Turn off auto-requires on perl/python/ruby
by Michal Vyskocil 16 Apr '13

16 Apr '13

Hi, I was surprised when I've cheched the taskwarior's dependencies and found /usr/bin/{perl,python.ruby}. It seems it's autogenerated because some addon scripts are installed with a package. However I am not sure which of our magic scripts makes it. The /usr/lib/rpm/find-requires seems to add perl when it find a shebang and python in a case something in /usr/libxy/python is installed. There are already fileattrs with perl.attr and python.atts, but I did no found anything for ruby. Has anyone an idea how to suppress the automatic adding of a dependency to interpreters by default? package https://build.opensuse.org/package/show?package=taskwarrior&project=utiliti… build log https://build.opensuse.org/package/rawlog?arch=x86_64&package=taskwarrior&p… Regards Michal Vyskocil

2 2

[opensuse-packaging] Re: [obs submit-request 164046] devel:libraries:c_c++/ppl: accepted by namtrac
by Richard Biener 15 Apr '13

15 Apr '13

On Mon, 15 Apr 2013, Ismail Doenmez wrote: > > State of submit-request #164046 was changed by namtrac: > > new -> accepted This should have been declined. It increases the size of the bootstrap cycle and it's dependencies. GCC depends on ppl. Thus it will break Base:build even more. > Comment: > > > https://build.opensuse.org/request/diff/164046 > > Source > project: home:namtrac:bugfix > package: ppl > revision: 2 > > Target: > project: devel:libraries:c_c++ > package: ppl > > > -- Richard Biener <rguenther(a)suse.de> SUSE / SUSE Labs SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746 GF: Jeff Hawn, Jennifer Guild, Felix Imend -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 7

[opensuse-packaging] Should kdebase4-workspace-plasma-calendar be merged into kdebase4-workspace
by Joseph Mulloy 15 Apr '13

15 Apr '13

After upgrading from 12.2 to 12.3 I started to get a dialog after logging into KDE asking me to install a "calendar data engine". Unfortunately the wizard can't actually find the package which turns out to be kdebase4-workspace-plasma-calendar. Since this package is required by the plasma clock widget for full operation it should either be required by kdebase4-workspace or merged into kdebase4-workspace. Based on the changelog from when the package was originally split off it's supposed to be recommended by kdebase4-workspace, but when I check it in 12.3 it's not. Is there any good reason for this package to be split? Is merging a split package into the main package on a released version of openSUSE allowed? https://bugzilla.novell.com/show_bug.cgi?id=803538 # kdebase4-workspace.changes ------------------------------------------------------------------- Wed Dec 7 14:18:37 UTC 2011 - saschpe(a)suse.de - New subpackages plasma-engine-akonadi and plasma-calendar: * Removed %kde4_akonadi_requires from base package, otherwise half of KDE depends on akonadi-runtime. * Both are recommended by base package Joseph Mulloy jdmulloy(a)gmail.com -- 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] "Upstream First" policy proposal
by Jan Engelhardt 12 Apr '13

12 Apr '13

Hi, I am hereby announcing that I added a new section regarding "Upstream First" policy to https://en.opensuse.org/openSUSE:Packaging_Patches_guidelines . Package maintainers who are upstream at the same time may declare UF if they think it helps their workflow, and the wiki entry just formally writes down the practice formally that had already been in place with some packages. (In that regard, it is not really a proposal.) On 04/11/2013 07:22 PM, MediaWiki Mail wrote: > >The openSUSE page openSUSE:Packaging Patches guidelines has been >changed on 11 April 2013 by Jengelh, see >https://en.opensuse.org/openSUSE:Packaging_Patches_guidelines for the >current version. > >Editor's summary: Declare "Upstream First" > > Your friendly openSUSE notification system -- 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] When to use recommends?
by Greg Freemyer 11 Apr '13

11 Apr '13

All, How is the decision made to have a recommends statement made? == my situation I packaged fio for 12.3. Fio is a performance testing tool for disk subsystems. One of its features is it can produce plots viewable via gnuplot so there is a recommends gnuplot in the specfile. I've just had a user raise the concern that on a server gnuplot brings in a ton of desktop related packages. Further he argues he would run fio on the server, but gnuplot on his desktop. I can see both sides of this, but I am inclined to remove the recommends statement. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

10 14

[opensuse-packaging] tftp
by Stephan Kulow 10 Apr '13

10 Apr '13

Hi, There seem to be different concepts what permissions and owner /srv/tftpboot should have. Can we agree on something? :) found conflict of atftp-0.7.0-156.1.x86_64 with kiwi-pxeboot-5.05.7-582.1.noarch: - /srv/tftpboot [mode mismatch: d750 tftp:tftp, d755 root:root] found conflict of dnsmasq-2.65-5.1.x86_64 with kiwi-pxeboot-5.05.7-582.1.noarch: - /srv/tftpboot [mode mismatch: d750 root:tftp, d755 root:root] found conflict of kiwi-pxeboot-5.05.7-582.1.noarch with tftp-5.2-5.1.x86_64: - /srv/tftpboot [mode mismatch: d755 root:root, d750 root:tftp] Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 4