openSUSE Packaging January 2013

packaging@lists.opensuse.org

56 participants
38 discussions

[opensuse-packaging] Packaging Guideline enforcement

by Dominique Leuenberger a.k.a DimStar

Dear Factory contributors and packagers, As openSUSE 12.2 is frozen and Factory is 'open to go wild' again, I would like to announce that the packaging guidelines have some extensions (not really new) that will be stricter enforced than they used to be. Currently a common rule to be 'ignored' or packagers are not aware is around the topics of: - .Changes entries - Patches First, the .changes entry (rpm changelog) surves two purposes: - News for the user - History tracking of packaging changes (often referenced in bugs to verify if a user has the latest packaging bugfixeS). A simple "Update to version x.y.z" is, as before, not accepted. There should be some buzz around the update for the user; some major reasons to the upgrade should be listed Changes on the package itself should be mentioned in a way that any other contributor to the same package can follow traces of why something is the way it is. Commonly, Added (build)dependencies are interesting to be seen, special hacks to make something work in a particular way [..]: Always consider that package maintenance is a distributed task and various contributors need to be able to step up at will. Patches: The rules about patches are listed at http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines . Most prominent is likely the mentioning of the patches life cycle, which forces you to mention additions and removals of patches in the changelog. As history shows, this can be helpful if a patch got removed, and later a regression is reported; finding out when a patch was removed can be crucial in reconstructing feature sets (including contacting the contributor that dropped it.. which is easily extracted from the .changes if listed) The main appeal is to the devel project maintainers / reviewers, to keep out for those rules, to live according to them, as it is frustrating for everybody if a package needs to be declined by the Factory Review team: - The dev prj maintainer is the one getting the 'decline' (as it was usually a forwarded request), which often leaves the 'fixing' to the devel project maintainers, where the 'originator' of the fix would have been willing to actually do that... And the Factory Review team also prefers to see complying submissions to having to reject SRs... reject is not fun for anybody! Looking forward to many more SRs to accept! Dominique / DimStar -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

7 years, 9 months

[opensuse-packaging] Package looking for volunteers: CodeAnalyst

by Cristian Morales Vega

As per https://bugzilla.novell.com/show_bug.cgi?id=793541 it seems CodeAnalyst needs a new maintainer. Any volunteer? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

7 years, 10 months

[opensuse-packaging] package looking for maintainer: the AT daemon

by Cristian Rodríguez

Hi: I will no longer maintain fix or otherwise care about the "at" daemon, starting now because I would rather devout my time testing and improving systemd.timer(5) So it is now up for grabs. that's all ;) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

8 years

[opensuse-packaging] ldconfig - I'm frustrated

by Greg Freemyer

All, I sent the httrack package to security a couple weeks ago. It builds, but with a few rpmlint issues. I thought I would clean up the one about the shared library needing to be split out to its own package. I've tried to do that in home:gregfreemyer:branches:security > httrack The diff is: https://build.opensuse.org/package/rdiff?opackage=httrack&oproject=security… I've tried multiple ways to call ldconfig. But my build always fails with: [ 218s] libhttrack2.x86_64: E: library-without-ldconfig-postin (Badness: 300) /usr/lib64/libhtsjava.so.2.0.46 [ 218s] libhttrack2.x86_64: E: library-without-ldconfig-postin (Badness: 300) /usr/lib64/libhttrack.so.2.0.46 [ 218s] This package contains a library and provides no %post scriptlet containing a [ 218s] call to ldconfig. The spec file currently has: === %post /sbin/ldconfig /usr/lib64 %postun /sbin/ldconfig /usr/lib64 === I've tried the basic versions as well. == %post -p /sbin/ldconfig %postun -p /sbin/ldconfig == %post /sbin/ldconfig %postun /sbin/ldconfig == Can anyone tell me what's going on? Thanks Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

8 years, 3 months

[opensuse-packaging] Factory iscsitarget build failure: problem with traceroute?

by Lee Duncan

Hi: I am trying to track down why Factory iscsitarget has been failing to build for the last month. It looks like it is because of a dependency on traceroute version 2.0.0 or later. On the iscsitarget page on the web interface, it shows the build results for x86_64 and i586 as "unresolvable", saying "nothing provides traceroute >= 2.0.0 needed by net-tools". When I look at the openSUSE:Factory/traceroute package, it says the same thing. Further adding to the strangeness, the openSUSE:Factory traceroute package links to the network:utilities traceroute package, and the network:utilities traceroute package seems to be building just fine. Not being familiar with this area of packaging, I'm guessing this has something to do with the recent changes to net-tools and traceroute? -- Lee Duncan SUSE Labs -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

8 years, 4 months

[opensuse-packaging] RE:From VCOM factory-Would you like to be the 80th distributor?

by vcom-Cherry

Dear VCOM Partner: Good day.How are you?How is business? Thanks for your 5minutes time to read this email.The potential business chance coming with it.Would you like to become the top brand in your computer accessories market and win a high reputation with pretty profit?VCOM will support products with ALL KIND OF COMPUTER CABLES,HEADPHONE,ANDROID TV PLAYER...etc. VCOM enterprise since 2010 start face to the world for deal our VCOM and AOPEN brand with great support to our distributors.Till now we would like to congratulate that current we finally have extend 79 distributors which dealing with our VCOM brand product in the world as well.In such short time we got a such excellent effort cause all of our VCOM group people have same aim as we are strive to let our brand become more famous as world brand in the coming future. We are doing best always.Welcome you join with us together to our big family. If you want to be a distributor,VCOM brand.VCOM company always are most trustable for you.Free marketing items support get ready for you with professional service as below:1.)VCOM Catalog 2.)VCOM Booklet 3.)VCOM Big Plastic Bag 4.)VCOM Small Bag 5.)VCOM PostCard 6.)VCOM Pen 7.)VCOM Poster-advertisement.(Pls check the attachment.) 8.)VCOM Stand 9.)VCOM T-Shirt 10.)VCOM Flag 10.)VCOM Flag with Etagere 11.)VCOM Oversea exhibition .......even more if you want~~! And it is so happy to inform that VCOM COMPANY is going again to attend the CEBIT exhibition in Hannover, Germany 2013.Welcome your visit to our booth in Hall 17 F42.We are waiting for you to show you newest VCOM high end product. We are also going to RUSSIA ,TAIWAN,BRAZIL,TURKEY,SOUTH AFRICA...... these oversea exhibition in our 2013 year plan.We will inform you the booth number later.Hope also can see you there too. Anything need my help pls dont hesitate to let me know. I am waiting for your golden feedback. Have a nice good day!~_~! Best regards Yours sincerely Cherry Vcom Electronic Mfg.Ltd.VCOM INTERNATIONAL LTD Address: 1/2F,Building D,Youke Business Center,Kexin Rd, Tangxia,Tianhe District,Guangzhou City,Guangdong Province,China TEL：+86-20-28265329 FAX：+86-20-22832562 Mobile:0086-13560398840 MSN：vpro88(a)hotmail.com SKYPE：vpro88 Website：www.vcom.com.hk (CABLE product) www.vpro.hk (TV antenna product) Email：vcom68(a)vcom.hk

8 years, 4 months

[opensuse-packaging] What is /usr/com?

by Andrey Borzenkov

I accidentally noticed bor@opensuse:~> rpm --eval %_sharedstatedir /usr/com bor@opensuse:~> rpm --eval %_datarootdir /usr/share bor@opensuse:~> As far as my memory serves me, %_sharedstatedir was /usr/share, was not it? And it the the first time I see /usr/com (which does not even exist on my system). Is it a new trend? Where can I read more about it? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

8 years, 4 months

[opensuse-packaging] [reminder] openSUSE 12.3 RC 1 is next week

by openSUSE Roadmap Reminder

Hello all, openSUSE 12.3 RC 1 will be released next week, on Thursday 07 February 2013. Please submit your packages before Friday afternoon (UTC time) to make sure they will get included in this release. Leaf packages submitted during the week-end might also get accepted on Monday. For a quick overview of the openSUSE Roadmap, please see: http://en.opensuse.org/Roadmap Thanks, -- openSUSE Roadmap Reminder -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

8 years, 4 months

[opensuse-packaging] Factory Status (2013/01/26)

by Cristian Morales Vega

27 packages failing for more than two weeks (and monodevelop has been failing already for 12 days). Name Devel Project Bug report Status - libzypp-bindings zypp:Head bnc#793554 Fails for 73 days: test suite fails - webyast-base YaST:Web bnc#793558 Fails for 69 days: No such file or directory - /var/lib/polkit-1/ (Request 149902 to YaST:Web) (Different changes in devel project (since 5 days)) - mono-tools Mono:Factory bnc#796901 Fails for 46 days: error CS1061: Type `Mono.Cecil.Cil.ExceptionHandler' does not contain a definition for `FilterEnd' (Different changes in devel project (since 4 days)) - nant Mono:Factory bnc#796902 Fails for 46 days: missing framework mono - sblim-cmpi-ssh_service_profile systemsmanagement:wbem bnc#796900 Fails for 46 days: /etc/init.d/sfcb: No such file or directory (Different changes in devel project (since 18 days)) - sblim-cmpi-power_supply_profile systemsmanagement:wbem bnc#796900 Fails for 46 days: /etc/init.d/sfcb: No such file or directory (Different changes in devel project (since 18 days)) - sblim-cmpi-fan_profile systemsmanagement:wbem bnc#796900 Fails for 46 days: /etc/init.d/sfcb: No such file or directory (Different changes in devel project (since 18 days)) - sblim-cmpi-ethport_profile systemsmanagement:wbem bnc#796900 Fails for 46 days: /etc/init.d/sfcb: No such file or directory (Different changes in devel project (since 18 days)) - sblim-cmpi-boot_control_profile systemsmanagement:wbem bnc#796900 Fails for 46 days: /etc/init.d/sfcb: No such file or directory (Different changes in devel project (since 18 days)) - atspiuiasource Mono:Factory bnc#796922 Fails for 45 days: Warning as Error: Assuming assembly reference `WindowsBase - uiadbus Mono:Factory bnc#796923 Fails for 45 days: Warning as Error: Assuming assembly reference `WindowsBase - uiaatkbridge Mono:Factory bnc#796924 Fails for 45 days: Warning as Error: Assuming assembly reference `WindowsBase - uiautomationwinforms Mono:Factory bnc#796925 Fails for 45 days: Warning as Error: Assuming assembly reference `WindowsBase - libdlm network:ha-clustering:Factory bnc#798263 Fails for 35 days: broken with kernel 3.7 - kde3-sim KDE:KDE3 bnc#800687 Fails for 16 days: invalid use of incomplete type 'xmlBuf {aka struct _xmlBuf}' - ipsec-tools security bnc#800688 Fails for 16 days: Unable to find linux-2.6 kernel headers (New upstream version 0.8.1 available) - delayacct-utils Base:System bnc#800689 Fails for 16 days: /linux/taskstats.h': No such file or directory (Different sources in devel project (since 2 days)) - kdewebdev3 KDE:KDE3 bnc#800690 Fails for 16 days: undefined reference to `docbParseFile' - hawk network:ha-clustering:Factory bnc#800691 Fails for 16 days: ERROR: Failed to build gem native extension. - yast2-pkg-bindings-devel-doc openSUSE:Factory bnc#800692 Fails for 16 days: Entity 'PkgModuleFunctionsPatch' not defined - gimp-help GNOME:Apps bnc#800693 Fails for 16 days: xml2po crash? - opensuse-manuals_en Documentation bnc#800694 Fails for 16 days: No rule to make target `document-files-html' (Different changes in devel project (since about 21 hours)) - opensuse-manuals_de Documentation bnc#800694 Fails for 16 days: No rule to make target `document-files-html' - opensuse-manuals_ru Documentation bnc#800694 Fails for 16 days: No rule to make target `document-files-html' - opensuse-manuals_ja Documentation bnc#800694 Fails for 16 days: No rule to make target `document-files-html' - pg_comparator server:database bnc#800695 Fails for 14 days: postgresql update broke it (Different changes in devel project (since about 18 hours)) - qbittorrent network bnc#800696 Fails for 14 days: something around boost -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

8 years, 4 months

[opensuse-packaging] new wiki page for Ruby gem packaging strategies

by Adam Spiers

[Reply-To: set to opensuse-ruby] Hi all, After many discussions on this list, and also many internal discussions within SUSE, I have attempted to summarise a collective understanding about the pros and cons of the various strategies for packaging Ruby applications. This is not a complete understanding since it was not possible to involve all experts in the area, nor is it even at this point a set of guidelines or recommendations for which strategy to adopt. However hopefully it should help Ruby application architects make an informed decision about which approach best suits their project. Feedback is warmly encouraged - please feel free to edit the wiki page directly with your additions / amendments! Thanks, Adam -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

8 years, 4 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging January 2013