1 |
Frank Peters <frank.peters@×××××××.net> posted |
2 |
20090425222359.6e3c49ca.frank.peters@×××××××.net, excerpted below, on |
3 |
Sat, 25 Apr 2009 22:23:59 -0400: |
4 |
|
5 |
> Hello, |
6 |
> |
7 |
> I am not sure if this list is the appropriate place to file a bug |
8 |
> report, but the problem does need confirmation before I go through |
9 |
> bugzilla. |
10 |
> |
11 |
> After building a working amd64 system using the latest portage tree, I |
12 |
> emerged my favorite text editor, cooledit, version 3.17.17 To my |
13 |
> surprise, any cut/copy/paste operation immediately caused a crash. |
14 |
> Fortunately, the error messages were quite informative and allowed me to |
15 |
> quickly find the cause. A call to "open" in the file widget/editcmd.c |
16 |
> of the cooledit source does not include the mode parameter. Somehow, |
17 |
> with the latest libraries, this missing parameter causes the crash. The |
18 |
> attached patch file, missing_mode.patch, will fix the problem. |
19 |
> |
20 |
> Apply with: patch -p1 < missing_mode.patch. The gentoo sources include |
21 |
> a few other patches as well that are also necessary, especially the gcc4 |
22 |
> patch. |
23 |
> |
24 |
> But, as I mentioned, it would be beneficial if this problem could be |
25 |
> confirmed. Cooledit is not the most popular text editor but maybe |
26 |
> someone also uses it or is willing to test it. |
27 |
> |
28 |
> If someone can confirmn this, then I can file a bugreport with gentoo |
29 |
> bugzilla. |
30 |
|
31 |
Hi. I don't use cooledit, but I use mc, the internal editor of which is |
32 |
a text console editor said to work very much like cooledit. In fact, I |
33 |
believe it uses some of the same format config files, for syntax |
34 |
hilighting and the like (or so various mc comments and documentation |
35 |
leads one to believe). So I feel a bit of kinship. =:^) |
36 |
|
37 |
I'd suggest going ahead and filing that bug and patch with Gentoo's |
38 |
bugzilla, particularly since you have a patch ready. Well, first do a |
39 |
search and see if there's already a bug filed on it that you can add the |
40 |
patch to. |
41 |
|
42 |
Gentoo's bugzilla works a bit different than some (in more than one way, |
43 |
as you'll soon discover if this is your first bug filed there, they've |
44 |
customized their version a LOT and it can be difficult getting used to). |
45 |
For users that don't hang out on the Gentoo developer list or IRC |
46 |
channels, bugs.gentoo is the main way developers and users interact, as |
47 |
well as the main tracking mechanism for everything from new and retired |
48 |
developers to organizational metabugs to feature requests (for Gentoo |
49 |
ebuilds or where Gentoo is the upstream) to the ordinary "bugs" such |
50 |
trackers are normally used for. |
51 |
|
52 |
If you have the skills to come up with a patch, you're already way ahead |
53 |
of most users and the bugs they file, and in the process of coming up |
54 |
with that patch will have already done way more verification than most |
55 |
users and their bugs do, so really, don't hesitate to file one. The only |
56 |
time the Gentoo package maintainers tend to get a bit irritated is when |
57 |
people don't look for previous bugs and therefore create dups. Sometimes |
58 |
that's unavoidable due to obscure bug names or something, but make a |
59 |
reasonable effort at searching for the bug before filing your own, and |
60 |
just file it if you don't find one. As either a new bug or attached to |
61 |
an old one, however, they'll definitely appreciate the patch. =:^) |
62 |
|
63 |
As I mentioned above, if you've not filed a bug on the Gentoo bugzilla |
64 |
before, it can be a bit confusing due to the way Gentoo uses bugzilla, |
65 |
especially if you're used to filing them elsewhere. I know it certainly |
66 |
was for me, and I still consider the Gentoo setup one of the more obtuse |
67 |
unintuitive setups out there, even if I'm used to it by now and even with |
68 |
the wizard. Thus, I'll quickly step thru the process below. Maybe it'll |
69 |
help you avoid shouting at the web page about how dumb it is like I did |
70 |
the first couple times thru! =:^) |
71 |
|
72 |
Short version: Product: Gentoo Linux, Component: Apps, include |
73 |
CATEGORY/package-ver (app-editors/cooledit-3.17.17) "copy/cut/paste |
74 |
crash" and "[patch]" on the summary/subject line, describe, submit, |
75 |
attach your emerge --info if it wasn't in your description, attach the |
76 |
patch. |
77 |
|
78 |
Long version: |
79 |
|
80 |
For "product", choose Gentoo Linux. That's the first page of the new bug |
81 |
wizard. |
82 |
|
83 |
If you use the normal wizard (not expert, which skips this as experts |
84 |
will know to do it before they ever start with actually filing one), the |
85 |
next step is to search for a dup. |
86 |
|
87 |
Then you fill out the rest of the bug information. Component in this |
88 |
case will be Application. Hardware platform, OS, etc... |
89 |
|
90 |
For the summary, start with the category and package name and version, |
91 |
app-editors/cooledit-3.17.17 , then describe the problem ("crash on cut/ |
92 |
copy/paste" , for instance). As you have a patch, add "[patch]" as |
93 |
well. Including the category is very important as some of the initial |
94 |
bug wrangling is automated and without that, you force a human to look it |
95 |
up, which of course delays the final bug assignment, getting it to |
96 |
someone that actually cares about that specific package. |
97 |
|
98 |
The normal wizard gets rather irritatingly "hand-holdy" at this point. |
99 |
There are a number of separate fields (description, reproducibility, |
100 |
steps to reproduce, actual results, expected results, additional info) |
101 |
that ultimately get merged into a single description field in the filed |
102 |
bug or if using the expert wizard. The first time I tried it, I had most |
103 |
of those already in the description by the time I got to the others, and |
104 |
what wasn't there didn't fit with the bug I was filing! But, it's |
105 |
evidence of the sort of bugs they normally get, or would, without the |
106 |
hand-holding, I guess. |
107 |
|
108 |
One thing you'll get used to if you file many Gentoo bugs. They almost |
109 |
always want/need your emerge --info output. I usually attach mine |
110 |
instead of posting inline as it clutters the bug otherwise, but even if |
111 |
you do NOT think it's necessary, always either include/attach it anyway |
112 |
or state why you aren't and that you'll attach it on request. Doing so |
113 |
often prevents a round with the bug wranglers before it even gets |
114 |
assigned to the appropriate package maintainer or herd. Of course, since |
115 |
there's no way to attach to the initial filing, that means a line like |
116 |
"emerge --info to be attached." |
117 |
|
118 |
Since you were getting error messages, if you still have them around, |
119 |
include them too. |
120 |
|
121 |
Don't forget to add that you'll be attaching the patch too! |
122 |
|
123 |
The Severity field is also treated differently on Gentoo. You could go |
124 |
with critical since it's a crash, but most of the time I just leave this |
125 |
normal (unless it's obviously lower than that, trivial/enhancement) and |
126 |
let the bug wrangler or maintainer change it if they want to. |
127 |
|
128 |
Then commit the bug, and go back and attach your emerge --info if |
129 |
necessary, then the patch. |
130 |
|
131 |
-- |
132 |
Duncan - List replies preferred. No HTML msgs. |
133 |
"Every nonfree program has a lord, a master -- |
134 |
and if you use the program, he is your master." Richard Stallman |