#6396 critpath needs help
Closed: Fixed 6 years ago Opened 8 years ago by kevin.

When we setup critpath it was a collection of packages that were critical to the things we were shipping, so we could have higher requirements on these things in the updates system and possibly someday run more tests on them, etc.

Right now:

  • Updating critpath is broken. The script that pulls packages from comps doesn't work and depends on yum.

  • Updating critpath is manual. It takes someone to remember to do it, which no one does.

  • Updating critpath hasn't happened in a long time. (due to the above)

  • critpath reflects the critical packages... as of Fedora 20 (before we started doing the products). So, we have critpath groups for all the desktops that were on the install dvd (which we no longer make) and nothing at all for cloud or server or atomic or docker or anything related to those.

So, we need to:

  • Fix generation of packages for critpath.

  • Fix the data it uses so it reflects the things we actually want to be critpath.

  • Automate it so it updates without humans being involved.


I tried figure out if not a pkgdb issue and the resume is here: https://github.com/fedora-infra/pkgdb2/issues/339

Its there because gstreamer-plugins-bad-free is listed and that depends on it.

3 days ago, I received these notifications:

ausil unset the critpath flag on the libcdaudio package (f24)

ausil unset the critpath flag on the libcdaudio package ()

After edited libcdaudio update on https://bodhi.fedoraproject.org/updates/FEDORA-2016-a487bfdd72 ,
bodhi and notifications doesn't have critpath anymore ...

kevin, maybe you are right, libcdaudio was on critpath because gstreamer-plugins-bad-free requires it.
That is the information that I can give you, if gstreamer-plugins-bad-free should be in critpath ? , if gstreamer-plugins-bad-free should use libio instead etc etc I don't know.

Best regards.

Metadata Update from @kevin:
- Issue set to the milestone: Fedora 24 Final

7 years ago

Everything requested has been done. Closing as Fixed.

Note that there is one issue with critpath still being worked: https://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/us/1002?kanban-status=145

Metadata Update from @syeghiay:
- Issue close_status updated to: None

6 years ago

Metadata Update from @syeghiay:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

Login to comment on this ticket.

Metadata