Upgrade Thunar in Wheezy to newest version

[djohnston]

PS-3 : found this:
https://sites.google.com/site/mydebiansourceslist/
this part:
the page about the siduction repos:
http://packages.siduction.org/?Repositories:xfce_next_i386

...

I had Thunar version 1.2.3 installed in Wheezy. I looked in the Debian unstable and experimental repos for a newer version. But, there isn't any. Same ol' same ol'. The following is how I upgraded to Thunar version 1.6.2.

(1) Get the Siduction keyring for package verification. Do these steps as user root. If you use sudo, act accordingly.

Code: [Sélectionner]

wget http://packages.siduction.org/base/pool/main/s/siduction-archive-keyring/siduction-archive-keyring_2013.03.29_all.deb

Code: [Sélectionner]

dpkg -i siduction-archive-keyring_2013.03.29_all.deb

Code: [Sélectionner]

rm siduction-archive-keyring_2013.03.29_all.deb
Removing the keyring package is optional. I left it in root's home directory.

(2) Create a text file named siduction_XFCE4_next.list. The name can be of your own choosing, but it must contain the suffix of .list. Note that this source list is only a subset of Siduction's full repository. That is what you want, unless you want to change your Wheezy/testing installation to Siduction (based on Debian unstable). The contents of the file are listed below.

Code: [Sélectionner]

# siduction
# XFCE4.10 xfcenext (amd64 / i386 )
deb http://packages.siduction.org/xfcenext unstable main
# deb-src http://packages.siduction.org/xfcenext unstable main
(3) Copy the file (as user root) so apt can use the source.

Code: [Sélectionner]

cp siduction_XFCE4_next.list /etc/apt/sources.list.d/
(4) (a) If you use apt-get, do:

Code: [Sélectionner]

su -

Code: [Sélectionner]

apt-get update

Code: [Sélectionner]

apt-get dist-upgrade

Code: [Sélectionner]

exit
(4) (b) If you use Synaptic, open Synaptic and click Reload. Click Mark All Upgrades. Click Apply.

You can leave the siduction_XFCE4_next repo list enabled. Only XFCE4 packages you have installed will be update/upgraded. In my installation, the following packages were upgraded/installed.

Upgraded the following packages:
exo-utils (0.6.2-5) to 0.10.2-1
libexo-1-0 (0.6.2-5) to 0.10.2-1
libexo-common (0.6.2-5) to 0.10.2-1
libexo-helpers (0.6.2-5) to 0.10.2-1
libthunarx-2-0 (1.2.3-4+b1) to 1.6.2-1
libxfce4ui-1-0 (4.8.1-1) to 4.10.0-1
libxfce4util-bin (4.8.2-1) to 4.10.0-2
libxfce4util-common (4.8.2-1) to 4.10.0-2
libxfconf-0-2 (4.8.1-1) to 4.10.0-1
thunar (1.2.3-4+b1) to 1.6.2-1
thunar-data (1.2.3-4) to 1.6.2-1
thunar-volman (0.6.1-1) to 0.8.0-1
xfce-keyboard-shortcuts (4.8.1-1) to 4.10.0-1
xfconf (4.8.1-1) to 4.10.0-1

Installed the following packages:
libxfce4util6 (4.10.0-2)

Here's the result:



I had edited the /usr/share/gvfs/mounts/network.mount file because of the extreme wait time for the earlier Thunar version to start after login. The line edited was:

AutoMount=false

I changed the value to true and rebooted. After logging in, I started Thunar version 1.6.2. There was no wait time to speak of, and Network mounts were ready to browse.

[Taco.22]

I thought I would try out djohnston's suggestion above and install Thunar 1.6.2 via Siduction.  The keyring bit didn't work so I just added the Siduction repo to sources.list and gave apt-get permission to download from an untrusted source.  Worked a treat and the new Thunar is very neat - even has tabs now.  Looks just a little different, kind of more stylish.  Works fine with my current settings and no issues with network or startup.

Speaking of network, I was having an issue where wicd wouldn't start the network for about 20 seconds after login.  Replaced wicd with network-manager-gnome and solved the issue!

[djohnston]

The keyring bit didn't work so I just added the Siduction repo to sources.list and gave apt-get permission to download from an untrusted source.

The keyring changed on March 29th, 2013, shortly after posting this. The command to get the keyring, (run as root), is now:

Code: [Sélectionner]

wget http://packages.siduction.org/base/pool/main/s/siduction-archive-keyring/siduction-archive-keyring_2013.03.29_all.deb

Code: [Sélectionner]

dpkg -i siduction-archive-keyring_2013.03.29_all.deb
Since you already have the sources list, just install the keyring from Synaptic. Do a search for "keyring" and install the siduction-archive-keyring package.

(1) I don't know why the keyring package isn't updated in Synaptic. I just did the manual wget and dpkg -i and the new keyring replaced the older one.
(2) I updated the instructions in the first post.

Thanks for posting!

[melodie]

Hello!

How are you with the hot weather these days?

I am about to restart working on the creation of packages in Debian and I was wondering if either one of you two would push a new Debian spin out soon? If not, which one of the latest would you advice me to install, for building packages in it? (I still have Taco's Scorpio RC4 installed, but not quite up to date and my guess is you both improved a lot the different remixes since then).

[djohnston]

How are you with the hot weather these days?

The heat has been tempered by a lot of rain lately, which is a new condition here in Oklahoma. We have not seen sustained 100 degree temperatures like we did last year.

I am about to restart working on the creation of packages in Debian and I was wondering if either one of you two would push a new Debian spin out soon? If not, which one of the latest would you advice me to install, for building packages in it? (I still have Taco's Scorpio RC4 installed, but not quite up to date and my guess is you both improved a lot the different remixes since then).

I suspect you want an Openbox based respin. I've only done one, the DebWeb. It has a few extra packages you may not want, and some were not installed conventionally, using a package manager. For that reason, I would pick one of Taco.22's, probably the Scorpio_2013-2. I think the only things you'd need to do are (1) a full update after installation and (2) (optionally) the installation of the latest Thunar.

Or, you could install the DebLXDE respin, do a full update, then remove the LXDE packages.

[patrick013]

Speaking of network, I was having an issue where wicd wouldn't start the network for about 20 seconds after login.  Replaced wicd with network-manager-gnome and solved the issue!

If you switch kernels frequently at boot my wicd conks out.
On Scorpio I have a 3.2.x a 3.7.x and a 3.9.x     If I stay with
the same kernel, it stays working, switching to some other
kernel it conks out.   The nm-applet didn't seem to care and
works regardless of the last kernel used or the next kernel used.

Just FYI

Patrick

[melodie]

The heat has been tempered by a lot of rain lately, which is a new condition here in Oklahoma. We have not seen sustained 100 degree temperatures like we did last year.

Good thing! Here we came out from freezer to oven. 
(although we also had quite so days with rain).

I suspect you want an Openbox based respin.

Yes I do.

I've only done one, the DebWeb. It has a few extra packages you may not want, and some were not installed conventionally, using a package manager. For that reason, I would pick one of Taco.22's, probably the Scorpio_2013-2. I think the only things you'd need to do are (1) a full update after installation and (2) (optionally) the installation of the latest Thunar.

Or, you could install the DebLXDE respin, do a full update, then remove the LXDE packages.

And what is ths status for Village RC2? Does it need to be tested? Else : which one do you think is ok to work with now, testing, or stable is still the way to go in order to have a reliable install?

Thanks.

[djohnston]

And what is ths status for Village RC2? Does it need to be tested? Else : which one do you think is ok to work with now, testing, or stable is still the way to go in order to have a reliable install?

I picked Scorpio because it's the newer one. Village_RC2_TEST is good to go, as far as I'm concerned. DebWeb is based on one of Taco's earlier efforts. Any of the ones I've mentioned would do fine after being updated. Whether to switch to testing is up to you. However, since this is going to be a "learning platform" for you, I'd say stay with the wheezy (current) repos. There's no sense adding extra problems. Switching to a different Debian repo is a piece of cake. I've already switched the Deb_e17 to unstable branch because it was the only way to get Debian's latest e17 packages. So far, I've had zero problems.

There is one thing you should be aware of. Once you've installed from Village_RC2_TEST or DebLXDE or Scorpio_2013-2, you need to check the installation. I believe they will all have the same problem. There's some cleanup needed after installation. The problem with the Remastersys installer began shortly before fragadelic quit work on Remastersys.

After installation, do as root:

Code: [Sélectionner]

updatedb

Code: [Sélectionner]

locate .squashfs | less
There will be two sets of .squashfs files in your installation that need to be deleted. The first in the list will be one file. Delete it with:

Code: [Sélectionner]

rm /lib/live/mount/medium/live/filesystem.squashfs
The next is a set of files. You'll see them in the listing. You need to take out the whole directory. Do:

Code: [Sélectionner]

rm -rf /lib/live/mount/rootfs/filesystem.squashfs
This is a problem with the last Remastersys installer not doing complete cleanup. I promised I'd look at it, but haven't gotten around to it yet.   

If after making a lot of changes to your installation you should decide to remaster, just shout out if you need any Remastersys pointers. Taco.22 and I have used it many times.