Hi,
If you have a Factory package that you also package in a
backports repo, then there is the problem that the
suse_update_desktop_file will erase translations not
known to the old distribution.
First let me explain the way Factory translates:
1. spec files have %suse_update_desktop_file, which will
a) mark the desktop file for the translation process
b) update the desktop files against desktop-translations
2. collect-desktop-files is built against all packages
with desktop files, this will collect all _upstream_ translations
from the desktop files
3. Karl is updating the lcn SVN to merge the openSUSE translations
with the upstream translations (upstream translations win)
4. Karl submits new desktop-translations to start the process over
So this works for Factory pretty well and allows openSUSE to
a) update the translations - unknown translations can be
filled up
b) update translations by an online update - translations unknown
will be erased from the desktop files to allow GNOME and KDE to
look into dekstop_translations.mo file
But this creates a problem with backports as way more translations
will be unknown and hurting more than it helps.
Now my tip: osc linkpac home:coolo update-desktop-files <myproject>
and make sure it's disabled for Factory. This version is patched
not to care about translations, so you get 100% the upstream translations
and not less.
Greetings, Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hi,
Looking at the packaging conventions, I didn't see any information for
creating devel packages, which is something rather... common :-) (or
maybe I missed the page about this)
It looks to me like all packages use different conventions for this,
while a standard pattern for summary and description would make sense.
Eg, a standard summary could be "Development files and libraries for
$package" and a standard description could be "Headers and libraries for
developing applications that use $something."
Also, right now, it's not clear to me if the group of the devel package
should be the same as the non-devel package or something like
Development/Libraries.
Any opinion?
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
Hi
I'm wondering how to set the javac target in a specfile.
[...]
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.
BTW, the error message contradicts itself ("later" means "lower"
version number?).
--> /usr/lib/rpm/brp-check-bytecode-version
How to reproduce:
osc co home:sndirsch geotag
cd home:sndirsch/geotag
env -u BUILD_DIST osc build
Best regards,
Stefan
Public Key available
------------------------------------------------------
Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH
Tel: 0911-740 53 0 Maxfeldstraße 5
FAX: 0911-740 53 479 D-90409 Nürnberg
http://www.suse.de Germany
-----------------------------------------------------------------
SUSE LINUX Products GmbH, GF: Markus Rex, 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
What do I do about these?
ERROR: translation is neither enabled nor disabled for this file:
... for a package that is /not/ going to be translated by SUSE? We are
not supposed to use %suse_update_desktop_file for such packages, but
when building against Factory this is a fatal error.
TIA,
Andrew
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hello,
Trying to build the latest GNOME for openSUSE 11.0. A fair amount of
those packages (~150) seem to require pcre-devel to be able to build
(which is not the case on Factory).
Is there an easy way to tell OBS to automatically install this package
during build for a specific project?
Thanks,
Magnus
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hi List,
i try to compile php5 on my own to package and make my own setup.
I have some difficulties at some extenstions.
Is this list also intended to use for questions to
php5-configure-line,needed packages and missing libs or only rpm-based
questions?
I asked in opensuse-list but answer was "why do you compile, you can
download it"... and the php-lists are barely useful.
Thanks,
Andre
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hi,
The update of intltool to 0.40.5 apparently made several packages fail with
this:
/work/built/info/failed/head-x86_64/jpilot:config.status: error:
po/Makefile.in.in was not created by intltoolize.
Is it something that should be fixed in intltool or in the failing packages?
Vladimir
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hi,
| $ submitpac -m .
| ...
| microcode_ctl-1.17-rpmlintrc is not mentioned in spec files as source
| or patch. Is this correct? [N/y/d] (y to ignore) ^C
So, should the rpmlintrc really be added to the spec file? The name is
microcode_ctl-1.17-rpmlintrc which I think is correct. As Source?
Regards,
Bernhard
--
Bernhard Walle, SUSE Linux Products GmbH, Architecture Development
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi all,
i have a problem with one of my packages, python-openssl: the previous
version was called 0.7a and the current one is 0.7.
However, in rpm's (and zypp's) view 0.7a > 0.7 and the package will
break distribution upgrade because it won't let itself be "downgraded".
How can i work around this? Is it possible to e.g. specify that the
newer one Obsoletes: %{name} = 0.7a and be done with it?
thanks for help
m.
- --
(if you have any comments, please CC me in the reply, otherwise my
replies will break threads. that is a bug in my way of using the
mailinglist, which is not yet fixed)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iEYEARECAAYFAkjuL9kACgkQjBrWA+AvBr8WXwCgie6RWXcffcUid45l3vaiDnrk
G7EAoKWKsK5eF3xjkAaGGcryImOrz/Fo
=0Pqb
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hi,
it seems that as part of some AutoReqProv mechanism scripts in
/usr/lib/rpm, rpmbuild, as part of the build systems, will add
/usr/bin/perl and /usr/bin/python as a requirement to my rpm packages
whenever they merely find a file that has them in the #!-line. Can I
disable this behavior?
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org