UPDATE PACK 5 FEEDBACK THREAD

[maxibuntu]

If anyone is curious, after getting UP5 I decided to install Xfce 4.10 following these instructions
http://forum.linuxmint.com/viewtopic.ph ... 86#p577386 (basically adding deb http://ftp.debian.org/debian experimental main contrib non-free and pulling in all necessary xfce4.10 stuff via synaptic) and all is well. System is happily running along.

Very nice, thanx! I will try that after UP5's final release.

[koll apraas]

Linux newbie(99.9% --- maybe more ... surely more ) and new guy here. I apologize if I am being abrupt, but is there any chance of knowing when the LMDE UP5 will hit latest. I saw here http://blog.linuxmint.com/?p=2097 that

In LMDE, Update Pack 5 reached “incoming” and should hit “latest” by the end of August. The mirror strategy was changed to face the upcoming demand in bandwidth and new servers will be purchased or rented by our project to make sure the release goes as smooth as possible.

. But last I checked I was unable to find UP5 latest.

Should I wait for the UP5 to hit "latest" OR should I just edit my sources.list to include the "incoming," is it safe (yes, I mean safe and not "safer") to get "incoming"?

A bit of background. I've been dabbling in LMDE for about a year or so now, and mostly via GUI and not CLI. Therefore I have at the very least updated from UP2 to UP3 and then to UP4. UP4 was a bit big and I was wondering if I can at the least "safely" download at least some updates and/or upgrades to at least "some" software without "breaking my system," rather than download "all" updates at one go -- ad i didn't mean breaking my system due to size constraints but due to issues with any packages in the "incoming".

And if I can indeed do that, how do I go about the same?

Actually, I am not afraid of getting my hands dirty and if i update and as a result break my LMDE OS, but I am able to repair it properly then I'm game for that.

Thank you for your time,
kollapraas

P.S. I apologize for the prolific quotation

[mclavey]

I am not a expert , but I thought I would give the test a try .... backed up my system and her we go .
I have a vanilla system gnome shell , mate , cinnimon , and xfce all installed , on a HP laptop 3 yrs old , 8gb ram.

1661 updates ,,, if it will download and install that many without a hitch .... I hope.

I will come back and edit this after it is finished and I reboot .... I hope .

everything downloaded without a problem .... now the install .

everything install without a hiccup and reboot just fine.

good job , Clem and the team .

Is there any reason I should not continue to use it .... as long as it works fine ??

[ketoth]

@koll apraas:

Matter of days, maybe hours before the Mint team switches the links, making UP5 out in latest There could be last-minute fixes before this, so if you want to go incoming now you could miss some and get an unstable system. It's like downloading Firefox from the mirrors before Mozilla announces it's release At this time I think it's about as safe as the final UP5, so if you absolutely want to, backup your data and go for it (don't forget to set your sources.list to latest again when UP5 is out, or you'll get the most dirty stuff when UP6 comes incoming). Upgrading some of the packages will definitively dive you in dependency chaos, and the mint meta packages will require the latest elements anyway (Gnome stuff, codecs, multimedia libraries, MATE stuff, kernel modules, firmwares and so on). Massive headache

@mclavey:

No But same for you: once UP5 out, update your sources.list to point to latest to avoid the first UP6 batch in incoming.

[koll apraas]

@ketoth
Hi,
Thank you for answering . Then waiting seems to be the way to go. Have a good day.

[LexMK]

I can understand why everyone is worried about doing a system backup, I have my /home on a separate partition, am I ok? If something screws up can I just format the / partition?

Also, any interesting news for Radeon free drivers?

[Schoelje]

It's always good practice to make a system backup before a major upgrade.
I use Clonezilla for that: http://clonezilla.org
If things go wrong you can always revert back to your system's original state.

It also might not harm to backup your /home directory, especially ~/.config, ~/.gconf, ~/.thunderbid, ~/.mozilla and ~/.mate* (and in my case ~/.kde).
I really hate it when an upgrade overwrites my carefully made settings

[rcrath]

couple more minor things...

Synaptic has regressed on two small but irritating things.

First,
when the authentication window comes up, the input field for authentication loses focus most of the time. This was a refreshing change in LMDE, that it kept focus, but that is now back to the buggy old focus losing thing.


Second,
LMDE allowed synaptic to reopen on the same authentication as previously opened under, operating on the same timer as sudo. Now it has returned to asking for authentication every time.

[maxibuntu]

For backups, I wrote this script, which uses fsarchiver.

Code: Select all

#!/bin/bash
#
# Description: This script creates backup filesystem images
# with fsarchiver.
#
# Usage: Place the script in "/usr/local/bin", do a
#
# "chmod +x /usr/local/bin/system-fsarchiver"
#
# Then, as root, run something like:
#
# "system-fsarchiver --outdir /path/to/backup/folder --devnode sdax --expire 30"
#
# The script is also suitable to run as a cron job.
#
# Uncomment for debugging
#
# set -x

# Start script

echo -e "\n\033[1;33mSTATUS\033[0m: Script \"$(basename $0)\" is gestart...\n"


# Check to see if we are root.

if [ "${UID}" != "0" ]; then

    echo -e "You must be root !!\n"

    sleep 2

    exit 1

fi


# Usage info

if [ "$1" != "--outdir" -o -z "$2" -o "$3" != "--devnode" -o -z "$4" -o "$5" != "--expire" -o -z "$6" ]; then

    echo -e "You MUST specify each of the following options in a fixed order:

    --outdir: a destination folder to where you want the archives saved. If the folder does not exist, it will be created.

    --devnode: device node of the filesystem to back up, for instance, sda1

    --expire: number of days after which old archives will be deleted to free up diskspace.\n"

    echo -e "Usage: $0 --outdir /path/to/backup/folder --devnode sdxx --expire 30\n"

    sleep 10

    exit 1

fi


# Check to see if the required package are installed

for BINARY in fsarchiver ; do

    if ! which ${BINARY} > /dev/null ; then

	echo -e "This script will not run without \"${BINARY}\""
	echo -e "Please install\"${BINARY}\" and try again."
	echo -e "Aborting now..."

	sleep 5

	exit 1

    fi

done


# Variables

OUTDIR="$2/$(hostname -s)/$(lsb_release -sc)"
DEVNODE="$4"
EXPIRE="$6"
DATE="$(date "+%y%m%d")"
CPUCORES="$(grep processor /proc/cpuinfo | wc -l)"
FSARCHIVE="filesystem_archive_${DATE}_$4_$(hostname -s).fsa"

# Create destination folder if non existant

[ -d "${OUTDIR}" ] || mkdir -p "${OUTDIR}"


# Start rolling

echo -e "Starting the filesystem backup. The filesystem archive will be written to ${OUTDIR}/${FSARCHIVE}\n"

if fsarchiver -A -a -j ${CPUCORES} -o -z 7 savefs "${OUTDIR}/${FSARCHIVE}" "/dev/$4"; then

    echo -e "\nCreation of filesystem archive \"${OUTDIR}/${FSARCHIVE}\" SUCCEEDED!"

else

    echo -e "\nCreation of filesystem archive \"${OUTDIR}/${FSARCHIVE}\" FAILED!"
    echo -e "Aborting now..."

    sleep 2

    exit 1

fi


# Cleanup expired archives

echo -e "\nCleaning up archives older than ${EXPIRE} days..."

for FILE in ${OUTDIR}/*.fsa ; do

    DIRNAME="$(dirname ${FILE})"
    BASENAME="$(basename ${FILE})"

    find ${DIRNAME} -name "${BASENAME}" -mtime "+${EXPIRE:=30}" | while read ARCHIVE; do

	rm -fv "${ARCHIVE}"

    done

done

echo -e "\nDone..."

sleep 10

exit 0

You can automate with cron:

Code: Select all

00 20 * * 1 root /usr/local/bin/system-fsarchiver --outdir /home/user/backup --devnode sda5 --expire 30

[Schoelje]

@maxibuntu
Could you post the script to restore the backup you made with fsarchiver?
Both scripts could help people upgrading their systems safely.

[maxibuntu]

@maxibuntu
Could you post the script to restore the backup you made with fsarchiver?
Both scripts could help people upgrading their systems safely.

There's no point in automating restores with a script. Restore should be done with a systemrepair-cd, as stated on the fsarchiver website. I use system rescue CD to restore my partitions: http://www.sysresccd.org/

For restoring an archive to partition /dev/sda5 you boot from the CD and mount the partition where your backup archives reside:

Code: Select all

mkdir /dir
mount /dev/sdb1 /dir

Change to the directory with the archives, e.g.:

Code: Select all

cd /dir/backups

Optionally, list your archive files to see what you have:

Code: Select all

ls

Restore an archive to a partition, e.g.:

Code: Select all

fsarchiver restfs archive_file.fsa id=0,dest=/dev/sda5

Of course when you make backups, be sure they are NOT written to a partition that might need to be restored. Or use a DVD to save your backups.

[maxibuntu]

Upgrading the following packages left me with no X when booting from my original PAE kernel. The upgrade also installed a new PAE-RT kernel, and when I booted that, I had X, but it consumed 50% CPU and would not load the XFCE panel. Big trouble and I had to restore my system again...

Mintupdate.history

2012.09.04 16:27:56 libegl1-mesa 7.11.2-1 8.0.3-1
2012.09.04 16:27:56 libegl1-mesa-drivers 7.11.2-1 8.0.3-1
2012.09.04 16:27:56 libevent-2.0-5 2.0.18-stable-1 2.0.19-stable-3
2012.09.04 16:27:56 libexif12 0.6.20-2 0.6.20-3
2012.09.04 16:27:56 libfaac0 1:1.28-0.8 1:1.28-dmo3
2012.09.04 16:27:56 libffado2 2.0.99+svn2124-1 2.0.99+svn2171-2
2012.09.04 16:27:56 libfftw3-3 3.3-1 3.3.2-3
2012.09.04 16:27:56 libfile-fcntllock-perl 0.14-1+b1 0.14-2
2012.09.04 16:27:56 libflite1 1.4-release-4 1.4-release-5
2012.09.04 16:27:56 libfltk1.1 1.1.10-13 1.1.10-14
2012.09.04 16:27:56 libgarcon-1-0 0.1.11-1 0.1.12-1
2012.09.04 16:27:56 libgarcon-common 0.1.11-1 0.1.12-1
2012.09.04 16:27:56 libgavl1 1.2.0-4 1.4.0-1
2012.09.04 16:27:56 libgbm1 7.11.2-1 8.0.3-1
2012.09.04 16:27:56 libgc1c2 1:7.1-8 1:7.1-9
2012.09.04 16:27:56 libgcr-3-common 3.2.2-2 3.4.1-3
2012.09.04 16:27:56 libgd2-xpm 2.0.36~rc1~dfsg-6+b1 2.0.36~rc1~dfsg-6.1
2012.09.04 16:27:56 libgdbm3 1.8.3-10 1.8.3-11
2012.09.04 16:27:56 libgettext-ruby1.8 2.1.0-2.1 2.2.1-2
2012.09.04 16:27:56 libgif4 4.1.6-9 4.1.6-9.1
2012.09.04 16:27:56 libgl1-mesa-dri 7.11.2-1 8.0.3-1
2012.09.04 16:27:56 libgl1-mesa-glx 7.11.2-1 8.0.3-1
2012.09.04 16:27:56 libgl1-nvidia-alternatives 295.40-1 302.17-3
2012.09.04 16:27:56 libgl1-nvidia-glx 295.40-1 302.17-3
2012.09.04 16:27:57 libglade2.0-cil 2.12.10-3 2.12.10-4
2012.09.04 16:27:57 libglapi-mesa 7.11.2-1 8.0.3-1
2012.09.04 16:27:57 libglib2.0-0 2.32.0-4 2.32.3-1
2012.09.04 16:27:57 libglib2.0-data 2.32.0-4 2.32.3-1
2012.09.04 16:27:57 libglib-perl 2:1.251-1 3:1.260-1
2012.09.04 16:27:57 libglu1-mesa 7.11.2-1 8.0.3-1
2012.09.04 16:27:57 libglx-nvidia-alternatives 295.40-1 302.17-3
2012.09.04 16:27:57 libgmp10 2:5.0.4+dfsg-1 2:5.0.5+dfsg-2
2012.09.04 16:27:57 libgnutls26 2.12.18-1 2.12.20-1
2012.09.04 16:27:57 libgraphite2-2.0.0 1.1.1-1 1.1.3-1
2012.09.04 16:27:57 libgssapi-krb5-2 1.10+dfsg~beta1-2 1.10.1+dfsg-1
2012.09.04 16:27:57 libgusb2 0.1.3-3 0.1.3-5

Kernel log:

Sep 4 16:37:47 kernel: [ 27.333832] NVRM: API mismatch: the client has the version 302.17, but
Sep 4 16:37:47 kernel: [ 27.333835] NVRM: this kernel module has the version 295.40. Please
Sep 4 16:37:47 kernel: [ 27.333837] NVRM: make sure that this kernel module and all NVIDIA driver
Sep 4 16:37:47 kernel: [ 27.333839] NVRM: components have the same version.

[zerozero]

maxibuntu,
why these updates today? the repo has been static (or almost) and surely not updating low level lib like the ones you have in that log.

[ketoth]

maxibuntu: just asking, did you install nvidia's homebrew proprietary driver ? If yes, remove it ALL (sudo apt-get purge nvidia*) then apt-get install "nvidia-glx". This should add the good DKMS modules. Don't forget to reboot after it.
(do an apt-get dist-upgrade after checking that your sources.list is complete, to make sure everything is up to date down to the kernel)

[maxibuntu]

maxibuntu,
why these updates today? the repo has been static (or almost) and surely not updating low level lib like the ones you have in that log.

As I posted before I had trouble when I updated the whole pack. I restored my system and now I'm updating in batches... So I have a partially upgraded system now, only 378 packages to go.

[maxibuntu]

maxibuntu: just asking, did you install nvidia's homebrew proprietary driver ? If yes, remove it ALL (sudo apt-get purge nvidia*) then apt-get install "nvidia-glx". This should add the good DKMS modules. Don't forget to reboot after it.
(do an apt-get dist-upgrade after checking that your sources.list is complete, to make sure everything is up to date down to the kernel)

Thanx, I will try that.

[sobrus]

It's a good idea to make Clonezilla copy of every important system partition before update.
In case something goes wrong you can restore root, home or both of them.
I use small home partition, just for system settings, because it is much easier to backup.

I've noticed that fglrx was removed from Incoming repo, probably due to x.org incompatibility.
I hope it will be added back before UP5 is released (I believe it is in debian testing and sid again).

On openSUSE, the fglrx driver recompiled itself automatically every kernel upgrade. This is not the case here?

[maxibuntu]

There is still no shutdown option in Gnome3.
EDIT: I got the shutdown option back after fiddling with policykit...

My gnome-shell extensions have disappeared. They have actually been deleted from /home/user/.local/share/gnome-shell/extensions . Odd...
EDIT: This could be a problem with my tmpreaper config...

[ptruchon]

@sobrus

I had the same problem with the fglrx drivers. The problem seems to be on the ATI's end of things. See page 5 of this thread for more info: http://forums.linuxmint.com/viewtopic.p ... 80#p617784

[maxibuntu]

Package mc 4.8.3-3 from mint incoming still has this very annoying bug (I use mcedit all the time):

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673252

mc 4.8.3-5 from wheezy repos also has the bug. It is fixed in mc 4.8.3-7 which is in sid:

http://packages.debian.org/sid/mc
http://packages.debian.org/sid/mc-data