Tag Info

New answers tagged

2

Generally, <name>_<version>.orig.tar.xz or <name>_<version>.orig.tar.gz is the source archive, as released by the project. It's simply renamed to fit the vagaries of the Debian packaging system. Usually, for packaging purposes, you need to unpack <name>_<version>.orig.tar.xz in the current folder and then place the ...


0

The bare minimum in sources.list is: deb http://us.archive.ubuntu.com/ubuntu/ precise main restricted universe multiverse deb-src http://us.archive.ubuntu.com/ubuntu/ precise main restricted universe multiverse Edit sources.list using: sudo -H gedit /etc/apt/sources.list Then run: sudo apt-get update You can find more alternative using Ubuntu ...


0

The bleeding edge PPA's are hosted by the OpenStack Ubuntu testing team - the following are actively maintained: ppa:openstack-ubuntu-testing/icehouse ppa:openstack-ubuntu-testing/juno ppa:openstack-ubuntu-testing/kilo You can enable these using the add-apt-repository command: Example: sudo add-apt-repository ppa:openstack-ubuntu-testing/kilo Testing ...


1

The PPA should be ppa:cloud-installer/stable


0

Guess Google messed it up but fixed now : had the same problem this morning, just tried again : sudo apt-get update && sudo apt-get upgrade ... and it worked!


0

...dont forget about `build-dep` In addition to those answers above -- I have to admit I am surprised that nobody have mentioned this approach which, is what I have always used as a "silver bullet" at any time I encountered apt-get conflicts or unresolved packages (or even if the system is being stubborn....ha!). sudo apt-get remove --purge [package] sudo ...


6

This will work better than these solutions: sudo apt-key list You will see this on this list: pub 1024D/7FAC5991 2007-03-08 uid Google, Inc. Linux Package Signing Key <linux-packages-keymaster@google.com> sub 2048g/C07CB649 2007-03-08 You will do now: sudo apt-key del 7FAC5991 Then you will do these commands: sudo -i ...


1

wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo apt-key remove - apt-get update && apt-get upgrade


11

Open a terminal and enter the following: wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo apt-key add - That will import Google's updated GPG Key. You should be able to update the system without any errors. Source: Google Linux Repositories


0

Today I found this one ppa:pkg-vim/vim-daily It uses the new dailybuild function from launchpad to automatically grab the upstream source and build if there has been a change. So nearly no maintenance needed from ubuntu side.


0

I think that this message, which I wrote yesterday on the ubuntu-translators mailing list, applies to your question as well. You'd better give us a couple of specific examples, and we may be able to check out if something is wrong.


0

A more general answer is: one can add PPAs which are not available (download of files fails with the HTTP error 404 you experienced) because they might be unavailable temporarily only (overloaded, down for maintenance, etc.) and become available later. Other repositories might have disappeared years ago or an URL has been constructed by appending a release ...


1

Ubuntu 15.04 is still in development and hasn't been released yet. Because of this, not too many PPAs will have software available for Vivid. In addition, support for this release (while its still in development) will be limited/not available. If you're a new Ubuntu user, I recommend that you instead reinstall either 14.04 LTS (Trusty) or 14.10 (Utopic). As ...


0

Ok, got it. The deb package build gets its version number not from the version field in the control file, but from the changelog entry.


0

First, manually delete the ppa using the following command: sudo rm /etc/apt/sources.list.d/kxstudio* Now, use "apt-pinning" to give priority to your current distro, regardless of package version number. First, create a file: sudo nano /etc/apt/preferences and copy/paste the following into the file replacing "trusty" with your current ubuntu version: ...


0

Installation instructions are here: https://nodesource.com/blog/nodejs-v012-iojs-and-the-nodesource-linux-repositories # Note the new setup script name for Node.js v0.12 curl -sL https://deb.nodesource.com/setup_0.12 | sudo bash - # Then install with: sudo apt-get install -y nodejs


0

Follow these steps taken from http://wiki.x2go.org/doku.php/wiki:repositories:ubuntu : Open terminal and execute following command : sudo gedit /etc/apt/sources.list Add following line to the file deb http://de.archive.ubuntu.com/ubuntu <my-ubuntu-version> main universe Then execute following command in terminal : sudo apt-get install ...


0

The problem here is to lock down the trouble maker package and kick it out. Then you can fix inconsistent dependencies with sudo apt-get -f install. So with cautious you may use: sudo dpkg --force-all -P libgbm1 to force removing the broken. This command may damage your system, so you should watch it. And try to fix: sudo apt-get -f install. If any ...


1

PPAs and other third-party repositories are disabled during a release upgrade. You have to manually enable them post-upgrade. The packages are upgraded if a newer version exists, or left alone if there's no corresponding package in the official repositories. You can visit the PPA page and check if it supports the newer release. In the Overview of ...


0

Trusty and Utopic have this problem. Most PPAs have support for both. But what if you dont have a PPA that supports trusty but not Utopic, you would simply uninstall the application by typing in a Terminal sudo apt-get autoremove packagename apt-get update It is completely up to the maintainer if they wanted to support anything past Trusty. In terms of ...


3

The 'partners' are companies that provide software that is approved by Canonical but for which the Ubuntu community is not providing updates. That's the responsibility of the partners themselves. The community however provides the install packages (builds the packages). For instance Adobe used to be a partner. Independent are essentially providers that are ...


0

answer given by Thanos in his question The only solution to my problem was found here How do I resolve unmet dependencies after adding a PPA?. I applied the following commands: sudo apt-get update sudo apt-get install aptitude then, sudo aptitude install grive-tools As a final step I had to downgrade some packages to met the dependencies. Sample of ...


1

No, this is not possible. You can theoretically build on utopic, and then manually sync only the binary packages to the older releases, but you cannot configure Launchpad to do so automatically. You could also just backport the newer dependencies to the older versions of Ubuntu (trusty and precise) so that you can build the source on all of them, which ...


1

Part of the problem is that it's now expected that the debian/rules file either uses the newer dh_* target names (which this doesn't) or that there are build-arch and build-indep target names. If you look in Ubuntu's debian/rules, you'll see that for Trusty, they've make a build-arch target that calls build-stamp, and made build depend on build-arch. This ...


0

I saw this same behaviour. It was because the signing key I was using had not been added to my profile yet. The dput command doesn't output any error, but the package is silently (no error on the console, or via email) ignored. So I suggest checking the list of OpenPGP keys in your Launchpad profile.


1

The canonical way to install seems to be ubuntu-make https://wiki.ubuntu.com/ubuntu-make


4

After unpacking the *.debian.tar.gz file, you can use the dch commands to create new changelog entries. For example, dch -i would (probably) bump up the version to 1.67-1~precise~ppa2. You can instead use dch -v "1.68-1~precise~ppa1" to specify the new version. Note that dch can also take in another argument that represents the message for that changelog ...



Top 50 recent answers are included