From: "Nirbheek Chauhan" <nirbheek.chauhan@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] The app-misc/beagle in portage is seriously outdated!
Date: Thu, 28 Feb 2008 16:47:08 +0530 [thread overview]
Message-ID: <8b4c83ad0802280317u9307742s47545414d0df5ac8@mail.gmail.com> (raw)
In-Reply-To: <47C68D33.4010405@gentoo.org>
On Thu, Feb 28, 2008 at 4:00 PM, Alistair Bush <ali_bush@gentoo.org> wrote:
> > BTW, besides the beagle bump request in the bugzilla of Gentoo, is there
> > any way to let us normal users get beagle up to date?
> >
>
> Im sure that there are more than a few dev that would be willing to
> proxy maintain the package, if a user is prepared to standup and take
> responsibility for it.
This is entirely my fault.
I'm a part of Beagle upstream, and had volunteered to proxy maintain
it. I was the one who was supposed to contact Petteri Räty
(Betelguese) after he had volunteered to proxy maintain it (via a
reply to dsd's email) several weeks ago.
However, I ended up getting busy with other things, procrastinating
this, and in the end majorly slacking in getting Beagle fixed (though
I did update the ebuild on the gentoo bug occasionally)
> Currently it seems that the package doesn't
> build for everyone ( by having a quick look at #201093 ) and this is
> something that any maintainer would have to rectify [1].
Beagle 0.3.3 itself compiles just fine, but yelp and nautilus don't
compile with beagle support (beagle USE flag) because libbeagle got
split from Beagle in 0.3, it's API changed, and the version number got
bumped. Work is in progress to fix yelp with the new libbeagle, but no
such progress has been made in nautilus.
Probably the "beagle" USE flag in nautilus and yelp has to be made to
depend on 0.2.18 since it doesn't work with >=0.3
All in all, I take complete blame for this mess.
/me feels majorly guilty
> [1] Sometimes I get the impression that users think that as long as a
> package works for them, that it works. This sadly isn't the case.
--
~Nirbheek Chauhan
--
gentoo-dev@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-02-28 11:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 2:27 [gentoo-dev] The app-misc/beagle in portage is seriously outdated! Shaochun Wang
2008-02-28 7:17 ` Rémi Cardona
2008-02-28 8:26 ` Shaochun Wang
2008-02-28 10:04 ` Gilles Dartiguelongue
2008-02-28 10:27 ` Cédric Krier
2008-02-28 15:32 ` Daniel Drake
2008-02-28 10:30 ` Alistair Bush
2008-02-28 11:17 ` Nirbheek Chauhan [this message]
2008-02-28 11:33 ` Nirbheek Chauhan
2008-02-28 12:49 ` Shaochun Wang
2008-02-28 18:43 ` Nirbheek Chauhan
2008-02-28 19:19 ` [gentoo-dev] RE: Mesa on i965 (DRI) Mateusz Mierzwinski
2008-02-28 19:32 ` Chris Gianelloni
2008-02-29 11:13 ` Rémi Cardona
2008-02-29 0:47 ` [gentoo-dev] The app-misc/beagle in portage is seriously outdated! Shaochun Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8b4c83ad0802280317u9307742s47545414d0df5ac8@mail.gmail.com \
--to=nirbheek.chauhan@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox