On Sep 10, 2015 2:04 PM, "Nikos Timiopulos" <ni...@timi.cz> wrote: > so I think I’ve applied that patch and it doesn’t fix the bug.
Most likely, patch wasn't applied. > Because I’m noob in the package modifications I’ve made these steps for > your review: > > $ apt-get source monit > $ cd monit-5.9 > I’ve put your patch file into the debian/patches folder > $ quilt new 13_umask_fix.patch > $ quilt push -a > File series fully applied, ends at patch 13_umask_fix.patch Try this: dget http://http.debian.net/debian/pool/main/m/monit/monit_5.9-1.dsc cd monit-5.9 wget 'https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=796989;msg=12;filename=13_umask_fix.patch' \ -O debian/patches/13_umask_fix.patch quilt push -a quilt new debian/patches/13_umask_fix.patch quilt push -a quilt pop -a Now check that patch is in place: quilt push -a ... Applying patch 13_umask_fix.patch patching file libmonit/src/system/Command.c patching file libmonit/src/system/Command.h patching file libmonit/src/system/Process.h patching file libmonit/test/CommandTest.c patching file src/control.c patching file src/p.y patching file src/tokens.h patching file src/y.tab.c Then build the package with debuild as usual.
