October 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] cups: upgrade from 1.4.x to version 1.5.0
by Johannes Meixner 04 Nov '11

04 Nov '11

Hello, in the OBS project "Printing" there is now CUPS version 1.5.0 for various openSUSE and SLE versions. It may take a few hours until RPMs appear under http://download.opensuse.org/repositories/Printing/ For openSUSE:Factory there is submitrequest 86888 pending to upgrade CUPS in openSUSE:Factory to version 1.5.0. See https://bugzilla.novell.com/show_bug.cgi?id=722057 for background information. Basically: According to http://www.cups.org/roadmap.php CUPS 1.4.x is no longer maintained by upstream which is the reason to upgrade to version 1.5.0. Backward incompatible changes: * The main header cups/cups.h no longer includes the PPD header cups/ppd.h which may require code changes to applications. * CUPS no longer supports the old ~/.cupsrc or ~/.lpoptions files from CUPS 1.1.x. The ~/.cups/client.conf and ~/.cups/lpoptions files that were introduced in CUPS 1.2 must now be used. * The scheduler now requires that filters and backends have group write permissions disabled (security). This means: Compiling software which use the CUPS PPD API but do not explicitly include the <cups/ppd.h> header file would fail. This backward-incompatible change should show up during package build in OBS so that affected packages can be fixed. In old-style applications which still use ~/.cupsrc and ~/.lpoptions user default settings would no longer work. I have no idea how many such old-style applications may exits. Printer driver packages which install their own filters and backends with group write permissions would no longer work. I will check those packages in OBS. For third party printer drivers from manufacturers I cannot do anything (they may no longer work without manual adjustment). I appreciate any testing and feedback regarding CUPS 1.5.0. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 25

[opensuse-packaging] KDE3 pattern
by Ilya Chernykh 31 Oct '11

31 Oct '11

Hi, Stephan! I know you had some points against creating a new pattern for KDE3, especially concerning the pattern's name. But the users seem to complain about that installing KDE3 without pattern is difficult: http://forums.opensuse.org/english/get-technical-help-here/pre-release-beta… Also it seems installing not fully complete set of packages may lead the users to believe that something is broken or incomplete (like in the linked case where the user thought kde3-ksnapshot was not included in Factory while actually it belongs to kdegraphics3). I have created a bugreport concerning the KDE3 pattern with a package list: https://bugzilla.novell.com/show_bug.cgi?id=721640 I hope you can revisit the issue before the release date. The name of the pattern is not that important actually, I just hope it would not confuse the users. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] Package boinc-client for sale
by Sascha Manns 27 Oct '11

27 Oct '11

Hello mates, sadly i haven't enough time to provide future update and versions of boinc-client. ATM it is placed there: https://build.opensuse.org/package/show?package=boinc-client&project=network We have open Bugs in Bugzilla: https://bugzilla.novell.com/show_bug.cgi?id=566289 https://bugzilla.novell.com/show_bug.cgi?id=689499 Maybe anyone would like to pick up the maintainance for this package? -- Sincerely yours Sascha Manns Community & Support Agent open-slx GmbH Web: http://community.open-slx.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] [reminder] openSUSE 12.1 RC 2 is next week
by openSUSE Roadmap Reminder 27 Oct '11

27 Oct '11

Hello all, openSUSE 12.1 RC 2 will be released next week, on Thursday 03 November 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 To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 5

[opensuse-packaging] Help with Mayavi
by Filipe Pires Alvarenga Fernandes 26 Oct '11

26 Oct '11

Hello, Recently vtk from the science repo was updated to version 5.8 and that broke my build of Mayavi: Building TVTK classes...: cannot connect to X server error: Bad exit status from /var/tmp/rpm-tmp.mkotMT (%build) Full log: https://build.opensuse.org/package/live_build_log?arch=i586&package=python-… If I understood it correctly I need to start an X-server, I tried the instruction I found here: http://en.opensuse.org/openSUSE:Build_Service_Tips_and_Tricks However, it did not work as expected. I guess that it might be a simple thing, but I'm still a beginner at "packaging". Can anyone help me understand what I should do ? Thank you for the attention, Filipe. -- 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] Packaging Javascript libraries as part of web-applications
by Johannes Weberhofer 26 Oct '11

26 Oct '11

Hi! I have a general question regarding packaging of Javascript libraries as parts of application: Eg. phpmyadmin contains jquery in a specific version. Because phpmyadmin is GPL2+, jquery must also be licensed under the GPL (which is possible). licensing under the GPL implies, the source-code is made available with the package. Unfortunately, only the compressed code is packed with the phpmyadmin sources. The only "clean" way - in my opinion - is to package those libraries in seperate package, which makes packaging quite complex. I could think of packaging the libs under /use/share/js/libraryname/version.release in packages called libraryVersion.release and package those seperately. Of course, packaging is getting very complex... What do you suggest, regarding this problem? 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

1 0

[opensuse-packaging] skip subpackages
by Ilya Chernykh 22 Oct '11

22 Oct '11

Hi! I want to skip all subpackages in a very fat package. How can I do this quickly, and, desirably, with a condition depending on a set variable? I think about the file list: to prevent failure I would have to either add %exclude to all non-needed files (tens of them) or delete them after installation. Is there another way? There is no option in configure script to skip building the subpackages. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 8

[opensuse-packaging] Debian packaging?
by Uwe Drechsel 22 Oct '11

22 Oct '11

Hi, yes, I know, this list is named differently. Still I'm trying to build a .deb in BS from https://build.opensuse.org/package/show?package=vym&project=home%3Ainsilmar… Installing in Ubuntu 11.10 shows, that all files go to /share/vym and /share/doc/packages/vym while they should go to /usr/share/vym/ and /usr/share/doc/packages/vym Any hints what's missing? Is this a problem in my debian.rules or in BuildService? Thanks Uwe -- mathematician, n: Someone who believes imaginary things appear right before your i's. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] openSUSE:12.1 is split from factory
by Stephan Kulow 21 Oct '11

21 Oct '11

Hi, Before you find it during some surfing around on build.opensuse.org, I better tell you: we copied openSUSE:12.1 from factory now. This means we will build RC2 from there. This also means I will move my focus to that new project and leave factory for a while building as it is. Please submit your 12.1 fixes to openSUSE:Factory as usual, I will review them and forward to 12.1 as I see important bugs fixed. The rest can stay in Factory for 12.2. Reminder: checkin deadline for RC2 is october 28th. Afterwards is a long weekend for many in Bavaria. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] opensuse fixes/equivalents fixes for 'nothing provides freetype-devel, nothing provides /usr/lib64/crt1.o, nothing provides glibc-static'
by doiggl＠velocitynet.com.au 20 Oct '11

20 Oct '11

Hello, What do I alter in a spec file to resolve this message in a spec file, need opensuse equivalents ? nothing provides freetype-devel, nothing provides /usr/lib64/crt1.o, nothing provides glibc-static Thanks Glenn Source https://build.opensuse.org/package/view_file?file=grub2.spec&package=grub2&… -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 4

[opensuse-packaging] Licensing question about libraries
by Greg Freemyer 20 Oct '11

20 Oct '11

All, Can all openSUSE approved licenses link together assuming a library has one license and the caller another? == My specific case is a library with "BSD with Advertizing" being called by an app with a CPL and IBM License. Thanks Greg -- 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] review split glibc-devel-static
by Rüdiger Meier 19 Oct '11

19 Oct '11

Hi, Even I've tripped over the separated static libc into the new package glibc-devel-static. reference http://old.nabble.com/glibc-devel-static-coming-to-Factory-tt31860569.html#… I think the split itself is a good idea but is the package name well choosen? Fedora/CentOS/RedHat have made the split into glibc-static Mandriva calls it glibc-static-devel Now suse invents glibc-devel-static IMO this is a pain for people trying to make portable spec files depending on static libc. So if possible I would suggest to follow Fedora (because they did that already years ago) and rename it to glibc-static too. cu, Rudi -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 3

[opensuse-packaging] Package fails at i586 but builds well at x86-64
by Ilya Chernykh 19 Oct '11

19 Oct '11

Hi! This package https://build.opensuse.org/package/show?package=tradeequip-drv&project=KDE%… fails for i586 with a very strange error when processing file list. The same package built well in another repository. I just wonder how this can happen? -- 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] What does it mean?
by Ilya Chernykh 18 Oct '11

18 Oct '11

-- Performing Test C_HAVE_PIC - Failed -- Performing Test CXX_HAVE_PIC -- Performing Test CXX_HAVE_PIC - Success CMake Error at CMakeLists.txt:123 (MESSAGE): shared library support is missing This happens only in Factory. The package is https://build.opensuse.org/package/live_build_log?arch=i586&package=kde3-kw… -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 6

[opensuse-packaging] Problem with PyV8 packaging
by Michal Vyskocil 14 Oct '11

14 Oct '11

Hi, I have packaged the PyV8 [1] as python-pyv8 [2]. It is a python wrapper for Google's V8 engine. To be sane and allow the future commit into the openSUSE Factory, I built the svn version (r414 [2]), which can be built against v8 3.4.6.1 we have in Factory. As the v8's API is changing very fast and PyV8 did not have any release during more than a year, one can only find a working version from svn, as the API changes are reflected, just not released. But there is a big issue atm - PyV8 needs to have RTTI and Exceptions enabled in libv8.so, which is disabled by default. From that reason my current incarnation rebuilds v8 from scratch without --fno-rtti and exceptions and the _PyV8.so is statically linked with libv8.so. So this has to be solved somehow. I see following three opinions sorted from the less effort (at least for me ;-) to the most one 1.) build system wide v8 with exceptions and rtti 2.) create v8-source package and build python-pyv8 agains it 3.) build it with rtti and exceptions and install it to different directory and use rpath during linking The most prefferable would be 1.), just I don't know if this version of v8 will be compatible with Chromium. Number 2.) can be achieved easyly, but solves the problem only partially. Number 3.) seems to be the most complex solution, but expect more work from us. What do you thinkg about? [1] http://code.google.com/p/pyv8/ [2] https://build.opensuse.org/package/show?package=python-pyv8&project=home%3A… [3] http://code.google.com/p/pyv8/source/detail?r=414a [4] http://code.google.com/p/pyv8/wiki/HowToBuild Regards Michal Vyskocil -- 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] Re: [opensuse] installing optimized packages like Gentoo
by Cristian Rodríguez 14 Oct '11

14 Oct '11

On 02/10/11 14:37, Carlos Alberto Gueto Tettay wrote: > Hi everybody, > > Gentoo linux is an special distro that can be automatically optimized and it offers an extreme performance according to machine specifications. > There is no such magical thing, although some very specific programs like multimedia libraries may run faster with -O3 (and the newer -Ofast) other programs do in fact run slower or produce huge bloated binaries, other optimizations are unsafe and produce broken code. In case you want to help to make binaries faster, the road ahead is awfully complicated, but Im gonna give you some hints on what to look for to start - There are many packages that for historical reasons or old bugs are built with -fno-strict-aliasing, it is needed that someone looks into them to see if such flag is really needed nowdays. - There are other packages that are compiled with less than standard optimization due to old bugs in the compiler, those need to be verified as well. - If you want faster application load times, there are a _lot_ of C and C++ libraries that may be able to load faster if someone takes the time to add "visibility" support to them see: http://gcc.gnu.org/wiki/Visibility for C++ libraries, you might just pass -fvisibility-inlines-hidden to the compiler and then test its functionality. - If you have debugging skills, you can profile particular software in order to find bottlenecks, this particular task is very hard and sometimes require profound knowledge of the language being used as well of the compiler/interpreter/OS. good luck :-D Cheers. -- 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] Adding a new distro as a build target
by Nasa 13 Oct '11

13 Oct '11

Hi, as the subject line suggest, I would like to build packages against a target that is presently not listed on OBS. Specifically, I would like to add Bodhi (which is a decendant of Ubuntu 10.04 and Enlightenment). The wiki talks about how to add a target on a local machine, but not the main server. I also assume one can create a new repo by adding a subproject and adding packages for the new distro there... But I was hoping for a simplier solution. Thanks in advance, Nasa -- 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] [reminder] openSUSE 12.1 RC 1 is next week
by openSUSE Roadmap Reminder 12 Oct '11

12 Oct '11

Hello all, openSUSE 12.1 RC 1 will be released next week, on Friday 21 October 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 To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] [devel:libs:c_c++] quvi-0.4.0
by David Haller 11 Oct '11

11 Oct '11

Hello, can any maintainers of devel:libraries:c_c++/quvi have a look over my updated quvi package (esp. the .spec and -rpmlintrc), as upstream has split up the package ... I'm quite unsure if packaging it like that is ok (-> see rpmlintrc). https://build.opensuse.org/package/files?package=quvi&project=home%3Adnh%3A… TIA, -dnh -- RAID: One more disk fails than can be recovered by the redundancy. -- Andreas Dau -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 2

[opensuse-packaging] Obsoletes < vs Obsoletes <=
by Jan Engelhardt 10 Oct '11

10 Oct '11

Hi, in discussions etc. people say one should use < in the obsoletes/provides relation: Obsoletes: foo < %version Provides: foo = %version However this does not reliably "work" when %version did not change across the change (e.g. changing EV from foo-1.0 towards libfoo-1.0), the old foo-1.0 will stick around because it is not obsoleted by libfoo-1.0. So "foo < %version" is actually bogus and should be either <=, or actually foo < %version-%release. <= makes technology unhappy ("package obsoletes itself"), so that leaves us with the %version-%release approach. Does baselibs.conf support obsoletes "foo < <version>-<release>" actually? -- 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] A couple fedora questions
by Greg Freemyer 07 Oct '11

07 Oct '11

All, I've got a normal package and a KMP I want to also build for Fedora. (The only 2 packages in home:next4:ext4-snapshots). The normal package is failing because I'm using the "Recommends" tag in my opensuse specfile. (I have it wrapped in %if suse currently). Is there a Fedora equivalent? The KMP is failing because I have %kernel_module_package in that specfile. Again, is there a Fedora equivalent? Thanks Greg -- 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] RPM scriptlets -e argument confusion
by Johannes Meixner 07 Oct '11

07 Oct '11

Hello, http://en.opensuse.org/openSUSE:Packaging_scriptlet_snippets reads ----------------------------------------------------------------------- ... rpm in its default configuration does not at the moment execute shell scriptlets with the -e argument ... ----------------------------------------------------------------------- Therefore this test scriptlet should work: ----------------------------------------------------------------------- %pre # Test if RPM executes shell scriptlets without the -e argument # (i.e. do not exit if a command exits with a non-zero status). # Without the -e argument it would not exit at the next command... cat doesnotexist 1>/dev/null 2>/tmp/testRPMpre.stderr # ...and therefore it would run this command: echo "RPM pre scriptlet runs without -e" 1>/tmp/testRPMpre.stdout ----------------------------------------------------------------------- But a package with such a scriptlet fails during build with: ----------------------------------------------------------------------- running 06-check-installtest ... testing for pre/postinstall scripts that are not idempotent preinstall script of <package>.rpm failed ----------------------------------------------------------------------- The reason is that the post-build-checks RPM in the build system contains a usr/lib/build/checks/06-check-installtest script which runs each RPM scriptlet with explicit -e argument setting via ----------------------------------------------------------------------- SCRIPT_ARG=-e ... chroot $BUILD_ROOT sh $SCRIPT_ARG /.build_patchrpmcheck_scr ... ----------------------------------------------------------------------- where /.build_patchrpmcheck_scr is a copy of the RPM scriptlet. With "#!BuildIgnore: post-build-checks" I enforced to skip all post build checks to get the package built. And now - surprise! - surprise! - I can install the built package without an error using plain "rpm" which shows that rpm does not use the -e argument - at least not the rpm on my workstation. I wonder why then the post build checks use the -e argument? I would expect that the post build checks emulate what rpm does (i.e. what happens on the user's system who installs it) and not exaggerate. >From my point of view using the -e argument for the post build checks does not provide better RPM scriplets. It only enforces packagers to add dumb "|| true" to all statements: ----------------------------------------------------------------------- %pre do_crap || true do_more_crap || true mess_up_everything || true ----------------------------------------------------------------------- Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer -- 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] [reminder] openSUSE 12.1 RC 1 is next week
by openSUSE Roadmap Reminder 05 Oct '11

05 Oct '11

Hello all, openSUSE 12.1 RC 1 will be released next week, on Thursday 13 October 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

2 1

[opensuse-packaging] another KMP questions
by Greg Freemyer 03 Oct '11

03 Oct '11

All, I just test installed the first KMP I've been part of building: The project is: home:next4:ext4-snapshots, and the package is: ext4dev-snapshots in that project. It installs via zypper in ext4dev-kmp-desktop. When I look in /lib/modules, it gets installed to: /lib/modules/3.1.0-rc7-3-desktop/ But the kernel is 3.1.0-rc7-5-desktop and the other modules are in /lib/modules/3.1.0-rc7-5-desktop/. (note -3 vs. -5 above). Is that okay, or do I need to do something to get the kernel and KMP version number to be exactly the same? Thanks Greg -- Greg Freemyer Head of EDD Tape Extraction and Processing team Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer CNN/TruTV Aired Forensic Imaging Demo - http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrie… The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 1

[opensuse-packaging] Need help with a kernel module - depends on libc.so.6 ??
by Greg Freemyer 03 Oct '11

03 Oct '11

All, I'm trying to get a KMP to work against current factory / kernel:HEAD (3.1-rc7) The project is: home:next4:ext4-snapshots And the package is: ext4dev-snapshots in that project. It builds fine, but when I go to install it I get: ======================== #### YaST2 conflicts list - generated 2011-10-03 13:39:52 #### nothing provides libc.so.6(GLIBC_2.14)(64bit) needed by ext4dev_snapshots-1.0.13-15.1.x86_64 [ ] do not install ext4dev_snapshots-1.0.13-15.1.x86_64 [ ] break ext4dev_snapshots by ignoring some of its dependencies ======================== I'm running tumbleweed, but I thought a KMP would be distro neutral. Thanks Greg -- 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] build-compare problem?
by Stefan Seyfried 01 Oct '11

01 Oct '11

Hi all, I'm trying to get the list of unnecessary republishings in my repos down, even in the "fun" repos. One problem I was not able to solve is: seife@susi:~/buildservice/arduino/avr-libc> osc bl openSUSE_Factory x86_64|tail -25 +++ /tmp/tmp.ilF7FI2UUs 2011-09-29 12:41:38.176000001 +0000 @@ -110,9 +110,9 @@ 000006d0 00 00 00 00 00 00 00 00 44 00 dd 00 00 00 00 00 |........D.......| 000006e0 00 00 00 00 44 00 df 00 00 00 00 00 00 00 00 00 |....D...........| 000006f0 44 00 24 01 00 00 00 00 00 00 00 00 44 00 25 01 |D.$.........D.%.| -00000700 00 00 00 00 00 2f 74 6d 70 2f 63 63 56 6a 77 49 |...../tmp/ccVjwI| -00000710 79 38 2e 73 00 2f 74 6d 70 2f 63 63 56 6a 77 49 |y8.s./tmp/ccVjwI| -00000720 79 38 2e 73 00 76 6f 69 64 3a 74 31 3d 31 00 5f |y8.s.void:t1=1._| +00000700 00 00 00 00 00 2f 74 6d 70 2f 63 63 6a 46 54 74 |...../tmp/ccjFTt| +00000710 5a 43 2e 73 00 2f 74 6d 70 2f 63 63 6a 46 54 74 |ZC.s./tmp/ccjFTt| +00000720 5a 43 2e 73 00 76 6f 69 64 3a 74 31 3d 31 00 5f |ZC.s.void:t1=1._| 00000730 5f 76 65 63 74 6f 72 73 3a 46 31 00 2e 2e 2f 2e |_vectors:F1.../.| 00000740 2e 2f 2e 2e 2f 2e 2e 2f 63 72 74 31 2f 67 63 72 |./../../crt1/gcr| 00000750 74 31 2e 53 00 5f 5f 62 61 64 5f 69 6e 74 65 72 |t1.S.__bad_inter| ... saving built packages /usr/src/packages/RPMS/noarch/avr-libc-1.7.1-3.9.noarch.rpm /usr/src/packages/SRPMS/avr-libc-1.7.1-3.9.src.rpm build34 finished "build avr-libc.spec" at Thu Sep 29 12:41:38 UTC 2011. [ 269.320282] SysRq : Power Off [ 271.127880] Power down. build: extracting built packages... avr-libc-1.7.1-3.9.noarch.rpm avr-libc-1.7.1-3.9.src.rpm This is in home:seife:arduino, my private "develproject" for CT:avr, the package avr-libc is linked from CrossToolchain:avr. It looks like the problem is some temporary filename from compilation. Anything I can do about this? Or can this be whitelisted in build-compare? Best regards, seife -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- 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] Re: [opensuse-factory] regression in (GNOME) factory regarding gtk2 development
by Boris Manojlovic 01 Oct '11

01 Oct '11

Hi Dominique and lists, On Sat, Oct 1, 2011 at 11:31 AM, Dimstar / Dominique Leuenberger <dimstar(a)opensuse.org> wrote: > On Sat, 2011-10-01 at 10:22 +0200, Boris Manojlovic wrote: >> Hi, >> >> gtk2-devel package does not pull "shared-mime-info" (more specificaly >> it should be pulled by gdk-pixbuf-devel) >> required by gdk-pixbuf-devel or specifically gdk-pixbuf-csource >> command from same package GDK uses mime-info for controlling >> which "loader" will be used for loading images and if package is >> missing it will fail to call correct shared library, >> as can not determine given image type. Installing shared-mime-info is >> enough to make loaders work as expected but should be fixed on higger >> level. >> >> Boris >> >> ------------------- error snip --------------- >> gdk-pixbuf-csource --extern --struct --raw --name=startbanner_pixdata >> rsrc/build.bmp > rsrc/editor_banner.c >> failed to load "rsrc/build.bmp": Couldn't recognize the image file >> format for file 'rsrc/build.bmp' >> ------------------- error snip --------------- > > Hi Boris, > > Thank you very much for your report and the analysis (and also the > submit request to implement your suggested solution). > > Unfortunately, I'm afraid, there must have been something else wrong, as > shared-mime-info is pulled in by a bunch of other dependencies. > > Explicitly, for gdk-pixbuf-devel, the chain is like this: > > shared-mime-info => libgio-2_0-0 => libgdk_pixbuf-2_0-0 => > gdk-pixbuf-devel. > > The dependency on libgio-2_0-0 to shared-mime-info was added back in > September 2010, based on bnc#555606. > > Can you please verify on your system if this dependency chain is the > same for your system and possibly also with "zypper verify" if your > system is in a consistent state? > yes it is consistent. You are correct 100% on my live factory it is really pulled by libgio and a lot of other packages. Unfortunately it is on OBS not on live system that i have a problem because of missing shared-mime-info package, so it was a bit wrong assessment from my side to begin with. But my maybe not perfect fix would fix issues on OBS. Maybe question is what changed from few days ago and now we do not pull shared-mime-info into gtk2-devel chain any more? Anyway I'm forwarding this to opensuse-packaging as this is more appropriate list for this exact issue. So recap is Factory installation is ok for development, but OBS fails for specified reason. > For now I put your SR on review with a link to this mail thread, until > it's all sorted out. > > Best regards, > Dominique / DimStar > > -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0