Re: Non-normalised field Provides in UDD table
Hi Andreas,
Andreas Tille <andreas@an3as.eu> writes:
> On Wed, Apr 11, 2018 at 10:02:39PM +0200, Ole Streicher wrote:
>> We had a short discussion in
>>
>> https://lists.debian.org/debian-blends/2018/03/msg00059.html
>>
>> and your answer. Do you mean something more?
>
> I mean we need different metapackages for say amd64, arm64, i386, etc.
> I agree that this is no solution for MultiArch but from my point of
> view that's rather a corner case. However, our metapackages are
> currently simply broken for all architectures except amd64 and I'd
> love to get this fixed in Buster.
>
> As I said blends-gsoc had some solution for this: [...]
>
> -Architecture: all
> +Architecture: any
> Recommends: abacas,
> - abyss
> + abyss [!s390 !hurd-i386 !kfreebsd-amd64 !powerpc !sparc !ia64 !kfreebsd-i386],
That was what I meant: This problem is in no way specific for blends
tasks, but is general for "Architecture: all" packages: You always may
run into the problem that such a package has a recommendation (or even
dependency) that is not fullfillable on one or the other architecture.
Imagine f.e. when R would stop the support for 32-bit architectures.
That would mean that all R packages (which are "Arch: all") cannot be
installed on those architectures anymore, since the dependency cannot be
resolved there. Would you then consider to rewrite all R packages to be
"Arch: !i386 !powerpc ..."? And to maintain all of these dependencies in
all R packages just to be in sync with the platforms supported by R? IMO
that is out of question.
What is the difference to a blends task med-bio with Arch: all and
recommending a package that does not exist on s390x? What do we gain
except getting MultiArch problems?
> It has another really great feature. It has the following warning
> output:
>
> WARNING:__main__:"filo" has been replaced with "bedtools"
Where does it get this from? Is this issued when "filo" is a "Provides"?
> WARNING:__main__: **Missing package python3-bd2k has the following existing versions:
> WARNING:__main__:python-bd2k
Similarly here: in which cases you issue this?
Best regards
Ole
Reply to: