openSUSE Packaging November 2008

packaging@lists.opensuse.org

29 participants
18 discussions

[opensuse-packaging] Cross-desktop games packaging mailing list
by Richard Hartmann 08 Jan '09

08 Jan '09

Hi all, if you are a games packager or have a general interest in FLOSS games, let me point you to games(a)lists.freedesktop.org The Debian and Ubuntu games teams have merged completely and the Fedora team has been working more and more with us to reduce duplicated work. We have been using the Debian games mailing list until now, but we decided that a distro-agnostic would be better. We will start defining requirements and possible layouts for intermediary repositories, soon. Distros could then pull from there and get a common, patched version. Distro-specific patches would be applied in your local SuSE repositories via your existing processes. It would be great if at least one SuSE games packager could subscribe to act as a liason. I suspect the rest will join over time as the benefits will, hopefully, be substantial. Thanks for reading this far and sorry to all people who are not interested in games packaging. Richard -- 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] Microdia Driver
by Günther J. Niederwimmer 03 Dec '08

03 Dec '08

Hello, can any tell me a working Mail Address for this package developer? The package is old :(, very old :((. I hope we have a updated package in the near ;). I am not a programmer and fail with a new spec file :(. -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 13

[opensuse-packaging] Incorrect rpmlint error: libdlm in head-i586
by Andrew Beekhof 01 Dec '08

01 Dec '08

Can someone please explain why the the rpmlint error below is occurring? Because according to the spec-file, there are two binaries (in sbin no less): %{_sbindir}/dlm_controld.pcmk %{_sbindir}/dlm_tool On Nov 30, 2008, at 1:08 AM, dist_root wrote: > Hi, > > > Detected the following changes in lint error output for libdlm > Distribution: head-i586 > > +E: libdlm no-binary > > > PS: Note that all occurrences of %{VERSION}-%{RELEASE} > are replaced by the verbatim string $VERSION-$RELEASE > to minimize useless output. -- 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] [ANN] New packages of Tidy and W3C Markup Validator available
by Sierk Bornemann 28 Nov '08

28 Nov '08

Hi all! Several days ago, I have packaged new packages of tidy and w3c-markup-validator via the openSUSE Build Service to be in sync with the most recent release state of their original project. They are available via http://download.opensuse.org/repositories/Tidy/ and http://download.opensuse.org/repositories/validators/ . The Build Service has had, for whatever reason, difficulties, to successfully finish building the packages for Factory Builds (SUSE_Linux_Factory). Please take a look at it, why these Factory Builds can't be built and saved successfully (they build, but while finishing and saving the RPMs, the build process stops for a reason unknown to me). I would be glad to see these packages being updated in the upcoming openSUSE 11.1 (the tidy packages in the official openSUSE 11.0 haven't been updated for whatever reason since a long time, although the Build Service provides the newest tidy packages maintained and regulary updated by me). Tidy note: ======= there does NOT exist an official release version of tidy. The most recent CVS HEAD version always is the most recent stable version. The official version string of tidy is a date string in tidy/src/version.h. That's why I name the tidy packages with two dates: the official date string of tidy/src/version.h and the date string of my CVS checkout. Because the date string in tidy/src/version.h only changes from time to time, when there have been core changes to the TidyLib. But not all changes in the sources of Tidy concern such core changes, often there are changes in the tidy project's environment, and the version string in tidy/src/version.h remains untouched. That's why I name the tidy packages for openSUSE with *both* date strings. I have had a little email correspondence with one of the tidy developers some month ago, and he told me about that versionning. He told me officially, that Tidy has no official versionning, that therefore there exists a version/date string in /ti dy/src/version.h (currently this is: static const char TY_(release_date)[] = "14 October 2008";), and that because auf that, we are free to name and version the resulting RPM packages to our needs. W3C Markup Validator note: See http://validator.w3.org/ http://validator.w3.org/whatsnew.html#t2008-11-20 http://www.w3.org/QA/2008/11/w3c_validator_now_with_html5.html Thanks, Sierk Bornemann -- -- Sierk Bornemann http://sierkbornemann.de/ Sensationsangebot nur bis 30.11: GMX FreeDSL - Telefonanschluss + DSL für nur 16,37 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a -- 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] Finishing up openSUSE 10.2 and SUSE Linux Enterprise 10 Service Pack 1
by Marcus Meissner 28 Nov '08

28 Nov '08

Hi folks, This is only interesting for SUSE packages. Following maintenance changes are going into place end of today (Nov 28): - openSUSE 10.2 The openSUSE 10.2 security and support cycle is ending November 30. The current 10.2 queue of updates will be flushed out in the next days. => You no longer need to submit fixes for openSUSE 10.2 starting now. - SUSE Linux Enterprise 10 Service Pack 1 The 6 months concurrent maintenance of SP1 and SP2 is also over on November 30. The SLE10 SP1 QA queue will be processed and flushed out over the next days. The SP1 branch leaves regular maintenance and enters a long term support mode. => Packages fixes and updates for SLE10 SP1 are from now on only needed when explicitly requested by L3, Security or Maintenance team. Ciao, Marcus -- 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] repository purge behaviour (was repository removal behaviour)
by Philip Ashmore 28 Nov '08

28 Nov '08

Ok, so what I'm really talking about is "purging" a repository, for exampling a testing repository, so that the effects of installing any packages from that repository is rolled back. Philip -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 4

Re: [opensuse-packaging] repository removal behaviour
by Philip Ashmore 27 Nov '08

27 Nov '08

>>> On 11/27/2008 at 2:52 PM, Dominique Leuenberger <Dominique.Leuenberger(a)TMF-Group.com> wrote: > I have /var/log/zypp/history on my system, which shows me what I > installed when from what repository... it also shows me when I added / > removed repos. I guess the reason why your reply has a time before that of my original message is daylight savings time! Anyway, using webpin http://packages.opensuse-community.org/ I could not find a package that owns /var/log/zypp/history and it's not on my system - I'm using OpenSuse 11.0 x86_64. Even if it were, I'm addressing the broader use-case of User Cathy installs "A" from repository "X" "A" requires "B" from repository "Y" for proper operation. "A" requires "C" with a vendor change from repository "Z" to repository "W" for proper operation. When Cathy chooses to remove repository "X", this should cause the removal of package "A". If package "B" is not required by packages from repositories other than "X" then it should be removed. If package "C" is not required by packages from repositories other than "X" then it should revert to the version from repository "Z". Tracking these dependencies "by hand" would be error-prone to say the least. Philip -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 2

[opensuse-packaging] Shared files in current factory
by Michael Schroeder 27 Nov '08

27 Nov '08

Hi folks, here's a list of shared files and file conflicts in factory. The file conflicts need to be reflected in the specfile by adding a corresponding "Conflicts" entry. Shared files are not an error per se, but may be caused by some oversight leading to too fat packages. They may also cause problems if some packages is updated and the update changes the shared file. Here's the list: real file conflicts: ---------------------------- /usr/share/kde4/services/iso.protocol kio_iso (subpackage of krusader) kde4-kio_iso /usr/share/java/jaf.jar gnu-jaf geronimo-jaf shared files: ---------------------------- /usr/src/linux-2.6.27.7-4-obj/i386/*/Module.symvers kernel-syms kernel-*-base /boot/symsets-2.6.27.7-4-*.tar.gz kernel-syms kernel-*-base /lib/modules/2.6.27.7-4-*/build kernel-syms kernel-default-base /etc/modprobe.d/module-renames kernel-default-base kernel-xen-base kernel-pae-base /usr/share/postgresql/tsearch_data/xsyn_sample.rules postgresql-contrib postgresql-server /usr/share/omf/vinagre/vinagre-*.omf vinagre vinagre-lang dito: sound-juicer sound-juicer-lang seahorse, seahorse-lang planner, planner-lang gthumb, gthumb-lang gnumeric, gnumeric-lang gnopernicus, gnopernicus-lang gnome-commander, gnome-commander-lang glade3, glade3-lang epiphany, epiphany-lang epiphany-extensions, epiphany-extensions-lang dasher, dasher-lang anjuta, anjuta-lang accerciser, accerciser-lang /usr/share/man/man8/beagle-imlogviewer.8.gz beagle beagle-gui /usr/share/kde4/services/amaroklastfm.protocol amarok kde4-amarok /usr/share/kde4/apps/kconf_update/kwin_window_shortcuts.upd kdebase4-workspace kde4-kwin /usr/share/inkscape/extensions/wmf_input.inx inkscape inkscape-extensions-extra /usr/share/inkscape/extensions/gimp_xcf.inx /usr/share/inkscape/extensions/export_gimp_palette.inx inkscape-extensions-gimp inkscape-extensions-extra /usr/share/inkscape/extensions/fig_input.inx inkscape inkscape-extensions-fig /usr/share/inkscape/extensions/dia.inx inkscape inkscape-extensions-dia /usr/share/info/skk.info.gz skkdic ddskk /usr/share/ant/etc/junit-frames-xalan1.xsl ant ant-junit /usr/share/dbus-1/services/org.freedesktop.Notifications.service [CONFLICT] notification-daemon notification-daemon-xfce /usr/lib/totem/totem-plugin-viewer totem totem-plugin /usr/lib/python2.6/config/Setup /usr/lib/python2.6/config/Makefile python-base python-devel /usr/lib/mpi.so libboost_mpi1_36_0 boost-devel /usr/lib/gvfs/gvfs-fuse-daemon gvfs-backends gvfs-fuse Thanks, Michael. -- Michael Schroeder mls(a)suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- 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] repository removal behaviour
by Philip Ashmore 27 Nov '08

27 Nov '08

Hi there. I recently ran into problems using a particular repository, http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_11.0/ - see http://bugs.freedesktop.org/show_bug.cgi?id=18433#c9 for a full explanation. Anyway this problem has a general use-case. Is there a way to remove a repository and downgrade / change vendor for packages originating in that repository? An alternative approach would be to list the recently (installed / updated / vendor changed) packages and operate on the list, which may be useful in it's own right, but I can't see an OpenSuse way of doing that either. Yum has /var/log/yum.log but unfortunately it's only for packages installed by yum, not Yast2. Philip Ashmore -- 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] java version issue in factory - java 1.5 or lower
by Denny Beyer 24 Nov '08

24 Nov '08

Hello all, i build a package for a java program in the build service, it works alright on most repositories except for Factory. Following issue: >ERROR: the files above contain java bytecode for something later than java 1.5, >ERROR: please set the javac target to 1.5 or lower. Considering that java 1.6 is out for quite some time now (sun & openjdk), I wonder why java applications are forced to be compiled for anything lower than 1.6, rather that forcing them to be compiled for AT LEAST 1.6? I understand some of the libraries require an older version for compatibility, but this is a desktop app and there the latest java (sun 1.6.0u10 or equiv. openjdk) should be default instead. Ah, and btw: Still waiting for sun java 1.6u10 coming through online update. Any idea anybody when that will be? Thanks, Denny -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 2

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging November 2008