[releng] Issue #8159: Sign modules tagged in f31-modular tag with f31 key
by Mohan Boddu
mohanboddu reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
As part of mass branching, we tagged some module builds into f31-modular tag but they were never signed with F31 key. Here's the list:
>
koji list-tagged f31-modular
Build Tag Built by
---------------------------------------- -------------------- ----------------
ant-1.10-20181122045734.819b5873 f31-modular mizdebsk
avocado-latest-3020190213183323.a5b0195c f31-modular mohanboddu
bat-latest-3020190214090936.e50d0d19 f31-modular ignatenkobrain
container-tools-2018.0-20180529173716.cb85db27 f31-modular lsm5
cri-o-1.11-3020190213213432.a5b0195c f31-modular mohanboddu
django-1.6-3020190213214749.a5b0195c f31-modular mohanboddu
docker-2017.0-20180409180031.3ff668f0 f31-modular lsm5
dwm-latest-3020190218224925.a5b0195c f31-modular releng
exa-latest-3020190214120734.e50d0d19 f31-modular ignatenkobrain
fish-3-3020190219150858.602da195 f31-modular ignatenkobrain
gcsf-master-20180804153258.b33445dc f31-modular ignatenkobrain
ghc-8.6-20181208145539.a5b0195c f31-modular petersen
gimp-2.10-3020190218225005.a5b0195c f31-modular releng
golang-1.10-20180816140129.a5b0195c f31-modular sgallagh
golang-ecosystem-2017.0-20180724154421.cbfb2833 f31-modular sgallagh
hub-pre_release-3020190218225058.a5b0195c f31-modular releng
jmc-latest-3020190218225130.a5b0195c f31-modular releng
kubernetes-openshift_3.10-20180827171820.a5b0195c f31-modular lsm5
libgit2-0.28-3020190218225325.a5b0195c f31-modular releng
lizardfs-devel-20180816140845.a5b0195c f31-modular sgallagh
mariadb-10.4-3020190219161708.a5b0195c f31-modular mschorm
maven-3.5-20180629153919.819b5873 f31-modular mizdebsk
meson-latest-3020190218225437.36245242 f31-modular releng
mongodb-3.6-20180601084133.6c81f848 f31-modular mskalick
mysql-5.6-3020190218225520.a5b0195c f31-modular releng
ninja-latest-3020190218225555.a5b0195c f31-modular releng
nodejs-10-3020190218225610.a5b0195c f31-modular releng
octave-4.4-20181216151019.a5b0195c f31-modular orion
openmpi-2.1-20181215212125.a5b0195c f31-modular orion
perl-5.26-20181207093623.d5758a6e f31-modular ppisar
perl-bootstrap-5.26-20181206150213.a5b0195c f31-modular ppisar
pki-10.6-20180713022640.6c81f848 f31-modular edewata
postgresql-9.6-3020190218225932.a5b0195c f31-modular releng
rawtherapee-devel-20180924154712.a5b0195c f31-modular mattdm
reviewboard-3.0-3020190218230050.65df4ea6 f31-modular releng
ripgrep-latest-3020190214090003.a5b0195c f31-modular ignatenkobrain
ruby-master-20181003163715.a5b0195c f31-modular jaruga
scala-2.10-20180702155503.819b5873 f31-modular mizdebsk
setools-4.2.0-20181121152035.a5b0195c f31-modular vmojzis
skychart-devel-3020190218230149.a5b0195c f31-modular releng
standard-test-roles-3.0-3020190214144451.a5b0195c f31-modular astepano
stratis-1-20181215204600.a5b0195c f31-modular ignatenkobrain
swig-3.0-3020190218230230.a5b0195c f31-modular releng
testmodule-master-3020190116152029.a5b0195c f31-modular mprahl
To fix this, we need to untag these modular from f31-modular tag and tag them into f31-modular-pending tag.
* When do you need this? (YYYY/MM/DD)
ASAP
* If we cannot complete your request, what is the impact?
No composes and everything falls apart.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8159
5 years, 3 months
[releng] Issue #8151: The commendation to do a rebase after branching is
wrong
by Zbigniew Jędrzejewski-Szmek
zbyszek reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
The email that is sent out:
> Fedora 30 has now been branched, please be sure to do a git pull
> --rebase to pick up the new branch
This is wrong. Releng simply creates a new branch, so this has no relation to a rebase. Please just say "git fetch".
> so this means that anything you do for f30 you also have to do in the
> master branch and do a build there
This is also misleading. Any work should be done in master/F31 first, and only then redone in F30. There are exceptions, but the *general* rule is the opposite of what is suggested here. So please say "anything you do for rawhide, you also have to do in the F30 branch and ...".
* When do you need this? (YYYY/MM/DD)
Before next branching.
* When is this no longer needed or useful? (YYYY/MM/DD)
Never.
* If we cannot complete your request, what is the impact?
Nothing, except possibly a few more new contributors being confused.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8151
5 years, 3 months
[releng] Issue #8139: unorphan netatalk
by Andrew Bauer
kni reported a new issue against the project: `releng` that you are following:
``
Please unorphan the following branches for the netatalk package:
- rawhide
- f29
- f28
- epel7
FAS Account: kni
NOTE: This is a duplicate of #7984. However, I was not getting a response.
Thank you.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8139
5 years, 3 months