Re: cdebconf progress
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 responsive in case of breakage. If you think the changes are sound, then there's no need to be excessively timid at this point in the release cycle. Well, uploaded last night, if it breaks something I missed, please shout. At this point, if you set DEBCONF_USE_CDEBONF=1, dpkg, dpkg-reconfigure, and dpkg-preconfigure will use cdebconf. I had an issue last night with a bacula postinst script, so everything is not perfect yet, but I didn't have time to investigate further. I started pushing a couple more patches, mostly related to a potential move GTK3. I'm not actually porting to GTK3, only removing the use of deprecated symbols, using GSeal, etc. Trivial changes, really. As usual, any feedback/comment more than welcome. Regis -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/0a562d372b0e3e92cb9d46d900e99861.squir...@imalip.net
Re: cdebconf progress
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 responsive in case of > breakage. If you think the changes are sound, then there's no need to > be excessively timid at this point in the release cycle. Guess I'll do that this evening, then. I fixed a bug yesterday evening that had broken the none and noninteractive frontend ; but other than that everything should be ok. I've actually been using it on my laptop for a few weeks. Regis -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/bd32f7e585e66696754bf34ac41bbd7e.squir...@imalip.net
Re: cdebconf progress
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 are sound, then there's no need to be excessively timid at this point in the release cycle. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110810101504.gb18...@riva.dynamic.greenend.org.uk
Re: cdebconf progress
On Tue, Aug 9, 2011 at 07:44, 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. > > Wait for Joey, Colin, Otavio's input about all this before proceesing, > though. I am with Christian on that; please upload it to sid. > PS: great job, Régis, anyway. I can't understand your changesbut I bet > they are those who will put us on the way to have cdebconf ready to > really replace debconf. Reminds me that I worked to have all > debconf-depending packages to depend on "debconf | > debconf-2.0"before the releaseof lenny! +1 :-D -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cap9odkroqk4kxfcpi88vscwbkpavswvmjomwkcgmenk0n2t...@mail.gmail.com
Re: cdebconf progress
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 >> debconf/priority, debconf/language, and debconf/frontend on calls to >> INPUT/GO as well as SET, and reworking frontend_new() to fall back to >> the next preferred option if loading one fails. >> >> It means cdebconf can load the current debconf.templates without >> crashing, and change frontend while running (although shutting down the >> gtk one seems to have some problem). >> >> I would be quite keen to make an upload, maybe to experimental to make >> sure I haven't broken anything for d-i. > > To experimental will not really expose the package except to those > people who want to replace debconf by cdebconf on real systems. > > Even for those, uploading to unstable would indeed give the same > exposure and, on the other hand, would really expose your changes to > D-I testing as all daily builds would then have the new cdebconf. > > I, for one, would vote for uploading to unstable. It is time to test > *now*. Closer to wheezy release might be too laste. Of course I would prefer to upload it to unstable, I just would like to test that I didn't break anything in d-i before that. I'm worried if I got something wrong I might make all daily builds unusable, which I would very much like to avoid. > Wait for Joey, Colin, Otavio's input about all this before proceesing, > though. Definitely. > PS: great job, Régis, anyway. I can't understand your changes They are not all that exciting, to be honnest. It does help me find some hidden bugs, though. > but I bet > they are those who will put us on the way to have cdebconf ready to > really replace debconf. Reminds me that I worked to have all > debconf-depending packages to depend on "debconf | > debconf-2.0"before the releaseof lenny! Well, I would like to think I'm on track to get cdebconf ready as a debconf replacement for wheezy. I'm already using it on my laptop. Thanks for the support :) Regis -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/3e245435033e2509f910cf8e24294ce6.squir...@imalip.net
Re: cdebconf progress
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 > INPUT/GO as well as SET, and reworking frontend_new() to fall back to > the next preferred option if loading one fails. > > It means cdebconf can load the current debconf.templates without > crashing, and change frontend while running (although shutting down the > gtk one seems to have some problem). > > I would be quite keen to make an upload, maybe to experimental to make > sure I haven't broken anything for d-i. To experimental will not really expose the package except to those people who want to replace debconf by cdebconf on real systems. Even for those, uploading to unstable would indeed give the same exposure and, on the other hand, would really expose your changes to D-I testing as all daily builds would then have the new cdebconf. 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. PS: great job, Régis, anyway. I can't understand your changesbut I bet they are those who will put us on the way to have cdebconf ready to really replace debconf. Reminds me that I worked to have all debconf-depending packages to depend on "debconf | debconf-2.0"before the releaseof lenny! signature.asc Description: Digital signature
cdebconf progress
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 fall back to the next preferred option if loading one fails. It means cdebconf can load the current debconf.templates without crashing, and change frontend while running (although shutting down the gtk one seems to have some problem). I would be quite keen to make an upload, maybe to experimental to make sure I haven't broken anything for d-i. Any opinion or comment ? Regis -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1312836646.11497.21.camel@x200s
Re: cdebconf progress bars and debootstrap
[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 the text frontend > for example. Not really. It can display many progress bars on the same line: [50%] Info 1 [70%] info 2 [20%] Info 3 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: cdebconf progress bars and debootstrap
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 (or progress set ) > > progress info > > progress stop > [...] > > The max value is missing: > progress set > The 'set' method is IMO more easily manageable, but you guys are using it, > so you know which one is better. 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) > I also asked whether several progress bars could be displayed > simultaneously. IIRC answer was yes, so adding a label may be > desirable: > progress start > progress set > progress info > progress stop Hrrm, maybe. It could be tricky frontend-ish... In the text frontend for example. /M signature.asc Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signeradmeddelandedel
Re: cdebconf progress bars and debootstrap
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 (or progress set ) > progress info > progress stop [...] The max value is missing: progress set The 'set' method is IMO more easily manageable, but you guys are using it, so you know which one is better. I also asked whether several progress bars could be displayed simultaneously. IIRC answer was yes, so adding a label may be desirable: progress start progress set progress info progress stop Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cdebconf progress bars and debootstrap
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 start progress step progress stop debootstrap: P: I: This is very incompatible, especially since the cdebconf way means that is added *after* the is displayed. I hacked around this in debootstrap to add a --debian-installer flag but aj thought it was much too horrible to include. I agree with him, though I wish he'd said it before I spent the hours doing this. Someone bloody well owes me a beer! ;) Thus, I suggest we change the API for cdebconf progress bar to match what b-f and debootstrap use. Something like: progress start (can still use this one, and it makes sense) progress step (or progress set ) progress info progress stop This means that when we (i.e. Thorsten in cdrom-checker and I in anna) used progress step 1 some/template we should instead use progress info some/template progress inc 1 which is much more compatible with debootstrap and it still makes sense. Comments? tausq? /M signature.asc Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signeradmeddelandedel
Bug#181083: marked as done (cdebconf: progress stuff isn't available in shell-scripts)
Your message dated Fri, 21 Feb 2003 18:32:10 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#181083: fixed in cdebconf 0.31 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 15 Feb 2003 09:37:20 + >From [EMAIL PROTECTED] Sat Feb 15 03:37:20 2003 Return-path: <[EMAIL PROTECTED]> Received: from pop.gmx.net (mail.gmx.net) [213.165.65.60] by master.debian.org with smtp (Exim 3.12 1 (Debian)) id 18jyl5-0002i3-00; Sat, 15 Feb 2003 03:37:19 -0600 Received: (qmail 30496 invoked by uid 0); 15 Feb 2003 09:36:47 - Received: from pD951800A.dip.t-dialin.net (HELO jacky.resix.de) (217.81.128.10) by mail.gmx.net (mp002-rz3) with SMTP; 15 Feb 2003 09:36:47 - Received: from sar by jacky.resix.de with local (Exim 3.36 #1 (Debian)) id 18jymP-RA-00; Sat, 15 Feb 2003 10:38:41 +0100 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Thorsten Sauter <[EMAIL PROTECTED]> 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: No, hits=-1.1 required=4.0 tests=HAS_PACKAGE,PATCH_UNIFIED_DIFF,SPAM_PHRASE_02_03 version=2.44 X-Spam-Level: Package: cdebconf Version: 0.31 (not installed) Severity: normal cddebconf currently doesn't support db_progress in shell-scripts. src/client/confmodule doesn't contain anything for progressbars. The following patch maywork: --- confmodule-orig 2003-02-15 10:36:42.0 +0100 +++ confmodule 2003-02-15 10:37:32.0 +0100 @@ -40,7 +40,9 @@ "input INPUT" "beginblock BEGINBLOCK" "endblock ENDBLOCK" "go GO" \ "get GET" "register REGISTER" "unregister UNREGISTER" "subst SUBST" \ "previous_module PREVIOUS_MODULE" "fset FSET" "fget FGET" \ -"purge PURGE" "metaget METAGET" "version VERSION" "clear CLEAR"; do +"purge PURGE" "metaget METAGET" "version VERSION" "clear CLEAR" \ +"progress_start PROGRESS START" "progress_stop PROGRESS STOP" \ +"progress_step PROGRESS STEP"; do # Break string up into words. set -- $i # Generate function on the fly. Please include it, because cdrom-checker, needs the progressbar to indicate the current progress. Thanks for your help Thorsten -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux jacky 2.4.18sar #2 SMP Don Aug 22 17:58:16 CEST 2002 i686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] --- Received: (at 181083-close) by bugs.debian.org; 21 Feb 2003 23:38:24 + >From [EMAIL PROTECTED] Fri Feb 21 17:38:23 2003 Return-path: <[EMAIL PROTECTED]> Received: from auric.debian.org [206.246.226.45] (mail) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 18mMkJ-0004ar-00; Fri, 21 Feb 2003 17:38:23 -0600 Received: from katie by auric.debian.org with local (Exim 3.35 1 (Debian)) id 18mMeI-0007pn-00; Fri, 21 Feb 2003 18:32:10 -0500 From: Martin Sjogren <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: $Revision: 1.32 $ Subject: Bug#181083: fixed in cdebconf 0.31 Message-Id: <[EMAIL PROTECTED]> Sender: Archive Administrator <[EMAIL PROTECTED]> Date: Fri, 21 Feb 2003 18:32:10 -0500 Delivered-To: [EMAIL PROTECTED] We believe that the bug you reported is fixed in the latest version of cdebconf, which is due to be installed in the Debian FTP archive: cdebconf-slang-udeb_0.31_i386.udeb to pool/main/c/cdebconf/cdebconf-slang-udeb_0.31_i386.udeb cdebconf-udeb_0.31_i386.udeb to pool/main/c/cdebconf/cdebconf-udeb_0.31_i386.udeb cdebconf_0.31.dsc to pool/main/c/cdebconf/cdebconf_0.31.dsc cdebconf_0.31.tar.gz to pool/main/c/cdebconf/cdebconf_0.31.tar.gz cdebconf_0.31_i386.deb to pool/main/c/cdebconf/cdebconf_0.31_i386.deb libdebconf1-dev_0.31_i386.deb to pool/main/c/cdebconf/libdebconf1-dev_0.31_i386.deb libdebconf1_0.31_i386.deb to pool/main/c/cdebconf/libdebconf1_
Bug#181083: cdebconf: progress stuff isn't available in shell-scripts
Package: cdebconf Version: 0.31 (not installed) Severity: normal cddebconf currently doesn't support db_progress in shell-scripts. src/client/confmodule doesn't contain anything for progressbars. The following patch maywork: --- confmodule-orig 2003-02-15 10:36:42.0 +0100 +++ confmodule 2003-02-15 10:37:32.0 +0100 @@ -40,7 +40,9 @@ "input INPUT" "beginblock BEGINBLOCK" "endblock ENDBLOCK" "go GO" \ "get GET" "register REGISTER" "unregister UNREGISTER" "subst SUBST" \ "previous_module PREVIOUS_MODULE" "fset FSET" "fget FGET" \ -"purge PURGE" "metaget METAGET" "version VERSION" "clear CLEAR"; do +"purge PURGE" "metaget METAGET" "version VERSION" "clear CLEAR" \ +"progress_start PROGRESS START" "progress_stop PROGRESS STOP" \ +"progress_step PROGRESS STEP"; do # Break string up into words. set -- $i # Generate function on the fly. Please include it, because cdrom-checker, needs the progressbar to indicate the current progress. Thanks for your help Thorsten -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux jacky 2.4.18sar #2 SMP Don Aug 22 17:58:16 CEST 2002 i686 Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: cdebconf progress module
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 further documentation for progress templates or how can I set > the values (progress_start, progress_end, ...). [...] Hi, an exemple is cdebconf/src/test/progress.config But this progress bar stuff has been implemnented only with the text frontend, and its interface will hopefully change soon (strings cannot be easily localized if they appear in config/postinst scripts). Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cdebconf progress module
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 (progress_start, progress_end, ...). So, should I create a template with typ progress and put the placeholders for the values in the description field? And then set the values via "db_subst xxx/myprogress progress_value 5"? The retriever currently doesn't fully use a progress widget, isn't it? Or I haven't seen the relevant parts in the code. Any hints? Thanks Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) msg24944/pgp0.pgp Description: PGP signature
