LMDE BREAKAGES - tracking TESTING

[zerozero]

if you have MATE installed from the tridex repo, you'll probably see this this today

Code: Select all

Errors were encountered while processing:
 /var/cache/apt/archives/mate-themes_1.2.1-1+wheezy_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Code: Select all

amadeu@amadeu:~$ sudo dpkg -i --force-overwrite /var/cache/apt/archives/mate-themes_1.2.1-1+wheezy_all.deb
(Reading database ... 363652 files and directories currently installed.)
Preparing to replace mate-themes 1.2.0-1 (using .../mate-themes_1.2.1-1+wheezy_all.deb) ...
Unpacking replacement mate-themes ...
dpkg: warning: overriding problem because --force enabled:
 trying to overwrite '/usr/share/themes/Glider/gtk-2.0/gtkrc', which is also in package gnome-themes 2.30.2-1
dpkg: warning: overriding problem because --force enabled:
 trying to overwrite '/usr/share/themes/Glider/index.theme', which is also in package gnome-themes 2.30.2-1
dpkg: warning: overriding problem because --force enabled:
 trying to overwrite '/usr/share/themes/Glider/metacity-1/metacity-theme-1.xml', which is also in package gnome-themes 2.30.2-1
Setting up mate-themes (1.2.1-1+wheezy) ...
Processing triggers for mate-icon-theme ..


important after this run again the dist-upgrade or apt-get -f install (because the process was stopped)

[Lippy]

Upgrading gtk2-engines to version 2.20.2-2 attempts to remove mint-artwork-debian and mint-artwork-xfce. It might be due to it removing the conflicts/replaces with gtk2-engines-clearlooks, which is a dependency of mint-artwork-debian.

In other news, the Mint-X theme has been updated and is now working well. Nice job on the quick fix!

[viking777]

Upgrading gtk2-engines to version 2.20.2-2 attempts to remove mint-artwork-debian and mint-artwork-xfce

I can confirm this as well. I decided to let it be removed (then removed the residual config as well). I have to say I can't see any difference yet. I am sure there must be some but it is invisible to me, then again I am not into 'theming' so maybe that is the reason.

I agree with Lippy gtk-engines-clearlooks is the conflict.

[zerozero]

at this moment i can't get a clean update, i keep getting >>

Reading package lists... Done
W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://packages.linuxmint.com debian Release: The following signatures were invalid: BADSIG 3EE67F3D0FF405B2 Clement Lefebvre (Linux Mint Package Repository v1) <root@linuxmint.com>

probably because the mirrors are "in the move" preparing UP4.

EDIT: solved (whatever it was)

Code: Select all

Calculating upgrade... Done
The following packages will be REMOVED:
  mint-artwork-debian
The following packages will be upgraded:
  aptdaemon aptdaemon-data caja caja-common debian-system-adjustments
  gir1.2-caja gtk2-engines libcaja-extension libcommon-sense-perl
  libdesktop-agnostic-cfg-gconf libdesktop-agnostic-data
  libdesktop-agnostic-fdo-gio libdesktop-agnostic-vfs-gio libdesktop-agnostic0
  libfontenc1 libfs6 libgnome-speech7 libv4l-0 libv4lconvert0 mate-themes
  python-aptdaemon python-aptdaemon.gtk3widgets python-desktop-agnostic
23 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 13.8 MB of archives.
After this operation, 3,567 kB disk space will be freed.
Do you want to continue [Y/n]?


[Bonsaii]

Hi, ZeroZero

I get this error message today:

W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://packages.linuxmint.com debian Release: The following signatures were invalid: BADSIG 3EE67F3D0FF405B2 Clement Lefebvre (Linux Mint Package Repository v1) <root@linuxmint.com>

W: Failed to fetch http://packages.linuxmint.com/dists/debian/Release

W: Some index files failed to download. They have been ignored, or old ones used instead.

How did you get rid of it way back then?

Thanks,
B.

[zerozero]

Bonsaii,
it just went away, try again, maybe the mirror is synced now.

[mockturtl]

Seems okay now, I'm able to safe-upgrade. (Woohoo! Firefox, Thunderbird 11!)

[Chris M]

Upgrading gtk2-engines to version 2.20.2-2 attempts to remove mint-artwork-debian and mint-artwork-xfce

I can confirm this as well. I decided to let it be removed (then removed the residual config as well). I have to say I can't see any difference yet. I am sure there must be some but it is invisible to me, then again I am not into 'theming' so maybe that is the reason.

I agree with Lippy gtk-engines-clearlooks is the conflict.

I get 3 files that will be removed:

mint-artwork-debian
mint-artwork-xfce
mintdesktop-xfce

Pushing forward...

Edit: No real problem with XFCE. But I had the deb http://packages.linuxmint.com/ debian main upstream import commented out in the sources list, and that may account for the mintdesktop-xfce removal.

[Bonsaii]

Thanks, Zerozero,

I want to update and it is getting worse:

W: Failed to fetch http://debian.linuxmint.com/latest/pool ... _amd64.deb
Could not connect to debian.linuxmint.com:80 (204.45.82.130). - connect (111: Connection refused)

W: Failed to fetch http://debian.linuxmint.com/latest/pool ... -3_all.deb
Unable to connect to debian.linuxmint.com:http:

and this list is endless.

Do you have an idea, what I am doing wrong?

Bonsaii

[zerozero]

Upgrading gtk2-engines to version 2.20.2-2 attempts to remove mint-artwork-debian and mint-artwork-xfce

I can confirm this as well. I decided to let it be removed (then removed the residual config as well). I have to say I can't see any difference yet. I am sure there must be some but it is invisible to me, then again I am not into 'theming' so maybe that is the reason.

I agree with Lippy gtk-engines-clearlooks is the conflict.

i get a solid blue now in gdm instead of the mint branding (and i'm sure there's more); 2.20.2-1 is compatible (and is available in latest, let's hope Clem makes mint-artwok-* compatible with the new gtk2-engines soon.

I want to update and it is getting worse:

[...]
Do you have an idea, what I am doing wrong?

Bonsaii

check the blog, http://blog.linuxmint.com/?p=1949 (you're not the only one getting that)

[Bonsaii]

Thanks, zerozero,

You are a star. And thanks for your patience!

Bonsaii

[Lippy]

The update to bash 4.2-2 will ask you if you want to overwrite bash.bashrc with a new config. If you choose not to keep the old config, fortune cookies will stop showing. It is possible to bring it back by opening either /etc/bash.bashrc or ~/.bashrc and adding this line to the bottom of the file:

Code: Select all

/usr/bin/mint-fortune


[äxl]

mate-notification-daemon breaks notification-daemon which is a dependency of gnome-session fallback.
gnome-session fallback needs notification-daemon which breaks mate-notification-daemon.
MND works better with MATE. Not that I "need" Gnome Classic but it would be good to have it hand.

Code: Select all

sudo apt-get -s install gnome-session-fallback
[sudo] password:
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  notification-daemon
Suggested packages:
  desktop-base
The following packages will be REMOVED:
  mate-notification-daemon
The following NEW packages will be installed:
  gnome-session-fallback notification-daemon
0 upgraded, 2 newly installed, 1 to remove and 0 not upgraded.
Remv mate-notification-daemon [1.2.0-1] [gnome-power-manager:amd64 mate-core:amd64 gufw:amd64 mate-power-manager:amd64 ]
Inst notification-daemon (0.7.3-1 Debian:testing [amd64])
Conf notification-daemon (0.7.3-1 Debian:testing [amd64])
Inst gnome-session-fallback (3.2.1-1 Debian:testing [all])
Conf gnome-session-fallback (3.2.1-1 Debian:testing [all])

[zerozero]

yeahh, it should be reported here viewtopic.php?f=206&t=86481

Code: Select all

amadeu@amadeu:~$ sudo apt-get -s install mate-notification-daemon notification-daemon
Reading package lists... Done
Building dependency tree       
Reading state information... Done
notification-daemon is already the newest version.
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:
 mate-notification-daemon : Conflicts: notification-daemon
E: Broken packages
amadeu@amadeu:~$ apt policy mate-notification-daemon notification-daemon
mate-notification-daemon:
  Installed: (none)
  Candidate: 1.2.0-2+wheezy
  Version table:
     1.2.0-2+wheezy 0
        500 http://tridex.net/repo/debian/ wheezy/main amd64 Packages
     1.2.0-1 0
        500 http://packages.linuxmint.com/ debian/import amd64 Packages
notification-daemon:
  Installed: 0.7.4-1
  Candidate: 0.7.4-1
  Version table:
 *** 0.7.4-1 0
        500 http://ftp.debian.org/debian/ testing/main amd64 Packages
        100 /var/lib/dpkg/status


[Bonsaii]

The update went through smoothly today.
So far, all is fine, no problems.

Excellent news: sound has improved (Skype).

Gnome3 takes a bit getting used to,
but evolution is less buggy now.

Overall it is top.
Thanks to Clem and all developers!
And thanks to all helpers here!

[äxl]

yeahh, it should be reported here viewtopic.php?f=206&t=86481

I think they know of that. Next step would be to contribute I guess ...

Code: Select all

500 http://tridex.net/repo/debian/ wheezy/main amd64 Packages

So tridex is a mirror/redirection for the MATE repositories ...

[zerozero]

I think they know of that.

never assume the obvious

So tridex is a mirror/redirection for the MATE repositories ..

there was a time tridex was the only way to have mate
viewtopic.php?f=198&t=87728
http://blog.karapetsas.com/2011/11/24/h ... inux-mint/

[äxl]

never assume the obvious

Look at that output. I'd like to make a package that jumps around with dependencies like that:

Code: Select all

~ $ sudo apt-get install mate-notification-daemon
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be REMOVED:
  notification-daemon
The following NEW packages will be installed:
  mate-notification-daemon
0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
dpkg: notification-daemon: dependency problems, but removing anyway as you requested:
 gnome-power-manager depends on notification-daemon.
 gufw depends on notify-osd | notification-daemon; however:
  Package notify-osd is not installed.
  Package notification-daemon is to be removed.
 mate-core depends on mate-notification-daemon | notification-daemon; however:
  Package mate-notification-daemon is not installed.
  Package notification-daemon is to be removed.
 mate-power-manager depends on mate-notification-daemon | notification-daemon; however:
  Package mate-notification-daemon is not installed.
  Package notification-daemon is to be removed.
(Reading database ... 214885 files and directories currently installed.)
Removing notification-daemon ...
Processing triggers for desktop-file-utils ...
Processing triggers for gnome-menus ...
Selecting previously unselected package mate-notification-daemon.
(Reading database ... 214819 files and directories currently installed.)
Unpacking mate-notification-daemon (from .../mate-notification-daemon_1.2.0-1_amd64.deb) ...
Processing triggers for mate-conf ...
Processing triggers for desktop-file-utils ...
Processing triggers for gnome-menus ...
Processing triggers for hicolor-icon-theme ...
Setting up mate-notification-daemon (1.2.0-1) ...
~ $


The other way around is even hotter:

Code: Select all

~ $ sudo apt-get install notification-daemon
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be REMOVED:
  mate-notification-daemon
The following NEW packages will be installed:
  notification-daemon
0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
dpkg: mate-notification-daemon: dependency problems, but removing anyway as you requested:
 mate-core depends on mate-notification-daemon | notification-daemon; however:
  Package mate-notification-daemon is to be removed.
  Package notification-daemon is not installed.
  Package mate-notification-daemon which provides notification-daemon is to be removed.
 mate-power-manager depends on mate-notification-daemon | notification-daemon; however:
  Package mate-notification-daemon is to be removed.
  Package notification-daemon is not installed.
  Package mate-notification-daemon which provides notification-daemon is to be removed.
 gnome-power-manager depends on notification-daemon; however:
  Package notification-daemon is not installed.
  Package mate-notification-daemon which provides notification-daemon is to be removed.
 gufw depends on notify-osd | notification-daemon; however:
  Package notify-osd is not installed.
  Package notification-daemon is not installed.
  Package mate-notification-daemon which provides notification-daemon is to be removed.
 mate-core depends on mate-notification-daemon | notification-daemon; however:
  Package mate-notification-daemon is to be removed.
  Package notification-daemon is not installed.
  Package mate-notification-daemon which provides notification-daemon is to be removed.
 mate-power-manager depends on mate-notification-daemon | notification-daemon; however:
  Package mate-notification-daemon is to be removed.
  Package notification-daemon is not installed.
  Package mate-notification-daemon which provides notification-daemon is to be removed.
(Reading database ... 214864 files and directories currently installed.)
Removing mate-notification-daemon ...
Processing triggers for hicolor-icon-theme ...
Processing triggers for desktop-file-utils ...
Processing triggers for gnome-menus ...
Processing triggers for mate-conf ...
Selecting previously unselected package notification-daemon.
(Reading database ... 214819 files and directories currently installed.)
Unpacking notification-daemon (from .../notification-daemon_0.7.3-1_amd64.deb) ...
Processing triggers for desktop-file-utils ...
Processing triggers for gnome-menus ...
Setting up notification-daemon (0.7.3-1) ...
~ $

I did this now and everything is fine! C'mon!

[äxl]

there was a time tridex was the only way to have mate
viewtopic.php?f=198&t=87728
http://blog.karapetsas.com/2011/11/24/h ... inux-mint/

So is it okay to take the tridex/mate-desktop repositories into the sources.list and give them a higher apt-pinning of course?
And I already did the former and they show slightly higher versions.

[zerozero]

i believe so (you'll be using newer pkgs from mate, once in awhile get a bug or a oops in an update >> but i think you can handle it )

Code: Select all

amadeu@amadeu ~ $ inxi -r
Repos:     Active apt sources in file: /etc/apt/sources.list
           deb http://packages.linuxmint.com/ debian main import backport romeo upstream
           deb-src http://packages.linuxmint.com/ debian main import backport romeo upstream #Added by software-properties
           deb http://ftp.debian.org/debian testing main contrib non-free
           deb-src http://ftp.debian.org/debian testing main contrib non-free
           deb http://security.debian.org/ testing/updates main contrib non-free
           deb-src http://security.debian.org/ testing/updates main contrib non-free
           deb http://www.debian-multimedia.org testing main non-free
           deb-src http://www.debian-multimedia.org testing main non-free
           deb http://tridex.net/repo/debian/ wheezy main