error when trying to install application through add/remove

[Daniel Stone]

Binary package hint: yelp

I receive an error when attempting to install application Jokosher using add/remove programs
I have included several screen shots for diagnosing the issue
I can install but it says not suthenticated and I can get the package from their website and get message that installing through wrong method by gdebi
I have a system with all updates installed

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/yelp
NonfreeKernelModules: nvidia
Package: yelp 2.25.1-0ubuntu5
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: yelp
Uname: Linux 2.6.28-15-generic x86_64

[Daniel Stone (danielstone)]

This is this package that is tried when error occurs do not see in previous installs and gdebi points to old but this is all in screen shots

[Laszlo Pandy (laszlok)]

The Gdebi message you see is the correct behaviour. If you install from a website, it will let you know there is an older version is the repositories. It is your choice to install the newer version if you like.

But you are right about the authentication. Jokosher should be an authenticated package, as well as python-setuptools and gnonlin. Maybe you have a missing authentication key. In the software dialog look what it says in the authentication tab.

[Laszlo Pandy (laszlok)]

I mean the "Authentication" tab in the "Software Sources" dialog.

[Daniel Stone (danielstone)]

here is an image of that

[Daniel Stone (danielstone)]

I think that this may have something to do with todays update that did alot of open office updates after or since it doesn't even do the updates correct this is because the updates list is i ca hoots with ubuntu's site at https://help.ubuntu.com/community/Repositories/Ubuntu and it appears to hang so maybe someone did an oops on the new build
take a peak at the screenshot7 it did this about four times... still won't complete

[Laszlo Pandy (laszlok)]

This is a different problem you are talking about. Before you said it installed correctly but was not authenticated. You can just ignore the authentication for jokosher if you know it is the correct package and not something malicious.

[Duane Hinnen (duanedesign)]

Daily Struggle,
looking at your screenshot-7.png I noticed you have repositories from two Ubuntu releases (Intrepid & Jaunty). I suspect you might have some repositories that are giving you trouble. I could not reproduce your problem downloading Jokosher. You might want to start back at square one with a default sources.list and go from there. I am not convinced this is a bug. I think you will get a quicker resolution to your problem if you post in launchpad Questions.
https://answers.launchpad.net/ubuntu/+addquestion
-Dh

[Daniel Stone (danielstone)]

ok duane from the link I gave https://help.ubuntu.com/community/Repositories/Ubuntu which is what I see the data authenticating from so I will put a screenshot9 for you to compare and the reference to this came from the Ubuntu Documentation > Community Documentation > RepositoriesUbuntu on the ubuntu site
I understand that I may have done updates but add remove has never given this warning for any packages before.
And it is jokosher that the issue exist with so I believe that jokosher or the add remove is at fault
By the way why would I need to start from square one and what are you saying is intrepid because the numbers and the links are the same in the switches I can turn on or off which are used
I do believe that this either needs an explanation or be marked as a valid bug because why would the program be in the list(screenshot2) if it says cant verify(screenshot3)??
So to me either the link that I reference repositories is wrong or the package in the list does not authenicate I am willing to ask a question but this is more a bug than a question maybe you should look closer..

[Daniel Stone (danielstone)]

As I stated this was an issue I did nothing to my repositories and it ran install correctly but the problem was and is solved
Steps I actually had to hard stop/start (shutdown) machine and start normally maybe this as discussed before had something to do with an Open Office Update today
Don't know why but it works fine now made no changes but as you can see the issue was existent from the screenshots recorded