Unable to fetch the Developer Changelog

Bug #119089 reported by bob23450
0
Affects Status Importance Assigned to Milestone
adept (Ubuntu)
Fix Released
Medium
Michael D. Stemle, Jr.

Bug Description

Binary package hint: adept-manager

Using Kubuntu 7.04 up-to-date.
In Adept Manager 2.1 Cruiser (KDE 3.5.6) select any package, the press "Details" button and go to the "Developer Changelog" tab.
After a while the message "Unable to fetch the Developer Changelog.: Host changelogs.ubuntu.com not found" is always shown.
I'm working behind a firewall and I'm connected to internet through a proxy server supporting web protocols (but no socks). I setup this in /etc/apt/apt.conf, ~/.kde/share/config/kioslaverc, /root/.kde/share/config/kioslaverc. I can install/upgrade any package from inside Adept Manager but I'm not able to read changelogs, though the URI http://changelogs.ubuntu.com can be browsed without problems outside Adept Manager.

File /etc/apt/apt.conf:
  Acquire::http::Proxy "http://myproxy:8080";
  Acquire::ftp::Proxy "http://myproxy:8080";

File ~/.kde/share/config/kioslaverc:
  PersistentProxyConnection=false

  [$Version]
  update_info=kioslave.upd:kde2.2/r1,kioslave.upd:kde2.2/r2,kioslave.upd:kde2.2/r3

  [Proxy Settings]
  AuthMode=0
  NoProxyFor=localhost
  Proxy Config Script=
  ProxyType=1
  ReversedException=false
  ftpProxy=http://myproxy:8080
  httpProxy=http://myproxy:8080
  httpsProxy=http://myproxy:8080

File /etc/apt/sources.list:
#
# deb cdrom:[Kubuntu 7.04 _Feisty Fawn_ - Release i386 (20070417)]/ feisty main restricted

deb cdrom:[Kubuntu 7.04 _Feisty Fawn_ - Release i386 (20070417)]/ feisty main restricted
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.

deb http://it.archive.ubuntu.com/ubuntu/ feisty main restricted multiverse
deb-src http://it.archive.ubuntu.com/ubuntu/ feisty main

## Major bug fix updates produced after the final release of the
## distribution.

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## universe WILL NOT receive any review or updates from the Ubuntu security
## team.
deb http://it.archive.ubuntu.com/ubuntu/ feisty universe
deb-src http://it.archive.ubuntu.com/ubuntu/ feisty universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.

## Uncomment the following two lines to add software from the 'backports'
## repository.
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
# deb http://it.archive.ubuntu.com/ubuntu/ feisty-backports main restricted universe multiverse
# deb-src http://it.archive.ubuntu.com/ubuntu/ feisty-backports main restricted universe multiverse

deb http://security.ubuntu.com/ubuntu feisty-security main restricted multiverse
deb-src http://security.ubuntu.com/ubuntu feisty-security main
deb http://security.ubuntu.com/ubuntu feisty-security universe
deb http://archive.ubuntu.com/ubuntu/ feisty-updates restricted main multiverse universe
deb-src http://security.ubuntu.com/ubuntu feisty-security universe

Revision history for this message
Rich Johnson (nixternal) wrote :

I spoke with Michael about this and he says it works, however I haven't had luck with it as of yet. It could very well be because I have dist-upgraded since Dapper or Breezy and there is a hung configuration somewhere.

Changed in adept:
importance: Undecided → Low
status: Unconfirmed → Confirmed
Revision history for this message
Michael D. Stemle, Jr. (manchicken) wrote :

This is a problem with how developer changelogs are being fetched. I'll try to fix this one.

Changed in adept:
assignee: nobody → manchicken
Changed in adept:
importance: Low → Medium
Revision history for this message
Michael D. Stemle, Jr. (manchicken) wrote :

Here's a patch to fix the proxy bit. In order to fix this bug I also had to fix bug #85056. This patch fixes both this bug (119089) and the bug where we had one package fetching the changelog for another package (85056). Enjoy.

Revision history for this message
bob23450 (bzanetti-deactivatedaccount) wrote :

Many thanks Michael, however I need a little help for applying this patch.
I downloaded the latest adept source package (adept-2.1.2ubuntu26.1) from the feisty repositories through the following command:

apt-get source adept

but then I was unable to apply the patch because no "changelog.cpp" , "changelog.h" files were there.
I'm sure I must have done the wrong thing, but I can't figure out what's the right one.
Thanks again.

Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

Adept has changed between feisty and gutsy. The patch above applies to gutsy.

Michael, do you need that sponsored?

Changed in adept:
status: Confirmed → In Progress
Revision history for this message
Michael D. Stemle, Jr. (manchicken) wrote :

Okay, so I'll apply to both bruno and sarah.

Bruno: Yeah, you need to apply the debian patches first. From within the adept path, type `./debian/rules apply-patches` and then apply my patch. That should do the trick.

Sarah: JR usually applies my patches. I don't know if I need sponsored or anything, but I usually just hand out patches.

Revision history for this message
bob23450 (bzanetti-deactivatedaccount) wrote :

I can confirm now that the patch solved the problem in Feisty (at least for me).
Thank you all peoples.

Revision history for this message
Jonathan Riddell (jr) wrote :

Adding this to current gutsy adept it seems to fail to download any changelogs (I'm not using a proxy).

Revision history for this message
bob23450 (bzanetti-deactivatedaccount) wrote :

It seems that the current Adept binary package for Gutsy (2.1.3ubuntu3) is no longer affected by this bug, changelogs are correctly fetched even through a proxy. If I'm not wrong, the source package already includes the fix among the debian patches.

Changed in adept:
status: In Progress → Fix Released
Revision history for this message
bob23450 (bzanetti-deactivatedaccount) wrote :

I re-checked after a long time and I found that the problem is still present in Gutsy (this is the bad news) but the patch given above (proxy_fix.patch) is still working for the current adept package: adept-2.1.3ubuntu17.1 (this is the good news). The patched package correctly retrieves the changelog information through the proxy as configured in KDE (not in /etc/apt.conf). I will check at home whether it works correctly also when no proxy is selected because here I can access the internet *only* through the corporate proxy server, and that's why I do care about it!

Revision history for this message
bob23450 (bzanetti-deactivatedaccount) wrote :

I apologize for the long delay, but at the end I got the patched Adept installed in a Kubuntu desktop 7.10 x86 virtual machine (vmware) hosted on both a PC directly connected to internet and a PC connected through a proxy/firewall. I played with them for a while and both worked fine for me.
I'd appreciate having that patch officially included in future updates.

Thanks.

Revision history for this message
bob23450 (bzanetti-deactivatedaccount) wrote :

Update: Hardy: problem still present :-( patch still apply :-)
I know that most users don't care about this problem because either (1) they don't need the changelog OR (2) they are not restricted behind a proxy OR (3) they use Synaptics or whatever else (1+2+3 probably makes near 100% of the audience), nevertheless IMHO it would take a little effort to put this modification in future binaries.
Can somebody tell me if I can help somehow?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.