[gentoo-user] Deleted kdevelop ebuilds

[gentoo-user] Deleted kdevelop ebuilds

[Fernando Rodriguez]

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 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 
if I install an unstable package by keywording a specific version and it gets 
deleted you get downgraded the next time you run emerge -vauDN so you have no 
simple way of going back to your working configuration since the ebuild is 
gone.

-- 
Fernando Rodriguez

Re: [gentoo-user] Deleted kdevelop ebuilds

[Matti Nykyri]

> On Feb 27, 2015, at 9:07, Fernando Rodriguez <frodriguez.developer@outlook.com> 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 
> if I install an unstable package by keywording a specific version and it gets 
> deleted you get downgraded the next time you run emerge -vauDN so you have no 
> simple way of going back to your working configuration since the ebuild is 
> gone.

I would do it like this:

Make an overlay of your own and copy the wanted ebuild there. Mask the package and unmask the version you copied to the overlay. 

Of course there are also other ways....

You can download an old portage snapshot to get the deleted ebuild back.

-- 
-Matti

Re: [gentoo-user] Deleted kdevelop ebuilds

[Alan McKinnon]

On Fri, 27 Feb 2015 03:07:34 -0500
Fernando Rodriguez <frodriguez.developer@outlook.com> 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 with remote debugging).
> 
> 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 if I install an unstable package by
> keywording a specific version and it gets deleted you get downgraded
> the next time you run emerge -vauDN so you have no simple way of
> going back to your working configuration since the ebuild is gone.
> 

You can look in the packages Changelog in the portage tree, perhaps
there's an entry there explaining why the old version was removed.

ebuilds are never truly lost, if you still have it installed the ebuild
is stored in /var/db. If not, you can find it in the gentoo attic
(google can help), download it and put it in your local overlay. Mask
the versions you don't want and portage will ensure your local copy
stays installed.

Alan

Re: [gentoo-user] Deleted kdevelop ebuilds

[Fernando Rodriguez]

[-- Attachment #1: Type: text/plain, Size: 756 bytes --]

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 installed the ebuild
> is stored in /var/db. If not, you can find it in the gentoo attic
> (google can help), download it and put it in your local overlay. Mask
> the versions you don't want and portage will ensure your local copy
> stays installed.

Thanks, I found it on the attic, I didn't know you could get deleted ebuilds 
from it. I think it would be best if portage didn't downgrade packages 
automatically.

-- 
Fernando Rodriguez

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[gentoo-user] Re: Deleted kdevelop ebuilds

[Michael Palimaka]

On 27/02/15 19:07, 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 with 
> remote debugging).
> 
> 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 
> if I install an unstable package by keywording a specific version and it gets 
> deleted you get downgraded the next time you run emerge -vauDN so you have no 
> simple way of going back to your working configuration since the ebuild is 
> gone.
> 

Don't forget to file a bug so we can track your issue.

Re: [gentoo-user] Re: Deleted kdevelop ebuilds

[Fernando Rodriguez]

On Sunday, March 01, 2015 3:01:09 AM Michael Palimaka wrote:
> On 27/02/15 19:07, 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 with 
> > remote debugging).
> > 
> > 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 
> > if I install an unstable package by keywording a specific version and it 
gets 
> > deleted you get downgraded the next time you run emerge -vauDN so you have 
no 
> > simple way of going back to your working configuration since the ebuild is 
> > gone.
> > 
> 
> 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?

-- 
Fernando Rodriguez

Re: [gentoo-user] Deleted kdevelop ebuilds

[Stroller]

On Mon, 2 March 2015, at 1:36 am, Fernando Rodriguez <frodriguez.developer@outlook.com> 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 answers. 

This may resolve in a quick fix, a bug being opened or no response, but in any case you can then open a ticket at bugs.gentoo.org giving a link to upstream - either "this is bug 1234 at KDE, see bugs.kde.org/ticket?1234" or "this is how you fix it" or "I tried to get help on the KDE mailing list but there was no response, see archive.lists.kde.org/989871".

At the end of the day, the Gentoo devs have scarcely more resources than you or I do. If the problem is going to get fixed then someone needs to roll up their sleeves and get their hands dirty. You might not be an elite QT programmer capable of fixing the bug, but if you believe it to be an upstream issue then at least you can bring it to their attention and help them identify when it shows up.

Stroller.