Linux Lite Forums
Problem Upgrading Linux Lite 3.4 - Printable Version

+- Linux Lite Forums (https://www.freecinema2022.gq/forums)
+-- Forum: Software - Support (https://www.freecinema2022.gq/forums/forumdisplay.php?fid=5)
+--- Forum: Installing Linux Lite (https://www.freecinema2022.gq/forums/forumdisplay.php?fid=17)
+--- Thread: Problem Upgrading Linux Lite 3.4 (/showthread.php?tid=4982)

Pages: 1 2

Re: Problem Upgrading Linux Lite 3.4 - mezzmer - 02-20-2018

(02-20-2018, 01:42 PM)bitsnpcs link Wrote: [quote author=mezzmer link=topic=5151.msg39154#msg39154 date=1519115718]
It would be very helpful if the website provided guidance about repos and different versions and what to do about upgrades.  When a repo that was part of the default install disappears it can cause a newer user a lot of grief.
Any constructive suggestions/comments/feedback is much appreciated.

Hello mezzmer,

there is already a tutorial in the Linux Lite Manual here -
https://www.freecinema2022.gq/manual/software.html#literepos

and info plus mirrors here - https://www.freecinema2022.gq/mirrors.php
^ use this link for the correct URL's to the mirrors.
The one you stated as used to Ralphy's mirror is an incomplete URL, there are instructions on the mirror link, it is important because a future member/s may copy/paste this, instead of looking at the official/correct URL's on the mirror link for the instructions.
That can have potential to further extend issues per number of users asking related questions etc.
[/quote]

Thanks for the reply, I went through the tutorial in the manual, and I tried to follow the trail (posted below for ease of reference), and I'm getting closer to my answer.  IIUC, LL only "vets/directly maintains/compiles" only a very tiny subset of the stuff in the Ubuntu Repos, and the vast majority of the info used by package manager are directly taken from Ubuntu.

Question #1
I've come across Release/InRelase in repo names, and I see them in the list (See http://repo.linuxliteos.com/linuxlite/dists/citrine/ below).  What's the difference - How do I know which one should be used when?

Question #2
How do all the extra lines shown in Update From Working v3.8 Virtual Machine successfully upgraded from v3.2 to v3.8 (see below) get picked up?

Question #3
In the posts above where thing were not working there were many more lines when I ran [tt]apt-get update[/tt].  I suspect that my problem came as a result of an incorrect repo list.  How can I prevent/follow changes/troubleshoot to prevent problems in the future?  My thinking is that Ubuntu is making a change, it hasn't been checked/tested by the LL team, I run update, and my installation gets corrupted?  Am I likely right about this, or is there an automated test procedure to screen/filter upstream changes from Ubuntu?

Thanks for the input... I'm getting closer, and hopefully we can create something that will make this problem easier for others in the future.


---------- Support Material Referred to Above ----------
Update From Working v3.8 Virtual Machine successfully upgraded from v3.2 to v3.8
Code:
linuxlite@lite:~$ sudo apt-get update
[sudo] password for linuxlite:
Hit:1 http://repo.linuxliteos.com/linuxlite citrine InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu xenial InRelease                                                                                         
Hit:3 http://security.ubuntu.com/ubuntu xenial-security InRelease                                                                                   
Hit:4 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease                                                                                 
Hit:5 http://ppa.launchpad.net/nemh/systemback/ubuntu xenial InRelease                                                       
Hit:6 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease                         
Hit:7 http://archive.canonical.com xenial InRelease                                               
Hit:8 http://ppa.launchpad.net/otto-kesselgulasch/gimp/ubuntu xenial InRelease                     
Hit:9 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu xenial InRelease       
Reading package lists... Done
--

Repository Structure:
Code:
--
http://repo.linuxliteos.com/linuxlite/
        Name    Last modified       Size    Description
[*]     Parent Directory             -     
[DIR]    conf/    2018-02-15 10:56     -     
[DIR]    db/     2018-01-31 08:25     -     
[DIR]    dists/    2016-04-28 04:13     -     
[DIR]    isos/    2018-01-25 03:26     -     
[DIR]    pool/    2014-05-06 23:47     -     

--
http://repo.linuxliteos.com/linuxlite/dists/
Index of /linuxlite/dists/citrine
        Name        Last modified       Size    Description
[*]     Parent Directory                -     
[DIR]    beryl/      2018-01-29 09:05     -     
[DIR]    citrine/    2018-01-31 08:25     -     

--
http://repo.linuxliteos.com/linuxlite/dists/citrine/
Index of /linuxlite/dists/citrine
[ICO]    Name            Last modified       Size    Description
[*]     Parent Directory                    -     
[ ]     InRelease       2018-01-31 08:25     2.1K    
[ ]     Release            2018-01-31 08:24     1.5K    
[ ]     Release.gpg     2018-01-31 08:24     473     
[DIR]    main/           2016-04-28 04:13      -     
--
http://repo.linuxliteos.com/linuxlite/dists/citrine/main/
Index of /linuxlite/dists/citrine/main
[ICO]    Name            Last modified       Size    Description
[*]        Parent Directory                     -     
[DIR]    binary-amd64/    2018-01-31 08:25     -     
[DIR]    binary-i386/    2018-01-31 08:25     -     
--
http://repo.linuxliteos.com/linuxlite/dists/citrine/InRelease
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Codename: citrine
Date: Wed, 31 Jan 2018 08:24:53 UTC
Architectures: i386 amd64
Components: main
Description: Linux Lite Repository
MD5Sum:
cdee2f1e60fc63d6bf1c530d5f38ff89 75734 main/binary-i386/Packages
7ad745f0d3f4db87d82710ab2deb4d1d 16150 main/binary-i386/Packages.gz
33911ab3dd30930ad76409a2f3701ddd 70 main/binary-i386/Release
e17f58410cb888ae6f443a972a134a76 78541 main/binary-amd64/Packages
fb4fda9228b603c9091da938e969c22d 16775 main/binary-amd64/Packages.gz
6eca642e8beb0c407779c0d649137289 71 main/binary-amd64/Release
SHA1:
11aa9263f49f02ed3bace9efdbc77ddc8488d44e 75734 main/binary-i386/Packages
1e2068ecc8f230ab75867108660b179c4437fb13 16150 main/binary-i386/Packages.gz
80b8a557ff7eda18af683054e8b813173dd2cfb4 70 main/binary-i386/Release
f984a3d2171ea8e1bda57773fc09155af887bc1d 78541 main/binary-amd64/Packages
34831bf0694b8a1b169116094364492ccb48b6a5 16775 main/binary-amd64/Packages.gz
066bb4bdeec42c25e9eda9e5272990bd24e8dfa3 71 main/binary-amd64/Release
SHA256:
71f56862c2854e352c26832f5ef17b320d44af83a50f3f6a9799dad37310dec8 75734 main/binary-i386/Packages
9d4b9d2a24cb0a37ab719a39f448eab1deec48a7b6aa0b863f05242763489007 16150 main/binary-i386/Packages.gz
de0357cfae20d6811d9af6ce27805f062aef8f99df6006d2f678c42dc1a21604 70 main/binary-i386/Release
9df77d53eca0ab3c7e926e8d813070900d93499f2240ce48fff5f92477a5892b 78541 main/binary-amd64/Packages
34fb72a95829808348403f07fddd2b8130a60aafe1eb4c21ea0605ab8a78f4c3 16775 main/binary-amd64/Packages.gz
839e1507ed9d136948f97ac37a792cc666b1966bed7027088d8f232d72faf4fd 71 main/binary-amd64/Release
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBCAAGBQJacX1bAAoJECKq6gqGoCYlpcoH/jlMgtxyOo/2tgc6RQwqX4Fv
RsbjYOyYGNCoVEalArrgjGctKxRBkQYq4Qzo/A0iier3PfHYUxbfnq8uzoMbUxTN
ixQJ9JwX0oMTMLLCvCVkL4f8g7Zqm2ViGxIUHP7Iuj3g0q1ZT3q0t5g5YiwA9F5Q
yDpw3jbweAIV7Az2o9lyMBGiEU3C3DQCHeQyV0gVO/gGGkrSlofPUrouiG2aGouc
fQFMDBny9umnVWGZUmuJQNa1YTrk6mK7/EqEYkhgZFi8aYEwwxcOKj0CqhUsYBqP
Y2LAiIJ5+sqTbi49ge6gCxon8QnmIdSuHhKmsz0SSitMfomFjSy4J8O9NPcy+XI=
=FQBK
-----END PGP SIGNATURE-----
--
http://repo.linuxliteos.com/linuxlite/dists/citrine/Release
Codename: citrine
Date: Wed, 31 Jan 2018 08:24:53 UTC
Architectures: i386 amd64
Components: main
Description: Linux Lite Repository
MD5Sum:
cdee2f1e60fc63d6bf1c530d5f38ff89 75734 main/binary-i386/Packages
7ad745f0d3f4db87d82710ab2deb4d1d 16150 main/binary-i386/Packages.gz
33911ab3dd30930ad76409a2f3701ddd 70 main/binary-i386/Release
e17f58410cb888ae6f443a972a134a76 78541 main/binary-amd64/Packages
fb4fda9228b603c9091da938e969c22d 16775 main/binary-amd64/Packages.gz
6eca642e8beb0c407779c0d649137289 71 main/binary-amd64/Release
SHA1:
11aa9263f49f02ed3bace9efdbc77ddc8488d44e 75734 main/binary-i386/Packages
1e2068ecc8f230ab75867108660b179c4437fb13 16150 main/binary-i386/Packages.gz
80b8a557ff7eda18af683054e8b813173dd2cfb4 70 main/binary-i386/Release
f984a3d2171ea8e1bda57773fc09155af887bc1d 78541 main/binary-amd64/Packages
34831bf0694b8a1b169116094364492ccb48b6a5 16775 main/binary-amd64/Packages.gz
066bb4bdeec42c25e9eda9e5272990bd24e8dfa3 71 main/binary-amd64/Release
SHA256:
71f56862c2854e352c26832f5ef17b320d44af83a50f3f6a9799dad37310dec8 75734 main/binary-i386/Packages
9d4b9d2a24cb0a37ab719a39f448eab1deec48a7b6aa0b863f05242763489007 16150 main/binary-i386/Packages.gz
de0357cfae20d6811d9af6ce27805f062aef8f99df6006d2f678c42dc1a21604 70 main/binary-i386/Release
9df77d53eca0ab3c7e926e8d813070900d93499f2240ce48fff5f92477a5892b 78541 main/binary-amd64/Packages
34fb72a95829808348403f07fddd2b8130a60aafe1eb4c21ea0605ab8a78f4c3 16775 main/binary-amd64/Packages.gz
839e1507ed9d136948f97ac37a792cc666b1966bed7027088d8f232d72faf4fd 71 main/binary-amd64/Release
--
http://repo.linuxliteos.com/linuxlite/dists/citrine/main/binary-amd64/Packages
Sample of one package:

Package: yad
Version: 0.40.2-1
Architecture: amd64
Maintainer: Jerry Bezencon <[email protected]>
Installed-Size: 501
Depends: libc6 (>= 2.7), libcairo2 (>= 1.2.4), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.30.0), libgtk-3-0 (>= 3.0.0), libpango-1.0-0 (>= 1.14.0), libpangocairo-1.0-0 (>= 1.14.0), libsoup2.4-1 (>= 2.33.92), libwebkitgtk-3.0-0 (>= 1.7.92)
Homepage: https://sourceforge.net/projects/yad-dialog/
Priority: extra
Section: x11
Filename: pool/main/y/yad/yad_0.40.2-1_amd64.deb
Size: 215516
SHA256: ce4429787fbe35894587593fcbb60fa36a93b0cf43dec28a7e26d3dbc9a3ae32
SHA1: 1f41c58ab31e9bb42bab962df9fbdb2855a69af8
MD5sum: e45bb4127bdd760ce54963700205e930
Description: Yet Another Dialog - dialogs for shell
Yad (yet another dialog) is a fork of Zenity with many improvements, such
as custom buttons, additional dialogs, pop-up menu in notification icon
and more.
.
This package is built from source by the Linux Lite team. This is done for two
reasons, both in the interests of our community. One, to obtain the latest bug
fixes and two, to get the latest features.

--


---------- Other Info / Feedback -- Not part of original question ----------
To [member=411]bitsnpcs[/member]:
Sorry I was having trouble matching this comment to the original post:
Quote:The one you stated as used to Ralphy's mirror is an incomplete URL, there are instructions on the mirror link, it is important because a future member/s may copy/paste this, instead of looking at the official/correct URL's on the mirror link for the instructions.
.  Can you please be a bit more explicit, and I'll edit the OP so it doesn't screw anybody up.  I'm spending as much time writing this for the benefit of others as solving my own problem.  The big problem with forums is that there isn't a good mechanism for fixing obsolete/wrong info unless posters take responsibility to clean up their own stuff.

---------- Notes on the tutorial ----------

A couple of possible suggestions for corrections or clarification for the benefit of Noobs like me-the doc team may wish to consider adding to the web page.

It appears that the statement:
Open your home folder and navigate to /etc/apt/ right click on the sources.d folder and Open as Administrator.
should read:
Open your home folder and navigate to /etc/apt/ right click on the sources.list.d folder and Open as Administrator.
since that's [tt]sources.list.d[/tt] is what's in the image and the other folder doesn't exist.

Since the info is so far down the page, changing:
See the notes on the Download page for Series information.
to
See the notes on the Download page under ROADMAP for Series information.
would have been helpful.  Used a find for citrine to match things up.  If the page gets out of date and the release info was out of date it would have been very confusing.

Re: Problem Upgrading Linux Lite 3.4 - bitsnpcs - 02-20-2018

(02-20-2018, 08:35 AM)mezzmer link Wrote: ---------- Other Info / Feedback -- Not part of original question ----------
To [member=411]bitsnpcs[/member]:
Sorry I was having trouble matching this comment to the original post:
Can you please be a bit more explicit, and I'll edit the OP so it doesn't screw anybody up. 

[Quote] https://www.freecinema2022.gq/mirrors.php -

REPOSITORY MIRRORS
What is a repository mirror, and why should I use one?
A repository mirror is an online location that stores software packages. In order for software packages to download to you at the best possible speed, it makes sense to choose a location that is closer to you.
How do I change the repository mirror on my computer? Click here.

[glow=red,2,300]Replace repo main[/glow] below from your selected Country repository, with the corresponding name of the release series.
[glow=red,2,300]
eg. deb http://sft.if.usp.br/linuxlite/ repo main
becomes
      deb http://sft.if.usp.br/linuxlite/ citrine main[/glow]
Releases:
Citrine Repositories (citrine main): Linux Lite 3.0 - 3.8
Beryl Repositories (beryl main): Linux Lite 2.0 - 2.8

COUNTRY: USA (West Coast)
FLAG: [img alt=usa width=24 height=24]https://www.freecinema2022.gq/flags/usa.png[/img]
REPO: [glow=red,2,300]deb http://mirror.unlockforus.com/linuxlite/ repo main[/glow]
[size=1em]STATUS:[/size] [size=1em]ONLINE


[/size]

Re: Problem Upgrading Linux Lite 3.4 - mezzmer - 02-20-2018

(02-20-2018, 09:42 PM)bitsnpcs link Wrote: REPOSITORY MIRRORS
What is a repository mirror, and why should I use one?
A repository mirror is an online location that stores software packages. In order for software packages to download to you at the best possible speed, it makes sense to choose a location that is closer to you.
How do I change the repository mirror on my computer? Click here.

Replace repo main below from your selected Country repository, with the corresponding name of the release series.
[glow=red,2,300]
eg. deb http://sft.if.usp.br/linuxlite/ repo main
becomes
deb http://sft.if.usp.br/linuxlite/ citrine main[/glow]
Releases:
Citrine Repositories (citrine main): Linux Lite 3.0 - 3.8
Beryl Repositories (beryl main): Linux Lite 2.0 - 2.8

COUNTRY: USA (West Coast)
FLAG: [img alt=usa width=24 height=24]https://www.freecinema2022.gq/flags/usa.png[/img]
REPO: [glow=red,2,300]deb http://mirror.unlockforus.com/linuxlite/ repo main[/glow]
[size=1em]STATUS:[/size] [size=1em]ONLINE

[/size]
Thanks, I get that part about mirrors... I swiched to the main REPO because at the time I tried to update I was getting errors, and when I switched to the main repo, the errors went away.

Any insight on any of the questions that I asked?

Re: Problem Upgrading Linux Lite 3.4 - bitsnpcs - 02-20-2018

(02-20-2018, 08:15 PM)mezzmer link Wrote: Question #2
How do all the extra lines shown in Update From Working v3.8 Virtual Machine successfully upgraded from v3.2 to v3.8 (see below) get picked up?

These are distro updates, and upstream Ubuntu updates such as security patches.
Also it includes updates for your installed softwares, such as
Gimp
Wine
Systemback

That is updating in Linux updates your distro, upstream base, and kernel, plus all of your installed softwares that may have updates.
Yes also the PPA will update.
Unless you untick the PPA by do -
1. Menu>All>Install Drivers
2. Click "Other software" tab


Re: Problem Upgrading Linux Lite 3.4 - bitsnpcs - 02-20-2018

(02-20-2018, 08:15 PM)mezzmer link Wrote: Question #1
I've come across Release/InRelase in repo names, and I see them in the list (See http://repo.linuxliteos.com/linuxlite/dists/citrine/ below).  What's the difference - How do I know which one should be used when?

Question #3
In the posts above where thing were not working there were many more lines when I ran

Code:
apt-get update

I suspect that my problem came as a result of an incorrect repo list.  How can I prevent/follow changes/troubleshoot to prevent problems in the future?  My thinking is that Ubuntu is making a change, it hasn't been checked/tested by the LL team, I run update, and my installation gets corrupted?  Am I likely right about this, or is there an automated test procedure to screen/filter upstream changes from Ubuntu?

Thanks for the input... I'm getting closer, and hopefully we can create something that will make this problem easier for others in the future.

InRelease is updates for within/to a LTS version

Re;#3 - the each time the updates is run and installed their will not be these same updates the following time if they have installed, then the number of available updates can reduce.
Or if many additional were added during that time frame it can also increase, with those different ones.

It can pull updates same if they are removed or altered enough that they are no longer recognised.