On Fri, Mar 02, 2012 at 06:36:29PM +0200, Sergey Poznyakoff wrote:
> It's downright impossible. Version 3.x differs drastically from 2.x,
> that's why it is assigned a new major number.

I figured this, but had to try, in case the bugfix wasn't lowlevel. :)

> > The alternative is to bite the bullet and start working on my promised
> > experimental 3.0 packages.
> That's what I'd urge you to do!

I'm on it! I have packages built, that fail at the testsuite. As soon as
you upload 2.99.6, I'll try again with that.

> > However, since the last 3.0pre release, I've
> > seen a number of big changes, some of which appeared to be interface
> > changes.
> None of them is critical.  The only reason why 3.0 is not yet released
> is that I'd hate to make a release with such a *defective* documentation
> as we have now.  However, given my sky-rocketed load average, I suppose
> I'd finally cease and release it, with at least minor improvements in
> the docs.  (Not willing to divulge anything, I'd only say that I'm going
> to release two GNU packages this weekend ...)

Interesting. My random bet is radius and tar!

Thanks, again, for the texinfo docs license change. 3.0 in Debian will
again have a info manual, even if its defective. :)

> Generally speaking, I do not expect any major change in the
> API. At most some minor bugfixes, but I don't expect many of these.
> I've got plenty of major changes in my mind indeed, and there *will be*
> a lot of major changes after 3.0, but not before.

Ok.

> > OTOH, a new Debian architecture (s390x) has testsuite failures, but I
> > still don't have an idea if this same error is still present in the
> > current git master code:
> > https://buildd.debian.org/status/fetch.php?pkg=mailutils&arch=s390x&ver=1%3A2.2%2Bdfsg1-5&stamp=1330644291
> 
> It's been more than a year ago, so it's hard to tell.  Since then a lot
> of things has changed.  In particular, I've succeeded in getting rid
> of DejaGNU as the testing framework, since it was too cumbersome to
> use.  It still persists for interactive utilities, such as mail (given
> no feasible alternative), but again, given the amount of changes and
> insufficient information in this log, I cannot say anything definite...
> Can you try this with the recent snapshot?

I've had a few problems trying to make dist from current git, so I'd be
glad if I could use an official tarball. Once I have something built and
uploaded to experimental, it'll get compiled in a gazillion architectures
(for values of gazillion near to 14) and we'll be able to find out how the
new release is doing in more exotic environments.

Jordi
-- 
Jordi Mallach Pérez  --  Debian developer     http://www.debian.org/
[email protected]     [email protected]     http://www.sindominio.net/
GnuPG public key information available at http://oskuro.net/

_______________________________________________
Bug-mailutils mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-mailutils

Reply via email to