sqlite install failure on Ubuntu 7.10
Reported by Chad Woolley | October 19th, 2008 @ 04:16 PM
Got this error. Can sqlite be made optional?
* executing "sudo -p 'sudo password: ' \\\n sh -c \"DEBCONF_TERSE='yes' DEBIAN_PRIORITY='critical' DEBIAN_FRONTEND=noninteractive apt-get -qyu --force-yes install libmysqlclient15-dev sqlite3 libsqlite3-ruby libsqlite3-dev \""
servers: ["announcedmate.r08.railsrumble.com"]
[announcedmate.r08.railsrumble.com] executing command
** [out :: announcedmate.r08.railsrumble.com] Reading package lists...
** [out :: announcedmate.r08.railsrumble.com]
** [out :: announcedmate.r08.railsrumble.com] Building dependency tree...
** [out :: announcedmate.r08.railsrumble.com]
** [out :: announcedmate.r08.railsrumble.com] Reading state information...
** [out :: announcedmate.r08.railsrumble.com]
** [out :: announcedmate.r08.railsrumble.com] Package sqlite3 is not available, but is referred to by another package.
** [out :: announcedmate.r08.railsrumble.com] This may mean that the package is missing, has been obsoleted, or
** [out :: announcedmate.r08.railsrumble.com] is only available from another source
** [out :: announcedmate.r08.railsrumble.com] E: Package sqlite3 has no installation candidate
Comments and changes to this ticket
-
Chad Woolley October 19th, 2008 @ 04:26 PM
Fix for this was to uncomment the "universe" sources in /etc/apt/sources.list.
Deprec should probably verify and uncomment this if necessary, or at least throw a meaningful proactive exception
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
<h1>Source available from github</h1>
The Git repository resides at <a href="http://github.com/mbailey">http://github.com/mbailey</a><br/><br/>
Check out the current development trunk with:<br/>
git clone git://github.com/mbailey/deprec.git
<br/>
<h1>Creating a bug report</h1>
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.<br/><br/>
Security vulnerabilities should be reported via an email to mike@bailey.net.au, do not use lighthouse for reporting security vulnerabilities. All content in lighthouse is publicly available as soon as it is posted.<br/><br/>
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too".<br/><br/>
(Wording copied from <a href="http://rails.lighthouseapp.com/projects/8994-ruby-on-rails">Rails lighthouse page</a>)
Chad Woolley