Bug#924253: mat2: Please update backport provided via stretch-backports

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#924253: mat2: Please update backport provided via stretch-backports

Georg Faerber-2
Package: mat2
Version: 0.7.0-1~bpo9+1
Severity: wishlist
Control: block -1 with 924250

Version 0.8.0-3, which is to migrate to testing in two days, will ship
the Nautilus extension. However, it needs a never version of
nautilus-python than what is currently available in stretch.

Therefore, the current version of nautilus-python in testing, 1.2.2-2,
needs to be backported first. I've asked the maintainers to provide such
a backport, see #924250 for details.

Cheers,
Georg

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#924253: [Pkg-privacy-maintainers] Bug#924253: mat2: Please update backport provided via stretch-backports

Georg Faerber-2
Hi all,

On 19-03-10 15:43:46, Georg Faerber wrote:
> [...]
>
> Therefore, the current version of nautilus-python in testing, 1.2.2-2,
> needs to be backported first. I've asked the maintainers to provide
> such a backport, see #924250 for details.

It has been five weeks since my initial mail, and I've pinged the
nautilus-python maintainers two more times in the meantime: some days
ago via the BTS, and yesterday again via IRC -- no response, so far.

Any hints how to go forward with this? I don't want to step on anyone's
toes, on the other hand, I'm a bit tired to wait (up until forever?).

Thanks,
Georg

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#924253: [Pkg-privacy-maintainers] Bug#924253: Bug#924253: mat2: Please update backport provided via stretch-backports

Ulrike Uhlig
Hi Georg,

On 16.04.19 13:15, Georg Faerber wrote:

> On 19-03-10 15:43:46, Georg Faerber wrote:
>> [...]
>>
>> Therefore, the current version of nautilus-python in testing, 1.2.2-2,
>> needs to be backported first. I've asked the maintainers to provide
>> such a backport, see #924250 for details.
>
> It has been five weeks since my initial mail, and I've pinged the
> nautilus-python maintainers two more times in the meantime: some days
> ago via the BTS, and yesterday again via IRC -- no response, so far.
>
> Any hints how to go forward with this? I don't want to step on anyone's
> toes, on the other hand, I'm a bit tired to wait (up until forever?).

I don't think there is a policy issue with uploading this backport
yourself (so no toe-stepping involved), but by uploading that backport
you commit to keep it alive during the lifetime of stretch-backports.

The question would rather be if there might be technical issues
resulting from that upload for users of packages that use nautilus-python.

Cheers!
u.

Reply | Threaded
Open this post in threaded view
|

Bug#924253: [Pkg-privacy-maintainers] Bug#924253: mat2: Please update backport provided via stretch-backports

Georg Faerber-2
Hi u,

Thanks for your fast reply, and sorry for the delay on my side:

On 19-04-16 13:35:18, Ulrike Uhlig wrote:
> I don't think there is a policy issue with uploading this backport
> yourself (so no toe-stepping involved), but by uploading that backport
> you commit to keep it alive during the lifetime of stretch-backports.

Alright and sure (regarding the future maintenance).

> The question would rather be if there might be technical issues
> resulting from that upload for users of packages that use
> nautilus-python.

I've read the changelog between the version in stable and the one in
testing, and didn't spot any breaking changes, mostly bug fixes.

Still, proper testing before doing the actual upload would be in order,
I guess? For example, ensuring that other extensions still work with
this new version?

Thanks again,
cheers,
Georg

signature.asc (849 bytes) Download Attachment