On 2020-01-03 Paul Gevers wrote:
> On 31-12-2019 18:26, Andreas Metzler wrote:
[...]
> > Afaict the involved packages should propagate to testing in 3 days, when
> > enblend-enfuse is old enough. I have commited the fix. [1]
> Unfortunately libvigraimpex is (hopefully only temporarily) blocked
Hi Andreas,
On 31-12-2019 18:26, Andreas Metzler wrote:
> On 2019-12-31 Sebastiaan Couwenberg wrote:
>> I would commit the change now, and upload it after the testing migration
>> unless there are other blockers that hold up the migration for more than
>> 5 days, then I would upload it now.
>
>
On 2019-12-31 Sebastiaan Couwenberg wrote:
> On 12/31/19 4:20 PM, Andreas Metzler wrote:
>> as Bas correctly diagnoses I am not currently building for all supported
>> versions but only for the default one because it is not trivial but
>> requires some work. Looking at python policy I think that
On Tue, Dec 31, 2019 at 04:35:22PM +0100, Sebastiaan Couwenberg wrote:
> On 12/31/19 4:20 PM, Andreas Metzler wrote:
> > as Bas correctly diagnoses I am not currently building for all supported
> > versions but only for the default one because it is not trivial but
> > requires some work. Looking
On 12/31/19 4:20 PM, Andreas Metzler wrote:
> as Bas correctly diagnoses I am not currently building for all supported
> versions but only for the default one because it is not trivial but
> requires some work. Looking at python policy I think that is acceptable
> but not perfect.
>
> Is my
On 2019-12-31 Sebastiaan Couwenberg wrote:
> On 12/30/19 9:48 PM, Paul Gevers wrote:
[...]
>> libvigraimpex is also part of the pseudo python3.8 transition [1], but
>> it is still red. This probably means that you are not correctly building
>> Python3 modules for all supported Python3 versions.
On 12/30/19 9:48 PM, Paul Gevers wrote:
> On 27-12-2019 18:08, Andreas Metzler wrote:
>> On 2019-12-26 Paul Gevers wrote:
>>> On 25-12-2019 19:29, Andreas Metzler wrote:
libvigraimpex is marked for autoremoval because of the python2 removal.
This is fixed in experimental, the new
Hi Andreas,
On 27-12-2019 18:08, Andreas Metzler wrote:
> On 2019-12-26 Paul Gevers wrote:
>> On 25-12-2019 19:29, Andreas Metzler wrote:
>>> libvigraimpex is marked for autoremoval because of the python2 removal.
>>> This is fixed in experimental, the new version features a soname bump.
> [...]
On 2019-12-26 Paul Gevers wrote:
> On 25-12-2019 19:29, Andreas Metzler wrote:
>> libvigraimpex is marked for autoremoval because of the python2 removal.
>> This is fixed in experimental, the new version features a soname bump.
[...]
> Normally we don't want python 2 removal package uploads and
Control: tags -1 confirmed
Hi Andreas,
On 25-12-2019 19:29, Andreas Metzler wrote:
> libvigraimpex is marked for autoremoval because of the python2 removal.
> This is fixed in experimental, the new version features a soname bump.
> this should be a small scale transition. I have successfully [1]
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hello,
libvigraimpex is marked for autoremoval because of the python2 removal.
This is fixed in experimental, the new version features a soname bump.
this should be a small scale
11 matches
Mail list logo
