[Aptitude-devel] Simple and direct question: Should we go ahead with a new release?

Daniel Hartwig mandyke at gmail.com
Tue Jan 31 06:04:54 UTC 2012

On 31 January 2012 06:17, Axel Beckert <abe at debian.org> wrote:
> Hi,
> Manuel A. Fernandez Montecelo wrote:
>> 2012/1/29 Christian PERRIER <bubulle at debian.org>:
>> > And, to answer Axel's question, the new release should be an upstream
>> > 0.6.5 release.
>> >
>> > I even wonder whether it should be 0.7 to reflect the change in maintenance.
>> >
>> > Of course, there are indeed no drastic changes in the code, so a
>> > "minor" release numer is also appropriate.
>> I think that 0.7 might be appropriate for this reason, too.
> I don't think that a 0.7 version number can be justified just with a
> maintainer change and a bunch of bug fixes. (But I wont' cry if you do
> it nevertheless. :-)

I agree.  A bump to 0.7 indicates changes more substantial than those
currently made.

>> Also, I guess that we should target experimental first for a few weeks?

Disagree with this.  Keep in mind these are primarily bug fixes and
translation updates, hardly justifying the use of experimental.  I
have kept an eye on the changes being committed and don't foresee any
major issues.  An upload to unstable is fine IMO.


There are no build issues (using sid, i386) on the current master
branch and, after "make dist && git-import-orig ...", the debian
branch builds fine also.

A couple of issues to resolve before releasing:

1. "make dist" currently fails trying to copy the gmock source files:

 (cd tests && make  top_distdir=../aptitude-0.6.4
distdir=../aptitude-0.6.4/tests \
     am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=: distdir)
make[1]: Entering directory
cp: cannot stat `.//usr/src/gmock/src/gmock-all.cc': No such file or directory
make[1]: *** [distdir] Error 1
make[1]: Leaving directory `/home/daniel/src/debian/aptitude/build-curses/tests'
make: *** [distdir] Error 1

These files (/usr/src/gmock/*) should probably be excluded from the
.tar.gz and the user expected to install them separately.

This currently prevents making a release, as "make dist" is (almost)
essential to the process.

2. Translation updates

It is great to see updates to a dozen or so translations, some quite major.

There have been some commits that slightly changed some strings.  An
example of this is 28ebd48 which adds missing newlines and full stops
to `aptitude --help`.  This is going to make the translations of those
strings fuzzy.

Given that it is only minor formatting and punctuation changes
involved it is easy for myself or someone else to update the concerned

I will look at both of these in the next 24 h and we should have
aptitude suitable for release after that.

More information about the Aptitude-devel mailing list