Bug#664257: multiarch tuples are not documented/defined
Ian Jackson <ijackson@chiark.greenend.org.uk> writes:
> Goswin von Brederlow writes ("Re: Bug#664257: multiarch tuples are not documented/defined"):
>> Ian Jackson <ijackson@chiark.greenend.org.uk> writes:
>> > What change to the Debian operating system, or to processes,
>> > documents, infrastructure or organisational arrangements, maintained
>> > by the Debian project, is this bug requesting ?
> ...
>> Aren't the Upstream and Forwarded tags exactly for this situation?
>
> No.
>
> Upstream means that we agree that the problem is a bug in Debian, but
> that the bug is also in the upstream code - ie, we have inherited it
> from upstream.
>
> Forwarded means that we agree that the problem is a bug in Debian; we
> think that the best way to fix it is to engage with upstream (and
> perhaps take their fix in due course, or perhaps cherry pick it); and
> we have therefore notified upstream via their bug tracker.
It is a bug in Debian: The multiarch tuples are not documented/defined
in Debian.
The bug is also in the upstream code since upstream does not document
the tuples and we inherited that from them.
So the bug should be reported in upstreams BTS and then tagged as
forwarded. Once they add the multiarch tuples we can cherry pick that or
wait for the next release. That all seems to fit perfectly with your
description.
Ok, we also created the problem by inventing the multiarch tuples. But
still, we want upstream to fix this and don't want to diverge from
them.
> These overlap. Normally Forwarded would imply Upstream although I
> guess there might be bizarre situations where we would (for example)
> ask for upstream help or advice with fixing a bug which manifests only
> in Debian.
>
> But neither of them is appropriate if the bug cannot be fixed by any
> change in Debian (a package, process, document, or whatever).
>
> Ian.
I don't agree with that. Where does it say that and how is that usefull?
For one thing a bug can always be fixed in Debian wth enough work if it
is fixable at all. It just might not be the right thing to do. For
example the multiarch tuples could be added to Debian policy with the
proper exceptions to the FHS and so on.
MfG
Goswin
Reply to: