Gentoo Archives: gentoo-dev

From: Ciaran McCreesh <ciaranm@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] SRC_URI component naming collision
Date: Sun, 26 Feb 2006 21:42:55
Message-Id: 20060226214011.13636962@snowdrop.home
In Reply to: Re: [gentoo-dev] SRC_URI component naming collision by Stuart Herbert
1 On Sun, 26 Feb 2006 21:30:22 +0000 Stuart Herbert <stuart@g.o>
2 wrote:
3 | On Sun, 2006-02-26 at 21:04 +0000, Ciaran McCreesh wrote:
4 | > Ok, so given that this is a closed source application, if upstream
5 | > won't cooperate on something as simple as this, why do you expect
6 | > them to cooperate with you on bugs or security issues?
7 |
8 | That's not the issue here. The issue here is whether the QA team is
9 | entitled to be requesting the removal of packages in this specific
10 | instance.
11
12 The issue is whether you have the right to leave broken packages in the
13 tree. I don't see any policy document granting you that right.
14
15 | There are never any guarantees that any UPSTREAM will co-operate with
16 | us on bugs or security issues. If we can't live with the issues, and
17 | we can't fix them, the packages get dropped. I've no problem with
18 | that.
19
20 Sure. And if upstream won't even cooperate to the extent of renaming a
21 file, how do you expect them to react when we require something less
22 trvial?
23
24 | > | Everything else is up for discussion. I think it's unreasonable
25 | > | to say that I'm refusing to work with you.
26 | >
27 | > You're repeatedly closing off the bug rather than suggesting
28 | > alternative ways of fixing the issue.
29 |
30 | I think, in this specific case, there are better things to spend the
31 | time on. I don't have a queue of users telling me that the way we
32 | handle this today is a problem. There's no evidence that, in this
33 | specific case, there is a problem out in the real world.
34
35 It's so bad a problem that you even had to document it in the user
36 guide and tell people to use some nasty hacked workaround.
37
38 | Hang on a moment. It's not clear to me why I must go to the Portage
39 | team for a change, when it's the QA team demanding change? As the QA
40 | team wants the change, why don't you go to the Portage team and ask
41 | them to implement DEST_PREFIX?
42
43 We don't have a legitimate demonstration package, and we're not going
44 to go and ask the Portage team to make code changes to support
45 hypothetical speculation. You're the only one with a test case here.
46
47 | > | The issue at hand is that the QA team is, in this case, repeatedly
48 | > | asking for something it doesn't have the authority to insist on.
49 | > | I also think you're being unreasonable in this specific case.
50 | >
51 | > We're asking you to work with us in fixing a tree breakage. That's
52 | > our goal here. We can't do this if you just go around closing off
53 | > bugs and refusing to cooperate.
54 |
55 | Please stop spreading FUD, and libelling my name here.
56
57 You've closed that bug five times now without fixing it.
58
59 --
60 Ciaran McCreesh : Gentoo Developer (Wearer of the shiny hat)
61 Mail : ciaranm at gentoo.org
62 Web : http://dev.gentoo.org/~ciaranm

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
Re: [gentoo-dev] SRC_URI component naming collision Stuart Herbert <stuart@g.o>
Re: [gentoo-dev] SRC_URI component naming collision Paul de Vrieze <pauldv@g.o>