Re: [Debian-sf-devel] Package is split! Testers wanted!

[Soon-Son Kwon]

I just upgraded my box from 2.6.11 to 2.6.11+.

If you are interested in testing 2.6.11+(the newest split version),
please visit http://dev.kldp.org and feel free to register
as a site user & test it on your own.
(Any data including your account information may
be deleted without notice because this is test server. :-) )

I was running 2.6.11 and built all the packages from CVS
and ran "dpkg -i sourceforge*.deb".
(I had to install sourceforge-common*.deb package first
because all the other packages were dependent on it.)

The upgrade itself seemed to be smooth and I didn't get any error.

I will test it from now on and will submit bug report on savannh
if I encounter any.

Thanks very much...



On Sat, May 25, 2002 at 12:37:59PM +0900, Soon-Son Kwon wrote:
> This was one of the most exciting news for me!
> 
> Thanks Roland & I will let you know the test result sooner or later.
> 
> I don't know when you will release 2.6.12 but if you can wait
> for me to work more on i18n, I will do that for this weekend
> to make it more multilingual...
> 
> Thanks again & let's prepare bug-hunting season! :-)
> 
> Have a nice weekend...
> 
> 
> On Fri, May 24, 2002 at 09:55:22PM +0200, Roland Mas wrote:
> > Roland Mas (2002-05-21 14:25:19 +0200) :
> > [...]
> > >   The way I see it is this: I'm currently splitting the package.  To
> > > be frank, the current state of my local checkout of the CVS
> > > repository is "utterly broken, don't even think of installing it, it
> > > won't install anyway".  That's why you probably won't see many CVS
> > > commits from me in the next few days.
> > 
> >   Well, I just did a rather large commit.  This means the package as
> > of the current CVS is split, hopefully nicely.  I have inserted a bit
> > of magic in the build process.  Namely, DSF-Helper.  This is basically
> > a Perl script to replace #DSFHELPER:blah# tags by contents of files in
> > the debian/dsf-helper/ directory.  The goal is to keep in one place
> > the code for functions used throughout the packages.
> > 
> > > On the other hand, the current package (as of what's in CVS) seems
> > > to install fairly dependably, and be mostly working.  The problem is
> > > we don't know exactly what this "mostly" covers.  Therefore, we need
> > > more testing, more reporting of problems, and more fixing of those
> > > problems.  Therefore, we need more visibility.
> > 
> >   It seems my last commit installed smoothly on at least two systems,
> > although these were installations from scratch (as opposed to upgrades
> > from a 2.5 or a pre-split 2.6 package).
> > 
> > > 0. I'm currently trying to "design" how the packages will behave
> > > after the split (my previous attempts were coded rather than
> > > designed, and the result didn't work.  When the design is done, I'll
> > > probably post it and ask for comments.
> > 
> >   Well, read debian/README.Maintainer, it's in there.  It's not *all*
> > in there, but most of the important stuff is.  I'll try to add more
> > text to document how I think variants should be done (like,
> > sourceforge-db-remote, for instance).
> > 
> > > 1. I get to the point of making the sourceforge-* installable in
> > > some cases (preferably most cases, but maybe not);
> > 
> >   Done.  dpkg -i sourceforge*deb worked on both my test server and
> > Christian's.  Now it's your turn to try it out and give us your results.
> > 
> > > 2. We upload to experimental with a big "This doesn't work.  If it
> > > does, please tell us." warning.  We announce it here, on the
> > > Savannah webpage, on the debian-devel mailing list, everywhere.
> > 
> >   That's still a few days/weeks from now.
> > 
> > > 3. We collect lots and lots of bug reports.  We fix them.  When no
> > > more appear for a reasonable amount of time, we upload to unstable.
> > 
> >   The "collect bug reports" part can start now.  We'll probably upload
> > a 2.6-0+12 pre-release sometime, in the meantime feel free to make
> > your own package from CVS.
> > 
> > >   During all this period, we fix any grave bugs in the 2.5 series,
> > > if only as a recreation from the nightmare that is the split.  I
> > > think it will be necessary to upload a 2.5-30 sometime anyway, but I
> > > definitely expect 2.5 to be frozen.  No patches providing new
> > > features against 2.5 please, only bugfixes.
> > 
> >   I already fixed two bugs in 2.5 (one was on the Debian BTS, the
> > other wasn't but prevented the mailing-lists from working).
> > 
> >   Now for the interesting part: go on, test, crash-test, try to
> > install on previous versions, re-install, whatever.  Report
> > everything, be it success (preferably on this list) or failure (on the
> > Savannah BTS, but try to include the relevant information).  Work is
> > happening!  Be a part of it, or hold your peace for a few weeks ;-)
> > 
> > Roland.
> > -- 
> > Roland Mas
> > 
> > La tradition orale, c'est comme un vieux fromage [...] -- Le Blaire
> >   -- Signatures � collectionner, s�rie n�2, partie 1/3.
> > 
> > _______________________________________________
> > Debian-sf-devel mailing list
> > address@hidden
> > http://mail.freesoftware.fsf.org/mailman/listinfo/debian-sf-devel
> 
> -- 
> -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
>            (o_             **WTFM**
> (o_  (o_   //\
> (/)_ (/)_  V_/_        http://kldp.org
> -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*     
> 
> _______________________________________________
> Debian-sf-devel mailing list
> address@hidden
> http://mail.freesoftware.fsf.org/mailman/listinfo/debian-sf-devel

-- 
-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
           (o_             **WTFM**
(o_  (o_   //\
(/)_ (/)_  V_/_        http://kldp.org
-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*