| 1 |
Patrick Lauer schrieb: |
| 2 |
> Bernd Steinhauser wrote: |
| 3 |
>> Luca Barbato schrieb: |
| 4 |
>>> Ciaran McCreesh wrote: |
| 5 |
>>>> The point is to make pkgcore a better package manager by getting the |
| 6 |
>>>> developers to do some basic testing. We're not talking some obscure, |
| 7 |
>>>> weird bug here. We're talking a really obvious, major screwup that a |
| 8 |
>>>> couple of quick unit tests would catch straight away. |
| 9 |
>>> |
| 10 |
>>> No, you aren't talking, you are babbling about undefined flaws that |
| 11 |
>>> nobody can evaluate, for which you aren't providing a way to |
| 12 |
>>> reproduce it and possibly doesn't exist. |
| 13 |
>>> |
| 14 |
>>> lu |
| 15 |
>>> |
| 16 |
>> So in your opinion, the pkgcore maintainers should just say "Screw it, |
| 17 |
>> it was just Ciaran who said that." and move on? |
| 18 |
> No, it's just unsubstantiated rumors. As such they are irrelevant until |
| 19 |
> some kind of proof is shown. |
| 20 |
It might be, but it might also be a bug. |
| 21 |
Of course the maintainers can choose if they go after it. |
| 22 |
|
| 23 |
BTW: The Paludis maintainers did have a look at the "security hole" you |
| 24 |
pointed out, even though everyone knows, that you spread lies about |
| 25 |
Paludis... |
| 26 |
|
| 27 |
>> Why is "Create tests for EAPI=1 stuff." not a way to describe how to |
| 28 |
>> reproduce a problem? |
| 29 |
> It is too generic and doesn't even describe the class of bug. By the |
| 30 |
> same rationale portage and paludis have multiple bugs ... |
| 31 |
It is indeed generic, but then you should test every part of EAPI. |
| 32 |
The main point was, that test are missing and the fact, that there is |
| 33 |
might be a bug, that they didn't catch yet is a follow up. |
| 34 |
|
| 35 |
Of course, filing a bug report for a single issue might get that issue |
| 36 |
fixed, but what caused this issue to be still there (missing tests) will |
| 37 |
still be there. |
| 38 |
|
| 39 |
>> Talking away problems, now that is a way to handle QA. |
| 40 |
> So, could anyone just actually mention what the problem is, or is the |
| 41 |
> hivemind not able to express such a simple thing? |
| 42 |
> |
| 43 |
> Just think of the thousands of emails, being read by hundreds of |
| 44 |
> readers, that have cost so much time ... in that time you could have |
| 45 |
> written a patch and a bugreport. |
| 46 |
Again, one patch and one bug report wouldn't wipe out the problem in the |
| 47 |
long term view. |
| 48 |
-- |
| 49 |
gentoo-dev@l.g.o mailing list |
Archives