TW
$SUBJECT can't be right, but trying to zypper rm opensans wants to remove
releasenotes. :-(
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Fellow packagers,
after some discussions in our team, we figured that it would be neat if we could
build python modules for Python 2 and 3 from a single spec file. Now that a
great deal of python modules work with both pythons, this makes a lot of sense.
A good deal of work can be done by RPM macros. Then we could even seamlessly
start building modules for PyPy, Jython and other pythons.
A sample specfile, and the corresponding set of RPM macros, is attached. As you
can see, the appropriate subpackage is generated automatically by
%python_subpackages, build and install steps are handled through %python_build
and %python_install respectively. There is some more magic involved, as well as
possibilities for customization.
There is a minor problem with BuildRequires. As long as you only need
python-devel, it's not too bad to just list $flavor-devel requirements by hand.
It's worse when you require more subpackages, because then you need all of them
in both python2 and python3 versions.
It would be nice to be able to specify %{python_require Mako} and expand that to
all the necessary BuildRequires, but OBS blocks us here, because the limited
environment will not expand such macros.
mls, ro, or anyone from the OBS team, would it be possible to solve this?
Still, it basically doesn't matter if you list all the BuildRequires twice in
one spec or in two specs, so there.
Another thing I'm still unclear on are the filelists. It's certainly possible to
make a generic filelist, something along the lines of:
%package -n %flavor-%modname # python3-Mako
%defattr(-, root, root)
%{%flavor_sitelib}/*
%{%flavor_sitearch}/*
but this doesn't solve docs and possible other files.
Again, obviously, we can write the filelists by hand. But if you have good
suggestions for some smart macros here, I'd love to see them.
What do you folks think? Comments, questions?
m.
Hi,
Those of you running SUSE Linux Enterprise somewhere may know the
problem. openSUSE contains some package that you want on SLE but since
there is no SUSE support for that particular package you won't find it
in any of the official repos either. openSUSE on the other hand contains
that package and maybe the package maintainer(you!?) even builds it in
the Factory devel project for SLE.
Devel projects however may contain lots of other experimental stuff that
you may not want on your SLE installation. So it would be really nice to
have a central project to collect known good community packages built
for SUSE Linux Enterprise server.
That project is here now: openSUSE:Backports:SLE-12!
Getting a package in there is quite easy. Just file a submit request to
openSUSE:Backports:SLE-12. There are basically two rules for packages in
that project:
- packages must not conflict with packages already contained in SLE
- package sources must be accepted also in Factory
More details are explained in the wiki:
https://en.opensuse.org/Portal:Backports
The whole thing is still a bit experimental to find out what works
and what not. Nevertheless testers, contributors and feedback in
general welcome!
cu
Ludwig
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.de/
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard,
Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg)
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
I see that lots of packages include changelog entries up to seconds. I
wounder, are people writing time with seconds (while rpm allows it to be date
only) or is there some special tool to do that properly that I'm not aware of?
--
Regards,
Stas
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hey fellow WindowMaker users.
The current maintainer of WindowMaker, Carlos Mafra, has expressed an
interest in building and distributing WM across multiple distributions,
using build.opensuse.org.
This is his message:
http://article.gmane.org/gmane.compw.window-managers.windowmaker.devel/9221
" It would be awesome if someone who understands about packaging could
set up the wmaker package to be built on https://build.opensuse.org/"
Let us help him out for the awesome window manager :)
Kind regards,
Howard
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Morning all,
during rebuild of a package I suddenly get a new error messages, resulting in a failed build:
[ 42s] package: trytond
[ 42s] /usr/bin/chkstat modified files that are not properly handled!
[ 42s] this will break rpm -V, ask ro for details.
[ 42s] diff for both runs of rpm -V:
[ 42s] +.M...UG.. /var/log
The only point I address /var/log in the spec file is
....
mkdir -p $RPM_BUILD_ROOT%{_localstatedir}/{lib,log}/%{basename}
[...]
%files
#%files -f filelist
%defattr(-,root,root)
%doc README tryton-server.README.SUSE trytond.conf.example doc/*
%{python_sitelib}/*
%dir %{_sysconfdir}/%{basename}
%{_bindir}/%{name}
%{_unitdir}/%{name}.service
%attr(640,root,tryton) %config(noreplace)%{_sysconfdir}/%{basename}/%{name}.conf
%attr(640,root,tryton) %config(noreplace)%{_sysconfdir}/%{basename}/%{name}_log.conf
%attr(744,tryton,tryton) %dir %{_localstatedir}/lib/%{basename}
%attr(744,tryton,tryton) %dir %{_localstatedir}/log/%{basename}
and that was not changed compared to before.
Any idea how I can get rid of the message, or what the reason suddenly is?
Thanks
Axel
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi to all.
I maintain monster-rpg-2 package at games repo. The game provided some
files at /usr/share/%name but now it should provide the single zip file
there. So I just updated the spec, rebuild packages and installed them.
For some reason /usr/share/%name' files weren't purged! So game tries to
load both files and zip file and fails.
Any tips please?
--
Best regards,
Dmitriy DA(P).DarkneSS Perlow @ Linux x64
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi,
I was wondering when the timezone will be updated to the 4th release of 2015?
http://mm.icann.org/pipermail/tz-announce/2015-April/000031.html
In Egypt, we won't be observing DST this year, however
'timezone-java-2015c-1.1.noarch', the current version in Tumbleweed,
applied it since 30th of April.
Regards,
Waleed Lutfi
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Dear packaging maintainers and users,
when playing around the openSUSE docker image and installing git I
figured out some "missing" dependency: ca-certificates-mozilla.
There's no direct or indirect depedency for installing
ca-certificates-mozilla.
That results to these kind of error messages:
git clone https://github.com/gitlabhq/gitlab-ci-runner.git
fatal: unable to access
'https://github.com/gitlabhq/gitlab-ci-runner.git/': SSL certificate
problem: unable to get local issuer certificate
What do the packagers think about adding a ca-certificates-mozilla
package dependency?
For example on Arch Linux, git has a curl dependency. And curl has a
"ca-certificates" dependency (this is not equivalent to the openSUSE
ca-certificates package, as it includs all Common CA certificates). So
it can be called an indirect dependency.
Thanks in advance for your feedback! Regards,
Stefan
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi All,
Quick question, I am getting the rpmlint warning "/opt may not be used by a
SUSE. It is reserved for 3rd party packagers". I am obviously not SUSE, but
how can I specify the vendor? I've tried "Vendor:" tag in spec file, it did
not helped. And disable of rpmlink check seems like a cheating, I'm sure there
should be proper solution which I'm not aware of.
--
Regards,
Stas
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org