Re: [arch-dev-public] Archlinux [current] status

9 May 2007

      On Wed, May 09, 2007 at 12:52:31PM -0500, Aaron Griffin wrote:
...
On 5/9/07, Jason Chu  wrote:
...
On Wed, May 09, 2007 at 10:42:12AM -0500, Aaron Griffin wrote:
...
On 5/9/07, Jason Chu  wrote:
...
On Wed, May 09, 2007 at 04:54:43PM +0200, Tobias Powalowski wrote:
...
...
On Tue, May 08, 2007 at 10:30:59PM +0200, Tobias Powalowski wrote:
> Hi
> something is really going wrong at the moment.
> People claim for having other interests or not time for doing the
> packaging work.
> I start here only with [current] first.
> Jan quit doing maintenance of important parts of our distro and probably
> also of doing quite some update tirades through current.
>
> Let me stress this, from my point of view Jan and me did the most
> [current] updates the last weeks, even if we didn't use the software for
> our own stuff, correct me if im wrong.
>
> We have inactive package maintainers, no doubt.
> Judd, Dorphell, Aurelien, Gregor, Woody, Arjan
>
> It's time to cleanup [current].
> Orphan all packages of Judd, Dorphell, Aurelien, Gregor
> 1 week of time to grab what packages you wanna have.
> Keep in mind it's your job then to test and ensure that the package
> works! Please one of the enablers do this, or give me the permission to
> orphan them.
Is it possible to have a step before this one that's not as disruptive?
This will create a lot of orphans very quickly.
Jason
Well that way you see quickly who wants to  take packages and which ones need
Am Mittwoch, 9. Mai 2007 schrieb Jason Chu:
maintainers, im sick of browsing judds and dorphells dashboard to find the
flagged ones, there are also some that are not outdated at all.
greetings
tpowa
I was just thinking there might be a few packages that each of the
developers (mostly Judd) wants to hang on to.  If you orphan all of them,
then they'll have to snatch them back up again.
They could always ask.  Besides, I don't see any hurt here besides the
false pride that comes with single-ownership of a package ("that's MY
package").
Alright, I conceed.  Let's do this thing!
Jason, can you take this task on? I want to
a) figure out a solution to the pacman upgrade issue
b) deal with the package cleanup
So I don't have huge amounts of time to spare at the moment.
I am also lacking in time.  Can you explain the pacman upgrade issue a
little better (there was a bug report about it at one point, right?)?

I will make sure something gets done, but I doubt I'll be the one to do it.

Jason