In order to help support automation around updating and building KDE packages, we want to have project tags/labels for each package project in Pagure so that automation can discover them as they're added.
Cf. "Modify project" API doc on https://src.fedoraproject.org/api/0/#projects-tab
Added tag "qt5" to the following packages I have recorded as qt5-modules released by qtproject.org : qt5 qt5-qtbase qt5-qtdeclarative qt5-qtscript qt5-qttools qt5-qtxmlpatterns qt5-qtx11extras qt5-qt3d qt5-qtcharts qt5-qtconnectivity qt5-qtdatavis3d qt5-qtdoc qt5-qtgamepad qt5-qtgraphicaleffects qt5-qtimageformats qt5-qtlocation qt5-qtmultimedia qt5-qtnetworkauth qt5-qtquickcontrols qt5-qtquickcontrols2 qt5-qtremoteobjects qt5-qtscxml qt5-qtsensors qt5-qtserialbus qt5-qtserialport qt5-qtspeech qt5-qtsvg qt5-qttranslations qt5-qtvirtualkeyboard qt5-qtwayland qt5-qtwebsockets qt5-qtwebview
Exceptions being: qt5-qtwebchannel (lacking permissions) qt5-qtwebengine (on purpose, this can and should be updated independantly)
Not documented here yet, so I'll propose using tags: kf5 : kde frameworks 5 pkgs (those formally part of upstream kde frameworks releases) plasma : all plasma-related pkgs (those formally part of upstream plasma releases)
Metadata Update from @ngompa: - Issue tagged with: meta
This doesn't appear to be blocking https://pagure.io/fedora-kde/SIG/issue/64 as I've created nightly builds without tags.
Login to comment on this ticket.