package libgnet2.0-0 (not installed) failed to install/upgrade: cannot access archive: No such file or directory

Bug #551808 reported by Matthew
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnet (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Was downloading Educational Desktop for Ubuntu.
It was applying changes.
This error message appeared.

ProblemType: Package
Architecture: i386
Date: Tue Mar 30 16:42:49 2010
DistroRelease: Ubuntu 9.10
ErrorMessage: cannot access archive: No such file or directory
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: libgnet2.0-0 (not installed)
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
SourcePackage: gnet
Title: package libgnet2.0-0 (not installed) failed to install/upgrade: cannot access archive: No such file or directory
Uname: Linux 2.6.31-20-generic i686

Revision history for this message
Matthew (mattytheratty) wrote :
Revision history for this message
Monkey (monkey-libre) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in gnet.
For future reference you might be interested to know that a lot of applications have bug reporting functionality built in to them. This can be accessed via the Report a Problem option in the Help menu for the application with which you are having an issue. You can learn more about this feature at https://wiki.ubuntu.com/ReportingBugs.

affects: ubuntu → gnet (Ubuntu)
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thanks for your report.

Are you using a local mirror, local cache, a proxy, how do you access the package archive ?

Changed in gnet (Ubuntu):
status: New → Incomplete
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future.
To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".
Thanks again!

Changed in gnet (Ubuntu):
status: Incomplete → Invalid
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.