Tag Info

Hot answers tagged

7

There's a package for that ;-). As well as cron-apt, which can be configured to perform certain upgrades automatically, another useful package is unattended-upgrades which is designed to safely apply security updates automatically. Beyond that, as Erathiel says it's not safe to run dist-upgrade automatically, but it's safe enough to run it manually every ...


7

sudo apt-get dist-upgrade is very safe to run as it won't do anything to the system, instead stopping to ask for your confirmation ;) You would have to add a -y switch, which is intended for unattended upgrades and makes apt assume that you always answer 'yes' to questions: sudo apt-get -y dist-upgrade. The man page states that If an undesirable ...


4

At the moment elementary isn't providing an upgrade path from update manager since results are mixed. Sometimes it works, sometimes it doesn't. You can try: Back up EVERYTHING. Make a Freya install disk. Boot from the install disk and select the "upgrade" option. However, as I said, results may vary. It's always recommended to perform a clean install. An ...


3

"(2015-03-01)" in your uname --all output is the date of the kernel compilation, probably. Debian will not automatically remove your existing kernels on upgrade. Every release has its own default binary kernels, which all correspond to a single kernel version, but of course are built for different architectures. It is generally a good ideas to use a ...


2

The more general approach is to compare the two source packages corresponding to the version you're upgrading from and the version you're upgrading to. To find the former you may need to look through the snapshots; the latter should be available from your archive. Then run debdiff on the two .dsc files. Here's an example, comparing stella 4.1.1-1 (the ...


2

For some reason, your initramfs is failing to start your RAID array. That could mean it just wasn't configured to, or that it was somehow generated wrong. Since you're able to boot from a recovery disk, you can easily change the setting and regenerate it using the following commands: dpkg-reconfigure mdadm. You should be asked which arrays to start in the ...


1

The solution is fairly easy, just replace auto to allow-hotplug. So I ended up with this: allow-hotplug lo iface lo inet loopback allow-hotplug wlan0 iface wlan0 inet static address 192.168.150.1 netmask 255.255.255.0 allow-hotplug eth1 iface eth1 inet manual up ifconfig $IFACE ...


1

For each of the urls mentioned in the error message in the question, do a search for it. Then remove it from the relevant file in /etc/apt/sources.list.. For example cd /etc/apt/sources.list.d grep -R http://old-releases.ubuntu.com/ubuntu/dists/trusty/main/binary-amd64/Packages This will give you a name of a file in /etc/apt/sources.list.d. Then go into ...


1

Up until a few hours ago testing was effectively jessie, so you should be able to cross-grade without trouble. Simply replace testing with jessie in your /etc/apt/sources.list... If you switched to testing after testing was unfrozen, you'll need to downgrade packages; you can use apt-show-versions to find packages which are from testing rather than from ...


1

As mentioned it will only be automatic if you have "stable" in the source.list file, if you specifically have "wheezy" it won't automatically happen when you run an apt-get upgrade. This is noted in the full release notes here. Or take a look at a cut down guide which covers this here. Essentially the sources.list must have either jessie or stable, then ...


1

You could try to download the deb package and open it up using the file explorer. Then it is possible it will install. You can download the .deb on the official Debian site at https://www.debian.org/distrib/packages then use dpkg -i package.deb



Only top voted, non community-wiki answers of a minimum length are eligible