On Mon, 2 March 2015, at 1:36 am, Fernando Rodriguez
wrote:
>> ...
>> Don't forget to file a bug so we can track your issue.
>
> Should I file one with gentoo even if it's an upstream bug?
Yes.
Usually what I do in this case is go to the upstream mailing list, and see if I
get any quick ans
On Friday, February 27, 2015 11:45:52 AM Alan McKinnon wrote:
> You can look in the packages Changelog in the portage tree, perhaps
> there's an entry there explaining why the old version was removed.
It only says "Version bump. Removed old"
> ebuilds are never truly lost, if you still have it
> On Feb 27, 2015, at 9:07, Fernando Rodriguez
> wrote:
>
> Why does a good ebuild gets replaced with a broken one? Is there any way to
> make sure that packages that I'm using don't get removed from the portage tree
> or at least that the package doesn't get downgraded automatically. Right now
On Fri, 27 Feb 2015 03:07:34 -0500
Fernando Rodriguez wrote:
>
> I've been using kdevelop-4.7.0 (unstable) for a while and it was
> working just fine. Then about a couple weeks ago it's ebuild got
> deleted from the portage tree and replaced with kdevelop-4.7.1 which
> is broken (I have issues w
I've been using kdevelop-4.7.0 (unstable) for a while and it was working just
fine. Then about a couple weeks ago it's ebuild got deleted from the portage
tree and replaced with kdevelop-4.7.1 which is broken (I have issues with
remote debugging).
Why does a good ebuild gets replaced with a br
5 matches
Mail list logo
