|
an
invention
by
jdelvare
I would like to change the way "quilt setup" is implemented.
At the moment, we call rpmbuild and intercept the calls to tar and patch in order to record the location where archives are extracted and the order and options of the patches which apply to them. Then we replay that record to create our own quilt-compatible source tree.
Updated
about 5 years
ago.
10 hacker ♥️.
|
|
a
project
by
fsundermeyer
DAPS, the "DocBook Authoring and Publishing Suite" provides a tool set for easy creation and publication of DocBook sources on Linux. DAPS lets you create HTML (incl. webhelp), PDF, EPUB, man pages, and other formats with a single command. DAPS is used and developed by teh SUSE documentation team.
The official DAPS release is 1.1.7. SUSE internally DAPS 2.0 rc2 has been released. A few issues need to be fixed (mainly closing open bugs and adding missing test cases). The goal of this project is to fix these issues, so DAPS 2.0 can be publicly released.
Updated
about 2 years
ago.
6 hacker ♥️.
|
|
an
invention
by
dguitarbite
OpenSUSE support for OpenStack Training Labs
Updated
about 5 years
ago.
6 hacker ♥️.
|
|
a
project
by
locilka
Yast team has a great experience in automating tasks that can be done by machines in order to save time that can be used better. We usually use Jenkins for running these jobs.
Why to use automation?
Updated
about 2 years
ago.
4 hacker ♥️.
|
|
an
idea
by
sleep_walker
Current status
Updated
about 5 years
ago.
1 hackers ♥️.
Has no hacker:
grab it!
|
|
a
record
by
sleep_walker
Sometimes we get from Labs team patch from kernel-source.git. It is nice as it contains not only patch against expended kernel tree, but also changes series.conf and changes file and identical patch is in GIT. Unfortunately it always leads to conflicts, tarballs need to be extracted and then repacked so most of the job is done manually.
I'd like to create tool which would help apply such patch automatically whenever it is possible.
Updated
about 5 years
ago.
1 hackers ♥️.
Has no hacker:
grab it!
|
|
a
project
by
bmwiedemann
In https://github.com/SUSE-Cloud/automation/ we already have mkcloud, which can setup a whole SUSE Cloud on a single host for testing. However, it would be cool, if (instead of a single machine) we could use cloud.suse.de with its capability to add extra networks as requested.
This can be pretty easy, as much of the mkcloud code is about making libvirt do the right thing
Updated
about 2 years
ago.
3 hacker ♥️.
|
|
an
invention
by
psimons
We have various individual tools to automate parts of the Haskell packaging process, like cabal-rpm, but those tools aren't integrated into a fully automated system that keeps Haskell packages up-to-date with as little human intervention as possible. I would like to build that system. Stackage provides us with an accurate list of packages and versions that are known to work together well, and there are basically two flavors: the nightly snapshot (bleeding edge) and the LTS release (stable API). The former is appropriate for Tumbleweed, IMHO, and the latter is appropriate for stable releases like SLE or Leap.
Now, we can use cabal-rpm to generate spec files automatically for all packages in a Stackage release and check them into OBS. The process does need some tweaking, however, because cabal-rpm generates spec files that don't always work well for SUSE. We could (a) branch cabal-rpm and add SUSE-specific know-how to remedy that issue or we could (b) maintain a set of patches that adapt the generated spec files to our needs. Once the Stackage releases are available in an OBS development project, we need another automated process that submits all updated packages to openSUSE:Factory, etc.
Updated
about 5 years
ago.
3 hacker ♥️.
|
|
a
project
by
dguitarbite
Introduction
Updated
about 7 years
ago.
No love.
|
|
a
project
by
fsundermeyer
DAPS is the tool used by the SUSE documentation team to generate HTML, ePUB, PDF, ... output of the SUSE manuals from DocBook XML sources. It uses the suse-xsl-stylesheets for this purpose.
Currently three different suse-xsl-stylesheet brands exist: SUSE, DAPS, openSUSE. Branding is done by adjusting the xsl-stylesheets directly. It would be desirable to be able to easily change the branding, e.g. via a simple config file in the style of /etc/sysconfig files, since most people cannot hack XSLT. This is also the number one enhancement request we get from DAPS users outside of SUSE.
Updated
about 2 years
ago.
3 hacker ♥️.
|
Release DAPS 2.0
Automate to save time for hacking
write mkcloudcloud - a nested cloud setup software
Add branding to DAPS and the suse-xsl-stylesheets
