Bug 1565257

Does it help if you run repoclosure command with --forcearch switch?
Like: $ dnf repoclosure --forcearch aarch64

Marek,

I implemented the forcearch setting in my rewrite of spam-o-matic using DNF via its config object info, and it still didn't work.

See: https://pagure.io/releng/pull-request/7407

Is there a way how can I reproduce and test this bug? I suppose, I will need to download this aarch64 repo, won't I?
https://kojipkgs.fedoraproject.org/compose/branched/latest-Fedora-28/compose/Everything/aarch64/os/
Can I see how exactly do you run repoclosure command?

Marek,

Pungi is using https://pagure.io/pungi/blob/master/f/pungi/wrappers/repoclosure.py to generate the repoclosure.

I tried your command with one little change - I replaced --arch with --forcearch (see  http://dnf-plugins-core.readthedocs.io/en/latest/repoclosure.html):

$ dnf repoclosure --forcearch=aarch64 --repofrompath=r,https://kojipkgs.fedoraproject.org/compose/branched/latest-Fedora-28/compose/Everything/aarch64/os/ --repo=r --check=r

The results I got seemed to be pretty reasonable. There is only one catch here: --forcearch option can not be used more than once, so you can check only one architecture a time. Is this viable for you?

Btw, I'm working on making "dnf repoclosure" more compatible with the yum. Basically I'm thinking about removing --check option and returning --lookaside option with the same meaning as in the yum. 
https://github.com/rpm-software-management/dnf-plugins-core/pull/255

This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

This bug appears to have been reported against 'rawhide' during the Fedora 30 development cycle.
Changing version to '30.

Did information from comment 5 resolved the issue?

This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.

This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Looks like this got re-discovered, reported to pungi, and fixed:

https://pagure.io/pungi/issue/1562
https://pagure.io/pungi/c/e2b3002726e6b25f2e8aa15d4ce7256fecd3ce4e

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days