Please transition gcr to multi-arch

Bug #998715 reported by Alexander Ponyatykh
82
This bug affects 16 people
Affects Status Importance Assigned to Milestone
gcr (Debian)
Fix Released
Unknown
gcr (Ubuntu)
Fix Released
High
Unassigned
Precise
Won't Fix
Undecided
Unassigned
Quantal
Won't Fix
Undecided
Unassigned
Raring
Won't Fix
Undecided
Unassigned
Saucy
Fix Released
High
Unassigned
gnome-keyring (Ubuntu)
Invalid
Undecided
Unassigned
Precise
Won't Fix
Undecided
Unassigned
Quantal
Invalid
Undecided
Unassigned
Raring
Invalid
Undecided
Unassigned
Saucy
Invalid
Undecided
Unassigned

Bug Description

[SRU] The debiffs attached to comments #4 and #5 backport the multi-arch changes from Saucy to Raring and Quantal respectively. See LP: #859600 for the Precise version.

[IMPACT]
libgcr-3-1:i386 and libgck-1-0:i386 are not installable on an x86_64 system.

[Test Case]
Run 'sudo apt-get install libgcr-3-1:i386' and verify that the files are installed in the correct location:
$ ls -l /usr/lib/i386-linux-gnu/libgcr*
$ ls -l /usr/lib/i386-linux-gnu/libgck*

[Regression Potential]
Low, changes only affect packaging.

libgcr-3-1:i386 depends on libgcr-3-common:i386, but this package doesn't exists, because libgcr-3-common is architecture independent.
===========================================================
$ LANG= sudo apt-get install libgcr-3-1:i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libgcr-3-1:i386 : Depends: libgcr-3-common:i386 but it is not installable
E: Unable to correct problems, you have held broken packages.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: libgcr-3-1:i386 (not installed)
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Sun May 13 14:05:01 2012
ProcEnviron:
 TERM=xterm
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=ru_RU.utf8
 LANGUAGE=ru_RU:ru:en_GB:en
SourcePackage: gnome-keyring
UpgradeStatus: Upgraded to precise on 2012-05-04 (9 days ago)

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

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-keyring (Ubuntu):
status: New → Confirmed
Graham Inggs (ginggs)
Changed in gcr (Ubuntu):
status: New → Confirmed
Graham Inggs (ginggs)
summary: - Unable to install libgck-1-0:i386 on amd64
+ Please transition gcr to multi-arch
Changed in gcr (Ubuntu):
importance: Undecided → High
Revision history for this message
Laurent Bigonville (bigon) wrote :

I've just uploaded gcr 3.8.2-3 in debian unstable which has been converted to multiarch

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

Fix released in Saucy (LP: #1191987).

Changed in gcr (Ubuntu):
status: Confirmed → Fix Released
Graham Inggs (ginggs)
Changed in gnome-keyring (Ubuntu Quantal):
status: New → Invalid
Changed in gnome-keyring (Ubuntu Raring):
status: New → Invalid
Changed in gnome-keyring (Ubuntu Saucy):
status: Confirmed → Invalid
Changed in gcr (Ubuntu Precise):
status: New → Invalid
Changed in gcr (Debian):
status: Unknown → Fix Released
Revision history for this message
Graham Inggs (ginggs) wrote :
Revision history for this message
Graham Inggs (ginggs) wrote :
Graham Inggs (ginggs)
description: updated
Revision history for this message
Martin Pitt (pitti) wrote :

At this point I'm inclined to say that backporting this to non-LTS releases isn't worth the effort of doing SRU exceptions.

Changed in gcr (Ubuntu Quantal):
status: New → Won't Fix
Changed in gcr (Ubuntu Raring):
status: New → Won't Fix
Revision history for this message
Martin Pitt (pitti) wrote :

Of course, this is by no means a final decision, please feel free to reopen and upload, especially if an SRU team member does it.

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

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-keyring (Ubuntu Precise):
status: New → Confirmed
Revision history for this message
Chucky (lechuck) wrote :

It is not yet solved for Precise 12.04.5 which has LTS.

Is it scheduled in any way for backporting to Precise ?

Revision history for this message
Chucky (lechuck) wrote :

Precise has LTS, and as told earlier in this bug discussion, the LTS should receive a fix.

Changed in gcr (Ubuntu Precise):
status: Invalid → Confirmed
Revision history for this message
Steve Langasek (vorlon) wrote :

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release

Changed in gcr (Ubuntu Precise):
status: Confirmed → Won't Fix
Changed in gnome-keyring (Ubuntu Precise):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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