On Sat, Dec 03, 2022 at 09:11:57AM +0100, Niels Thykier wrote:
> Jelmer Vernooij:
> > On Thu, Aug 26, 2021 at 11:39:06AM +0200, Lucas Nussbaum wrote:
> > > [...]
> > > Jelmer, did you already think about that? Is there a way one could help
> > > you?
> >
> > Reviving this thread that's more than
Jelmer Vernooij:
Hi Lucas,
On Thu, Aug 26, 2021 at 11:39:06AM +0200, Lucas Nussbaum wrote:
[...]
Jelmer, did you already think about that? Is there a way one could help
you?
Reviving this thread that's more than a year old...
[...]
Known issues that still need to be addressed:
*
Hi Lucas,
On Thu, Aug 26, 2021 at 11:39:06AM +0200, Lucas Nussbaum wrote:
> I'm really amazed by all the great work done around the Debian Janitor
> project. It's great to see how it focuses the maintainer's work on where
> there's some actual value with having humans in the loop.
>
> Watching
On 30 August 2021 19:17:54 CEST, Christian Kastner wrote:
>On 30.08.21 15:49, Jelmer Vernooij wrote:
>> I think one of the main challenges here is to make sure that the
>> dependencies for packages in unstable/testing are correct.
>
>Why wouldn't they be correct, though? If it's less strict than
On 30.08.21 15:49, Jelmer Vernooij wrote:
> I think one of the main challenges here is to make sure that the
> dependencies for packages in unstable/testing are correct.
Why wouldn't they be correct, though? If it's less strict than it should
be, then that is a bug. And if it's too strict,
Hi Lucas,
On Thu, Aug 26, 2021 at 11:39:06AM +0200, Lucas Nussbaum wrote:
> Watching the talk[0] on automatically providing packages for new
> upstream releases and new upstream git snapshots, I wondered if the same
> tooling could be used to automatically provide stable backports
> for packages
Hey Lucas
On 2021/08/27 15:04, Lucas Nussbaum wrote:
Oh I wasn't thinking about uploading to the official backports suite.
In the same spirit as the fresh-{releases,snapshots} suites provided by
janitor, I was thinking about an automatically-generated backports
suite.
That sounds great.
On Fri, Aug 27, 2021 at 03:04:34PM +0200, Lucas Nussbaum wrote:
> > uploading to -backports also implies the promise to keep maintaining that
> > backport until the next release is out... I'm not sure that part of the
> > upload should be automated nor forgotten ;)
> Oh I wasn't thinking about
On 27/08/21 at 12:54 +, Holger Levsen wrote:
> On Thu, Aug 26, 2021 at 11:39:06AM +0200, Lucas Nussbaum wrote:
> > There's probably a large number of packages that just require a
> > rebuild (+ test with autopkgtest) to be backported.
>
> uploading to -backports also implies the promise to
On Thu, Aug 26, 2021 at 11:39:06AM +0200, Lucas Nussbaum wrote:
> There's probably a large number of packages that just require a
> rebuild (+ test with autopkgtest) to be backported.
uploading to -backports also implies the promise to keep maintaining that
backport until the next release is
On 26.08.21 11:39, Lucas Nussbaum wrote:
> Additionally, one could imagine a DSL to:
> - make minor changes to the source package before building (adjust
> dependencies, apply an additional patch, etc.)
> - tell sbuild that some build-dependencies must be pulled from backported
> packages
>
>
Hi,
I'm really amazed by all the great work done around the Debian Janitor
project. It's great to see how it focuses the maintainer's work on where
there's some actual value with having humans in the loop.
Watching the talk[0] on automatically providing packages for new
upstream releases and new
12 matches
Mail list logo
