Hello,
Any news about this?
By not allowing this package on some architectures, you are shifting the
complexity of adding architecture qualifier to other packages higher in
the dependency chain, so I'm also not sure this is a good thing either.
As said by other, disabling optional language b
On 6 Feb 2021, at 12:44, Santiago Vila wrote:
>
> On Sat, Feb 06, 2021 at 12:34:07PM +, Jessica Clarke wrote:
>> unless you want porters to have to
>> manually build gettext with the nojava profile every time a new version
>> is uploaded
>
> The reverse of that would be: "Unless you want eve
On Sat, Feb 06, 2021 at 12:34:07PM +, Jessica Clarke wrote:
> unless you want porters to have to
> manually build gettext with the nojava profile every time a new version
> is uploaded
The reverse of that would be: "Unless you want every package
maintainer to manually track the java stuff ever
On 6 Feb 2021, at 12:24, Santiago Vila wrote:
> On Sat, Feb 06, 2021 at 12:04:30PM +, Jessica Clarke wrote:
>> Source: gettext
>> Version: 0.21-4
>> Severity: important
>> Tags: patch
>>
>> Hi,
>> Currently gettext Build-Depends on dh-elpa (which Depends on emacs) and
>> default-jdk, so archi
On Sat, Feb 06, 2021 at 12:04:30PM +, Jessica Clarke wrote:
> Source: gettext
> Version: 0.21-4
> Severity: important
> Tags: patch
>
> Hi,
> Currently gettext Build-Depends on dh-elpa (which Depends on emacs) and
> default-jdk, so architectures that lack one or more of emacs and openjdk
> are
Source: gettext
Version: 0.21-4
Severity: important
Tags: patch
Hi,
Currently gettext Build-Depends on dh-elpa (which Depends on emacs) and
default-jdk, so architectures that lack one or more of emacs and openjdk
are unable to build gettext (whilst there is now a nojava build profile,
that does no
6 matches
Mail list logo
