flatpaks/baobab
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Compare commits

base: flatpaks:stable
Branches Tags
flatpaks:stable
flatpaks:f32
..
compare: flatpaks:f32
Branches Tags
flatpaks:stable
flatpaks:f32

4 commits
stable ... f32

Author SHA1 Message Date
Kalev Lember
3b27a28ba0 end-of-life-rebase: org.gnome.baobab 
The previous commit had a successful build, whic means that we now
correctly have both 'org.gnome.Baobab' (old name) and 'org.gnome.baobab'
(new name) in the repos, which is what we need long term, but more
importantly, as a hotfix to avoid breaking flatpak update for people who
had 'org.gnome.Baobab' already installed.

This commit now adds back the metadata to mark org.gnome.baobab as a
replacement for org.gnome.Baobab. For that to work, we need latest
flatpak-module-tools installed in the OSBS buildroot to actually get a
successful build.

This reverts commit f8ee4d8dd0.
 2020-10-07 09:47:20 +02:00
Kalev Lember
b613543ffc Try 'eol/baobab' instead of 'eol/org.gnome.Baobab' as the repository name 
There appears to be something in 'eol/org.gnome.Baobab' that the
registry is rejecting. Let's try without dots and see if this works
better.

52917228 buildContainer (noarch): open (buildvm-x86-04.iad2.fedoraproject.org) -> FAILED: Fault: <Fault 2001: 'Image build failed. Error in plugin orchestrate_build: {"x86_64": {"tag_and_push": "Command \'[\'skopeo\', \'copy\', \'--authfile=/var/run/secrets/atomic-reactor/v2-registry-dockercfg/.dockercfg\', \'oci:/tmp/tmpmictw3xf/flatpak-oci-image:app/org.gnome.Baobab/x86_64/stable\', \'docker://candidate-registry.fedoraproject.org/eol/org.gnome.Baobab:f32-flatpak-candidate-83731-20201007070318-x86_64\']\' returned non-zero exit status 1."}}. OSBS build id: baobab-f32-c1d99-5'>
 2020-10-07 09:13:52 +02:00
Kalev Lember
f8ee4d8dd0 Temporarily remove end-of-life-rebase 
We need to get flatpak-module-tools updated in the OSBS buildroot and
it's running into some infra issues with networking.
 2020-10-06 01:47:55 +02:00
Kalev Lember
2701d7f223 Rename org.gnome.Baobab to org.gnome.baobab 
The plan is to have org.gnome.Baobab available from the f32 branch, and
org.gnome.baobab from master. Having both the old and new version
available in the repo is needed in order to correctly handle the
rename from org.gnome.Baobab to org.gnome.baobab.
 2020-10-05 19:01:05 +02:00
2 changed files with 45 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

31
baobab.yaml Normal file
View file

@ -0,0 +1,31 @@
---
document: modulemd
version: 2
data:
summary: A graphical directory tree analyzer
description: >-
Baobab is able to scan either specific directories or the whole filesystem, in
order to give the user a graphical tree representation including each directory
size or percentage in the branch. It also auto-detects in real-time any change
made to your home folder as far as any mounted/unmounted device.
license:
module:
- MIT
dependencies:
- buildrequires:
flatpak-runtime: [f32]
platform: [f32]
requires:
flatpak-runtime: [f32]
platform: [f32]
profiles:
default:
rpms:
- baobab
components:
rpms:
baobab:
rationale: Application package
ref: f32
buildorder: 10
...

30
container.yaml
View file

@ -1,20 +1,20 @@
compose:
modules:
- baobab:f32
flatpak:
id: org.gnome.baobab
# Derived from the project's domain name
id: org.gnome.Baobab
name: eol/baobab
end-of-life-rebase: org.gnome.baobab
branch: stable
runtime-name: flatpak-runtime
runtime-version: f44
packages:
- baobab
# Binary to execute to run the app
command: baobab
finish-args: |-
--device=dri
--share=ipc
--socket=fallback-x11
--socket=wayland
tags: []
# Not sandboxed. See 'man flatpak-build-finish'
finish-args: |
--filesystem=host
--filesystem=~/.var/app
--metadata=X-DConf=migrate-path=/org/gnome/baobab/
--share=ipc
--socket=x11
--socket=wayland
--socket=session-bus
--talk-name=org.gtk.vfs.*
--system-talk-name=org.freedesktop.hostname1
--filesystem=xdg-run/gvfs
--filesystem=xdg-run/gvfsd