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

Looking for hackers with the skills:

git web scripting

This project is part of:

Hack Week 11 Hack Week 12

Activity

  • over 10 years ago: david_chang liked this project.
  • over 10 years ago: mkubecek liked this project.
  • over 10 years ago: joeyli liked this project.
  • about 11 years ago: sndirsch liked this project.
  • about 11 years ago: michal-m added keyword "git" to this project.
  • about 11 years ago: michal-m added keyword "web" to this project.
  • about 11 years ago: michal-m added keyword "scripting" to this project.
  • about 11 years ago: michal-m originated this project.

  • Comments

    • michal-m
      about 11 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.

    • michal-m
      about 11 years ago by michal-m | Reply

      The archive on milos.suse.de is complete. Anybody wants to write a web frontend to it? :)

    Similar Projects

    Create a page with all devel:languages:perl packages and their versions by tinita

    Description

    Perl projects now live in git: https://src.opensuse.org/perl

    It would be useful to have an easy way to check which version of which perl module is in devel:languages:perl. Also we have meta overrides and patches for various modules, and it would be good to have them at a central place, so it is easier to lookup, and we can share with other vendors.

    I did some initial data dump here a while ago: https://github.com/perlpunk/cpan-meta

    But I never had the time to automate this.

    I can also use the data to check if there are necessary updates (currently it uses data from download.opensuse.org, so there is some delay and it depends on building).

    Goals

    • Have a script that updates a central repository (e.g. https://src.opensuse.org/perl/_metadata) with metadata by looking at https://src.opensuse.org/perl/_ObsPrj (check if there are any changes from the last run)
    • Create a HTML page with the list of packages (use Javascript and some table library to make it easily searchable)

    Resources


    go-git: unlocking SHA256-based repository cloning ahead of git v3 by pgomes

    Description

    The go-git library implements the git internals in pure Go, so that any Go application can handle not only Git repositories, but also lower-level primitives (e.g. packfiles, idxfiles, etc) without needing to shell out to the git binary.

    The focus for this Hackweek is to fast track key improvements for the project ahead of the upstream release of Git V3, which may take place at some point next year.

    Goals

    Stretch goals

    Resources

    • https://github.com/go-git/go-git/
    • https://go-git.github.io/docs/