[SOLVED] Update Manager vs The Instructions

Archived topics about LMDE 1
Locked
TomRoche
Level 4
Level 4
Posts: 248
Joined: Thu Jan 13, 2011 2:52 pm

[SOLVED] Update Manager vs The Instructions

Post by TomRoche » Sun Jun 21, 2015 7:23 pm

summary: I followed The Instructions (with one additional item that IMHO should be added to the tutorial), and achieved what I believed was a successful UP8->LMDE2 `dist-upgrade`. However, after rebooting to my new environment, I got this error dialog=`Update Pack Info` from Update Manager:

Code: Select all

Your system configuration: Your system is not pointing to the Linux Mint repositories. Add 'deb http://packages.linuxmint.com/ debian main upstream import' to your APT sources
Current Update Pack available: N/A
Latest Update Pack used by this system: 8
But that repository is not among those listed in The Instructions to be contained in `/etc/apt/sources.list.d/official-package-repositories.list`: what to do?

solution: Thanks to Monsta's post,
  1. I learned that, by deleting packages={`mint-meta-debian-cinnamon`, `mint-meta-debian-mate`} (since I installed Xfce), I apparently prevented the `dist-upgrading` from replacing package=`mintupdate-debian` with package=`mintupdate`.
  2. Accordingly, I should

    Code: Select all

    $ sudo aptitude remove mintupdate-debian ; sudo aptitude install mintupdate
  3. After doing that (and restarting the hardware Just To Be Sure) Update Manager is without its old `Update Pack Info` UI and thus can't produce the error dialog :-)
details:

I worked through the the instructions to Upgrade from LMDE 1 to LMDE 2 apparently successfully, though I noticed one item that could well be added to that tutorial (more below). To summarize hugely, I upgraded as follows a 10-year-old 32-bit/686-pae laptop with 2 cores, 2 GB RAM, ~100 GB spinning disk, Intel graphics (`inxi -G` -> Intel Mobile 945GM/GMS 943/940GML Express Integrated):
  1. I updated from UP5 to UP8: wasn't too difficult, and I noted no change in function after rebooting into UP8.
  2. (note problem caused by this below) Pre-upgrade I had been using Cinnamon, which seemed to cause problems. Intending to use Xfce in LMDE2, I removed packages={`mint-meta-debian-cinnamon`, `mint-meta-debian-mate`}, intending that they would remove all Cinnamon and MATE packages. (Afterward, I noted some Cinnamon packages remained on the box, so removed them manually.)
  3. I backed up my previous `/etc/apt/sources.list`, then deleted `/etc/apt/sources.list`
  4. To my current `/etc/apt/sources.list.d/` (which already contained `google-chrome.list`, though no other files), I added root-owned file=`official-package-repositories.list` containing

    Code: Select all

    deb http://packages.linuxmint.com betsy main upstream import
    deb http://http.debian.net/debian jessie main contrib non-free
    deb http://http.debian.net/debian jessie-updates main contrib non-free
    deb http://security.debian.org jessie/updates main contrib non-free
    deb http://www.deb-multimedia.org jessie main non-free
    deb http://extra.linuxmint.com betsy main
  5. I also installed packages={`debian-archive-keyring`, `deb-multimedia-keyring`, `sysvinit-core`}. (Installing packages={`adwaita-icon-theme`, `blueberry`} was too painful, so I deferred that until the next step.) I long before had turned off the screensaver, but checked to be sure.
  6. I traversed the following loop several times:
    1. `sudo aptitude dist-upgrade`
    2. resolve declared package conflicts and dependency failures
    until at last `sudo aptitude dist-upgrade` ran clean
  7. After end of first complete run of `sudo aptitude dist-upgrade`, I verified that

    Code: Select all

    $ date ; sudo aptitude dist-upgrade
    Sun Jun 21 16:34:52 EDT 2015
    No packages will be installed, upgraded, or removed.
    0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    Need to get 0 B of archives. After unpacking 0 B will be used.
  8. I installed Xfce (

    Code: Select all

    sudo aptitude install xfce4 xfce4-goodies
    )
  9. I rebooted, and noticed that GRUB (which had updated from version=1.99... to version=2.02...) was still booting the same old kernel version='3.2.0-4-686-pae'
  10. (TODO: add this to The Instructions for i686/PAE hardware users) I updated the PAE kernel with

    Code: Select all

    sudo aptitude install linux-headers-686-pae linux-image-686-pae
    and rebooted.
  11. I noted on restart that I was now booting kernel version='3.16.0-4-686-pae'
However I then noted (after starting Xfce) the following problem with Update Manager. (Note again that, after `sudo aptitude update`, both `sudo aptitude dist-upgrade` and `sudo aptitude dist-upgrade` claim nothing to do.) Update Manager shows in the Xfce (top) panel with the Green Checkmark of Happiness(tm). However, if I start Update Manager (by clicking on its panel icon) and then click on button=`Update Pack Info`, the resulting dialog=`Update Pack Info` raises error, with the following message (in the body of the dialog):

Code: Select all

Your system configuration: Your system is not pointing to the Linux Mint repositories. Add 'deb http://packages.linuxmint.com/ debian main upstream import' to your APT sources
Current Update Pack available: N/A
Latest Update Pack used by this system: 8
However The Instructions seem pretty clear about what should be in `/etc/apt/sources.list.d/official-package-repositories.list`:
Step 1 - Modify your APT Source

First, we need to point the computer at the LMDE 2 "Betsy" repositories.

As root, edit /etc/apt/sources.list.d/official-package-repositories.list to make it look like this:

deb http://packages.linuxmint.com betsy main upstream import
deb http://http.debian.net/debian jessie main contrib non-free
deb http://http.debian.net/debian jessie-updates main contrib non-free
deb http://security.debian.org jessie/updates main contrib non-free
deb http://www.deb-multimedia.org jessie main non-free
deb http://extra.linuxmint.com betsy main
Note particularly that the first line above is

deb http://packages.linuxmint.com betsy main upstream import

and not

deb http://packages.linuxmint.com/ debian main upstream import

as directed by the Update Manager error dialog. (I'm assuming that the trailing slash on the URI is not important--am I missing something?) This turned out to be due to my `dist-upgrade` not having replaced package=`mintupdate-debian` with package=`mintupdate`, which appears to be due (per this post from Monsta) due to deleting packages={`mint-meta-debian-cinnamon`, `mint-meta-debian-mate`}. I fixed the problem by

Code: Select all

$ date ; sudo aptitude remove mintupdate-debian
Sun Jun 21 19:41:44 EDT 2015
The following packages will be REMOVED:
  mintupdate-debian
0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
...
Removing mintupdate-debian (1.1.1) ...
Processing triggers for gnome-menus (3.13.3-6) ...
Processing triggers for mime-support (3.58) ...
Processing triggers for desktop-file-utils (0.22-1) ...

$ date ; sudo aptitude install mintupdate
Sun Jun 21 19:42:48 EDT 2015
The following NEW packages will be installed:
  mint-mirrors{a} mintupdate python-configobj{a}
0 packages upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
...
Processing triggers for gnome-menus (3.13.3-6) ...
Processing triggers for mime-support (3.58) ...
Processing triggers for desktop-file-utils (0.22-1) ...
Setting up mint-mirrors (1.1.2) ...
Setting up python-configobj (5.0.6-1) ...
Setting up mintupdate (4.8.4) ...
Installing new version of config file /etc/xdg/autostart/mintupdate.desktop ...
Upon restarting the hardware, Update Manager is without its old `Update Pack Info` UI (and thus can't produce the error dialog :-)
Last edited by TomRoche on Mon Jun 22, 2015 6:30 pm, edited 1 time in total.

Distro-Don
Level 3
Level 3
Posts: 149
Joined: Thu May 23, 2013 8:43 pm

Re: [SOLVED] Update Manager vs The Instructions

Post by Distro-Don » Sun Jun 21, 2015 8:20 pm

I always find it much easier to install the latest version of any Linux version such as Betsy-2 and then run my "easy upgrade program, ezup.sh".
Attachments
Screenshot-ezup.sh (-archives) - pluma-1.png
Last edited by Distro-Don on Thu Jun 25, 2015 9:09 pm, edited 2 times in total.

TomRoche
Level 4
Level 4
Posts: 248
Joined: Thu Jan 13, 2011 2:52 pm

missing the point of rolling release

Post by TomRoche » Mon Jun 22, 2015 11:33 am

Distro-Don wrote:I always find it much easier to install the latest version
Your claim is only true iff you have no significant local configuration (or, for that matter, non-package-installed apps) to restore. The reason for having a rolling release--indeed, the main reason for using LMDE--is because restoring local configuration after an install is painful for folks who customize extensively ("power users" et al).

User avatar
killer de bug
Level 14
Level 14
Posts: 5415
Joined: Tue Jul 08, 2008 1:49 pm
Location: Leuven, Belgium

Re: missing the point of rolling release

Post by killer de bug » Mon Jun 22, 2015 2:21 pm

TomRoche wrote: -indeed, the main reason for using LMDE--is because restoring local configuration after an install is painful for folks who customize extensively ("power users" et al).
Agreed! I don't want to spent 1 day tuning my system again to be exactly perfectly shaped for my use. I did this once 3 years ago, no need to do it again. :wink:
If it ain't broke, fix it until it is.

Distro-Don
Level 3
Level 3
Posts: 149
Joined: Thu May 23, 2013 8:43 pm

Re: [SOLVED] Update Manager vs The Instructions

Post by Distro-Don » Mon Jun 22, 2015 5:27 pm

The reason I am called, Distro-Don, is because I have used and handed out so many different distributions over the years. I started by building a Southwest Technical Products computer kit in 1974. The reason I haven't had any trouble with any of them yet is because I know what to include and what not to include in my data package and link that into each distribution. By doing it this way I do not need to have a separate home partition. Each distribution has its own /home and each are/can be a little or a lot different from all the others. After installing a Debian based distribution, I can have it completely configured and customized in less than 30 minutes.

TomRoche
Level 4
Level 4
Posts: 248
Joined: Thu Jan 13, 2011 2:52 pm

Re: missing the point of rolling release

Post by TomRoche » Mon Jun 22, 2015 6:01 pm

Distro-Don wrote:After installing a Debian based distribution, I can have it completely configured and customized in less than 30 minutes.
Perhaps you should be called "Don Sequitur" instead :-) Because, again, you seem oblivious regarding why one uses a rolling release.

Distro-Don
Level 3
Level 3
Posts: 149
Joined: Thu May 23, 2013 8:43 pm

Re: missing the point of rolling release

Post by Distro-Don » Thu Jun 25, 2015 9:13 pm

TomRoche wrote:
Distro-Don wrote:After installing a Debian based distribution, I can have it completely configured and customized in less than 30 minutes.
Perhaps you should be called "Don Sequitur" instead :-) Because, again, you seem oblivious regarding why one uses a rolling release.
I know why I don't care if it is rolling or not. It is because I can make any release just the way I want it in a shorter time than any other way that I know of.

Distro-Don
Level 3
Level 3
Posts: 149
Joined: Thu May 23, 2013 8:43 pm

Re: missing the point of rolling release

Post by Distro-Don » Thu Jun 25, 2015 10:58 pm

TomRoche wrote:
Distro-Don wrote:After installing a Debian based distribution, I can have it completely configured and customized in less than 30 minutes.
Perhaps you should be called "Don Sequitur" instead :-) Because, again, you seem oblivious regarding why one uses a rolling release.
Sticks and stones...

Locked

Return to “LMDE 1 Archive”