workstation-ostree-config

#26 error building tree in f26: No package matches 'clucene09-core'
Closed Opened by dustymabe.

Closed
Reopen Issue

The atomic workstation config somehow tries to install a package that does not exist. From this log you can see: 

COMMAND: rpm-ostree compose tree --repo=/mnt/koji/compose/ostree/26/ --write-commitid-to=/mnt/koji/compose/branched/Fedora-26-20170515.n.0/logs/x86_64/ostree/ostree-3/commitid.log /mnt/koji/compose/branched/Fedora-26-20170515.n.0/work/ostree-3/config_repo/fedora-ostree-workstation.json
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
No previous commit for fedora/26/x86_64/workstation
Downloading metadata: 4%
Downloading metadata: 5%
Downloading metadata: 100%
rpm-md repository versions:
  Fedora-26-20170515.n.0-Workstation-20170515141626: packages=3008 generated=2017-05-15 14:00:10
Disabled repositories: fedora-26-updates fedora-26 
error: No package matches 'clucene09-core'

I think this is really an issue with the pungi config (comps?). The situation is really weird - for some reason we try to limit the packages that end up in the compose for each product. Then we toss all of that away at release time and just have two gigantic fedora/fedora-updates repos.

AIUI, https://pagure.io/pungi-fedora/blob/master/f/variants-fedora.xml#_103 uses https://pagure.io/fedora-comps/blob/master/f/comps-f26.xml.in

(Using rpm-ostree as is the goal here would radically change this situation as all of a sudden the Workstation has a persistent identity rather than dissolving into a big bag of packages)
Edited by walters

I fixed this and a bunch of other removed packages (e.g. #20 and #21 and #22) for f27.
If you want, you could submit those to f26, but since the workstation group intends to start shipping Atomic Workstation from f27 onwards, I didn't really look at it.

I generally think we should try to have the f26 tree compose as well, unless it ends up being too much work:

A) It allows for showing off some of the power of ostree and flatpak (switch back to test your app with f26..)
B) We still have a ways to go to always have a non-broken rawhide - f26 branch of atomic workstation allows for less adventuresome people to try it out

https://lists.fedoraproject.org/archives/list/desktop@lists.fedoraproject.org/thread/ATX4ILUIREPSRGXE7HLPXJCOWB25KF3O/

Has discussion of an f26 branch.

https://pagure.io/workstation-ostree-config/pull-request/28 is just a cherry-pick of all @puiterwijk 's commits from master. Not tested, but I don't see anything there that would be obviously different f26 vs. f27.

This is fixed, but there are other bugs.

Metadata Update from @walters:
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.