Your message dated Sat, 28 Jul 2012 13:26:38 +0200 with message-id <20120728112638.gp10...@radis.cristau.org> and subject line Re: Bug#682268: unblock: foremost/1.5.7-4 has caused the Debian Bug report #682268, regarding unblock: foremost/1.5.7-4 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 682268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682268 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: release.debian.org User: release.debian....@packages.debian.org Usertags: unblock Severity: normal Please unblock the package foremost. The updated version fixed the build on kfreebsd-* (1.5.7-3) and hurd (1.5.7-4). It would be great to have one more software ported to those platform by making simple build system changes. -- Regards, Aron Xu
--- End Message ---
--- Begin Message ---On Sat, Jul 21, 2012 at 04:28:53 +0800, Aron Xu wrote: > Package: release.debian.org > User: release.debian....@packages.debian.org > Usertags: unblock > Severity: normal > > Please unblock the package foremost. > > The updated version fixed the build on kfreebsd-* (1.5.7-3) and hurd > (1.5.7-4). It would be great to have one more software ported to those > platform by making simple build system changes. > Unblocked. The dpkg-buildflags stuff shouldn't really be in a patch though, I'd just set the variables in debian/rules when calling make and remove the .c.o rule which overrides the builtin one. Cheers, Juliensignature.asc
Description: Digital signature
--- End Message ---