From: Michal Marek <mmarek-AlSwsSmVLrQ@public.gmane.org>
To: opensuse-kernel
<opensuse-kernel-stAJ6ESoqRxg9hUCZPvPmw@public.gmane.org>,
linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: linux-next packages for openSUSE
Date: Tue, 22 Feb 2011 18:36:42 +0100 [thread overview]
Message-ID: <4D63F42A.8010803@suse.cz> (raw)
Hi,
If you are using opensuse and want to contribute to kernel development
by testing the linux-next tree, reporting bugs and verifying fixes, you
now have a convenient way:
# zypper addrepo --refresh \
http://download.opensuse.org/repositories/Kernel:/linux-next/standard \
linux-next
# zypper install --from linux-next kernel-vanilla
and then just do 'zypper install kernel-vanilla' (*) every day. The
packages are updated daily by a script and fixed by me as necessary, so
they might be lagging behind at times. The config is previous config +
allmodconfig for new options, so some unwanted debug options can creep
in occasionally. The build logs are here:
https://build.opensuse.org/project/monitor?project=Kernel%3Alinux-next
the configs are here:
http://gitorious.org/opensuse/kernel-source/trees/linux-next/config
Please report installation and config issues to
opensuse-kernel-stAJ6ESoqRxg9hUCZPvPmw@public.gmane.org, everything else should go to the upstream
mailing lists as usual.
Happy testing.
Oh, and there are also builds of latest Linus' tree and latest stable:
http://download.opensuse.org/repositories/Kernel:/vanilla/standard/
http://download.opensuse.org/repositories/Kernel:/stable/openSUSE_Factory/
Michal
(*) The name kernel-vanilla might be a bit confusing; in the suse build
scripts it means "upstream kernel without suse patches", not necessarily
Linus' kernel.
reply other threads:[~2011-02-22 17:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4D63F42A.8010803@suse.cz \
--to=mmarek-alswssmvlrq@public.gmane.org \
--cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=opensuse-kernel-stAJ6ESoqRxg9hUCZPvPmw@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).