View previous topic :: View next topic |
Author |
Message |
pd1986 Guru
Joined: 19 Feb 2012 Posts: 404 Location: Paris
|
Posted: Wed Feb 26, 2014 11:15 pm Post subject: [solved]find a bug in ebuild in overlay, how to report it? |
|
|
I found a bug that media-libs/libao.needs to be added in the ebuild of goldendict-9999 in overlay "stuff", how to tell it to the manager? thanks
Last edited by pd1986 on Thu Feb 27, 2014 8:40 am; edited 1 time in total |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21630
|
Posted: Wed Feb 26, 2014 11:57 pm Post subject: |
|
|
Contact whoever has write access to the overlay. Either they can fix it or they can tell refer you to someone more appropriate. |
|
Back to top |
|
|
khayyam Watchman
Joined: 07 Jun 2012 Posts: 6227 Location: Room 101
|
Posted: Thu Feb 27, 2014 12:30 am Post subject: |
|
|
pd1986 ...
Code: | # grep -i contact <(layman --nocolor --info stuff)
* Contact : megagreener[at]gmail[dot]com |
(spam protected)
HTH & best ... khay |
|
Back to top |
|
|
pd1986 Guru
Joined: 19 Feb 2012 Posts: 404 Location: Paris
|
Posted: Thu Feb 27, 2014 8:06 am Post subject: |
|
|
Hu wrote: | Contact whoever has write access to the overlay. Either they can fix it or they can tell refer you to someone more appropriate. |
I don't know who write this. I didn't find this. That why I asked here. |
|
Back to top |
|
|
i92guboj Bodhisattva
Joined: 30 Nov 2004 Posts: 10315 Location: Córdoba (Spain)
|
Posted: Thu Feb 27, 2014 8:28 am Post subject: |
|
|
khayyam told you how to see that information. Each overlay contains some metainfo files which describe among many other things the person to contact in these cases. The command he posted is just a convenient way to extract that little bit of info. You just have to substitute "stuff" with the name of the offending overlay. |
|
Back to top |
|
|
pd1986 Guru
Joined: 19 Feb 2012 Posts: 404 Location: Paris
|
Posted: Thu Feb 27, 2014 8:32 am Post subject: |
|
|
i92guboj wrote: | khayyam told you how to see that information. Each overlay contains some metainfo files which describe among many other things the person to contact in these cases. The command he posted is just a convenient way to extract that little bit of info. You just have to substitute "stuff" with the name of the offending overlay. |
I didn't notice that. Thanks
I was trying to find the contact who write that ebuild |
|
Back to top |
|
|
Freeky Tux's lil' helper
Joined: 11 Mar 2011 Posts: 129 Location: Novosibirsk, Russia
|
|
Back to top |
|
|
pd1986 Guru
Joined: 19 Feb 2012 Posts: 404 Location: Paris
|
Posted: Thu Feb 27, 2014 9:23 am Post subject: |
|
|
Yes, I found that and I posted an issue via the site |
|
Back to top |
|
|
Yamakuzure Advocate
Joined: 21 Jun 2006 Posts: 2284 Location: Adendorf, Germany
|
Posted: Thu Feb 27, 2014 10:55 am Post subject: |
|
|
And the most easy solution is to use layman itself: Code: | ~ $ layman -i stuff
* stuff
* ~~~~~
* Source : https://github.com/megabaks/stuff.git
* Contact : megagreener@gmail.com
* Type : Git; Priority: 50
* Quality : experimental
*
* Description:
* stuff
*
* Link:
* https://github.com/megabaks/stuff
*
* Feed:
* https://github.com/megabaks/stuff/commits/master.atom
* | _________________ Important German:- "Aha" - German reaction to pretend that you are really interested while giving no f*ck.
- "Tja" - German reaction to the apocalypse, nuclear war, an alien invasion or no bread in the house.
|
|
Back to top |
|
|
pd1986 Guru
Joined: 19 Feb 2012 Posts: 404 Location: Paris
|
Posted: Thu Feb 27, 2014 5:11 pm Post subject: |
|
|
Yamakuzure wrote: | And the most easy solution is to use layman itself: Code: | ~ $ layman -i stuff
* stuff
* ~~~~~
* Source : https://github.com/megabaks/stuff.git
* Contact : megagreener@gmail.com
* Type : Git; Priority: 50
* Quality : experimental
*
* Description:
* stuff
*
* Link:
* https://github.com/megabaks/stuff
*
* Feed:
* https://github.com/megabaks/stuff/commits/master.atom
* | |
Yes, that's what I did |
|
Back to top |
|
|
|