On Wed, August 10, 2011 11:15, Colin Watson wrote:
On Tue, Aug 09, 2011 at 07:44:38AM +0200, Christian PERRIER wrote:
I, for one, would vote for uploading to unstable. It is time to test
*now*. Closer to wheezy release might be too laste.
Agreed, just go for unstable and (obviously) be
On Tue, Aug 09, 2011 at 07:44:38AM +0200, Christian PERRIER wrote:
I, for one, would vote for uploading to unstable. It is time to test
*now*. Closer to wheezy release might be too laste.
Agreed, just go for unstable and (obviously) be responsive in case of
breakage. If you think the changes
On Wed, August 10, 2011 11:15, Colin Watson wrote:
On Tue, Aug 09, 2011 at 07:44:38AM +0200, Christian PERRIER wrote:
I, for one, would vote for uploading to unstable. It is time to test
*now*. Closer to wheezy release might be too laste.
Agreed, just go for unstable and (obviously) be
Good morning,
On Tue, August 9, 2011 06:44, Christian PERRIER wrote:
Quoting Regis Boudin (re...@boudin.name):
Hi folks,
I think I've pushed a fair number of patched to cdebconf already, and it
is time to call for testing.
The latest changes involve making cdebconf take changes to
On Tue, Aug 9, 2011 at 07:44, Christian PERRIER bubu...@debian.org wrote:
...
I, for one, would vote for uploading to unstable. It is time to test
*now*. Closer to wheezy release might be too laste.
Wait for Joey, Colin, Otavio's input about all this before proceesing,
though.
I am with
Hi folks,
I think I've pushed a fair number of patched to cdebconf already, and it
is time to call for testing.
The latest changes involve making cdebconf take changes to
debconf/priority, debconf/language, and debconf/frontend on calls to
INPUT/GO as well as SET, and reworking frontend_new() to
Quoting Regis Boudin (re...@boudin.name):
Hi folks,
I think I've pushed a fair number of patched to cdebconf already, and it
is time to call for testing.
The latest changes involve making cdebconf take changes to
debconf/priority, debconf/language, and debconf/frontend on calls to
[Martin Sjögren]
Why would you need max in the progress set command if you've got min
and max in progress start (okay I didn't write that, but I meant it)
Could you document the current and proposed protocol and API in
d-i/docs/ somewhere?
Hrrm, maybe. It could be tricky frontend-ish... In
Well, after discussing with aj for a while, he had the following
comment about the cdebconf progress bar API:
it sucks
;-)
Myself, I am of the opinion that it was a bad idea not to look at what
debootstrap and b-f use, when designing the API.
Short summary:
cdebconf progress bars:
progress
On Wed, Mar 05, 2003 at 07:40:32PM +0100, Martin Sjögren wrote:
[...]
progress start (can still use this one, and it makes sense)
progress step inc (or progress set val)
progress info info
progress stop
[...]
The max value is missing:
progress set val max
The 'set' method is IMO more
ons 2003-03-05 klockan 22.35 skrev Denis Barbier:
On Wed, Mar 05, 2003 at 07:40:32PM +0100, Martin Sjögren wrote:
[...]
progress start (can still use this one, and it makes sense)
progress step inc (or progress set val)
progress info info
progress stop
[...]
The max value is
]
To: Debian Bug Tracking System [EMAIL PROTECTED]
Subject: cdebconf: progress stuff isn't available in shell-scripts
X-Mailer: reportbug 2.10
Date: Sat, 15 Feb 2003 10:38:41 +0100
Message-Id: [EMAIL PROTECTED]
Sender: Thorsten Sauter [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status
On Thu, Dec 26, 2002 at 03:06:21AM +0100, Thorsten Sauter wrote:
Hi all,
I'm searching for a way to realise a progressbar with cdebconf.
After a little bit reading of the retriever and cdebconf code, I think
there should something exist to deal with this problem. But I haven't
found any
Hi all,
I'm searching for a way to realise a progressbar with cdebconf.
After a little bit reading of the retriever and cdebconf code, I think
there should something exist to deal with this problem. But I haven't
found any further documentation for progress templates or how can I set
the values
14 matches
Mail list logo
