Re: unbound 1.17.1 for bullseye-backports

[chriss <chriss-lists@posteo.mx>]

Hi

If you can provide a backport for unbound it would save me some time. I 
would eventually get the backport build with sbuild (or as mentioned 
with a simple chroot). As I wrote - I got it build just not in the 
official way. I thought backports would only be accepted if build in a 
official way with sbuild.

Keep me posted on how you could provide a unbound backport or not. In 
case of not I would take the steps necessary to upload my package to the 
repo.

//chriss

On 09.04.23 15:05, Michael Tokarev wrote:
> 06.04.2023 10:34, chriss wrote:
> > Hi
> >
> > I'd like to submit unbound 1.17.1 (from bookworm) to bullseye-backports.
> >
> >
> > Currently I build it locally within a docker container and have it 
> > running on 2 different systems.
> >
> >
> > I have a set up an environment with sbuild (as mentioned @ 
> > https://wiki.debian.org/BuildingFormalBackports) but right now I 
> > cannot get it build with the instructions linked. Isn't there any 
> > simple step-by-step guide for an example dummy package?
>
> sbuild just works to build backports packages. So the failure you see
> is specific to your setup. Some packages needs more recent dependencies
> than the ones available in bullseye, but not unbound, it is 
> stright-forward
> to backport it.
>
> I always built unbound for bullseye the same way I upload it to 
> unstable, -
> to be used on our systems.  But I never thought it might be useful in
> bullseye-backports.  Guess I can provide a backport just fine.
>
> /mjt