froxlor Server Management Panel

create and start a push request upstream the openSUSE Leap 42.1 configuration tab

https://github.com/Froxlor/Froxlor/pull/366#discussion_r68934507

http://www.froxlor.org/

Looking for hackers with the skills:

obs

This project is part of:

Hack Week 10 Hack Week 15 Hack Week 14 Hack Week 13 Hack Week 12 Hack Week 11

Activity

  • about 8 years ago: asemen added keyword "obs" to this project.
  • over 10 years ago: asemen liked this project.
  • over 10 years ago: asemen started this project.
  • over 10 years ago: jdsn left this project.
  • over 10 years ago: jdsn started this project.
  • over 11 years ago: asemen originated this project.

  • Comments

    • jdsn
      over 10 years ago by jdsn | Reply

      This project is done already: https://build.opensuse.org/package/show/server:php:applications/froxlor

    • asemen
      over 10 years ago by asemen | Reply

      As the latest version is 0.9.32 and we do have some openSUSE releases the howto documentation has to be updated. And the latest configuration templates for openSUSE has to be created.

    • asemen
      over 10 years ago by asemen | Reply

      Right I am packaging it for openSUSE The developers uses deben and gentoo do not test or install on openSUSE

    • asemen
      about 10 years ago by asemen | Reply

      fixing database problems on initial install

    Similar Projects

    Bootstrap openSUSE on LoongArch by glaubitz

    Description

    LoongArch is a new architecture from China which has its roots in the MIPS architecture. It has been created by Loongson and is already supported by Debian Ports, Gentoo and Loongnix.

    Upstream support for LoongArch is already quite complete which includes LLVM, Rust, Golang, GRUB, QEMU, LibreOffice and many more. In Debian Ports, where the port is called "loong64", more than 95% of the whole Debian archive have been successfully built for LoongArch.

    QEMU support is rather complete and stable such that packages can be built in emulated environments. Hardware can also be requested by Loongson on request for free. Access to real hardware is also provided through the GCC Compile Farm.

    Goals

    The initial goal should be to add LoongArch to OBS and build a minimal set of packages.

    Resources

    Results

    Acknowledgements

    • Thanks to Adrian Schröter and Rüdiger Oertl for the help with setting up the FTP space and OBS project
    • Thanks to Dirk Müller for the input on how to get started with a new port
    • Thanks to Richard Biener for quickly accepting my submit requests to add loongarch64 support to the toolchain


    Switch software-o-o to parse repomd data by hennevogel

    Currently software.opensuse.org search is using the OBS binary search for everything, even for packages inside the openSUSE distributions. Let's switch this to use repomd data from download.opensuse.org


    Learn obs/ibs sync tool by xlai

    Description

    Once images/repo are built from IBS/OBS, there is a tool to sync the image from IBS/OBS to openqa asset directory and trigger openqa jobs accordingly.

    Goals

    Check how the tool is implemented, and be capable to add/modify our needed images/repo in future by ourselves.

    Resources

    • https://github.com/os-autoinst/openqa-trigger-from-obs
    • https://gitlab.suse.de/openqa/openqa-trigger-from-ibs-plugin/-/tree/master?ref_type=heads


    obs-service-vendor_node_modules by cdimonaco

    Description

    When building a javascript package for obs, one option is to use https://github.com/openSUSE/obs-service-node_modules as source service to get the project npm dependencies available for package bulding.

    obs-service-vendornodemodules aims to be a source service that vendors npm dependencies, installing them with npm install (optionally only production ones) and then creating a tar package of the installed dependencies.

    The tar will be used as source in the package building definitions.

    Goals

    • Create an obs service package that vendors the npm dependencies as tar archive.
    • Maybe add some macros to unpack the vendor package in the specfiles

    Resources


    Git CI to automate the creation of product definition by gyribeiro

    Description

    Automate the creation of product definition

    Goals

    Create a Git CI that will:

    • automatically be triggered once a change (commit) in package list is done.
    • run tool responsible to update product definition based on the changes in package list
    • test the updated product definition in OBS
    • submit a pull request updating the product definition in the repository

    NOTE: this Git CI may also be triggered manually

    Resources

    • https://docs.gitlab.com/ee/ci/
    • https://openbuildservice.org/2021/05/31/scm-integration/
    • https://github.com/openSUSE/openSUSE-release-tools