Mailinglist Archive: opensuse-factory (842 mails)
| < Previous | Next > |
Re: [opensuse-factory] How do changed & new modules enter 'openSUSE'?
- From: Andreas Jaeger <aj@xxxxxxx>
- Date: Fri, 23 May 2008 13:05:13 +0200
- Message-id: <m3zlqh1dsm.fsf@xxxxxxxxxxx>
Linda Walsh <suse@xxxxxxxxx> writes:
That might mean that you have different packages in the environment than
we have. Please double check the BuildRequires line.
Yes, it is.
It might be that more people can help you on the opensuse-packaging
mailing list - or try the IRC channel,
Andreas
--
Andreas Jaeger, Director Platform/openSUSE, aj@xxxxxxx
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Andreas Jaeger wrote:
Are you using the build command?----
All I can say is that it builds without problems. Otherwise you would
not have a src rpm to look at ;-)
Andreas
I understand, I think, your point -- how did the src rpm
get generated if it didn't work.
That's what I'm trying to find out.
I'm using rpmbuild -ba.
That might mean that you have different packages in the environment than
we have. Please double check the BuildRequires line.
I'm doing things that build might not support -- but that
*shouldn't* make a difference. If I find something that is making
the difference, I want to understand why its failing and correct the
problem.
1) My initial purpose was to drain the swamp that had the
alligators in it...no. Wait, that was last week.
1a) Initial purpose was to apply high-performance source
patches to scp/ssh. Goal -- going from current ~3MB/s up to
about 10 times that. Max raw TCP with jumbo packets was over 90MB/s.
So I have a bit of headroom to improve on. Max file transfer with
normal size packets was ~70+MB/s over UDB (CIFS). I hoped NFS/TCP
would do better, but that hasn't been the case so far. Nevertheless,
my most common method of xferring files has been scp/ssh. So that's my
short-term goal.
The patches were available against 4.7 or 5.0 versions of openssh.
suse10.3 has 4.6 in it. I thought I'd have better luck in 'eventual
integration into my systems if I started with a suSE rpm -- I prefer packaging
my software mods in rpms -- they are usually fairly stable ways of reproducing
the software and preserving its source for later.
I checked suse11.0 -- and it is using openssh5.0 -- one of the versions
supported by the patchsets. Discovered via trial&error that applying the
high-perf patches, Then applying the rest of the suse patches generated fewest
conflicts. Only conflict was in a makefile that added suse's libaudit to a
link.
So at this point, I'm building across releases 11.0 src rpm on
10.3 with 3rd party patches. Is this something "build" is designed for?
Yes, it is.
It might be that more people can help you on the opensuse-packaging
mailing list - or try the IRC channel,
Andreas
--
Andreas Jaeger, Director Platform/openSUSE, aj@xxxxxxx
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
| < Previous | Next > |