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 everyone,
having maintained the following packages in Factory/STABLE for quite some
time, I would like to get rid of them. Either by tranfering them to a
maintainer inside SUSE/Novell, by moving them to Contrib
(http://en.opensuse.org/Contrib/packages) or by dropping them completely.
* duplicity
* nano
* newmail
* offlineimap
* python-GnuPG-Interface
* python-curl
* python-gpgme
* python-kid
* python-setuptools
* rdiff-backup
* repoview
* safecat
* smart
* yum
* yum-utils
If you are interested, please speak up now!
Thanks,
Christoph
--
Christoph Thiel, Tech. Project Management, Research & Development
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
While cleaning up the libqca2 package according to rpmlint checks using osc
build, I got a warning that there are no Packager: tags in the packages.
After adding a Packager tag, I got a warning that I should not hardcode
Packager: becauser "rebuilder cannot change it". What's the correct behaviour
here?
1) Is this rpmlint check spurious, eg since packages in the distro seem to
have a Packager tag of http://bugs.opensuse.org that was added automatically?
2) Or is there a correct Packager tag using some macro that is automatically
filled for packages that are only in the public Build Service?
The fedora packaging guidelines
(http://fedoraproject.org/wiki/Packaging/Guidelines) discourage the use of
Packager. I'll add this info to our guidelines once I know how to do it
right.
Will
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hi everyone,
This is just a reminder: We have next week Alpha2 of openSUSE 11.1.
Check-in deadline for base/core packages or packages with a huge
dependency list: Friday, 15:00 CET
Check-in deadline for leaf packages: Monday, 17:00 CET
We decided in accordance with legal to move the ECR deadline from
August 18th (Monday) to September 5th (Friday).
Thu, Aug 21: Alpha2
o Kernel and installer work on a limited range of machines.
o Bootable ISO with kernel, installer and all toolchain packages
updated.
o Top priority for x86, but fix/release other archs the following days.
o Start install and functional tests on those features which are
available.
Best,
Christoph
--
Christoph Thiel, Tech. Project Management, Research & Development
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
Czech Packagers Team (Prague) meeting minutes 2008-08-21
========================================================
Present: anicka anosek jmatejek lmichnovic mkudlvasr mmarek
mvyskocil nadvornik prusnak puzel
Minutes: jmatejek
Topics:
(1) packaging news
(2) Jeff Jaffe's visit
(3) Christmas party & Mountain trip plans
(4) Internal presentations
(5) RAG reports summary from 2008-08-22
(1) packaging news
There are some interesting news worth mentioning in the main report:
Anosek packaged the new Eclipse 3.4 in buildservice.
Anicka has some problems with perl-tk. The package is long dead and it is
also incompatible with new Tk, it carries it's own old version.
Apparently, this old Tk doesn't work with newest Xorg. Upgrading Tk in
perl-tk seems infeasible, and it's quite possible that the bug will be too
hard to fix. Also, we can't drop the package because TeX depends on it. We
have recently learned that there exists another "perl-tk" module,
implemented differently, in a way that is much more stable and
maintainable. We still need to confirm that it is source-compatible with
our perl-tk.
(2) Jeff Jaffe's visit
We're expecting Jeff Jaffe to visit us on Thursday (28. 8.) There probably
won't be any formal meeting.
(3) Christmas party & Mountain trip plans
Most of us agreed that last year's christmas party on the skating rink was
a success and that we should do it again this year.
The mountain trip will probably be on second weekend in January, so that
we can enjoy some actual snow.
(4) Internal presentations
We discussed some possible topics for internal presentations, and they
will probably all revolve around programming languages. As we are
expecting rguenther's C++ training, anosek offered to do a presentation
about Java and how it compares to C++, and prusnak reacted by offering C#
presentation.
We also talked about possible presentations for Perl (by anicka): "what's
new and interesting in perl6", and "basic scripting tasks made easier in
perl".
Regarding the latter, we are encouraged to think of simple real-world
scripts that we'd like to see (and do) in perl, and send the ideas to
anicka.
(5) RAG reports summary from 2008-08-22
anicka:
- perl-Tk: investigating failing build
- bacula: update to version 2.4.1, fix #414957
- work on openSUSE Stats
anosek:
- fixed z88
- updated ant 1.7 -> 1.7.1, submitted to Beta first
- updated Eclipse to 3.4 in BS
jmatejek:
- writing tests for python security updates
- work on splitting python feature
lmichnovic:
- gtkspell: Version update.
- amanda: Fixed bug #412636 - amanda file permission problem.
- sK1: new package as successor of skencil for Factory. Building also in
Build Service. Fixed python incompatible code on 64bit arch. Upstreamed
patch.
- opera: Security update to version 9.52.
- Fixing failing packages due to LSB conformation of init scripts. -
Fixing failing packages due changes in ncurses package.
mmarek:
- updated kbd to 1.14.1
- SoC
- submitted final evaluation
- testing further fixes and features
- packaged sblim-cmpi-dhcp and sblim-tools-libra for Factory
(fate#304337)
- discussing the "Contrib repository" idea on opensuse-factory
mvyskocil:
- submitt many of openproj build dependencies:
- crimson
- swing-worker
- asm2 2.2.1
- jgoodies-forms 1.2.1
- nachocalendar 0.23
- jcalendar 1.3.2
- jreleaseinfo 1.3.0
- l2fprod-common 7.2
- isorelax 0.1
- jflrg 1.0
- openmarkup 1.1
- jdnc 0.7*
- update jpackage-utils to 1.7.5
*dropped the jdnc 0.7 due the Sun Proprietary license in some source files
[bnc#418698] - this package will be replaced by swingx 0.9.6
- cleaning and updates of packages in home:mvyskocil
- proposed two packages - drscheme, python-yapps2 - from home:mvyskocil as
candidate packages to the Contrib (http://en.opensuse.org/Contrib/packages)
prusnak:
- sysstat: fixed disk statistics, minor changes in SUSE-specific files -
Xfce: packaged 4.6 alpha into OBS (X11:xfce:unstable)
- open-vm-tools: updated to 2008.08.08 and fixed build
puzel:
- mftrace: update to new version
- ec-fonts-mftraced: fixed build in beta
- at: work on update to 3.1.10
- parted: considered implementing of ext4 support (bnc#417950)
- vim-plugins packages moved to 'editors' OBS project
sbrabec:
pidgin, gaim: Research and fixing ssl certificate checks (bnc#415679).
libnut, libgadu, lha, libp11: Update, fixing.
gdm, gnome-patch-translation, shared-mime-info: Update.
gdm: Research on new branding for version 2.22.
gimp, pidgin: Updates.
PackageKit: Locale fixes.
gcalctool: Searching and backporting locale specific fixes (bnc#402630).
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Packagers/Developers,
during the merge of sf.net, sls.de and the openSUSE support forums at
forums.novell.com into the official openSUSE Forums, we decided to
establish a dedicated subsection for questions about the openSUSE
Build Service. In addition to that, there's a section dealing with
programming/scripting in general. The ultimate goal of that approach
was to achieve synergies for the OBS out of the openSUSE Forums
(especially to achieve the participation of folks not that used to
mailinglists). Unfortunately these sections in the Forums are not that
frequently used, questions by newbies could not be answered
appropraite as we lack participation of advanced folks in
programming/scripting and packaging.
Therefore I'd like to ask you if it would be possible for you to help
us and participate in the following section of the openSUSE Forums?
http://forums.opensuse.org/programming-scripting/
The OBS section is designed as a subsection here,
http://forums.opensuse.org/programming-scripting/opensuse-build-service-obs/
The whole OSF staff would be pleased if you'd be able to help out and
provide some of your experiences to new and existing users interested
in the OBS and programming/scripting in general.
As I said we hope to achieve synergies and bring you back some folks
interested, but not that used to mailinglists and prefer the Forums as
a communication medium.
I myself wrote an article at lizards.o.o 2 months ago, that is maybe
worth a read in that context,
http://lizards.opensuse.org/2008/06/17/nntp-access-to-the-opensuse-forums/
I'd love to get an insight into your thoughts about it. Suggestions
for further attracting of developers/packagers to use the OSF (besides
NNTP) are certainly welcome and appreciated!
Thanks a lot in advance!
Best,
Rupert
--
Rupert Horstkötter, openSUSE Community
Email: rhorstkoetter(a)opensuse.org
Phone: +49 6151 7897817
Mobile: +49 176 21820039
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hello.
Package skencil can't work with tcl/tk 8.5 (see
https://bugzilla.novell.com/show_bug.cgi?id=392195), so it has been
dropped.
It's fuctionalitty will provide new package sk1 (http://sk1project.org/).
Regards Ladislav.
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hello.
FYI:
I have submitted new version of djvulibre and it's library has now
version *.21.
So according to Shared Library Packaging Policy I have also renamed
the library subpackage libdjvulibre21.
Best regards Ladislav.
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hi,
if you never read about the fillup_and_insserv or fillup_only rpm macros
in openSUSE, you can probaby stop reading here (and be happy ... ;)
After long years (SuSE Linux 8.0 has been a while away) I went over
the fillup_and_insserv and related macros and killed the support for the
rc.config file migration and the old START_XXX variables.
Additionally the option "-p" which has been a no-op since just as long
has been removed.
this means:
fillup_and_insserv will error out if the options "-s" or "-p" are used,
currently with echoing a line explaining the problem, later on by cleanly
removing the options from the rpm declaration so that rpm will just
error out with "unknown option for ..."
As a general note:
- for a new package, fillup_and_insserv should almost _never_ be
needed at all, to just use fillup on the sysconfig file, the macro
fillup_only should be used. It's really only needed if a service
should be active by default with either "-y" or "-Y" depending if
it should be activated only on first installation of a package
or on any installation/update of a package.
- fillup_and_insserv was invented during the days when we migrated
from rc.config to the /etc/sysconfig structure and at the same time
removed all the START_* variables and added the dynamic list
of initscripts using "insserv". Back then the macro was needed
even for packages with services defaulting to "off", but this use-case
is not relevant any more.
mgration example:
old call:
apache2/apache2.spec:%{fillup_and_insserv -ns apache2 apache2 START_HTTPD}
new call (step1):
apache2/apache2.spec:%{fillup_and_insserv -n apache2 apache2}
or even (step2):
apache2/apache2.spec:%{fillup_and_insserv apache2}
(since "-n apache2" is a no-op, since -n is there to overwrite %{name}, which
is apache2 again)
or (since we are not activating by default):
apache2/apache2.spec:%{fillup_only -n apache2}
or shorter (see above, -n works the same way here)
apache2/apache2.spec:%{fillup_only}
PS: thus shrinking the length of most postinstall scripts dramatically,
as I learnt over the years: each and every line of pre/post/... scripts
should be eliminated if at all possible ;)
--
with kind regards (mit freundlichem Grinsen),
Ruediger Oertel (ro@novell.com,ro@suse.de,bugfinder@t-online.de)
----------------------------------------------------------------------
Linux MacBookRudi 2.6.26-14-default #1 SMP 2008-08-08 13:52:24 +0200 x86_64
Key fingerprint = 17DC 6553 86A7 384B 53C5 CA5C 3CE4 F2E7 23F2 B417
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
Hi,
for all those who have faling package due missing Required-Stop
and/or Should-Stop tags:
Required-Stop: is for services which must still be available
during the shutdown of the service.
Should-Stop: is for services which should still be available
during the shutdown of the service.
You may rename this in mind to Required-(During-)Stop and
Should-(During-)Stop to have a mnemonic. Any other interpretation
is simply wrong, compare with
<http://refspecs.freestandards.org/LSB_3.2.0/LSB-Core-generic/LSB-Core-gener…>
The special facility `$null' is only for enforcing an empty
dependency in Required-Stop and Should-Stop otherwise insserv
assumes the same dependencies as for the Start case. This is
done to be able to support foreign and third party boot scripts.
Beside this the old tags
X-SuSE-Should-Start
X-SuSE-Should-Stop
X-UnitedLinux-Should-Start
X-UnitedLinux-Should-Stop
are obsolete since LSB 2.0 and have to be replaced with the LSB tags
Should-Start
Should-Stop
To enforce clean scripts, an LSB header may have the following tags
Provides
Required-Start
Required-Stop
Default-Start
to be fully functional. If the tag
Should-Start
is used also the tag
Should-Stop
has to be used. The tag
Default-Stop
is optional on openSuSE whereas the tags
Short-Description
Description
should be used and filled with text to have a description around
in the runlevel editors.
The Debian/openSuSE vendor tags
X-Start-Before
X-Stop-After
implies that the script using the keyword X-Start-Before should be
started before the specified service names respectively that the
script using the keyword X-Stop-After should be stopped after the
specified service names.
Beside this it is possible to use a LSB header for third party
boot scripts without editing them. For this only a file with
the LSB header therein and the same name as the foreign boot
script has to placed in
/usr/share/insserv/overrides/
or to overwrite a LSB header of a third party script it is
possible to place an replacment LSB header with the same
file name in
/etc/insserv/overrides/
Werner
--
Dr. Werner Fink <werner(a)suse.de>
SuSE LINUX Products GmbH, Maxfeldstrasse 5, Nuernberg, Germany
GF: Markus Rex, HRB 16746 (AG Nuernberg)
phone: +49-911-740-53-0, fax: +49-911-3206727, www.opensuse.org
------------------------------------------------------------------
"Having a smoking section in a restaurant is like having
a peeing section in a swimming pool." -- Edward Burr
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org