Lucas Nussbaum writes ("Re: package testing, autopkgtest, and all that"):
> If there's a packaged tool to run the test suite on a given package,
> then it's quite easy to integrate it into my infrastructure. But I
> clearly do not have the time to get autopkgtest'
On 31/01/11 at 00:29 +0100, Stefano Zacchiroli wrote:
> The best incentive for adoption in this case is having periodic runs of
> package tests, with reporting. At first glance, I'm tempted to propose
> to use grid archive rebuilds to run tests. Lucas: how much work would it
> be to hack your rebui
Stefano Zacchiroli writes ("Re: package testing, autopkgtest, and all that"):
>
> I confess that this seems to be exactly one of those cases where the
> DEP process (should) shine. By putting the specification in a more
> visible place than (only) in an archive packa
On Thu, Jan 27, 2011 at 02:45:57PM +, Ian Jackson wrote:
> > Ian: would you mind summarizing the status of that effort and
> > comment on whether, in your opinion, people interested on this topic
> > should continue from there or start over?
>
> Sure. autopkgtest (the codebase) isn't very big
Hi,
> I was asking for an interface for automated package testing on
> #debian-mentors, but there does not seem to be such an interface. What I
> was thinking about would be some kind of script being invoked before a
> package is installed or upgraded, after it is upgraded or i
On la, 2007-06-16 at 18:14 +0200, Helmut Grohne wrote:
> (posting from outside, so please CC me)
ACK.
> I was asking for an interface for automated package testing on
> #debian-mentors, but there does not seem to be such an interface. What I
> was thinking about would be some ki
Hi,
(posting from outside, so please CC me)
I was asking for an interface for automated package testing on
#debian-mentors, but there does not seem to be such an interface. What I
was thinking about would be some kind of script being invoked before a
package is installed or upgraded, after it is
7 matches
Mail list logo
