http://build.opensuse.org/package/show?package=cedilla&project=M17N
I already know that this can be fixed by adding the comment
#!BuildIgnore: NX
into the cedilla.spec file.
But I still think this is somehow weird because cedilla doesn't
require X11, it only requires clisp which in turn requires X11.
Should I really add
#!BuildIgnore: NX
to the cedilla.spec file?
Is there a general solution for that problem without having
to add this comment to many .spec files?
--
Mike FABIAN <mfabian(a)suse.de> http://www.suse.de/~mfabian
睡眠不足はいい仕事の敵だ。
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice-unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice-help(a)opensuse.org
Hello community
I have %{_mandir}/man1/* under %files. The package builds fine for
the factory, but fails on 10.1 with this error
"File not found by glob: /var/tmp/gcompizthemer-0.7-build/usr/share/man/man1/*"
The file is actually present in /usr/man/man1/*
How do I map according to the distribution any suggestions?
Regards
Jigish
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice-unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice-help(a)opensuse.org
The package "freefont" failed in the openSUSE build service
with the error "Permission denied" when trying to execute
$RPM_SOURCE_DIR/remove-kana-glyphs ./sfd/*.sfd
"remove-kana-glyphs" is a fontforge script and has the executable
flags set in the original file. Therefore it builds fine with mbuild
and build.
But apparently the executable flags disappear when uploading the
source to the openSUSE build service.
Adding the line
chmod 755 $RPM_SOURCE_DIR/remove-kana-glyphs
makes the package build in the openSUSE build service as well.
--
Mike FABIAN <mfabian(a)suse.de> http://www.suse.de/~mfabian
睡眠不足はいい仕事の敵だ。
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice-unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice-help(a)opensuse.org
Hello,
I'm doing some experiments with a QA package for Fontlinge:
http://build.opensuse.org/package/show?package=fontlinge-QA&project=home%3A…
(its main reason is to check if the perl modules are in @INC)
Unfortunately, I had to add some php5-* BuildRequires to work around
"multiple choice" expansion errors in SUSE 9.3 and 10.0 (which shipped
with PHP4 and PHP5).
The requirements I'd like to use are those from the Fontlinge package:
mod_php_any php-mysql php-gd (without PHP version specified).
Can you add a "prefer" for php5-* in the global configuration of
SUSE 9.3 and 10.0, please?
Even more bad luck: I get several expansion errors for Fedora 4 and 5 as
well as Mandriva :-(
Fedora 4/5 doesn't offer
- mod_php_any, one of the Fontlinge requirements - this probably has
another name/provide there, but which one?
- php5-mysql and php5-gd which I used for the workaround above - not
really a problem since I will remove this after the problem with SUSE
9.3/10.0 has been fixed
Mandriva misses more packages/provides:
- perl-PerlMagick, perl-Msql-Mysql-modules, perl-TermReadKey - different
names?
- httpd, mod_php_any - probably available with a different name, which
one?
- apache2-mod_php5 (because of the workaround from above, also not a
real problem)
Should I use different Requires: or do you have another idea to solve
this problem?
I also have a strange requirement on Mandriva: pear(config.inc.php)
Where does this requirement come from? [1] Fontlinge don't use any pear
script - how can I remove this requirement? Is there something like
NotRequired: I could place in the Specfile? ;-)
Regards,
Christian Boltz
[1] a wild guess: the PHP files include() it, but it is generated at
user installation (aka "not part of the RPM"). Could this be the
reason?
--
Das soll jetzt wirklich keine Arroganz sein, aber es macht keinen Sinn,
das Haus abzureissen, weil du den Hausschlüssel vergessen hast. :-)
[Ratti in suse-linux]
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice-unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice-help(a)opensuse.org
Hi everyone,
we have recently added a way to disable single packages to be built. The
only way to disable packages at this time, is to use the 'osc' commandline
client. Just use
osc editmeta <project> <package>
and add the <disable>-Tag to the package metadata. You can either use:
<disable arch="<build-arch>"/>
or
<disable repository="<name-of-build-repository"/>
or both, like:
<disable repository="SLES9" arch="x86_64"/>
As there is a bug/feature in the API that strips out unkown tag (like
disable) when you'r redownloading the package metadata you'll find the
disable-tags to have vanished. So, you need to readd those everytime you
edit the package metadata until the API is fixed (which will hopefully be
the case pretty soon.)
Are there any questions, suggestions for improvements, comments or
criticism? ;)
Oh, and last, not least, many thanks to mls for implementing this
functionality.
Regards
Christoph
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice-unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice-help(a)opensuse.org
This morning I updated idzebra as part of the XML project. Version
1.3.36 is now available, I checked it by browsing the server at
http://software.opensuse.org/download/XML/xml-10.1/i586/ . But if I add
http://software.opensuse.org/download/repositories/XML/xml-10.1 as an
installation source, Yast still sees 1.3.34, and if I select it for
installation, if fails with this message:
┌────────────────────────────────────────┐
│Cannot access installation media │
│ CD 1. │
│Check that the server is accessible. │
│[ ] Show details │
│ │
│ │
│ [OK][Abort][Skip] │
└────────────────────────────────────────┘
Obviously, there is a inconsistency in the meta data. How can I fix
this?
--
Karl Eichwalder
R&D / Documentation SUSE Linux Products GmbH
Key fingerprint = B2A3 AF2F CFC8 40B1 67EA 475A 5903 A21B 06EB 882E