[11:29] <mitya57> Unit193, there are new KDE applications 17.04.3, and some Qt modules could have been autosynced from Debian.
[11:34] <juliank> grr, apt autopkgtests are horribly broken on non-amd64
[11:34] <juliank> on ppc64el there is still the regression from the gcc 7 upgrade
[11:36] <juliank> probably because that compiles with -O3 (IIRC)
[19:29] <ktosiek[m]> Hi! What are the tools for working on a debian package? I've had to mock a bit with network-manager today (basically backport a patch to a backported patch :-)), and neither doing a full rebuild with dpkg-buildpackage nor generating patches for said tool to apply was nice
[19:32] <ktosiek[m]> I've started with `apt-get source`, copied the source dir, edited one of them, did a diff, added patch to series, and waited for full dpkg-buildpackage
[23:24] <JanC> ktosiek[m]: did you see http://packaging.ubuntu.com/html/ ?
[23:25] <ktosiek[m]> JanC: not yet, thank you!
[23:25] <JanC> and maybe also https://www.debian.org/doc/manuals/maint-guide/ if it's not in there
[23:26] <ktosiek[m]> I was just doing the things the way I've remembered, it was probably never a good one :-)
[23:26] <JanC> there is Debian-specific stuff in the latter that might not apply to Ubuntu, but OTOH it might have details that the Ubuntu one doesn't have
[23:32] <JanC> it's probably best to use a "clean" build environment like pbuilder (which uses a chroot) or similar