On Mon, Jun 17, 2013 at 11:01 AM, Geoffrey Thomas geo...@mit.edu wrote:
On Thu, 13 Jun 2013, Anders Kaseorg wrote:
The current input format for DPkg::Pre-Install-Pkgs hooks makes it
impossible to tell which architecture of a multiarch package is being
removed. For example, removing
On Wed, 26 Jun 2013 18:06:53 +0200 David Kalnischkies wrote:
[...]
So the attached patch adds the architecture behind every version number it
prints (and while at it, it also adds the MultiArch flag), doesn't break
the ABI (the method is protected, so in theory someone could use it) and
adds
On Wed, Jun 26, 2013 at 6:47 PM, Francesco Poli
invernom...@paranoici.org wrote:
On Wed, 26 Jun 2013 18:06:53 +0200 David Kalnischkies wrote:
as it
looks like it pins the wrong package if its using v2 currently and I am also
not really sure if the pin-logic shouldn't be changed drastically as
On Wed, 26 Jun 2013 19:45:52 +0200 David Kalnischkies wrote:
On Wed, Jun 26, 2013 at 6:47 PM, Francesco Poli
invernom...@paranoici.org wrote:
On Wed, 26 Jun 2013 18:06:53 +0200 David Kalnischkies wrote:
as it
looks like it pins the wrong package if its using v2 currently and I am
also
tags 712116 + patch
thanks
Dear maintainers,
On Thu, 13 Jun 2013, Anders Kaseorg wrote:
The current input format for DPkg::Pre-Install-Pkgs hooks makes it
impossible to tell which architecture of a multiarch package is being
removed. For example, removing libbz2-1.0:amd64 and libbz2-1.0:i386
Package: apt
Version: 0.9.7.7
The current input format for DPkg::Pre-Install-Pkgs hooks makes it
impossible to tell which architecture of a multiarch package is being
removed. For example, removing libbz2-1.0:amd64 and libbz2-1.0:i386
results in this input:
libbz2-1.0 1.0.6-4 - **REMOVE**
6 matches
Mail list logo
