On Thursday 06 January 2005 10:26 am, Jon Dowland wrote: > On Thu, Jan 06, 2005 at 09:32:35AM -0500, Aldebaran wrote: > > After thrashing back and forth in man pages and at.allow and at.deny I > > found that at has a bug. > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=115295 > > > > Now at that bug report there is a patch. I managed to apply the patch > > but one hunk got rejected but that was for the change log so I imagine > > thats not important? > > Generally the package build process would do the patching, and the > failure would stop the build. > > I'd recommend creating a patches directory inside the debian one, > dropping that patch in (with a .patch extension), > > Cut everything in the patch below and including this line > diff -ruN at-3.1.8/debian/changelog at-3.1.8.hs/debian/changelog > > execute dpkg-buildpackage -rfakeroot > > Note that this doesn't work for me but I think that is for a different > reason (some kind of environment problem that also stops me building > apache)
This didn't work. dpkg-buildpackage -r fakeroot did compile the package without errors, but I didn't see any mention of any patching going on. The patch was named ./at-3.1.8/debian/patches/atpatch.patch and then dpkg -i at_3.1.8-11_i386.deb installed the deb and stopped and restarted atd but nothing has changed, I wish I had cp the old atd somewhere so I could diff it to see if anything was changed, but I didn't going to try a variation of what you suggested. You indicated all I needed to do was put the patch in a patch dir in the debian director right? I'm going to apply the patch and see if dpkg-buildpackage will still "do it" ok it's installed and a job is queued up and .. atq reports that the job is gone, and /var/log/syslog isn't saying anything and I have mail!! It worked! Jon, you fixed my debian, thank you very much. Sam, I didn't try your suggestion I have used dpkg-buildpackage and fakeroot before so I tried them first. If what Jon suggested hadn't worked, I would have tried your idea next. Justin, I don't think apt-get -b would work here as the source that apt-get would not have the patch. Oh, I guess I could point apt-get at a file, but I've never done that. Roland, thank you for your comment. Thanks everyone, the very best and most important thing about debian is [email protected] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
