Bug#977939: Acknowledgement (linux-base: [INTL:de] updated German man page translation)

2021-03-28 Thread Helge Kreutzmann
Hello Ben,
hello Kernel team,

We are now quite in the freeze.

Is there any chance this still gets in Bullseye? (debian-release might
still allow a targetted fix).

This would be highly appreciated by German speaking users.

Thanks!

Greetings

   Helge

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature


Kindly consider uploading the updated (German) translation

2021-02-14 Thread Helge Kreutzmann
Dear Ben,
the freeze has begun and the German man page translation for linux-base
is not yet included.

Could you kindly consider performing another upload with the
translation? If you need help packaging the update, please contact me.

You will need to ask for a freeze exception, but by experience those
are granted for l10n (only) changes.

Thanks!

Greetings

 Helge

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature


Bug#977939: linux-base: [INTL:de] updated German man page translation

2020-12-22 Thread Helge Kreutzmann
Package: linux-base
Version: 4.6
Severity: wishlist
Tags: patch l10n

Please find the updated German man page translation for linux-base
attached.

If you update your template, please use 
'msgfmt --statistics '
to check the po-files for fuzzy or untranslated strings.

If there are such strings, please contact me so I can update the 
German translation.

Greetings
Helge
# Translation of the linux-base documentation to German.
# Copyright (C) 1996-2006 Manoj Srivastava.
# This file is distributed under the GPL version 2 or later.
# Copyright (C) of this file 2011, 2012 Chris Leick.
# Helge Kreutzmann , 2020.
#
msgid ""
msgstr ""
"Project-Id-Version: linux-base 4.6\n"
"Report-Msgid-Bugs-To: linux-b...@packages.debian.org\n"
"POT-Creation-Date: 2019-03-24 21:37+\n"
"PO-Revision-Date: 2020-12-23 07:39+0100\n"
"Last-Translator: Ben Hutchings \n"
"Language-Team: German \n"
"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. type: TH
#: man/kernel-img.conf.5:25
#, no-wrap
msgid "KERNEL-IMG.CONF"
msgstr "KERNEL-IMG.CONF"

#. type: TH
#: man/kernel-img.conf.5:25
#, no-wrap
msgid "24 March 2019"
msgstr "24. März 2019"

#. type: TH
#: man/kernel-img.conf.5:25
#, no-wrap
msgid "Debian"
msgstr "Debian"

#. type: TH
#: man/kernel-img.conf.5:25
#, no-wrap
msgid "Debian GNU/Linux manual"
msgstr "Debian-GNU/Linux-Handbuch"

#.  NAME should be all caps, SECTION should be 1-8, maybe w/ subsection
#.  other parms are allowed: see man(7), man(1)
#. type: SH
#: man/kernel-img.conf.5:28
#, no-wrap
msgid "NAME"
msgstr "BEZEICHNUNG"

#. type: Plain text
#: man/kernel-img.conf.5:30
msgid "kernel-img.conf - configuration file for Linux kernel packages"
msgstr "kernel-img.conf - Konfigurationsdatei für Linux-Kernel-Image-Pakete"

#. type: SH
#: man/kernel-img.conf.5:30
#, no-wrap
msgid "SYNOPSIS"
msgstr "ÜBERSICHT"

#. type: Plain text
#: man/kernel-img.conf.5:32
msgid "I"
msgstr "I"

#. type: SH
#: man/kernel-img.conf.5:32
#, no-wrap
msgid "DESCRIPTION"
msgstr "BESCHREIBUNG"

#. type: Plain text
#: man/kernel-img.conf.5:38
msgid ""
"The file I is used by the kernel package installation "
"and removal process to allow local options for handling some aspects of the "
"installation.  Most configuration variables apply only to kernel image "
"packages."
msgstr ""
"Die Datei I wird von dem Kernelpaket-Installations- "
"und -Entfernungsprozess verwandt, um lokale Optionen "
"zu ermöglichen, die einige Aspekte der Installation behandeln. Die meisten "
"Konfigurationsvariablen gelten nur für Kernel-Abbild-Pakete."

#. type: Plain text
#: man/kernel-img.conf.5:41
msgid ""
"Not all kernel image package creators support this file, or all the "
"configuration variables.  Support status for the file itself is:"
msgstr ""
"Nicht alle Erstellprogramme für Kernelabbilder unterstützen diese Datei oder "
"alle Konfigurationsvariablen. Der Unterstützungsstatus für die Datei selbst "
"ist wie folgt:"

#. type: tbl table
#: man/kernel-img.conf.5:44 man/kernel-img.conf.5:74 man/kernel-img.conf.5:88
#: man/kernel-img.conf.5:102 man/kernel-img.conf.5:142
#: man/kernel-img.conf.5:177 man/kernel-img.conf.5:207
#: man/kernel-img.conf.5:242 man/kernel-img.conf.5:275
#: man/kernel-img.conf.5:304 man/kernel-img.conf.5:319
#: man/kernel-img.conf.5:337 man/kernel-img.conf.5:352
#: man/kernel-img.conf.5:367 man/kernel-img.conf.5:380
#: man/kernel-img.conf.5:402 man/kernel-img.conf.5:416
#, no-wrap
msgid "B"
msgstr "B"

#. type: tbl table
#: man/kernel-img.conf.5:44 man/kernel-img.conf.5:74 man/kernel-img.conf.5:88
#: man/kernel-img.conf.5:102 man/kernel-img.conf.5:142
#: man/kernel-img.conf.5:177 man/kernel-img.conf.5:207
#: man/kernel-img.conf.5:242 man/kernel-img.conf.5:275
#: man/kernel-img.conf.5:304 man/kernel-img.conf.5:319
#: man/kernel-img.conf.5:337 man/kernel-img.conf.5:352
#: man/kernel-img.conf.5:367 man/kernel-img.conf.5:380
#: man/kernel-img.conf.5:402 man/kernel-img.conf.5:416
#, no-wrap
msgid "B"
msgstr "B"

#. type: tbl table
#: man/kernel-img.conf.5:45 man/kernel-img.conf.5:75 man/kernel-img.conf.5:89
#: man/kernel-img.conf.5:103 man/kernel-img.conf.5:143
#: man/kernel-img.conf.5:178 man/kernel-img.conf.5:208
#: man/kernel-img.conf.5:243 man/kernel-img.conf.5:276
#: man/kernel-img.conf.5:305 man/kernel-img.conf.5:320
#: man/kernel-img.conf.5:338 man/kernel-img.conf.5:353
#: man/kernel-img.conf.5:368 ma

Bug#605090: Great idea to get grsec flavored Debian kernels

2011-05-18 Thread Helge Kreutzmann
Hello,
it would be really great to get grsec enabled kernels. We've using them
for years (self compiled) and except for the recent problems with
iceweasel (cf. #623997) without any modifications / problems (except
for a root kit we caught 7 years ago, but that's on purpose).

Greetings

   Helge
-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software libre: http://www.ffii.de/


signature.asc
Description: Digital signature


Bug#462802: redhat-cluster: Superfluous white spaces in Debconf template

2008-01-27 Thread Helge Kreutzmann
Package: redhat-cluster
Severity: minor
Tags: patch

While translating your Debconf template to German I noticed the
following superfluous white spaces:
-The new version 2.0 of the Red Hat Cluster Suite is not compatible with  the 
+The new version 2.0 of the Red Hat Cluster Suite is not compatible with the 
-currently installed one. Upgrading these packages without stopping  the 
+currently installed one. Upgrading these packages without stopping the 

-complete cluster can cause file system corruption on shared storage  devices.
+complete cluster can cause file system corruption on shared storage devices.

Please unfuzzy all translations after fixing.

-- 
  Dr. Helge Kreutzmann [EMAIL PROTECTED]
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software libre: http://www.ffii.de/


signature.asc
Description: Digital signature


Bug#462801: redhat-cluster: [INTL:de] initial German debconf translation

2008-01-27 Thread Helge Kreutzmann
Package: redhat-cluster
Severity: wishlist
Tags: patch l10n

Please find the initial German debconf translation for redhat-cluster
attached.

Please place this file in debian/po/ as de.po for your next upload.

If you update your template, please use 
'msgfmt --statistics pofile.po'
to check the po-files for fuzzy or untranslated strings.

If there are such strings, please contact me so I can update the 
German translation.

Greetings
Helge
# Translation of redhat-cluster debconf templates to German
# Copyright (C) Helge Kreutzmann [EMAIL PROTECTED], 2008.
# This file is distributed under the same license as the redhat-cluster package.
#
msgid 
msgstr 
Project-Id-Version: redhat-cluster \n
Report-Msgid-Bugs-To: [EMAIL PROTECTED]
POT-Creation-Date: 2008-01-26 17:44+0100\n
PO-Revision-Date: 2008-01-27 17:00+0100\n
Last-Translator: Helge Kreutzmann [EMAIL PROTECTED]\n
Language-Team: German [EMAIL PROTECTED]\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=ISO-8859-15\n
Content-Transfer-Encoding: 8bit\n

#. Type: boolean
#. Description
#: ../cman.templates:2001
msgid Abort the potentially disruptive upgrade of Red Hat Cluster Suite?
msgstr 
Soll das möglicherweise störende Upgrade der Red Hat Cluster Suite 
abgebrochen werden?

#. Type: boolean
#. Description
#: ../cman.templates:2001
msgid 
The new version 2.0 of the Red Hat Cluster Suite is not compatible with  the 
currently installed one. Upgrading these packages without stopping  the 
complete cluster can cause file system corruption on shared storage  devices.
msgstr 
Die neue Version 2.0 der Red Hat Cluster Suite ist zu der derzeit 
installierten nicht kompatibel. Ein Upgrade dieser Pakete ohne Anhalten des 
kompletten Clusters kann zu Dateisystem-Verfälschungen auf gemeinsam 
benutzten Speichersystemen führen.

#. Type: boolean
#. Description
#: ../cman.templates:2001
msgid 
For instructions on how to safely upgrade the Red Hat Cluster Suite to 
version 2.0, please refer to 'http://wiki.debian.org/UpgradeRHCSV1toV2'.
msgstr 
Für Anweisungen, wie Sie sicher ein Upgrade der Red Hat Cluster Suite auf 
Version 2.0 durchführen können, lesen Sie bitte http://wiki.debian.org/;
UpgradeRHCSV1toV2.


Bug#451367: installation-reports: Does not allow ethernet over firewire

2007-11-20 Thread Helge Kreutzmann
Hello,
On Tue, Nov 20, 2007 at 08:01:40PM +0100, maximilian attems wrote:
 eth1394 is missing that is by far the less used firewire driver.

But for some people the driver used early in the installation (where a
kernel rebuild is not very convenient).

 the switch to the juju stack allowed to close a huge nr. of bugs.
 the old stack is just not supportable and never was, plus is a
 security nightmare. ieee1394 in fact deserves the Kbuild variable BROKEN.

Well, it worked fine for me, except that the version from 2.4 could
not interoperate with the version from 2.6. The only minor oddity was
that sometimes the logs were flooded with certain warnings (I can dig
them out if necessary).

 i consider that smallish to the *huge* usability improvement
 on not having a strange firewire ethernet device to choose
 for your network connectivity in d-i.
 so no tears for it.

Well, I cannot really argue with you on technical merits, but then it
was one of the (long) supported options for d-i, so please *document*
it properly. I would've started out with an Etch image, if I had known
this regression.

 RH did rewrite the stack and it's main upstream developer ships
 it already enabled in 2 major releases fedora 7 and 8.
 juju has already nicely improved since the 2.6.22 inclusion,
 so still looks for the most promising option for the lenny release.

It would be great if also eth1394 would reappear in the new stack, 
especially since the original developer is an @debian.org person.

Greetings

Helge

-- 
  Dr. Helge Kreutzmann [EMAIL PROTECTED]
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software libre: http://www.ffii.de/


signature.asc
Description: Digital signature


Bug#451367: installation-reports: Does not allow ethernet over firewire

2007-11-16 Thread Helge Kreutzmann
Hello,
On Thu, Nov 15, 2007 at 05:21:36PM +0100, Frans Pop wrote:
 Hmm. One more try. Let's check the mailing list for June. Ah, a hit!
 http://lists.debian.org/debian-kernel/2007/06/msg00079.html
 
 No discussion though (at least, I don't usually call a single message a 
 discussion). Not all that surprising that no users spoke up since the 
 message is only to the kernel list, which is a _developer_ list.
 I'd say the lack of response is a better indication of the fact that other 
 kernel developers did not really care about the change than about what 
 users think of it.

Yes, it would have been nice if this issue could've been discussed,
especially since it was perfectly working and if user are confused then
the interface (i.e. d-i) should be improved and not simply the
functionality be dropped (more precisely: this issue should've been
brought up in a bug report).

 [1] http://wiki.linux1394.org/JujuMigration

Well, I don't know if there is a possibility for the kernel, but this
looks like experimental stuff, e.g.:
Stability issues of the storage device driver firewire-sbp2

I'm glad that I do not use storage currently via firewire 

Well, if you like me to test later versions feel free to contact me. I
routinely connect ppc-amd64 via firewire (of course using the old
stack).

Greetings

  Helge

-- 
  Dr. Helge Kreutzmann [EMAIL PROTECTED]
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software libre: http://www.ffii.de/


signature.asc
Description: Digital signature


Re: Bug#450836: installation-reports: Does not allow ethernet over firewire

2007-11-16 Thread Helge Kreutzmann
Hello Maximilian,
On Thu, Nov 15, 2007 at 01:24:32PM +0100, maximilian attems wrote:
 On Thu, Nov 15, 2007 at 12:53:31PM +0100, Frans Pop wrote:
  On Thursday 15 November 2007, Frans Pop wrote:
  It looks as if the new stack just does not have any Ethernet support (yet?).
  I also no longer have a firewire Ethernet device on my x86_64 system.
  
  This is confirmed on:
  http://wiki.linux1394.org/JujuMigration
  
  That same page lists several issues with the new stack when compared to the 
  old one and also has the following recommendation:
  ! ! Regarding Linux 2.6.22 and 2.6.23, the best advice to Linux
  ! distributors (kernel packagers) as well as to regular users is: Build only
  ! the old IEEE 1394 drivers.
  
  Please activate the old stack again.
 
 the new stack is very promising,
 we will reconsider later if no eth1394 shows up,
 for now that's just a minor regression.

Well, for *me* at least this is not minor, because it means I need to
rebuild the kernel before I can start installing, as I've currently
only have a spare firewire cable (which I frequently used with
various kernels already). 

At which state do you reconsider eth1394 support? Given that the
developer of this module is a DD I hope this happens soon.

 see discussions on d-kernel,
 nobody spoke up when the anncouncement about missing eth1394 was declared.

It would be kind if you could announce this a little more prominently
(e.g. on http://www.debian.org/devel/debian-installer/ ) as I do not
read d-kernel.

Thanks!

Greetings

Helge
-- 
  Dr. Helge Kreutzmann [EMAIL PROTECTED]
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software libre: http://www.ffii.de/


signature.asc
Description: Digital signature


Bug#299875: A different, not kernel related bug

2005-03-23 Thread Helge Kreutzmann
clone 299875 -1
reassign -1 ppp
retitle -1 ppp_2.4.3 pppd hangs on re-connect
tags -1 - patch
tags -1 - security
severity -1 important
thanks

The security issue does not seem relevant to this bug, according to
the submitter. Hence reassign to ppp, where downgrading solves the
issue. 

This might be still security related (DoS), but I doubt it.

I lowered the severity to important, because only one (albeit
important) feature does not work, namly re-connect. So the initial
connect works. Since the submitter cannot trigger it manually and has
a script for re-connects in place, a possible workaround would be to
manually disconnect in time, e.g., before the provider disconnects,
and then manually re-connect.

Of course, the true problem should still be found here.

Greetings

 Helge
-- 
Dr. Helge Kreutzmann, Dipl.-Phys.   [EMAIL PROTECTED]
   gpg signed mail preferred 
64bit GNU powered  http://www.itp.uni-hannover.de/~kreutzm
   Help keep free software libre: http://www.freepatents.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]