Bug#1022721: New aptly upstream version 1.5.0

2023-01-31 Thread Sébastien Delafond
On Mon, Jan 30 2023, Roland Mas wrote:
> golang-github-cavaliergopher-grab has been accepted into
> unstable. Shall I proceed with the aptly upload or would one of you
> guys prefer doing it?

You can go ahead.

Cheers,

-- 
Seb



Bug#1022721: New aptly upstream version 1.5.0

2023-01-30 Thread Roland Mas

Hi there,

golang-github-cavaliergopher-grab has been accepted into unstable. Shall 
I proceed with the aptly upload or would one of you guys prefer doing it?


Roland.

Le 04/01/2023 à 14:49, Sébastien Delafond a écrit :

On 02/01 15:04, Roland Mas wrote:

I took the liberty of packaging the cavaliergopher/grab library

Thanks for uploading that to NEW and closing the associated RFP.


I also updated the packaging for aptly 1.5.0, which I committed and
pushed to salsa, but I'd rather you had a look before uploading, as
I'm not a Golang expert at all.

On a very general note I would have rather preferred a MR on a separate
branch, at least until cavaliergopher/grab gets accepted from NEW before
the freeze. This would have ketp the CI status green, and made for
easier fixes around freeze time if some problem arises in the current
version. But this is git anyway, so if it comes to that we'll have to
ignore debian/master and build something off of 4c7796ca instead.

I don't have much time right now, but after a cursory glance at the
current HEAD it looks fine to me. Thanks a lot for your work on aptly,
it's much appreciated and hopefully will allow us to get 1.5 into
bookworm.

Cheers,





Bug#1022721: New aptly upstream version 1.5.0

2023-01-04 Thread Sébastien Delafond
On 02/01 15:04, Roland Mas wrote:
> I took the liberty of packaging the cavaliergopher/grab library

Thanks for uploading that to NEW and closing the associated RFP.

> I also updated the packaging for aptly 1.5.0, which I committed and
> pushed to salsa, but I'd rather you had a look before uploading, as
> I'm not a Golang expert at all.

On a very general note I would have rather preferred a MR on a separate
branch, at least until cavaliergopher/grab gets accepted from NEW before
the freeze. This would have ketp the CI status green, and made for
easier fixes around freeze time if some problem arises in the current
version. But this is git anyway, so if it comes to that we'll have to
ignore debian/master and build something off of 4c7796ca instead.

I don't have much time right now, but after a cursory glance at the
current HEAD it looks fine to me. Thanks a lot for your work on aptly,
it's much appreciated and hopefully will allow us to get 1.5 into
bookworm.

Cheers,

-- 
Seb



Bug#1022721: New aptly upstream version 1.5.0

2023-01-02 Thread Roland Mas

Hi,

I took the liberty of packaging the cavaliergopher/grab library; I also 
updated the packaging for aptly 1.5.0, which I committed and pushed to 
salsa, but I'd rather you had a look before uploading, as I'm not a 
Golang expert at all.


Thanks for packaging aptly!

Roland.