#50 Make rawhide "version" usable in pkgdb collections
Opened 4 years ago by kalev. Modified 3 years ago

Right now the rawhide entry is:

{
  "allow_retire": true,
  "branchname": "master",
  "date_created": "2014-05-14 12:36:15",
  "date_updated": "2014-05-14 12:36:15",
  "dist_tag": ".fc24",
  "koji_name": "rawhide",
  "name": "Fedora",
  "status": "Under Development",
  "version": "devel"
},

However, "devel" isn't particularly useful for client side tools. I'd like to have something that can be passed to 'dnf update --releasever='. Would it be possible to change it to say "rawhide" instead of "devel", please? That would work fine when passed to --releasever.


On a second thought, I'd also need to know the numeric version, something that I can match up with VERSION_ID in /etc/os-release. How about changing the "version" field in pkgdb to be a numeric entry, so that current rawhide would be 24, and then add another field, called releasever, which would say "rawhide"?

Instead of:
{
...

"version": "devel"

},

It would be:

{
...

"version": 24
"releasever": "rawhide"

},

This would allow using "version" to match up with VERSION_ID in /etc/os-release, and keep "releasever" separate that can be passed to dnf --releasever=

I just realized that version has to be a string to support rpm style versions with dots, like "23.1" and "23.2" :)

Nevertheless, it would be great to have separate version and releasever fields.

Sounds doable, just to be clear, what would be the releasever for the other ones? f23, f22?

Replying to [comment:3 pingou]:

Sounds doable, just to be clear, what would be the releasever for the other ones? f23, f22?

I think it should be "22", "23", "24", "rawhide", so that I can have something that works as an argument to 'dnf update --releasever='

Login to comment on this ticket.

Metadata