Ok Steve, it's done : https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/767634
Thanks for your help ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/756381
Title:
dpkg: confused about installatio
Damien,
Please file a new bug report against dpkg for the issue you're seeing.
There appears to be a regression in the handling of --force-depends,
making it impossible to force installation of a foreign-arch package
without satisfying the dependencies. That's certainly not the preferred
way to i
What surprises me is that I had not this problem on maverick_amd64
whereas I had the same installed packages...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/756381
Title:
dpkg: confused about insta
On Sat, Apr 16, 2011 at 08:46:56AM -, Damien Laporte wrote:
> I applied your method, but the dependency problem is the same:
> sudo dpkg -i rebuilt_common.deb
> (Lecture de la base de données... 94296 fichiers et répertoires déjà
> installés.)
> Préparation du remplacement de cnijfilter-comm
I applied your method, but the dependency problem is the same:
sudo dpkg -i rebuilt_common.deb
(Lecture de la base de données... 94296 fichiers et répertoires déjà installés.)
Préparation du remplacement de cnijfilter-common:i386 2.90-1 (en utilisant
rebuilt_common.deb) ...
Dépaquetage de la mis
On Fri, Apr 15, 2011 at 06:46:05PM -, Damien Laporte wrote:
> It doesn't work for me yet. With sudo dpkg -i --force-architecture
> rebuilt_common.deb
That's not correct usage. For multiarch, you should be setting
'foreign-architecture i386' in dpkg.cfg; no --force-architecture arguments
shoul
It doesn't work for me yet. With sudo dpkg -i --force-architecture
rebuilt_common.deb, I obtain the following result:
dpkg : avertissement : problème contourné par utilisation de --force :
l'architecture du paquet (i386) ne correspond pas à celle du système (amd64)
(Lecture de la base de données.
This bug was fixed in the package dpkg - 1.16.0~ubuntu7
---
dpkg (1.16.0~ubuntu7) natty; urgency=low
* src/packages.c: fix the check for whether our dependencies are
installed, so that it works correctly for multi-arch: foreign packages
configured during the current dpkg run
** Changed in: dpkg (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/756381
Title:
dpkg: confused about installation status of Multi-Arch: foreign
package
** Branch linked: lp:ubuntu/dpkg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/756381
Title:
dpkg: confused about installation status of Multi-Arch: foreign
packages configured in the current run?
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/756381
Title:
dpkg: confused about installation status of Multi-Arch: foreign
packages configured in the current run?
--
ubuntu
Thanks for the report. Indeed it was easy to reproduce, a bit less easy
to fix even though it's a one line patch.
The problem was that when the configuration is not immediately possible,
clientdata->istobe is reset to itb_installnew and in some places I use
that information to decide whether I wan
** Tags added: multiarch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/756381
Title:
dpkg: confused about installation status of Multi-Arch: foreign
packages configured in the current run?
--
ub
13 matches
Mail list logo
