[Fink-devel] checksum on libnet patch

2007-01-23 Thread Robert T Wyatt
fyi,

The new libnet1.0 patch's checksum needs updating:

Removing fink-buildlock-libnet1.0-1.0.2a-111 ...
Failed: PatchFile 
/sw/fink/dists/unstable/main/finkinfo/net/libnet1.0.patch checksum 
does not match!
Actual: 281fd76538e02537e3b2311c42ca50fd
Expected: ba84afda4ea0f24ca8f1e59fa6756f7b

... and thanks for fixing it so that I can build snort again


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel


Re: [Fink-devel] checksum on libnet patch

2007-01-23 Thread Daniel Macks
On Tue, Jan 23, 2007 at 11:40:33AM -0600, Robert T Wyatt wrote:
 fyi,
 
 The new libnet1.0 patch's checksum needs updating:
 
 Removing fink-buildlock-libnet1.0-1.0.2a-111 ...
 Failed: PatchFile 
 /sw/fink/dists/unstable/main/finkinfo/net/libnet1.0.patch checksum 
 does not match!
 Actual: 281fd76538e02537e3b2311c42ca50fd
 Expected: ba84afda4ea0f24ca8f1e59fa6756f7b

Actually I forgot to commit the updated .patch; cvs conflict, then I
got side-tracked:(

 ... and thanks for fixing it so that I can build snort again

You're welcome. Thanks especially too to the new maintainer.

dan

-- 
Daniel Macks
[EMAIL PROTECTED]
http://www.netspace.org/~dmacks


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel


Re: [Fink-devel] [cvs] fink ChangeLog, 1.453, 1.454 bootstrap, 1.9, 1.10

2007-01-23 Thread Martin Costabel
Benjamin Reed wrote:
 Update of /cvsroot/fink/fink
 In directory sc8-pr-cvs5.sourceforge.net:/tmp/cvs-serv15529
 
 Modified Files:
   ChangeLog bootstrap 
 Log Message:
 10.4.9 will mess things up for us... yay sudo  :P

Just a small memory update (I saw in IRC log that everybody seems to 
have forgotten): This was discussed already 6 months ago on fink-core, 
thread Will the next sudo break fink?
http://thread.gmane.org/gmane.os.apple.fink.core/1189
That's why it had already been fixed in Services::execute (see ChangeLog 
for 2006-07-26). Apparently that fix was not complete.

Now that fink is fixed, the Fink sudo package (maintainer dmalloc) could 
perhaps be uncrippled (or re-crippled), too.

-- 
Martin




-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel


[Fink-devel] Parens in *Script under explicit interpretter

2007-01-23 Thread Daniel Macks
Anyone wanna guess what happens in the following case if compiling of
the cool-thing executable failed in CompileScript?

  InstallScript: 
  #!/bin/sh -ev
mkdir -p %i/bin
(cd src; cp cool-thing %i/bin)
echo installed successfully
  

Right, it gets installed successfully and the user gets a deficient
.deb. The cmd in the paren'ed subshell fails, but that failure code
doesn't propagate as a failure of the whole subshell. The top-level
interpretter's -e abort mode isn't triggered. It's a feature of
using subshells in any Patch/Compile/InstallScript with an explicit #!
interpretter, or any Pre/PostInst/RmScript.

A quick solution is to check the return code of the subshell manually
and explicitly crash if necessary:

  InstallScript: 
  #!/bin/sh -ev
mkdir -p %i/bin
(cd src; cp cool-thing %i/bin) || exit 1
echo installed successfully
  

Would love to hear other solutions and/or relatively fool-proof ways
for validator to check for this maintainer goof.

Found this on 10.3/unstable netcdf and ptex, but a quick grep finds
other places as well.

dan

-- 
Daniel Macks
[EMAIL PROTECTED]
http://www.netspace.org/~dmacks


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel