Cannot file an ubiquity bug using apport after performing offline installation
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| apport (Ubuntu) |
Triaged
|
Low
|
Unassigned | ||
| ubiquity (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
After performing an offline installation, I am unable to run apport via ubuntu-bug to file a bug against ubiquity until I first run an apt-get update to update the archive. When an installation is offline, it seems like this list is missing. Apport gives the following error:
dpkg-query: no packages found matching ubiquity
After running the update, everything went fine, and obviously, network access is required to file a bug. However, this interaction is confusing, and if possible should be fixed. Could ubiquity generate the list during an offline install? Could apport run an update if it doesn't find the package in the current list before giving the error? This might just be a 'won't fix'.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: ubiquity (not installed)
ProcVersionSign
Uname: Linux 3.5.0-14-generic x86_64
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
Date: Thu Sep 13 15:07:51 2012
InstallCmdLine: file=/cdrom/
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120913.3)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
| Nicholas Skaggs (nskaggs) wrote | #1 |
| Martin Pitt (pitti) wrote | #2 |
| Changed in ubiquity (Ubuntu): | |
| status: | New → Won't Fix |
| summary: |
- Cannot file a bug using apport after performing offline installation + Cannot file an ubiquity bug using apport after performing offline + installation |
| affects: | apport → apport (Ubuntu) |
| Changed in apport (Ubuntu): | |
| importance: | Undecided → Low |
| status: | New → Triaged |
Right, as Ubiquity is not installed in the target system, it cannot determine the package status/
I don't think we want to try and forge the apt lists in Ubiquity; creating them should be apt's job the first time the computer is online in my opinion, so I tentatively set the ubiquity task to wont fix.