Tag Info

New answers tagged

2

Most of the time, a source line will be in the file /etc/apt/sources.list, so you should edit that. However, if you don't find it there, look at files inside the directory /etc/apt/sources.list.d. Putting the comment character # in front of any source line should be enough for apt to ignore it.


1

You are in a pager program, where you can scroll through the change logs of the packages that you are installing. Ubuntu's default pager (like most unices out there, except some embedded or antique systems which have the more primitive more) is less. The installation process is not hung: it's waiting for you to read the changes. You can use arrow or page ...


-1

I solved the problem by simply reinstalling the dpkg binarys. For the I downloaded the .deb package of dpkg and extracted it by hand. The I copied and pasted the binarys in the right place (/usr/bin).


1

I think the errors you're seeing are pertaining to APT's changelog facility. You can either disable it or remove it all together. 1. to disable In the file /etc/apt/listchanges.conf open it in a text editor and change the frontend line to none. [apt] frontend=none email_address=root confirm=0 save_seen=/var/lib/apt/listchanges.db which=news You can also ...


0

I tried installing several Ubuntu packages on Debian Wheezy There's your problem: Ubuntu and Debian use the same package format, but you can't so easily mix Debian and Ubuntu packages on the same system, because the releases have different versions of the packages. You'd get similar issues if you mixed multiple releases of Debian or of Ubuntu. It can be ...


0

In the end, I moved the directory with the problematic files: sudo mv /usr/share/doc/libqtwebkit4 /usr/share/doc/libqtwebkit4.backup After that apt-get -f install ran successfully.


1

The problem is that the package is broken. You have unstable repository enables. It is called "Unstable" for a reason.


1

You've upgraded the package containing the openssl frontend command, but not the package containing the OpenSSL library. That package is called libssl1.0.0, and you can upgrade it with apt-get install libssl1.0.0. Debian provides libraries in separate packages so that you can install multiple versions with incompatible binary interfaces simultaneously. For ...


0

On Debian-based distros, you can upgrade the single offending OpenSSL package without a full apt-get upgrade: apt-get install libssl1.0.0


0

Hijacking old topic, but faced with the same problem recently. So, based on the advice given above and the output of host and whois: # host security.debian.org security.debian.org has address 212.211.132.250 security.debian.org has address 195.20.242.89 security.debian.org has address 212.211.132.32 security.debian.org has IPv6 address ...


1

Partial success. I was able to get the system to register to spacewalk by manually adding the upstream sources to my /etc/apt/sources.list: deb http://ftp.de.debian.org/debian sid main Importing the GPG key: gpg --keyserver pgpkeys.mit.edu --recv-key 8B48AD6246925553 gpg -a --export 8B48AD6246925553 | apt-key add - Then I did an apt-get update for good ...


1

It looks as if those packages just aren't available to 12.04 LTS (Precise). Searching via Ubuntu Packages seems to bear this out. excerpt Exact hits - Package apt-transport-spacewalk         Since you're probably comfortable rolling your own RPMs I might be inclined to roll my own .deb file here, taking the package files ...


2

Linux Mint is not meant to be updated over release boundaries. The suggested approach is killing your old installation by re-installing. I know this is a rather unsatisfying answer, but it's the way it's meant to be from upstream. Trying to do a "rolling" update ia is essence possible but might break in an unpredictable and thus horrible way and when trying ...


0

You may still have emacs23 and friends installed. sudo apt-get remove emacs*


0

Ok, it just looks like the apt-get exited before it could install the necessary dependencies. Since there don't appear to be any reverse dependencies for python-setuptools, I would just try removing it and see what happens: apt-get purge python-setuptools If that doesn't work, then: dpkg -P python-setuptools From there you could try installing again, ...


1

You should fix /etc/initramfs/post-update.d/flash-kernel so that it successfully flashes your kernel & initrd. It's in /etc, so you're free to edit it to make it work on your board. If you can't edit it to make it work (e.g., flashing is done with JTAG), then you ought to have it print out a big warning reminding you to flash it, and exit 0. Once ...


0

If you use aptitude, you have to look somewhere different: tail -20 /var/log/aptitude or cat /var/log/aptitude For older, zipped logs, use this command zcat /var/log/aptitude.1.gz or zcat /var/log/aptitude.1.gz | tail -20


3

Definitely nothing is broken. When a package is installed, there are often other packages that it depends on. These will be automatically installed by apt-get. It used to be that you would be forced to use a separate program if you wanted keep track of these packages and remove them if you ever removed the original program that you installed. Now apt ...


0

Why not remove them with the command suggested by apt-get, i.e. apt-get autoremove? If they were installed by default on Kali and used by the previous web browser, and no longer used now that you have removed this browser, it will not be a problem. Plus if someday one of the package is needed again, install it explicitly via apt-get and it will not ...


0

You have global configuration file - /etc/myysql/my.cnf. Other variables are inside mysql database that is (along with others), in the following location: /var/lib/mysql/. In fact, what you need is only binary mysql/mysqld/mysqladmin. If you really really wanted to see a whole list mysql server files, then: assuming you haven't cleaned anything on this ...


0

It is recommended to leave this on default as it is unless you are really low on disk-space to get less problems. for more info see this answer: http://unix.stackexchange.com/a/77076/20661


0

If it's in your path, try one of these: which mysql which mysqld Edit: InnoDB is now the default engine, and to find its data files, assuming the installation was correctly done, view the /etc/mysql/my.cnf file and look for the lines that contain innodb_data_home_dir and/or innodb_data_file_path.


2

Debian versions of MySQL packages store the MySQL data in /var/lib/mysql directory by default. You can see this in /etc/mysql/my.cnf file also. Debian packages don't contain any source code, if that is what you meant by source files. Binaries are installed generally in /usr/bin and /usr/sbin directories. You can see where the package files are installed by ...


4

From man 8 apt-get: --no-install-recommends Do not consider recommended packages as a dependency for installing. Configuration Item: APT::Install-Recommends.


2

apt-cache show shows information for all versions of a package. $ apt-cache show 0ad | grep Version: Version: 0.0.14-3~bpo70+2 Version: 0~r11863-2 apt-cache policy presents the information you want in a more compact form, and includes the corresponding repository origin. $ apt-cache policy 0ad 0ad: Installed: (none) Candidate: 0~r11863-2 ...


2

500 and 100 are the priority numbers. To know more about them, I recommend man apt_preferences. 500 corresponds to installable, 100 means installed. From the man page: If the target release has not been specified then APT simply assigns priority 100 to all installed package versions and priority 500 to all uninstalled package versions. The *** ...


1

The ubuntu-desktop package is used to pull in all of the graphical packages, like Xorg, Gnome, Unity, etc. (see here for a list). As such, you won't find the ubuntu-desktop package on a server installation disk. You can find a list of these "metapackages" here.


0

My apt-cache does not have -t switch, so I use apt-show-versions $ apt-show-versions bash bash:i386 4.1-3 install ok installed bash:i386 4.1-3 squeeze ftp.de.debian.org bash:i386 4.2+dfsg-1 testing ftp.de.debian.org bash:i386 4.3-2 testing ftp.de.debian.org


1

The standard approach to debugging such issues is to check the priority numbers of the available versions of each package mentioned in the error message. This is commonly done using apt-cache policy. For example, to use just the first part of the error message, you should run apt-cache policy libgl1-mesa-dri:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 ...


0

Apart of the method you mentioned of doing apt-get install package package-dependency you can use aptitude's why-not command to easily figure out: aptitude why-not sysvinit-core i A systemd-sysv Breaks sysvinit-core


3

These aren't documented. My guess is that a is for an automatic install, u is for an (automatic?) upgrade and b is for packages installed to fix broken packages. This would mean debfoster is removing packages it is not supposed to, note that the website says: As of 2006-01-01, debfoster is officially deprecated. Possibly this has developed bugs over the ...


3

"... But it is not going to be installed" generally means that a serious dependency conflict will ensue if it's allowed to go on. Try the following command: aptitude why-not citadel-mta why-not basically checks dependencies and returns the reasons it would have to not fill a particular dependency automatically. In the case of my system at home: ...


0

Downloading source code from Debian repositories is as simple as running apt-get source <PACKAGE>. It will put 3 files in your current directory, .dsc that describes package, .orig.tar.gz that contains unmodified sources, and .diff.gz that contains Debian-specific changes. But if you get error E: Unable to find a source package for <PACKAGE>, ...


6

apt-get install sudo -y - Used to install sudo package in Debian based systems and y is used to specify yes during installation. yum install -y sudo - Used to install sudo package in fedora based systems and y is used to specify yes during installation. echo "stack ALL=(ALL_ NOPASSWD: ALL" >> /etc/sudoers - Concatenating the line stack ALL=(ALL_ ...


0

It's unusual to use sudo on a Debian system. So it might just have been a permissions problem. Next time try adminstrator account via su



Top 50 recent answers are included