Re: [Pkg-octave-devel] Processed: Re: FTBFS: fatal error: curl/types.h: No such file or directory

[Jonathan Nieder <jrnieder@gmail.com>]

Hi Rafael,

Rafael Laboissiere wrote:
> * Debian Bug Tracking System <owner@bugs.debian.org> [2012-07-14 14:42]:
>> Processing commands for control@bugs.debian.org:

>>> # > octave3.2 currently FTBFS on sid, as it tries to include curl/types.h
>>> # > which has been removed (see bug#636457):
>>> #
>>> # ... but not in squeeze, luckily.
>>> #tags 637787 +notsqueeze
>>> tags 637787 + wheezy sid experimental
>> Bug #637787 {Done: Thomas Weber <tweber@debian.org>} [octave3.2] FTBFS: fatal error: curl/types.h: No such file or directory
>> Added tag(s) sid, wheezy, and experimental.
>
> Bug#637787 is already closed and the octave3.2 has been removed from both
> wheezy and sid.  Is there any special reason for adding those tags to the
> bug report?

Yes.

Short explanation: it removes a bug that does not affect squeeze from
the list at http://bugs.debian.org/release-critical/other/stable.html
so only bugs in need of fixes that actually affect stable are left.

Longer explanation: the release tags have two purposes:

 * On one hand, for bugs with no found/fixed information, they can act
   as a stand-in.

 * On the other hand, for bugs with found/fixed information, they
   indicate which suites other packages must come from for the bug to
   matter.

For example a file conflict with a package that is only in
experimental would be tagged experimental, and a build failure that is
due to an API break that happened in sid or wheezy would be tagged
wheezy, sid, and experimental.

Hope that helps,
Jonathan