[Piuparts-devel] remaining updates targeting for jessie

[Holger Levsen]

Hi Andreas,

On Montag, 1. Dezember 2014, Andreas Beckmann wrote:
> On 2014-11-30 23:43, Holger Levsen wrote:
> > So keep testing=jessie for now, upload 0.61 tomorrow and then upload 0.62
> > with testing=stretch real short before the release eventually. (and use
> > develop on piu.d.o..)
> 
> No, throw out the alias *now* in the next upload targeting jessie, it's
> harmless if it's not there (since [testing] will get sane defaults that
> are always correct). It's only needed for testing2sid tests that are to
> reuse a tarball (no, symlinks are *not* a solution) (can I create a
> proper base tarball from an distupgrade test?), and there are probably
> less than log log n people running these in master-slave setups.
> It *is* harmful if it is wrong and someone uses piuparts -d testing.

so wouldnt the solution be simple to recommend using -d $codename (so 
jessie/stretch) instead of testing?

> For the benefit of p.d.o it should always be enabled in git. And there
> we hopefully remember to change it in time - along with adding new tests
> right after the release.
> 
> 
> Andreas
> 
> PS: tarball generation needs to be overhauled, I have some ideas,
> probably adding tarball/$RELEASE(/$ARCH) sections to p.conf that are not
> used to run any tests at all - not implemented, would not have been
> freeze material

*nods*

> I recently added locally a jessie-i386-nodocs test - now, where do I get
> a proper jessie_i386.tar.gz?

debootstrap it?


cheers,
	Holger
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/piuparts-devel/attachments/20141201/f3078291/attachment-0001.sig>