Enhance Staging Project process: reduce the gap between Letter staging and ADI staging
a project by mlin7442
Updated about 8 years ago. No love.

We have a known defect exists in Staging Project process, according to the staging project design(in-ring/non-ring), the requests of a application stack can be dispatched to letter staging and adi staging both, in case the request staged in adi staging relies the request staged in letter staging which may causes sometimes the request in adi staging will not be checked-in at the same round, this leads that application stack have different version in TW and those package had request left in adi staging may does not work well as version unmatched to other library. We see this issue happened on Qt5 stack; KDE Applications, etc. For example: a Qt5 stack update, libqt5-qtbase will be staged in a letter staging however libqt5-qtwebview will be staged in a adi staging, once libqt5-qtbase be accepted that libqt5-qtwebview won't be accept in the same round due to it can not be built before libqt5-qtbase merged to Factory but after - 2-phase update. Therefore we need a way to handle those cases to reduce the gap between Letter staging and ADI staging.

The concept of this idea:

1) osc staging connect REQUEST REQUEST_IN_ADI which connected two requests between letter and adi, the metadata in the letter/adi staging can be

connected: { id: XXX, package: XXX, project: XXX }

2) create package link in the adi staging per the command above to adopt the requirement of other packages can be built.

3) while accept command accepting that letter staging, the command have to check that relevant adi staging, if that adi staging is ok to accept then accept command should to do that.

4) to protect this process, unselect, select --move and adi --move have to remember update the metadata and wipes the package container.

Join this project

Looking for hackers with the skills:

stagingproject python

This project is part of:

Hack Week 16

Activity

  • about 8 years ago: mlin7442 added keyword "python" to this project.
  • about 8 years ago: mlin7442 added keyword "stagingproject" to this project.
  • about 8 years ago: mlin7442 started this project.
  • about 8 years ago: mlin7442 originated this project.


    • Comments

    Be the first to comment!

    Similar Projects

    Song Search with CLAP by gcolangiuli

    Description

    Contrastive Language-Audio Pretraining (CLAP) is an open-source library that enables the training of a neural network on both Audio and Text descriptions, making it possible to search for Audio using a Text input. Several pre-trained models for song search are already available on huggingface

    SUSE Hackweek AI Song Search

    Goals

    Evaluate how CLAP can be used for song searching and determine which types of queries yield the best results by developing a Minimum Viable Product (MVP) in Python. Based on the results of this MVP, future steps could include:

    • Music Tagging;
    • Free text search;
    • Integration with an LLM (for example, with MCP or the OpenAI API) for music suggestions based on your own library.

    The code for this project will be entirely written using AI to better explore and demonstrate AI capabilities.

    Result

    References

    Update M2Crypto by mcepl

    There are couple of projects I work on, which need my attention and putting them to shape:

    Goal for this Hackweek

    • Put M2Crypto into better shape (most issues closed, all pull requests processed)
    • More fun to learn jujutsu
    • Play more with Gemini, how much it help (or not).
    • Perhaps, also (just slightly related), help to fix vis to work with LuaJIT, particularly to make vis-lspc working.

    HTTP API for nftables by crameleon

    Background

    The idea originated in https://progress.opensuse.org/issues/164060 and is about building RESTful API which translates authorized HTTP requests to operations in nftables, possibly utilizing libnftables-json(5).

    Originally, I started developing such an interface in Go, utilizing https://github.com/google/nftables. The conversion of string networks to nftables set elements was problematic (unfortunately no record of details), and I started a second attempt in Python, which made interaction much simpler thanks to native nftables Python bindings.

    Goals

    1. Find and track the issue with google/nftables
    2. Revisit and polish the Go or Python code (prefer Go, but possibly depends on implementing missing functionality), primarily the server component
    3. Finish functionality to interact with nftables sets (retrieving and updating elements), which are of interest for the originating issue
    4. Align test suite
    5. Packaging

    Resources

    • https://git.netfilter.org/nftables/tree/py/src/nftables.py
    • https://git.com.de/Georg/nftables-http-api (to be moved to GitHub)
    • https://build.opensuse.org/package/show/home:crameleon:containers/pytest-nftables-container

    Results

    • Go nftables issue was related to set elements needing to be added with different start and end addresses - coincidentally, this was recently discovered by someone else, who added a useful helper function for this: https://github.com/google/nftables/pull/342.

    Side results

    Upon starting to unify the structure and implementing more functionality, missing JSON output support was noticed for some subcommands in libnftables. I am submitting patches as needed:

    • https://lore.kernel.org/netfilter-devel/20251203131736.4036382-2-georg@syscid.com/T/#u

    Improvements to osc (especially with regards to the Git workflow) by mcepl

    Description

    There is plenty of hacking on osc, where we could spent some fun time. I would like to see a solution for https://github.com/openSUSE/osc/issues/2006 (which is sufficiently non-serious, that it could be part of HackWeek project).

    Enhance git-sha-verify: A tool to checkout validated git hashes by gpathak

    Description

    git-sha-verify is a simple shell utility to verify and checkout trusted git commits signed using GPG key. This tool helps ensure that only authorized or validated commit hashes are checked out from a git repository, supporting better code integrity and security within the workflow.

    Supports:

    • Verifying commit authenticity signed using gpg key
    • Checking out trusted commits

    Ideal for teams and projects where the integrity of git history is crucial.

    Goals

    A minimal python code of the shell script exists as a pull request.

    The goal of this hackweek is to:

    • DONE: Add more unit tests
      • New and more tests can be added later
    • Make the python code modular
    • DONE: Add code coverage if possible

    Resources