Darcs is a version control system written in Haskell, and in order to
learn more about packaging, I decided to try and package it up. As
luck would have it, I now have a fully packaged version sitting in my
home repository:
https://build.opensuse.org/package/show?package=darcs&project=home%3Akog13
It has build dependencies on packages in devel:languages:haskell and
devel:languages:haskell:next, but the program itself can be used for
more than Haskell development. So my question comes in several parts:
1) Where would the ideal place to submit this package be? Is it too
late to get it in one of the default repos for 12.2, or would Packman
be better?
2) Am I correct in thinking that the repos holding build dependencies
(in this case, the haskell development repos) aren't necessary to be
subscribed to when a user installs it?
3) What are some things to keep in mind when trying to submit new
packages to a repository?
I'm pretty new at this, so any help or advice is welcome.
Thanks,
~Damien
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi all,
I have been using spec cleaner for while. What I notice it that it uses
macro %make_install instead of %makeinstall. Both macros are OK for
openSUSE but the first one breaks the build for SLE.
<quote>
+ %make_install
/var/tmp/rpm-tmp.59594: line 45: fg: no job control
</quote>
I wonder if this should be fixed, in either spec-cleaner (use%makeinstall
in stead of %make_install) or in the buildserver (add macro %make_install
for SLE)?
Regards,
Joop.
See also: https://bugzilla.novell.com/show_bug.cgi?id=712171
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Probably have mostly the same people on the obs list and the packaging
list, but never the less I will try my luck here as well.
I have a couple of requests/questions in "cleaning up" OCaml related
packages and a problem.
1.) Since we have top level devel:languages:ocaml project can we please
move everything that is ocaml related and maintained
devel:languages:misc into the ocaml project?
2.) Do we have anyone that is really interested in OCaml or do we just
have what we have because other projects/packages depend on the few
packages we do have?
in d:l:ocaml the ocaml package is a link to the package in Factory. The
devel project for factory is d:l:misc. Because of local mods in
d:l:ocaml the link is busted due to merge conflicts. This breaks other
packages in d:l:ocaml. I have no idea how to fix this as every time I
try to touch any of these packages to get something fixed I get a stupid:
buildinfo is broken... it says:
type of message. This is of course complete crap as it prevents a person
trying to fix something from fixing it.
In addition to the gripes above I have a problem that I am stuck on and
could also use some help with. I am trying to build ocamlnet which
depends on pcre. The build process failes with this error:
ocamlfind ocamlc -g -I ../../src/netstring -package "unix" -custom -o
ocamlrpcgen -package unix,netstring \
rpc_generator.cma main.cmo -linkpkg
/usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld:
cannot find -lpcre_stubs
collect2: ld returned 1 exit status
File "_none_", line 1, characters 0-1:
Error: Error while building custom runtime system
make[1]: *** [ocamlrpcgen] Error 2
Knowing nothing about OCaml build and link processes I can only infer
things. Obviously the process calls ld to link a binary and passes
-lpcre_stubs, this would require the presence of libpcre_stubs.so
somewhere in the default search directories of ld. However, the package
ocaml-pcre does not provide this, it provides a dllpcre_stubs.so file in
a none-standard location (%{_libdir}/ocaml/stublibs).
Should ocaml-pcre create and provide a link %{_libdir}/libpcre_stubs.so
to {_libdir}/ocaml/stublibs/dllpcre_stubs.so, or maybe a link in
%{_libdir}/ocaml/stublibs and then a -L argument on the link line? Or is
there some trick that ocamlfind is supposed to play for me?
Help is as always appreciated.
Thanks,
Robert
--
Robert Schweikert MAY THE SOURCE BE WITH YOU
SUSE-IBM Software Integration Center LINUX
Tech Lead
rjschwei(a)suse.com
rschweik(a)ca.ibm.com
781-464-8147
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi,
I would like to create an update request for shorewall package which is
at 4.5.5.1 for 12.2 but the latest release in factory is 4.5.6.
The package should not breaking any other package as no other package
depends on it. Of course the ending decision is the maintenance team but
by looking to the osc commandline I should be using
osc maintenancerequest security:netfilter shorewall openSUSE:12.2
Is this correct or do I need to use a different approach
Thanks
Togan
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hello,
some days ago, Werner wrote about the split of the texlive package.
This has some side effects - for example, it broke the build of the
AppArmor package for factory :-(
Package: home:cboltz apparmor
Build log:
https://build.opensuse.org/package/live_build_log?arch=x86_64&package=appar…
Some issues I noticed in the log (not sure if I catched all):
[ 647s] kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 cmtt8
[ 648s] /usr/lib/mktex/mktexpk: line 118: mf: command not found
^^^^^^^^^^^^^^^^^^^^^
[ 648s] mktexpk: Mismatched mode ljfour and resolution 600; ignoring mode.
[ 648s] mktexpk: Running mf \mode:=ljfour; mag:=1+0/600; nonstopmode; input cmtt8
[ 648s] /usr/lib/mktex/mktexpk: line 235: mf: command not found
[ 648s] grep: cmtt8.log: No such file or directory
[ 648s] mktexpk: `mf \mode:=ljfour; mag:=1+0/600; nonstopmode; input cmtt8' failed to make cmtt8.600pk.
[ 648s] kpathsea: Appending font creation commands to missfont.log.
[ 648s]
[ 648s] !pdfTeX error: pdflatex (file cmtt8): Font cmtt8 at 600 not found
^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ 648s] ==> Fatal error occurred, no output PDF file produced!
I'd guess I need some additional BuildRequires - can someone give me
a hint (or a SR ;-) what exactly I need, please?
Do I need to wrap the additional BuildRequires in a
%if %{?suse_version} >= 1220
?
Regards,
Christian Boltz
--
> und wie lade ich Programme ein,
Hm, ruf sie an, oder schreib ihnen ne Karte.
[> Marlies/Ullrich Velter und Manfred Tremmel in suse-linux]
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi all,
we are trying to find out whether the current notification system we are
using in the OBS useful and fulfills the requirements of its users.
So a loose collection of questions might be:
Do you know the different ways of being notified (email, RSS, twitter)?
Do you use other channels than email?
Do you know the configuration interface https://hermes.opensuse.org/ ?
Do you use it? means: did you ever tweak params there?
Is it intuitive to use?
Did you ever use the expert mode?
Is the expert mode intuitive to use?
Are you missing features?
Is it working as you expected? (Except of things already known as bugs.)
Other thoughts?
Bye,
Christopher
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
All,
I packaged up SPITBOL which is a SNOBOL4 implementation.
home:gregfreemyer > Packages > SPITBOL
Where should I push it as a devel tool. I don't see a
devel:languages:misc equivalent.
Thanks
Greg
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
All,
I want to add a couple dirs from the tarball to the docs section.
I tried:
%doc docs/* demos/* test/*
No subfolders were created and I ended up with everything lumped in
the /usr/share/doc/packages/<package> folder which I found confusing.
So how do I get demos as an example as a sub-folder?
Greg
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org