Lazarus

Programming => Operating Systems => Linux => Topic started by: Hartmut on August 30, 2018, 10:40:50 am

Title: [SOLVED] Ubuntu: Lazarus-Installation lost by System-Update - how to prevent?
Post by: Hartmut on August 30, 2018, 10:40:50 am
During an automatic System-Update my Lazarus Installation was automaticilly deinstalled. In Synaptic I can still see fpc, fpc-3.0.4 and fpc-source-3.0.4, but fpc-source and Lazarus are missing. I am not amused.

This is the way how I installed Lazarus 1.8.4 with fpc 3.0.4 less then 2 days ago:
1) uninstalled all fpc* and lazarus* packages
2) downloaded 3 packages (fpc, fpc-src and lazarus) from the web site (http://www.lazarus-ide.org/)
3) moved this 3 packages to my home folder
4) installed package "libgtk2.0-dev"
5) executed "sudo dpkg -i ~/*.deb" in my home folder

Bevor I repeat the next installation, I want to learn how to prevent another automatic deinstallation.

I heared about version locking with Synaptic, but did this never before. I found there Menu "Package / Lock version". Is this the right way? Which packages exactly must I lock (there are so many after Lazarus/fpc is installed)?

I am a bloody beginner on Linux (started just a week ago). So please be a little more detailed with your answers. My Ubuntu is 18.04. Thanks a lot in advance.
Title: Re: Ubuntu: Lazarus-Installation lost by System-Update - how to prevent this?
Post by: JuhaManninen on August 30, 2018, 10:56:49 am
Uhhh... you are not the first one. :(
There is another active thread about the issue as you may have noticed:
 http://forum.lazarus-ide.org/index.php/topic,42387.0.html

A short answer is: avoid .dep packages.
Longer answers are in the other thread.

People, we should add a sticky forum post explaining the easiest ways to install FPC and Lazarus in Debian related systems.
Only the last option would be to use .deb packages. They must not be recommended for new Linux users, or maybe not for anybody.
Title: Re: Ubuntu: Lazarus-Installation lost by System-Update - how to prevent this?
Post by: Handoko on August 30, 2018, 11:00:46 am
@Hartmut

I only version locked the fpc package. So far never have any issue.

On Synaptic Package Manager, the version-locked item can be found by clicking Status > Pinned. That item usually marked red and has a padlock icon at its side.

Note:
This thread is similar with:
https://forum.lazarus.freepascal.org/index.php/topic,42387.0.html
Moderator, please merge them together.
Title: Re: Ubuntu: Lazarus-Installation lost by System-Update - how to prevent this?
Post by: JuhaManninen on August 30, 2018, 11:06:27 am
This thread is similar with:
https://forum.lazarus.freepascal.org/index.php/topic,42387.0.html
Moderator, please merge them together.
IIRC there are hundreds of similar threads. Then we should merge them all. Not realistic.
Title: Re: Ubuntu: Lazarus-Installation lost by System-Update - how to prevent this?
Post by: valdir.marcos on August 30, 2018, 11:33:16 am
This thread is similar with:
https://forum.lazarus.freepascal.org/index.php/topic,42387.0.html
Moderator, please merge them together.
IIRC there are hundreds of similar threads. Then we should merge them all. Not realistic.
Maybe create a wiki page with explanation and possible solutions? Maybe a FAQ?
Title: Re: Ubuntu: Lazarus-Installation lost by System-Update - how to prevent this?
Post by: Hartmut on August 30, 2018, 01:13:12 pm
There is another active thread about the issue as you may have noticed:
http://forum.lazarus-ide.org/index.php/topic,42387.0.html

A short answer is: avoid .dep packages.
Longer answers are in the other thread.

I walked through that topic twice and for me as an absolute beginner to Linux it is extremely hard to understand. What I learned is, that installation of Lazarus on Ubuntu is a common problem and that most people say "avoid *.deb files".

But the problem of dfergfla was an automatic update of his FPC, my problem was the  automatic deinstall of Lazarus.

From that topic I could not extract clear instructions about the right way to install Lazarus on Ubuntu. Only for Manjaro, but I don't want to change my distribution now. So I hope for clear and easy instructions for Ubuntu 18.04, that an absolute beginner can master. Thanks in advance.
Title: Re: Ubuntu: Lazarus-Installation lost by System-Update - how to prevent this?
Post by: Hartmut on August 30, 2018, 01:14:50 pm
I only version locked the fpc package. So far never have any issue.

@Handoko: hello again.

Are you sure that a lock on fpc is my solution? My problem was the deinstall of Lazarus, not an update of fpc.

And what would you recommend how to repeat my Lazarus installation?
Title: Re: Ubuntu: Lazarus-Installation lost by System-Update - how to prevent this?
Post by: marcov on August 30, 2018, 01:27:52 pm
To me it sounds like a conflict between external repo and in-repo packages.

That could be avoided by renaming the external (lazarus site) packages to set them clearly apart. (renaming at the package file level, not just the filename)
Title: Re: Ubuntu: Lazarus-Installation lost by System-Update - how to prevent this?
Post by: JuhaManninen on August 30, 2018, 01:29:09 pm
But the problem of dfergfla was an automatic update of his FPC, my problem was the  automatic deinstall of Lazarus.
Makes no difference. The system got screwed after using external packages. I have seen that many times.

Quote
So I hope for clear and easy instructions for Ubuntu 18.04, that an absolute beginner can master. Thanks in advance.
Here comes:
First uninstall the external FPC and Lazarus packages. Then:
Code: [Select]
sudo apt-get install subversionif you don't have subversion installed already. Then:
Code: [Select]
sudo apt-get install fpcThis gives you the distro's "official" FPC, either 3.0.2 or 3.0.4. They are good for compiling Lazarus. Then in your home dir:
Code: [Select]
svn co https://svn.freepascal.org/svn/lazarus/branches/fixes_1_8/ lazarus_1_8
cd lazarus_1_8
make
./lazarus
...and there you go!
Actually it requires GTK2 related development packages but I guess you already have them after your experiments.
Title: Re: Ubuntu: Lazarus-Installation lost by System-Update - how to prevent this?
Post by: JuhaManninen on August 30, 2018, 01:32:08 pm
To me it sounds like a conflict between external repo and in-repo packages.
That could be avoided by renaming the external (lazarus site) packages to set them clearly apart. (renaming at the package file level, not just the filename)
Let's not confuse him more. :)
Title: Re: Ubuntu: Lazarus-Installation lost by System-Update - how to prevent this?
Post by: Handoko on August 30, 2018, 02:26:50 pm
I only version locked the fpc package. So far never have any issue.
Are you sure that a lock on fpc is my solution? My problem was the deinstall of Lazarus, not an update of fpc.

Your case might be different. But what happened on my case was my Ubuntu was holding a broken package (which caused by the software update), I knew it because I checked using Synaptic Package Manager. I simply uninstalled that broken package, reboot the computer, remove all the lazarus/fp* related items and reinstall the things I want ... everything just back to normal.



For you information. You should use the installation provided by Ubuntu, it is the most easiest thing to do. Unless, you want to use the version you that has not been available on the Ubuntu repository yet. For example, Lazarus just makes a new release available.

All this Lazarus-Ubuntu troubles only happen because you're not using the installation packages provided by your Ubuntu. I'm not sure but I guess Lazarus 1.8.4 should now already been available on Ubuntu repository.

So for ubuntu users: don't use the deb files downloaded from SourceForge.

But if you're adventurous :D, here are my advices:

Make sure you have some knowledge in using Linux Terminal or at least you've already installed some tools to make it easier. I'm not very good in using Linux Terminal, so I prefer the GUI tools. I recommend Synaptic Package Manager and GDebi.

Pay attention and write down all the steps you're doing. So you can review and roll back if anything goes wrong.

You may need to disconnect the Internet. Not always but it ever happened on my test, Ubuntu automatically downloaded and forced me to use the packages from its repository when installing Lazarus/FPC from the deb files I got from SourceForge.

And don't forget doing version locking.



My solution is not the only solutions. You may tried @JuhaManninen suggestion to manually build your own Lazarus or @bylaardt trick to modify the deb files. I haven't tried them but they should work.

JuhaManninen's how to build your own Lazarus from source:
https://forum.lazarus.freepascal.org/index.php/topic,42393.msg295887.html#msg295887

bylaardt's how to modify the deb files:
https://forum.lazarus.freepascal.org/index.php/topic,41333.msg287683.html#msg287683
Title: Re: Ubuntu: Lazarus-Installation lost by System-Update - how to prevent this?
Post by: Hartmut on August 30, 2018, 06:22:27 pm
You should use the installation provided by Ubuntu, it is the most easiest thing to do ... All this Lazarus-Ubuntu troubles only happen because you're not using the installation packages provided by your Ubuntu.

My very 1st Lazarus Installation was by "sudo apt-get install lazarus" which I think is the "official Ubuntu way", or not? But exactly with this installation we had so much trouble, see http://forum.lazarus.freepascal.org/index.php/topic,42364.0.html. So for now I wanted to go another way.

First uninstall the external FPC and Lazarus packages. Then:
Code: [Select]
sudo apt-get install subversionif you don't have subversion installed already. Then:
Code: [Select]
sudo apt-get install fpcThis gives you the distro's "official" FPC, either 3.0.2 or 3.0.4. They are good for compiling Lazarus. Then in your home dir:
Code: [Select]
svn co https://svn.freepascal.org/svn/lazarus/branches/fixes_1_8/ lazarus_1_8
cd lazarus_1_8
make
./lazarus
...and there you go!

Thank you for this easy to follow instructions. I could execute them without problems. As a test I did an IDE rebuild and got no errors.

To be able to cross compile 32 bit programs then I tried the 9 steps from Handoko in http://forum.lazarus.freepascal.org/index.php/topic,42364.0.html reply #1, but step 7 gave me the same error message then 3 days before: "make: *** Keine Regel, um „clean“ zu erstellen.  Schluss". This means "no rule to create "clean". Finish" (see attached screenshot).

That meens my installation now has the same problem then my very 1st installation by "sudo apt-get install lazarus" :-((

My folder /usr/share/fpcsrc/3.0.4/ contains 4 folders and 2 files, but no Makefile (see screenshot).

What shall I do?
Title: Re: Ubuntu: Lazarus-Installation lost by System-Update - how to prevent this?
Post by: Handoko on August 30, 2018, 06:30:08 pm
I guess the problem is on step #6:
06. cd /usr/share/fpcsrc/3.0.4

The fpcsrc is not on the location. Where do you save the downloaded file? Is it on [your_home_folder]/lazarus_1_8 ?


Please ignore this post. :-[
Title: Re: Ubuntu: Lazarus-Installation lost by System-Update - how to prevent this?
Post by: Hartmut on August 30, 2018, 06:41:59 pm
Sorry, I don't understand your question.
Folder /usr/share/fpcsrc/3.0.4/ contains about 360 MB files.

The fpcsrc is not on the location. Where do you save the downloaded file?
Which location and which downloaded file do you mean? I followed the instructions of JuhaManninen exactly. Do you mean his svn-command? I used
"lazarus_1_8" as recommended. Thanks for your help!
Title: Re: Ubuntu: Lazarus-Installation lost by System-Update - how to prevent this?
Post by: JuhaManninen on August 30, 2018, 07:18:10 pm
My folder /usr/share/fpcsrc/3.0.4/ contains 4 folders and 2 files, but no Makefile (see screenshot).
Maybe they are in a devel package, fpc-dev or similar. I don't have Ubuntu around now.
I did not know you need a cross-compiler. It is always more tricky than just installing a native compiler. I have not learned the cross-compiler stuff really, I always compile in a native OS using a virtual machine or so.
Title: Re: Ubuntu: Lazarus-Installation lost by System-Update - how to prevent this?
Post by: Handoko on August 30, 2018, 07:25:37 pm
I just tried to install the fpc packages provided by Ubuntu. And these are what I found:

- There is no fpc-dev or similar packages in Ubuntu repository.
- There are no makefiles in .../fpcsrc/3.0.4 if installing FPC using Ubuntu repository.
- Currently Ubuntu only provides Lazarus version 1.8.2.

I checked fpc's trunk, yes I can see the makefiles are there:
https://svn.freepascal.org/cgi-bin/viewvc.cgi/trunk/

>:( It seems Ubuntu guys remove the makefiles or hide them to somewhere we cannot find.



@Hartmut

Sad, but I have to tell you. This is the only last thing you can do ... remove all your Lazarus/FPC related installations and then install them again using the steps I provided here:
https://forum.lazarus.freepascal.org/index.php/topic,41524.0.html

Of course you can abandon Ubuntu and use other distros if you want.
Most people here recommend Manjaro.
 ;D
Title: Re: Ubuntu: Lazarus-Installation lost by System-Update - how to prevent this?
Post by: Hartmut on August 30, 2018, 08:10:28 pm
I just tried to install the fpc packages provided by Ubuntu. And these are what I found:

- There is no fpc-dev or similar packages in Ubuntu repository.
- There are no makefiles in .../fpcsrc/3.0.4 if installing FPC using Ubuntu repository.
- Currently Ubuntu only provide Lazarus version 1.8.2.

I checked fpc's trunk, yes I can see the makefiles are there:
https://svn.freepascal.org/cgi-bin/viewvc.cgi/trunk/

I seems Ubuntu guys remove the makefiles or hide them to somewhere we cannot find.
Thank you for that valuable information, also for other people.

I will follow your installation steps in https://forum.lazarus.freepascal.org/index.php/topic,41524.0.html (like I started 2 days ago and then stuck in step 6, where you told me to do this step twice: once with internet connection enabled and once without).

As soon as I have a result I will report it here, but this might be tomorrow.
Title: Re: Ubuntu: Lazarus-Installation lost by System-Update - how to prevent this?
Post by: Handoko on August 30, 2018, 08:36:01 pm
I've just reinstalled back my Lazarus 1.8.4 and I can saw the makefiles are back now.

FYI, I just found the GDebi now behaves differently, which I guess was caused by Ubuntu update. If you click the 'install' button on GDebi, it will exit immediately. You need to start the GDebi as the superuser if you want to install a new package.

If this behavior also happens on you, here is what you need to:
Instead of double clicking the deb file, you start the GDebi by using Linux Terminal
sudo gdebi-gtk, then use File > Open to open the deb file.
Title: Re: Ubuntu: Lazarus-Installation lost by System-Update - how to prevent this?
Post by: Hartmut on August 31, 2018, 09:28:57 pm
FYI, I just found the GDebi now behaves differently, which I guess was caused by Ubuntu update. If you click the 'install' button on GDebi, it will exit immediately. You need to start the GDebi as the superuser if you want to install a new package.
Thank you for that info, so I could postpone the GDebi update and do it the old way.
Title: Re: Ubuntu: Lazarus-Installation lost by System-Update - how to prevent this?
Post by: Hartmut on August 31, 2018, 09:34:56 pm
Now it works!

I installed Lazarus according to https://forum.lazarus.freepascal.org/index.php/topic,41524.0.html:
 - Step 6 I did without internet connection, which was only possible, because a couple of packages had been downloaded already on an earlier try.
 - Steps 7..9 were not neccessary.
 - In Step 12 I locked "fpc" and "fpc-src"

Then I could do the steps to be able to cross compile 32 bit programs with a 64 bit Lazarus, which are described in reply #1 of http://forum.lazarus.freepascal.org/index.php/topic,42364.15.html (take care of the correction for steps 2 and 3 in reply #3).

After all I started a System-Update, but nothing was deinstalled or destroyed :-)

Thank you very much to all who helped me, especially to Handoko for his continuous help. This is a great forum!

Update:
If you use KDE-Plasma desktop, then this might be important:
Version locking via Synaptic seems not to be the right way on KDE-Plasma desktop.
I did it, but update of fpc package was still offered during system update. KDE-Plasma desktop seems to use Muon package manager. I repeated version locking in Muon and update of fpc package was not longer offered :-)

I'm an absolute beginner on Linux, so I am not sure. Maybe one of the experts can prove this?
Title: Re: Ubuntu: Lazarus-Installation lost by System-Update - how to prevent this?
Post by: Handoko on August 31, 2018, 09:39:45 pm
Thank you reporting the result.

Someone recently said it didn't work. But I tried to reproduce the issue yesterday, reinstalled and did version locking. It seems to work, everything is just okay. I now lock the fpc only, lets see what will happen.

If anything bad happen with your Lazarus-Ubuntu installation, please let us know.
Title: Re: Ubuntu: Lazarus-Installation lost by System-Update - how to prevent this?
Post by: prof7bit on September 10, 2018, 08:54:35 pm
@Hartmut

I only version locked the fpc package. So far never have any issue.

On Synaptic Package Manager, the version-locked item can be found by clicking Status > Pinned. That item usually marked red and has a padlock icon at its side.

Version locking in synaptic does not work. It only affects upgrades made through synaptic itself, it does not have any influence on command line apt-get. Real pinning should be done in /etc/apt/preferences.d/ and synaptic does not store the pinned packages anywhere in that folder, it apparently uses its own private database for these settings and apt-get cannot see it and will know nothing about these pseudo "pins" in synaptic.

I am still investigating how this ugly problem can be solved without too much trouble. If I can not find any graphical apt frontend that supports real apt pinning it probably must be done manually in the /etc/apt/prefereces.d/


---

The following contents in /etc/apt/preferences (or in any file in the folder /etc/apt/preferences.d) will prevent the problem:

Code: [Select]
Package: fpc
Pin: version 3.0.4
Pin-Priority: 1000

it can be tested with the following command:

Code: [Select]
apt list --upgradeable

this will output a list of packages that would be upgraded, if fpc is in the list it did not work, if fpc disappears from the list after the above file has been created then it is safe again to do do apt-get dist-upgrade.

---

Upstream devs should choose a version number for their deb package that is safe from being regarded as older than any Ubuntu repo versions, or maybe even give it a different name to avoid collisions altogether, there should be possibilities to do this within the rules of the naming conventions, maybe I'm going to file a bug after I have studied the version number formatting conventions and rules and figured out a way.
Title: Re: Ubuntu: Lazarus-Installation lost by System-Update - how to prevent this?
Post by: Hartmut on September 10, 2018, 10:08:58 pm
I am still investigating how this ugly problem can be solved without too much trouble. If I can not find any graphical apt frontend that supports real apt pinning it probably must be done manually in the /etc/apt/prefereces.d/

After I locked package "fpc" via Muon package manager (see reply #19) I entered
Code: [Select]
apt list --upgradeableand package "fpc" was not listed. So mybe your graphical frontend is found. I tried it on Ubuntu 18.04 with KDE-Plasma Desktop.
Title: Re: Ubuntu: Lazarus-Installation lost by System-Update - how to prevent this?
Post by: lucamar on September 10, 2018, 10:51:07 pm
I am still investigating how this ugly problem can be solved without too much trouble. If I can not find any graphical apt frontend that supports real apt pinning it probably must be done manually in the /etc/apt/prefereces.d/

Aparently, Muon does it right (?). As said in a previous post:

Version locking via Synaptic seems not to be the right way on KDE-Plasma desktop.
I did it, but update of fpc package was still offered during system update. KDE-Plasma desktop seems to use Muon package manager. I repeated version locking in Muon and update of fpc package was not longer offered :-)
Title: Re: [SOLVED] Ubuntu: Lazarus-Installation lost by System-Update - how to prevent?
Post by: Handoko on September 11, 2018, 04:06:40 am
Thank you for reporting back. I never use KDE Plasma Desktop, I will later investigate the problem. What distro should I try? Kubuntu?
Title: Re: [SOLVED] Ubuntu: Lazarus-Installation lost by System-Update - how to prevent?
Post by: Hartmut on September 11, 2018, 10:59:54 am
Thank you for reporting back. I never use KDE Plasma Desktop, I will later investigate the problem. What distro should I try? Kubuntu?

KDE Plasma desktop comes with Kubuntu. But I installed first Ubuntu 18.04 (which came with Gnome3 desktop) and switched later to KDE Plasma desktop via "sudo apt install kubuntu-desktop".
Title: Re: Ubuntu: Lazarus-Installation lost by System-Update - how to prevent this?
Post by: prof7bit on September 11, 2018, 01:20:44 pm
Version locking via Synaptic seems not to be the right way on KDE-Plasma desktop.
I did it, but update of fpc package was still offered during system update. KDE-Plasma desktop seems to use Muon package manager.

Apparently Muon uses the proper way[TM] to pin a package which is adding an entry to apt preferences, that way *every* updater tool that uses apt and also plain old apt-get on the command line will respect this setting.
Title: Re: [SOLVED] Ubuntu: Lazarus-Installation lost by System-Update - how to prevent?
Post by: prof7bit on September 11, 2018, 07:00:57 pm
There is an even more generic way than pinning by version number:

create a new file
/etc/apt/preferences.d/fpc
Code: [Select]
Package: fpc*
Pin: release a=now
Pin-Priority: 1001

The a=now filter matches manually installed packages that were installed with dpkg and the priority >1000 ensures that it will always have higher priority than every other package source, even those with higher versions. And because we don't mention a specific version number it would stay that way and still work if you later install the next version manually and Ubuntu then releases an even higher version number too.

If you issue the command
apt-cache policy
you will see the following output:
Code: [Select]
Package files:
 100 /var/lib/dpkg/status
     release a=now
 500 http://security.ubuntu.com/ubuntu bionic-security/multiverse i386 Packages
     release v=18.04,o=Ubuntu,a=bionic-security,n=bionic,l=Ubuntu,c=multiverse,b=i386
     origin security.ubuntu.com
 500 http://security.ubuntu.com/ubuntu bionic-security/universe i386 Packages
     release v=18.04,o=Ubuntu,a=bionic-security,n=bionic,l=Ubuntu,c=universe,b=i386
     origin security.ubuntu.com
 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages
     release v=18.04,o=Ubuntu,a=bionic-security,n=bionic,l=Ubuntu,c=main,b=i386
     origin security.ubuntu.com
 100 http://de.archive.ubuntu.com/ubuntu bionic-backports/universe i386 Packages
     release v=18.04,o=Ubuntu,a=bionic-backports,n=bionic,l=Ubuntu,c=universe,b=i386
     origin de.archive.ubuntu.com
 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/multiverse i386 Packages
     release v=18.04,o=Ubuntu,a=bionic-updates,n=bionic,l=Ubuntu,c=multiverse,b=i386
     origin de.archive.ubuntu.com
 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages
     release v=18.04,o=Ubuntu,a=bionic-updates,n=bionic,l=Ubuntu,c=universe,b=i386
     origin de.archive.ubuntu.com
 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages
     release v=18.04,o=Ubuntu,a=bionic-updates,n=bionic,l=Ubuntu,c=main,b=i386
     origin de.archive.ubuntu.com
 500 http://de.archive.ubuntu.com/ubuntu bionic/multiverse i386 Packages
     release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=multiverse,b=i386
     origin de.archive.ubuntu.com
 500 http://de.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
     release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=universe,b=i386
     origin de.archive.ubuntu.com
 500 http://de.archive.ubuntu.com/ubuntu bionic/restricted i386 Packages
     release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=restricted,b=i386
     origin de.archive.ubuntu.com
 500 http://de.archive.ubuntu.com/ubuntu bionic/main i386 Packages
     release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=main,b=i386
     origin de.archive.ubuntu.com
Pinned packages:
     fpc -> 3.0.4 with priority 1001
     fpc-src -> 3.0.4 with priority 1001

In the last two lines you can see that it has matched my manually installed fpc-3.0.4 and fpc-src-3.0.4 and gave them priority 1001 (which means always keep this, even if higher versions from other repositories are available)

An alternative way that also works would be to match release o=Ubuntu and give it priority of -1 which means "never install", this has the effect of effectively blacklisting all fpc packages that originate from Ubuntu and also works for our purpose.

---

btw the reason it uninstalled lazarus was probably that lazarus-project depends on fpc-src and fpc-src-3.0.4 depends on fpc-3.0.4 from upstream but the Ubuntu version of fpc did not satisfy these dependencies and now fpc-src and lazarus-project had to be uninstalled automatically. I have also tried to pin lazarus-project with 1001 to enforce this dependency chain from the other end but this did not work.
Title: Re: [SOLVED] Ubuntu: Lazarus-Installation lost by System-Update - how to prevent?
Post by: rjhover50 on September 28, 2018, 05:20:01 am
I was having the same problem after upgrading to Ubuntu 18.04 from 16.04.

I tried what JuhaManninen suggested and it worked!

Thanks!!!!!
Title: Re: [SOLVED] Ubuntu: Lazarus-Installation lost by System-Update - how to prevent?
Post by: JuhaManninen on September 28, 2018, 09:50:50 am
I was having the same problem after upgrading to Ubuntu 18.04 from 16.04.
I tried what JuhaManninen suggested and it worked!
Heh, at least somebody tries my instructions!
Most people seem to have an obsession for .deb packages regardless of how much you try to warn them.
I still think Handoko and others do a bad disservice when promoting the external .deb packages.

A related comment in this thread:
Maybe create a wiki page with explanation and possible solutions? Maybe a FAQ?
The wiki page would also soon promote using external .deb packages. It would also be a disservice.
Even if I create a page without that info, somebody would very likely add it.

P.S.
@rjhover50, as an extra bonus you get the latest bug fixes of the SVN branch by running "svn up" sometimes.
You could also start using the fixes 2.0 branch already which was forked recently. It will get bug fixes for many years to come. Recommended.
 https://svn.freepascal.org/svn/lazarus/branches/fixes_2_0/
TinyPortal © 2005-2018