On Wed, Jun 24, 2009 at 2:18 PM, Eric Bélanger wrote:

On Wed, Jun 24, 2009 at 2:53 PM, Aaron Griffin wrote:

...

Hey all, This is part informational, and part not.

We have a donated server from SevenL networks that has sat mostly unused up until now. What we would like to do is more the AUR and community on to that machine, so that TUs can get real (limited) shell accounts and the people managing this side of the project get a bit more control.

As far as I know, things are almost ready to go, but what we need to do is setup a good time to "freeze" the AUR and community so we can switch over the DNS and change checkout locations.

Once this is complete, we can move forward with switching community to SVN and using the official dbscripts for managing the repo. This way you guys can get your own testing repo too!

Sooo... the list, as I see it: * Decide on a date and time for the move * Get SSH keys from all TUs * Switch DNS over * Disable the AUR/community on gerolde

Anything I'm missing? Suggestions as to a good date?

I propose keeping the readline rebuild in testing until the AUR/community move is done. So we could do the community readline rebuild (http://bugs.archlinux.org/task/15165) in the new community-testing repo then move everything to core/extra/community once it's done.

I was thinking of a bit longer timeline for the SVN switchover. In my head I had: move machines sometime this week, do the svn transition next week. Is that too long?

 If we go this way, I suggest doing the move  very soon (this week or next week) as we want to complete the readline rebuild so we could start the massive libjpeg rebuild. The timing of the AUR/community move couldn't be better.

On Wed, Jun 24, 2009 at 11:58 PM, Daenyth Blank wrote:

On Wed, Jun 24, 2009 at 15:59, Aaron Griffin wrote:

...

...

...

Anything I'm missing? Suggestions as to a good date?

Sounds good to me. I don't have any requests for a specific date. Looking forward to the improvements :)

May i suggest something slightly relevant, but probably very radical? Disable comments on AUR completely. I dont think there is a question about its usefulness in [community], not even TU's themselves http://aur.archlinux.org/packages.php?ID=8737 http://bugs.archlinux.org/task/15126 or developers http://aur.archlinux.org/packages.php?ID=13315 http://bugs.archlinux.org/task/15127 bother making (formal) bug reports in the convinience of an (informal) comment. If someone wants to comment on a package he should use this mailing list. That will generate much more traffic here. -- Greg

On Wed, Jun 24, 2009 at 3:59 PM, Aaron Griffin wrote:

On Wed, Jun 24, 2009 at 2:18 PM, Eric Bélanger wrote:

...

On Wed, Jun 24, 2009 at 2:53 PM, Aaron Griffin wrote:

...

Hey all, This is part informational, and part not.

We have a donated server from SevenL networks that has sat mostly unused up until now. What we would like to do is more the AUR and community on to that machine, so that TUs can get real (limited) shell accounts and the people managing this side of the project get a bit more control.

As far as I know, things are almost ready to go, but what we need to do is setup a good time to "freeze" the AUR and community so we can switch over the DNS and change checkout locations.

Once this is complete, we can move forward with switching community to SVN and using the official dbscripts for managing the repo. This way you guys can get your own testing repo too!

Sooo... the list, as I see it: * Decide on a date and time for the move * Get SSH keys from all TUs * Switch DNS over * Disable the AUR/community on gerolde

Anything I'm missing? Suggestions as to a good date?

I propose keeping the readline rebuild in testing until the AUR/community move is done. So we could do the community readline rebuild (http://bugs.archlinux.org/task/15165) in the new community-testing repo then move everything to core/extra/community once it's done.

I was thinking of a bit longer timeline for the SVN switchover. In my head I had: move machines sometime this week, do the svn transition next week. Is that too long?

That's not too long IMO. The first mention of that readline rebuild was a few months ago. So it doesn't matter much if it stays in testing for another week or two.

...

 If we go this way, I suggest doing the move  very soon (this week or next week) as we want to complete the readline rebuild so we could start the massive libjpeg rebuild. The timing of the AUR/community move couldn't be better.

On Wed, Jun 24, 2009 at 11:22 PM, Pierre Schmitz wrote:

On Wednesday 24 June 2009 21:18:25 Eric Bélanger wrote:

...

I propose keeping the readline rebuild in testing until the AUR/community move is done.

I would prefer a strategy which wont block "our" repos. For example I have php waiting in testing and Allan mentioned a libjpeg rebuild.

There are only a few packages in community which need a readline rebuild. So what about moving the readline rebuild very soon (tomorrow), commit the needed rebuild for community and then freeze it.

During the community transition we have an "empty" testing to play with libjpeg and others.

--

Pierre Schmitz, http://users.archlinux.de/~pierrehttp://users.archlinux.de/%7Epierre

that seems fine. We should be able to do the readline rebuilds for community in notime with a few people, it are only a few packages. Having the community repo switched over sometime during the libjpeg rebuilds is more important as I imagine this will be a whole lot more packages. Ronald

On Wed, Jun 24, 2009 at 5:54 PM, Aaron Griffin wrote:

On Wed, Jun 24, 2009 at 4:22 PM, Pierre Schmitz wrote:

...

On Wednesday 24 June 2009 21:18:25 Eric Bélanger wrote:

...

I propose keeping the readline rebuild in testing until the AUR/community move is done.

I would prefer a strategy which wont block "our" repos. For example I have php waiting in testing and Allan mentioned a libjpeg rebuild.

There are only a few packages in community which need a readline rebuild. So what about moving the readline rebuild very soon (tomorrow), commit the needed rebuild for community and then freeze it.

During the community transition we have an "empty" testing to play with libjpeg and others.

Yeah. Considering that the libjpeg updates may be much larger, let's plan on having community-testing ready for that rebuild. How does that sound?

sounds good.

On Wed, Jun 24, 2009 at 7:38 PM, Allan McRae wrote:

Just noting that that libjpeg being large is wrong as far as community goes: 84 rebuilds in community for readline 31 rebuilds in community for libjpeg

Yeesh, I wasn't aware - I thought it was only around 20 packages or so

Eric Bélanger wrote:

On Wed, Jun 24, 2009 at 8:38 PM, Allan McRae wrote:

...

Aaron Griffin wrote:

...

On Wed, Jun 24, 2009 at 4:22 PM, Pierre Schmitz wrote:

...

On Wednesday 24 June 2009 21:18:25 Eric Bélanger wrote:

...

I propose keeping the readline rebuild in testing until the AUR/community move is done.

I would prefer a strategy which wont block "our" repos. For example I have php waiting in testing and Allan mentioned a libjpeg rebuild.

There are only a few packages in community which need a readline rebuild. So what about moving the readline rebuild very soon (tomorrow), commit the needed rebuild for community and then freeze it.

During the community transition we have an "empty" testing to play with libjpeg and others.

Yeah. Considering that the libjpeg updates may be much larger, let's plan on having community-testing ready for that rebuild. How does that sound?

Just noting that that libjpeg being large is wrong as far as community goes: 84 rebuilds in community for readline 31 rebuilds in community for libjpeg

Are you sure about that? From a quick glance at the bug reports, it seems to be the opposite: http://bugs.archlinux.org/task/15165 http://bugs.archlinux.org/task/15222

Haha, I suck! Never deal with emails first thing in the morning... Allan