linaro-release team mailing list archive

[Loïc Minier <lool@xxxxxxxx>]

On Wed, Nov 16, 2011, Fathi Boudra wrote:
> >  - re-add the debian/changelog entries from the Ubuntu package you
> >   copied over
> There's no reason to do that. We have a different packaging for the
> PPA and Debian/Ubuntu Oneiric/Precise.
> The latter packages were re-done from scratch.
> 
> >  - consider changing Vcs-Bzr: lp:ubuntu/linaro-image-tools unless that's
> >   truly where the current *Debian* packaging is kept?
> It's considered but as mentioned, we have 2 different packaging.
> For PPA, where we should keep lucid running and have a packaging to
> easy the backport.
> For current distro, using dh_python2.
> We need 2 branches and "current" packaging isn't kept anywhere atm

 Why couldn't we use the most backwards-compatible packaging all across
 the board instead of having two?

 debian/changelog > I don't care enough, but the current oneiric/precise
 packages seem to have some bits from the older packaging; I'd preferred
 if this was clear from the changelog, e.g. with a changelog entry that
 this or that part of the packaging had been rewritten, dropping the
 testuite.  Anyway, not a big deal.

-- 
Loïc Minier

-- 
You received this bug notification because you are a member of linaro-
infrastructure-drivers, which is the registrant for Linaro Image Tools.
https://bugs.launchpad.net/bugs/888555

Title:
  Set up l-i-t testing on multiple archs and releases

Status in Linaro Image Tools:
  Triaged

Bug description:
  We need to test l-i-t on all supported releases and architectures. We
  have seen a number of cases where new features are later found to not
  work on old releases or older versions of Python. We just had a
  problem with linaro-hwpack create not working on Oneiric 64 bit, but
  happily work on 32 bit.

  For testing new code and especially for release testing we would need
  to set something up to enable this since a single developer won't have
  access to all variants of installations.

  We could perhaps automate something to set up virtual machines on
  local dev PC:s with possible impact on TDD since tests would take many
  times longer to run. Perhaps we can use LAVA?

  For full coverage we'd need to test on all possible combinations of
  the below components (please add to them as you see fit), but that is
  probably overkill.

  Python:
      2.6
      2.7

  Ubuntu:
      Precise
      Oneiric
      Natty
      Maverick
      (how far back do we want to ensure support?)

  Archs:
      i386
      x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/linaro-image-tools/+bug/888555/+subscriptions