Tag Info

New answers tagged

1

## Multiarch sources deb [arch=amd64,i386] http://uk.archive.ubuntu.com/ubuntu/ quantal main universe deb http://ports.ubuntu.com/ubuntu-ports quantal main universe Those lines are for an old version of Ubuntu, remove them and do sudo apt-get update. For PPA 404 errors follow this: How can I fix a 404 Error when updating packages?


0

I added the Linux Mint LTS release (Qiana or Mint 17) repositories to my Ubuntu 14.04 LTS by running the following commands through the terminal: sudo sh -c 'echo "deb http://packages.linuxmint.com/ qiana main" >> /etc/apt/sources.list.d/mint.list' Now run an update to retrieve information about what packages are available: sudo apt-get update ...


0

A two-stage method would be to create a script which, given a path to a package, checks for the existence of an amd64 version and if it finds such a version, deletes the i386 package. Something like: #! /bin/bash PKG=${1/i386/amd64} if [[ -f $PKG ]] then rm $1 fi saved as script.sh, for example. And then: find ${REPOSITORY_ROOT} -iname '*i386.deb' ...


6

You can trust them as much as you trust the people who put them up. Anyone can put up a PPA; a repository owned by some random user is obviously less trustworthy than the official LibreOffice PPA, for example.


2

Good question. The short answer is: you can't trust them.


1

just open nano /etc/apt/sources.list and replace all 'pk' to 'us'


0

For the most part you can get away with changing all the references of the old release to the new release (ie: "quantal" to "trusty" for example) in /etc/apt/sources.list (and any .list files under /etc/apt/sources.list.d/), run an apt-get update and then an apt-get dist-upgrade - I've seen very few installations "break" using this hackish method. But the ...


0

I think that that proxy is the fail, edit the file /etc/apt/apt.conf Acquire::http::proxy "http://user:pass@proxyIP:8080/" Hope it works :) In my case, the node was brought up using Juju which had put MAAS server as the proxy. Once I deleted that entry, the apt-get update started working.


0

I think the reason is that as of April, Quantal (12.10) has reached end of life and is no longer supported in the main Ubuntu package repositories. However I don't know why it's trying to install a Quantal package on a Precise system. This might be of use but I'd want to check first that your precise sources aren't touched by sed (sorry, sed's not my area): ...


0

Try resetting your configuration files with sudo apt-get -o dpkg::options::="--force-confnew" -o dpkg::options::="--force-confmiss" --reinstall install PAKET If this does not help, open your sources.list file with sudo gedit /etc/apt/sources.list and try commenting this part out http://gr.archive.ubuntu.com/ubuntu/dists/quantal/restricted/source/Sources ...


1

For Finding PPA: Visit Launchpad Personal Package Archives for Ubuntu Visit ubuntu updates and search with "Package Search" then find appropriate package according to your version of Ubuntu. For Browsing all PPAs, visit : PPA List For getting Information about PPA and use, visit: What are PPAs and how do I use them? Repositories/Ubuntu From ...


0

https://launchpad.net/ seems to host all of the PPAs. You can search for it here (or here) to find various PPAs - e.g: Virtualbox Git The problem here is finding out if the PPA is official, or just someone's personal PPA. For the possible security concerns, you may want to read this question


1

You can't upgrade Kali(backtracks' new name) to Ubuntu. Kali is Debian Testing based.


2

Since what you want is, essentially, simple, the sane thing to do is just revert all your changes instead of using third parties which can be too complicated. Just copy the /usr/share/doc/apt/examples/sources.list file to /etc/apt/ and remove the files in your /etc/apt/sources.list.d directory. Or, in simple commands: sudo mv /etc/apt/sources.list{,.bk} ...


0

Try "sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys " command for all errors like: sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 16126D3A3E5C1192


3

13.04 has reached EOL there for the repositories have been removed so there will be no more updates for 13.04 not even security so it is vulnerable to attacks. There is an archive here that you can use to install software but it will be old software outdated and there will be no improvements and no new security update. If you want to use an outdated ...



Top 50 recent answers are included