LinuxBBQ

The recommended period between ISO birthday and first upgrade should be less than 3 months. Everything else, check the Upgrade Warnings section back, and don't waste your time asking anything else, because we don't know it.

In other words. If you are new to the grill, grab one of the *recent* releases. If you already use older spins, then you can upgrade as usual, always having an eye on upgrade warnings.

Do not bother us with breakages if you try to install a very old BBQ ISO. LinuxBBQ is a DIY distro, we do not support months old upgrade paths.

Check always the release notes before downloading blindly a LinuxBBQ ISO.

"Outdated" releases are stored here: http://linuxbbq.com/bbs/viewforum.php?f=34

A little addition for those who still want the old shit :)

After installing and rebooting, run an update of the sources first: then, grab yourself the new APT and dpkg optionally, add apt-listbugs when this is done, you can do a full dist-upgrade You might run into smaller problems during the upgrade of the packages. If so, try to resolve with and then, try again
APT has a lot of bug reports, so before you bark up the wrong tree when your upgrade fails, check this: https://bugs.debian.org/cgi-bin/pkgrepo ... t=unstable

super useful, thanks for writing this.

i always wondered what the fuck the -f option exactly does that suddenly makes errors go away. i mean, if that is the default way of fixing apt errors, why doesn't apt just try that itself first anyway? or is it the exact working of that flag that i do not understand that makes it seem so strange to me? orrr is it just Debian being pro-choice?

IIUC, the -f flag tries an installation of a given package (or the next in the list on installable packages) without checking for dependency, allowing the package manager to proceed even if broken dependencies exist. The man page also mentions that dpkg (or dselect) could be used to remove conflicting package dependencies or to resolve this problem manually (dpkg -r or -i in this case).