| Summary: | guidedog ebuild (based on guarddog) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | al grabauskas <alleycat> |
| Component: | New packages | Assignee: | José Alberto Suárez López <bass> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
ebuild file
digest downloaded by emerge rsync digest created by ebuild ... digest |
||
|
Description
al grabauskas
2002-08-10 18:43:52 UTC
Created attachment 2980 [details]
ebuild file
ok, it is now in the cvs plese unmask test it (you & friends ;), and tell me Al, i'm waiting for you testing report, please... Created attachment 3312 [details]
digest downloaded by emerge rsync
Created attachment 3313 [details]
digest created by ebuild ... digest
my apologies for the delay. it's been a busy week. if i: delete it entirely from my portage tree # emerge rsync a new copy appears i unmask it in the package.mask then # emerge guidedog it fails, complaining that the digest appears to be corrupt if i then delete the digest, # emerge guidedog to download it, then ebuild the digest and emerge guidedog again to finish installing, it completes successfully. so it appears there's something wrong with the digest. comparing the two, i find the one i created is identical, except that mine starts with "MD5 " and ends with " 566451". see new attachments. or am i doing this wrong? once compiled and installed, it appears to work fine, at least superficially. a. ko valid for me :) thanks for all |