Bisect (open)SUSE kernels using prebuilt packages
I have been building an archive of the x86_64/default KOTDs for some months now. It's time to make them available at least internally and write some web frontend to the archive. The frontend could do various things:
- Display all packages for a given branch
- For a given commit, offer the nearest commit for which there are packages (useful when bisecting manually)
- Given a good and bad kernel, start a git-bisect behind the scenes and offer packages for download and testing
No Hackers yet
This project is part of:
Hack Week 11 Hack Week 12
Activity
Comments
-
about 10 years ago by michal-m | Reply
I'm syncing the archive to milos.suse.de. Just do mount milos.suse.de:/srv/kbuild/kerneltest /mnt to have a look. There are three subdirectories, each of them contains further subdirectories with the actual kernel packages: * linux-next, with packages from the linux-next branch of kernel-source.git. These are numbered by the timestamp of each linux-next tree (YYYYMMDD). * mainline: Snapshot of Linus's tree, built in the vanilla branch of * kernel-source.git. For tagged releases, the subdirectories are named after the tag, otherwise, an abbreviation of the upstream commit's SHA1 is used. * suse: These are our kernels from the various maintained branches. The subdirectory names use the abbreviated SHA1 of the commit in kernel-source.git. Only the default flavor (for RT kernels, the rt flavor) is archived.
In all cases, only x86_64 is archived.
-
Similar Projects
Port git-fixup to POSIX shell script and submit to git/git by mcepl
Description
https://github.com/keis/git-fix...
Explore the integration between OBS and GitHub by pdostal
Project Description
The goals:
1) When...