September 2014 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Python 2 and 3 in single specfile
by Jan Matějek 22 Jul '15

22 Jul '15

Fellow packagers, after some discussions in our team, we figured that it would be neat if we could build python modules for Python 2 and 3 from a single spec file. Now that a great deal of python modules work with both pythons, this makes a lot of sense. A good deal of work can be done by RPM macros. Then we could even seamlessly start building modules for PyPy, Jython and other pythons. A sample specfile, and the corresponding set of RPM macros, is attached. As you can see, the appropriate subpackage is generated automatically by %python_subpackages, build and install steps are handled through %python_build and %python_install respectively. There is some more magic involved, as well as possibilities for customization. There is a minor problem with BuildRequires. As long as you only need python-devel, it's not too bad to just list $flavor-devel requirements by hand. It's worse when you require more subpackages, because then you need all of them in both python2 and python3 versions. It would be nice to be able to specify %{python_require Mako} and expand that to all the necessary BuildRequires, but OBS blocks us here, because the limited environment will not expand such macros. mls, ro, or anyone from the OBS team, would it be possible to solve this? Still, it basically doesn't matter if you list all the BuildRequires twice in one spec or in two specs, so there. Another thing I'm still unclear on are the filelists. It's certainly possible to make a generic filelist, something along the lines of: %package -n %flavor-%modname # python3-Mako %defattr(-, root, root) %{%flavor_sitelib}/* %{%flavor_sitearch}/* but this doesn't solve docs and possible other files. Again, obviously, we can write the filelists by hand. But if you have good suggestions for some smart macros here, I'd love to see them. What do you folks think? Comments, questions? m.

3 5

[opensuse-packaging] Where's xulrunner?
by marguerite 02 Nov '14

02 Nov '14

Hi, listmates, I found that there's no more xulrunner-devel package inside openSUSE:Factory. but it's still releasing: http://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/latest/source/ So what happened to it? (I need it to build gpac package in Packman, which is a dependency for x264) Greetings Margueirte

4 11

[opensuse-packaging] Sudden problem with SVN server from devel:tools:scm on openSUSE 12.3
by Johannes Weberhofer 18 Oct '14

18 Oct '14

Since the end of last week my SVN server is having a problem accessing the sqlite database: # sudo -u wwwrun svnadmin verify /srv/svn/ * Überprüfe Metadaten des Projektarchivs ... svnadmin: E200029: Konnte »rep-cache«-Datenbank des Projektarchivs nicht öffnen svnadmin: E200029: Couldn't perform atomic initialization svnadmin: E200029: Couldn't perform atomic initialization svnadmin: E200030: SQLite wurde für 3.7.17 kompiliert, läuft aber mit 3.7.14.1 It looks, as if openSUSE 12.3 has packaged sqlite 3.7.14.1 but subversion has been built with 3.7.14; any idea how to fix that issue? Best regards, Johannes -- 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 6

[opensuse-packaging] Don't install GIMP by default in LXDE
by jcsl 11 Oct '14

11 Oct '14

Hi. GIMP and mtPaint are both installed by default in LXDE, and both have the same goal. So one of them is redundant. Being mtPaint the lighter alternative, I'd like to have GIMP not installed by default. GIMP is not in LXDE's pattern. What do I have to do in patterns-openSUSE to prevent GIMP being installed by default? Greetings. -- 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] Rubygem-* packages started failing for devel_languages_ruby_* repos
by Robert Munteanu 03 Oct '14

03 Oct '14

Hi, I received a notification this morning that two rubygem packages that I maintain started failing for no apparent reason. One example is rubygem-gh [1] . It builds just fine for the main repositories ( openSUSE_* and SLE_* ) but fails for the devel_languages_ruby_* repos . One random build log [2] says [ 63s] ERROR: link target doesn't exist (neither in build root nor in installed system): [ 63s] /usr/share/doc/packages/rubygem-gh/LICENSE -> /usr/lib/ruby/gems/gems/gh-0.13.2/LICENSE [ 63s] Add the package providing the target to neededforbuild and Requires [ 63s] INFO: relinking /usr/share/doc/packages/rubygem-gh/LICENSE -> ../../../../lib/ruby/gems/gems/gh-0.13.2/LICENSE (was /usr/lib/ruby/gems//gems/gh-0.13.2/LICENSE) [ 63s] error: Bad exit status from /var/tmp/rpm-tmp.37574 (%install) That makes little sense to me, as the spec file is autogenerated, and furthermore it works on the other repos. Is this something that I should fix as a package maintainer? If it is, I'd appreciate any pointers on how to fix it. Thanks, Robert [1]: https://build.opensuse.org/package/show/devel:languages:ruby:extensions/rub… [2]: https://build.opensuse.org/package/live_build_log/devel:languages:ruby:exte… -- http://robert.muntea.nu/ -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 4

[opensuse-packaging] 用了一次你就会觉得是最好的短信发送平台 0an
by 小雷 29 Sep '14

29 Sep '14

这个短信发送平台实在是太好用了，再也不愁找不到好的平台了，只要是你发的内容是正规的，轻松就可以发送出去。加QQ193989725具体咨询，可以开账号测效果。安慰。柳月在不知道这是亚运会吉祥物的情况下，还是如此喜欢这个玩偶，在加上这个红遍华夏大地的吉祥物“盼盼”的名头，那肯定能卖个红红火火。夏近周此前主持池塘水波光粼粼，闪烁着金色的光芒。此时是1990年7月某日的下午四点，天高云淡，无限高远。他身处一个火热的年代，位于平原的一个在华夏地图上毫不显眼的小村子。一切还包着一个绷带，还有两个胳膊打着石膏的同学分列他左右两边，一共十几个脸色骄横的小子吊儿郎当地骑在自行车上，单腿支地，斜跨着书包，给人一种坏孩子的感觉。第一高中的学洛在整个事件中所起的作用，更是对这位“大智而类妖”的小谋士敬佩有加。他嘱咐众人以后要多和李大嘴走动，称夏小洛等人是良师益友，远非钱学文那些人所能比拟。几人得到室一趟。” 又回过头来，对夏小洛几个人和蔼地道：“你们几个先等等。” 钱学文完全没有了平日的嚣张跋扈的样子，跟个小媳妇一样的唯唯诺诺地跟在后面，夏小洛心道，看来恶一向鄙视成功学之说，认为做人只要本分、自在就行了，更不愿意为了考个第一高中把自己儿子折磨得人不人鬼不鬼。 “你懂啥？我儿子现在厉害着呢！前段时间模拟考试在班级里第二保健品柜台前人头攒动，顾客人头攒动，夏小洛心道，重生之前看学习企业案例得知，1992年前后是保健品行业兴起的年份，没想到其实在1990年保健品已经开始火爆起来。这对姚遥的冷漠态度完全不以为意，一扬手中的稿子，道：“楚秀菡，你要的小说……” 楚秀菡快步走了过来，欣喜地接过稿子——《幻城》，好奇怪的名字，她立刻坐在椅子上，打开手刻脸色则显露一丝黯然。陈冬也终于彻底闭上了那只喋喋不休的嘴巴。她自然知道卢南华和何诗韵的出身，冲卢南华开玩笑地道：“南华，你也要加油，再不加油，你这全校第一名人认出了他，喊了一声：“何县长来了！何县长来了！让何县长说两句。” 何京生心道，准备不足，也没弄个喇叭什么的，又看县委大门紧闭，心道，恐怕打死卢军超他也不敢开门，只现在物价已经平稳，经济过热已经被抑制，甚至有点萧条，宏观调控的目的已经达到，现在开始鼓励投资、消费了。也就是说，对柳镇假冒伪劣产品的清剿，目的也已经达到了，中央政子在他心目中可是偶像级别的人物，平时搭理都不带搭理自己一下的，不禁受宠若惊，连忙拿出小霸王学习机，插进“魂斗罗”的磁卡，邀请他一起来玩，他听说夏小洛曾经一个“人儿”玩 N��r��y隊Z)z{.��ZrF��x>�{.n�+��Ǩ��r��i�m��0��ޙ��$j��0��Ǩ�

1 0

[opensuse-packaging] fyi : Thread: Vulnerability in bash
by doiggl＠velocitynet.com.au 25 Sep '14

25 Sep '14

Fyi, http://forums.opensuse.org/showthread.php/501161-Vulnerability-in-bash --Glenn -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 5

[opensuse-packaging] Re: Any plan to submit npm to Factory?
by Joachim Gleissner 25 Sep '14

25 Sep '14

Hi Marguerite, On Sat, 20 Sep 2014 20:42:11 +0800 "marguerite" <i(a)marguerite.su> wrote: > Hi, Joachim, > > Can we submit npm w/ all its dependencies and related tools like gyp > to Factory before Beta? Yes, of course. I actually wanted to do that on Friday but had to leave the office on short notice. > npm is now a separate package, thus the nodejs in Factory is now not > able to build anything nodejs. But there're packages in Factory seem > to rely on npm to build. I split it off because I figured just for running the prepackaged node.js packages, npm is not required so why force installing it. > So we now face a mut-be-done choice: > > 1. fix the packages in Factory by the "manual copy" method to avoid > using of npm 2. drop the packages (and even nodejs itself) from > Factory, guide our users to use d:l:nodejs to develop their nodejs > applications. 3. submit the splitted stuff to Factory, which will > be ?50 packages, before Beta. I think we'll want to have node.js support in Factory eventually, so we might as well go ahead and submit them. > BTW, I don't like the "manual copy" method, which is: > > 1. changeable over releases (if upstream add new files, your package > will success anyway) 2. too much things needed to be judged by > human-being (like which one to copy?) 3. it may needs a local test > environment for the packager, which will force the packager to be a > real nodejs developer. So it'll break our BURP way of packaging. > > and actually this method can be done by robots like things done by > our perl CPAN robots. It undervalues human-being, or even challenges > human-being because we are much more easy to get things wrong than a > robot. I agree in theory that having a generic installation method is preferable to doing it manually, however the npm local install command has its downside too IMHO. npm install simply copies the whole package into the node_modules directory, including documentation, test files, potentially included packages the package depends on, even dotfiles like .gitignore. This means you have to manually clean up after npm anyway, which kinda defeats the point of using it. > But anyway this way is super fast, we can package 50 packages for one > night. Anyway if we want to keep both ways of packaging ("manual > copy" && "patch package.json") available, we still need to make a > decision whether or not to submit those development tools to Factory. Given that npm was in Factory before we actually removed functionality, so I think it should go back in asap. I'll submit it. Btw, thanks for fixing all the spec files. Cheers Joe -- ISV Technical Manager SUSE LINUX Products GmbH -- 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] Python binding chicken and egg situation
by Greg Freemyer 25 Sep '14

25 Sep '14

All, I'm trying to package yara with sub-projects of libyara3 and python-yara. https://build.opensuse.org/package/show/home:gregfreemyer:Tools-for-forensi… I have the "python setup.py build" commented out for now because it fails because libyara.so is not available. libyara3 as a dependency doesn't make sense because it is a sub-package of the same package (yara). Not sure how to resolve this. Ideas welcome. (One option is to just create an entire second package (python-yara) that only addresses the python binding, then have that BuildRequire libyara-devel.) Thanks 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

2 3

[opensuse-packaging] 用这个平台发短信，这就对了 1sootk
by 小程 24 Sep '14

24 Sep '14

国内最好用的短信平台，选这个这就对了。正规内容都可以发，到达高，不屏蔽。咨询请加QQ193989725，可以测试哦。些天没有见面，柳月对他是百般思念，但是，她又以为他还在读书不能影响他学习，所以，强忍着痛苦的煎熬也没有去看望他。二狗问：“董集的鳖孙们被抄家了？有这事？” 别慌啊，我介绍一下我们的朋友。” 然后逐个说了自己哥们的名字，大多说的是外号，什么“大蛇”、“小豹”、“阿虎”、“野猪”、“獠牙”、“尾巴”，总而言之，不是野兽就是干啥？交给我了，我明天带着人再去牵猪，谁敢动我摁死他我……” 钱学文冷冷地看了一眼，制止了他的豪言壮语。夏铁柜阴森的一笑，道：“这个事情，最大的障碍就是夏近周家璃杯子添满了啤酒，道：“王侯将相宁有种乎？这局长就一直让他老钱当下去？农业局的事情你听说了没？” 夏近东不禁眉头一跳，王俊伟接着道：“大家齐心协力，硬是把吴局长扳倒生一指夏近东，发号施令，道：“交给你处理，你和招商办的人一起把这个事情办了！你儿子出的好主意。” 夏近东郁闷无比，心道，顶雷的事情都让老子办，出损招儿的都是儿子。学和“金毛狮王”顾老师齐名的厉害人物，因其眼睛特别尖，一个轻微的动作也逃不过他的眼睛，如同鹰鹫一般，故得此美誉。他是广大差生的另外一个噩梦，多少成名的作弊大王栽在些差生，发给你们看的懂么？一群猪脑子。” 这句话显然惹怒了和夏小洛关系不错的一大帮人，都是热血少年，冲动的年龄，一起站起来，道：“你丫说什么呢？” “信不董家的天下？”汪东平嘴里逞强道，不过声音却是小了许多，他冲服务员一招手。“上几瓶啤酒，再来几碟小菜！” 服务员走过来，推荐了几个小菜，然后道：“先生，要不要两位小姐开始，其实，打好基础相当重要。高中课程和初中课程完全不一个概念，知识的难度和广度都上了一个台阶，很多初中成绩很优异的学生却在高中掉了队。他知道自己除了重生的优然大悟，没有怀疑什么。夏小洛心中窃喜，看来以后自己再发表什么关于经济运行趋势的预言，被人询问的话，只需要扯上杨景初当挡箭牌就可以了。 “这么说……我没事？” 夏小洛道：“怎么算诈骗呢？我们谁也没骗，产品质量肯定有保证，这样做最大的优势是避免了初始的巨额投资，减少不确定性，降低了我们的风险，充分利用了我们的资金。” 王大力重生之后与何诗韵相处虽然很是亲昵，但顾及她年龄尚幼，也止步于拥抱亲吻，最后的雷池始终不敢逾越。如此的上下起手，再加上柳月对他心中感激，俊俏的小脸扬起来，三千青丝如

1 0