June 2011 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Desktop-related macros for scriptlets
by Vincent Untz 20 Nov '11

20 Nov '11

Hi, Something I probably failed to document properly in 11.4 is the new macros that got introduced for desktop-related things (some of them being, arguably, GTK+-only). They were introduced to fix various issues, and move away from the SuSEconfig scripts. With rpm 4.9, we might be able to use another solution. In that case, the macros listed below will just expand to an empty string and do nothing. So it won't harm to use them either. Desktop-related macros ====================== a) Package installs a .desktop file in /usr/share/applications Macros: %desktop_database_post/%desktop_database_postun What it does: calls update-desktop-database to update a cache mapping MIME types to apps handling them. This is needed to make the desktops aware that an app can handle a MIME type. b) Package installs a MIME definition (in /usr/share/mime): Macros: %mime_database_post/%mime_database_postun What it does: calls update-mime-database to update the database containing information about all MIME definitions. c) Package installs an icon in hicolor (/usr/share/icons/hicolor): Macros: %icon_theme_cache_post/%icon_theme_cache_postun What it does: calls gtk-update-icon-cache (if existing) to update the GTK+ icon cache for hicolor, as specified by the spec. This is needed to make the icon visible to GTK+ apps. d) Package installs an icon in another icon theme (let's say "geeko" theme, /usr/share/icons/geeko) Macros: %icon_theme_cache_post geeko / %icon_theme_cache_postun geeko What it does: calls gtk-update-icon-cache (if existing) to update the GTK+ icon cache for geeko. This is needed to make the icon visible to GTK+ apps. e) Package installs a GSettings schema (in /usr/share/glib-2.0/schemas): Macros: %glib2_gsettings_schema_post/%glib2_gsettings_schema_postun %glib2_gsettings_schema_requires (similar to %py_requires) What it does: calls glib-compile-schemas to build the blob containing the data for all schemas. This is needed to have your app not crash :-) f) Package installs a gio module (in /usr/lib/gio/modules): Macros: %glib2_gio_module_post/%glib2_gio_module_postun %glib2_gio_module_requires (similar to %py_requires) What it does: calls gio-querymodules to update a cache listing all gio modules and the extension points they are using. This is needed to make the gio module known to gio. g) Package installs a gdk-pixbuf loader (in /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders): Macros: %gdk_pixbuf_loader_post/%gdk_pixbuf_loader_postun %gdk_pixbuf_loader_requires (similar to %py_requires) What it does: calls gdk-pixbuf-query-loaders to update a cache listing all gdk-pixbuf loaders and their abilities. This is needed to make the gdk-pixbuf loader known to gdk-pixbuf. h) Package installs a GTK+ (2 or 3) IM module (in /usr/lib/gtk-2.0/2.10.0/immodules or /usr/lib/gtk-3.0/3.0.0/immodules): Macros: %gtk2_immodule_post/%gtk2_immodule_postun %gtk2_immodule_requires %gtk3_immodule_post/%gtk3_immodule_postun %gtk3_immodule_requires What it does: calls gtk-query-immodules-2.0/gtk-query-immodules-3.0 to build a cache listing all IM modules and the locale/language they apply to. You obviously need to only call the gtk2/gtk3 version, depending on which version of GTK+ you target. This is needed to make the IM module known to GTK+. i) Package installs a pango module (in /usr/lib/pango/1.6.0/modules): Macros: %pango_module_post/%pango_module_postun %pango_module_requires (similar to %py_requires) What it does: calls pango-querymodules to update a cache listing all pango modules and information about what they handle. This is needed to make the module known to pango. Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- 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

5 10

[opensuse-packaging] Packaging policy for systemd .unit file
by Frederic Crozat 26 Aug '11

26 Aug '11

Hi all, as part of systemd integration in openSUSE, Michal suggested we might want to create our own openSUSE policy for packaging systemd .unit file, similar to Fedora policy http://fedoraproject.org/wiki/Packaging:Systemd , moreover the scriptlets part : http://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd However, I'm not sure we should directly add those direct call to systemctl in %post but instead, use some macros, similar to the one we have for sysvinit and / or update those macros to be systemd compliant : %stop_on_removal / %insserv_force_if_yast / %{fillup_only} / % restart_on_update / etc.. Opinions ? -- Frederic Crozat <fcrozat(a)suse.com> SUSE -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

10 35

[opensuse-packaging] HAL and related
by Ilya Chernykh 18 Jul '11

18 Jul '11

First of all I want to ask whether hal will be available under 12.1 or it is to be decided? My second question is as follows. As you know, hal is depreciated and people who prepare 12.1 want to remove dependency on hal from different packages. For instance they want to remove it from kdebase3-runtime which will be included in 12.1. But hal is necessary for normal function of KDE3 so we, who use KDE3 as a desktop want hal functions to be enabled. That's why my question. Is it possible to build a package with hal if hal is available in the repository and without hal otherwise? How to properly organize the check on whether the package exists in the repo at the buildtime? Or may be another solution based on an option constant defined in the project's properties is better? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

8 12

[opensuse-packaging] python > 2.7.1 for 11.4?
by Mathias Homann 01 Jul '11

01 Jul '11

hi there, I'm still trying to package calibre >= 0.8 for opensuse. Problems are: 1. calibre by now requires python 2.7.1 or higher but NOT python 3 2. the original author is about as cooperative and helpful as the german tax authorities on a bad day. His general approach to any kind of support question is "If you're not running the binaries from my website, go eff yourself." ...problem with that is, calibre is pretty much the only decent ebook reader management software that is platform independent. any ideas? bye, MH -- Die unaufgeforderte Zusendung einer Werbemail an Privatleute verstößt gegen §1 UWG und §823 I BGB (Beschluß des LG Berlin vom 2.8.1998 Az: 16 O 201/98). Jede kommerzielle Nutzung der übermittelten persönlichen Daten sowie deren Weitergabe an Dritte ist ausdrücklich untersagt! -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

9 16

Re: [opensuse-packaging] python > 2.7.1 for 11.4?
by Ismail Doenmez 01 Jul '11

01 Jul '11

On 06/30/2011 10:25 AM, Mathias Homann wrote: > nope, my package works fine, I just don't know if the requirement "python>= 2.7.1" on > calibre's website is just a quirk or actually justified... I think the author actually meant "Don't use Python3". So please submit updated calibre to Factory and we can move on :) -- Ismail Dönmez - openSUSE Booster SUSE LINUX Products GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 5

[opensuse-packaging] Debuginfo is not included on 11.1
by Michal Vyskocil 30 Jun '11

30 Jun '11

Hi all, I have a problem with icedtea-web build on (Evergreen) 11.1. Checking for unpackaged file(s): /usr/lib/rpm/check-files /var/tmp/icedtea-web-1.1-build error: Installed (but unpackaged) file(s) found: /usr/lib/debug/.build-id/3e/c823cdc0980d1f9ddc5ee234b19bc0565e8804 /usr/lib/debug/.build-id/3e/c823cdc0980d1f9ddc5ee234b19bc0565e8804.debug so it seems like debuginfo and debugsource packages are not included into spec file. The debug is enabled for that project (build with --debug did not change anything) and I see %suse_insert_debug_package after rpmbuild, so don't don't where is the problem. The same spec works well for 11.2+. https://build.opensuse.org/package/live_build_log?arch=i586&package=icedtea… Anyone have a hint what should be wrong? Regards Michal Vyskocil

2 2

[opensuse-packaging] pyparsing naming advice/notice
by aledr 30 Jun '11

30 Jun '11

Good day! We currently have python-parsing and python-pyparsing, and both points to pyparsing[1]. As the naming convention says and discussed before[2], seems that the name python-pyparsing is the most suited here. If there is no objections i would like to provide the needed changes (removing python-parsing, updating python-pyparsing, cleaning the spec file and setting needed Provides/Obsoletes tags). Thanks. [1]: http://pypi.python.org/pypi/pyparsing [2]: http://lists.opensuse.org/opensuse-packaging/2011-05/msg00186.html -- [ ]'s Aledr - Alexandre "OpenSource Solutions for SmallBusiness Problems" -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 3

[opensuse-packaging] Package categorization
by Ilya Chernykh 30 Jun '11

30 Jun '11

Hi! I first discussed this issue with coolo in private but possible a wider range of ideas may be beneficial. All of us know that is is sometimes confusing to find a package which belongs to your desktop environment, whether Gnome or KDE. Sometimes you have to look into package's dependencies to find out whether it is written in GTK or Qt. As the number of desktops increases, the problem only becomes worser. Currently the packages are classifies using the RPM groups. But for the most packages this groupping only reflects the package's purpose, i.e. network, game or office. This groupping is organized as a tree, and there is no possibility to add another categorization. An obvious solution is to add a desktop environment name to the package's name such as prefixing all KDE apps with "kde-" or simple "k". But this is also confusing and may require much of work as renaming is not an easy task. So are there any ideas on how to organize this better? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1

[opensuse-packaging] Strange issue...
by Nelson Marques 25 Jun '11

25 Jun '11

Hi all, I'm having a small problem with a package which giving me a huge headache to build the latest version of Banshee. This dependency was introduced in this development version (dbus-sharp-glib). The spec file[1] seems to be ok... but: 1. The log shows that either dbus-sharp-glib and dbus-sharp-glib-devel have been installed (but it's false, osc chroot and a simple query to the rpm database shows this package hasn't been installed). This makes the build fail (of course it does)... Anyone has a clear idea on how to debug this further on ? NM [1] - http://tinyurl.com/64nb9cw -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] Failed source download service in obs, but locally it works (server:php:applications horde4)
by Ralf Lang 24 Jun '11

24 Jun '11

Can anybody give me clues why the download source service in OBS server:php:applications horde4 says it cannot download (making the package broken) but locally it runs just fine against a checkout of this repo? -- Ralf Lang Linux Consultant / Developer B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] php5-pear-phpunit-PHP_CodeBrowser gives me E: file-contains-buildroot
by Ralf Lang 24 Jun '11

24 Jun '11

Hi, the following happened before with other packages (which I then packaged without fancy macros which lead to some factory complaints) but this puzzles me once again: RPMLINT report: php5-pear-phpunit-PHP_CodeBrowser.noarch: W: no-manual-page-for-binary phpcb Each executable in standard binary directories should have a man page. php5-pear-phpunit-PHP_CodeBrowser.noarch: W: files-duplicate /usr/share/php5/PEAR/data/PHP_CodeBrowser/templates/img/treeToggle- extended.png /usr/share/php5/PEAR/data/PHP_CodeBrowser/templates/js/jquery.sidebar/css/codebrowser/inject- right.png php5-pear-phpunit-PHP_CodeBrowser.noarch: E: file-contains-buildroot (Badness: 10000) /usr/share/php5/PEAR/PHP_CodeBrowser/CLIController.php php5-pear-phpunit-PHP_CodeBrowser.noarch: E: file-contains-buildroot (Badness: 10000) /usr/bin/phpcb Your file contains traces of $RPM_BUILD_ROOT. (none): E: badness 20000 exceeds threshold 1000, aborting. 2 packages and 0 specfiles checked; 2 errors, 2 warnings. The original file does not contain static paths but relative ones (../) After rpm packaging they contain static paths and generate errors Why is that? I think rpm imagines these references to runtime dependencies are compile-time objects in the buildroot. How to circumvent this? -- Ralf Lang Linux Consultant / Developer B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1

[opensuse-packaging] Advice for packaging Jinchess
by Bruno Friedmann 23 Jun '11

23 Jun '11

Hi All. I've a request to package Jin [1] which is a java frontend for online chess game servers. The project is gpl, no a problem with that. Now I've two questions, can we put and package the official .jar published by the author ? [3] contain all needed to run the game. Main deps is java (the sun one is recommended) Or to be accepted, it would be preferable to rebuild entirely from sources (the author mention that) [4] but seems to not be in favour of. In case of it can be accepted in obs. which layout in the filesystem would be the best /opt/jinchess ? Thanks for your time [1] http://www.jinchess.com home page [2] http://jin.sourceforge.net devel project [3] http://prdownloads.sourceforge.net/jin/jin-2.14.1-unix.tar.gz?download [4] http://jin.cvs.sourceforge.net/viewvc/jin/jin/release/build.xml?revision=1.… -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1

[opensuse-packaging] Policy change for factory
by Stephan Kulow 22 Jun '11

22 Jun '11

Hi, It wasn't enforced for quite a while, but now it's also gone from rpmlint so I should make more people aware: please don't recompress tarballs unless it saves >1MB for download. The original policy was necessary because SUSE shipped a DVD, but by now we ship 3 DVDs if people order source DVDs and one more doesn't really matter (as the one ordering has to pay it anyway - but such orders are still very rare ;) And if you recompress your tarball, using bz2 might not be the best choice, xz might save even more - many upstream projects change to it as default. What will become policy sooner or later is that you should not have incorrect source URLs behind Source*, so _if_ you have to recompress, don't lie in the Source line, but put the original tar as comment and use local file names in Source: Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 2

Re: [opensuse-packaging] Packaging policy for systemd .unit file - Proposal
by Frederic Crozat 21 Jun '11

21 Jun '11

Le mardi 21 juin 2011 à 09:12 +0200, Ludwig Nussel a écrit : > Frederic Crozat wrote: > > Le lundi 20 juin 2011 à 17:35 +0200, Frederic Crozat a écrit : > > > Le lundi 20 juin 2011 à 17:07 +0200, Ludwig Nussel a écrit : > > > > Frederic Crozat wrote: > > > > > [...] > > > > > Here is a proposal I plan to submit upstream if it is fine with people > > > > > here. I've reused Michael Schröder proposal from FOSDEM 2006, adapted to > > > > > systemd. > > > > > > > > > > For openSUSE, we could modify slightly this proposal to call % > > > > > fillup_and_insserv / %stop_on_removal / %restart_on_update when package > > > > > hasn't migrated to systemd (I didn't add this part to systemd proposal, > > > > > since it is distro specific) and would keep compat for current users of > > > > > service_add / service_del_preun / service_del_post > > > > > > > > > > > > > > > (proposed at fosdem 2006) > > > > > %service_add() > > > > > if [ "$1" -eq 1 ] ; then > > > > > # Initial installation > > > > > /bin/systemctl daemon-reload >/dev/null 2>&1 || : > > > > > fi > > > > > > > > > > %service_add_enabled() > > > > > if [ "$1" -eq 1 ] ; then > > > > > # Initial installation > > > > > /bin/systemctl enable %{1}.service >/dev/null 2>&1 || : > > > > > fi > > > > > > > > There are some packages that directly package the symlink in e.g. > > > > multi-user.target.wants. I suppose that shouldn't be done in favor > > > > of the macro then? > > > > > > Good question. I guess this should be discussed with upstream folks. > > > > I can see one big issue, mostly in migration : > > systemctl enable (or disable) only works if systemd is running. So, if > > you are installing a package which tries to enable a .service and if > > systemd isn't running (old init or upgrade for 11.4), systemctl won't do > > anything :( > > > "systemctl enable" could simply be replaced with a "ln -s" call I suppose. > OTOH the package could just as well simply include the symlink in > %files then. Yes, both are possible (and using "ln -s" is probably better since it will work on an upgrade). Adding to %files will ensure removing the link will be detected by rpm -V. Probably worth discussing with upstream. -- Frederic Crozat <fcrozat(a)suse.com> SUSE -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] OBS adds extra unneeded dependency to a package
by Ilya Chernykh 20 Jun '11

20 Jun '11

Hi! I am trying to package kderadiostation: https://build.opensuse.org/package/show?package=kderadiostation&project=hom… The package includes a library libkradiopart.1 But when trying to install this package zypper and Yast say that it needs libkradiopart.1 which is not provided by any package. After installation if to break the dependency, the application works well. So why OBS adds to this package a dependency on a library which is already included inside itself and does not add the same library to Provides? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 5

[opensuse-packaging] Linux shared library policy
by Dave Plater 19 Jun '11

19 Jun '11

I'm relatively new to Linux, a friend gave me, I think 5, SuSE 7.3 cds and it was the splash screen on installation showing the staff and workplace that really got to me and Win xp didn't appeal to me after 98se. The packaging list would have seen the Packman email I cced there about mjpegtools, I was very tired then now my head is clear. During my period as a maintainer I've learned quite a bit about Linux internals and rules that are applied to the way that packages are made up. One of these is the shared library policy which I've seen practical examples of it's necessity. I've also just discovered something which appears to me to be a rot setting in the Linux development world or possibly these are two exceptions, one old and one new or maybe somebody like me is needed, a fresh "outsiders perspective" from the inside. I've learned the meaning of ABI (application binary interface), it's the address offset (from the base address the binary is loaded into) of the various functions that shared libraries offer to their calling programs. Maybe it's a coincidence that I just happen to be trying to turn a new not yet submitted library package into a proper shared library, as I said I lack Linux / Unix experience so please correct any misconceptions I have, then my old enemy mjpegtools surfaces as version 2.0.0. Both these packages are the "anti openSUSE shared library naming policy" and what appears to me to be a trend to deviate from consistency in shared libraries, Mjpegtools appears, from what the developer has said (note appears means speculation not certainty) to have undergone a "not small" ABI change and that would mean a bump in the major so version, I've studied libtool and other library build aspects since making openCOLLADA and I'm not sure without digging through piles of references but I think libtool can actually detect these ABI changes. Ok the punchline is mjpegtools's libraries are named thus and have been for at least the last three versions, I've downloaded an entire history of mjpegtools source rpms to find out where this came from, mjpegtools supply a spec file which ours is based on, I only use supplied spec files for reference nowadays, after I've made an original myself in my own words so to speak : /usr/lib64/liblavfile-2.0.so.0 /usr/lib64/liblavfile-2.0.so.0.0.0 /usr/lib64/liblavjpeg-2.0.so.0 /usr/lib64/liblavjpeg-2.0.so.0.0.0 /usr/lib64/liblavplay-2.0.so.0 /usr/lib64/liblavplay-2.0.so.0.0.0 /usr/lib64/liblavrec-2.0.so.0 /usr/lib64/liblavrec-2.0.so.0.0.0 /usr/lib64/libmjpegutils-2.0.so.0 /usr/lib64/libmjpegutils-2.0.so.0.0.0 /usr/lib64/libmpeg2encpp-2.0.so.0 /usr/lib64/libmpeg2encpp-2.0.so.0.0.0 /usr/lib64/libmplex2-2.0.so.0 /usr/lib64/libmplex2-2.0.so.0.0.0 The new package I referred to earlier uses, taken from one of the three libraries, "libserd-2.0.0.so.0.0.0" ok this is easy, once I've named the libraries container package "libserd-2_0_0-0" for the "untechnical" users, this is why some packages have such strange and ugly names. The author of the new package has instructions that this naming is to ensure that his shared libraries future versions can be installed in parallel, I've read about this somewhere, oh yes the shared library policy but doesn't that refer to the digits after the ".so" oh yes that's what they're there for. (I apologise to those of you that don't like sarcasm but it's the only thing I have to anchor my sanity) Maybe this is the root cause of gstreamer never actually functioning 100%, I've switched back to obsolete backend-xine for the umpteenth time after trying gstreamer again. One thing I have a wealth of experience with is trouble shooting hardware and embedded program bugs in things designed and produced both by myself and by third parties and the worst kind of bug is the type produced by a slight intermittent clock jitter or for that matter an infrequent transient from an undefined logic state. Worst still is a part of a program that loses sync and enters address space that is undefined but by sheer luck stumbles back into sync, this is actually extreme bad luck if you are talking about life support systems or for those of you that value money over life a slot machine or vending machine. This can go unnoticed for ever or irritate the life (excuse the pun) out of the user. Such a bug can be caused by an ABI missmatch, which is the reason why I'm so vocal about software using the exact libraries it was built with, I was involved in a heated debate (wasn't really a debate because my opinion was ignored) about obsoleting a Packman devel package with a ficticious version number to prevent it from being paired with an openSUSE built library package because it introduces an element of uncertainty which to me is an undefined logic state and capable of introducing the "hidden bug" I described earlier. Is this a new trend in the Linux world? Are we eventually going to drop those pesky digits after ".so"? One thing that ms windows and osx have going for them is singularity which makes regularity easy, opensource is a collaboration of many spread out all over the world, something my generation wanted with a passion when we were young and wanted to unite the whole world in peace. This is why the shared library and naming conventions are so important, otherwise paths will deviate and confusion will creep in. As far as the new package is concerned, it's a small package and all three libraries build in one online build service page or the blink of an eye. I'm busy learning the "waf" build system, quite good library build support and quite easy to get the libraries in shape. I just have to get the named header directories to fit in and allow shared devel packages and then I will, in the best possible way (I would hate to be in the position of the debian packager who clashed with Jorge Schilling) present my patches and explain the library packaging policies of Linux distributions and how grateful I would be if could call the library containers "libserd0" and not "libserd-2_0_0-0" (sarcasm tried to creep in there). If he doesn't want to due to ego maybe, to be a good musician or for that matter outstanding at anything you have to have a large ego, I know I've got one myself, I'm a performer and I've dealt with musical performers in the past, in fact a large percentage of my acquaintances .are musicians, sound engineers or both, larger than the technical portion. I wonder why I ended up maintaining multimedia. Why has mjpegtools been allowed to abuse library naming. I filed a bug with them thinking it was a problem with the 2.0rc1 version but the developer I was communicating with didn't seem to understand what I was trying to say. I'm going to continue to work on patching mjpegtools to have correct versioning, it's good practise and the right thing to do in my mind and as I pick up experience I will patch every other package I stumble upon that has this disease and eventually be able to build libraries in my sleep, this frees time to do other things like fixing somebodies computer, which is where I'm supposed to be now. What is going on? I'm hoping that those of you who've been around Linux for a while can tell me. If the answer is "it doesn't matter" I'm going to relentlessly campaign for a serious change in the openSUSE shared library policy and silently lose faith in the future of Linux. Now go back up the page and look at the part that says "gstreamer doesn't quite work 100%". Can somebody please give me a pointer on how to detect ABI differences between library versions. I know how to look for bad linking so far, maybe these are just isolated incidents.] Thanks for your time. Dave Plater -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 7

[opensuse-packaging] What´s wrong with my spec-file?
by Kim Leyendecker 19 Jun '11

19 Jun '11

Dear packagers, I created a spec-file for my app according to this reference: http://www.rpm.org/max-rpm/s1-rpm-specref-scripts.html My app should be build with OBS, and here´s my spec-file: https://build.opensuse.org/package/view_file?file=diav.spec&package=diav-3.… The reference says, that I can use every valid sh-command, so, I used the command to decompress the source tarball and the "make" command for building from sources. Oh, I think, I forgot something like configure? What do you think? thanks in advance, -- Kim Leyendecker kdl(a)k-dl.de.vu openSUSE Ambassador, openSUSE Wiki DE Send from my notebook -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 4

[opensuse-packaging] HTTP Error 400: remote error lilo no logfile
by Per Jessen 17 Jun '11

17 Jun '11

I'm upgrading lilo - 23.2 has a fix needed for making current Factory boot. > osc results lilo . SLE_11_SP1 i586 (unpublished) U SLE_11_SP1 x86_64 (unpublished) . openSUSE_11.3 i586 (unpublished) U openSUSE_11.3 x86_64 (unpublished) . openSUSE_11.4 i586 (unpublished) . openSUSE_11.4 x86_64 (unpublished) . openSUSE_Factory i586 (unpublished) . openSUSE_Factory x86_64 (unpublished) U= unresolved. When I try to get the buildlog: ...Base:System/lilo> osc buildlog openSUSE_11.3 x86_64 Server returned an error: HTTP Error 400: remote error lilo no logfile remote error: lilo no logfile ...Base:System/lilo> osc buildlog SLE_11_SP1 x86_64 Server returned an error: HTTP Error 400: remote error lilo no logfile remote error: lilo no logfile I'm stuck. -- Per Jessen, Zürich (17.2°C) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 9

[opensuse-packaging] Pushing python 3.2 to Factory?
by Vincent Untz 17 Jun '11

17 Jun '11

Hi Jan, Is it planned to push python 3.2 to Factory soon? To be honest, I don't care much about 3.2 itself, but the package in the devel project has the nice rpm macros, and it's harder to package anything for python3 without those... Cheers, 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

7 13

[opensuse-packaging] glibc-devel-static coming to Factory
by Andreas Jaeger 17 Jun '11

17 Jun '11

I'm submitting now to Base:System a glibc with a glibc-devel-static subpackage, so for static linking you need to add to your spec files: BuildRequire: glibc-devel-static this was suggested at bnc#655261. if you see serious problems, please speak up, Andreas -- Andreas Jaeger, Program Manager openSUSE aj(a){novell.com,suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) 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

5 5

[opensuse-packaging] New package abi-compliance-checker
by Dave Plater 17 Jun '11

17 Jun '11

I've packaged the "abi-compliance-checker" as used by the Linux foundation's "LSB Infrastructure program". http://ispras.linuxfoundation.org/index.php/ABI_compliance_checker I was wondering which devel project it should live in? Sorry I forgot an important point : home:plater abi-compliance-checker is where the package is. Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 2

[opensuse-packaging] OBS corrupts tarballs on downloading
by Ilya Chernykh 17 Jun '11

17 Jun '11

Hi! It seems that OBS corrupts .tar.gz and .tar.bz2 archives when downloading. I want to look inside the source of a package to make it build. Un\fortunately I deleted the localk copy. Now I press "download" button, the file is downloaded but cannot be opened with an archiver. This happens with nearly all my packages: all files are corrupted. Sonetimes I have to search a similar tarball elsewhere on the Internet. It there a way to download the uncorrupted files? (other than make the package build successfully and extract the ressulting src.rpm) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 12

[opensuse-packaging] New package abi-compliance-checker
by Dave Plater 17 Jun '11

17 Jun '11

I've packaged the "abi-compliance-checker" as used by the Linux foundation's "LSB Infrastructure program". http://ispras.linuxfoundation.org/index.php/ABI_compliance_checker I was wondering which devel project it should live in? Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

Re: [opensuse-packaging] OBS corrupts tarballs on downloading
by Adrian Schröter 16 Jun '11

16 Jun '11

Am Thursday, 16. June 2011, 18:53:39 schrieb Ilya Chernykh: > On Thursday 16 June 2011 18:49:51 you wrote: > > > No problem with them. > > This cannot be the case. I tried different browsers (Opera, Firefox) and different archivers > (Ark, File Roller). They cannot be opened. Ah, you used the webui ... It does apply indeed another level of compression on top of it... we need to fix that... -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 2

[opensuse-packaging] Is it possible to enable or compile in AMD CodeAnalyst as part of a .rpm ?
by doiggl＠velocitynet.com.au 16 Jun '11

16 Jun '11

Hello, Is it possible to enable or compile in AMD CodeAnalyst as part of a .rpm build in a project[1] on openSUSE Build Service. A sample build .specfile listed at [2] In the specfile can the "BuildRequires: [packagename]" statement be used to include CodeAnalyst ? Example package build [3] Thanks Glenn [1]-> https://build.opensuse.org/package/show?package=smart&project=home%3Adoiggl [2]-> https://build.opensuse.org/package/view_file?file=smart.spec&package=smart&… [3]-> https://build.opensuse.org/package/live_build_log?arch=x86_64&package=smart… -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] How to resolve one package dependency problem
by Stefan Lijewski 16 Jun '11

16 Jun '11

Hi all, I have a problem with workrave (X11:Utilities) package. It requires python-cheetah for build, unfortunately there is no such package in openSUSE_11.3 (in my branch I link it against devel:languages:python). So how do link single package against another repo? Or should the link be added to the project X11:Utilities? If so, how could it be done - I'm only a maintainer of this package, is there some ''request add link'' option? regards Stefan

3 7

[opensuse-packaging] New Source Service mode actived!
by Adrian Schröter 16 Jun '11

16 Jun '11

build.opensuse.org is running now with the new source service mode. We recommend to upgrade to osc 0.132 version as available in openSUSE:Tools project if you work with source services. The difference to the old way source service were handled is that with the new mode, no "source service" commits are generated. This means, the history just contains the commits done by the user, which makes things like revision diffs much easier. The source service result is handled as an internal commit, like with source links. Builds are still done with those internal commits. A manual service run trigger is handled as commit by the user, so it is part of the history. This solves also the blocking of commits (403 errors) during a service run. Michael and Adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de

5 10

[opensuse-packaging] error: line 37: Unknown tag: Supplements: filesystem(jfs)
by Per Jessen 15 Jun '11

15 Jun '11

I need help again - I'm doing a simple upgrade of jfsutils, but it fails to build for SLES_9. I haven't touched the spec file. All hints and pointers appreciated. -- Per Jessen, Zürich (18.9°C) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 2

[opensuse-packaging] Sysconfig for tomcat6
by Andrew Wafaa 15 Jun '11

15 Jun '11

Aloha all, Sorry if this a bit of an obvious question, but for the life of me I can't find the answer. Where has /etc/sysconfig/tomcat6 gone? I am in the process of packaging a couple of tomcat based applications and I need to make some modifications to said file (memory changes etc). If it is an intentional drop, how do I do the changes that would have been done there? Many thanks, Andy -- Andrew Wafaa IRC: FunkyPenguin GPG: 0x3A36312F openSUSE: Get It, Discover It, Create It at http://www.opensuse.org -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] My rpmlint/brp series continues (Today: I: Statement might be overflowing a buffer in strncat.)
by Dimstar / Dominique Leuenberger 15 Jun '11

15 Jun '11

Hi, As some of you are certainly already aware, I am creating a series of blog posts around rpmlint errors and brp-check errors that can arise in packages. So on the weekend, Thanks to the input of Malcolm Lewis, a new post went online, which addresses this error: I: Statement might be overflowing a buffer in strncat. The b log post with explanation why it happens and how to solve it can be found at http://dominique.leuenberger.net/blog/?p=189 Hope it helps you all out. Dominique PS: The offer still stands of course: whichever brp/lint you struggle with, just send me a message and I will try to come up with a post about it. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1

[opensuse-packaging] preprocessor sanity checks ?
by Cristian Rodríguez 15 Jun '11

15 Jun '11

Hi: Is there any way to enable some kind of preprocessor basic sanity checks... ? found a package that used #defina instead of #define .. and no warning was emitted .. hints ? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

8 13

[opensuse-packaging] SLES_9 - Server returned an error: HTTP Error 404: Not Found
by Per Jessen 15 Jun '11

15 Jun '11

How should I interpret this: osc results SLES_9 x86_64 Server returned an error: HTTP Error 404: Not Found SLES_9 I see this for SLES_9 i586 and x86_64. -- Per Jessen, Zürich (16.2°C) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 8

[opensuse-packaging] [reminder] openSUSE 12.1 Milestone 2 is next week
by openSUSE Roadmap Reminder 15 Jun '11

15 Jun '11

Hello all, openSUSE 12.1 Milestone 2 will be released next week, on Wednesday 22 June 2011. 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 For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] Watch out configure scripts detecting kernel version
by Cristian Rodríguez 14 Jun '11

14 Jun '11

Hi: Just a heads-up, I'm already seeing configure scripts who do not handle new linux kernel version scheme, in particular ones that assume that linux version starts with number 2. Next time you build your packages ensure there is no buggy regular expression checking the value of uname -r. Cheers. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] unresolvable confusion
by Robert Schweikert 14 Jun '11

14 Jun '11

Hi, Could someone take a look at https://build.opensuse.org/project/show?project=Virtualization%3ACloud%3AOp… and help me figure out why for the SLES 11 SP1 build pwgen shows up as unresolvable? I added pwgen to the project via _aggregate yesterday and https://build.opensuse.org/package/show?package=pwgen&project=Virtualizatio… shows that it built successfully for SLES 11 SP1. pwgen is part of the openSUSE distributions, thus it is disabled for those repositories. Shouldn't pwgen be picked up for the SLES 11 SP1 build. Confused, help is appreciated. Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rschweikert(a)novell.com rschweikert(a)ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] Re: [packman] mjpegtools 2.0.0-1
by Dave Plater 12 Jun '11

12 Jun '11

On 06/12/2011 02:38 PM, Manfred Tremmel wrote: > Am Sonntag, 12. Juni 2011 schrieb Dave Plater: >> On 06/09/2011 08:15 PM, Manfred Tremmel wrote: >>> Am Donnerstag, 9. Juni 2011 schrieb yahoo-pier_andreit: >>>> from tumbleweed I'm trying to update to mjpegtools 2.0.0-1 from >>>> 1.9.0.0 but yast shows me this conflicts: >>> I'll take a look on it this weekend. If I'm not able to fix the >>> gstreamer incompatibility with mjpegtools 2.0.0 I'll add a >>> mjpegtools compatibility package with the old libs. >> The developers of mjpegtools are misguided about library versioning. > So it is. > >> I attempted to update openSUSE multimedia:libs to 2.0.0rc1 last >> December and eventually reverted to the existing 1.9.0. The >> libraries are at major version 2 and they end up like this >> "liblavfile-2.0.so.0.0.0" but the unversioned devel link is >> "liblavfile.so". There's no logic here at all, if the developer >> wanted parallel installable libraries why not match the devel parts >> too and install the headers in versioned directories. To cut a long >> story short I filed an upstream bug and started to fix the library >> build to give proper so numbers because 2.0.0rc1 broke gstreamer in >> factory and because there was plenty of other things to update and >> fix for the looming release of 11.4, I reverted to the old version >> and gstreamer was happy. If you patch gstreamer to work with a > Sounds good. > >> broken package it will complicate matters more, rather revert to >> 1.9.0 and help to fix the real problem with 2.0.0.. When I saw >> Packman had 2.0.0 I thought that it would have a fixed build, >> unfortunately not. > I've done a quick and dirty solution at packman now. I've splitted out > the libs into a mjpegtools-lib package and readded mjpegtools 1.9.0 as > mjpegtools19. Both library packages (mjpegtools-lib and mjpegtools19- > lib) can be installed without conflicts. Packagis having problems to > build against mjpegtools 2.0.0 can use BuildRequires: mjpegtools19-devel > >> As all this happened at the beginning of >> February I can't be sure but AFAIR I had gone as far as tracing the >> gstreamer problem to the lib builds in mjpegtools, I've started to >> pick at mjpegtools again and it will become priority one after I've >> finished a few other packages. I have to cope with openSUSE library >> policy and I'm not sure what the eventual outcome of library >> developers making their own method of shared library parallel >> installation, I'm working on a new package where the dev has done >> the same as this but it's new and not as important as mjpegtools >> which can silently break plenty of packages and render multimedia >> unusable. > Thanks for your engagemnet. > >> I'm about too collapse into bed, coffee doesn't work anymore so >> please ask for clarification on anything I've said that sounds >> insulting because that's not my intention. I'm cc ing >> opensuse-packaging for comments and guidance. > Sorry I can't do much on this topic. My skills in c programming are not > so great and I've to big projects @work, so my sparetime is extremely > limited. > The move to get openSUSE multimedia involved in Packman can only reduce your workload. Sorry I can't say much I've got things to do, read the email I cced to the Packman list when you've got time it's long. Regards Dave -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] Re: [packman] mjpegtools 2.0.0-1
by Dave Plater 12 Jun '11

12 Jun '11

On 06/09/2011 08:15 PM, Manfred Tremmel wrote: > Am Donnerstag, 9. Juni 2011 schrieb yahoo-pier_andreit: >> from tumbleweed I'm trying to update to mjpegtools 2.0.0-1 from >> 1.9.0.0 but yast shows me this conflicts: > I'll take a look on it this weekend. If I'm not able to fix the > gstreamer incompatibility with mjpegtools 2.0.0 I'll add a mjpegtools > compatibility package with the old libs. > > The developers of mjpegtools are misguided about library versioning. I attempted to update openSUSE multimedia:libs to 2.0.0rc1 last December and eventually reverted to the existing 1.9.0. The libraries are at major version 2 and they end up like this "liblavfile-2.0.so.0.0.0" but the unversioned devel link is "liblavfile.so". There's no logic here at all, if the developer wanted parallel installable libraries why not match the devel parts too and install the headers in versioned directories. To cut a long story short I filed an upstream bug and started to fix the library build to give proper so numbers because 2.0.0rc1 broke gstreamer in factory and because there was plenty of other things to update and fix for the looming release of 11.4, I reverted to the old version and gstreamer was happy. If you patch gstreamer to work with a broken package it will complicate matters more, rather revert to 1.9.0 and help to fix the real problem with 2.0.0.. When I saw Packman had 2.0.0 I thought that it would have a fixed build, unfortunately not. As all this happened at the beginning of February I can't be sure but AFAIR I had gone as far as tracing the gstreamer problem to the lib builds in mjpegtools, I've started to pick at mjpegtools again and it will become priority one after I've finished a few other packages. I have to cope with openSUSE library policy and I'm not sure what the eventual outcome of library developers making their own method of shared library parallel installation, I'm working on a new package where the dev has done the same as this but it's new and not as important as mjpegtools which can silently break plenty of packages and render multimedia unusable. I'm about too collapse into bed, coffee doesn't work anymore so please ask for clarification on anything I've said that sounds insulting because that's not my intention. I'm cc ing opensuse-packaging for comments and guidance. Regards Dave Plater Maintainer openSUSE multimedia libs and apps Packman user name davepl openSUSE user name plater -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] RFC: best way to deal with unresolvable state created by automatic Requires (for gobject-introspection)
by Vincent Untz 10 Jun '11

10 Jun '11

Hi, Thanks to Dominique, packages using gobject-introspection how have automatic typelib() Requires/Provides. For those who don't know, the introspection support is a way to easily use C libraries from the GNOME stack, from various other languages (js, python, vala, etc.). In concrete terms, libgtk-2_0-0 ships this file /usr/lib/girepository-1.0/Gtk-2.0.typelib and gets a typelib(Gtk) = 2.0 Provides. Similarly, libgtk-3-0 will get a typelib(Gtk) = 3.0 Provides. However, we're stuck with one issue: for packages depending on a typelib file, the Requires we get are not necessarily versioned, because there is not necessarily the information for which version to require in the code. And so we end up with this in the build service: "have choice for typelib(Gtk) needed by python-gobject: libgtk-2_0-0 libgtk-3-0" This is an issue in the build service, and it's also something that zypper would have to deal with (although it might just take the provider with the bigger version?). I'd like to hear what people think is the best way to solve this. The possible options we had so far were: 1) Explicitly require libgtk-3-0 so that there would be a provider anyway 2) Have a "Prefer: libgtk-3-0" in the prjconf (but that wouldn't help zypper) 3) Create some kind of manifest file for the package, where we tell which version of typelib(Gtk) is required, and use this data when generating the Requires. Thanks, 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

2 1

[opensuse-packaging] manual page warning for factory builds
by Togan Muftuoglu 10 Jun '11

10 Jun '11

Hi When building packages locally with osc or in the OBS for factory RPMLINT reports the following for the man pages "manual-page-warning can't find macro file `deunicode.tmac' This man page may contain problems that can cause it not to be formatted as intended." The package builds fine for openSUSE_11.3 and openSUSE_11.4 Any ideas ? Thanks Togan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1

[opensuse-packaging] Chromium build problems on openSUSE with make 3.82
by Sankar P 10 Jun '11

10 Jun '11

Hi, I am trying to build chromium from the sources on openSUSE. During this, for any change I make in any file, all the sources of all the modules (dependents etc.) were getting recompiled. So, for a simple "cout " addition, it took about 3 hours to build. I asked for help in the chromium list and found that this issue has happened in fedora and openSUSE with the make version 3.82 and works fine in make version 3.81 Related bug ids: http://code.google.com/p/gyp/issues/detail?id=197 http://code.google.com/p/chromium/issues/detail?id=64703 Can someone help find out why this issue is happening and what is the right fix for this ? Should I file a regression bug on make 3.82 on openSUSE ? I did a google search and dug thru' man pages but with my inadequate packaging knowledge could not find out the right solution. Any help is appreciated. thanks. -- Sankar P http://psankar.blogspot.com -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 6

[opensuse-packaging] New RPM dependency generator problem?
by Cristian Morales Vega 03 Jun '11

03 Jun '11

Can someone explain the (lack of) "requirements" in this package: https://build.opensuse.org/package/binary?arch=x86_64&filename=libpt2_6_7-2… ? I suppose it's related to the new dependency generator, but... -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 4

[opensuse-packaging] Can I do 2 local "osc build" processes at the same time?
by Greg Freemyer 03 Jun '11

03 Jun '11

All, I was doing a local kernel build in support of the Evergreen project. It seemed to be moving along, but in another konsole I started a obs build on a small package. The kernel build seemed to die at that point. I did both a "osc build", and a "osc build --clean" in the small project, so either one or both of those may of been the culprit. Regardless, is there a safe way to do 2 simultaneous local builds? Thanks Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

6 6

[opensuse-packaging] Can packages in the 11.4 standard or update repos build against tumbleweed?
by Dave Plater 03 Jun '11

03 Jun '11

Can packages in 11.4 standard or update repositories build against packages provided in the tumbleweed update repository.? I've filed bnc#696826 about 11.4's lv2core-devel's lv2config being unable to function due to a lack of package python-redland. The LV2 plugin system cannot be used at all if the package can't build against lv2core and slv2, I submitted new packages lv2core, slv2 and an updated redland package that included the python bindings before 11.4's release, lv2core is in the 11.4 distribution but slv2 is still in review, here is it's history : 62079 State:declined By:autobuild When:2011-02-18T16:30:51 submit: multimedia:libs/slv2 -> openSUSE:Factory note: obsoleted by submitreq 62078 From: plater(new) Descr: Removed conflict for libslv2-8 62078 State:review By:coolo When:2011-03-28T16:14:46 submit: multimedia:libs/slv2 -> openSUSE:Factory From: plater(new) -> saschpe(review) Descr: Removed conflict for libslv2-8 60049 State:declined By:autobuild When:2011-02-18T16:30:43 submit: multimedia:libs/slv2 -> openSUSE:Factory From: plater(new) Descr: Add slv2-0.6.6-licencefix.patch to remove file with conflicting GPLv2 statement in the header. See bnc#669117 and slv upstream drobillad #630 59638 State:declined By:autobuild When:2011-02-04T17:25:01 submit: multimedia:libs/slv2 -> openSUSE:Factory From: plater(new) Descr: New package slv2 is a library to make the use of LV2 plugins as simple as possible for applications.slv2 is free software (GPL v2 or later) written in C99 using the Redland RDF toolkit, and is known to work on GNU/Linux and Mac OS X. This package is the other part of the slv2 lv2core needed for openSUSE packages to use the LV2 plugin system and compliments submit request sr#59624 the home url for this package is http://drobilla.net/software/slv2/ apart from the url and licence all of the other relevant information is contained in submit request id 59624 and this is sr#62078 the last request which is still open : Request #62078: submit: multimedia:libs/slv2(r5) -> openSUSE:Factory/slv2 Message: Removed conflict for libslv2-8 State: review 2011-03-28T16:14:46 coolo Comment: run checker Review: new darix None None None Please decide accepted None factory-auto 2011-03-29T16:16:48 coolo Builds for all Factory repos found Output of check script (non-fatal): History: review 2011-03-18T10:39:07 saschpe new 2011-02-18T16:18:50 plater This last request effectively blocks slv from even going into factory. There was a comment made in a reply during one of my many emails pleading for slv2 to be accepted that it was a duplicate of a Packman package and I replied that it's purpose was to enable multimedia applications to build with support for LV2 plugins and openSUSE packages cannot build against Packman packages. I'm busy updating qtractor from 0.7.8 to 0.7.9 the earlier version would have been in 11.4 had slv2 been present and now it seems that version 0.7.9 is also going to be blocked. Reference threads : http://lists.opensuse.org/opensuse-factory/2011-02/msg00678.html http://lists.opensuse.org/opensuse-factory/2011-02/msg00004.html http://lists.opensuse.org/opensuse-factory/2011-01/msg00377.html I originally created the lv2core and slv2 packages when a user requested LV2 plugin support for ardour which isn't in the main distribution but he was happy with the result and this verifies that there isn't anything wrong with the package. Maybe I violated an openSUSE rule inadvertently but if nobody explains what it was I may do it again. I'm passionate about openSUSE multimedia and I feel that it presents an important face of openSUSE. Regards Dave Plater -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 4

[opensuse-packaging] How to setup 7zip-packed source?
by Kyrill Detinov 02 Jun '11

02 Jun '11

Thursday 02 June 2011 Hello. I have 7zip-packed source file. Now it works for me: ... Requires(pre): p7zip ... %prep 7za x -o%{_builddir} %{_sourcedir}/%{name}-%{version}-src.7z %setup -DTqn %{name}-%{version}-src ... Is this correct? -- WBR Kyrill -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0