On 17.02.2018 16:32, Sven Joachim wrote:
> On 2018-02-17 09:33 +0700, Matthias Klose wrote:
>
>> On 17.02.2018 03:06, Sven Joachim wrote:
>>> On 2016-12-15 21:28 +0100, Sven Joachim wrote:
>>>
Which use case of foreign architecture dependencies is handled by the
existing readline
On 2018-02-17 09:33 +0700, Matthias Klose wrote:
> On 17.02.2018 03:06, Sven Joachim wrote:
>> On 2016-12-15 21:28 +0100, Sven Joachim wrote:
>>
>>> Which use case of foreign architecture dependencies is handled by the
>>> existing readline multilib packages?
>>
>> I still have not received an
On 17.02.2018 03:06, Sven Joachim wrote:
> On 2016-12-15 21:28 +0100, Sven Joachim wrote:
>
>> Which use case of foreign architecture dependencies is handled by the
>> existing readline multilib packages?
>
> I still have not received an answer to this question, could you please
> elaborate?
On 2016-12-15 21:28 +0100, Sven Joachim wrote:
> Which use case of foreign architecture dependencies is handled by the
> existing readline multilib packages?
I still have not received an answer to this question, could you please
elaborate?
Cheers,
Sven
On 2018-02-10 18:44 +0100, Matthias Klose wrote:
> that's not how cross builds are supposed to work. build with dpkg-buildpackage
> -a . of course fixing / removing the libc6-i386 b-d. And no, you
> can't
> upload such a package to the archive. Everything with dependencies on foreign
> archs
On 10.02.2018 18:09, Sven Joachim wrote:
> On 2018-02-10 15:00 +0100, Matthias Klose wrote:
>
>> On 10.02.2018 13:41, Sven Joachim wrote:
>>>
>>> Also, while installing foreign architecture packages might sometimes be
>>> useful, linking a program in a newly built package against a shared
>>>
On 2018-02-10 15:00 +0100, Matthias Klose wrote:
> On 10.02.2018 13:41, Sven Joachim wrote:
>>
>> Also, while installing foreign architecture packages might sometimes be
>> useful, linking a program in a newly built package against a shared
>> foreign-arch library is not really possible, because
On 10.02.2018 13:41, Sven Joachim wrote:
> Control: tags -1 + patch
>
> On 2016-12-15 21:28 +0100, Sven Joachim wrote:
>
>> On 2016-12-15 08:38 +0100, Matthias Klose wrote:
>>
>>> On 14.12.2016 21:05, Sven Joachim wrote:
Source: readline
Version: 7.0-1
Tags: buster sid
Control: tags -1 + patch
On 2016-12-15 21:28 +0100, Sven Joachim wrote:
> On 2016-12-15 08:38 +0100, Matthias Klose wrote:
>
>> On 14.12.2016 21:05, Sven Joachim wrote:
>>> Source: readline
>>> Version: 7.0-1
>>> Tags: buster sid
>>> Control: block 848163 by -1
>>>
>>> I intend to remove the
On 2016-12-15 08:38 +0100, Matthias Klose wrote:
> On 14.12.2016 21:05, Sven Joachim wrote:
>> Source: readline
>> Version: 7.0-1
>> Tags: buster sid
>> Control: block 848163 by -1
>>
>> I intend to remove the ncurses multilib packages after the stretch
>> release, see #848163. Since ncurses is
On 14.12.2016 21:05, Sven Joachim wrote:
> Source: readline
> Version: 7.0-1
> Tags: buster sid
> Control: block 848163 by -1
>
> I intend to remove the ncurses multilib packages after the stretch
> release, see #848163. Since ncurses is required to build readline, this
> means that the readline
Control: clone -1 -2
Control: reassign -2 src:readline6
On 2016-12-14 21:05 +0100, Sven Joachim wrote:
> Source: readline
> Version: 7.0-1
> Tags: buster sid
> Control: block 848163 by -1
>
> I intend to remove the ncurses multilib packages after the stretch
> release, see #848163. Since
Source: readline
Version: 7.0-1
Tags: buster sid
Control: block 848163 by -1
I intend to remove the ncurses multilib packages after the stretch
release, see #848163. Since ncurses is required to build readline, this
means that the readline multilib packages can then no longer be built.
There
13 matches
Mail list logo
