From: Jeff Mahoney <jeffm@suse.com>
To: doiggl@velocitynet.com.au
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: Nightly Builds
Date: Mon, 30 Jun 2008 10:55:04 -0400 [thread overview]
Message-ID: <4868F3C8.2090006@suse.com> (raw)
In-Reply-To: <23784.202.168.22.19.1214826598.squirrel@webmail.velocity.net.au>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
doiggl@velocitynet.com.au wrote:
> Hello,
> I Installed the file (reiser4-0.1-23.1.x86_64.rpm) but it has a problem it
> contains no files that I can see and it was only 1858 bytes long.
That's not what you want. That's an artifact of the KMP process. You
want reiser4-kmp-<flavor>
- -Jeff
> # rpm -qlp reiser4-0.1-23.1.x86_64.rpm
> warning: reiser4-0.1-23.1.x86_64.rpm: Header V3 DSA signature: NOKEY, key
> ID 29ca2faf
> (contains no files)
>
> # rpm -qa | grep -i reiser4
> reiser4progs-1.0.6-3.5
> reiser4-0.1-23.1
>
> # rpm -qa | grep -i kernel
> kernel-syms-2.6.25.5-1.1
> nfs-kernel-server-1.1.2-9
> kernel-default-2.6.25.5-1.1
> kernel-xen-2.6.25.5-1.1
> kernel-source-2.6.25.5-1.1
> linux-kernel-headers-2.6.25-8.1
>
> Jeff wrote:
>> No, you should be all set now, just download the same file you did
>> before. The problem was that I was trying to do double indirection with
>> the compliation (external kernel dir and external module dir), and it
>> ended up only packaging the last flavor to be built, which was -xen.
>>
>> Now that's fixed so downloading from
>> http://download.opensuse.org/repositories/drivers:/filesystems/openSUSE_11.0/
>> will contain the correct files.
>>
>> - -Jeff
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iEYEARECAAYFAkho88gACgkQLPWxlyuTD7JwUACeIZfcGgwJGZ4sfoXjtPScJ3Y8
zvQAnjJpnzkqqFmmf/v/y7FeMmp2VSXe
=1wUC
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-06-30 14:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 19:42 Nightly Builds J. Todd Slack
2008-06-20 19:57 ` Jeff Mahoney
2008-06-22 14:51 ` doiggl
2008-06-22 16:06 ` Jeff Mahoney
2008-06-23 4:16 ` doiggl
2008-06-23 14:13 ` Jeff Mahoney
2008-06-24 14:44 ` doiggl
2008-06-24 14:58 ` Jeff Mahoney
2008-06-25 12:59 ` doiggl
2008-06-25 16:11 ` Jeff Mahoney
2008-06-28 7:34 ` doiggl
2008-06-28 15:23 ` Jeff Mahoney
2008-06-29 14:02 ` doiggl
2008-06-29 19:02 ` Jeff Mahoney
2008-06-30 11:49 ` doiggl
2008-06-30 14:55 ` Jeff Mahoney [this message]
2008-07-01 13:48 ` doiggl
2008-07-09 15:00 ` doiggl
2008-07-09 15:11 ` Jeff Mahoney
2008-07-10 15:21 ` doiggl
2008-07-10 15:51 ` Jeff Mahoney
[not found] ` <27342.202.168.22.19.1215840119.squirrel@webmail .velocity.net.au>
2008-07-12 5:21 ` doiggl
2008-07-12 7:10 ` Jeff Mahoney
2008-07-13 14:21 ` doiggl
2008-07-13 17:00 ` Edward Shishkin
2008-07-14 13:39 ` doiggl
2008-07-14 18:21 ` stroetmann
2008-07-14 20:51 ` Edward Shishkin
2008-07-14 20:54 ` J. Todd Slack
2008-07-14 21:20 ` Volker Armin Hemmann
2008-07-14 21:53 ` Christian Stroetmann
2008-07-14 21:42 ` Christian Stroetmann
2008-07-14 22:26 ` Volker Armin Hemmann
2008-07-14 22:37 ` Christian Stroetmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4868F3C8.2090006@suse.com \
--to=jeffm@suse.com \
--cc=doiggl@velocitynet.com.au \
--cc=reiserfs-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.