Re: debian-testing and upgrade-reports bugs

[Bill Allombert <allomber@math.u-bordeaux.fr>]

On Sat, Jun 25, 2005 at 01:37:48PM +0200, Andreas Barth wrote:
> * Bill Allombert (allomber@math.u-bordeaux.fr) [050624 18:51]:
> > On Thu, Jun 16, 2005 at 10:12:39PM +0200, Cord Beermann wrote:
> > Haha. According to the documentation about submitting upgrade report,
> > it is likely to be a lot, see
> > 
> >   <http://release.debian.org/upgrade-report.html>
> >   
> >   Please attach the output of "COLUMNS=200 dpkg -l" (or "env COLUMNS ...",
> >   depending on your shell) from before and after the upgrade so that we
> >   know what packages were installed on your system.
> > 
> > On my system this is 255430 bytes by itself, but I do not have much
> > packages installed, and sarge+etch is going to be larger than 
> > woody+sarge, so probably we need to raise the limit to 500kb. 
> > 
> > Alternatively, we could the above to
> > 
> >   Please attach the output of "COLUMNS=200 dpkg -l" (or "env COLUMNS ...",
> >   depending on your shell) from before the upgrade so that we know what
> >   packages were installed on your system.
> > 
> > and raise the limit to 300kb. So far I never needed the dpkg -l output 
> > after the upgrade.
> > 
> > Opinion, Andreas ? Also it would be better if submitters avoid to
> > use inline attachment for that. This make upgrade-report buglog
> > painful to proceed.
> 
> I don't have any real opinion on it. Perhaps discuss it on debin-release.
> And as always, if nobody disagrees enough, just do it. :)

Well I cannot change the upgrade-report template, and that should rather
be discussed on debian-testing since this list is in charge of the 
upgrade-report bugs.

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large red swirl here.