update-notifier and -manager

[GuiGuy]

What question is that you have?

How were we supposed to know that that file should be removed?
How should we remove it? Thunar does not allow me to remove (or rename) it.

Edit: The notifier says 7 updates available, but synaptic shows just six.

[Jerry3904]

What question is that you have?

How were we supposed to know that that file should be removed?
How should we remove it? Thunar does not allow me to remove (or rename) it.

1) We had no knowledge ourselves until the beta was released, and the solution to the problem has emerged during this beta cycle--that's what beta testing is all about!
2) right-click in Thunar > open root Thunar here or, if you prefer, use the usual way in Linux: open a terminal, become root, and start Thunar

[GuiGuy]

..............
2) right-click in Thunar > open root Thunar here or, if you prefer, use the usual way in Linux: open a terminal, become root, and start Thunar

No joy with either method.

Edit:Have at last managed to rename the file.

[kmathern]

If you still have the default /etc/lsb-release file, you can try this in a terminal

Code: Select all

su -c 'mv /etc/lsb-release /etc/lsb-release~'

After doing that

Code: Select all

pkill update-notifier

Restart update-notifier, I do this step from the run command box: Alt+F2 update-notifier <enter>
Check the left-click / right-click actions of update-notifier's icon in the notification area (I'm assuming updates are available)


You can return to the original setup by:

Code: Select all

su -c 'mv /etc/lsb-release~ /etc/lsb-release'

Code: Select all

pkill update-notifier

Alt+F2 update-notifier <enter>
Again check the left-click / right-click actions



edit:
If you've editted or deleted the /etc/lsb-release file, this is what it was originally:

Code: Select all

DISTRIB_ID=MX-14
DISTRIB_RELEASE=14.0
DISTRIB_CODENAME=wheezy
DISTRIB_DESCRIPTION="MX-14"

[anticapitalista]

What is MX 14 using, Debian, Antix, (both of which are distro's in there own right) and the Mepis Community repo,
If you want it as a distro, it would be Debian, plus a mx repo, that is maintained as such,
any other way and it is a remaster, as Anti has said.

Actually, I didn't say it was a remaster, but a respin. MX-14 is not remastered off any existing iso whether that be antiX or MEPIS. It is totally built from scratch using the same scripts that antiX uses to build its isos (ie via debootstrap and chroot). It is not built in a virtual environment either. We do not use debian live, nor siduction/aptosid scripts. The build scripts and live init scripts are home made by BitJam.

[zeeone]

And Away we go.

Fresh cd rw burn with the patches installed.

Fresh install XM-14 beta 1. Apple 15" booting from the OS, on an external usb HD.
Still no Apple laptop keyboard driver at the install, using US keyboard driver.

Start the system. Desktop up, network manager says it is connected to the wired network,
have the update manager icon showing and saying there are 8 updates. It did not launch.
Used cl to update and upgrade. Used thunar under root and removed "/etc/lsb-release" file,
rebooted.

Desktop backup, icon is there saying there are 3 updates, launch Update Manager from the icon.
First we are asked for the root password, enter it. It opens still saying there are 3 updates
(still not showing what they are), continued and ends with "Your System is up-to-date"

Close the manager window, icon is still highlighted and still says "There are 3 updates available"

[kmathern]

...Start the system. Desktop up, network manager says it is connected to the wired network,
have the update manager icon showing and saying there are 8 updates. It did not launch.
Used cl to update and upgrade. Used thunar under root and removed "/etc/lsb-release" file,
rebooted.

Desktop backup, icon is there saying there are 3 updates, launch Update Manager from the icon.
First we are asked for the root password, enter it. It opens still saying there are 3 updates
(still not showing what they are), continued and ends with "Your System is up-to-date"

Close the manager window, icon is still highlighted and still says "There are 3 updates available"

Was your command line upgrade a "apt-get upgrade", or a "apt-get dist-upgrade" ?

With a "apt-get upgrade" I'm seeing 6 upgrades:

Code: Select all

demo@mx1:~
$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages have been kept back:
  vlc vlc-nox
The following packages will be upgraded:
  install-meta-mx libvlc5 libvlccore7 live-init-mx smartmontools vlc-data
6 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Need to get 6,028 kB of archives.
After this operation, 188 kB of additional disk space will be used.
Do you want to continue [Y/n]? n
Abort.

With a dist-upgrade I'm seeing 9 packages in total, 6 upgrades & 3 newly installed:

Code: Select all

demo@mx1:~
$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  libavcodec54 libavformat54 libavutil52
The following packages have been kept back:
  vlc vlc-nox
The following packages will be upgraded:
  install-meta-mx libvlc5 libvlccore7 live-init-mx smartmontools vlc-data
6 upgraded, 3 newly installed, 0 to remove and 2 not upgraded.
Need to get 9,944 kB of archives.
After this operation, 18.0 MB of additional disk space will be used.
Do you want to continue [Y/n]? n
Abort.
demo@mx1:~

The default behaviour for Update Manager might be to do a 'apt-get dist-upgrade', I think it is for Synaptic as well.


The bigger issue for me right now is figuring out why there are vlc & vlc-nox upgrades that have been kept back with both a 'apt-get upgrade' & 'apt-get dist-upgrade'.

[Stevo]

Maybe the repo is resyncing? I just sent a new VLC to Tim that should not pull in the sizable samba client from wheezy-backports.

[kmathern]

Maybe the repo is resyncing? I just sent a new VLC to Tim that should not pull in the sizable samba client from wheezy-backports.

That must be it, it's complaining about wanting the wheezy-backports version of the libsmbclient package

Code: Select all

demo@mx1:~
$ sudo apt-get install vlc/mepis vlc-nox/mepis -s
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Selected version '2.1.2-2mcr120+1' (Mepis community repository:12.0/mepis [i386]) for 'vlc'
Selected version '2.1.2-2mcr120+1' (Mepis community repository:12.0/mepis [i386]) for 'vlc-nox'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 vlc-nox : Depends: libsmbclient (>= 2:4.0.3+dfsg1) but 2:3.6.6-6+deb7u2 is to be installed
           Depends: libswscale2 (>= 6:9.1-1) but 6:0.8.9-1 is to be installed
E: Unable to correct problems, you have held broken packages.
demo@mx1:~

I'll try doing another 'apt-get update' in a little bit, to see if they'll install correctly.

[Stevo]

This is turning into a can of worms...maybe update-notifier could be replaced by a menu entry "check for updates", that runs "apt-get update" in the terminal? It's not as pretty and won't nag the user, but would save a few MB.