[arch-dev-public] Repository cleanup [current] and [base] --> [core] , this weekend!

[Travis Willard]

On Thu, 13 Sep 2007 10:14:46 +0300
"Roman Kyrylych" <roman.kyrylych at gmail.com> wrote:

> 2007/9/13, Tobias Powalowski <t.powa at gmx.de>:
> > Am Mittwoch 12 September 2007 schrieb Jason Chu:
> > > On Wed, Sep 12, 2007 at 04:42:51PM -0500, Aaron Griffin wrote:
> > > > On 9/12/07, Tobias Powalowski <t.powa at gmx.de> wrote:
> > > > > Im pretty sure Jan(is a little bit busy) and me will be there too
> > > >
> > > > I don't have plans this weekend, but of course, I'm on a different
> > > > schedule than the germans.
> > >
> > > Ze Germans!
> > >
> > > > I'm sure I can do some of the work, just let me know what time you
> > > > plan on starting, and I can figure out what works best for me.
> > > >
> > > > I think tpowa is on the right track here - even if we don't get
> > > > everything, we don't cover 100% of the packages, we can get MOST of
> > > > it. We may forget one or two - big deal, we can add them later.
> > > >
> > > > Thanks for picking this up again, this is one of the (many) important
> > > > infrastructure things that have gone by the wayside.
> > >
> > > I'm still worried about the three different versions of the packages.  Can
> > > someone give me some numbers about untagged changes or differences between
> > > arch64 and arch32?
> > >
> > > Jason
> >
> > http://archlinux.org/~andyrtr/pkg_diff.html
> > i would say the red ones could be troublemakers
> > the rest should be fine
> 
> There should be some untagged packages with done bugfixes in them.
> In any case we shouldn't lose those untagged changes, as it will be a
> PITA to find and fix them later again.
> Doesn't CVS has some possibility to move untagged changes?
> 

If one of the packages we're moving has untagged changes, then why don't we use this move to tag the newest version, build, and upload it?  Problem solved?

Is anything we're moving in TESTING currently?  'Cause there's another tag we have to deal with.

--
Travis