Your message dated Sun, 27 Apr 2008 20:42:19 +0200
with message-id <[EMAIL PROTECTED]>
and subject line CLosing bug
has caused the Debian Bug report #457026,
regarding roxen4: [debconf_rewrite] Debconf templates and debian/control review
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
457026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=457026
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: roxen4
Version: N/A
Severity: normal
Tags: patch
Dear Debian maintainer,
On Thursday, November 29, 2007, I notified you of the beginning of a review
process
concerning debconf templates for roxen4.
The debian-l10n-english contributors have now reviewed these templates,
and the proposed changes are attached to this bug report.
Please review the suggested changes are suggested, and if you have any
objections, let me know in the next 3 days.
Please try to avoid uploading roxen4 with these changes right now.
The second phase of this process will begin on Saturday, December 22, 2007,
when I will
coordinate updates to translations of debconf templates.
The existing translators will be notified of the changes: they will
receive an updated PO file for their language.
Simultaneously, a general call for new translations will be sent to
the debian-i18n mailing list.
Both these calls for translations will request updates to be sent as
individual bug reports. That will probably trigger a lot of bug
reports against your package, but these should be easier to deal with.
The call for translation updates and new translations will run until
about Saturday, January 12, 2008. Please avoid uploading a package with fixed
or changed
debconf templates and/or translation updates in the meantime. Of
course, other changes are safe.
Please note that this is an approximative delay, which depends on my
own availability to process this work and is influenced by the fact
that I simultaneously work on many packages.
Around Sunday, January 13, 2008, I will contact you again and will send a final
patch
summarizing all the updates (changes to debconf templates,
updates to debconf translations and new debconf translations).
Again, thanks for your attention and cooperation.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
--- roxen4.old/debian/templates 2007-11-24 13:43:11.766273058 +0530
+++ roxen4/debian/templates 2007-12-19 11:57:23.346140445 +0530
@@ -1,123 +1,125 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# [EMAIL PROTECTED] for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
Template: roxen4/server_name
Type: string
Default: Administration Interface
-_Description: Server Configuration Name:
- What name to give to the server?
+_Description: Server name:
+ Please enter the name that should be given to the Roxen server.
Template: roxen4/server_url
Type: string
_Description: Administration page URL:
- What URL should roxen4 listen to for the administration server. Should be
- something like:
+ Please enter the URL that should be used to access Roxen's administration
+ server. Example:
.
- http://*:1234/
+ http://www.example.org:<port>/
.
- where '1234' is the port to listen to. A random port has been created
- for you to accept. The likelihood of it being occupied is slim, but
- make sure you want this port before pressing ENTER.
+ where '<port>' is the port to listen to. A random port is proposed
+ by default. It is very probably free for use but you should check this
+ before accepting this value.
Template: roxen4/admin_user
Type: string
Default: administrator
_Description: Administrator username:
- The name of the administrator.
+ Please enter the username for the Roxen server administrator.
Template: roxen4/admin_password
Type: password
+# Translators: do not translate ${SERVER_ADMIN}
_Description: Administrator password:
- Please enter a password for the server administrator
- user (which is ${SERVER_ADMIN}).
+ Please choose a password for the Roxen server administrator
+ (${SERVER_ADMIN}).
Template: roxen4/admin_password_verification
Type: password
-_Description: Administrator password verification:
- Please enter the administration password again.
+_Description: Administrator password confirmation:
Template: roxen4/admin_password_missing
-Type: note
+Type: error
_Description: Empty administrator password
- Unable to accept an empty password!
Template: roxen4/update_system
Type: boolean
Default: false
_Description: Enable built-in update system?
- You may enable the automatic update system. This requires an account in the
Roxen
- Community.
+ Roxen offers an automatic update system. To use this feature, you need
+ an account in the Roxen Community.
Template: roxen4/update_system_proxy
Type: boolean
Default: false
_Description: Access update server through proxy?
- This option allows you to access the update server through an HTTP proxy.
+ Please choose whether the update server should be accessed through
+ an HTTP proxy.
Template: roxen4/proxy_host
Type: string
-_Description: Proxy host:
- Host to use as proxy for the connection to the Roxen Community.
+_Description: Proxy server hostname:
Template: roxen4/proxy_port
Type: string
-_Description: Proxy port:
- Port for the HTTP proxy
+_Description: Proxy server port:
Template: roxen4/proxy_value_missing
-Type: note
-_Description: Missing proxy host/port value
- If you specify that you want to use a HTTP proxy to connect via when
- connecting to the Roxen Community, you MUST specify a value! Do over.
+Type: error
+_Description: Empty proxy host or port
Template: roxen4/community_identity
Type: string
_Description: Roxen Community identity:
- Give your Roxen Community identity (your e-mail).
+ Please enter your Roxen Community identity (e-mail address).
.
- Enter 'none' to disable the automatic update system.
+ Entering 'none' will disable the automatic update system.
Template: roxen4/community_identity_missing
-Type: note
+Type: error
_Description: Missing community identity
- You MUST give a community id to be able to use the automatic update
- facility. Do over.
+ A community identity is mandatory for access to the automatic update
+ facility.
Template: roxen4/community_password
Type: password
_Description: Roxen Community password:
- Password for the Roxen Community.
Template: roxen4/community_password_verification
Type: password
-_Description: Roxen Community password verification:
- Please enter the Community password again.
+_Description: Roxen Community password confirmation:
Template: roxen4/password_missmatch
-Type: note
-_Description: Passwords don't match
+Type: error
+_Description: Password mismatch
+ The password and its confirmation do not match.
Template: roxen4/previous_installation_roxen2
Type: note
-_Description: Previous installation (Roxen2) detected
- Roxe 2 seems to be installed. As many values as possible will be taken from
- this configuration, but you still have to give SOME your self. Mostly
- passwords, since they are encrypted and can't be decrypted easily...
- .
- You still have to MANUALLY move any configurations you have for Roxen2 to
- your new Roxen4 server (they CAN coexist as long as you don't use the
- same ports)...
+_Description: Roxen 2 installation detected
+ Roxen 2 appears to be installed on this host. As many values as
+ possible will be taken from this configuration, but some will need
+ manual intervention, such as passwords.
+ .
+ Roxen 2 and Roxen 4 can coexist on the same server as long as they
+ use different ports.
.
- The administration port is the same as the Roxen2 installation but plus
- one (ie, ${SERVER_URL}).
+ The administrative interface for Roxen 4 will use the same URL as the
+ equivalent for Roxen 2, but one port number higher: ${SERVER_URL}.
Template: roxen4/previous_installation_roxen3
Type: note
-_Description: Previous installation (Roxen3) detected
- Roxen3 seems to be installed. As many values as possible will be taken from
- this configuration, but you still have to give SOME your self. Mostly
- passwords, since they are encrypted and can't be decrypted easily...
- .
- You still have to MANUALLY move any configurations you have for Roxen 3 to
- your new Roxen 4 server (they CAN coexist as long as you don't use the
- same ports)...
+_Description: Roxen 3 installation detected
+ Roxen 3 appears to be installed on this host. As many values as
+ possible will be taken from this configuration, but some will need
+ manual intervention, such as passwords.
+ .
+ Roxen 3 and Roxen 4 can coexist on the same server as long as they
+ use different ports.
.
- The administration port is the same as the Roxen2 installation but plus
- one (ie, ${SERVER_URL}).
+ The administrative interface for Roxen 4 will use the same URL as the
+ equivalent for Roxen 3, but one port number higher: ${SERVER_URL}.
--- roxen4.old/debian/control 2007-11-24 13:43:11.766273058 +0530
+++ roxen4/debian/control 2007-12-16 15:39:03.471563875 +0530
@@ -13,29 +13,22 @@
Provides: httpd, httpd-cgi, roxen3
Replaces: roxen3
Conflicts: roxen3
-Description: The Roxen Challenger Webserver
- The Roxen Challenger is a very powerful and easy to maintain web
- server. The server is written in Pike which is C-like but interpreted
- at runtime. Roxen may be configured comfortable via any web browser.
+Description: Roxen WebWerver - binaries
+ The Roxen WebServer is very powerful and easy to maintain.
+ The server is written in Pike (which is C-like but interpreted
+ at runtime) and can be configured via any web browser.
.
- The Roxen Challenger server is the foundation of a powerful
- information and communication environment. Challenger is a secure and
- competent web server. If your intention is minimizing your Total Cost
- of Ownership, Challenger is entirely in line. Challenger offers a
- smorgasbord of features, and on top of that, a whole suite of
- commercial and tightly integrated extensions. Challenger is just as
- suitable for powering an any-sized web site, as for an intranet
- application.
+ Roxen is the foundation of a powerful information and communication
+ environment. It is a secure and reliable web server, offering
+ numerous features including a whole suite of commercial and tightly
+ integrated extensions. Roxen is also suitable for powering any web
+ site or intranet application.
.
- This is the official version of the new 'Roxen WebServer' (the new
- name of the webserver). This is still a beta release and the old
- configuration files of the server is not fully compatible with this
- version. There will be a conversion script in a later version, but
- until then I'm installing in .../roxen4/ without any automatic config
- transference. You will have to configure the server manually... You
- can still have both the stable (1.3 and 2.1) versions, since they
- don't clash (at least not filesystem wise), but make sure they don't
- try to talk/listen on the same ports!
+ This package provides version 4 of 'Roxen WebServer' (formerly known
+ as Roxen Challenger). Configuration files for older server versions
+ are not fully compatible with this version. Several parts of the
+ server must be configured or migrated manually. The new version can
+ coexist with former versions on the same host.
Package: roxen4-doc
Architecture: all
@@ -44,5 +37,15 @@
Replaces: roxen3-doc
Conflicts: roxen3-doc
Depends: roxen4
-Description: Roxen 4.0 documentation
- Documentation for the Roxen Webserver, v4.0.
+Description: Roxen Challenger web server - documentation
+ The Roxen WebServer is very powerful and easy to maintain.
+ The server is written in Pike (which is C-like but interpreted
+ at runtime) and can be configured via any web browser.
+ .
+ Roxen is the foundation of a powerful information and communication
+ environment. It is a secure and reliable web server, offering
+ numerous features including a whole suite of commercial and tightly
+ integrated extensions. Roxen is also suitable for powering any web
+ site or intranet application.
+ .
+ This package provides the server's documentation.
--- End Message ---
--- Begin Message ---
Version: 4.0.425-8
This bug should have been closed by the 4.0.425-8 version.
--- End Message ---
