[gentoo-dev] Changes in libreoffice ebuild
As per my comment in bugzilla [1] I said that the patch should be submitted upstream prior having it in cvs. Yet you decided to completely ignore my statement and just smash in the patch anyway [2]. Please don't do this ever again. We had shitload of distro patches before and it is hell to strip away later on. For your statement of lacking documentation, when I google gerrit libreoffice first two links lead directly to the instance and 3rd to wiki [3], which no suprise is guide how to set it up and submit request, so stop lying. As you like to ignore maintainer requests I now expect you to submit it to the gerit, since now you have the guide and you can proceed without an issue right? Note that I have nothing against other devs submitting fixes to ebuilds maintained by me, but directly ignoring what I said on a bug and doing whatever you see fit does not match that at all. Tomas [1] https://bugs.gentoo.org/show_bug.cgi?id=479604#16 [2] https://bugs.gentoo.org/show_bug.cgi?id=479604#19 [3] https://wiki.documentfoundation.org/Development/gerrit
Re: [gentoo-dev] desktop experience on smartphone: thoughts and plans against Ubuntu edge
On 08/13/2013 12:21 AM, heroxbd wrote: Dear Fellows, Canonical is raising money by pushing their concept of Ubuntu for Android[1][2]. The idea is to put GNU environment (esp. Ubuntu userland) in parallel to Android to drive the external HDMI output with X11 protocal, so that desktop applications can run on the smartphone. The idea is cool, but not new. The idea is general to all android devices, while Canonical is binding the concept with its own new device. The project is developed underground by Canonical, so far nothing, not to say repository, is available except advertisements and the call for people to donate. As a natual consequence of the on-going Google Summer of Code project, Gentoo on Android[3], we can run native Gentoo on *all* the Android devices. Compiling out an Xorg and output to HDMI has no theoretical difficulty. Furthermore, sharing of graphic output with Android (instead of a separate HDMI output) can be explored with wayland x11[4]. I feel sorry to the behavior of Canonical. We, people from the Gentoo community, can show the general public what is the cooperative way to develop desktop/smartphone hybrid to benefit all. I would like to kick out a sub-project of Gentoo targeting smartphone and tablets. It would be nice to find out a solution based on Gentoo for desktop/smartphone hybrid *before* Canonical's release. Comments welcome. Cheers, Benda 1. http://www.ubuntu.com/phone/ubuntu-for-android 2. http://www.indiegogo.com/projects/ubuntu-edge 3. http://www.awa.tohoku.ac.jp/~benda/projects/android.html 4. http://en.wikipedia.org/wiki/Wayland_%28display_server_protocol%29 I'm not a developer but this project's existence would motivate me to get a compatible smartphone and test this new Gentoo version on it, assuming it's also capable of standard phone calls and texts, etc.
[gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in profiles: ChangeLog package.mask
On Tue, 13 Aug 2013 05:29:32 +0300 Samuli Suominen ssuomi...@gentoo.org wrote: -# Samuli Suominen ssuomi...@gentoo.org (05 Mar 2013) -# Fails to compile unless system has previously installed copy -# wrt bugs 411443 and 413753 -# Masked temporarily until fixed -=media-libs/libcaca-0.99_beta18 -=app-misc/toilet-0.3 Mask restored, mentioned bugs are still present and the package can't be compiled unless bootstrapped with _beta17. it builds very fine here, I didn't have time to comment on the bugs that are at best unclear, that's all
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in profiles: ChangeLog package.mask
On Tue, 13 Aug 2013 07:37:08 -0400 Alexis Ballier aball...@gentoo.org wrote: On Tue, 13 Aug 2013 05:29:32 +0300 Samuli Suominen ssuomi...@gentoo.org wrote: -# Samuli Suominen ssuomi...@gentoo.org (05 Mar 2013) -# Fails to compile unless system has previously installed copy -# wrt bugs 411443 and 413753 -# Masked temporarily until fixed -=media-libs/libcaca-0.99_beta18 -=app-misc/toilet-0.3 Mask restored, mentioned bugs are still present and the package can't be compiled unless bootstrapped with _beta17. it builds very fine here, I didn't have time to comment on the bugs that are at best unclear, that's all OTOH, it's sad to say but that kind of smartass commit from my part lead to some fixes that had not happened in 5+ months :)
Re: [gentoo-dev] desktop experience on smartphone: thoughts and plans against Ubuntu edge
On 13 August 2013 13:21, heroxbd hero...@gentoo.org wrote: Dear Fellows, I would like to kick out a sub-project of Gentoo targeting smartphone and tablets. It would be nice to find out a solution based on Gentoo for desktop/smartphone hybrid *before* Canonical's release. I would be interested in such a project. -- Cheers, Ben | yngwin Gentoo developer
Re: [gentoo-dev] Changes in libreoffice ebuild
On Tue, 2013-08-13 at 10:10 +0200, Tomáš Chvátal wrote: As per my comment in bugzilla [1] I said that the patch should be submitted upstream prior having it in cvs. Yet you decided to completely ignore my statement and just smash in the patch anyway [2]. Please don't do this ever again. We had shitload of distro patches before and it is hell to strip away later on. For your statement of lacking documentation, when I google gerrit libreoffice first two links lead directly to the instance and 3rd to wiki [3], which no suprise is guide how to set it up and submit request, so stop lying. As you like to ignore maintainer requests I now expect you to submit it to the gerit, since now you have the guide and you can proceed without an issue right? Note that I have nothing against other devs submitting fixes to ebuilds maintained by me, but directly ignoring what I said on a bug and doing whatever you see fit does not match that at all. Tomas [1] https://bugs.gentoo.org/show_bug.cgi?id=479604#16 [2] https://bugs.gentoo.org/show_bug.cgi?id=479604#19 [3] https://wiki.documentfoundation.org/Development/gerrit Tomáš, considering that libreoffice and libreoffice-bin were both broken on ~arch (so ~arch users did not have a compatible office suite to fall back on); the bug had 33 people in the CC list; a working patch was submitted, with a justification for why it is the correct solution, and was verified to work; and your response was (paraphrased) I will look at this later - I personally think that a small violation of openoffice team policies could in this particular case be forgiven. In addition, the policy itself is IMHO rather strange. If the goal is to ensure that any gentoo patch is visible to upstream developers and to libreoffice maintainers from other distros, so that they can merge it if they agree with the implementation, surely it would make no difference whether the patch got submitted to gerrit by Patrick before committing to gx86, or by you a week later? [1] On the other hand, if the goal is to avoid any divergence from upstream, presumably you want to first obtain feedback from upstream developers and an indication that they will merge the patch - in which case merely submitting something to gerrit, without waiting for upstream developer response, doesn't make sense. [1] on August 11, you had indicated that you would have time to look at the bug in ~10 days time.
Re: [gentoo-dev] Changes in libreoffice ebuild
On Tue, 13 Aug 2013 11:00:57 -0400 Alexandre Rostovtsev tetrom...@gentoo.org wrote: Tomáš, considering that libreoffice and libreoffice-bin were both broken on ~arch (so ~arch users did not have a compatible office suite to fall back on); the bug had 33 people in the CC list; a working patch was submitted, with a justification for why it is the correct solution, and was verified to work; and your response was (paraphrased) I will look at this later - I personally think that a small violation of openoffice team policies could in this particular case be forgiven. In addition, the policy itself is IMHO rather strange. If the goal is to ensure that any gentoo patch is visible to upstream developers and to libreoffice maintainers from other distros, so that they can merge it if they agree with the implementation, surely it would make no difference whether the patch got submitted to gerrit by Patrick before committing to gx86, or by you a week later? [1] On the other hand, if the goal is to avoid any divergence from upstream, presumably you want to first obtain feedback from upstream developers and an indication that they will merge the patch - in which case merely submitting something to gerrit, without waiting for upstream developer response, doesn't make sense. [1] on August 11, you had indicated that you would have time to look at the bug in ~10 days time. Your arguments make sense but you should also consider it the other way: When you are maintaining a package properly by forwarding patches upstream, having $randomdev jumping in, adding a patch, and letting you clean up the mess is kind of annoying. Part of Tomas' original email was: I've googled it for you, now would you please submit that patch upstream and be forgiven? Alexis.
Re: [gentoo-dev] desktop experience on smartphone: thoughts and plans against Ubuntu edge
On 8/12/13 10:21 PM, heroxbd wrote: As a natual consequence of the on-going Google Summer of Code project, Gentoo on Android[3], we can run native Gentoo on *all* the Android devices. Compiling out an Xorg and output to HDMI has no theoretical difficulty. Furthermore, sharing of graphic output with Android (instead of a separate HDMI output) can be explored with wayland x11[4]. Sounds good. Note that it doesn't need to be set up as against Canonical. Just do the best thing for the users. I would like to kick out a sub-project of Gentoo targeting smartphone and tablets. It would be nice to find out a solution based on Gentoo for desktop/smartphone hybrid *before* Canonical's release. Everybody can create a sub-project, and I'm happy to see this kind of project appearing in Gentoo. I'd recommend focusing on creating a good, compelling experience, not just pushing out something before Canonical. :) Paweł signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Changes in libreoffice ebuild
On 8/13/13 8:39 AM, Alexis Ballier wrote: Your arguments make sense but you should also consider it the other way: When you are maintaining a package properly by forwarding patches upstream, having $randomdev jumping in, adding a patch, and letting you clean up the mess is kind of annoying. Part of Tomas' original email was: I've googled it for you, now would you please submit that patch upstream and be forgiven? I agree with staying very close to upstream and submitting patches to them. This is especially important for big packages like libreoffice or say chromium (I help to maintain the latter). Note that there is a possible confusion what ~arch is about. Are breakages allowed there? How long before they get fixed? For example, one could arguably say neon-0.30.0 was added to the tree without testing reverse dependencies. Interestingly, it was submitted by Arfrever (just stating the fact). To his defense, he submitted the libreoffice patch to bugzilla on the same day. Still, one could ask: why wasn't neon-0.30.0 masked instead? One thing I think is really important is respecting the maintainers. If maintainer said please send the patch upstream before committing to cvs, it is _not_ OK to just ignore that. There are other options available like masking neon. And finally to the defense of libreoffice maintainers: packages take long time to compile, people have life. The policy about staying close to upstream is a very good one, and I can totally understand and agree with what they're saying. Paweł signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] desktop experience on smartphone: thoughts and plans against Ubuntu edge
On 13/08/13 08:21, heroxbd wrote: Dear Fellows, Canonical is raising money by pushing their concept of Ubuntu for Android[1][2]. The idea is to put GNU environment (esp. Ubuntu userland) in parallel to Android to drive the external HDMI output with X11 protocal, so that desktop applications can run on the smartphone. The idea is cool, but not new. The idea is general to all android devices, while Canonical is binding the concept with its own new device. The project is developed underground by Canonical, so far nothing, not to say repository, is available except advertisements and the call for people to donate. As a natual consequence of the on-going Google Summer of Code project, Gentoo on Android[3], we can run native Gentoo on *all* the Android devices. Compiling out an Xorg and output to HDMI has no theoretical difficulty. Furthermore, sharing of graphic output with Android (instead of a separate HDMI output) can be explored with wayland x11[4]. I feel sorry to the behavior of Canonical. We, people from the Gentoo community, can show the general public what is the cooperative way to develop desktop/smartphone hybrid to benefit all. I would like to kick out a sub-project of Gentoo targeting smartphone and tablets. It would be nice to find out a solution based on Gentoo for desktop/smartphone hybrid *before* Canonical's release. Comments welcome. Cheers, Benda 1. http://www.ubuntu.com/phone/ubuntu-for-android 2. http://www.indiegogo.com/projects/ubuntu-edge 3. http://www.awa.tohoku.ac.jp/~benda/projects/android.html 4. http://en.wikipedia.org/wiki/Wayland_%28display_server_protocol%29 Does gpe-base/* and gpe-utils/* relate to this at all?
Re: [gentoo-dev] desktop experience on smartphone: thoughts and plans against Ubuntu edge
Benda, while I won't have the time to contribute much, I would like to tell you that this is definitely a very cool and worthwhile project! I think you should make a project page and sign yourself up as team lead immediately... :) Chris Reffett from KDE team has done already a lot of work on packaging Plasma Active, see http://plasma-active.org/ - it's in the KDE overlay but mostly untested so far. You might be interested! Best, Andreas Dear Fellows, Canonical is raising money by pushing their concept of Ubuntu for Android[1][2]. The idea is to put GNU environment (esp. Ubuntu userland) in parallel to Android to drive the external HDMI output with X11 protocal, so that desktop applications can run on the smartphone. The idea is cool, but not new. The idea is general to all android devices, while Canonical is binding the concept with its own new device. The project is developed underground by Canonical, so far nothing, not to say repository, is available except advertisements and the call for people to donate. As a natual consequence of the on-going Google Summer of Code project, Gentoo on Android[3], we can run native Gentoo on *all* the Android devices. Compiling out an Xorg and output to HDMI has no theoretical difficulty. Furthermore, sharing of graphic output with Android (instead of a separate HDMI output) can be explored with wayland x11[4]. I feel sorry to the behavior of Canonical. We, people from the Gentoo community, can show the general public what is the cooperative way to develop desktop/smartphone hybrid to benefit all. I would like to kick out a sub-project of Gentoo targeting smartphone and tablets. It would be nice to find out a solution based on Gentoo for desktop/smartphone hybrid *before* Canonical's release. Comments welcome. Cheers, Benda 1. http://www.ubuntu.com/phone/ubuntu-for-android 2. http://www.indiegogo.com/projects/ubuntu-edge 3. http://www.awa.tohoku.ac.jp/~benda/projects/android.html 4. http://en.wikipedia.org/wiki/Wayland_%28display_server_protocol%29 -- Andreas K. Huettel Gentoo Linux developer kde, sci, arm, tex, printing signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] Changes in libreoffice ebuild
On Tue, Aug 13, 2013 at 12:03 PM, Paweł Hajdan, Jr. phajdan...@gentoo.org wrote: One thing I think is really important is respecting the maintainers. If maintainer said please send the patch upstream before committing to cvs, it is _not_ OK to just ignore that. There are other options available like masking neon. Also, users running ~arch should know to search bugzilla when they have problems, and there they would find the patch which they could apply. I think it is important to work with maintainers first and foremost. They're the ones with the long-term commitment. Sure, there can be exceptions for simple file additions like init scripts, but certainly random parties shouldn't be adding patches to ebuilds without maintainer agreement unless they're willing to step in and become a committed co-maintainer (with all the responsibilities that entails). If a maintainer is holding something up for months by all means escalate it if you think it is justified, but if a maintainer just wants a few days to look into things, that isn't asking too much. If this were a security patch I might feel differently, or a stable regression (though as has been pointed out that shouldn't happen with reverse dep testing). Rich
Re: [gentoo-dev] desktop experience on smartphone: thoughts and plans against Ubuntu edge
Indeed I have. If you want to start such a project, I would certainly be interested in joining. Plasma Active is basically untested because I don't have a mobile device with Gentoo and installing it on a normal computer leads to display sizing issues, but I welcome any suggestions or bug reports you have for that. What I would really like to see come out of this is some pre-made Gentoo stage4s for different kinds of devices, which I think would be a big draw for users. Chris Reffett On 8/13/2013 1:09 PM, Andreas K. Huettel wrote: Benda, while I won't have the time to contribute much, I would like to tell you that this is definitely a very cool and worthwhile project! I think you should make a project page and sign yourself up as team lead immediately... :) Chris Reffett from KDE team has done already a lot of work on packaging Plasma Active, see http://plasma-active.org/ - it's in the KDE overlay but mostly untested so far. You might be interested! Best, Andreas Dear Fellows, Canonical is raising money by pushing their concept of Ubuntu for Android[1][2]. The idea is to put GNU environment (esp. Ubuntu userland) in parallel to Android to drive the external HDMI output with X11 protocal, so that desktop applications can run on the smartphone. The idea is cool, but not new. The idea is general to all android devices, while Canonical is binding the concept with its own new device. The project is developed underground by Canonical, so far nothing, not to say repository, is available except advertisements and the call for people to donate. As a natual consequence of the on-going Google Summer of Code project, Gentoo on Android[3], we can run native Gentoo on *all* the Android devices. Compiling out an Xorg and output to HDMI has no theoretical difficulty. Furthermore, sharing of graphic output with Android (instead of a separate HDMI output) can be explored with wayland x11[4]. I feel sorry to the behavior of Canonical. We, people from the Gentoo community, can show the general public what is the cooperative way to develop desktop/smartphone hybrid to benefit all. I would like to kick out a sub-project of Gentoo targeting smartphone and tablets. It would be nice to find out a solution based on Gentoo for desktop/smartphone hybrid *before* Canonical's release. Comments welcome. Cheers, Benda 1. http://www.ubuntu.com/phone/ubuntu-for-android 2. http://www.indiegogo.com/projects/ubuntu-edge 3. http://www.awa.tohoku.ac.jp/~benda/projects/android.html 4. http://en.wikipedia.org/wiki/Wayland_%28display_server_protocol%29
[gentoo-dev] news item: Language of compiler messages etc. in build logs
Dear all, in today's council session, we decided to add LC_MESSAGES=C to the base profile make.defaults, accompanied by a news item. Below is a draft for said news item for review and comments. I will commit the news item and the profile change upcoming friday evening. ### Title: Language of compiler messages etc. in build logs Author: Andreas K. Huettel dilfri...@gentoo.org Content-Type: text/plain Posted: 2013-08-16 Revision: 1 News-Item-Format: 1.0 As of today, the emerge build logs do not use the system locale anymore but default to English. The intention behind this is to ease the work of bug-wranglers and package maintainers, who may have a hard time analyzing localized builds. This change only affects the emerge build logs, nothing else. If you really want to have e.g. localized compiler error messages in your builds, set LC_MESSAGES in your /etc/portage/make.conf. Note that submitting localized build logs to the Gentoo Bugzilla is discouraged, and that such bug reports may be closed as INVALID by the package maintainer. ### Cheers, Andreas -- Andreas K. Huettel Gentoo Linux developer dilfri...@gentoo.org http://www.akhuettel.de/ signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] news item: Language of compiler messages etc. in build logs
Dnia 2013-08-13, o godz. 22:59:49 Andreas K. Huettel dilfri...@gentoo.org napisał(a): Note that submitting localized build logs to the Gentoo Bugzilla is discouraged, and that such bug reports may be closed as INVALID by the package maintainer. Sounds too harsh IMO. And NEEDINFO seems more correct resolution when maintainer needs more information (English build log). How about telling instead something like 'maintainer may request English build log which will greatly delay resolving the bug'? -- Best regards, Michał Górny signature.asc Description: PGP signature
Re: [gentoo-dev] news item: Language of compiler messages etc. in build logs
On Tue, Aug 13, 2013 at 5:04 PM, Michał Górny mgo...@gentoo.org wrote: Dnia 2013-08-13, o godz. 22:59:49 Andreas K. Huettel dilfri...@gentoo.org napisał(a): Note that submitting localized build logs to the Gentoo Bugzilla is discouraged, and that such bug reports may be closed as INVALID by the package maintainer. Sounds too harsh IMO. And NEEDINFO seems more correct resolution when maintainer needs more information (English build log). How about telling instead something like 'maintainer may request English build log which will greatly delay resolving the bug'? Agree NEEDINFO is better, but end result is the same. Fine with softening the language. Bottom line though is that maintainers will only accept non-English at their own discretion. Rich
Re: [gentoo-dev] news item: Language of compiler messages etc. in build logs
On Tue, 13 Aug 2013 22:59:49 +0200 Andreas K. Huettel dilfri...@gentoo.org wrote: As of today, the emerge build logs do not use the system locale anymore but default to English. The intention behind this is to ease the work of bug-wranglers and package maintainers, who may have a hard time analyzing localized builds. This change only affects the emerge build logs, nothing else. If you really want to have e.g. localized compiler error messages in your builds, set LC_MESSAGES in your /etc/portage/make.conf. Could you add something like For more details w.r.t. localization, see https://wiki.gentoo.org/wiki/Localization/HOWTO; so people can look up here how to set that particular setting and learn about other settings. Note that submitting localized build logs to the Gentoo Bugzilla is discouraged, and that such bug reports may be closed as INVALID by the package maintainer. Would very much like to see this part dropped or a bit more polite; even in another language, you often only need the error message and if you use a translator like Google Translate you often get an error code that closely resembles the English error. As far as I am aware bug wranglers usually translate the error; and only very rarely, it can't be translated or other parts of the build logs are needed. I haven't heard of much problems with this yet... If kept, word it something like When filing bugs; if maintainers are unable to translate the necessary information from the build log, please attach an English build log [1] and then reopen the bug. [1]: `LC_MESSAGES=C emerge ...`. Thanks for the change and thank you very much in advance. -- With kind regards, Tom Wijsman (TomWij) Gentoo Developer E-mail address : tom...@gentoo.org GPG Public Key : 6D34E57D GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D signature.asc Description: PGP signature
Re: [gentoo-dev] desktop experience on smartphone: thoughts and plans against Ubuntu edge
Hi Benda, Great idea! I would definitely be interested in joining. Regards, Pavel On Mon, Aug 12, 2013 at 10:21 PM, heroxbd hero...@gentoo.org wrote: Dear Fellows, Canonical is raising money by pushing their concept of Ubuntu for Android[1][2]. The idea is to put GNU environment (esp. Ubuntu userland) in parallel to Android to drive the external HDMI output with X11 protocal, so that desktop applications can run on the smartphone. The idea is cool, but not new. The idea is general to all android devices, while Canonical is binding the concept with its own new device. The project is developed underground by Canonical, so far nothing, not to say repository, is available except advertisements and the call for people to donate. As a natual consequence of the on-going Google Summer of Code project, Gentoo on Android[3], we can run native Gentoo on *all* the Android devices. Compiling out an Xorg and output to HDMI has no theoretical difficulty. Furthermore, sharing of graphic output with Android (instead of a separate HDMI output) can be explored with wayland x11[4]. I feel sorry to the behavior of Canonical. We, people from the Gentoo community, can show the general public what is the cooperative way to develop desktop/smartphone hybrid to benefit all. I would like to kick out a sub-project of Gentoo targeting smartphone and tablets. It would be nice to find out a solution based on Gentoo for desktop/smartphone hybrid *before* Canonical's release. Comments welcome. Cheers, Benda 1. http://www.ubuntu.com/phone/ubuntu-for-android 2. http://www.indiegogo.com/projects/ubuntu-edge 3. http://www.awa.tohoku.ac.jp/~benda/projects/android.html 4. http://en.wikipedia.org/wiki/Wayland_%28display_server_protocol%29
Re: [gentoo-dev] news item: Language of compiler messages etc. in build logs
On Tue, Aug 13, 2013 at 5:37 PM, Tom Wijsman tom...@gentoo.org wrote: If kept, word it something like When filing bugs; if maintainers are unable to translate the necessary information from the build log, please attach an English build log [1] and then reopen the bug. So, this is why I wanted a vote on whether maintainers had to support non-English logs. By all means make the wording nice, but my feeling is that acceptance of bugs in something other than English should be purely at the maintainer's discretion. Rich
[gentoo-dev] Re: GCC 4.8 unmasking
On Tue, 13 Aug 2013 07:13:13 +0200 Luca Barbato lu_z...@gentoo.org wrote: On 13/08/13 03:41, Ryan Hill wrote: I don't see any reason to keep this masked other than bug #416069, which needs to be fixed anyways. How does Friday sound? https://bugs.gentoo.org/416069 xorg-2.eclass: add --disable-selective-werror to configure https://bugs.gentoo.org/461954 GCC 4.8 porting gcc-4.8 can miscompile libc http://gcc.gnu.org/bugzilla//show_bug.cgi?id=56888 We should make sure we do not get bitten by this. We don't build glibc with -O3. Other libc's should either not use -O3 or use -fno-tree-loop-distribute-patterns where applicable. -- Ryan Hillpsn: dirtyepic_sk gcc-porting/toolchain/wxwidgets @ gentoo.org 47C3 6D62 4864 0E49 8E9E 7F92 ED38 BD49 957A 8463 signature.asc Description: PGP signature
Re: [gentoo-dev] Changes in libreoffice ebuild
On 14:37 Tue 13 Aug , Rich Freeman wrote: If a maintainer is holding something up for months by all means escalate it if you think it is justified, but if a maintainer just wants a few days to look into things, that isn't asking too much. If this were a security patch I might feel differently, or a stable regression (though as has been pointed out that shouldn't happen with reverse dep testing). Turns out we already wrote this down. See Touching other developers ebuilds: http://devmanual.gentoo.org/ebuild-writing/ebuild-maintenance/index.html Otherwise a soft limit of 2 to 4 weeks depending on the severity of the bug is an acceptable time frame before you go ahead and fix it yourself. -- Thanks, Donnie Donnie Berkholz Council Member / Sr. Developer, Gentoo Linux http://dberkholz.com Analyst, RedMonk http://redmonk.com/dberkholz/ pgpFgfbAJDv3x.pgp Description: PGP signature
