On Thursday, 28. September. 2006 04:23, Drake Wyrm wrote:
Christian Heim [EMAIL PROTECTED] wrote:
# Alec Warner [EMAIL PROTECTED] (27 Aug 2006)
# Masking media-radio/xlog for treecleaners and bug(s) # 88580
# Sept 27th for removal
media-radio/xlog
Punted.
So, why was this one
On Wed, 27 Sep 2006 21:13:59 +0200, Christian Heim wrote:
Its my pleasure to introduce to you lack, our recent addition joining us to
take care of the rox-related ebuilds.
He hails from Saskatoon, Saskatchewan, Canada.
Eh?
When he's unplugged from
his computer, he tries to play some
Drake Wyrm wrote:
Christian Heim [EMAIL PROTECTED] wrote:
# Alec Warner [EMAIL PROTECTED] (27 Aug 2006)
# Masking media-radio/xlog for treecleaners and bug(s) # 88580
# Sept 27th for removal
media-radio/xlog
Punted.
So, why was this one punted, anyway? The bug was fixed in the new
version,
How about entering the removed ebuilds into bugzilla under an adequate section?
--
gentoo-dev@gentoo.org mailing list
On 9/28/06, Mark Stier [EMAIL PROTECTED] wrote:
How about entering the removed ebuilds into bugzilla under an adequate section?
--
gentoo-dev@gentoo.org mailing list
In the event of tree booting, you have the option to maintain the
ebuild in an overlay such as sunrise[1]. Or seeking out some
Alec Warner wrote:
stuff gets fixed (aka pornview)
Why doesn't this surprise me? :)
--
Andrew Gaffneyhttp://dev.gentoo.org/~agaffney/
Gentoo Linux Developer Installer Project
Today's lesson in political correctness: Go
Mark Stier wrote:
How about entering the removed ebuilds into bugzilla under an adequate
section?
Uhm...
http://sources.gentoo.org/viewcvs.py/gentoo-x86/
--
jakub
signature.asc
Description: OpenPGP digital signature
I took over as the maintainer for net-misc/freenet6 in hopes to spend
some time bringing it up to date and to close the few bugs[1][2][3] open
for it. I have not had nearly the time that I would have liked to work
on this, and I no longer use the package.
I'm hoping to find another maintainer to
stuff gets fixed (aka pornview)
Why doesn't this surprise me? :)
Heh.
If you actually tried it, though, you'd see that's it's a nice
application and the pr0n thingy is just a joke .-)
--
gentoo-dev@gentoo.org mailing list
+++ Mark Stier [28/09/06 15:35 +0200]:
How about entering the removed ebuilds into bugzilla under an adequate
section?
I think my original reply got lost, so just in case - seems like a time for
sunset overlays ;0
~mcummings
--
gentoo-dev@gentoo.org mailing list
On 9/28/06, Michael Cummings [EMAIL PROTECTED] wrote:
+++ Mark Stier [28/09/06 15:35 +0200]:How about entering the removed ebuilds into bugzilla under an adequatesection?I think my original reply got lost, so just in case - seems like a time forsunset overlays ;0
or sunrise rather...-- David
Tach David, 0x2B859DE3 (PGP-PK-ID)
David Grant schrieb:
On 9/28/06, Michael Cummings [EMAIL PROTECTED] wrote:
+++ Mark Stier [28/09/06 15:35 +0200]:
How about entering the removed ebuilds into bugzilla under an adequate
section?
I think my original reply got
Christian 'Opfer' Faulhammer wrote:
Tach David, 0x2B859DE3 (PGP-PK-ID)
David Grant schrieb:
On 9/28/06, Michael Cummings [EMAIL PROTECTED] wrote:
+++ Mark Stier [28/09/06 15:35 +0200]:
How about entering the removed ebuilds into bugzilla under an adequate
Hi folks,
maybe you remember the discussion about package removal and
problems for users on that ...
The problem was: someone (who's not reading this list) might be
interested in some package (or even had installed it) and now
gets trouble because its (from his view) sudden removal.
An
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Enrico Weigelt wrote:
Hi folks,
snip
To be perfectly honest, we're not going to hold someone's hand with
this. We shouldn't be expected to. A package will be in mask for a
month before its removed. That's a good warning sign that something is
up.
On Thu, 28 Sep 2006 22:28:27 +0200
Enrico Weigelt [EMAIL PROTECTED] wrote:
An solution could be an database of packages scheduled for
removal. But this database has to be maintained. And it doesn't
seem that there's someone who's interested in doing this extra work.
As I understand it, every
Enrico Weigelt wrote:
An solution could be an database of packages scheduled for
removal. But this database has to be maintained. And it doesn't
seem that there's someone who's interested in doing this extra work.
Well, there is bugzilla. Just track any bugs with [EMAIL PROTECTED] in
The problem was: someone (who's not reading this list) might be
interested in some package (or even had installed it) and now
gets trouble because its (from his view) sudden removal.
My project is responsible for what I'd imagine to be the most tree
removals; we have strict guidelines
18 matches
Mail list logo
