On 4/23/24 14:05, Daniel Baumann wrote:
Hi,

On 4/23/24 13:58, Jakub Ružička wrote:
but we've agreed the time has come to get extra testing & feedback through Debian experimental.

yay, thanks!

[ we use knot-resolver at work for the central resolvers for the university, and we love it. kresd 6 offers some nice improvements for us, so looking forward testing it (via local bookworm-backports we maintain) ]
Awesome, I've forwarded your words of praise to the hard-working Knot Resolver team :)

The only blocker for that is missing python3-json-schema-for-humans needed for docs build which I intend to package later - for now I guess I'll just disable the docs build.

(just as an offer) I'll maintain a bunch of python modules already and don't mind another, so I can upload that later today if this is any help.

Thanks, but I'm part of PythonTeam so I can do that myself and I'm actually quite interested in (the nightmares of) python packaging in general so it's a welcome opportunity to have some real world experience plus I think it will be a trivial package.


I'm hitting boundaries of my Debian knowledge so it's slow.

I'm happy to help if you want.
Cool, I've already mental-marked you as a person I'm gonna bother with reviewing my v6 changes even before your willing reply :)


For example, upstream package uses meson directly and builds in meson_deb dir, but debian package uses debhelper with obj-x86_64-linux-gnu dir and I don't know howto properly reference it from d/rules without relying on shady strings.

I didn't find a branch on the salsa repo, where would I find the current 6.x state to send patches against?
I don't like pushing broken/incomplete branches but yeah this is gonna take a while so I pushed my Draft to debian/experimental salsa branch (also pristine-tar and new upstream-6).

The upstream package is well tested, but it diverged quite far from debian package and syncing them is non-trivial - my mission is to fix that.

git clone -b 6.0 https://gitlab.nic.cz/knot/knot-resolver
meld knot-resolver/distro/pkg/deb ~/debian/knot-resolver/debian

IOW ~/src/knot-resolver/distro/pkg/deb and ~/debian/knot-resolver/debian should be as close as possible.

Of course the changes can flow both ways - I'm happy to update the upstream packaging as well.

Feel free to push your changes (if any) to debian/experimental or use your branch as you prefer, I'm always eager to learn how other DDs do things.

I'd be especially interested about how you translate the distro/pkg/deb/rules to debian/rules without using the static build_deb dir 🤔 There might be variable already defined for this purpose, but I just don't know how to find it.


Regards,
Daniel


Cheers,
Jakub

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to