On Mon, 22 Mar 2021 10:16:20 +0100 n...@debian.org wrote:
Yes you are right. After your email I worked on the package but the
bullseye freeze policy doesn't allow new package versions anymore.:(
Hi Noël,
I have filed a request for a new lftp release at #995920.
It is now long after the bullsey
Hello Noel
Do I understand this correctly, the freeze does not allow a new version
even if there are no dependencies on the package?
In any case, if the package gets updated in unstable now one could then
propagate it later with the bullseye-backports repo, yes?
Regards
Stefan
Hello Stefan
Am Sonntag, dem 21.03.2021 um 00:16 +0100 schrieb Stefan Schindler:
> I am sorry for appearing hostile, I tried to contact you via email
No problem.
> back in 2020-10-16, but it appears that this email never found you.
Uh, sorry.
> Regarding the "new upstream package", I was not
Good evening Noel
I am sorry for appearing hostile, I tried to contact you via email back in
2020-10-16, but it appears that this email never found you.
Regarding the "new upstream package", I was not sure that I needed to
create a special ticket because the tracker had the new version already
lis
Good morning Stefan,
Am Donnerstag, dem 25.02.2021 um 01:14 +0100 schrieb Stefan Schindler:
> Package: lftp
> Version: 4.9.2; reported 2020-02-25
> Severity: important
>
> The upstream has released multiple packages since 2018 when the last
> debian package was fetched.
> * https://github.com/lav
Package: lftp
Version: 4.9.2; reported 2020-02-25
Severity: important
The upstream has released multiple packages since 2018 when the last debian
package was fetched.
* https://github.com/lavv17/lftp/blob/master/NEWS
* https://packages.debian.org/source/sid/lftp
I would like to maintain this pack
6 matches
Mail list logo
