Update version in noble to 1707406511ubuntu3 (due to new LLVM version & updates blocked)

Bug #2056080 reported by bastif
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
google-android-installers (Ubuntu)
Fix Released
Undecided
Graham Inggs

Bug Description

Please update the version of the package to 1707406511ubuntu3 which fixes 2 issues:

- "Conflicts/Provides" were too strict so that the upgrades were blocked for google-android-build-tools-*-installer
- Fix Depends of google-android-extras-google-auto-installer where package was depending on libc++1-14 & libc++abi1-14 while the current llvm version in noble is now llvm18 and which would have required to depend on libc++1-18 & libc++abi1-18. However the binary also works with the versions provided in Debian stretch (which was v3.5), so the version constraint on these packages it not needed.

PPA: https://launchpad.net/~bastif/+archive/ubuntu/google-android-installers-merge/+packages

bastif (bastif)
description: updated
bastif (bastif)
description: updated
Revision history for this message
bastif (bastif) wrote : Re: Update version in noble to 1707406511ubuntu3

Graham Inggs (ginggs), could you have a look at his please? Like you did with https://bugs.launchpad.net/ubuntu/+source/google-android-installers/+bug/2055635

summary: - Update version in noble to 1707406511ubuntu2
+ Update version in noble to 1707406511ubuntu3
description: updated
Revision history for this message
bastif (bastif) wrote :
bastif (bastif)
description: updated
description: updated
bastif (bastif)
summary: - Update version in noble to 1707406511ubuntu3
+ Update version in noble to 1707406511ubuntu3 (due to new LLVM version &
+ updates blocked)
Revision history for this message
Dan Bungert (dbungert) wrote :

Hi Bastif, thanks for the proposal.

Reading this comment here:
> "Conflicts/Provides" were too strict so that the upgrades were blocked for google-android-build-tools-*-installer

I attempted to provoke this behavior by installing google-android-build-tools-34.0.0-installer_34.0.0+1686227321_amd64.deb and allowing it to upgrade, that seemed to work ok. Would you add more details about what's going on with upgrade failures?

Revision history for this message
bastif (bastif) wrote :

The issue is with 1707406511ubuntu1 and 1707406511ubuntu2

Revision history for this message
bastif (bastif) wrote :

BTW you may need to have 2 packages of build-tools installed like:
google-android-build-tools-34.0.0-installer and google-android-build-tools-33.0.0-installer
Then try to upgrade, without this change it should not be possible.

Revision history for this message
Dan Bungert (dbungert) wrote :

Thanks for clarifying - I can see the upgrade bug now.

However, building ubuntu3 with the supplied patch seems to not address the upgrade:

dpkg: regarding google-android-build-tools-33.0.0-installer_33.0.0+1707406511ubuntu3_amd64.deb containing google-android-build-tools-33.0.0-installer:
 google-android-build-tools-33.0.0-installer conflicts with aapt (>> 1)
  google-android-build-tools-34.0.0-installer provides aapt and is present and installed.

dpkg: error processing archive google-android-build-tools-33.0.0-installer_33.0.0+1707406511ubuntu3_amd64.deb (--install):
 conflicting packages - not installing google-android-build-tools-33.0.0-installer
dpkg: regarding google-android-build-tools-34.0.0-installer_34.0.0+1707406511ubuntu3_amd64.deb containing google-android-build-tools-34.0.0-installer:
 google-android-build-tools-34.0.0-installer conflicts with aapt (>> 1)
  google-android-build-tools-33.0.0-installer provides aapt and is present and installed.

dpkg: error processing archive google-android-build-tools-34.0.0-installer_34.0.0+1707406511ubuntu3_amd64.deb (--install):
 conflicting packages - not installing google-android-build-tools-34.0.0-installer
(Reading database ... 108377 files and directories currently installed.)
Preparing to unpack google-android-licenses_1707406511ubuntu3_all.deb ...
Unpacking google-android-licenses (1707406511ubuntu3) over (1707406511ubuntu1) ...
Setting up google-android-licenses (1707406511ubuntu3) ...
Errors were encountered while processing:
 google-android-build-tools-33.0.0-installer_33.0.0+1707406511ubuntu3_amd64.deb
 google-android-build-tools-34.0.0-installer_34.0.0+1707406511ubuntu3_amd64.deb

test scenario:
* install google-android-build-tools-3[34].0.0 ubuntu1
* build with the attached patch
* attempt upgrade to the ubuntu3 versions of google-android-build-tools-3[34].0.0 and google-android-licenses

Revision history for this message
bastif (bastif) wrote (last edit ):

Yes, unfortunately there is no easy way to upgrade between update1 & the fix. One has to purge the buggy package first :/

That's why the sooner this is uploaded the better, in the hope that as few people as possible have them installed.

You can also have a look at the conversation in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065668 which mentions the same problem & how to proceed (ie purge the old packages).

Revision history for this message
Graham Inggs (ginggs) wrote :

Agreed, let's get this fix in sooner rather than later, to avoid people being stuck with the ubuntu1 version.

Changed in google-android-installers (Ubuntu):
assignee: nobody → Graham Inggs (ginggs)
status: New → Fix Committed
Revision history for this message
bastif (bastif) wrote :

Thank you!

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

This bug was fixed in the package google-android-installers - 1707406511ubuntu3

---------------
google-android-installers (1707406511ubuntu3) noble; urgency=medium

  * d/scripts/run_after_dh_prep.sh: fix version constraint on
    Conflicts/Provides to not block upgrades (LP: #2056080)
  * google-android-extras-google-auto-installer: relax Depends (use libc++1 &
    libc++abi1 virtual packages instead of libc++1-14 & libc++abi1-14, don't
    set version constraint on libc6, add alternative dep libgcc1)

 -- Fab Stz <email address hidden> Sun, 17 Mar 2024 14:03:03 +0100

Changed in google-android-installers (Ubuntu):
status: Fix Committed → Fix Released
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.