Bug#739948: [kinetic-audio-setup] kinetic-audio-setup [INTL:de] German translation of debconf template
Package: kinetic-audio-setup Version: 0.3.2 Severity: wishlist Tags: l10n patch --- Please enter the report below this line. --- Hello, please find attached the German translation of the debconf template for the mentioned package. File name: de.po Please move the file to the folder it belongs to. Feel free to report any errors regarding the translation's content or formatting issues by contacting me at my email address. Kind regards Stephan Beck --- System information. --- Architecture: i386 Kernel: Linux 3.9.6 Debian Release: 7.4 990 stable security.debian.org 990 stable ftp.de.debian.org 500 stable-updates ftp.de.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. # German translation for kinect-audio-setup. # Copyright (C) 2014 Antonio Ospite # This file is distributed under the same license as the kinect-audio-setup package. # Stephan Beck , 2014. # msgid "" msgstr "" "Project-Id-Version: kinect-audio-setup 0.3.2\n" "Report-Msgid-Bugs-To: kinect-audio-se...@packages.debian.org\n" "POT-Creation-Date: 2014-02-17 18:39+0100\n" "PO-Revision-Date: 2014-02-23 23:04-\n" "Last-Translator: Stephan Beck \n" "Language-Team: Debian German translation team \n" "Language: de\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: boolean #. Description #: ../templates:2001 msgid "Do you accept the Microsoft Kinect for Windows EULA?" msgstr "Stimmen Sie der EULA für Microsoft Kinect für Windows zu?" #. Type: boolean #. Description #: ../templates:2001 msgid "" "In order to fetch the binary firmware needed by the kinect-audio-setup " "package, you need to agree to the End User License Agreement (EULA) of the " "Microsoft Kinect for Windows Software Development Kit:" msgstr "" "Um die für das Paket kinect-audio-setup notwendige Binär-Firmware abzurufen, " "ist Ihre Zustimmung zur Lizenzvereinbarung für Endbenutzer (EULA) des " "Software Development Kit von Microsoft Kinect für Windows erforderlich:" #. Type: error #. Description #: ../templates:3001 msgid "EULA not accepted" msgstr "EULA nicht zugestimmt" #. Type: error #. Description #: ../templates:3001 msgid "" "You need to accept the End User License Agreement (EULA) of the Microsoft " "Kinect for Windows Software Development Kit in order to fetch the binary " "firmware needed by the kinect-audio-setup package." msgstr "" "Ihre Zustimmung zur Lizenzvereinbarung für Endbenutzer (EULA) des Software " "Development Kit von Microsoft Kinect für Windows ist erforderlich, um die für " "das Paket kinect-audio-setup notwendige Binär-Firmware abzurufen." #. Type: error #. Description #: ../templates:3001 msgid "You can do this later with \"dpkg-reconfigure kinect-audio-setup\"." msgstr "" "Sie können dies später noch erledigen, indem Sie »dpkg-reconfigure kinect-" "audio-setup« ausführen." signature.asc Description: OpenPGP digital signature
Bug#739948: kinetic-audio-setup [INTL:de] German translation of debconf template
I am terribly sorry, I've seen that it was my fault (there was missing a space just before Antonio's email address. It is because I forgot to do the final statistics check. I will not forget it again! I guess I am going to buy glasses, right now. 8-) Kind regards Stephan Beck Am 25.02.2014 10:52, schrieb Antonio Ospite: > On Tue, 25 Feb 2014 07:13:27 +0100 > Christian PERRIER wrote: > >> >> A line was split out in the file's header. Please use the attached >> file instead. >> > > I am adding the translations now, and the de.po attached by Christian > seems to still have the Language-Team tag broken in two lines. > > I fixed it locally and I am going to apply the one from Christian with > the header fix (see the attached file). > > Thanks, >Antonio > signature.asc Description: OpenPGP digital signature
Bug#739948: kinetic-audio-setup [INTL:de] German translation of debconf template
Sorry, Antonio. It was the Language Tag, as you mention it. In the file version I sent, the Copyright note (with your email address) was broken in two lines, too. I really need glasses, don't I? Cari saluti a Italia! Stephan Beck Am 25.02.2014 10:52, schrieb Antonio Ospite: > On Tue, 25 Feb 2014 07:13:27 +0100 > Christian PERRIER wrote: > >> >> A line was split out in the file's header. Please use the attached >> file instead. >> > > I am adding the translations now, and the de.po attached by Christian > seems to still have the Language-Team tag broken in two lines. > > I fixed it locally and I am going to apply the one from Christian with > the header fix (see the attached file). > > Thanks, >Antonio > signature.asc Description: OpenPGP digital signature
Bug#740113: [chef] chef: [INTL:de] German debconf templates translation
Package: chef Version: 11.8.2-4 Severity: wishlist Tags: l10n patch --- Please enter the report below this line. --- Hello, Please find attached the German debconf template translation for the package chef. Please move the file to debian/po/ as de.po for your next upload and check whether the copyright information is correct. I searched for the package maintainer in Debian Search (Project Participants) and the only maintainer without an asterisk behind "chef" (* = indicating co-maintainership) was the one I put in the copyright text. If I was wrong, I beg your pardon. Kind regards Stephan Beck --- System information. --- Architecture: i386 Kernel: Linux 3.9.6 Debian Release: 7.4 990 stable security.debian.org 990 stable ftp.de.debian.org 500 stable-updates ftp.de.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. # German translation for chef. # Copyright (C) 2014 Timberman, Joshua # This file is distributed under the same license as the chef package. # Stephan Beck , 2014. # msgid "" msgstr "" "Project-Id-Version: chef 11.8.2-4\n" "Report-Msgid-Bugs-To: c...@packages.debian.org\n" "POT-Creation-Date: 2014-02-18 07:08+0100\n" "PO-Revision-Date: 2014-02-25 22:14-\n" "Last-Translator: Stephan Beck \n" "Language-Team: Debian German translation team \n" "Language: de\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: string #. Description #: ../chef.templates:2001 msgid "URL of Chef server" msgstr "URL des Chef-Servers" #. Type: string #. Description #: ../chef.templates:2001 msgid "Please choose the full URI that clients will use to connect to the server (for instance: http://chef.example.com:4000)." msgstr "Bitte wählen Sie die vollständige URI, welche die Clients zur Verbindung mit dem Server verwenden (z. B. http://chef.example.com:4000)." #. Type: string #. Description #: ../chef.templates:2001 msgid "This setting will be stored in /etc/chef/client.rb as \"chef_server_url\"." msgstr "Diese Einstellung wird unter »chef_server_url« in /etc/chef/client.rb gespeichert." signature.asc Description: OpenPGP digital signature
Bug#741169: [shinken] German debconf templates translation
Package: shinken Version: 1.4-2 Severity: wishlist Tags: l10n patch --- Please enter the report below this line. --- Hello, please find attached the German translation of the debconf template for shinken. Please place the file in po-debconf://shinken/po/de.po Please check if the YEAR information in the header's copyright info actually corresponds with the year of the release of the 1.4-2 version. I was not very sure about it and put 2014, though it may as well be 2013. On shinken-monitoring.org I found the name of the copyright holder. Shinken seems to be a great nm-tool! Kind regards Stephan Beck Debian German translation team --- System information. --- Architecture: i386 Kernel: Linux 3.9.6 Debian Release: 7.4 990 stable security.debian.org 990 stable ftp.de.debian.org 500 stable-updates ftp.de.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. # German translation for shinken. # Copyright (C) 2014 Jean Gabès # This file is distributed under the same license as the shinken package. # Stephan Beck , 2014. # msgid "" msgstr "" "Project-Id-Version: shinken_1.4-2\n" "Report-Msgid-Bugs-To: shin...@packages.debian.org\n" "POT-Creation-Date: 2013-12-04 18:02-0500\n" "PO-Revision-Date: 2014-03-06 20:21-\n" "Last-Translator: Stephan Beck \n" "Language-Team: \n" "Language: de\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: note #. Description #: ../shinken-module-broker-webui.templates:1001 msgid "Recommendation for the WebUI module" msgstr "Empfehlung für das »WebUI«-Modul" #. Type: note #. Description #: ../shinken-module-broker-webui.templates:1001 msgid "" "Change 'auth_secret' option in /etc/shinken/shinken-specific/broker-webui.cfg" msgstr "" "Ãndern Sie die Option »auth_secret« in /etc/shinken/shinken-specific/broker-" "webui.cfg." #. Type: note #. Description #: ../shinken.templates:1001 msgid "To access to Shinken" msgstr "Sie können wie folgt auf Shinken zugreifen:" #. Type: note #. Description #: ../shinken.templates:1001 msgid "* Address: http://127.0.0.1:7767 * Username: admin * Password: admin" msgstr "" "* Adresse: http://127.0.0.1:7767 * Benutzername: admin * Kennwort: admin" signature.asc Description: OpenPGP digital signature
Bug#772963: release-notes: cellphone friendly CSS
Am 31.01.2015 um 17:14 schrieb Stéphane Blondon: > Thank you Niels for your help! I cloned your git repository and > patched the debian.css file. > I attach here the new file and a diff. If it's nicer for you, I could > create a temporary repository on GitHub. I've got a account on alioth > (sblondon-guest) too. Me, too (stebe-guest). It would be nice to exchange ideas there, if desired and possible. > > The temporary demo: > http://stephane.yaal.fr/tmp/release-notes.amd64.html/index.en.html > The home image is below the arrows. In my opinion, it would be better > to display it at the same height than the arrows. I don't know if it's > hard to do. The first quick and dirty solution (only touching the .html file) is to suppress the second table row in the.html file. (1) I've only applied it to the What's new in Debian 8.html, just as an example. In this case you do not have to change anything in the .css. Disadvantage: The footer has lost height. For now, I cannot provide a demo url and I don't want to attach a file because it's too large for a mailing list. Below you find a simple diff. A second solution I'll work on is to replace the table with a "div id="navfooter" containing a nav element that includes anchors and images. I think it's better to use "table" only for "real" tables, not as a space structuring design element. This solution will imply changes to the .css. (1) diff --suppress-common-lines ch-whats-new.en-old.html ch-whats-new.en.html 215c215 < Chapter 1. Introduction Chapter 3. Installation System \ no line-break at end of file --- >Chapter 1. Introduction Chapter 3. Installation System \ no line-break at end of file > > > What do you think about these changes? > > For next improvement, we could replace the caution and note images > with more modern ones (from the publican project or tango desktop > project for example). I haven't had time to check but if there's still time I'll check some new designs. > Regards Stephan signature.asc Description: OpenPGP digital signature
Bug#772963: release-notes: cellphone friendly CSS
Hi Stéphane, hi Niels,
Am 31.01.2015 um 17:14 schrieb Stéphane Blondon:
[...]
I cloned the git as well and worked out another solution for the footer which I
announced in my previous message (suppressing the table and adding a nav
element).
Please have a look at the attached files:
(1) ch-whats-new.en.diff
(2) debian.css
Please comment on any issues you may find. There might be plenty of them :-)
In my next message I will propose some new designs for the home and the arrow
icons.
Kind regards
Stephan
Index: ch-whats-new.en_a.html
===
--- ch-whats-new.en_a.html (Revision 1)
+++ ch-whats-new.en_a.html (Arbeitskopie)
@@ -212,4 +212,4 @@
shipped with Stretch. See the http://wiki.debian.org/Teams/MySQL"; target="_top">Debian MySQL Team wiki page
for more information.2.2.7. PHP applicationsThe Horde Application Framework is available in Jessie, via
the php-horde package.
-    Chapter 1. Introduction  Chapter 3. Installation System
\ No newline at end of file
+ Chapter 1. IntroductionChapter 3. Installation System
\ No newline at end of file
/* Cascading stylesheet for the Debian Installer Installation Guide */
/* global style of the page */
body {
background-color: #EE;
border: 40px solid #EE;
margin: 0;
padding: 0 10px;
font-family: "liberation sans", "Myriad ", "Bitstream Vera Sans", "Lucida Grande", "Luxi Sans", "Trebuchet MS", helvetica, verdana, arial, sans-serif;
line-height: 1.2em;
}
@media (max-width: 5in), (max-device-width: 5in) {
body {
border: 0px;
padding: 0px;
}
}
body > div.book, body > div.article, body > div.set, body > div.preface, body > div.chapter, body > div.section, body > div.appendix, body > div.part {
margin-top: 0;
padding: 2em 6em 6em;
}
body > div.book, body > div.article, body > div.set, body > div.preface, body > div.chapter, body > div.section, body > div.appendix, body > div.part {
padding: 2em;
}
body > div.book, body > div.article, body > div.set, body > div.preface, body > div.chapter, body > div.section, body > div.appendix, body > div.part, body > div.index {
background-color: #FF;
margin: 40px auto 4em;
padding: 1px 40px 20px 30px;
}
@media (max-width: 1024px) {
body > div.book, body > div.article, body > div.set, body > div.preface, body > div.chapter, body > div.section, body > div.appendix, body > div.part, body > div.index {
max-width: 45em;
}
}
@media (min-width: 1025px) {
body > div.book, body > div.article, body > div.set, body > div.preface, body > div.chapter, body > div.section, body > div.appendix, body > div.part, body > div.index {
max-width: 70em;
}
}
@media (max-width: 5in), (max-device-width: 5in) {
body > div.book, body > div.article, body > div.set, body > div.preface, body > div.chapter, body > div.section, body > div.appendix, body > div.part, body > div.index {
max-width: 100%;
}
}
hr {
border-top: 1px dotted #808080;
margin: 0;
}
a:link {
color: #0035C7;
text-decoration: none;
}
a:visited {
color: #00207A;
text-decoration: none;
}
a:link:hover {
color: #00207A;
text-decoration: underline;
}
code {
font-family: "liberation mono","bitstream vera mono","dejavu mono",monospace;
font-weight: bold;
word-wrap: break-word;
}
h1 {
color: #C70036;
line-height: 1.1em;
}
h2, h3, h4, h5, h6 {
color: #C70036;
}
@media (max-width: 5in), (max-device-width: 5in){
dl, dt, dd {
margin-left: 0.25em;
}
ul, ol {
padding-left: 1.5em;
}
}
/* for first page */
.book > .titlepage h1.title {
text-align: center;
}
.titlepage h1.title {
text-align: left;
}
.authorgroup div {
text-align: center;
}
/* table in content */
.informaltable table {
border: 1px solid #AA;
}
.informaltable table th {
border-width: 0;
background-color: #C70036;
}
.informaltable table td {
border-width: 0;
}
.informaltable tbody tr:nth-child(even) {
background-color:#DD;
}
.informaltable tbody tr:hover {
background-color:#66;
color: #FF;
}
/* Terminal examples */
pre.screen {
-moz-tab-size: 4;
background-color: #F5F5F5;
border-radius: 11px 11px 11px 11px;
border-style: none;
box-shadow: 0 2px 5px #AA inset;
color: #00;
display: block;
font-family: "liberation mono","bitstream vera mono","dejavu mono",monospace;
font-size: 0.9em;
margin-bottom: 1em;
padding: 0.5em 1em;
page-break-inside: avoid;
white-space: pre-wrap;
word-wrap: break-word;
}
/* Navigation elements */
.navheader a, .navfooter a {
opacity: 0.50;
transition: opacity 0.15s ease-in-out;
}
.navheader a:hover, .navfooter a:hover {
opacity: 1;
}
.navheader, .navfooter {
background-image: url('images/draft.png');
background-repeat: no-repeat;
background-position: top left
Bug#772963: release-notes: cellphone friendly CSS
Hi, Osamu, [...] Is there any chance to get access to the docbook-xml (source) file, as a draft, at least? [...] > Basically, any part of HTML generation definitions in the packaged conversion > scheme can be overridden by the user. > > Normal customization xslt file in the source of documentation starts off > like: ... after some standard lines ... > href="file:///usr/share/xml/docbook/stylesheet/docbook-xsl/xhtml-1_1/chunk.xsl"/> I guess you mean "stylesheet" when you refer to customization xslt file, don't you? You usually use the element, or even the element to use external rules and declarations in your base stylesheet. I haven't checked it with docbook-xml, but in XML the reference to the stylesheet is usually done via (at least when we talk about a client-based transformation) By the way, in Debian-doc, is it done client-based or server-based (using php)? > > let's see it. > > It import chunk-common.xsl which seems to be the one making , , > etc. > > All you need is to create a customized chunk-common.xsl and import it to your > customization xslt file in the source of documentation before chunk.xsl so > the customized definition wins over default one. Again, I haven't checked that issue with docbook5-xml yet (I understand that "source of documentation" refers to the docbook-xml source), but in XSLT, in the case of template rules having the same "match" attribute, the local template rules, which are those declared in your base stylesheet, override the imported ones. If you want to use the imported rules in addition to those declared in your base stylesheet, you have to use . [...] > But I think this is not something we should do for this late in the freeze > time. Let's stick with simple CSS only fix for now. Yes, I agree to that. > > Also, if Stephan Beck docbook-xml can be improved for its HTML, submitting > bug report to the upstream of docbook-xml may be good idea. Well, not to use tables as a layout element is laid down in (1), (2), (3), for instance, and it reminds me of the early st(ages) of the web when everything was done using tables. I guess, it's a question of authoring, not one of the docbook-xml package, but I'm not quite sure about that. Moreover, I have decided to use the fairly new docbook5-xml which differs considerably from docbook-xml (4.xx), well, that's what the .doc says. I will check the possibilities for XSLT processing and (X)HTML output generation docbook5-xml ships with, and may suggest a way for getting rid of too much tables, or maybe not. > > Osamu > (1)http://www.w3.org/TR/2009/NOTE-mwbp-guidelines-20091020/ CH. 3.28 (2) http://www.w3.org/TR/2008/REC-mobileOK-basic10-tests-20081208/ Chs. 3.22, 3.23 (3) http://css4you.de (German) Stephan signature.asc Description: OpenPGP digital signature
Bug#772963: release-notes: cellphone friendly CSS
Hi, Stéphane, >> The first quick and dirty solution (only touching the .html file) is to >> suppress >> the second table row in the.html file. > > The solution I provided is CSS only. If we need to change the HTML, I > think your second solution (removing the table) is a better one. Well, it (the second one) was just a suggestion, not a solution. It works with 320x480 as one of the most common small screen sizes. I have tested some other screen sizes and my suggestion is not working that fine there, I admit. I retract it for the moment, expecting to give it another try or throw it in the garbage pale :-) > Do you want I host your patch, so it will be easy to everyone to view > your version? Thank you, but it should be revised first. Cheers, Stephan Beck signature.asc Description: OpenPGP digital signature
Bug#772963: release-notes: cellphone friendly CSS
Hi, Niels, > > The main problem with changing the HTML is that it is mostly generated > beyond our control. So far I managed to extend the existing HTML using > "supported" hooks for the given cases, but I fear this table might not > have such a hook. > Disclaimer, I know nothing more about docbook-xml than I can google - > by all means, feel free to prove me wrong. I have started working with docbook5-xml some time ago. It might take me some time to prove you wrong, though ;-) What I forgot to ask (you) all along this thread is: Is there any chance to get access to the original docbook-xml file of the Release notes (as a draft)? It would be a nice chance to keep practising, even if it takes me a while. I've been doing it with some remorse, lately, as I still have to get that tag description translation work done, for, ehm, the lintian maintainer. :-) Regards Stephan signature.asc Description: OpenPGP digital signature
Bug#772963: release-notes: cellphone friendly CSS
Hi, Am 21.01.2015 um 09:10 schrieb W. Martin Borgert: > On 2015-01-21 01:23, Stéphane Blondon wrote: >> Demos are temporary available : [...] > > 2. I find the icons (esp. the house icon, but also the arrows) >too old-fashioned and too large. Not sure, whether there is >anything more "modern" and slim, however. > After looking at some designs of arrows and house/home icons which did not satisfy me, I have drafted a new design for both the arrow and the home icons (please find attached the new .png draft files). Well, it's a somewhat reductional design (particularly, in the case of the home icon) that, in my opinion, has a modern and slim touch, but I don't know what you think about it. It's just a draft and there has to be done some more work concerning details (background, maybe the size as well), but before going on, I'd like to hear your comments. And, Stéphane, this time you may integrate it into the html file(s) and publish it, if you like. I have a website, too, but the provider does not support the scp command, and I am not willing to use simple ftp transfer anymore, so I'm a bit stuck with that issue at the moment. I guess, I have to look for a new provider. Cheers, Stephan Beck signature.asc Description: OpenPGP digital signature
Bug#778348: [release-notes] fixed some typos in release-notes-libv8.patch
Package: release-notes Hi, I've fixed some typos in Michael Gilbert's patch. Please find attached the .diff Best regards Stephan Beck Index: /home/knoppix/project2/release-notes-libv8.patch === --- /home/knoppix/project2/release-notes-libv8.patch (Revision 1) +++ /home/knoppix/project2/release-notes-libv8.patch (Arbeitskopie) @@ -7,7 +7,7 @@ + +Lack of security support for the ecosystem around libv8 and nodejs + -+ nodejs is built on top of libv8, which recieves a high volume of ++ nodejs is built on top of libv8, which receives a high volume of + security issues but there are currently no volunteers within the + project or the security team sufficiently interested and willing + to spend the large amount of time required to stem those incoming @@ -19,7 +19,7 @@ + untrusted content, for example unsanitized data from the internet. + + -+ In addition, these packages will not recieve any security updates ++ In addition, these packages will not receive any security updates + during the lifetime of the jessie release. + + signature.asc Description: OpenPGP digital signature
Bug#778348: [release-notes] release-notes:document security status for libv8/nodejs in jessie - added missing tag
Package: release-notes Hi, I added a missing tag twice and revised punctuation. What I don't know is if the occurrence of "jessie" requires another tag to be inserted. Please find attached the diff of the patch as 0002-en-issues-Document-lack-of-security-support-for-Node.patch Good night Stephan Beck Index: /home/knoppix/project3/0001-en-issues-Document-lack-of-security-support-for-Node.patch === --- /home/knoppix/project3/0001-en-issues-Document-lack-of-security-support-for-Node.patch (Revision 1) +++ /home/knoppix/project3/0001-en-issues-Document-lack-of-security-support-for-Node.patch (Arbeitskopie) @@ -1,4 +1,4 @@ ->From b4a2d1c275bf871705d53b4861c1dd26f568f2c8 Mon Sep 17 00:00:00 2001 +>From b4a2d1c275bf871705d53b4861c1dd26f568f2c8 Mon Sep 17 00:00:00 2001 From: nthykier Date: Mon, 16 Feb 2015 08:07:01 + Subject: [PATCH 1/2] en/issues: Document lack of security support for Node.js @@ -24,10 +24,10 @@ + -+Lack of security support for the ecosystem around libv8 and Node.js ++Lack of security support for the ecosystem around libv8 and Node.js + -+ The Node.js platform is built on top of libv8, which receives a -+ high volume of security issues but there are currently no ++ The Node.js platform is built on top of libv8, which receives a ++ high volume of security issues, but there are currently no + volunteers within the project or the security team sufficiently + interested and willing to spend the large amount of time required + to stem those incoming issues. @@ -35,7 +35,7 @@ + + Unfortunately, this means that libv8, nodejs, and the associated node-* ++ role="package">nodejs and the associated node-* + package ecosystem should not currently be used with untrusted + content, for example unsanitized data from the internet. + signature.asc Description: OpenPGP digital signature
Bug#772963: release-notes: cellphone friendly CSS
Hi, Stéphane, Am 17.02.2015 um 01:04 schrieb Stéphane Blondon: > > I uploaded them at: > http://stephane.yaal.fr/tmp/release-notes.amd64.html.sbeck/index.en.html Thanks, very kind of you. > > I think they are not well integrated with the others icons and the > rest of the CSS. Well, they have been designed without glancing at the stylesheets and images available in /usr/share/xml/docbook/stylesheet/docbook-xsl-ns/images, that's true, and they may not fit too well in the pictorial imagery used there. I came across Martin Borgert's comment and focused on "modern and slim". On the other hand, they don't come up to their inherent "aesthetics" on this draft background. Anyway, they are just a suggestion. (However if people think they are better, commit them > instead of the current ones.) Let's wait for other comments. Anyway, I think I don't have r/w access to the referred svn directory, do I? > > The 'home' icon is confusing: it's an 'up' arrow so it means more 'go > to the top of the page' than 'go to home page'. Indeed, but any house with a sloping roof, particularly saddle or gable roof, looks like an arrow pointing upwards, if you look at it freely enough, with imagination, without being permuted by too many predefined concepts. This is what I meant with "a somewhat reductional" design. The house is made up of the arrow forms. But the roof's slope may be increased so that it is not equal to the slope of the arrows. >> I have a website, too, but the provider does not support the >> scp command, and I am not willing to use simple ftp transfer anymore > > If your concerns with the FTP protocol is security, perhaps your > provider accepts FTPS or SFTP? Thanks, I'll check this. I'd prefer ssh using the scp command, but that was not possible the last time I wanted to upload content. signature.asc Description: OpenPGP digital signature
Bug#771925: [release-notes] Add a note of base-passwd hardening shell on backup user - reviewed (corrected some typos and spaces)
Package: release-notes --- Please enter the report below this line. --- Hi Niels, I reviewed the patch and corrected some typos and spaces. Moreover, I'd prefer to use ..."corresponding" instead of "necessary" in the "If your local setup requires..." sentence, merely a question of style, though. Take it or leave it :-) Attached you'll find the diff of the patch. I renamed it using 0002-... I hope that's ok. Regards Stephan Beck Index: 0001-en-issues-Document-the-base-password-shell-reset.patch === --- 0001-en-issues-Document-the-base-password-shell-reset.patch (Revision 1) +++ 0001-en-issues-Document-the-base-password-shell-reset.patch (Arbeitskopie) @@ -23,7 +23,7 @@ + base-passwd + +The upgrade of base-passwd -+package will reset the shell of system users that is provides to ++package will reset the shell of system users that is provided to +the "nologin" shell. This includes the following users: + + @@ -79,13 +79,13 @@ + +If your local setup requires that any of these users have a shell, +you should say no to migrating or migrate and then change the shell -+of the necessary users. Notable examples includes local backups ++of the corresponding users. Notable examples include local backups +done via the "backup" user with an "ssh-key" authentication. + + + + The migration will happen automatically if your debconf question -+ priorty is "high" or above. ++ priority is "high" or above. + + + @@ -98,7 +98,7 @@ + +Where username is the name of the user +in question and current-shell-mangled -+is the mangled name of the shell. The mangling is done by ++is the mangled name of the shell. The mangling is done by +replacing all non-alphanumerical, non-dashes and non-underscores +with underscores. E.g. /bin/bash becomes _bin_bash. + signature.asc Description: OpenPGP digital signature
Bug#772963: release-notes: cellphone friendly CSS
Hi, Stéphane, Am 18.02.2015 um 01:42 schrieb Stéphane Blondon: [...] > In case it's easier to apply my patches, I setted up a repository on GitHub: > https://github.com/sblondon/release-notes/tree/cellphone-css > > It's a clone of Niels's git repository. The files are added into the > cellphone-css branch. > > With this last patch, I think the main needs are filled but I remember > the warning from Google test suite about the use on small screen. > I will probably check that during the week or next week-end. > > since I am involved in other things as, for instance, my tag description translation work and other stuff, I opt out of participating in this particular thread/issue. I hope you don't mind. Regards Stephan signature.asc Description: OpenPGP digital signature
