Control: tags 1066850 -moreinfo +pending
Matthias Klose wrote...
> On 14.03.24 21:38, Christoph Biedl wrote:
> > Do you have an idea, an existing solution how to do that?
> dep := $(shell dpkg-query '-f${Depends}' -W libmagic-dev | sed
> 's/.*\(libmagic[a-z0-9]*\).*/\1/')
> echo
On 14.03.24 21:38, Christoph Biedl wrote:
After getting some help in IRC, I guess the problem boils down to:
1. All architectures provide the t64 variant (libmagic1t64).
2. Some architectures no longer provide the old variant (libmagic1), for
example armhf.
3. Therefore, the install
After getting some help in IRC, I guess the problem boils down to:
1. All architectures provide the t64 variant (libmagic1t64).
2. Some architectures no longer provide the old variant (libmagic1), for
example armhf.
3. Therefore, the install dependency of python3-magic must be the t64 variant.
On 14.03.24 18:52, Christoph Biedl wrote:
Control: tags 1066850 moreinfo
Matthias Klose wrote...
Package: src:python-magic
Version: 2:0.4.27-2
Severity: serious
Tags: sid trixie
the package build-depends on libmagic1, and depends on it. The name was
recently changed to libmagic1t64.
This
Control: tags 1066850 moreinfo
Matthias Klose wrote...
> Package: src:python-magic
> Version: 2:0.4.27-2
> Severity: serious
> Tags: sid trixie
>
> the package build-depends on libmagic1, and depends on it. The name was
> recently changed to libmagic1t64.
This is not a real problem as
Package: src:python-magic
Version: 2:0.4.27-2
Severity: serious
Tags: sid trixie
the package build-depends on libmagic1, and depends on it. The name was
recently changed to libmagic1t64. Please don't hard-code it, but try to
b-d on libmagic-dev, and derive the name of the shared library
6 matches
Mail list logo
