Request for documentation about creation of Debian Language Packs

2015-10-06 Thread Linus Hughes
Hello, I would like to request some documentation be provided to the public forums or just myself appertaining the process of how a person can create a unique language pack for Debian. A couple of example language packs which could be created of community members would be, Personal English for p

Re: Request for documentation about creation of Debian Language Packs

2015-10-06 Thread Riley Baird
On Mon, 5 Oct 2015 12:46:11 -0500 Zeus Hughes wrote: > Hello, > > I would like to request some documentation be provided to the public forums > or just myself appertaining the process of how a person can create a unique > language pack for Debian. I can't find any documentation on how to do thi

Re: init script, installed but not activated

2015-10-06 Thread Matt Zagrabelny
On Tue, Oct 6, 2015 at 3:16 PM, Antonio Terceiro wrote: > On Tue, Oct 06, 2015 at 10:47:28PM +0300, Hleb Valoshka wrote: >> Hi all. >> >> I'm packaging web server for ruby called unicorn. The package installs >> sysv init script, I want to make it installed but not activated >> because unicorn its

Re: init script, installed but not activated

2015-10-06 Thread Michael Biebl
Am 06.10.2015 um 22:16 schrieb Antonio Terceiro: > On Tue, Oct 06, 2015 at 10:47:28PM +0300, Hleb Valoshka wrote: >> Hi all. >> >> I'm packaging web server for ruby called unicorn. The package installs >> sysv init script, I want to make it installed but not activated >> because unicorn itself is u

Re: init script, installed but not activated

2015-10-06 Thread Antonio Terceiro
On Tue, Oct 06, 2015 at 10:47:28PM +0300, Hleb Valoshka wrote: > Hi all. > > I'm packaging web server for ruby called unicorn. The package installs > sysv init script, I want to make it installed but not activated > because unicorn itself is useless, user should configure it and > activate it with

init script, installed but not activated

2015-10-06 Thread Hleb Valoshka
Hi all. I'm packaging web server for ruby called unicorn. The package installs sysv init script, I want to make it installed but not activated because unicorn itself is useless, user should configure it and activate it with "update-rc.d unicorn enable". Or it may installed as dependency for rainbo

Re: Defaulting to i686 for the Debian i386 architecture

2015-10-06 Thread Christoph Biedl
Konstantin Khomoutov wrote... > On Tue, 6 Oct 2015 18:52:28 +0300 > Lars Wirzenius wrote: > > > Would it be useful to have something like that script in a package? If > > so, which package? > > To me, this is something to probably put into the release notes for the > next release if the origina

Re: Defaulting to i686 for the Debian i386 architecture

2015-10-06 Thread Christoph Biedl
Ben Hutchings wrote... > So far as I know the required feature flags are: fpu tsc cx8 cmov; > and the CPUs that have them are: Thanks for that. So for the records, VIA C3 Ezra and AMD-K6 lack cmov and therefore will fall out of support. I see no reason why there should be an exception for these,

Re: Defaulting to i686 for the Debian i386 architecture

2015-10-06 Thread Konstantin Khomoutov
On Tue, 6 Oct 2015 18:52:28 +0300 Lars Wirzenius wrote: > > A minor heads-up: your script incorrectly uses "tac" instead of > > "tsc". > > If anyone wants to put this into a package, please fix that. :) > > Would it be useful to have something like that script in a package? If > so, which packa

Bug#801134: general: Laptops's external screen is blank despite still recognised by Settings>Dispaly

2015-10-06 Thread Pantelis
Package: general Severity: important Dear Maintainer, I have lost the ability to share a screen through VGA. The screen is still recognised in Settings>Dispaly but it remains black. Withing Settings>Display I have options to turn the screen off, set as primary or secondary display or just mirro

Re: Defaulting to i686 for the Debian i386 architecture

2015-10-06 Thread Lars Wirzenius
On Tue, Oct 06, 2015 at 04:45:08PM +0300, Konstantin Khomoutov wrote: > A minor heads-up: your script incorrectly uses "tac" instead of "tsc". If anyone wants to put this into a package, please fix that. :) Would it be useful to have something like that script in a package? If so, which package?

Bug#801133: ITP: node-tern -- JavaScript code analyzer for text editors

2015-10-06 Thread James Cowgill
Package: wnpp Severity: wishlist Owner: James Cowgill X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-tern   Version : 0.15.0   Upstream Author : Marijn Haverbeke * URL : https://github.com/marijnh/tern * License : Expat   Programming Lang: JavaSc

Earn Credits at Home Effortlessly

2015-10-06 Thread Candice at Namaya

Re: Defaulting to i686 for the Debian i386 architecture

2015-10-06 Thread Konstantin Khomoutov
On Tue, 6 Oct 2015 12:04:29 +0300 Lars Wirzenius wrote: > On Tue, Oct 06, 2015 at 10:47:43AM +0200, Jakub Wilk wrote: > > * Philip Hands , 2015-10-06, 09:35: > > > sed -ne '/^flags\t/{s/\b\(fpu\|tsc\|cx8\|cmov\)\b/%/g;s/[^% > > > ]*//g;s//i686 SUPPORTED/p}' /proc/cpuinfo > > > > Or a more re

Re: is the whole unstable still broken by gcc-5?

2015-10-06 Thread Vincent Lefevre
On 2015-09-13 23:57:13 +0200, Paul Wise wrote: > This config option improves the aptitude resolver for some situations: > > /etc/apt/apt.conf.d/99aptitude-resolver: > Aptitude::ProblemResolver { SolutionCost "removals"; } Unfortunately this has the consequence that aptitude sometimes wants to dow

Re: Defaulting to i686 for the Debian i386 architecture

2015-10-06 Thread Jakub Wilk
* Lars Wirzenius , 2015-10-06, 12:04: sed -ne '/^flags\t/{s/\b\(fpu\|tsc\|cx8\|cmov\)\b/%/g;s/[^%]*//g;s//i686 SUPPORTED/p}' /proc/cpuinfo Or a more readable version: [ $(lscpu | grep ^Flags: | grep -owE 'fpu|tsc|cx8|cmov' | wc -l) = 4 ] && echo i686 SUPPORTED Phil's second one works fo

Re: Defaulting to i686 for the Debian i386 architecture

2015-10-06 Thread Lars Wirzenius
On Tue, Oct 06, 2015 at 10:47:43AM +0200, Jakub Wilk wrote: > * Philip Hands , 2015-10-06, 09:35: > > sed -ne > > '/^flags\t/{s/\b\(fpu\|tsc\|cx8\|cmov\)\b/%/g;s/[^%]*//g;s//i686 > > SUPPORTED/p}' /proc/cpuinfo > > Or a more readable version: > > [ $(lscpu | grep ^Flags: | grep -owE 'fpu|ts

Re: Defaulting to i686 for the Debian i386 architecture

2015-10-06 Thread Jakub Wilk
* Philip Hands , 2015-10-06, 09:35: sed -ne '/^flags\t/{s/\b\(fpu\|tsc\|cx8\|cmov\)\b/%/g;s/[^%]*//g;s//i686 SUPPORTED/p}' /proc/cpuinfo Or a more readable version: [ $(lscpu | grep ^Flags: | grep -owE 'fpu|tsc|cx8|cmov' | wc -l) = 4 ] && echo i686 SUPPORTED -- Jakub Wilk

Re: Defaulting to i686 for the Debian i386 architecture

2015-10-06 Thread Philip Hands
Philip Hands writes: > For those wanting to check their systems, this may help: > > sed -ne '/^flags /{s/\b\(fpu\|tsc\|cx8\|cmov\)\b/%/g;s/[^%]*//g;s//i686 > SUPPORTED/p}' /proc/cpuinfo Oops - that's meant to be a TAB. Make that: sed -ne '/^flags\t/{s/\b\(fpu\|tsc\|cx8\|cmov\)\b/%/g;s/

Re: Defaulting to i686 for the Debian i386 architecture

2015-10-06 Thread Philip Hands
Ben Hutchings writes: > On Mon, 2015-10-05 at 20:43 +0200, Christoph Biedl wrote: >> Ben Hutchings wrote... >> >> > We propose to drop support for i386 processors older than 686-class in >> > the current release cycle. This would include folding libc6-i686 into >> > libc6, changing the default