Hey,
Dominique and I are currently wondering what to do wrt libexecdir for
evolution-data-server. Should we leave it unchanged (so files will be in
/usr/lib) or should we change it to /usr/lib/evolution-data-server?
If the latter, is there any reason this is not done automatically?
Also, hrm, would rpmlint have ways to warn about packages that put
binaries in libdir instead of libexecdir? (I can find a few of them here
with a grep)
Vincent
--
Les gens heureux ne sont pas pressés.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
A runlevel script X without further dependencies was split into X and Y.
Now Y needs to be started before X.
Both scripts are in the same rpm package.
Adding '# Required-Start: Y' to script X will break updating the package
because there seems to be no way to get Y enabled during the package
update.
For fresh install this may work.
%post
%{fillup_and_insserv -y -n Y Y}
%{fillup_and_insserv -y -n X X}
But for upgrade there is appearently no way to enable Y only if X is
already active.
How is this situation supposed to be handled, cleanly?
Olaf
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
I'm trying to package up the liboauth library (needed for my bti tool as
twitter is about to require oauth authentication soon) and I'm getting
the following error from rpmlint:
liboauth.i586: E: shlib-policy-name-error (Badness: 10000) liboauth0
Your package contains a single shared library but is not named after its
SONAME.
My .spec file seems sane and simple, yet I can't figure out the real
issue here. Odds are it's a problem in the original package, as I can't
see any other distro packaging it yet and it's very new.
My package is at:
https://build.opensuse.org/package/show?package=liboauth&project=home%3Agre…
if anyone wants to take a look at it and tell me how badly I messed it
up :)
And yes, I did read the information at:
http://en.opensuse.org/openSUSE:Shared_library_packaging_policy
but can't find anything relevant to this issue there, but I might be
totally missing the relevant portion.
Any help is greatly appreciated.
thanks,
greg k-h
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
2010/7/28 Greg KH <gregkh(a)suse.de>:
> I'm trying to package up the liboauth library (needed for my bti tool as
> twitter is about to require oauth authentication soon) and I'm getting
> the following error from rpmlint:
>
> liboauth.i586: E: shlib-policy-name-error (Badness: 10000) liboauth0
> Your package contains a single shared library but is not named after its
> SONAME.
>
> My .spec file seems sane and simple, yet I can't figure out the real
> issue here. Odds are it's a problem in the original package, as I can't
> see any other distro packaging it yet and it's very new.
>
> My package is at:
> https://build.opensuse.org/package/show?package=liboauth&project=home%3Agre…
>
> if anyone wants to take a look at it and tell me how badly I messed it
> up :)
>
> And yes, I did read the information at:
> http://en.opensuse.org/openSUSE:Shared_library_packaging_policy
> but can't find anything relevant to this issue there, but I might be
> totally missing the relevant portion.
>
> Any help is greatly appreciated.
Since the soname of the library is liboauth.so.0 the package that
contain it must be named liboauth0, but your package is named liboauth
(lacks the 0 at the end). You just need to rename it.
Note that the devel package must be named liboauth-devel, not
liboauth0-devel. So you can't do "%package devel", instead you will
need "%package -n liboauth-devel".
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hi:
I wonder if there is anyway to programatically tell the buildservice:
1) execute script X
2) if that succedeeds and there are diferences in the "working copy" ,
attempt to "compile", if success, create submit request.
This can be useful for example for documentation packages that do not
really need to be compiled, just packaged and published.
Thanks
Hello.
How do I create a link from a package in 11.3 repository to same package
name in home repository ?
Im using kdegames-4.4.92 as an example.
Steps I've done so far.
Build Service > Projects > home:<user> > Packages
- Click on 'Link Package from other Project'
What do I put for these values to link in openSUSE:11.3 [kdegames4]
- Name of original project: ?
- Name of package in original project:?
- Name of linked package in target project:?
References
https://build.opensuse.org/package/show?package=kdegames4&project=openSUSE%…
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hi,
due the reduced manpower and increased maintenance load, we are not able to
provide any reasonable support (nor bugfixing, nor updates) for the following
list of packages:
* multimedia:apps/audacity; A Free, Cross-Platform Digital Audio Editor
* graphics/barcode; Text-Mode Barcode Creation Utility
* devel:tools/colordiff; Colour-highlighted 'diff' output
* Base:System/convert; Unit Conversion
* devel:libraries:c_c++/dbh; Disk-Based Hash Library
* server:database/dbview; Viewer for dBase III and dBase IV Files
* graphics/dx; IBM Open Visualization Data Explorer
* Education/garlic; Molecular Graphics Visualization Tool
* Education/gonvert; Unit Conversion Utility
* GNOME:Apps/gwget; GTK+ Front-End to wget
* bundle-lang-gnome-extras
* network/licq; A graphical ICQ Client for Linux
* graphics/pixmap; XPM Pixel Editor for the X Window System
* server:proxy/privoxy; The Internet Junkbuster - HTTP Proxy Server
* multimedia:apps/qtractor; A MIDI/Audio multi-track sequencer
* Education/rasmol; Molecular Graphics Visualization Tool
* graphics/sk1; Python-Based Vector Drawing Program
* network:telephony/smssend; interface to internet SMS forwarding
services
* devel:languages:tcl/spectcl; Interface Builder for Tcl/Tk and Java
* devel:tools/tkdiff; 2 and 3-way diff/merge tool
* multimedia:apps/tuxguitar; A multitrack guitar tablature editor and
player
* Virtualization/virtualbox-ose; VirtualBox OSE is an Emulator
* installation-images
* X11:Utilities/xcolors; Displays colors defined in rgb.txt
* X11:Utilities/xgrabsc; A Screen Grabber for the X Window System.
* X11:Utilities/xfishtank; An aquarium in the root window
* Education/xmoontool; The Moon in focus
* X11:Utilities/xroach; Some cockroaches on your root window
* X11:Utilities/xselection; Manipulate the XSelection
* graphics/zimg; display 2-D data of arbitrary format
* network/ytalk; Multi-User replacement for Unix talk client
Regards
Michal Vyskocil
Hello list,
I have installed opensuse 11.3 on a new production server. This server will be a webhosting server and needs php 5.2 actually. Is there any repo which can be added into a production server to provide php 5.2 for opensuse 11.3 ? Kindly advice.
Thanks
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Another osc release is out.
The major changes in this one are:
* Different trust handling, osc is now maintaining an own list, which projects
do you trust for package building.
* osc signkey --extend
An often request was that keys left their expiration date. But one don't want
to create new ones. You can now trigger the server to extend the expiration date.
This is supported on api.opensuse.org and will be supported with OBS 2.0.4
osc 0.128 is available via
http://download.opensuse.org/repositories/openSUSE:/Tools/
The full change log from the NEWS file:
- better default commands selection for editor/pager
- support "osc rq reopen" to set a request in new state again
- "osc repos" and "wipebinaries" is checking for local project now
- "osc getbinaries" works in project dir now
- support added for SPARC builds
- support build --oldpackages
- introduced the "trusted projects"
- Fixes for default editor, api check on deleterequest call, tempfile leaks, getbinaries source package handling, results command
#
# Feature which require either OBS 2.1 or 2.0.4
#
- add osc signkey --extend for extending the expiration date of the gpg public key
--
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
Hi,
I have a question regarding some build breakages with the freetype and
fontconfig packages in my OBS. I'm patching freetype and fontconfig
with some specific cherry-picked patches from Ubuntu in my OBS
athttp://download.opensuse.org/repositories/home:/anshuljain: for
11.3. I've done these for 11.2 successfully in the past and they've
worked perfectly.
I'm getting build breakage errors for freetype (live build log at:-
https://build.opensuse.org/package/live_build_log?arch=i586&package=freetyp…)
and fontconfig (https://build.opensuse.org/package/live_build_log?arch=i586&package=fontcon…).
The patches get applied successfully, and the problems occur during
the configure or final packaging moments. The strange part is that
I've been able to build these with no problems on my laptop. Its the
OBS which is giving me errors.
I'd appreciate some help :)
Regards
Anshul
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org