| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Mark Haney wrote: |
| 5 |
> |
| 6 |
> Since I'm not as up to speed as I really want to be on manipulating |
| 7 |
> ebuilds and portage, I simply deleted the ebuild and re-sync'd, this one |
| 8 |
> came down fine and is compiling now. I thought about a bug report, but |
| 9 |
> I felt that to be too extreme a measure if I was the only person seeing |
| 10 |
> the problem. |
| 11 |
|
| 12 |
If an emerge sync doesn't fix the problem filing a bug is a perfectly |
| 13 |
appropriate solution - any dev can fix this in 30 seconds (assuming it |
| 14 |
is obvious the ebuild wasn't tampered with). Most likely a dev forgot |
| 15 |
to run repoman when doing a commit - otherwise the digest error would |
| 16 |
have been caught (in theory they are supposed to do this all the time, |
| 17 |
but it can be slow). Ditto for problems when a package is marked stable |
| 18 |
and one of its dependencies is not. |
| 19 |
|
| 20 |
90% of the time it was noticed 5 minutes later and fixed, and you might |
| 21 |
have done your last emerge sync in the interim. As a result I usually |
| 22 |
resync before filing a bug. |
| 23 |
-----BEGIN PGP SIGNATURE----- |
| 24 |
Version: GnuPG v1.4.4 (GNU/Linux) |
| 25 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 26 |
|
| 27 |
iD8DBQFEz0X9G4/rWKZmVWkRAsTgAJ0UfDfcyiStNZDuhfV47x4zw29KAACcD3Ht |
| 28 |
Ilg3uGqR1lIeznRHBdyR+Dw= |
| 29 |
=anj+ |
| 30 |
-----END PGP SIGNATURE----- |
Archives