Bug#634166: go language support
Package: exuberant-ctags
Severity: wishlist
Tags: patch
Could you please apply the attached patch which was picked from an
unofficial fork at https://github.com/lyosha/ctags-go (maintained by
Alexey Marinichev)? The patch seems fairly clean, I've tested it
without any problem.
FYI, here is the relevant commit:
https://github.com/lyosha/ctags-go/commit/ca097bd639e35470a9abccbf348016b7cc44f811
Thanks,
--
roktas
diff --git a/go.c b/go.c
new file mode 100644
index 000..6bd3a36
--- /dev/null
+++ b/go.c
@@ -0,0 +1,670 @@
+/*
+* INCLUDE FILES
+*/
+#include general.h/* must always come first */
+#include setjmp.h
+
+#include debug.h
+#include entry.h
+#include keyword.h
+#include read.h
+#include main.h
+#include routines.h
+#include vstring.h
+#include options.h
+
+/*
+ * MACROS
+ */
+#define isType(token,t) (boolean) ((token)-type == (t))
+#define isKeyword(token,k) (boolean) ((token)-keyword == (k))
+
+/*
+ * DATA DECLARATIONS
+ */
+
+typedef enum eException { ExceptionNone, ExceptionEOF } exception_t;
+
+typedef enum eKeywordId {
+ KEYWORD_NONE = -1,
+ KEYWORD_package,
+ KEYWORD_import,
+ KEYWORD_const,
+ KEYWORD_type,
+ KEYWORD_var,
+ KEYWORD_func,
+ KEYWORD_struct,
+ KEYWORD_interface,
+ KEYWORD_map,
+ KEYWORD_chan
+} keywordId;
+
+/* Used to determine whether keyword is valid for the current language and
+ * what its ID is.
+ */
+typedef struct sKeywordDesc {
+ const char *name;
+ keywordId id;
+} keywordDesc;
+
+typedef enum eTokenType {
+ TOKEN_NONE = -1,
+ TOKEN_CHARACTER,
+ // Don't need TOKEN_FORWARD_SLASH
+ TOKEN_FORWARD_SLASH,
+ TOKEN_KEYWORD,
+ TOKEN_IDENTIFIER,
+ TOKEN_STRING,
+ TOKEN_OPEN_PAREN,
+ TOKEN_CLOSE_PAREN,
+ TOKEN_OPEN_CURLY,
+ TOKEN_CLOSE_CURLY,
+ TOKEN_OPEN_SQUARE,
+ TOKEN_CLOSE_SQUARE,
+ TOKEN_SEMICOLON,
+ TOKEN_STAR,
+ TOKEN_LEFT_ARROW,
+ TOKEN_DOT,
+ TOKEN_COMMA
+} tokenType;
+
+typedef struct sTokenInfo {
+ tokenType type;
+ keywordId keyword;
+ vString *string; /* the name of the token */
+ unsigned long lineNumber; /* line number of tag */
+ fpos_t filePosition; /* file position of line containing name */
+} tokenInfo;
+
+/*
+* DATA DEFINITIONS
+*/
+
+static int Lang_go;
+static jmp_buf Exception;
+static vString *scope;
+
+typedef enum {
+ GOTAG_UNDEFINED = -1,
+ GOTAG_PACKAGE,
+ GOTAG_FUNCTION,
+ GOTAG_CONST,
+ GOTAG_TYPE,
+ GOTAG_VAR,
+} goKind;
+
+static kindOption GoKinds[] = {
+ {TRUE, 'p', package, packages},
+ {TRUE, 'f', func, functions},
+ {TRUE, 'c', const, constants},
+ {TRUE, 't', type, types},
+ {TRUE, 'v', var, variables}
+};
+
+static keywordDesc GoKeywordTable[] = {
+ {package, KEYWORD_package},
+ {import, KEYWORD_import},
+ {const, KEYWORD_const},
+ {type, KEYWORD_type},
+ {var, KEYWORD_var},
+ {func, KEYWORD_func},
+ {struct, KEYWORD_struct},
+ {interface, KEYWORD_interface},
+ {map, KEYWORD_map},
+ {chan, KEYWORD_chan}
+};
+
+/*
+* FUNCTION DEFINITIONS
+*/
+
+// XXX UTF-8
+static boolean isIdentChar (const int c)
+{
+ return (boolean)
+ (isalpha (c) || isdigit (c) || c == '$' ||
+ c == '@' || c == '_' || c == '#' || c 128);
+}
+
+static void initialize (const langType language)
+{
+ size_t i;
+ const size_t count =
+ sizeof (GoKeywordTable) / sizeof (GoKeywordTable[0]);
+ Lang_go = language;
+ for (i = 0; i count; ++i)
+ {
+ const keywordDesc *const p = GoKeywordTable[i];
+ addKeyword (p-name, language, (int) p-id);
+ }
+}
+
+static tokenInfo *newToken (void)
+{
+ tokenInfo *const token = xMalloc (1, tokenInfo);
+ token-type = TOKEN_NONE;
+ token-keyword = KEYWORD_NONE;
+ token-string = vStringNew ();
+ token-lineNumber = getSourceLineNumber ();
+ token-filePosition = getInputFilePosition ();
+ return token;
+}
+
+static void deleteToken (tokenInfo * const token)
+{
+ if (token != NULL)
+ {
+ vStringDelete (token-string);
+ eFree (token);
+ }
+}
+
+/*
+ * Parsing functions
+ */
+
+static void parseString (vString *const string, const int delimiter)
+{
+ boolean end = FALSE;
+ while (!end)
+ {
+ int c = fileGetc ();
+ if (c == EOF)
+ end = TRUE;
+ else if (c == '\\' delimiter != '`')
+ {
+ c = fileGetc (); /* This maybe a ' or . */
+ vStringPut (string, c);
+ }
+ else if (c == delimiter)
+ end = TRUE;
+ else
+ vStringPut (string, c);
+ }
+ vStringTerminate (string);
+}
+
+static void parseIdentifier (vString *const string, const int firstChar)
+{
+ int c = firstChar;
+ //Assert (isIdentChar (c));
+ do
+ {
+ vStringPut (string, c);
+ c = fileGetc ();
+ } while (isIdentChar (c));
+ vStringTerminate (string);
+ fileUngetc (c); /* always unget, LF might add a semicolon */
+}
+
+static void readToken (tokenInfo *const token)
+{
+ int c;
+ static tokenType lastTokenType = TOKEN_NONE;
+
+ token-type = TOKEN_NONE;
+ token-keyword = KEYWORD_NONE;
+ vStringClear (token-string);
+
+getNextChar:
+ do
+ {
+ c = fileGetc ();
+ token-lineNumber = getSourceLineNumber ();
+ token-filePosition = getInputFilePosition ();
+ if (c == '\n' (lastTokenType == TOKEN_IDENTIFIER ||
+ lastTokenType ==
Bug#556744: ikiwiki: (incomplete) Turkish translation
Package: ikiwiki Version: 3.1415926 Severity: wishlist Tags: patch l10n please find it attched. -- roktas # Turkish translation for ikiwiki. # This file is distributed under the same license as the ikiwiki package. # Recai Oktaş rok...@debian.org, 2009. msgid msgstr Project-Id-Version: ikiwiki 3.20091031\n Report-Msgid-Bugs-To: \n POT-Creation-Date: 2009-10-23 12:40-0400\n PO-Revision-Date: 2009-11-08 03:04+0200\n Last-Translator: Recai Oktaş rok...@debian.org\n Language-Team: Turkish debian-l10n-turk...@lists.debian.org\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n #: ../IkiWiki/CGI.pm:113 msgid You need to log in first. msgstr Önce sisteme giriş yapmanız gerekiyor. #: ../IkiWiki/CGI.pm:146 msgid probable misconfiguration: sslcookie is set, but you are attempting to login via http, not https msgstr #: ../IkiWiki/CGI.pm:149 msgid login failed, perhaps you need to turn on cookies? msgstr #: ../IkiWiki/CGI.pm:168 ../IkiWiki/CGI.pm:313 msgid Your login session has expired. msgstr #: ../IkiWiki/CGI.pm:189 msgid Login msgstr Giriş #: ../IkiWiki/CGI.pm:190 msgid Preferences msgstr Tercihler #: ../IkiWiki/CGI.pm:191 msgid Admin msgstr Yönet #: ../IkiWiki/CGI.pm:231 msgid Preferences saved. msgstr Tercihler kaydedildi. #: ../IkiWiki/CGI.pm:277 msgid You are banned. msgstr #: ../IkiWiki/CGI.pm:404 ../IkiWiki/CGI.pm:405 ../IkiWiki.pm:1282 msgid Error msgstr Hata #: ../IkiWiki/Plugin/aggregate.pm:84 msgid Aggregation triggered via web. msgstr #: ../IkiWiki/Plugin/aggregate.pm:93 msgid Nothing to do right now, all feeds are up-to-date! msgstr #: ../IkiWiki/Plugin/aggregate.pm:220 #, perl-format msgid missing %s parameter msgstr %s parametresi eksik #: ../IkiWiki/Plugin/aggregate.pm:255 msgid new feed msgstr yeni özet akışı #: ../IkiWiki/Plugin/aggregate.pm:269 msgid posts msgstr gönderi #: ../IkiWiki/Plugin/aggregate.pm:271 msgid new msgstr yeni #: ../IkiWiki/Plugin/aggregate.pm:441 #, perl-format msgid expiring %s (%s days old) msgstr %s için zaman aşımı (%s gün eski) #: ../IkiWiki/Plugin/aggregate.pm:448 #, perl-format msgid expiring %s msgstr %s için zaman aşımı #: ../IkiWiki/Plugin/aggregate.pm:475 #, perl-format msgid last checked %s msgstr son güncelleme: %s #: ../IkiWiki/Plugin/aggregate.pm:479 #, perl-format msgid checking feed %s ... msgstr %s özet akışı denetleniyor ... #: ../IkiWiki/Plugin/aggregate.pm:484 #, perl-format msgid could not find feed at %s msgstr %s özet akışı bulunamadı #: ../IkiWiki/Plugin/aggregate.pm:503 msgid feed not found msgstr özet akışı bulunamadı #: ../IkiWiki/Plugin/aggregate.pm:514 #, perl-format msgid (invalid UTF-8 stripped from feed) msgstr (geçersiz UTF-8 dizgisi özet akışından çıkarıldı) #: ../IkiWiki/Plugin/aggregate.pm:522 #, perl-format msgid (feed entities escaped) msgstr (özet akışı girdileri işlendi) #: ../IkiWiki/Plugin/aggregate.pm:530 msgid feed crashed XML::Feed! msgstr özet akışı XML::Feed'in çakılmasına yol açtı! #: ../IkiWiki/Plugin/aggregate.pm:616 #, perl-format msgid creating new page %s msgstr %s için yeni sayfa oluşturuluyor #: ../IkiWiki/Plugin/amazon_s3.pm:31 msgid deleting bucket.. msgstr #: ../IkiWiki/Plugin/amazon_s3.pm:38 ../ikiwiki.in:206 msgid done msgstr #: ../IkiWiki/Plugin/amazon_s3.pm:97 #, perl-format msgid Must specify %s msgstr #: ../IkiWiki/Plugin/amazon_s3.pm:136 msgid Failed to create S3 bucket: msgstr #: ../IkiWiki/Plugin/amazon_s3.pm:221 msgid Failed to save file to S3: msgstr #: ../IkiWiki/Plugin/amazon_s3.pm:243 msgid Failed to delete file from S3: msgstr #: ../IkiWiki/Plugin/attachment.pm:49 #, perl-format msgid there is already a page named %s msgstr #: ../IkiWiki/Plugin/attachment.pm:65 msgid prohibited by allowed_attachments msgstr #: ../IkiWiki/Plugin/attachment.pm:140 msgid bad attachment filename msgstr #: ../IkiWiki/Plugin/attachment.pm:182 msgid attachment upload msgstr #: ../IkiWiki/Plugin/autoindex.pm:105 msgid automatic index generation msgstr #: ../IkiWiki/Plugin/blogspam.pm:108 msgid Sorry, but that looks like spam to a href=\http://blogspam.net/; \blogspam/a: msgstr #: ../IkiWiki/Plugin/brokenlinks.pm:38 #, perl-format msgid %s from %s msgstr #: ../IkiWiki/Plugin/brokenlinks.pm:46 msgid There are no broken links! msgstr #: ../IkiWiki/Plugin/comments.pm:124 ../IkiWiki/Plugin/format.pm:38 #, perl-format msgid unsupported page format %s msgstr #: ../IkiWiki/Plugin/comments.pm:129 msgid comment must have content msgstr #: ../IkiWiki/Plugin/comments.pm:185 msgid Anonymous msgstr #: ../IkiWiki/Plugin/comments.pm:340 ../IkiWiki/Plugin/editpage.pm:97 msgid bad page name msgstr #: ../IkiWiki/Plugin/comments.pm:345 #, perl-format msgid commenting on %s msgstr #: ../IkiWiki/Plugin/comments.pm:363 #, perl-format msgid page '%s' doesn't exist, so you can't comment msgstr #: ../IkiWiki/Plugin/comments.pm:370 #, perl-format msgid comments on page '%s' are closed msgstr #: ../IkiWiki/Plugin
Bug#533648: ikiwiki: allow automator to just only dump the generated setup without performing a full setup
Package: ikiwiki
Version: 3.141
Severity: wishlist
Tags: patch
Hi Joey,
I have a few projects which are already in Git repositories, so I don't
want the Automator to create repositories (via ikiwiki-makerepo). Could it
be possible to split the import subroutine to just only dump the generated
setup without performing a full setup? The attached patch is a first
attempt for this feature.
--
roktas
From 9fa79b9cbdb72ae7a1e596bac399965fb1fab879 Mon Sep 17 00:00:00 2001
From: =?utf-8?q?Recai=20Okta=C5=9F?= rok...@debian.org
Date: Fri, 19 Jun 2009 17:40:19 +0300
Subject: allow automator to just only dump the generated setup without performing a full setup
- use 'dump' (instead of 'import'), e.g.
IkiWiki::Setup::Automator-dump(...)
- dumps to STDOUT if $config{dumpsetup} is not defined
---
IkiWiki/Setup.pm | 14 ++
IkiWiki/Setup/Automator.pm | 18 --
2 files changed, 26 insertions(+), 6 deletions(-)
diff --git a/IkiWiki/Setup.pm b/IkiWiki/Setup.pm
index 6ee1120..44632f1 100644
--- a/IkiWiki/Setup.pm
+++ b/IkiWiki/Setup.pm
@@ -108,14 +108,20 @@ sub getsetup () {
}
sub dump ($) {
- my $file=IkiWiki::possibly_foolish_untaint(shift);
+ my $file=shift;
require IkiWiki::Setup::Standard;
my @dump=IkiWiki::Setup::Standard::gendump(Setup file for ikiwiki.);
- open (OUT, , $file) || die $file: $!;
- print OUT $_\n foreach @dump;
- close OUT;
+ if (defined $file) {
+ $file=IkiWiki::possibly_foolish_untaint($file);
+ open (OUT, , $file) || die $file: $!;
+ print OUT $_\n foreach @dump;
+ close OUT;
+ }
+ else {
+ print $_\n foreach @dump;
+ }
}
1
diff --git a/IkiWiki/Setup/Automator.pm b/IkiWiki/Setup/Automator.pm
index 742d676..20b9155 100644
--- a/IkiWiki/Setup/Automator.pm
+++ b/IkiWiki/Setup/Automator.pm
@@ -24,7 +24,7 @@ sub prettydir ($) {
return $dir;
}
-sub import (@) {
+sub gensetup (@) {
my $this=shift;
IkiWiki::Setup::merge({...@_});
@@ -36,7 +36,7 @@ sub import (@) {
# Avoid overwriting any existing files.
foreach my $key (qw{srcdir destdir repository dumpsetup}) {
- next unless exists $config{$key};
+ next unless defined $config{$key};
my $add=;
my $dir=IkiWiki::dirname($config{$key})./;
my $base=IkiWiki::basename($config{$key});
@@ -74,6 +74,20 @@ sub import (@) {
}
IkiWiki::checkconfig();
+}
+
+sub dump (@) {
+ gensetup(@_);
+
+ # Generate setup file.
+ require IkiWiki::Setup;
+ IkiWiki::Setup::dump($config{dumpsetup});
+
+ exit 0;
+}
+
+sub import (@) {
+ gensetup(@_);
print \n\nSetting up $config{wikiname} ...\n;
--
1.6.2.4
Bug#529263: FTBFS with GCC 4.4: missing #include
[Rail: you forgot to mention that you fixed #529272 in the changelog of mozzemberek-0.1.2-2, closing the bug via BTS.] * Rail Aliev [2009-05-18 14:45:00+0400] On Monday 18 May 2009 14:05:37 Martin Michlmayr wrote: Package: zpspell Version: 0.4.2-4 User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.4 Tags: patch Your package fails to build with GCC 4.4, which has cleaned up some more C++ headers. You always have to #include headers directly and cannot rely for things to be included indirectly. Martin, Thanks a lot for the patch. The upstream version has fixed this bug already. To be fixed in the next upload. Recai, Could you pull the changes from bzr.debian.org and reupload this package? Done (#529263). * Rail Aliev [2009-05-18 15:39:37+0400] On Monday 18 May 2009 15:23:43 Martin Michlmayr wrote: Package: mozzemberek Version: 0.1.1-3 User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.4 Your package fails to build with GCC 4.4, which has cleaned up some more C++ headers. You always have to #include headers directly and cannot rely for things to be included indirectly. You can reproduce this problem with gcc-4.4/g++-4.4 from unstable. I guess you know about this too? Yes, already fixed in upstream. Recai, Could you upload a new version? Done (#529272). -- roktas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509200: [INTL:tr] Turkish debconf-po file for ppp
Package: ppp Severity: wishlist Tags: l10n patch Hi, Please find attached the Turkish debconf templates translation. Thanks to Deniz Bahadir Gur. -- roktas tr.po.gz Description: Binary data
Bug#505924: ITP: cwm -- a lightweight and efficient window manager for X11
Package: wnpp Severity: wishlist Owner: Recai Oktaş [EMAIL PROTECTED] * Package name: cwm Version : 20081115 (CVS snapshot) Upstream Authors: Marius Aamodt Eriksen [EMAIL PROTECTED] Andy Adamson [EMAIL PROTECTED] et al. * URL : http://xenocara.org/ * License : BSD Programming Lang: C Description : a lightweight and efficient window manager for X11 cwm (calmwm) is a window manager for X11 which contains many features that concentrate on the efficiency and transparency of window management. It also aims to maintain the simplest and most pleasant aesthetic. cwm has been developed by the OpenBSD developers and comes as part of the OpenBSD base system. P.S. An early release can be found at: http://people.debian.org/~roktas/packages/cwm_20081115-1_i386.deb Git repository for the package: http://git.00101010.info/?p=debcwm.git -- roktas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493139: iso-scan: Allow using shell patterns to select ISO images
* Recai Oktaş [2008-07-31 23:16:43+0300] * Joey Hess [2008-07-31 14:05:22-0400] Recai Oktaş wrote: The following patch allows one to select ISO images in iso-scan. With this patch grub configurations as exampled below can be used to perform an i386 or amd64 hd-media installation: iso-scan already checks what architecture the iso is for. Why do you need a second, filename-based architecture check? Did you mean the ISO selection logic in register_cd (which I'm not aware of)? If so, forget my patch[1]. My previous attempts to use multiple ISOs had been failed, probably for unrelated reasons. I'll make a new test and let you know. Ok, I've managed to make i386 and am64 installations from an external hdd containing multiple ISOs (great!). My previous failed attempts must be related to incorrect ISOs. Feel free to close this bug report. Sorry for the fuss! -- roktas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493139: iso-scan: Allow using shell patterns to select ISO images
Package: iso-scan
Severity: wishlist
Tags: patch
The following patch allows one to select ISO images in iso-scan. With this
patch grub configurations as exampled below can be used to perform an i386
or amd64 hd-media installation:
title New Debian Installation - i386
root (hd0,0)
kernel (hd0,0)/images/i386/hd-media/vmlinuz iso-scan/files=*i386*.iso
initrd (hd0,0)/images/i386/hd-media/initrd.gz
title New Debian Installation - amd64
root (hd0,0)
kernel (hd0,0)/images/amd64/hd-media/vmlinuz iso-scan/files=*amd64*.iso
initrd (hd0,0)/images/amd64/hd-media/initrd.gz
Note that, the patch preserves the current behaviour.
--
roktas
diff --git a/packages/iso-scan/debian/iso-scan.postinst b/packages/iso-scan/debian/iso-scan.postinst
index da354cc..80b4a3f 100755
--- a/packages/iso-scan/debian/iso-scan.postinst
+++ b/packages/iso-scan/debian/iso-scan.postinst
@@ -112,6 +112,10 @@ modprobe loop /dev/null || true
mkdir /cdrom 2/dev/null || true
mkdir /hd-media 2/dev/null || true
+db_get iso-scan/files || RET=''
+ISO_FILES=${RET:-'*.[iI][sS][oO]'}
+log Using '$ISO_FILES' pattern for ISO files.
+
log First pass: Look for ISOs near top-level of each filesystem.
DEVS=$(list-devices partition; list-devices disk; list-devices maybe-usb-floppy)
# Repeat twice if necessary, to accomodate devices that need some
@@ -145,12 +149,14 @@ for i in 1 2; do
fi
db_subst iso-scan/progress_scan DIRECTORY $dir/
db_progress INFO iso-scan/progress_scan
-for iso in $dir/*.iso $dir/*.ISO; do
- if [ -e $iso ]; then
- log Found ISO $iso on $dev
- ISO_COUNT=$(expr $ISO_COUNT + 1)
- try_iso $iso $dev
- fi
+for pattern in $ISO_FILES; do
+ for iso in $dir/$pattern; do
+ if [ -e $iso ]; then
+ log Found ISO $iso on $dev
+ ISO_COUNT=$(expr $ISO_COUNT + 1)
+ try_iso $iso $dev
+ fi
+ done
done
fi
done
Bug#493139: iso-scan: Allow using shell patterns to select ISO images
* Joey Hess [2008-07-31 14:05:22-0400] Recai Oktaş wrote: The following patch allows one to select ISO images in iso-scan. With this patch grub configurations as exampled below can be used to perform an i386 or amd64 hd-media installation: iso-scan already checks what architecture the iso is for. Why do you need a second, filename-based architecture check? Did you mean the ISO selection logic in register_cd (which I'm not aware of)? If so, forget my patch[1]. My previous attempts to use multiple ISOs had been failed, probably for unrelated reasons. I'll make a new test and let you know. [1] The only sane reason to keep this patch could be that a netinst or a full CD ISO could be selected. But this is not my original intention in the first place and I'm unsure whether it deserves to populate boot options with a new variable. -- roktas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#482079: libghc6-pcre-light-dev fails to install: workaround
* Luca Falavigna [2008-07-12 21:05:12+0200] Attached is a workaround for this issue: Thank you. Many thanks for the patch which (hopefully) resolved this issue that I haven't been able to deal with. I'm going to make a new upload. -- roktas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487465: gitweb: should open files (e.g. indextext.html) in utf8 mode
Package: gitweb
Version: 1:1.5.5.1-1
Severity: normal
Tags: patch
Subject says it all. In the current code, gitweb uses utf8 only in stdout.
As a result, included files like indextext.html appears garbled if it
contains utf8 characters. The attached patch works fine without any
observed side-effects.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (600, 'unstable'), (500, 'testing'), (450, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core)
Locale: LANG=tr_TR.UTF-8, LC_CTYPE=tr_TR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages gitweb depends on:
ii git-core 1:1.5.5.1-1 fast, scalable, distributed revisi
ii perl 5.10.0-10 Larry Wall's Practical Extraction
gitweb recommends no packages.
-- no debconf information
--
roktas
--- /usr/lib/cgi-bin/gitweb.cgi.orig 2008-06-22 00:51:53.0 +
+++ /usr/lib/cgi-bin/gitweb.cgi 2008-06-22 00:52:07.0 +
@@ -16,7 +16,7 @@
use Fcntl ':mode';
use File::Find qw();
use File::Basename qw(basename);
-binmode STDOUT, ':utf8';
+use open qw(:std :utf8);
BEGIN {
CGI-compile() if $ENV{'MOD_PERL'};
Bug#484834: [Fwd: Bug#484834: console-data: please drop trf (Turkish F layout) in the udeb]
Package: console-data Severity: wishlist Tags: d-i There are currently *two* Turkish keymaps proposed to users in Debian Installer. I think this is one too many..:-) Do you think we can safely drop one between trf and trq? Absolutely no... All other languages have only one keymap proposed in D-I (except pt_BR for which I asked the same question and fr, for which I'll remove the extra keymap) Christian, I'm not sure if I understood you correctly, but trf/trq is a completely different case and it would make no sense to compare the situtation with pt_BR and fr. Please note that these keymaps are the *console* keymaps. However, the default X keymap is derived from these ones: - if users choose trf in D-I, they'll get a tr keymap in X with f variant - if users choose trq in D-I, they'll get a tr keymap in X with q variant Please also note that the default when choosing Turkish as language is trq As a consequence, I consider removing the trf keymap from console-data udeb. Therefore, that keymap will no longer be offered in D-I. It will still be available in the regular console-data package, though. Note that, Turkish F is a different **layout** than Turkish Q. It's not just a 'variant' as misleadingly declared in X (perhaps for historical reasons, which is something we should also change): http://wiki.laptop.org/go/OLPC_Turkey_Keyboard There are actually plenty of trf users in Turkey, especially in the government offices. So I strongly disagree with this proposal. -- roktas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#472279: elog: should this package be removed?
[Also CC'ing to Nico... I've just noticed the response at #464902.] * Raphael Geissert [2008-03-22 20:37:35-0600] Source: elog Version: 2.6.3+r1764-1 Severity: serious User: [EMAIL PROTECTED] Usertags: proposed-removal Hi, While reviewing some packages, your package came up as a possible candidate for removal from Debian, because: * It has a RC bug * It has a history of security issues * last maintainer upload was on 2006 * It has almost no users * It is not part of etch and, as for now, won't be part of lenny * There's a new upstream release that is said to address the RC bug If you think that it should be orphaned instead of being removed from Debian, please reply to this bug and tell so. Sorry for the late response! I had already filed a bug report to orphan elog: #464902. However removing this package from the archives is also fine with me, unless someone willing to maintain it comes up. Best regards, -- roktas signature.asc Description: Digital signature
Bug#464901: ITP: pcre-light -- a lightweight GHC library for Perl 5 compatible regular expressions
Package: wnpp Severity: wishlist Owner: Recai Oktaş [EMAIL PROTECTED] * Package name: pcre-light Version : 0.3.1 Upstream Author : Don Stewart [EMAIL PROTECTED] * URL : http://www.example.org/ * License : BSD Programming Lang: Haskell Description : a lightweight GHC library for Perl 5 compatible regular expressions The PCRE library is a set of functions that implement regular expression pattern matching using the same syntax and semantics as Perl 5. P.S. This package is required for the syntax highlighting support of pandoc. -- roktas signature.asc Description: Digital signature
Bug#464902: O: elog
Package: wnpp Severity: normal Elog has some security issues. Due to the insufficient time I can't deal with all these issues in time. -- roktas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464920: ITP: highlighting-kate -- syntax highlighting library based on Kate syntax descriptions
Package: wnpp Severity: wishlist Owner: Recai Oktaş [EMAIL PROTECTED] * Package name: highlighting-kate Version : 0.1 Upstream Author : John MacFarlane [EMAIL PROTECTED] * URL : http://johnmacfarlane.net/highlighting-kate/ * License : GPL Programming Lang: Haskell Description : syntax highlighting library based on Kate syntax descriptions highlighting-kate is a syntax highlighting library with support for over 50 languages. The syntax parsers are automatically generated from Kate syntax descriptions, so any syntax supported by Kate can be added. An (optional) command-line program is provided, along with a utility for generating new parsers from Kate XML syntax descriptions. . Currently the following languages are supported: Ada, Asp, Awk, Bash, Bibtex, C, Cmake, Coldfusion, Commonlisp, Cpp, Css, D, Djangotemplate, Doxygen, Dtd, Eiffel, Erlang, Fortran, Haskell, Html, Java, Javadoc, Javascript, Json, Latex, Lex, LiterateHaskell, Lua, Makefile, Matlab, Mediawiki, Modula3, Nasm, Objectivec, Ocaml, Pascal, Perl, Php, Postscript, Prolog, Python, Rhtml, Ruby, Scala, Scheme, Sgml, Sql, SqlMysql, SqlPostgresql, Tcl, Texinfo, Xml, Xslt, Yacc. P.S. This library is needed for the syntax highlighting support of pandoc. -- roktas
Bug#445235: libghc6-pandoc-dev: the package fails to install
tags 445235 + fixed-upstream thanks -- roktas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392016: elog in stable is also vulnerable
* Ulf Harnhammar [2006-11-08 23:14:16+0100] I've just verified that elog in stable is vulnerable to all issues mentioned in bug #392016. Thank you very much for looking into this! I've got another report attached below. I'll look into this problem also and will keep this bug report open as I think elog should not enter to Etch due to all potential security issues which increase the work-load on our security team during the stable release cycle. --8--- FYI Hi, We are working with Mr. Stefan Ritt on this issue and waiting for the fix. Thanks, OS2A Forwarded Conversation Subject: ELOG Web Logbook Remote Denial of Service Vulnerability From: OS2A BTO [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Wed, Nov 8, 2006 at 6:12 PM Attachments: os2a_1008.txt Hi, We recently came across a Denial of Service vulnerability in ELOG's elogd server which allows attackers to crash the service, thereby preventing legitimate access. Attached is our security advisory which describes the vulnerability in detail. Please let us know the time you might require to fix this issue. And also let us know if you have any questions. A quick and positive response from your side would be highly appreciated. Thanks, OS2A Team. From: Stefan Ritt [EMAIL PROTECTED] To: OS2A BTO [EMAIL PROTECTED] Date: Wed, Nov 8, 2006 at 6:31 PM Dear OS2A team, thank you for reporting this vulnerability and for the detailed analysis, I really appreciate. I fixed this problem and just released version 2.6.2-7 (SVN revision 1746). Best regards, Stefan Ritt -- Dr. Stefan Ritt Phone: +41 56 310 3728 Paul Scherrer Institute FAX: +41 56 310 2199 OLGA/021 mailto:[EMAIL PROTECTED] CH-5232 Villigen PSI http://midas.psi.ch/~stefan [Quoted text hidden] ELOG Web Logbook Remote Denial of Service Vulnerability OS2A ID: OS2A_1008Status: 10/31/2006 Issue Discovered 11/08/2006 Reported to the Vendor -- Fixed by Vendor -- Advisory Released Class: Denial of Service Severity: Medium Overview: - The Electronic Logbook (ELOG) is part of a family of applications known as weblogs. ELOG is a remarkable implementation of a weblog in its simplicity of use and versatility. http://midas.psi.ch/elog/index.html Description: Remote exploitation of a denial of service vulnerability in ELOG's elogd server allows attackers to crash the service, thereby preventing legitimate access. The [global] section in configuration file elogd.cfg is used for settings common to all logbooks. The vulnerability is due to improper handling of an HTTP GET request if logbook name 'global' (or any logbook name prefixed with global) is used in the request. When such a request is received, a NULL pointer dereference occurs, leading to a crash of the service. Only authenticated users can exploit this vulnerability if the application is configured with password. Impact: --- Successful exploitation allows a remote attacker to crash the elogd server. Affected Software(s): - ELOG 2.6.2 and prior. Proof of Concept: - The HTTP GET request given below is sufficient to crash affected server: http://www.example.com/global/ Analysis: --- #gdb ./elogd ... ... (gdb) break show_elog_list Breakpoint 2 at 0x809d6e0 (gdb) c Continuing. (no debugging symbols found) elogd 2.6.2 built Nov 8 2006, 01:25:48 revision 1699 Falling back to default group elog Falling back to default user elog Indexing logbooks ... done Server listening on port 8080 ... Breakpoint 2, 0x0809d6e0 in show_elog_list () (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. 0x0809eb7a in show_elog_list () (gdb) bt #0 0x0809eb7a in show_elog_list () #1 0x in ?? () (gdb) i r eax0x0 0 ecx0x9d43d88164904328 edx0x0 0 ebx0x0 0 esp0xbfa8aca0 0xbfa8aca0 ebp0x80df40c0x80df40c esi0xbfb27050 -1078824880 edi0x0 0 eip0x809eb7a0x809eb7a eflags 0x200246 2097734 cs 0x73 115 ss 0x7b 123 ds 0x7b 123 es 0x7b 123 fs 0x0 0 gs 0x33 51 (gdb) x/i $eip 0x809eb7a show_elog_list+5274:mov(%eax),%eax The vulnerable code is at Line:16774 of elogd.c, n_msg = *lbs-n_el_index; where the pointer lbs is dereferenced before being null checked. --- elogd.c, Line:16772 - }
Bug#393309: ITP: libtemplate-latex-perl -- LaTeX support for the perl Template Toolkit
Package: wnpp Severity: wishlist * Package name: libtemplate-latex-perl Version : 2.17 Upstream Author : Andy Wardley [EMAIL PROTECTED] * URL : http://mirrors.kernel.org/cpan/modules/by-module/Template/Template-Latex-2.17.tar.gz * License : Perl Description : LaTeX support for the perl Template Toolkit This module is a wrapper of convenience around the Template Toolkit module, providing additional support for generating PDF, PostScript and DVI documents from LaTeX templates. . The Template Toolkit is a fast, powerful, flexible, and easily extensible template processing system written in Perl. -- roktas signature.asc Description: Digital signature
Bug#393311: New upstream version 2.15 available at CPAN.
Package: libtemplate-perl Version: 2.14-1 Severity: wishlist Hi, I'm about to package Template::Latex (on behalf of Debian Perl group) which requires Template 2.15. Could it be possible to update this package in the near future? Let me know if I can help in any way. Thanks for your efforts. Cheers, -- roktas signature.asc Description: Digital signature
Bug#391768: Please update debconf PO translation for the package exim4 4.63-4.0
* Christian Perrier [2006-10-08 16:17:40+0200] You are noted as the last translator of the debconf translation for exim4. Please respect the Reply-To: field and send your updated translation to [EMAIL PROTECTED] Attached is the updated Turkish translation. -- roktas tr.po.gz Description: Binary data
Bug#391603: [INTL:tr] Turkish translation update
Package: console-common Version: 0.7.47 Severity: wishlist Tags: patch l10n Could you please include the attached up-to-date Turkish translation in newer versions. Thanks! -- roktas # Turkish translation of console-common. # This file is distributed under the same license as the console-common package. # Recai Oktaş [EMAIL PROTECTED] 2004, 2006. # msgid msgstr Project-Id-Version: console-common\n Report-Msgid-Bugs-To: \n POT-Creation-Date: 2006-09-19 09:15+0200\n PO-Revision-Date: 2006-10-07 17:25+0300\n Last-Translator: Recai Oktaş [EMAIL PROTECTED]\n Language-Team: Turkish debian-l10n-turkish@lists.debian.org\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n Plural-Forms: nplurals=1; plural=0;\n #. Type: select #. Choices #: ../templates.in:1001 msgid Select keymap from arch list msgstr Klavye düzenini mimari (arch) listesinden seç #. Type: select #. Choices #: ../templates.in:1001 msgid Don't touch keymap msgstr Klavye ayarına dokunma #. Type: select #. Choices #: ../templates.in:1001 msgid Keep kernel keymap msgstr Çekirdekle gelen klavye düzenini koru #. Type: select #. Choices #: ../templates.in:1001 msgid Select keymap from full list msgstr Klavye düzenini tam listeden seç #. Type: select #. Description #: ../templates.in:1002 msgid Policy for handling keymaps: msgstr Klavye düzenlerinin idaresinde uyulacak yöntem: #. Type: select #. Description #: ../templates.in:1002 msgid The keymap describes how keys are laid out on your keyboard, and what symbols (letters, digits, etc.) are drawn on them. msgstr Klavye düzeni tuşların klavye üzerinde nasıl dizildiğini ve bunların üzerinde (harfler, rakamlar, vb.) hangi sembollerin bulunduğunu tanımlar. #. Type: select #. Description #: ../templates.in:1002 msgid \Select keymap from arch list\ will allow you to select one of the predefined keymaps specific for your architecture - you will most likely want this unless you have a USB keyboard. msgstr \Klavye düzenini mimari (arch) listesinden seç\ kullandığınız mimariye (i386, powerpc gibi) özgü önceden tanımlı klavye düzenlerinden birini seçmenizi sağlar - USB klavye kullanmıyorsanız bunun seçilmesi önerilir. #. Type: select #. Description #: ../templates.in:1002 msgid \Don't touch keymap\ will prevent the configuration system from overwriting the keymap you have in /etc/console. Select this if you want to keep a keymap you obtained through other means. Please remember to install new keymaps with install-keymap(8) if you select this choice. msgstr \Klavye ayarına dokunma\ bu yapılandırma sisteminin /etc/console dosyasında bulunan klavye ayarının üzerine yazmasını önleyecektir. Bu paketin kontrolü dışında bir yolla kurmak istediğiniz bir klavye düzeni varsa bunu seçin. Bu seçeneğin kullanılması halinde yeni klavye düzenlerini install-keymap komutuyla kurmayı lütfen unutmayın. #. Type: select #. Description #: ../templates.in:1002 msgid \Keep kernel keymap\ will prevent any keymap from being loaded next time your system boots. It will remove from /etc/console any keymap you may have already selected (it will be lost), but if you have already loaded a keymap, it cannot be changed back until you reboot. msgstr \Çekirdekle gelen klavye düzenini koru \ sistemin bir sonraki açılışında herhangi bir klavye düzeninin yüklenmesini önleyecektir. Bu seçenek /etc/ console'da zaten varolan bir ayarı silecektir (bu ayarı kaybedeceksiniz). Fakat şu an zaten yüklenmiş ve etkin olan bir klavye düzeni varsa, sistemi tekrar açıncaya kadar bu ayar değiştirilemez. #. Type: select #. Description #: ../templates.in:1002 msgid \Select keymap from full list\ offers a full listing of all predefined keymaps. You want this, if you use an USB keyboard from a different computer architecture or if you use an adapter to use such a keyboard. msgstr \Klavye düzenini tam listeden seç\ önceden tanımlı bütün klavye düzenlerini listeler. Farklı bir mimaride USB klavye veya klavye için bir uyarlayıcı (adaptör) kullanıyorsanız bunu seçmek isteyeceksiniz. #. Type: note #. Description #: ../templates.in:2001 msgid Ignored boot-time keymap in an old location msgstr Eski bir dizinde bulunan açılış zamanında yüklenmek niyetiyle hazırlanmış bir klavye düzeni göz ardı edildi. #. Type: note #. Description #: ../templates.in:2001 msgid You have asked the keymap configuration tool not to touch an existing keymap you installed, or you asked for higher-priority questions only to be asked and the tool decided not to mess with your existing setup. msgstr Bu yapılandırma aracının kurulu bulunan klavye düzenine dokunmamasını veya sadece yüksek önceliğe sahip yapılandırma sorularının yöneltilmesini istediğinizden mevcut ayarla ilgili hiçbir şey yapılmayacak. #. Type: note #. Description #: ../templates.in:2001 msgid However, you have file(s) that were recognized as boot-time keymaps by older versions of the console utilities, either in /etc/kbd
Bug#390887: [INTL:tr] Update Turkish podebconf translation
Package: samba Severity: wishlist Tags: l10n patch Updated Turkish translation is attached. Thanks to Mehmet Türker. -- roktas # Turkish translation of samba. # This file is distributed under the same license as the samba package. # Mehmet Türker [EMAIL PROTECTED], 2004. # msgid msgstr Project-Id-Version: samba\n Report-Msgid-Bugs-To: \n POT-Creation-Date: 2006-08-15 07:59-0500\n PO-Revision-Date: 2006-10-03 13:38+0200\n Last-Translator: Mehmet Türker [EMAIL PROTECTED]\n Language-Team: Turkish debian-l10n-turkish@lists.debian.org\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n #. Type: boolean #. Description #: ../samba-common.templates:1001 msgid Modify smb.conf to use WINS settings from DHCP? msgstr WINS ayarlarını DHCP'den kullanmak için smb.conf dosyasında değişiklik yapılsın mı? #. Type: boolean #. Description #: ../samba-common.templates:1001 msgid If your computer gets IP address information from a DHCP server on the network, the DHCP server may also provide information about WINS servers (\NetBIOS name servers\) present on the network. This requires a change to your smb.conf file so that DHCP-provided WINS settings will automatically be read from /etc/samba/dhcp.conf. msgstr Eğer bilgisayarınız IP adresini ağınızdaki bir DHCP sunucusundan alıyorsa, DHCP sunucusu ayrıca ağınızda bulunan WINS sunucuları (\NetBIOS alanadı sunucuları\) hakkında da bilgi verebilir. Bu, smb.conf dosyanızda DHCP tarafından sunulan WINS ayarlarının otomatik olarak /etc/samba/dhcp.conf dosyasından okunmasını sağlayan bir değişikliği gerektirir. #. Type: boolean #. Description #: ../samba-common.templates:1001 msgid The dhcp3-client package must be installed to take advantage of this feature. msgstr Bu özellikten yararlanabilmek için dhcp3-client paketinin kurulmuş olması gerekir. #. Type: boolean #. Description #: ../samba-common.templates:2001 msgid Configure smb.conf automatically? msgstr smb.conf dosyası otomatik olarak yapılandırılsın mı? #. Type: boolean #. Description #: ../samba-common.templates:2001 msgid The rest of the configuration of Samba deals with questions that affect parameters in /etc/samba/smb.conf, which is the file used to configure the Samba programs (nmbd and smbd). Your current smb.conf contains an 'include' line or an option that spans multiple lines, which could confuse the automated configuration process and require you to edit your smb.conf by hand to get it working again. msgstr Geri kalan Samba yapılandırması, Samba uygulamalarını (nmbd ve smbd) yapılandırmak için kullanılan /etc/samba/smb.conf dosyasındaki parametreleri etkileyen sorularla devam edecektir. Mevcut smb.conf dosyası, debconf'u şaşırtabilecek ve smb.conf dosyanızı elle değiştirilmesi zorunda kılacak bir 'include' satırı veya birden fazla satır boyunca devam eden bir seçenek içeriyor ve tekrar çalışabilmesi için smb.conf dosyanızın sizin tarafınızdan değiştirilmesi gerekiyor. #. Type: boolean #. Description #: ../samba-common.templates:2001 msgid If you do not choose this option, you will have to handle any configuration changes yourself, and will not be able to take advantage of periodic configuration enhancements. msgstr Eğer bu seçeneği seçmezseniz, bütün yapılandırma değişikliklerini kendiniz yapmak zorunda kalacaksınız ve periyodik yapılandırma iyileştirmelerinin avantajlarını kullanamayacaksınız. #. Type: string #. Description #: ../samba-common.templates:3001 msgid Workgroup/Domain Name: msgstr Çalışma Grubu/Etki Alanı İsmi: #. Type: string #. Description #: ../samba-common.templates:3001 msgid Please specify the workgroup you want this server to appear to be in when queried by clients. Note that this parameter also controls the domain name used with the security=domain setting. msgstr Lütfen sunucunuzun istemciler tarafından sorgulandığında içerisinde gözükmesini istediğiniz Çalışma Grubu'nu belirtiniz. Aklınızda bulunsun, bu parametre ayrıca security=domain ayarı ile beraber kullanılacak Etki Alanını da kontrol eder. #. Type: boolean #. Description #: ../samba-common.templates:4001 msgid Use password encryption? msgstr Parola şifrelenmesi kullanılsın mı? #. Type: boolean #. Description #: ../samba-common.templates:4001 msgid All recent Windows clients communicate with SMB servers using encrypted passwords. If you want to use clear text passwords you will need to change a parameter in your Windows registry. msgstr Yeni Windows istemcileri SBM sunucularıyla şifrelenmiş parolalar kullanarak iletişim kurarlar. Eğer düz metin parolaları kullanmak istiyorsanız Windows registry içinde bir parametreyi değiştirmelisiniz. #. Type: boolean #. Description #: ../samba-common.templates:4001 msgid Enabling this option is highly recommended. If you do, make sure you have a valid /etc/samba/smbpasswd file and that you set passwords in there for each user using the smbpasswd command. msgstr Bu işlemi yapmanız şiddetle önerilir. Eğer
Bug#389361: XSS vulnerability in elog
* Tilman Koschnick [2006-09-25 11:27:10+0200] Package: elog Version: 2.6.1+r1642-1 Severity: grave Tags: security Justification: user security hole Hi, when editing a log entry in HTML mode, elog accepts arbitrary JavaScript code. This code will be executed in the browser of other users viewing the entry (provided they have JavaScript enabled), thus exposing the users to a XSS (cross site scripting) attack. Hi, Thanks for your bug report. I'm going to make a new upload (r1719) which includes a fix for this issue. Feel free to reopen this bug if the problem persists. -- roktas signature.asc Description: Digital signature
Bug#389361: XSS vulnerability fixed
* Stefan Ritt [2006-09-27 23:09:27+0200] The reported XSS vulnerability has been fixed in SVN revision 1719 of elog by not allowing HTML mode by default. This mode has to be enabled explicitly by setting Allowed encoding = 7. Hi Stefan, Thanks for the fix! I haven't checked the stable version. Does this issue also exist in our stable version (release 2.5.7, svn revision: r1558)? If so, we should prepare a backport for it. Cheers, -- roktas signature.asc Description: Digital signature
Bug#387846: ITP: libtext-typography-perl -- markup ASCII text with correct typography for HTML
Package: wnpp Severity: wishlist * Package name: libtext-typography-perl Version : 0.01 Upstream Author : Thomas Sibley [EMAIL PROTECTED] * URL : http://mirrors.kernel.org/cpan/modules/by-module/Text/Text-Typography-0.01.tar.gz * License : BSD-style Description : markup ASCII text with correct typography for HTML This module is a thin wrapper for John Gruber's SmartyPants plugin for various CMSs. SmartyPants is a web publishing utility that translates plain ASCII punctuation characters into smart typographic punctuation HTML entities. -- roktas signature.asc Description: Digital signature
Bug#387258: Please update debconf PO translation for the package alsa-driver 1.0.12-1
* [EMAIL PROTECTED] [2006-09-14 15:10:07+0200] Take your pardon, last mail was against alsa-driver 1.0.12-2, but should be alsa-driver 1.0.12-1, which is available in sid. Hi, You are noted as the last translator of the debconf translation for alsa-driver. The English template has been changed, and now some messages are marked fuzzy in your translation or are missing. I would be grateful if you could take the time and update it. Please respect the Reply-To: field and send your updated translation to [EMAIL PROTECTED] Attached is the updated Turkish translation. Thanks for notifying! -- roktas tr.po.gz Description: Binary data
Bug#385729: firefox-locale-tr: Please use Turkish as the language name
Package: firefox-locale-tr Severity: minor Hi, Could you please make a 's/Turkey/Turkish/g' in the package description? Thanks for maintaining this package! Cheers, -- roktas signature.asc Description: Digital signature
Bug#380334: [INTL:tr] Turkish po update
Package: popularity-contest Severity: wishlist Tags: l10n patch File is attached. -- roktas # Turkish translation of popularity-contest. # This file is distributed under the same license as the popularity-contest package. # Özgür Murat Homurlu [EMAIL PROTECTED], 2004. # Recai Oktaş [EMAIL PROTECTED], 2006 # msgid msgstr Project-Id-Version: popularity-contest\n Report-Msgid-Bugs-To: \n POT-Creation-Date: 2006-07-29 12:23+0200\n PO-Revision-Date: 2006-07-29 14:02+0300\n Last-Translator: Recai Oktaş [EMAIL PROTECTED]\n Language-Team: Debian L10n Turkish debian-l10n-turkish@lists.debian.org\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n X-Generator: KBabel 1.0.2\n Plural-Forms: nplurals=1; plural=0;\n #. Type: boolean #. Description #: ../templates:4 msgid Participate in the package usage survey? msgstr Paket kullanım anketine katılmak ister miydiniz? #. Type: boolean #. Description #: ../templates:4 msgid The system may anonymously supply the distribution developers with statistics about the most used packages on this system. This information influences decisions such as which packages should go on the first distribution CD. msgstr Bu sistemde en çok kullanılan paketler hakkındaki istatistiksel bilgiler isimsiz (anonim) şekilde dağıtım geliştiricilerine iletilebilir. Bu bilgiler, dağıtımın birinci CD'si içinde olması gereken paketlerin belirlenmesi gibi bazı kararlar üzerinde etkili olacaktır. #. Type: boolean #. Description #: ../templates:4 msgid If you choose to participate, the automatic submission script will run once every week, sending statistics to the distribution developers. The collected statistics can be viewed on http://popcon.debian.org/.; msgstr Katılmak isterseniz otomatik gönderim betiği haftada bir kez çalışacak ve toplanan istatistikleri dağıtım geliştiricilerine gönderecektir. Bu istatistiklere http://popcon.debian.org/ adresinden erişilebilir. #. Type: boolean #. Description #: ../templates:4 msgid This choice can be later modified by running \dpkg-reconfigure popularity- contest\. msgstr Burada yapılan seçim, \dpkg-reconfigure popularity-contest\ komutu çalıştırılarak daha sonra değiştirilebilir. signature.asc Description: Digital signature
Bug#376485: elog: List Menu commands parameter does not work
Hi, * Jamie Rollins [2006-07-03 16:50:20-0700] It seems to me that actually none of the List options are working. At least I can't get them to work. I can't get the List Menu text or List page title options to work either. I'm trying to use the same capitalization as mentioned in the on-line documentation, although I have tried various permutations. Maybe I'm just missing something, though. My understanding is that the List page is what you get to when you click on a particular logbook from the start logbook selection page, or from one of the logbook tabs. If this is not the case, the documentation is then very unclear. Please let me know if there's anything I can do to help sort out the problem. Thanks again for maintaining. Thanks for bug reporting. This issue might have already been resolved in upstream. Could you please test out the (unofficial) new package and see if it works right? http://people.debian.org/~roktas/packages/elog_2.6.1+r1695-0unofficial_i386.deb -- roktas signature.asc Description: Digital signature
Bug#376090: irssi: Privmsg problem
* David Pashley [2006-06-30 18:47:41+0100]
I wonder. I know there was a bug involving tr_TR locale regarding
uppercasing/lowercasing of characters.
Yep, I strongly suspect that the same upper/lowercasing + strcasecmp issues
cause this bug[1].
[EMAIL PROTECTED]:~/tmp/irssi/irssi-0.8.10$ grep -R g_strcasecmp * | wc -l
186
While working on this issue, I'm sending some test progs showing the
behaviour of glib's g_strcasecmp with some problematic i/ı/İ/I input
strings, for your convenience.
[1] For more info: http://www.i18nguy.com/unicode/turkish-i18n.html
--
roktas
test-turkish.sh
Description: Bourne shell script
#include stdlib.h
#include stdio.h
#include string.h
#include locale.h
#include glib.h
#define DUMP(s1, s2, call) \
(g_print(s1: %s\ts2: %s\t%s == %d\n, (s1), (s2), #call, (call)))
int
main (int argc, char **argv)
{
gchar *s1 = argv[1];
gchar *s2 = argv[2];
if (argc 3) {
fprintf (stderr, Usage: %s string1 string2\n, argv[0]);
exit (EXIT_FAILURE);
}
setlocale (LC_ALL, );
g_print (Locale: %s\n, setlocale (LC_ALL, NULL));
DUMP (s1, s2, strlen (s1));
DUMP (s1, s2, g_utf8_strlen (s1, -1));
DUMP (s1, s2, strcasecmp (s1, s2));
DUMP (s1, s2, g_strcasecmp (s1, s2));
DUMP (s1, s2, g_ascii_strcasecmp (s1, s2));
DUMP (s1, s2,
g_strcasecmp (g_utf8_strup (s1, 128), g_utf8_strup (s2, 128)));
DUMP (s1, s2,
g_strcasecmp (g_utf8_strdown (s1, 128), g_utf8_strdown (s2, 128)));
exit (EXIT_SUCCESS);
}
Locale: tr_TR.UTF-8
s1: ascii s2: ASCII strlen (s1) == 5
s1: ascii s2: ASCII g_utf8_strlen (s1, -1) == 5
s1: ascii s2: ASCII strcasecmp (s1, s2) == 32
s1: ascii s2: ASCII g_strcasecmp (s1, s2) == 32
s1: ascii s2: ASCII g_ascii_strcasecmp (s1, s2) == 0
s1: ascii s2: ASCII g_strcasecmp (g_utf8_strup (s1, 128),
g_utf8_strup (s2, 128)) == 123
s1: ascii s2: ASCII g_strcasecmp (g_utf8_strdown (s1, 128),
g_utf8_strdown (s2, 128)) == -91
Locale: tr_TR.UTF-8
s1: ascii s2: ASCİİ strlen (s1) == 5
s1: ascii s2: ASCİİ g_utf8_strlen (s1, -1) == 5
s1: ascii s2: ASCİİ strcasecmp (s1, s2) == -91
s1: ascii s2: ASCİİ g_strcasecmp (s1, s2) == -91
s1: ascii s2: ASCİİ g_ascii_strcasecmp (s1, s2) == -91
s1: ascii s2: ASCİİ g_strcasecmp (g_utf8_strup (s1, 128),
g_utf8_strup (s2, 128)) == 0
s1: ascii s2: ASCİİ g_strcasecmp (g_utf8_strdown (s1, 128),
g_utf8_strdown (s2, 128)) == -99
Locale: tr_TR.UTF-8
s1: ascıı s2: ASCII strlen (s1) == 7
s1: ascıı s2: ASCII g_utf8_strlen (s1, -1) == 5
s1: ascıı s2: ASCII strcasecmp (s1, s2) == 123
s1: ascıı s2: ASCII g_strcasecmp (s1, s2) == 123
s1: ascıı s2: ASCII g_ascii_strcasecmp (s1, s2) == 91
s1: ascıı s2: ASCII g_strcasecmp (g_utf8_strup (s1, 128),
g_utf8_strup (s2, 128)) == 0
s1: ascıı s2: ASCII g_strcasecmp (g_utf8_strdown (s1, 128),
g_utf8_strdown (s2, 128)) == 0
Locale: tr_TR.UTF-8
s1: ascıı s2: ASCİİ strlen (s1) == 7
s1: ascıı s2: ASCİİ g_utf8_strlen (s1, -1) == 5
s1: ascıı s2: ASCİİ strcasecmp (s1, s2) == 1
s1: ascıı s2: ASCİİ g_strcasecmp (s1, s2) == 1
s1: ascıı s2: ASCİİ g_ascii_strcasecmp (s1, s2) == 1
s1: ascıı s2: ASCİİ g_strcasecmp (g_utf8_strup (s1, 128),
g_utf8_strup (s2, 128)) == -123
s1: ascıı s2: ASCİİ g_strcasecmp (g_utf8_strdown (s1, 128),
g_utf8_strdown (s2, 128)) == 91
signature.asc
Description: Digital signature
Bug#359202: RM: mozilla-firefox-locale-tr -- RoM; superseded by mozilla-firefox-locale-all
Package: ftp.debian.org Severity: normal Could you please remove mozilla-firefox-locale-tr as this package is superseded by firefox-locale-tr (from mozilla-firefox-locale-all)? No other Debian package does currently depend upon it. Regards, -- roktas signature.asc Description: Digital signature
Bug#355061: [INTL:tr] Turkish po-debconf translation
Package: tex-common
Severity: wishlist
Tags: patch l10n
Please find attached the updated Turkish po-debconf translation. Thanks to
Osman Yüksel.
Regards,
--
roktas
# translation of tr.po to Turkish
# Turkish translation of tetex-bin.
# This file is distributed under the same license as the tetex-bin package.
#
# Osman Yüksel [EMAIL PROTECTED], 2004, 2006.
msgid
msgstr
Project-Id-Version: tr\n
Report-Msgid-Bugs-To: \n
POT-Creation-Date: 2006-03-02 19:02+0100\n
PO-Revision-Date: 2006-03-03 02:44+0200\n
Last-Translator: Osman Yüksel [EMAIL PROTECTED]\n
Language-Team: Turkish tr@li.org\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
Plural-Forms: nplurals=1; plural=0;\n
X-Generator: KBabel 1.11.1\n
#. Type: boolean
#. Description
#: ../templates:4
msgid Manage the permissions of the TeX font cache with debconf?
msgstr TeX yazı tipi önbelleği yetkileri debconf ile yönetilsin mi?
#. Type: boolean
#. Description
#: ../templates:4
msgid
A TeX system may have to generate new font data (pixel data, metric,
sources) on the fly. These files can be saved into the TeX font cache in /
var/cache/fonts and later reused.
msgstr
Bir TeX sistemi (benek verileri, ölçüler, kaynaklar gibi) yazıtipi verilerini
anlık oluşturabilmelidir. Bu dosyalar /var/cache/fonts altındaki TeX yazıtipi
önbelleğine kaydedilir ve daha sonra yeniden kullanılır.
#. Type: boolean
#. Description
#: ../templates:4
msgid
If you accept, you can specify a group name and *all* directories under /var/
cache/fonts will get ownership root:groupname and permission bits 3775 (i.
e. writable for the group groupname, sticky and setgid bit set).
Accordingly, the ls-R index file will be owned and writable by that group.
msgstr
Eğer kabul ederseniz /var/cache/fonts altındaki tüm dizinlerin sahiplikleri
belirlediğiniz bir grup adına göre root:grupadı ve izinleri de 3775
(yani grupadı grubu tarafından yazılabilir ve, yapışkan [\sticky\] ve
\setgid\ bayrakları etkinleştirilmiş) olacaktır. Buna göre, ls-R dosyasının
sahibi bu grup olacak ve bu grup tarafından yazılabilecektir.
#. Type: boolean
#. Description
#: ../templates:4
msgid
The default is not to manage permissions with debconf, but this is just
because this is required for building other Debian packages. In almost
every other setup, like desktop machines or multi-user servers, accepting
this is strongly recommended!
msgstr
Diğer Debian paketlerinin de oluşturulabilmesi için, öntanımlı olarak izinler
debconf ile yönetilmez. Masaüstü bilgisayarlar veya çok kullanıcılı sunucular
gibi diğer tüm kurulumlarda bunu kabul etmeniz şiddetle önerilir!
#. Type: string
#. Description
#: ../templates:23
msgid Group that should own the TeX font cache
msgstr TeX önbelleğinin sahibi olan grup
#. Type: string
#. Description
#: ../templates:23
msgid
You can choose a specific group which will own all directories under and
including the TeX font cache /var/cache/fonts. These directories will get
permission 3775. We suggest to select the group 'users' here.
msgstr
TeX yazıtipi önbelleğini de içeren /var/cache/fonts dizini sahipliği için
belli
bir grup belirleyebilirsiniz. Bu dizinler 3775 izinlerini alacaktır. Burada
'users' grubunu seçmenizi öneririz.
#. Type: note
#. Description
#: ../templates:30
msgid Change of name of files in /etc/texmf/texmf.d/
msgstr /etc/texmf/texmf.d/ altındaki dosya adı değişiklikleri
#. Type: note
#. Description
#: ../templates:30
msgid
texmf.cnf has previously been generated by update-texmf from all files in /
etc/texmf/texmf.d/. Now update-texmf is changed and only reads files with
extension '.cnf'.
msgstr
texmf.cnf, update-texmf komutu ile /etc/texmf/texmf.d/ içindeki tüm
dosyalardan
oluşturuldu. Şimdi update-texmf değiştirildi ve şu anda sadece '.cnf' uzantılı
dosyaları okuyor.
#. Type: note
#. Description
#: ../templates:30
msgid
So if you had any private file in /etc/texmf/texmf.d/, then you should add '.
cnf' to its name; for example, 22mymacro = 22mymacro.cnf.
msgstr
Eğer /etc/texmf/texmf.d/ içinde özel bir dosyanız varsa, bunun
ismine '.cnf' uzantısını ekleyin; örneğin, 22mymacro = 22mymacro.cnf .
#. Type: note
#. Description
#: ../templates:40
msgid Essential entry missing in ${filename}
msgstr ${filename} dosyasında gerekli bir girdi eksik
#. Type: note
#. Description
#: ../templates:40
msgid An essential entry is missing in ${filename}:
msgstr ${filename} dosyasında gerekli bir girdi eksik:
#. Type: note
#. Description
#: ../templates:40
msgid No setting of ${variable}.
msgstr ${variable} için ayar yok.
#. Type: note
#. Description
#: ../templates:53
msgid Essential entry wrong in ${filename}
msgstr ${filename} dosyasındaki gerekli bir girdi yanlış
#. Type: note
#. Description
#: ../templates:53
msgid An essential entry is wrong in ${filename}: ${variable} does not contain
msgstr ${filename} dosyasında gerekli bir girdi yanlış: ${variable} içermiyor
#. Type: note
#.
Bug#348027: errors in Turkish keyboard setup
* Recai Oktaş [2006-02-09 02:57:23+0200] * Denis Barbier [2006-02-09 00:21:08+0100] Thanks, I applied your patch and also reviewed all other layouts, hopefully it should work better now for more people. Great! Thanks for all your help. Hi Denis, Could you please apply the attached patch as well? As I stated in this bug report, seeing the f variant, people tends to define the non-existed q or tr_q variants because of the false assumption that Turkish should have these variants[1]. This patch tries to be conservative for future changes (i.e. q variant may be added in future). [1] https://launchpad.net/distros/ubuntu/+source/xorg/+bug/23944 -- roktas --- xserver-xorg.config.in.orig 2006-02-10 12:29:01.0 +0200 +++ xserver-xorg.config.in 2006-02-10 13:17:23.0 +0200 @@ -1259,6 +1259,17 @@ TR_VARIANT=$RET case ,$TR_VARIANT, in +*,q,*|*,tr_q,*) + # For extra sanity, remove bogus tr_q or q variants. + if [ -e $TR_KEYMAP ] +grep -q ^[[:space:]]*xkb_symbols[[:space:]]*\q\ $TR_KEYMAP; then +SANITIZED_TR_VARIANT=q + else +# There is no such variant at least in X.Org = 7.0. Default variant +# basic points to the Q layout in these versions. +SANITIZED_TR_VARIANT=basic + fi + ;; *,f,*|*,tr_f,*) # X.Org version 6.9 uses tr_f, while = 6.9 uses only f if [ -e $TR_KEYMAP ] @@ -1282,8 +1293,8 @@ if [ -n $SANITIZED_TR_VARIANT ]; then # remove the unsanitized variant TR_VARIANT=$(echo $TR_VARIANT | \ - sed -e s/\\(tr_\)*\(f\|alt\)[[:space:]]*,//g \ - -e s/\(^\|,\)[[:space:]]*\(tr_\)*\(f\|alt\)[[:space:]]*$//g) + sed -e s/\\(tr_\)*\(q\|f\|alt\)[[:space:]]*,//g \ + -e s/\(^\|,\)[[:space:]]*\(tr_\)*\(q\|f\|alt\)[[:space:]]*$//g) # add the sanitized variant if [ -n $TR_VARIANT ]; then signature.asc Description: Digital signature
Bug#348027: errors in Turkish keyboard setup
* Denis Barbier [2006-02-09 00:21:08+0100] Thanks, I applied your patch and also reviewed all other layouts, hopefully it should work better now for more people. Great! Thanks for all your help. -- roktas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#349528: Security bugs in elog
* Moritz Muehlenhoff [2006-02-05 19:47:45+0100] Recai Oktaş wrote: Let me know whether it is fine and I'll make the upload to stable-security (right?). Did you upload? I don't see any builds trickling in. If not, I'll do it. Yes, uploaded on 28 January: http://lists.debian.org/debian-changes/2006/01/msg00048.html -- roktas
Bug#349528: Security bugs in elog
* Recai Oktaş [2006-01-28 01:56:06+0200] Hmm, just found some other issues regarding this CVE-2005-4439. Previous tests had seemed fine to me, but when I made more tests, the bug came up again. I believe the attached patch should fix this completely. Stefan, could you have a look at it please? Stefan has confirmed my patch and applied it in r1642. So far, the following patches have been applied: http://people.debian.org/~roktas/elog-backport-patches/ I've created a new package and confirmed that it works: http://people.debian.org/~roktas/packages/elog_2.5.7+r1558-4+sarge1.diff.gz http://people.debian.org/~roktas/packages/elog_2.5.7+r1558-4+sarge1.dsc http://people.debian.org/~roktas/packages/elog_2.5.7+r1558-4+sarge1_i386.deb Debdiff is attached and here is the new changelog for your convenience: elog (2.5.7+r1558-4+sarge1) stable-security; urgency=critical * Major security update (big thanks to Florian Weimer) + Backport r1333 from upstream's Subversion repository: Fixed crashes with very long (revisions) attributes + Backport r1335 from upstream's Subversion repository: Applied patch from Emiliano to fix possible buffer overflow + Backport r1472 from upstream's Subversion repository: Do not distinguish between invalid user name and invalid password for security reasons + Backport r1487 from upstream's Subversion repository: Fixed infinite redirection with ?fail=1 + Backport r1529 from upstream's Subversion repository: Fixed bug with fprintf and buffer containing % [Our patch just eliminates the format string vulnerability.] + Backport r1620 from upstream's Subversion repository: Prohibit '..' in URLs [CVE-2006-0347] + Backport r1635 and r1642 from upstream's Subversion repository: Fixed potential buffer overflows [CVE-2005-4439] Let me know whether it is fine and I'll make the upload to stable-security (right?). Regards, -- roktas elog_2.5.7+r1558-3_2.5.7+r1558-4+sarge1.debdiff.gz Description: Binary data signature.asc Description: Digital signature
Bug#349528: Security bugs in elog
* Moritz Muehlenhoff [2006-01-27 15:28:00+0100]
Recai Oktaş wrote:
+ Backport r1636 from upstream's Subversion repository:
Added IP address to log file
Why is r1636 necessary? This seems like a new feature (better logging
in case of an attack), but doesn't seem to fix a direct security problem
and could potentially break scripts that monitor the log file and expect
the current logfile file format.
I'll remove it.
The rest of the patch looks fine.
Hmm, just found some other issues regarding this CVE-2005-4439. Previous
tests had seemed fine to me, but when I made more tests, the bug came up
again. I believe the attached patch should fix this completely. Stefan,
could you have a look at it please?
--
roktas
Subject: [PATCH]: More Fixes for CVE-2005-4439: buffer overflow through
long URL parameters
--- a/src/elogd.c 2006-01-27 10:27:21.0 +0200
+++ b/src/elogd.c 2006-01-28 01:31:33.0 +0200
@@ -23205,7 +23205,7 @@ void server_loop(void)
{
int status, i, n, n_error, authorized, min, i_min, i_conn, length;
struct sockaddr_in serv_addr, acc_addr;
- char pwd[256], str[1000], url[256], cl_pwd[256], *p, *pd;
+ char pwd[256], str[1000], url[256], cl_pwd[256], *p;
char cookie[256], boundary[256], list[1000], theme[256],
host_list[MAX_N_LIST][NAME_LENGTH], logbook[256], logbook_enc[256],
global_cmd[256];
int lsock, len, flag, content_length, header_length;
@@ -23756,7 +23756,7 @@ void server_loop(void)
p = strchr(net_buffer, '/') + 1;
/* check for ../.. to avoid serving of files on top of the elog
directory */
-for (i = 0; p[i] p[i] != ' ' p[i] != '?'; i++)
+for (i = 0; p[i] p[i] != ' ' p[i] != '?' i (int)
sizeof(url); i++)
url[i] = p[i];
url[i] = 0;
@@ -23774,7 +23774,7 @@ void server_loop(void)
}
/* check if file is in scripts directory or in its subdirs */
-for (i = 0; p[i] p[i] != ' ' p[i] != '?'; i++)
+for (i = 0; p[i] p[i] != ' ' p[i] != '?' i (int)
sizeof(url); i++)
url[i] = (p[i] == '/') ? DIR_SEPARATOR : p[i];
url[i] = 0;
if (strchr(url, '.')) {
@@ -23810,7 +23810,7 @@ void server_loop(void)
}
logbook[0] = 0;
-for (i = 0; *p *p != '/' *p != '?' *p != ' '; i++)
+for (i = 0; *p *p != '/' *p != '?' *p != ' ' i (int)
sizeof(logbook); i++)
logbook[i] = *p++;
logbook[i] = 0;
strcpy(logbook_enc, logbook);
@@ -23831,10 +23831,9 @@ void server_loop(void)
/* check for trailing '/' after logbook/ID */
if (logbook[0] *p == '/' *(p + 1) != ' ') {
sprintf(url, %s, logbook_enc);
- pd = url + strlen(url);
- while (*p *p != ' ')
- *pd++ = *p++;
- *pd = 0;
+ for (i = strlen(url); *p *p != ' ' i (int) sizeof(url);
i++)
+ url[i] = *p++;
+ url[i] = 0;
if (*(p - 1) == '/') {
sprintf(str, Invalid URL: %s, url);
show_error(str);
@@ -24109,7 +24108,8 @@ void server_loop(void)
goto redir;
} else if (strncmp(net_buffer, GET, 3) == 0) {
/* extract path and commands */
- *strchr(net_buffer, '\r') = 0;
+ if (strchr(net_buffer, '\r'))
+ *strchr(net_buffer, '\r') = 0;
if (!strstr(net_buffer, HTTP/1))
goto finished;
*(strstr(net_buffer, HTTP/1) - 1) = 0;
signature.asc
Description: Digital signature
Bug#349528: Security bugs in elog
* Recai Oktaş [2006-01-25 09:34:15+0200] All three patches + your previous six patches were applied and compiled successfully. I've also tested the fixed package in my system without any glitches. Now, I'm going to build and test it in a Sarge chroot jail. I've just tested the _pbuilded_ Sarge package against the CVE-2005-4439 vulnerability and confirmed that elogd behaved normally (no core dump). Florian: If you haven't any objections, I'll upload to stable-security (with some final cosmetic touches). Also, the new upstream package will follow (for sid). Stefan: Thank you very much for the urgent fix. Regards, -- roktas signature.asc Description: Digital signature
Bug#349528: (no subject)
[sorry for the delay, my internet connection is sketchy these days] * Moritz Muehlenhoff [2006-01-26 10:57:53+0100] Florian, thanks a lot for sorting this out! I'll prepare the DSA; Recai, what cosmetic fixes do you intent to do? A security upload's changes you be strictly limited to the security issues. Only changes in debian/changelog (adopt my changelog style). Can you send me the debdiff between the Sarge version and your proposed upload to the security queue or the proposed update itself? Debdiff is attached. You can reach the proposed update at the following uri: http://people.debian.org/~roktas/packages/elog_2.5.7+r1558-4+sarge1.diff.gz http://people.debian.org/~roktas/packages/elog_2.5.7+r1558-4+sarge1.dsc http://people.debian.org/~roktas/packages/elog_2.5.7+r1558-4+sarge1_i386.deb And here is the relevant changelog entry for your inspection: elog (2.5.7+r1558-4+sarge1) stable-security; urgency=high * Major security update (big thanks to Florian Weimer) + Backport r1333 from upstream's Subversion repository: Fixed crashes with very long (revisions) attributes + Backport r1335 from upstream's Subversion repository: Applied patch from Emiliano to fix possible buffer overflow + Backport r1472 from upstream's Subversion repository: Do not distinguish between invalid user name and invalid password for security reasons + Backport r1487 from upstream's Subversion repository: Fixed infinite redirection with ?fail=1 + Backport r1529 from upstream's Subversion repository: Fixed bug with fprintf and buffer containing % [Our patch just eliminates the format string vulnerability.] + Backport r1620 from upstream's Subversion repository: Prohibit '..' in URLs [CVE-2006-0347] + Backport r1635 from upstream's Subversion repository: Fixed potential buffer overflows [CVE-2005-4439] + Backport r1636 from upstream's Subversion repository: Added IP address to log file * Florian Weimer [2006-01-26 13:41:53+0100] So far, the patch for CVE-2006-0347 was missing. A tentative backport of the upstream fix is included below. I dropped the hunk which dealt with scripts support because this functionality is not present in the sarge version. The changelog entry should look like this: Backport revision 1620 from upstream Subversion repository: Prohibit '..' in URLs [CVE-2006-0347] Hmm, I should have checked the CVE database for other issues. Thanks for doing it on behalf of me. I have applied the above patch and tested it for a failure case explained in Elog forums: http://midas.psi.ch/elogs/Forum/1615 It seems fine here (Elog returns an Invalid URL message). Regards, -- roktas elog_2.5.7+r1558-3_2.5.7+r1558-4+sarge1.debdiff.gz Description: Binary data signature.asc Description: Digital signature
Bug#349528: Security bugs in elog
* Florian Weimer [2006-01-24 21:51:00+0100]
* Stefan Ritt:
Is this list complete as far as fixes past r1202 are concerned? What
about r1487, is it a significant DoS condition?
Yes.
Okay, this patch shouldn't be too hard to extract. Recai, could you
backport that one and the fixes from r1635 to stable?
OK. I'm sending three separate patches attached for your review:
* 0007-r1635-Fix-CVE-2005-4439.txt
Backport r1635: targets to fix CVE-2005-4439
* 0008-r1487-Fix-DoS-condition.txt
Backport r1487: fixes infinite redirection
* 0009-r1636-Add-IP-address-to-logfile.txt [optional]
Backport r1636: adds IP address to log file
All three patches + your previous six patches were applied and compiled
successfully. I've also tested the fixed package in my system without any
glitches. Now, I'm going to build and test it in a Sarge chroot jail.
Hope I haven't missed anything.
Regards,
--
roktas
Subject: [PATCH] r1635: Fixes CVE-2005-4439: buffer overflow through long URL
parameters
--- a/debian/changelog 2006-01-25 08:24:44.0 +0200
+++ b/debian/changelog 2006-01-25 08:24:50.0 +0200
@@ -11,6 +11,10 @@ elog (2.5.7+r1558-4+sarge1) unstable; ur
* Backport r1529 from upstream's Subversion repository:
Fixed bug with fprintf and buffer containing %
(Our patch just eliminates the format string vulnerability.)
+ * Backport r1635 from upstream's Subversion repository:
+Fixed potential buffer overflows
+This backport addresses CVE-2005-4439: buffer overflow through long
+URL parameters http://marc.theaimsgroup.com/?m=113498708213563
-- Florian Weimer [EMAIL PROTECTED] Mon, 23 Jan 2006 15:56:37 +0100
--- a/src/elogd.c 2006-01-25 08:21:00.0 +0200
+++ b/src/elogd.c 2006-01-25 08:21:48.0 +0200
@@ -1839,13 +1839,15 @@ void base64_decode(char *s, char *d)
*d = 0;
}
-void base64_encode(char *s, char *d)
+void base64_encode(unsigned char *s, unsigned char *d, int size)
{
unsigned int t, pad;
+ unsigned char *p;
pad = 3 - strlen(s) % 3;
if (pad == 3)
pad = 0;
+ p = d;
while (*s) {
t = (*s++) 16;
if (*s)
@@ -1862,6 +1864,8 @@ void base64_encode(char *s, char *d)
*(d + 0) = map[t 63];
d += 4;
+ if (d-p = size-3)
+ return;
}
*d = 0;
while (pad--)
@@ -1898,12 +1902,12 @@ void base64_bufenc(unsigned char *s, int
*(--d) = '=';
}
-void do_crypt(char *s, char *d)
+void do_crypt(char *s, char *d, int size)
{
#ifdef HAVE_CRYPT
- strcpy(d, crypt(s, el));
+ strlcpy(d, crypt(s, el), size);
#else
- base64_encode(s, d);
+ base64_encode((unsigned char *) s, (unsigned char *) d, size);
#endif
}
@@ -2652,7 +2656,7 @@ int retrieve_url(char *url, char **buffe
{
struct sockaddr_in bind_addr;
struct hostent *phe;
- char str[256], host[256], subdir[256], param[256], auth[256], pwd_enc[256];
+ char str[1000], unm[256], upwd[256], host[256], subdir[256], param[256],
auth[256], pwd_enc[256];
int port, bufsize;
INT i, n;
fd_set readfds;
@@ -2704,12 +2708,15 @@ int retrieve_url(char *url, char **buffe
sprintf(str, GET %s%s HTTP/1.0\r\nConnection: Close\r\n, subdir, param);
/* add local username/password */
- if (isparam(unm))
+ if (isparam(unm) isparam(upwd)) {
+ strlcpy(unm, getparam(unm), sizeof(unm));
+ strlcpy(upwd, getparam(upwd), sizeof(upwd));
sprintf(str + strlen(str), Cookie: unm=%s; upwd=%s\r\n,
getparam(unm), getparam(upwd));
+ }
if (rpwd rpwd[0]) {
sprintf(auth, anybody:%s, rpwd);
- base64_encode(auth, pwd_enc);
+ base64_encode((unsigned char *) auth, (unsigned char *) pwd_enc,
sizeof(pwd_enc));
sprintf(str + strlen(str), Authorization: Basic %s\r\n, pwd_enc);
}
@@ -3523,13 +3530,13 @@ void check_config()
void retrieve_email_from(LOGBOOK * lbs, char *ret, char
attrib[MAX_N_ATTR][NAME_LENGTH])
{
- char str[256], *p, login_name[256];
+ char email_from[256], str[256], *p, login_name[256];
char slist[MAX_N_ATTR + 10][NAME_LENGTH], svalue[MAX_N_ATTR +
10][NAME_LENGTH];
int i;
if (!getcfg(lbs-name, Use Email from, str, sizeof(str))) {
if (isparam(user_email) *getparam(user_email))
- strcpy(str, getparam(user_email));
+ strlcpy(str, getparam(user_email), sizeof(email_from));
else
sprintf(str, [EMAIL PROTECTED], host_name);
}
@@ -5254,7 +5261,7 @@ void write_logfile(LOGBOOK * lbs, const
{
char file_name[2000];
va_list argptr;
- char str[1];
+ char str[1], unm[256];
FILE *f;
time_t now;
char buf[1];
@@ -5284,9 +5291,10 @@ void write_logfile(LOGBOOK * lbs, const
strftime(buf, sizeof(buf), %d-%b-%Y %H:%M:%S, localtime(now));
strcat(buf, );
- if (*getparam(unm) rem_host[0])
- sprintf(buf + strlen(buf), [EMAIL PROTECTED] , getparam(unm),
rem_host);
- else if (rem_host[0])
+ if
Bug#349528: various unfixed security bugs
First of all thanks for the detailed analysis! I haven't been able to work
on elog much, due to heavy work load these days.
* Florian Weimer [2006-01-23 16:42:16+0100]
Package: elog
Version: 2.6.0beta2+r1716-1
Tags: security upstream fixed-upstream
Severity: grave
First a little version cross-reference, based on the src/elog{,d}.c
files.
Debian CVS (elogd.c)Subversion
2.6.0beta2+r1716-1 1.717* r1445
2.5.7+r1558-3 1.558 + 1.648r1202 + r1347
* Part of the upstream are contained in the .diff.gz file, so the
embedded version number is not quite correct.
The following issues are unfixed upstream:
- CVE-2005-4439: buffer overflow through long URL parameters
http://marc.theaimsgroup.com/?m=113498708213563
- If host names are resolved, no forward lookup is performed to
verify the PTR RR. (This does not affect the sarge version
because it unconditionally uses addresses, not host names.)
- There are still some format string issues when things are written
to the logfile.
Apparently, upstream is not aware of those three issues.
The following potential security issues have been fixed upstream, but
not in the sid version (there are some more issues apparently, but
those bugs were introduced past the sid version AFAICS):
I'm going to prepare an urgent sid upload for those bugs.
r1529 | ritt | 2005-10-25 20:26:34 +0200 (Tue, 25 Oct 2005) | 1 line
Changed paths:
M /trunk/src/elogd.c
Fixed bug with fprintf and buffer containing %
r1472 | ritt | 2005-08-04 22:26:35 +0200 (Thu, 04 Aug 2005) | 2 lines
Changed paths:
M /trunk/src/elog.c
M /trunk/src/elogd.c
Do not distinguish between invalid user name and invalid password for
security reasons
On top of that, the following issues affect the sarge version only:
r1335 | ritt | 2005-04-27 12:43:43 +0200 (Wed, 27 Apr 2005) | 2 lines
Changed paths:
M /trunk/src/elogd.c
Applied patch from Emiliano to fix possible buffer overflow
r1333 | ritt | 2005-04-22 15:41:18 +0200 (Fri, 22 Apr 2005) | 2 lines
Changed paths:
M /trunk/src/elogd.c
Fixed crashes with very long (revisions) attributes
I've back-ported all four issues to the sarge version, but they
haven't received any testing yet. If anybody has got a sarge elog
installation, please speak up.
Thanks for the backport, unfortunately I don't have a Sarge box at the
moment, but will try to find one. Could you please supply the url of
backported patch so that I can also work on it?
I'm going to ask upstream about the following issue:
r1487 | ritt | 2005-09-09 22:59:46 +0200 (Fri, 09 Sep 2005) | 2 lines
Changed paths:
M /trunk/src/elogd.c
Fixed infinite redirection with ?fail=1
CCing to Stefan.
[Stefan: Please keep the discussion CCed to the bug report]
Regards,
--
roktas
signature.asc
Description: Digital signature
Bug#349528: various unfixed security bugs
Hi, * Florian Weimer [2006-01-24 00:07:35+0100] * Recai Oktaş: I'm going to prepare an urgent sid upload for those bugs. I'm not sure if it is worth the effort, until we have all other issues sorted out. Agreed. I would be glad if you add yourself in Uploaders field. You're totally free to make any upload. -- roktas signature.asc Description: Digital signature
Bug#348027: errors in Turkish keyboard setup
* Denis Barbier [2006-01-15 10:22:21+0100]
On Sun, Jan 15, 2006 at 04:24:17AM +0200, Recai Oktaş wrote:
I tested your code, and have one remark: you change tr_f - f when
debian-installer/keymap is known, but you may also perform this
change after user selected a variant, he may get used to tr_f and
not know about this name change.
You're right, the second patch is problematic. But as far as I can see it,
the first one has not a flaw in this respect, since the TR handling code is
in the:
if [ -n $RECONFIGURE ] || [ -n $FIRSTINST ]; then
body, before the db_inputs. Have I understood it correctly?
The problem is precisely that it appears before db_inputs. So if
XMAP is UNKNOWN, or if previous value was different from tr but
user selects tr this time, variant is not sanitized. Maybe this
sanitization could be performed at the end, just before writing
xorg.conf, to make sure that tr_{f,alt} variants are not written
into this file?
Ok, I understood it now. I had thought that you meant we should not
silently overwrite the users' choice. :-)
How about the attached patch? This one sanitizes the variant just after
the user's input. It's also kludgy, but I couldn't find a better way.
--
roktas
--- xserver-xorg.config.in.orig 2006-01-12 03:11:03.0 +0200
+++ xserver-xorg.config.in 2006-01-15 12:37:40.0 +0200
@@ -960,7 +960,7 @@
br-abnt2--ie*) XMAP=ie;;
br-abnt2--*) XMAP=br; OPTIONS=abnt2;;
by--*) XMAP=by;;
-cf--tr*) XMAP=tr; OPTIONS=tr_f;;
+cf--tr*) XMAP=tr; VARIANT=f;;
cf--ie*) XMAP=ie;;
cf--lv*) XMAP=lv;;
cf--it*) XMAP=it;;
@@ -1009,7 +1009,7 @@
gr--ua*) XMAP=ua;;
gr--by*) XMAP=by;;
gr--tj*) XMAP=tj;;
-gr--tr*) XMAP=tr_f;;
+gr--tr*) XMAP=tr; VARIANT=f;;
gr--uz*) XMAP=uz;;
hu--*) XMAP=hu;;
is-latin1--*) XMAP=is;;
@@ -1029,7 +1029,7 @@
lt--tj*) XMAP=tj;;
lt--lv*) XMAP=lv;;
lt--mt*) XMAP=mt_us;;
-lt--tr*) XMAP=tr; OPTIONS=tr_f;;
+lt--tr*) XMAP=tr; VARIANT=f;;
lt--uz*) XMAP=uz;;
lt--*) XMAP=lt;;
mac-us-std--*) XMAP=us;;
@@ -1037,7 +1037,7 @@
mac-fr2-ext--*) XMAP=fr;;
mac-fr3--*) XMAP=fr;;
mac-es--*) XMAP=es;;
-mk--tr*) XMAP=tr; OPTIONS=tr_f;;
+mk--tr*) XMAP=tr; VARIANT=f;;
mk--sr*) XMAP=sr;;
mk--hr*) XMAP=hr;;
no-latin1--*) XMAP=no;;
@@ -1065,14 +1065,18 @@
sg-latin1--fr*) XMAP=ch; OPTIONS=fr;;
sk-qwerty--cz*) XMAP=cz_querty;;
sk-qwerty--*) XMAP=sk_querty;;
-sr-cy--tr*) XMAP=tr; OPTIONS=tr_f;;
+sr-cy--tr*) XMAP=tr; VARIANT=f;;
sr-cy--yu*) XMAP=yu;;
sr-cy--*) XMAP=sr;;
+tralt--*) XMAP=tr; VARIANT=alt;;
trfu--hu*) XMAP=hu; OPTIONS=qwerty;;
trfu--yu*) XMAP=yu;;
-trfu--*) XMAP=tr; OPTIONS=tr_f;;
+trf--*) XMAP=tr; VARIANT=f;;
+trfu--*) XMAP=tr; VARIANT=f;;
+trq--*) XMAP=tr;;
+*trqalt*) XMAP=tr; VARIANT=alt;;
trqu--*) XMAP=tr;;
-ua--tr*) XMAP=tr; OPTIONS=tr_f;;
+ua--tr*) XMAP=tr; VARIANT=f;;
ua--by*) XMAP=by;;
ua--*) XMAP=ua;;
uk--mt*) XMAP=mt;;
@@ -1167,6 +1171,15 @@
PRIORITY=high
else
PRIORITY=low
+
+# for Turkish, ensure to add caps:shift to make Caps Lock behave correctly
+if [ $XMAP = tr ]; then
+ case $OPTIONS in
+*caps:shift*) ;; # do nothing if it's already defined
+) OPTIONS=caps:shift ;;
+ *) OPTIONS=$OPTIONS,caps:shift ;;
+ esac
+fi
fi
# we can't do non-Latin usernames, so people with Latin layouts need a US
@@ -1190,6 +1203,7 @@
XKBLAYOUT=$XMAP
XKBOPTIONS=$OPTIONS
+ XKBVARIANT=$VARIANT
else
db_get xserver-xorg/config/inputdevice/keyboard/layout || debug_report_status db_get xserver-xorg/config/inputdevice/keyboard/layout
XKBLAYOUT=$RET
@@ -1234,10 +1248,64 @@
if [ $RET = us ]; then
PRIORITY=low
elif [ $RET = br ]; then
- db_set xserver-xorg/config/inputdevice/keyboard/variant abnt2
+# add abnt2 option
+case $XKBVARIANT in
+ *abnt2*) ;; # do nothing if it's already defined
+ ) XKBVARIANT=abnt2 ;;
+ *) XKBVARIANT=$XKBVARIANT,abnt2 ;;
+esac
fi
+
+db_set xserver-xorg/config/inputdevice/keyboard/variant $XKBVARIANT
MAY_BE_NULL=yes validate_string_db_input $(priority_ceil $PRIORITY) xserver-xorg/config/inputdevice/keyboard/variant
+# handle Turkish keyboard setup specially due to its oddities
+db_get xserver-xorg/config/inputdevice/keyboard/layout
+if [ $RET = tr ]; then
+ TR_KEYMAP=$CONFIG_DIR/xkb/symbols/pc/tr
+
+ db_get xserver-xorg/config/inputdevice/keyboard/variant
+ TR_VARIANT=$RET
+
+ case $TR_VARIANT in
+f|*,f|f,*|*,f,*|*tr_f*)
+ # X.Org version 6.9 uses tr_f, while = 6.9 uses only f
+ if [ -e $TR_KEYMAP ]
+grep -q ^[[:space:]]*xkb_symbols[[:space:]]*\tr_f\ $TR_KEYMAP; then
+SANITIZED_TR_VARIANT=tr_f
+ else
+SANITIZED_TR_VARIANT=f
+ fi
+ ;;
+alt|*,alt|alt,*|*,alt,*|*tr_alt*)
+ # X.Org version 6.9 uses tr_alt
Bug#348027: errors in Turkish keyboard setup
Package: xserver-xorg Severity: important Tags: patch l10n [Due to the similar problems in Ubuntu, CCing to Daniel Stone to let him aware of the situation and also to review the patches attached.] Hi, I've noticed a serious bug in keyboard setup regarding Turkish. What makes Turkish so special in this respect is that, Turkish has three distinct keyboard layouts. The word layout is used here in the physical sense, not as in XkbLayout (this situation causes too much confusion). To make the situation more worst, Turkish keyboard settings differ among the X versions. Here are the different XKB settings[1]: * xfree86 version 4.3 to xorg version 6.8 [2] +---++-+-+ | XkbLayout | XkbVariant | XkbOptions | Description | |===++=+=+ | tr| NONE [3] | caps:shift | qwerty + TR keys [4]| +---++-+-+ | tr| tr_f | caps:shift | fgGIod + TR keys [5]| +---++-+-+ | tr| tr_alt | caps:shift | qwerty + AltGr [6]| +---++-+-+ * xorg version 6.9 and above (including version 7.0) [7] +---++-+-+ | XkbLayout | XkbVariant | XkbOptions | Description | |===++=+=+ | tr| NONE | caps:shift | qwerty + TR keys| +---++-+-+ | tr| f | caps:shift | fgGIod + TR keys| +---++-+-+ | tr| alt| caps:shift | qwerty + AltGr | +---++-+-+ As shown in the tables, Turkish F/Alt keyboards are configured through the XkbVariant; they must neither be configured as an XkbLayout (i.e. tr_f) nor as an entry in XkbOptions which is the current case in xserver-xorg.config: ... trfu--*) XMAP=tr; OPTIONS=tr_f;; trqu--*) XMAP=tr;; ... Apart from such obvious errors, there are some other issues which I would like to fix in the Turkish keyboard setup: * There are 5 Turkish VT keymaps (for i386): trq, trqu, trf, trfu and tralt. Of these, the first two correspond to the Turkish Q layout (the one suffixed with 'u' is the console keymap defined with Unicode code-points), the next two are Turkish F layouts and the last one (tralt) corresponds to the Turkish programmers' Q layout (maps to the XkbVariant 'tr_alt') The current xserver-xorg.config code does not tolerate the changes in console keymap names. (FYI, we've just experienced a bug because of such issues.) * There is no support for tralt which I'm planning to add in d-i. We should also take the sunt5-trqalt keymap into account, the Sun version of tr_alt. Sorry for the keymap mess. :-) * Finally, we should handle the tr_f/f and tr_alt/alt inconsistency gracefully. I've prepared two separate patches targeting all these issues for your convenience. In the first (recommended) patch, which uses a more general approach, I've changed the code to handle XkbVariant through an XKBVARIANT variable. (To eliminate the code duplication, I modified the 'br' setup a little bit, though it could be improved further). The 2nd not-so-invasive patch treats Turkish as an exceptional case. Both of the patches take care of the tr_f/f name change in a somewhat kludgy way (you can remove the this kludge if you feel uncomfortable). Could you please investigate them? I haven't tested them in a real installation, but the logic and shell expressions were tested separately. Hope I haven't missed anything off. Regards, [1] http://necrotic.deadbeast.net/svn/xorg-x11/tags/6.9.0.dfsg.1-3/xc/programs/xkbcomp/symbols/tr As can be seen in the link above, there is the xkb/symbols/tr_f file (along with the xkb/symbols/tr) in the X distribution, which can be specified as a valid XkbLayout entry. But both of the files are _obsolete_. We use the xkb/symbols/pc/tr, an all-in-one file which includes Q, F and Alt layouts as depicted in the table above. [2] http://necrotic.deadbeast.net/svn/xorg-x11/tags/6.8.2.dfsg.1-9/xc/programs/xkbcomp/symbols/pc/tr [3] For Turkish Q layout XkbVariant should be left as empty. There is _no_ such q variant (and specifying it so causes serious problems, as in Ubuntu BZ#17787). [4] http://www.katpatuka.org/pub/doc/keyboard/trq.html [5] http://www.katpatuka.org/pub/doc/keyboard/trf.html [6] In this layout (also known as alternative Turkish Q or programmers' Q layout) Turkish characters are typed by
Bug#348030: Turkish Alt-Q layout support
Package: console-data
Severity: wishlist
Tags: patch l10n
Hi,
Could you please review the patches attached which add d-i+debconf support
for Turkish Alt Q layout. I hope this change doesn't break the current
default selection (trqu) at the kbd-chooser menu[1].
P.S. At the result of these patches, a new message string (tralt) will be
inserted to po template.
Regards,
[1] AFAIK, the default keymap (trqu) must be placed at the end of the
Turkish keymaps list in console-keymaps-{at,acorn}
http://bugs.debian.org/247442
--
roktas
diff -ru console-data-2002.12.04dbs.orig/debian/console-data.config
console-data-2002.12.04dbs/debian/console-data.config
--- console-data-2002.12.04dbs.orig/debian/console-data.config 2006-01-08
03:05:59.0 +0200
+++ console-data-2002.12.04dbs/debian/console-data.config 2006-01-08
03:39:48.0 +0200
@@ -317,8 +317,8 @@
{
default = 'Q Layout',
'Q Layout' = 'trq',
+ 'Alternate Q Layout' = 'tralt',
'Q Layout with Unicode' = 'trqu',
- 'Alternate' = 'tralt',
},
},
'Ukrainian' =
diff -ru console-data-2002.12.04dbs.orig/debian/console-data.keymaps
console-data-2002.12.04dbs/debian/console-data.keymaps
--- console-data-2002.12.04dbs.orig/debian/console-data.keymaps 2006-01-08
03:05:59.0 +0200
+++ console-data-2002.12.04dbs/debian/console-data.keymaps 2006-01-08
03:39:32.0 +0200
@@ -297,8 +297,8 @@
{
default = 'Q Layout',
'Q Layout' = 'trq',
+ 'Alternate Q Layout' = 'tralt',
'Q Layout with Unicode' = 'trqu',
- 'Alternate' = 'tralt',
},
},
'Ukrainian' =
diff -ru console-data-2002.12.04dbs.orig/debian/console-keymaps-acorn.install
console-data-2002.12.04dbs/debian/console-keymaps-acorn.install
--- console-data-2002.12.04dbs.orig/debian/console-keymaps-acorn.install
2006-01-08 03:05:59.0 +0200
+++ console-data-2002.12.04dbs/debian/console-keymaps-acorn.install
2006-01-08 03:12:52.0 +0200
@@ -39,6 +39,7 @@
build-tree/console-data-1999.08.29/keymaps/i386/qwerty/la-latin1.kmap.gz
usr/share/acorn/qwerty
build-tree/console-data-1999.08.29/keymaps/i386/qwertz/fr_CH-latin1.kmap.gz
usr/share/acorn/qwertz
build-tree/console-data-1999.08.29/keymaps/i386/qwertz/sg-latin1.kmap.gz
usr/share/acorn/qwertz
+build-tree/console-data-1999.08.29/keymaps/i386/qwerty/tralt.kmap.gz
usr/share/acorn/qwerty
build-tree/console-data-1999.08.29/keymaps/i386/qwerty/trqu.kmap.gz
usr/share/acorn/qwerty
build-tree/console-data-1999.08.29/keymaps/i386/fgGIod/trfu.kmap.gz
usr/share/acorn/fgGIod
build-tree/console-data-1999.08.29/keymaps-acorn/i386/qwerty/ua-utf.kmap.gz
usr/share/acorn/qwerty
diff -ru console-data-2002.12.04dbs.orig/debian/console-keymaps-acorn.templates
console-data-2002.12.04dbs/debian/console-keymaps-acorn.templates
--- console-data-2002.12.04dbs.orig/debian/console-keymaps-acorn.templates
2006-01-08 03:05:59.0 +0200
+++ console-data-2002.12.04dbs/debian/console-keymaps-acorn.templates
2006-01-08 03:31:05.0 +0200
@@ -1,4 +1,4 @@
Template: console-keymaps-acorn/keymap
Type: select
-__Choices:
by,bg,croat,cz-lat2,sg-latin1,de-latin1-nodeadkeys,dk-latin1,us,uk,dvorak,et,la-latin1,es,fi-latin1,fr-latin9,fr-latin1,be2-latin1,cf,fr_CH-latin1,gr,hebrew,hu,is-latin1,it,lt,lv-latin4,jp106,mk,no-latin1,nl,pl,pt-latin1,br-abnt2,br-latin1,ro,ru,sk-qwerty,slovene,sr-cy,se-latin1,trfu,trqu,ua
+__Choices:
by,bg,croat,cz-lat2,sg-latin1,de-latin1-nodeadkeys,dk-latin1,us,uk,dvorak,et,la-latin1,es,fi-latin1,fr-latin9,fr-latin1,be2-latin1,cf,fr_CH-latin1,gr,hebrew,hu,is-latin1,it,lt,lv-latin4,jp106,mk,no-latin1,nl,pl,pt-latin1,br-abnt2,br-latin1,ro,ru,sk-qwerty,slovene,sr-cy,se-latin1,tralt,trfu,trqu,ua
_Description: Keymap to use:
diff -ru console-data-2002.12.04dbs.orig/debian/console-keymaps-at.install
console-data-2002.12.04dbs/debian/console-keymaps-at.install
--- console-data-2002.12.04dbs.orig/debian/console-keymaps-at.install
2006-01-08 03:05:59.0 +0200
+++ console-data-2002.12.04dbs/debian/console-keymaps-at.install
2006-01-08 03:10:45.0 +0200
@@ -42,6 +42,7 @@
build-tree/console-data-1999.08.29/keymaps/i386/qwerty/la-latin1.kmap.gz
usr/share/keymaps/i386/qwerty
build-tree/console-data-1999.08.29/keymaps/i386/qwertz/fr_CH-latin1.kmap.gz
usr/share/keymaps/i386/qwertz
build-tree/console-data-1999.08.29/keymaps/i386/qwertz/sg-latin1.kmap.gz
usr/share/keymaps/i386/qwertz
+build-tree/console-data-1999.08.29/keymaps/i386/qwerty/tralt.kmap.gz
usr/share/keymaps/i386/qwerty
build-tree/console-data-1999.08.29/keymaps/i386/qwerty/trqu.kmap.gz
Bug#348027: errors in Turkish keyboard setup
* Denis Barbier [2006-01-15 02:06:24+0100] On Sat, Jan 14, 2006 at 10:16:47AM +0200, Recai Oktaş wrote: [...] I've prepared two separate patches targeting all these issues for your convenience. In the first (recommended) patch, which uses a more general approach, I've changed the code to handle XkbVariant through an XKBVARIANT variable. (To eliminate the code duplication, I modified the 'br' setup a little bit, though it could be improved further). The 2nd not-so-invasive patch treats Turkish as an exceptional case. You are right, XkbVariant has to be added to this code, so your first patch is definitely better. But an upload is planned very soon and I do not have the time to check that it does not break anything, so I applied your second one for now and will apply your first one in few days. Thanks for your work. Hi Denis, Thank you very much for your sensitive response. No problem, we can wait. I tested your code, and have one remark: you change tr_f - f when debian-installer/keymap is known, but you may also perform this change after user selected a variant, he may get used to tr_f and not know about this name change. You're right, the second patch is problematic. But as far as I can see it, the first one has not a flaw in this respect, since the TR handling code is in the: if [ -n $RECONFIGURE ] || [ -n $FIRSTINST ]; then body, before the db_inputs. Have I understood it correctly? Regards, -- roktas
Bug#347713: [INTL:tr] Turkish po-debconf update
Package: popularity-contest Severity: wishlist Tags: l10n patch Please find attached the Turkish po-debconf translation. Regards, -- roktas # Turkish translation of popularity-contest. # This file is distributed under the same license as the popularity-contest package. # Ãzgür Murat Homurlu [EMAIL PROTECTED], 2004. # Recai OktaÅ [EMAIL PROTECTED], 2006 # msgid msgstr Project-Id-Version: popularity-contest\n Report-Msgid-Bugs-To: \n POT-Creation-Date: 2005-07-04 08:46+0200\n PO-Revision-Date: 2006-01-12 10:54+0200\n Last-Translator: Recai OktaÅ [EMAIL PROTECTED]\n Language-Team: Debian L10n Turkish debian-l10n-turkish@lists.debian.org\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n X-Generator: KBabel 1.0.2\n Plural-Forms: nplurals=1; plural=0;\n #. Type: boolean #. Description #: ../templates:4 msgid Participate in the Debian Package Popularity Contest? msgstr Debian Popüler Paketler YarıÅması'nda yer almak ister misiniz? #. Type: boolean #. Description #: ../templates:4 msgid You can have your system anonymously supply the Debian developers with statistics about your most used Debian packages. This information influences decisions such as which packages should go on the first Debian CD. msgstr Sisteminizin, en çok kullandıÄınız Debian paketleri hakkında Debian geliÅtiricilerine isimsiz bir e-posta göndermesini saÄlayabilirsiniz. Bu bilgi, birinci Debian CD'si içinde olması gereken paketler gibi bazı kararları etkileyecektir. #. Type: boolean #. Description #: ../templates:4 msgid If you choose to participate, the automatic submission script will run once every week, sending statistics to the Debian developers. msgstr Katılmak isterseniz otomatik gönderim betiÄi haftada bir kez çalıÅacak ve istatistikleri Debian geliÅtiricilerine e-posta ile gönderecektir. #. Type: boolean #. Description #: ../templates:4 msgid You can always change your mind after making this decision: \dpkg- reconfigure popularity-contest\ msgstr Bu kararı verdikten sonra tercihinizi Åu komutla istediÄiniz zaman deÄiÅtirebilirsiniz: \dpkg-reconfigure popularity-contest\ #. Type: note #. Description #: ../templates:17 msgid Generating unique host identifier failed msgstr Makineyi tanımlayan benzersiz bir tanıtıcı üretilemedi #. Type: note #. Description #: ../templates:17 msgid The install script could not generate a unique host identifier. This is a fatal error, as all hosts submitting information need to have an unique identifier. msgstr Kurulum betiÄi benzersiz bir makine tanıtıcısı üretemedi. Bilgi gönderen tüm makinelerin farklı bir tanıtıcıya sahip olması gerektiÄinden bu ölümcül bir hata. #. Type: note #. Description #: ../templates:17 msgid Please report this problem as a bug against the popularity-contest package, and include information about your configuration. msgstr Lütfen bu hatayı popularity-contest paketine iliÅkin bir hata olarak yapılandırma bilgileriyle birlikte raporlayın. #. Type: boolean #. Description #: ../templates:28 msgid Use HTTP to submit reports? msgstr Raporları göndermek için HTTP kullanılsın mı? #. Type: boolean #. Description #: ../templates:28 msgid If you do not want to use HTTP, email is used instead. msgstr HTTP'nin kullanılmasını istemiyorsanız onun yerine e-posta kullanılacaktır. signature.asc Description: Digital signature
Bug#347714: [INTL:tr] Turkish po-debconf update
Package: debconf Severity: wishlist Tags: l10n patch Please find attached the Turkish po-debconf translation. Regards, -- roktas # Turkish messages for debconf. # Copyright (C) 2003, 2004 Software in the Public Interest, Inc. # This file is distributed under the same license as debian-installer. # # Osman Yüksel [EMAIL PROTECTED], 2004. # Recai OktaÅ [EMAIL PROTECTED], 2004, 2006. # Ãzgür Murat Homurlu [EMAIL PROTECTED], 2004. # Halil Demirezen [EMAIL PROTECTED], 2004. # Murat Demirten [EMAIL PROTECTED], 2004. # msgid msgstr Project-Id-Version: debconf\n Report-Msgid-Bugs-To: \n POT-Creation-Date: 2005-12-04 12:55-0700\n PO-Revision-Date: 2006-01-12 11:12+0200\n Last-Translator: Recai OktaÅ [EMAIL PROTECTED]\n Language-Team: Debian L10n Turkish debian-l10n-turkish@lists.debian.org\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n Plural-Forms: nplurals=1; plural=0;\n X-Generator: KBabel 1.9.1\n #. Type: select #. Choices #: ../templates:3 msgid Dialog, Readline, Gnome, Kde, Editor, Noninteractive msgstr Diyalog, Readline, Gnome, Kde, Düzenleyici, EtkileÅimsiz #. Type: select #. Description #: ../templates:5 msgid What interface should be used for configuring packages? msgstr Paketleri yapılandırmak için hangi arayüz kullanılacak? #. Type: select #. Description #: ../templates:5 msgid Packages that use debconf for configuration share a common look and feel. You can select the type of user interface they use. msgstr Yapılandırma için debconf kullanan paketler ortak bir görüntü ve izlenim verirler. Yapılandırmada kullanılacak arayüz tipini seçebilirsiniz. #. Type: select #. Description #: ../templates:5 msgid The dialog frontend is a full-screen, character based interface, while the readline frontend uses a more traditional plain text interface, and both the gnome and kde frontends are modern X interfaces, fitting the respective desktops (but may be used in any X environment). The editor frontend lets you configure things using your favorite text editor. The noninteractive frontend never asks you any questions. msgstr Diyalog arayüzü tam ekran, metin tabanlı bir arayüz sunarken; Readline daha geleneksel bir salt metin arayüzü, gnome ve kde ise kendi masaüstü ortamlarına uygun Åekilde (fakat herhangi bir X ortamı içinde de kullanılabilecek) daha çaÄdaÅ X arayüzleri sunmaktadır. Düzenleyici arayüzü, kullanmayı tercih ettiÄiniz metin düzenleyici ile elle yapılandırmaya olanak saÄlar. EtkileÅimsiz arayüz herhangi bir soru sormaz. #. Type: select #. Choices #: ../templates:18 msgid critical, high, medium, low msgstr kritik, yüksek, orta, düÅük #. Type: select #. Description #: ../templates:20 msgid Ignore questions with a priority less than... msgstr Göz ardı edilecek sorular aÅaÄıdakinden düÅük önceliÄe sahip olacak... #: ../templates:20 msgid Debconf prioritizes the questions it asks you. Pick the lowest priority of question you want to see:\n - 'critical' only prompts you if the system might break.\n Pick it if you are a newbie, or in a hurry.\n - 'high' is for rather important questions\n - 'medium' is for normal questions\n - 'low' is for control freaks who want to see everything msgstr Debconf görüntülediÄi sorulara öncelikler verir. Görmek istediÄiniz sorular için en düÅük önceliÄi seçin:\n - 'kritik' size sadece sistemi bozabilecek durumlarda soru sorar.\n Yeni baÅlayan birisi ya da aceleci birisiyseniz bunu seçin.\n - 'yüksek' önemi daha yüksek sorular\n - 'orta' normal düzeyde sorular\n - 'düÅük' bütün seçenekleri görmek isteyen kontrol düÅkünleri için #. Type: select #. Description #: ../templates:20 msgid Note that no matter what level you pick here, you will be able to see every question if you reconfigure a package with dpkg-reconfigure. msgstr Unutmayın ki paketlerin dpkg-reconfigure komutu ile tekrar yapılandırılması sırasında burada seçtiÄiniz öncelik seviyesi ne olursa olsun bütün soruları görebileceksiniz. #. Type: text #. Description #: ../templates:34 msgid Installing packages msgstr Paketler kuruluyor #. Type: text #. Description #: ../templates:38 msgid Please wait... msgstr Lütfen bekleyin... signature.asc Description: Digital signature
Bug#347494: [INTL:tr] Turkish po-debconf update
Package: xorg-x11 Severity: wishlist Tags: l10n patch Please find attached the Turkish po-debconf translation. Thanks to Osman Yüksel. Regards, -- roktas tr.po.gz Description: Binary data signature.asc Description: Digital signature
