Bug#923310: ITS: ninja-build
Hi, On 2019-02-26 08:09, Mo Zhou wrote: Source: ninja-build X-Debbugs-CC: fge...@debian.org Hi Felix, The last upload for ninja-build dates back to more than 1 year ago. There are some changes lined up but nothing that warranted an upload: https://salsa.debian.org/debian/ninja-build/commits/master Just because a package hasn't been uploaded in a while doesn't mean it has been abandoned. It might just continue to work without problems. The package looks quite old since it has an ancient std-ver. I'm sorry but that's a really bad criteria. In the end it's just a number in a control field. Is there anything in the package that you think needs improving besides bumping a number? I intend to help update the package and import the latest upstream version 1.9.0 then upload it to unstable, does that sound good to you? This could be either an ITS or an NMU, at your preference. At this stage in the release I consider it a very bad idea since many packages use ninja to build. I don't want to potentially break those in the freeze by uploading a new major upstream release. I wanted to fix [1] but clearly we cannot do that at this stage. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849513 As mentioned in the bug report I don't see a reason to "fix" this. I should just close that bug. Felix
Bug#923310: ITS: ninja-build
control: close -1 I agree with you, and let's close this bug.. On Tue, Feb 26, 2019 at 09:15:16AM +0100, Felix Geyer wrote: > Hi, > > On 2019-02-26 08:09, Mo Zhou wrote: > > Source: ninja-build > > X-Debbugs-CC: fge...@debian.org > > > > Hi Felix, > > > > The last upload for ninja-build dates back to more than 1 year ago. > > There are some changes lined up but nothing that warranted an upload: > https://salsa.debian.org/debian/ninja-build/commits/master > > Just because a package hasn't been uploaded in a while doesn't mean it has > been abandoned. > It might just continue to work without problems. > > > The package looks quite old since it has an ancient std-ver. > > I'm sorry but that's a really bad criteria. In the end it's just a number in > a control field. > Is there anything in the package that you think needs improving besides > bumping a number? > > > I intend to help update the package and import the latest upstream > > version 1.9.0 then upload it to unstable, does that sound good to you? > > This could be either an ITS or an NMU, at your preference. > > At this stage in the release I consider it a very bad idea since many > packages use ninja to build. > I don't want to potentially break those in the freeze by uploading a new > major upstream release. > > > I wanted to fix [1] but clearly we cannot do that at this stage. > > > > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849513 > > As mentioned in the bug report I don't see a reason to "fix" this. > I should just close that bug. > > Felix
Bug#923310: ITS: ninja-build
Source: ninja-build X-Debbugs-CC: fge...@debian.org Hi Felix, The last upload for ninja-build dates back to more than 1 year ago. The package looks quite old since it has an ancient std-ver. I intend to help update the package and import the latest upstream version 1.9.0 then upload it to unstable, does that sound good to you? This could be either an ITS or an NMU, at your preference. I wanted to fix [1] but clearly we cannot do that at this stage. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849513
