up to par
with its current level, please enlighten us ;)
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\ <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
_\_v The more things change, the more they stay insane.
-BEGIN PGP SIGNATURE-
Version
ibdb_cxx-4_5-devel ?
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\ <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
_\_v The more things change, the more they stay insane.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuP
r)
> Every distro does it approximately the same, with enough differences to drive
> one
> mad!
Yep.
> Will Linux Standard base or some big documentation writer ever come to save
> the day and bring order to this chaos?
No.
cheers
- --
-o) Pascal Bleser http://linux0
Juergen Weigert wrote:
> On Oct 25, 07 11:51:50 +0400, Nikolay Derkach wrote:
>> ?? ??, 25/10/2007 ?? 01:43 +0200, Pascal Bleser ??:
>>> -BEGIN PGP SIGNED MESSAGE-
>>> When I look at the "Team" presented on http://rpm5.org I notice several
:)
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\ <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
_\_v The more things change, the more they stay insane.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Gruenbacher wrote:
> On Sunday 14 October 2007 12:36:52 Pascal Bleser wrote:
>> Just that it doesn't work, you can only specify one arch for all
>> packages in one spec file. But I'm sure you already knew that ;)
>
-f mc.lang
%else
%files
%doc ...
%{_bindir}/mc
...
%endif
Not sure that's better though.
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\ <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
_\_v The more things change, the more they stay insane.
-BEGI
attr(-, root, root)
>> %doc AUTHORS COPYING ChangeLog NEWS README INTERNATIONALIZATION
>> %{_bindir}/peless
>> %{_datadir}/applications/%{name}.desktop
>> %{_datadir}/pixmaps/%{name}.png
>> %{_datadir}/pixmaps/%{name}.xpm
>> %_mandir/man1/peless.1.*
>
> A lo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Now also in the Build Service:
http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_10.2/
(and Factory, and ...)
Please pull it from there, I'll remove it from my repository in a few days.
cheers
- --
-o) Pascal Bleser
e/~pbleser/files/webpin/screenshots/
Will move it to openSUSE:Tools in the BS as soon as someone adds me as a
maintainer there ;) (or creates a project "webpin" and makes me the
maintainer)
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\ <[EMAIL PROTECTED]&
header) is available, or to find out whether someone already packages
foobar or not.
More information here:
http://dev-loki.blogspot.com/2007/07/webpin-command-line-client.html
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\ <[EMAIL PROTECTED]> <[EMAIL PR
oking for Java/Python/YCP developers, web designers,
artwork designers, and people with ideas, suggestions, and motivation.
[1]http://forge.novell.com/mailman/listinfo/appinstaller-devel
Please spread the word ;)
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\ &l
Or maybe in a form where people can add comments, hints, additional
information.
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\ <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
_\_v The more things change, the more they stay insane.
-BEGIN PGP SIGNATURE--
1] is fine and could even be
considered good practice, but overriding/adding macros means the src.rpm
won't build on other hosts/environments than your own.
[1] e.g.:
%packager Pascal Bleser <[EMAIL PROTECTED]>
%distribution SUSE LINUX 10.1 (X86-64)
just my 0.02?
cheers
- --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marcus Rueckert wrote:
> On 2006-10-27 00:07:28 +0200, Pascal Bleser wrote:
>> e... it's on purpose:
>> - ---8<
>> for lib in libobjc libgfortran libgfortranbegin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pascal Bleser wrote:
> Seems someone decided to remove /usr/%{_lib}/libstdc++.la on 10.2... ?
> At least it's not in any of the following packages:
> # rpm -qa | grep libstdc++
> libstdc++41-4.1.2_20061018-4
> libstdc++41-32
"\.la"
# rpm -ql libstdc++41-devel-4.1.2_20061018-4 | grep "\.la"
# rpm -ql libstdc++41-devel-4.1.2_20061018-4 | grep "\.la"
Any particular reason ? Is it somewhere else ?
I sure hope it wasn't "optimized" away because it breaks other packages
that need that .la :\
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Anyone already packaging "brasero" (used to be named "bonfire") ?
http://gnomefiles.org/app.php/Brasero
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\ <[EMAIL PROTECTED]> <[EMAIL PROTECTED]&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Bolt wrote:
> On Sat, 19 Aug 2006, Pascal Bleser <[EMAIL PROTECTED]> wrote:-
>> jdd wrote:
>>> Pascal Bleser a écrit :
>>>> "packaging made simple" - I'm afraid it's not simple, at least
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jdd wrote:
> Pascal Bleser a écrit :
>> "packaging made simple" - I'm afraid it's not simple, at least making
>> good packages isn't.
>
> I'm sure there are case where it's simple.
> some
ans it.
Actually, doing as above could end up in a race condition, so do *not*
do that, never.
It's an often made mistake, and I guess at least 60% of the spec files
of SUSE Linux packages still contain that line.
It's not dramatic though, but if you write or edit a spec file, n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adrian Schröter wrote:
...
> SL 10.0 has no Qt4 IIRC, so you need to compile against the KDE:Qt project.
10.0 ships qt-4.0.1
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\ <[EMAIL PROTECTED]> <[EMAIL PROTECTED
ubpackages ?
Reinhard, AFAICR, you were saying that having subpackages for backends
would be too difficult for end users to install/choose from.
If that's the reason for not doing it that way, then I wouldn't quite
agree.. handling explicitly broken/removed dependencies is much more
comp
few GNOME apps in my repository as well (e.g. and most notably
(latest stable) gimp and gnomebaker).
I'd say opensuse-packaging@opensuse.org would be the best place to do so.
James, "welcome back" from me as well ;)
cheers
--
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser
repositories at gwdg.de
That's fine, but suse.com/projects is mirrored on a lot more servers, so
I would prefer to use and reference an RPM-MD repository that's created
right there.
Thanks :)
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\ <[EMAIL PROTECTED]>
[1] http://www.suse.de/~mhopf/xgl/
How to handle KDE:KDE3 bugs ? bugzilla ? one of these lists ?
Could someone have a look at it please ? thanks :)
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\ <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
_\_v The more t
te_package_descr from 10.1/Factory, that adds those =Cks:
tags into the "packages" file, can I also use it to generate "packages"
for, say, 10.0/9.3/9.2/9.1 ?
Or will YaST2 on 10.0 and older bark, saying that it does not know
anything about the "=Cks:&quo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinhard Max wrote:
> Hi,
>
> On Thu, 18 May 2006 at 21:34, Pascal Bleser wrote:
>
>>> 4. Common advise
>>> -
>>> - when fixing package, try to keep style convention set by author
ires some non-default (as of what is
set as the default in rpmmacros and %_* path placeholders), you'd have
to pass it to configure anyway, no matter whether you
CFLAGS="%{optflags}" CXXFLAGS="%{optflags}" \
./configure --libdir=...
or
%define _libdir ...
%configure
>
to your proposal ;D
Should be %{name}-po-fix-typos.patch
> Patch2: blender-home-to-datadir.patch
> # patch is applied only on x86-64
> Patch5: Scons.patch [...]
(same nitpicking as above ;))
> 4. Common advise
> -
> - when fixing package
that has a different SONAME without
> having to worry about conflicts. The -devel packages would still be clashing
> in most of such cases, but the run-time packages can be installed in
> parallel.
100% ACK.
And always splitting is an easy rule, no need to consider subjective
criteria
atest amarok releases in my package
repository.
Let's pick that one as an example. How are we supposed to work
together, to avoid duplicate efforts ? Or is it way too early to even
consider it ? ;)
cheers
--
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\ <[EMAIL PROTECTED
ar as Python is concerned, you also have .so's under
/usr/lib[64]/python/site-packages/
It would be slightly more complicated than that I'm afraid :\
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\ <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
_\_v
ain package (foo).
...
> now, 33 doc packages are i386 ? And, of course all of them contain
> binaries, huh!
> :)
> Look, it wastes time & server space to get noarch packges built for
> different platforms.
>
> Why is this ?
Please buy yourself a clue before starting to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michal Marek wrote:
> Pascal Bleser wrote:
>> What just makes me wonder... what's the point of installing Python
>> libraries under /usr/local when the default sys.path doesn't include
>> that directory ?
>>
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michal Marek wrote:
> Pascal Bleser wrote:
>> 2) all your spec files that build using python setuptools are hosed
>> ~~~
>> The default prefix for builds with Python
cted.
I wanted to file a bug for this one as well, but I've been told it's
explicitely wanted that way.
Could someone @SUSE comment on this one ? Adrian ?
Is it a bug or is it intended ?
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\ <[EMAIL PROTECTED]>
most probably a broken mirror (broken = did not sync
correctly and/or all the data).
What mirror are you using ?
Try this one, it works for sure:
http://ftp.belnet.be/packages/opensuse/distribution/SL-10.0-OSS/inst-source/
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
in the
distribution btw), and pine.. well... anyone still use pine ? (hint: use
mutt ;))
What do you think ?
NB: thanks to Benjamin for collecting all that data, I'm just
transmitting ;)
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\ <[EMAIL PROTECTED]> <[E
Marcus Rueckert wrote:
On 2006-03-13 12:14:47 +0100, Pascal Bleser wrote:
/etc/y2pmbuild/files/*/etc/rpm/macros
Ok. Unfortunately y2pmbuild is no option for me, I have my own build
scripts that better fit my environment (and that support any
BuildRequires syntax).
i am getting bored telling
Ludwig Nussel wrote:
On Sunday 12 March 2006 16:40, Pascal Bleser wrote:
Following "issue": to set the %{DISTRIBUTION} header in my RPMs, I use
the following trick in my spec files:
Distribution: %(head -1 /etc/SuSE-release)
That's nasty.
Nasty but works, except for 10.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'd just like to stress this mail again, it's pretty critical for us 3rd
party packagers.
Could someone forward it to some yast2 developer who could answer this ?
Thanks.
Pascal Bleser wrote:
> Hi
>
> A question to YaST2 develop
PM ends
up with "Distribution: (none)".
Now I wonder, has anyone a better solution for this ?
How is this solved @SUSE ? Are you setting it using
build/abuild/y2pmbuild ? spec-file postprocessing ?
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\ <[EMAIL PROTECT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adrian Schröter wrote:
> Am Friday 10 March 2006 11:36 schrieb Pascal Bleser:
>> Robert Schiele wrote:
>>> On Fri, Mar 10, 2006 at 11:17:53AM +0100, Pascal Bleser wrote:
>>>> Apart from that, I'd be willing to p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Schiele wrote:
> On Fri, Mar 10, 2006 at 11:17:53AM +0100, Pascal Bleser wrote:
>> Apart from that, I'd be willing to provide gcc3 packages for SUSE Linux
>> in my repository (for C and C++) but... what would be the best pla
?
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\ <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
_\_v The more things change, the more they stay insane.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFEEVJQr3NMWliFcXcRAljcAJ9qCjiwo6
ge with exactly
the same
version+release is available from more than one installation source ?
Or is it random/unpredictable ?
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\ <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
_\_v The more things change, the
t long. Some other things are pretty
> annoying with it, mainly not being able to exclude symlinks and probably more.
>
> I hope to get something done within one or two weeks.
Thanks again for taking care of this :)
How about filing those modifications to upstream ?
cheers
- --
-o) Pascal Ble
ate trees ;)
Yes but please take care of SUSE <= 10.0 as well.
Not everyone is using factory, and it will take time until everyone is using
10.1.
Thanks for taking care of that bugzilla item.
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\ <[EMAIL PROTECTED]>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richard Bos wrote:
> Op maandag 6 maart 2006 17:26, schreef Pascal Bleser:
>> Would make it very convenient to use from y2pmsh or smart.
>
> And even apt :) The latest version has been extended with repomd support,
> indeed. D
smart.
And IMO it shouldn't be that much work (createrepo .)
thanks
--
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\ <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
_\_v FOSDEM 2006 -- 25+26 February 2006 in Brussels
signature.asc
Description: OpenPGP digital signature
said I'd have a look at it ;)
Any other packager interested ?
(I'll cross-forward this mail to the opensuse-packaging mailing-list as
well - maybe someone over there is interested in maintaining RPMs for
those Horde add-ons)
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.
52 matches
Mail list logo
