Lars Wirzenius [EMAIL PROTECTED] writes:
I'm running piuparts, my package installation, upgrading, and removal
tester, against etch. It takes a while, and produces a fairly large
number of error logs that need to be investigated manually. This
sometimes reveals a bug in piuparts, and sometimes
[Lars Wirzenius]
The way I'm running it now, it installs and purges each package
(plus dependencies), and then compares the state of the filesystem
(the chroot) before and after and reports files that have been
modified, removed, or created.
Can you do upgrade testing as well. It would be
In article [EMAIL PROTECTED] you wrote:
Is this acceptable to everyone? Suggestions on how to do this better?
This would be real great QA work, would you mind to also send a final or
intermediate report with the most common errors you encountered. In my
experience somebody who audits a
* Petter Reinholdtsen
Can you do upgrade testing as well. It would be great to know what
packages fail to upgrade properly from woody to sarge, and from sarge
to etch.
Indeed. And if you can, Lars, please include a test to see which
packages which modify their own conffiles so the user
pe, 2005-07-22 kello 09:38 +0200, Petter Reinholdtsen kirjoitti:
[Lars Wirzenius]
The way I'm running it now, it installs and purges each package
(plus dependencies), and then compares the state of the filesystem
(the chroot) before and after and reports files that have been
modified,
Lars Wirzenius wrote:
The way I'm running it now, it installs and purges each package (plus
dependencies), and then compares the state of the filesystem (the
chroot) before and after and reports files that have been modified,
removed, or created. Quite simplistic, really, but good enough to
pe, 2005-07-22 kello 13:19 +0200, Helmut Wollmersdorfer kirjoitti:
Lars Wirzenius wrote:
The way I'm running it now, it installs and purges each package (plus
dependencies), and then compares the state of the filesystem (the
chroot) before and after and reports files that have been
I'm running piuparts, my package installation, upgrading, and removal
tester, against etch. It takes a while, and produces a fairly large
number of error logs that need to be investigated manually. This
sometimes reveals a bug in piuparts, and sometimes in the package, or a
depency of the package.
On Thu, Jul 21, 2005 at 03:41:10PM +0300, Lars Wirzenius wrote:
I'm running piuparts, my package installation, upgrading, and removal
tester, against etch. It takes a while, and produces a fairly large
number of error logs that need to be investigated manually. This
sometimes reveals a bug in
Lars Wirzenius writes:
Is this acceptable to everyone?
It's fine with me.
--
John Hasler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Thu, Jul 21, 2005 at 03:41:10PM +0300, Lars Wirzenius wrote:
Is this acceptable to everyone? Suggestions on how to do this better?
Any possibility of producing a nice web report on a per package basis?
It could be useful to re-run periodically and your tester could
probably have the same
Francesco P. Lovergine writes:
Any possibility of producing a nice web report on a per package basis?
...
Filling BTS reports could be not so appropriate.
I'd prefer bug reports.
--
John Hasler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
On Thursday 21 July 2005 14.41, Lars Wirzenius wrote:
[piuparts]
Go ahead - if you, as you say, investigate the bugs manually, it doesn't
matter how you discovered the bug.
Just curious: what kind of bugs can piuparts help discover?
cheers
-- vbi
--
The jig's up, Elman.
to, 2005-07-21 kello 16:44 +0200, Francesco P. Lovergine kirjoitti:
On Thu, Jul 21, 2005 at 03:41:10PM +0300, Lars Wirzenius wrote:
Is this acceptable to everyone? Suggestions on how to do this better?
Any possibility of producing a nice web report on a per package basis?
It could be
to, 2005-07-21 kello 21:11 +0200, Adrian von Bidder kirjoitti:
On Thursday 21 July 2005 14.41, Lars Wirzenius wrote:
[piuparts]
Go ahead - if you, as you say, investigate the bugs manually, it doesn't
matter how you discovered the bug.
Just curious: what kind of bugs can piuparts help
On Thu, Jul 21, 2005 at 03:41:10PM +0300, Lars Wirzenius wrote:
Is this acceptable to everyone? Suggestions on how to do this better?
Hi Lars,
by all means, proceed! Who say FLOSS lacks 'innovation'! Debian devs
seem to comeup with good ideas all the time! Also, have you determined
if any
16 matches
Mail list logo
