> Hmm. I did not get the memo.
>
> My test run a day ago with test 3.5.12 tarballs went okay. I did not try
> to build all files but just a few.
>
> Today I tried and the build scripts kept failing.
>
> First thing I finally discover is the file compression is tar.gz and not
> tar.bz2. When did that change?

It didn't; they were always tar.gz when I created them.  bzip would take
overnight to run; as it is gzip takes many hours.  To me, the difference
in compressed file size was not great enough to justify the performance
hit from bzip.

>
> Second, the non-core packages all have "3.5.12" in the source tarball file
> name. Previously those packages used a local version.
>
> arts: 1.5.10
> koffice: 1.6.3
> k3b: 1.0.5
> etc.
>
> Now all of them are 3.5.12.

That is normal and will stay that way for all future releases, unless
there is a good reason for not doing things this way.

>
> Third, when the non-core tarballs unpack, they are in a subdirectory
> rather than just under the package name. For example, both tqtinterface
> and arts unpack to a parent directory named dependencies. Koffice, knemo,
> k3b, etc all unpack to a parent directory named applications. Yes, that
> matches SVN, but the tarballs don't need to match SVN. Downstream builders
> will not be expecting that. They will expect the unpacked tarball to be in
> its own directory of the same name.

This issue I can definitely fix.

Tim