Hi folks,
recently, a lot of PHP packages have been either converted from PEAR
format to composer or offered in both format. Some new software has been
composer-only right from the start.
As far as I know, we only have tools for automatically dealing with PEAR
format packages.
This is going to get worse as the most widely used 3rd party pear server
software, pirum, has been deprecated in favor of composer.
This renders more and more pear based installations useless.
http://pirum.sensiolabs.org/https://twitter.com/fabpot/status/434256189258735616
Do you know how other distributions handle this?
Is there any effort for (semi)automatic composer->rpm conversion tools?
--
Ralf Lang
Linux Consultant / Developer
Tel.: +49-170-6381563
Mail: lang(a)b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
Hi.
The Solaar package is in several repositories, but none of them install the
translations files. I've branched the package to try to build it with the
translations but if I do what I have done with other packages, use the
%lang_package macro and add %files lang -f %{name}.lang in the spec file, it
doesn't work. I get this:
find:
'/home/abuild/rpmbuild/BUILDROOT/solaar-0.9.2-22.1.x86_64/usr/share/locale/':
No such file or directory
find:
'/home/abuild/rpmbuild/BUILDROOT/solaar-0.9.2-22.1.x86_64/usr/share/help/': No
such file or directory
No translations found for solaar in
/home/abuild/rpmbuild/BUILDROOT/solaar-0.9.2-22.1.x86_64
error: Bad exit status from /var/tmp/rpm-tmp.GyVbWN (%install)
I have no clue on how to fix this. Any hints? I've tried copying the .po files
to the locale dir and it doesn't work. I'm making the translation for my
languaje and I'd like it to be included in the package.
Greetings.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi.
I've updated the package FBReader, but now it crashes when you click Read book
in the Library. I've reported the bug upstream
https://github.com/geometer/FBReader/issues/254
but I don't know if I should submit the package or not.
Greetings.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi.
First of all, I'm having problems with this particular list because I don't
receive the answers in my mail account, so I cannot answer to anybody that is
trying to help me. I've unsubscribed and subscribed again to see if it works
now. Sorry for the inconveniences.
In this answer to a previous question I did,
http://lists.opensuse.org/opensuse-packaging/2014-05/msg00032.html
I was said how to get the SONAME of a library, but how do you know it "before"
the library is built? I mean, if I don't have that library installed and the
package doesn't build so I can install the library and get it, I cannot run
the suggested commands (readelf or objdump) to get the SONAME. So, how do you
get the SONAME? I've read the page
http://en.opensuse.org/openSUSE:Shared_library_packaging_policy
but I can't see the answer to my question there (I may have overlooked it
because my English is quite bad).
Greetings.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Unsubscribe
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
> Partial Answer (I do not know enough to give the full info):
>
> The SONAME of the lib is "libzlui0_99".
>
> According to the Packaging Rules for shared libs (shlib-policy-name),
> the package-name should start with the SONAME, here "libzlui0_99".
>
> ATM the package is named "zlibrary-ui-qt", and this should be changed
> in the spec-file (to a name starting with "libzlui" and ending with a
> digit, try "libzlui0_99" for a start).
>
> Hope this gives you a hint in the right direction.
>
> - Yamaban.
Thank you for your answer Yamaban. I'll try what you suggest, but I still have
a doubt: where does the SONAME comes from? Is it the number that appears after
libname.so (0.99 from libzlui.so.0.99 in this case)?
Greetings.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi everyone,
in my home-project (home:ojkastl_buildservice) I updated and created
some packages, that might be interesting for factory. At least I
wanted to try them, so I thought I'd dive into packaging on obs.
I tried to follow the fantastic build documentation and the
guidelines, but I bet there are tons of errors in the specs. I would
kindly ask for feedback, so if anybody wants to have a look that would
be nice. With the exception of docker for 13.1 they all are correctly
built at the moment, and the ones I tried do work.
#### rdfind ###
rdfind is a new package, its a tool to find duplicate files and
sym/hardlink them to save disk space. Small and nice.
### keepassx ###
keepassx is a password safe. I use the older version 0.4.3 as the
database format changed with version 2.x, and most android
implementations can't read the newer format. And the newer one is
still alpha...
### seafile & seafile-client ###
I updated the seafile-packages and related tools (ccnet, libsearpc) to
the newest 3.0.3 release, and got them to build. I have not tested
them, but I plan to do that soon. I also want to ask upstream if they
would like to use the obs to build packages, like owncloud does in ISV:...
### dirvish ###
dirvish is a nice backup-by-rsync solution, which has not been
developed any more upstream, basically because it seems complete and
mostly bug-free. I use it a lot and just linked the package.
The rest is just newer versions that I wanted to install on my
not-Tumbleweed machines, so I added them to have them at hand without
pulling in too much new stuff from other repos.
I am looking forward to any comments and hints and thank you in
advance. If someone is interested in taking maintainership I wont
object, though ;-)
Recommendations for devel projects where they might fit in are also
very welcome. ;-)
Regards,
Johannes
- --
Carpe diem - Seize the day.
Carp in denim - There's a fish in my pants!
(unknown)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/
iEYEARECAAYFAlNqgUwACgkQzi3gQ/xETbJgzQCfeeP4uM/ZWYzzpajGzpX2+iQl
yFYAnRRUTwvN9kv+5zCEO8WegV8g/HYV
=0yna
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi,
The filesystem package was changed to provide /var/run only as a symlink
to /run instead of doing two mounts of the same file system.
This has one (and only one AFAICS) consequence: %ghost entries in
packages need to move to /run - as packaging behind symlinks is
forbidden by policy.
In doubt you can easily remove this %ghost entry - their only use
case is reporting something for rpm -qf, which is of doubtful use
as most packages create a directory with their name and leave the
content unreported for -qf.
All other uses of /var/run will continue to work, so don't touch them
unless you have a very good reason to do so.
Greetings, Stephan
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi.
I'm trying to update the package FBReader but I have the following error:
(none): E: badness 10000 exceeds threshold 1000, aborting.
zlibrary-ui-qt.x86_64: E: shlib-policy-name-error (Badness: 10000) libzlui0_99
Your package contains a single shared library but is not named after its
SONAME.
and the following warning:
zlibrary.x86_64: W: shlib-policy-missing-suffix
Your package containing shared libraries does not end in a digit and should
probably be split.
The log file is at
https://build.opensuse.org/package/live_build_log/home:jcsl:test/fbreader/o…
I have read openSUSE:Shared library packaging policy but I still don't
understand how to fix this. Where do I get the soname from? Where do I have to
put it in the spec file? I've cleaned the spec file and fixed it as much as
I'm able to, but this is out of my range. If someone is kind enough to paste
the spec file somewhere, with comments, or explain in simple terms how to fix
this thing, I will update the wiki page to help others if they have this
problem.
If it's not asking too much, I also like to know if I put the files in the
right packages. The knowledge adquired with this will help me to build better
packages.
Thanks in advance.
Greetings.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org