Bug 1301702

Summary: some issues with copr repos
Product: [Fedora] Fedora Reporter: Sergio Basto <sergio>
Component: PackageKitAssignee: Richard Hughes <rhughes>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: jonathan, klember, rdieter, rhughes, smparrish
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 11:07:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Sergio Basto 2016-01-25 17:58:05 UTC
Description of problem:
sometimes pkcon fails to refresh with an error for an copr repo .


How reproducible:
pkcon refresh force                                        
Refreshing cache              [=========================]         
Waiting for authentication    [=========================]         
Starting                      [=========================]         
Loading cache                 [=========================]         
Downloading repository information[=========================]         
Finished                      [=========================]         
Fatal error: Error when getting information for file '/var/cache/PackageKit/metadata/sergiomb-buildsforF21/repodata/ee87c64252e755f0ac964eca50da87e42daacad34d4dfdfcbd7620b9f359d5b8-appstream.xml.gz': No such file or directory

Version-Release number of selected component (if applicable):

PackageKit-1.0.11-1.fc23.x86_64


Actual results:
Fatal error: Error when getting information for file '/var/cache/PackageKit/metadata/sergiomb-buildsforF21/repodata/ee87c64252e755f0ac964eca50da87e42daacad34d4dfdfcbd7620b9f359d5b8-appstream.xml.gz': No such file or directory

Expected results:

refresh pkcon

Additional info:
dnf config-manager --set-disable sergiomb-buildsforF21
pkcon refresh force
dnf config-manager --set-enable sergiomb-buildsforF21
pkcon refresh force

is one workaround , that fixes the problem until next time , it happens often.

I think this issue prevents pkcon notify me for updates .

Comment 1 Sergio Basto 2016-09-20 07:13:25 UTC
ATM I got Fatal error: Error when getting information for file '/var/cache/PackageKit/23/metadata/sergiomb-vboxfor23/repodata/cea16b8c526b0de3a6a092298431fcdf8076939cca934bd9f1f6c8c4462ac27e-appstream.xml.gz': No such file or directory
 
but after a while I found that copr is down because he have one Planned Outage: fedora infra cloud / copr - 2016-09-20 06:00 UTC

PackageKit-1.1.3-2.fc23.x86_64 

So maybe this is not a real bug and just happens when copr is down , closing as not a bug

Comment 2 Sergio Basto 2016-10-27 22:32:24 UTC
I got this issue again and was fixed with: 

dnf config-manager --set-disable sergiomb-kde4for23 
pkcon refresh
dnf config-manager --set-enable sergiomb-kde4for23 
pkcon refresh

Comment 3 Sergio Basto 2017-01-06 00:17:22 UTC
Fatal error: Error when getting information for file ..., appears again in F24 
just set enable (even if it is enabled) the repo in question solves the issue. why dnf config-manager --set-enable fix the pkcon refresh ? 

For example: 

dnf config-manager --set-enable sergiomb-builds_for_Stable_Releases
pkcon refresh

Comment 4 Fedora End Of Life 2017-07-25 19:51:03 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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.

Comment 5 Fedora End Of Life 2017-08-08 12:42:31 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.

Comment 6 Sergio Basto 2017-09-30 19:32:18 UTC
I'd like understand why run 

dnf config-manager --set-enable on copr repo fixes the packagekit error .

Comment 7 Fedora End Of Life 2017-11-16 18:53:34 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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.

Comment 8 Fedora End Of Life 2017-12-12 11:07:03 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.