First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 24292
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Patrick Kursawe <phosphan@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Jan Schubert <Jan.Schubert@GMX.li>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
doxygen-1.3.2.ebuild doxygen-1.3.2.ebuild text/plain Jan Schubert 2003-07-11 09:42 0000 2.08 KB Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 24292 depends on: Show dependency tree
Bug 24292 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2003-07-11 09:41 0000 
version bumo based on ebuild for 1.3 

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

------- Comment #1 From Jan Schubert 2003-07-11 09:42:20 0000 ------- 
Created an attachment (id=14382) [edit]
doxygen-1.3.2.ebuild

------- Comment #2 From Patrick Kursawe 2003-07-14 03:27:51 0000 ------- 
Would you please next time just state that the old ebuild works instead of
attaching it and leaving it to me to find out you didn't change anything? :-)

Thanks for the hint.

------- Comment #3 From Jan Schubert 2003-07-14 03:51:36 0000 ------- 
Suree, there where changes: I changed the filename :-) 
 
Sorry, the next time i'll make that clear. But this might be an more generell question on how to 
submit ebuilds or notify about new programm versions. The way using bugzilla might not be the 
smartest way. 
How do i know who is responsible for an specific ebuild? Should i point her/him in an direct 
mail?

------- Comment #4 From Patrick Kursawe 2003-07-14 04:14:06 0000 ------- 
Bugzilla is quite fine for this job (I think), because you can search the bug
database to see if someone has already done what you are planning to do.
Imagine the developer responsible for some popular program doesn't have much
time and gets (insert large number here) e-mails all requesting the same.

About the question of responsibility for ebuilds, that's work in progress. Have
a look at http://www.gentoo.org/proj/en/metastructure/herds/ for the technical
side of it.

Until further notics, please keep reporting this kind of stuff on bugzilla.

------- Comment #5 From Patrick Kursawe 2003-07-14 04:14:18 0000 ------- 
Bugzilla is quite fine for this job (I think), because you can search the bug
database to see if someone has already done what you are planning to do.
Imagine the developer responsible for some popular program doesn't have much
time and gets (insert large number here) e-mails all requesting the same.

About the question of responsibility for ebuilds, that's work in progress. Have
a look at http://www.gentoo.org/proj/en/metastructure/herds/ for the technical
side of it.

Until further notice, please keep reporting this kind of stuff on bugzilla.

------- Comment #6 From Patrick Kursawe 2003-07-14 04:14:44 0000 ------- 
whoops... that click was a bit too fast :-)
First Last Prev Next    No search results available      Search page      Enter new bug