On Fri, Aug 04, 2017 at 05:56:12PM +0200, chrysn wrote:
> In going through the code, I found several places where dpkg error codes
> were ignored (will send patch to this bug when I've worked out the last
> error code); [...]
I think that this patch would have made spotting the errors easier, and
On Fri, Aug 04, 2017 at 04:53:01PM +0200, Guillem Jover wrote:
> I've fixed this locally with an additional ":$inst->{Architecture}" to
> the dpkg -L call, but might switch back to using $pkgname as passed
> by the user for greated backwards compat with older dpkg versions.
In going through the
Control: found -1 1.42
Hi!
On Fri, 2017-08-04 at 16:29:35 +0200, chrysn wrote:
> Package: dpkg-repack
> Version: 1.43
> Severity: normal
[…examples…]
> The :amd64 ones actually produce empty (control file only) .deb files.
>
> For a quick fix, I needed to add some more :amd64 throughout
>
Processing control commands:
> found -1 1.42
Bug #870724 [dpkg-repack] can't repackage multiarch libraries
Marked as found in versions dpkg-repack/1.42.
--
870724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870724
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: dpkg-repack
Version: 1.43
Severity: normal
| dpkg-repack does not produce a proper .deb for packages that are
| multiply installed via multiarch, eg. libpng16-16:amd64. i tried various
| approaches:
|
| $ dpkg-repack libpng16-16
| dpkg-query: error: --status needs a valid package name
5 matches
Mail list logo
