After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 728690 - generic ostree.versionlist attribute?
generic ostree.versionlist attribute?
Status: RESOLVED WONTFIX
Product: ostree
Classification: Infrastructure
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: OSTree maintainer(s)
OSTree maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-04-21 22:23 UTC by Colin Walters
Modified: 2018-08-17 18:58 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Colin Walters 2014-04-21 22:23:42 UTC 
Right now upgrade refuses chronological downgrades.

However, there's no reason we couldn't optionally enforce semantic versions.  One thing that occurred to me is to support a generic "ostree.version" or "ostree.versionlist" metadata on commits, and have ostree check that.

If it was ostree.versionlist, we could *potentially* explode the rpmdb versions into there.  It would be a noticeable space hit though.

Another option is to have the tree builder synthesize a version from something like the package repository timestamps.  What we'd be accomplishing with this over the pure commit timestamp is that for a project like fedora-atomic where there are multiple base trees, then each commit would have an equal timestamp, so "ostree admin switch" could also enforce some kind of versioning.
Comment 1 André Klapper 2018-08-17 18:58:43 UTC 
OSTree has moved to Github a while ago.
Furthermore, GNOME Bugzilla will be shut down and replaced by gitlab.gnome.org.

If the problem reported in this Bugzilla ticket is still valid, please report it to https://github.com/ostreedev/ostree/issues instead. Thank you!

Closing this report as WONTFIX as part of Bugzilla Housekeeping.