Bug 995723

This is an issue with the packagekit yum backend, I remmember seeing this issue before, not sure if it was fixed yet. Iirc there is an workaround.

*** Bug 1007933 has been marked as a duplicate of this bug. ***

*** Bug 1030716 has been marked as a duplicate of this bug. ***

Confirmed, apper simply reports the error from the backend, in this case,

    case Transaction::ErrorRepoNotFound :
        return i18n("The remote software origin name was not found.\n"
                    "You may need to enable an item in Software Origins.");

and,

void PkTransaction::installFiles()
{
    setupTransaction();
    Transaction::installFiles(d->files, d->flags);
    if (internalError()) {
        showSorry(i18np("Failed to install file",
                        "Failed to install files", d->files.size()),
                  PkStrings::daemonError(internalError()));
    }
}

should I just silence apper reporting these backend errors?

on Fedora 20 Beta I have this issue when I try to install local rpm from apper
for example (rpmfusion, mysql-workbench)

Additional info:
I have encountered the same bug on fedora 19.
Although the failure message "cannot find repo local" is returned,
the package is successfully installed without other problems.
Seems to be a packagekit yum backend bug.

This also affects installation of Google-packaged software such as Chrome. Is there a way to work around it in the package?

This happens in F20 too,I think we should raise its priority, I think everybody using Fedora and installs Chrome, of Flash Player, or any 3rd party rpm will face it.

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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

I ran the following test on Fedora 20

- use Firefox to go to Koji (http://koji.fedoraproject.org)
- search for gnucash
- on the gnucash page click on the link for the 2.6.5-1.fc20 build
- on the page that appears click on the download link after the x86_64 rpm

The download window gives me the option to use apper to install the package. That's the option I select.
When the download finishes I get a small dialog asking if I want to install the package (in Dutch: Wilt u dit bestand installeren?)
I click install.
Immediatel a second dialog pops up telling me the installation failed (in Dutch: Installeren van bestand is mislukt). Reason is an unknown error.

The package itself is successfully downloaded as /tmp/gnucash-2.6.5-1.fc20.x86_64.rpm.
And using yum localinstall I can install it without any issue.

Conclusion: this issue is not fixed in Fedora 20, so I have changed the version te keep the bug open.

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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

Still affecting Apper in F22

Tested F21 today as well. Not fixed either. I'll bump the version to 22.

Same problem in Fedora 23 (?)

1) Go to http://rpmfusion.org/Configuration 
2) Click on the "free" link for "rpmfusion free repositories"

The link will start "apper" and configure the repositories (asks for root password).

The Apper starts to download the remote repository. This takes a bit. Then the operation breaks off with:

>> Failed to find rpmfusion-free-release:23-0.1;noarch;local"

Those semicolons are very fishy...

The package "rpmfusion-free-release-23.0.1.noarch" actually has been installed ok.

Bumping as per comment #15.

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.

This is still current with the Apper in F24, at least. I'll have to recheck with F25/Rawhide.

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.

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.