Ubuntu
apt package

Unknown package origin after fresh Hardy desktop installation

Bug #188953 reported by Martin Pitt
12
Affects Status Importance Assigned to Milestone
apt (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: apt

I installed Hardy alpha-4 amd64 and booted without network. An apport crash could not be reported because apport claimed that jockey-gtk wasn't a genuine Ubuntu package.

This is due to apt not being able to determine the package origin until I run apt-get update from the network:

$ python -c 'import apt; print apt.Cache()["jockey-gtk"].candidateOrigin'
/usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet
  warnings.warn("apt API not stable yet", FutureWarning)
[component: '' archive: 'now' origin: '' label: '' site '' isTrusted: 'False']

(Note origin is ''). This happens for all other packages, too.

It does not help to run the command as root or to delete /var/cache/apt/*.bin first.

Revision history for this message
Martin Pitt (pitti) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

Curiously enough this *does* work correctly in the life system.

Revision history for this message
Martin Pitt (pitti) wrote :

The installed system is lacking Packages for hardy main. All other Packages files (-updates, -security, universe, etc.) are present.

Revision history for this message
Martin Pitt (pitti) wrote :

Ah, this entry in sources.list seems to explain the missing file:

# Line commented out by installer because it failed to verify:
#deb http://de.archive.ubuntu.com/ubuntu/ hardy main restricted

Revision history for this message
Martin Pitt (pitti) wrote :

Confirming that the python apt call does work for an universe package.

Revision history for this message
Martin Pitt (pitti) wrote :

Attaching installer syslog. This showed that it could not connect properly to archive.u.c. I am not 100% sure why, but since the same problem was reported by someone else on the mailing list, I'm not the only one, and it might not just be unfortunate timing of a network outage.

Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :

Hi Martin, this bug was probably forgot about, just wondered if this is still valid, as it was reported about an alpha Hardy release. Thank you :)

Changed in apt (Ubuntu):
status: New → Incomplete
Revision history for this message
Martin Pitt (pitti) wrote :

It's not a bug in apt, but rather installer related. Also, it was probably just a network glitch.

Changed in apt (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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