Unable to calculate the upgrade to 20.04 due to nodejs from nodesource

Bug #1889250 reported by Trevor White
720
This bug affects 98 people
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Error Upgrading 18.04 system which was previously running 16.04, logs should be uploaded.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.37
ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
Uname: Linux 4.15.0-112-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CrashDB: ubuntu
Date: Tue Jul 28 15:53:37 2020
InstallationDate: Installed on 2017-04-06 (1209 days ago)
InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2020-07-28 (0 days ago)

Revision history for this message
Trevor White (trevor-white) wrote :
Revision history for this message
Brian Murray (brian-murray) wrote :

The release upgrade failed to calculate because you have installed nodejs from a location other than the official Ubuntu archive. This version of nodejs is greater than the one in the archive and is keeping some python packages installed which then prevents the upgrade from being calculated. Please remove nodejs and then try the upgrade again.

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Incomplete
tags: added: nodesource-nodejs
summary: - Problems Upgrading to Ubuntu 20.04
+ Unable to calculate the upgrade to 20.04 due to nodejs from nodesource
Revision history for this message
GB (querty) wrote :

Hi Brian,

I did remove nodejs and related packages and I tried again.

The result is the same. I'll open a new bug report.

Where did you check to say nodejs was responsible?

Thanks.

Revision history for this message
Andreas Landhäußer (alandhae) wrote : Re: [Bug 1889250] Unable to calculate the upgrade to 20.04 due to nodejs from nodesource

I've removed nodejs,related packages and all source lists referring to
older ubuntu versions, after this, the upgrade succeeded .

Ciao

Andreas

On 13.10.20 12:36, GB wrote:
> Hi Brian,
>
> I did remove nodejs and related packages and I tried again.
>
> The result is the same. I'll open a new bug report.
>
> Where did you check to say nodejs was responsible?
>
> Thanks.
>
--
Andreas Landhäußer +49 151 12133027 (mobile)
<email address hidden>

Revision history for this message
Brian Murray (brian-murray) wrote : Re: [Bug 1889250] Re: Unable to calculate the upgrade to 20.04 due to nodejs from nodesource

On Tue, Oct 13, 2020 at 10:36:19AM -0000, GB wrote:
> Hi Brian,
>
> I did remove nodejs and related packages and I tried again.
>
> The result is the same. I'll open a new bug report.
>
> Where did you check to say nodejs was responsible?

It was in /var/log/dist-upgrade/apt.log. You'll notice that nodejs
appears in the log early and there are more messages about holding back
python because of nodejs.

--
Brian Murray

Revision history for this message
Andrew (meatnordrink) wrote :

Ditto the above; worked for me as well once I deleted Node (which I had upgraded to a newer version).

I'll note that I also disabled all my PPA's, if you haven't done that yet.

Revision history for this message
GB (querty) wrote :

I disabled all my PPA's...
I still cannot do-release-upgrade

grep Broken /var/log/dist-upgrade/apt.log |wc
   1405 17699 153251

Does it mean i have to remove all "Broken" 1405 packages ?!

Thank you for your help!

Revision history for this message
Daniel Letzeisen (dtl131) wrote :

@GB(querty): When you say you disabled the PPA's, did you just remove them from the source list or did you actually run ppa-purge on them? And counting "Broken" packages is not really useful, as just a small number of broken packages can cause a chain reaction.

Revision history for this message
GB (querty) wrote :

Hello Daniel,

I ran ppa-purge on them.

Do you have an idea how to detect the packages causing the trouble?

Thank you!

Guillaume

Revision history for this message
Daniel Letzeisen (dtl131) wrote :

@GB: If you attach the relevant /var/log/dist-upgrade/apt.log, I will take a look at it. Unfortunately, the log still leaves some guesswork. It's not an exact science.

Revision history for this message
GB (querty) wrote :

@Daniel, Here it is. Thank you!

Revision history for this message
Daniel Letzeisen (dtl131) wrote :

Oh, I admit I'm in over my head when looking at these things, but I'd start with the Investigating (0) stuff.

Investigating (0) libjack-jackd2-0:amd64 < 1.9.12~dfsg-2 -> 1.9.12~dfsg-2ubuntu2 @ii umU Ib >
Investigating (0) mate-menus:amd64 < 1.20.0-2 -> 1.24.0-1 @ii umU Ib >

Revision history for this message
GB (querty) wrote :

@Daniel, after cleanning a LOT (removing everything from /etc/apt/source.list.d/ and expurging /etc/apt/source.list this is what i get...
Any idea? (I'm afraid I must remove python-minimal... and so remove mate*!)

Revision history for this message
Eyal Lior (eyallior) wrote :

Attaching my apt and main log files.
I have similar problem.
purging nodejs didn't help.

Revision history for this message
GB (querty) wrote :

@eyallior not exactly the same, I don't get;
...
INFO failed to remove python-minimal
...
INFO failed to remove libpython-stdlib

my case seems worst that your!

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]

Changed in ubuntu-release-upgrader (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.