openSUSE Packaging September 2010

packaging@lists.opensuse.org

46 participants
36 discussions

[opensuse-packaging] Right usage of libexecdir?

by Vincent Untz

Hey, Dominique and I are currently wondering what to do wrt libexecdir for evolution-data-server. Should we leave it unchanged (so files will be in /usr/lib) or should we change it to /usr/lib/evolution-data-server? If the latter, is there any reason this is not done automatically? Also, hrm, would rpmlint have ways to warn about packages that put binaries in libdir instead of libexecdir? (I can find a few of them here with a grep) Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

10 years

[opensuse-packaging] Python 2.7 coming to Factory

by Jan Matejek

Fellow developers and users, just a heads-up: moments ago I have submitted a new Python version 2.7. This version contains many new and interesting features, and only a small chance of breaking existing code: no backwards-incompatible changes, and no big changes worth mentioning. For more details see [1]. There is one thing notable for people who write or maintain software that embeds Python: the new function PySys_SetArgvEx [2] does the job originally done by PySys_SetArgv, but closes a nasty security problem with the latter [3][4]. Most software should be fixed by now, but please review your packages anyway. have fun m. [1] http://docs.python.org/dev/whatsnew/2.7.html#porting-to-python-2-7 [2] http://docs.python.org/dev/c-api/init.html#PySys_SetArgvEx - the link points to python 3 docs, but applies to 2.7 as well [3] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5983 [4] http://www.openwall.com/lists/oss-security/2009/01/26/2 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

10 years, 8 months

[opensuse-packaging] a library naming question.

by Dave Plater

Hi, I'm trying to update multimedia:libs libraw1394 but it has a sub package called libraw1394-8 with a file called libraw1394.so.8 which is required specifically by a ton of packages. The new package has a lib called libraw1394.so.11, it's close to my bedtime so the brain isn't 100% but updating libraw will at least cause a major rebuild hopefully no missing dependencies. The rebuild would take care of Requires: naming. My question is - should I just leave the 8 in libraw1394-8 or should it become libraw1394-11 and have I missed anything? I've already contacted the upstream maintainer about it's patch for streaming video that prevented it building and was a fix for a novell bug. The package wasn't updated for years possibly due to the fact that the Url: pointed to a defunct domain which is up for sale. I'm working on it in home:plater libraw1394 if somebody can have a look. Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

10 years, 8 months

[opensuse-packaging] boinc-client to sale

by Sascha 'saigkill' Manns

Hello Mates, since a few years i'm serving as Maintainer of the BOINC Package. Sadly the last Versions can't driven correctly. So i would like to give the Maintainer Job another, better Person. Maybe we can place then a running Version into Factory. All needed Files (my latest Status) can seen under home:saigkill:boinc. cu Sascha -- Sincerely yours Sascha Manns open-slx GmbH openSUSE Community & Support Agent openSUSE Marketing Team Blog: http://saigkill.wordpress.com Web: http://www.saschamanns.de Web: http://www.open-slx.de (openSUSE Box Support German) Web: http://www.open-slx.com (openSUSE Box Support English) Open-SLX : Linux convenient, simple, secure and complete

10 years, 8 months

[opensuse-packaging] Why should an unstable released package be favoured over a stable svn package?

by Dave Plater

Hi, I've been trying to submit an svn derived version of KTrafficAnalyzer to KDE:Extra, the package used to be in the old kde3 community repo and has been around in openSUSE for quite a while. It's been ported to kde4. I've been using the package from the authors home project and it occasionally crashed and lost the usage stats but after my recent update from KDE:Distro:Factory it consistently segfaulted on start up. This is a good thing that enabled me to track down the problem and patch it. It's now stable on a patched svn revision 44 so I decided to submit this very usefull package to KDE:Extra and am quite happy to maintain it as I use it all the time and it's a simple package only to have it rejected on the grounds that it's svn derived. This seems a bit stupid because the released package is unstable and even has a source forge bug against it from an openSUSE 11.3 user. I've had problems submitting a package fix to KDE:Extra before but in that case the maintainers reply was rather rude that issue was simply bad communication and was resolved and that particular maintainer accepted my second submit attempt of KTrafficAnalyzer pointing out that there wasn't a Url: in the spec file and asking me to fix it. I decided to patch the released tarball to svn 44 and submit that along with the fixed spec file but alas the first anti subversion maintainer caught the request and declined it. I was under the assumption that I'm helping to make openSUSE a better distribution but my encounters with KDE:Extra have made me think that that particular repository is an ego circus, it's easier to get a new package into Factory than into KDE:Extra, I've two new packages in 11.3 one of them totally new to openSUSE and one that the previous maintainer didn't have time for so it was dropped so I speak from experience. The point of this email are the questions :- am I flogging a dead horse trying to be a useful member of the community? Why do I get the impression that KDE:Extra is maintained a an exclusive club? Thanks for taking the time to read my rant. Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

10 years, 8 months

[opensuse-packaging] Corruption in openSUSE update repositories, how to report?

by Remco de Vreugd

Hi all, This is probably not quite the right place to ask, but I could find no list closer to the subject at hand. Sorry about that. I am regularly running into corruption within the openSUSE update repositories, i.e. the collections of files as downloadable from mirrors throughout the world. Every once in a while, the information listed in the metadata files (as in 'repodata/...-primary.xml' or 'repodata/...-deltainfo.xml') mismatches the characteristics of the downloadable RPMs. For some items, the metadata says the SHA1 hash of the RPM should be X, whereas the actual value of the downloadable file turns out to be Y. Everywhere, on all mirrors. To whom do I report this kind of problem? Aside from finding the root cause of the issue (which so far is occurring only with 11.2, not with 11.1 or 11.3, and most often with delta RPMs), it would be nice to have a way of getting detected occurrences 'flushed' from all mirrors. Something quicker, that is, than just waiting for the packages to get updated once more. Best regards, Remco de Vreugd. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

10 years, 8 months

[opensuse-packaging] kde-obs-generator is looking for a new name

by Michal Hrusecky

You probably already [5]heard about that. Some time ago, [6]Luboš [7]created really great tool - [8]kde-obs-generator. This tool takes a simple config and analyze tarball with sources. Then it will try to create spec file, dsc file and everything you need to build package from that. Easy to use even for non-packagers ;-) One little potential inconvinience with kde-obs-generator was that it depended on one KDE core library. Not really problem in openSUSE, just one little library to install, but it might be more complicated elsewhere. On other distributions dependency on this one KDE library might be non-trivial and pull in quite some KDE components. And some folks might dislike it even because something not so practical. I can imagine that it may sound quite funny packaging Gnome application with KDE application ;-) So with some poking (and little help) from our side, Luboš dropped the dependency on KDE libraries and now it depends only on Qt. So as it no longer depends on KDE, name kde-obs-generator doesn't really describe this tool well. So we are looking for a new name! Ideas suggested so far are obs-generator and Packager-O-Matic. But we know that our community can be really creative - we got the name for our chameleon in Prague ZOO from our community - so we are asking for your help again. Please propose some names for this great tool in [9]questionare. And if you are going to openSUSE Conference or you know somebody going there and your proposal will be selected, then you you can win plush Geeko! 5. http://www.kdedevelopers.org/node/4265 6. http://www.kdedevelopers.org/blog/280 7. http://www.kdedevelopers.org/node/4177 8. http://kde-apps.org/content/show.php/kde-obs-generator?content=121094 9. http://spreadsheets.google.com/embeddedform?formkey=dHdmM1ljMDhoUFFBUDM1bjJ… Blogpost about that available at http://bit.ly/9ppw8s -- Michal HRUSECKY SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xFED656F6 19000 Praha 9 mhrusecky[at]suse.cz Czech Republic http://michal.hrusecky.net http://www.suse.cz

10 years, 8 months

[opensuse-packaging] Explaining how to fix a package for a new packager

by Andreas Jaeger

Michl and myself have cleaned up the Junior Jobs page and moved some contents to: http://en.opensuse.org/openSUSE:Fixing_bugs The contents there is not detailed enough for a new package - s/he will not know what a project is etc. Could some of you improve this page, please? Thanks, Andreas -- Andreas Jaeger, Program Manager openSUSE, aj(a){novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

10 years, 8 months

[opensuse-packaging] Why Base:System doesn't publish non-Factory packages?

by Cristian Morales Vega

The Base:System project config <build> <disable repository="openSUSE_11.2"/> <disable repository="SLE_11_SP1"/> </build> <publish> <enable repository="openSUSE_Factory" arch="i586"/> <enable repository="openSUSE_Factory" arch="x86_64"/> <disable/> </publish> is somehow unusual. It is building 11.3 packages that then are never published. It kills the "backport" use of the repository. And there is even packages, as cdrtools/cdrecord, that are only available there... so only for Factory. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

10 years, 8 months

[opensuse-packaging] susehelp... what it is?

by Cristian Morales Vega

Hi, The Stellarium package, from the Education repo, installs a file in /usr/share/susehelp/meta/Stellarium/stellarium_user_guide.desktop. First time I see that, and searching in the wiki/Google doesn't helps. If I run "susehelp" KHelpCenter is started... from where there is no signal of any stellarium docs. So... What susehelp is? How does it work? Are all packages with some kind of documentation supposed to install a file in %{_datadir}/susehelp/meta? TIA. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

10 years, 8 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging September 2010