Your message dated Thu, 28 Sep 2006 10:17:04 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#338849: fixed in ifupdown 0.6.8
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)

--- Begin Message ---
Package: ifupdown
Version: 0.6.7
Severity: wishlist
Tags: patch l10n


Here is an update for the swedish translation of the debconf template
for ifupdown.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13.2
Locale: LANG=sv_SE, LC_CTYPE=sv_SE (charmap=ISO-8859-1)

Versions of packages ifupdown depends on:
ii  debconf [debconf-2.0]         1.4.59     Debian configuration management sy
ii  libc6                         2.3.5-7    GNU C Library: Shared libraries an
ii  net-tools                     1.60-16    The NET-3 networking toolkit

ifupdown recommends no packages.

-- debconf information excluded
#
#    Translators, if you are not familiar with the PO format, gettext
#    documentation is worth reading, especially sections dedicated to
#    this format, e.g. by running:
#         info -n '(gettext)PO Files'
#         info -n '(gettext)Header Entry'
#
#    Some information specific to po-debconf are available at
#            /usr/share/doc/po-debconf/README-trans
#         or http://www.debian.org/intl/l10n/po-debconf/README-trans
#
#    Developers do not need to manually edit POT or PO files.
#
msgid ""
msgstr ""
"Project-Id-Version: ifupdown 0.6.7\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2004-08-04 17:16+0200\n"
"PO-Revision-Date: 2005-11-13 12:23+0100\n"
"Last-Translator: Daniel Nylander <[EMAIL PROTECTED]>\n"
"Language-Team: Swedish <[EMAIL PROTECTED]>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=ISO-8859-1\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Poedit-Language: swe\n"
"X-Poedit-Country: swe\n"

#. Type: boolean
#. Description
#: ../templates.master:4
msgid "Update /etc/network/interfaces?"
msgstr "Uppdatera /etc/network/interfaces?"

#. Type: boolean
#. Description
#: ../templates.master:4
msgid "The format of /etc/network/interfaces has had a minor but incompatible 
change made between version 0.5.x and 0.6.x of ifupdown. It is however possible 
to automatically convert from the old format to the new in almost all cases."
msgstr "Formatet på /etc/network/interfaces har genomgått en liten ändring som 
gör att versionerna 0.5.x och 0.6.x av ifupdown blivit inkompatibla. Dock är 
det möjligt att nästan alltid automatiskt konvertera från det gamla formatet 
till det nya."


--- End Message ---
--- Begin Message ---
Source: ifupdown
Source-Version: 0.6.8

We believe that the bug you reported is fixed in the latest version of
ifupdown, which is due to be installed in the Debian FTP archive:

ifupdown_0.6.8.dsc
  to pool/main/i/ifupdown/ifupdown_0.6.8.dsc
ifupdown_0.6.8.tar.gz
  to pool/main/i/ifupdown/ifupdown_0.6.8.tar.gz
ifupdown_0.6.8_i386.deb
  to pool/main/i/ifupdown/ifupdown_0.6.8_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Petter Reinholdtsen <[EMAIL PROTECTED]> (supplier of updated ifupdown package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu, 28 Sep 2006 18:14:47 +0200
Source: ifupdown
Binary: ifupdown
Architecture: source i386
Version: 0.6.8
Distribution: unstable
Urgency: low
Maintainer: Anthony Towns <[EMAIL PROTECTED]>
Changed-By: Petter Reinholdtsen <[EMAIL PROTECTED]>
Description: 
 ifupdown   - high level tools to configure network interfaces
Closes: 266021 311011 311443 311777 311928 312988 330230 336931 338849 339834 
347580 353154 362093 384438 384866 386794 387155 387453 387677
Changes: 
 ifupdown (0.6.8) unstable; urgency=low
 .
   * Add myself as co-maintainer with approval from Anthony Towns.
   * Change path of dhclient.leases to make sure the dhcp state survive
     reboots. (Closes: #311777)
   * Change leasehours option value to match the option name.
   * Async ifup/ifdown modication based on patch from Scott James
     Remnant and Ubuntu.  (Closes: #347580)
     - Rewrite the way that ifup and ifdown read and write the state
       file.  Instead of storing it in memory and holding a lock on it
       (preventing concurrent processes from actually being concurrent)
       use atomic read and write functions that only hold the lock for
       very short periods.
     - Write to the state file when we start bringing up or tearing
       down the interface, so we don't ever try to do the same
       operation at the same time.
     - Update the state file once the operation is complete to ensure
       we record the actual status of it.
   * Acknowledge NMUs. (Closes: #311011, #311443, #353154, #339834, #311928,
     #336931, #338849, #362093, #330230, #386794, #384866, #312988, #266021,
     #384438, #387155, #387453, #387677)
Files: 
 a2da1ec7d7fdf06792b1b0e5bb8cec94 549 admin important ifupdown_0.6.8.dsc
 0c4cf072305b1e798e9e704558ec01f1 375416 admin important ifupdown_0.6.8.tar.gz
 63377920f0fdcd98d86e22eabf148395 50852 admin important ifupdown_0.6.8_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFHALF20zMSyow1ykRAt5gAKDIsujpHPdPU1S9zjEbb8xVv73+KQCeMVPJ
o585sBatKYTkn7yK5aswXcE=
=yZbT
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to