Bug#720138: general: weekly cron crashed

2013-08-19 Thread Vincent Cheng
reassign 720138 app-install-data
forcemerge 716779 720138
thanks

On Sun, Aug 18, 2013 at 11:51 PM, Antoon Pardon  wrote:

> xdg.Exceptions.ParsingError: ParsingError in file '/usr/share/app-
> install/desktop/spout.desktop', Invalid line:
> Categories:Application:Game:ArcadeGame
> run-parts: /etc/cron.weekly/apt-xapian-index exited with return code 1

That looks exactly like bug #716779 [1]. Workaround is to change that
invalid line to something that is valid, i.e.:

Categories=Application;Game;ArcadeGame;

Regards,
Vincent

[1] http://bugs.debian.org/716779


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CACZd_tDTw=XYpOY=zgmka_bfjuoo4d2zzdpfufrrwfyak8g...@mail.gmail.com



Processed: Re: Bug#720138: general: weekly cron crashed

2013-08-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 720138 app-install-data
Bug #720138 [general] general: weekly cron crashed
Bug reassigned from package 'general' to 'app-install-data'.
Ignoring request to alter found versions of bug #720138 to the same values 
previously set
Ignoring request to alter fixed versions of bug #720138 to the same values 
previously set
> forcemerge 716779 720138
Bug #716779 [app-install-data] apt-xapian-index: xdg.Exceptions.ParsingError 
from cron.weekly/apt-xapian-index
Bug #700810 [app-install-data] app-install-data: a typo in spout.desktop
Bug #720138 [app-install-data] general: weekly cron crashed
720138 was not blocked by any bugs.
720138 was not blocking any bugs.
Added blocking bug(s) of 720138: 556938
Marked as found in versions app-install-data/2012.06.16.1.
Added tag(s) confirmed and patch.
Bug #700810 [app-install-data] app-install-data: a typo in spout.desktop
Merged 700810 716779 720138
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
700810: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700810
716779: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716779
720138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720138
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.137690071910277.transcr...@bugs.debian.org



Bug#720196: ITP: vpcs -- Virtual PC Simulator

2013-08-19 Thread Daniel Lintott
Package: wnpp
Severity: wishlist
Owner: Daniel Lintott 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

  Package name: vpcs
  Version : 0.4b2
  Upstream Author : Paul Meng 
  URL : http://sourceforge.net/projects/vpcs/
  License : BSD
  Programming Lang: C
  Description : VPCS can simulate up to 9 PCs. You can ping/traceroute to
them or ping/traceroute to other hosts/routers from the VPCS.
VPCS is not intended to be a fully functional PC.




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

iQEcBAEBAgAGBQJSEjBgAAoJEMw/9yOWzAkJUnYIAIDvVNQ6SQ1edL0huz0oTfVe
8hgjucYCHmU3pxPqN2Fo6/fLqKXvhi3OTvCPLvOkoxv357VOFZsa+iCzfLTSbPbv
AKnX59D9ziFVGw/9g92IGBWl0oC6jjbbNAXSoOx4vIMPmTYB05f1wDCV3NRlc0Kf
Ugthc7Ll0MVs60L2xv2vWMHV4j5aJebEex7AZxcEPpoBXZmelbQyZkYZYUsB8zhf
sLFSopydL4NG+Lj7Qy8awaltfMbuqMeyENCoGIPH58R94dxCUFfTmz3d4mT4nn7t
/G10Db7xmIARQfvu0MwLux1Jv2NydAtEroi1BRrty7QZzyp1fLKJ7l0nEhl52GE=
=4QtV
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130819144904.6349.41861.reportbug@daniel-Mint



Bug#720202: ITP: qreator -- utility for creating QR codes

2013-08-19 Thread Chow Loong Jin
Package: wnpp
Severity: wishlist
Owner: Chow Loong Jin 

* Package name: qreator
  Version : 13.05.3
  Upstream Author : David Planella 
* URL : https://launchpad.net/qreator
* License : GPL-3
  Programming Lang: Python
  Description : utility for creating QR codes

Qreator enables you to easily create your own QR codes to encode different types
of information in an efficient, compact and cool way.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130819152448.17279.741.reportbug@thinkpwn



Re: System resume issues

2013-08-19 Thread Andreas Metzler
Rodolfo García Peñas  wrote:
> currently I am maintaining the uswsusp package. I have some bugs
> related to the resume process [1]. I was talking with Ben in
> debian-kernel, and I am writing to debian-devel trying to get the
> best option to solve the problems and because other packages could
> be affected (cryptsetup, hibernate, pm-utils,...).
[...]

Just a wild thought, as there was  presentation on debconf: Jave you
checked whether dracut (instead od intramfs) handles this better?

cu Andreas



-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pkv9ea-604@argenau.downhill.at.eu.org



Bug#720206: ITP: liblexical-var-perl -- Perl module for using static variables without namespace pollution

2013-08-19 Thread Salvatore Bonaccorso
Package: wnpp
Owner: Salvatore Bonaccorso 
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org,debian-p...@lists.debian.org

* Package name: liblexical-var-perl
  Version : 0.008
  Upstream Author : Andrew Main (Zefram) 
* URL : https://metacpan.org/release/Lexical-Var
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Perl module for using static variables without namespace 
pollution

Lexical::Var implements lexical scoping of subroutines. Although it can be
used directly, it is mainly intended to be infrastructure for modules that
manage namespaces.

This module influences the meaning of single-part subroutine names that
appear directly in code, such as "&foo" and "foo(123)". Normally, in the
absence of any particular declaration, these would refer to the subroutine of
that name located in the current package. A Lexical::Sub declaration can
change this to refer to any particular subroutine, bypassing the package
system entirely. A subroutine name that includes an explicit package part,
such as "&main::foo", always refers to the subroutine in the specified
package, and is unaffected by this module. A symbolic reference through a
string value, such as "&{'foo'}", also looks in the package system, and so is
unaffected by this module.

The types of name that can be influenced are scalar ("$foo"), array
("@foo"), hash ("%foo"), subroutine ("&foo"), and glob ("*foo").


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1376932513.545415.17745@elende



Bug#720209: ITP: libinotify-kqueue -- inotify compatible implementation using kqueue

2013-08-19 Thread Dmitrijs Ledkovs
Package: wnpp
Owner: Dmitrijs Ledkovs 
Severity: wishlist

* Package name: libinotify-kqueue
  Version : upstream snapshot from 20120419
  Upstream Author : Dmitry Matveev 
* URL or Web page : https://github.com/dmatveev/libinotify-kqueue
* License : MIT/BSD
  Description : inotify compatible implementation using kqueue

This package provides an implementation of sys/inotify.h using
kqueue. This is kind of reverse of libkqueue package, as it allows to
compile software on kFreeBSD which otherwise is using Linux specific
inotify API.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87eh9py3tu@debian.org



Dreamhost dumps Debian

2013-08-19 Thread jidanni
http://dreamhost.com/dreamscape/2013/06/03/change-is-in-the-air-dreamhost-upgrades/


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87wqnhpkn3@jidanni.org



Re: Dreamhost dumps Debian

2013-08-19 Thread Vincent Bernat
 ❦ 19 août 2013 21:04 CEST, jida...@jidanni.org :

> http://dreamhost.com/dreamscape/2013/06/03/change-is-in-the-air-dreamhost-upgrades/

Many people seem to justify a switch to Ubuntu LTS with the argument of
5-year security support. This support only applies for packages in
main. A common example is nginx which is in universe. Packages in
universe are just unsupported. They may or may not get any security
support. If you need to advocate for Debian vs Ubuntu, I think this is a
strong argument.
-- 
printk("??? No FDIV bug? Lucky you...\n");
2.2.16 /usr/src/linux/include/asm-i386/bugs.h


signature.asc
Description: PGP signature


Re: Bug#720202: ITP: qreator -- utility for creating QR codes

2013-08-19 Thread Thomas Preud'homme
Le lundi 19 août 2013 23:24:48 Chow Loong Jin a écrit :
> Package: wnpp
> Severity: wishlist
> Owner: Chow Loong Jin 
> 
> * Package name: qreator
>   Version : 13.05.3
>   Upstream Author : David Planella 
> * URL : https://launchpad.net/qreator
> * License : GPL-3
>   Programming Lang: Python
>   Description : utility for creating QR codes
> 
> Qreator enables you to easily create your own QR codes to encode different
> types of information in an efficient, compact and cool way.

Greetings Loong Jin,

Since it seems there is already a qr generator in Debian (qrencode), I suppose 
qreator has some feature that are lacking in qrencode. Could you develop 
those? That would be especially useful in the long description so that a user 
looking for a tool creating a qr code have enough information to choose 
between these two packages.

Best regards,

Thomas

signature.asc
Description: This is a digitally signed message part.


Re: Dreamhost dumps Debian

2013-08-19 Thread Clint Byrum
Excerpts from Vincent Bernat's message of 2013-08-19 12:34:17 -0700:
>  ❦ 19 août 2013 21:04 CEST, jida...@jidanni.org :
> 
> > http://dreamhost.com/dreamscape/2013/06/03/change-is-in-the-air-dreamhost-upgrades/
> 
> Many people seem to justify a switch to Ubuntu LTS with the argument of
> 5-year security support. This support only applies for packages in
> main. A common example is nginx which is in universe. Packages in
> universe are just unsupported. They may or may not get any security
> support. If you need to advocate for Debian vs Ubuntu, I think this is a
> strong argument.

Most places as large and tech-savvy as Dreamhost are happy to maintain
something at the core of their business like a webserver (i.e. nginx). It
is glibc, gcc, sshd, the kernel, bash, etc., that they don't want to
have to think about.

The 2 year cadence has left users with very little time to actually
capitalize on their investment when upgrading. If one has 10 apps to
test and roll out on the new stable, and each app takes 1 month to get
there, and one starts immediately on release day, one now has 14 months
to recoup that time investment before one must start again. The only
real answer that makes sense is to continuously deploy on unstable,
but then you will suffer when a massive breaking transition begins.

Those 5 year cycles just give users more cushion.

Also, if you're going to argue Debian vs. Ubuntu, you are going to argue
that volunteer maintainers on _all_ packages are more desirable than
paid maintainers on the core OS that you don't want to care about. I am
not sure that is an argument that I could win, but maybe you are more
persuasive than I am.

Debian has its place in businesses, however I think we will find more
businesses willing to accept Ubuntu's drawbacks than Debian's.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1376942753-sup-2...@fewbar.com



Re: Dreamhost dumps Debian

2013-08-19 Thread Russ Allbery
Clint Byrum  writes:

> Most places as large and tech-savvy as Dreamhost are happy to maintain
> something at the core of their business like a webserver
> (i.e. nginx). It is glibc, gcc, sshd, the kernel, bash, etc., that they
> don't want to have to think about.

> The 2 year cadence has left users with very little time to actually
> capitalize on their investment when upgrading. If one has 10 apps to
> test and roll out on the new stable, and each app takes 1 month to get
> there, and one starts immediately on release day, one now has 14 months
> to recoup that time investment before one must start again. The only
> real answer that makes sense is to continuously deploy on unstable, but
> then you will suffer when a massive breaking transition begins.

> Those 5 year cycles just give users more cushion.

Not that it helps with our marketing posture here, but my experience in
seeing what people actually *do* with Ubuntu LTS is that they run it for
five years with exactly the software that shipped with it.  They do *not*
maintain their own versions of non-core software that has had security
problems.  Rather, they just blindly assume that LTS having security
support for five years means that, as long as they regularly upgrade, they
don't have to worry about security.

They therefore end up running various non-core software with open security
vulnerabilities.

This is mostly neither here nor there, since we're not Ubuntu and can't
change anything about their model.  However, as a Debian Developer, I
would be extremely uncomfortable about having tiers of security support
for our packages were we to try to duplicate something like LTS.  I
believe the actual effect on the users (unintended though it may be) is to
deceive them into thinking they have security support when they don't.
Debian currently provides security support for the whole archive as best
as we can for the life of our stable release, and I don't think we should
relax that standard to increase the lifetime of stable.

-- 
Russ Allbery (r...@debian.org)   


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/871u5pmmlf@windlord.stanford.edu



Re: Dreamhost dumps Debian

2013-08-19 Thread Pau Garcia i Quiles
On Mon, Aug 19, 2013 at 9:34 PM, Vincent Bernat  wrote:

>  ❦ 19 août 2013 21:04 CEST, jida...@jidanni.org :
>
> >
> http://dreamhost.com/dreamscape/2013/06/03/change-is-in-the-air-dreamhost-upgrades/
>
> Many people seem to justify a switch to Ubuntu LTS with the argument of
> 5-year security support. This support only applies for packages in
> main. A common example is nginx which is in universe. Packages in
> universe are just unsupported. They may or may not get any security
> support. If you need to advocate for Debian vs Ubuntu, I think this is a
> strong argument.
>

The fact that Debian only supports stable releases for about 1 year after
the release of the next version does not exactly help make a case against
Ubuntu, even now that non-LTS get only 12 months (instead of the former 18
months) of support. Maybe longer support terms for stable versions of
Debian would help (3 years?).

Also, many advanced users of Ubuntu end up contacting the Debian packager
for updates, fixes, backports, etc Even through Launchpad directly (the
Debian maintainer is shown as the package maintainer and receives e-mail
automatically)

-- 
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)


Re: Dreamhost dumps Debian

2013-08-19 Thread Vincent Bernat
 ❦ 19 août 2013 22:19 CEST, Clint Byrum  :

>> Many people seem to justify a switch to Ubuntu LTS with the argument of
>> 5-year security support. This support only applies for packages in
>> main. A common example is nginx which is in universe. Packages in
>> universe are just unsupported. They may or may not get any security
>> support. If you need to advocate for Debian vs Ubuntu, I think this is a
>> strong argument.
>
> Most places as large and tech-savvy as Dreamhost are happy to maintain
> something at the core of their business like a webserver (i.e. nginx). It
> is glibc, gcc, sshd, the kernel, bash, etc., that they don't want to
> have to think about.
>
> The 2 year cadence has left users with very little time to actually
> capitalize on their investment when upgrading. If one has 10 apps to
> test and roll out on the new stable, and each app takes 1 month to get
> there, and one starts immediately on release day, one now has 14 months
> to recoup that time investment before one must start again. The only
> real answer that makes sense is to continuously deploy on unstable,
> but then you will suffer when a massive breaking transition begins.
>
> Those 5 year cycles just give users more cushion.

Russ already replied and I agree with its reply. Just to say that Debian
usually has a 3 year support. This is the kind of misguiding that I
usually hear when people promotes Ubuntu over Debian.

> Also, if you're going to argue Debian vs. Ubuntu, you are going to argue
> that volunteer maintainers on _all_ packages are more desirable than
> paid maintainers on the core OS that you don't want to care about. I am
> not sure that is an argument that I could win, but maybe you are more
> persuasive than I am.

Please, this is FUD. Stick to the facts. What core packages is of lesser
quality in Debian than in Ubuntu?
-- 
 /*
  * For moronic filesystems that do not allow holes in file.
  * We may have to extend the file.
  */
2.4.0-test2 /usr/src/linux/fs/buffer.c


signature.asc
Description: PGP signature


Re: Dreamhost dumps Debian

2013-08-19 Thread Clint Byrum
Excerpts from Russ Allbery's message of 2013-08-19 13:50:36 -0700:
> Clint Byrum  writes:
> 
> > Most places as large and tech-savvy as Dreamhost are happy to maintain
> > something at the core of their business like a webserver
> > (i.e. nginx). It is glibc, gcc, sshd, the kernel, bash, etc., that they
> > don't want to have to think about.
> 
> > The 2 year cadence has left users with very little time to actually
> > capitalize on their investment when upgrading. If one has 10 apps to
> > test and roll out on the new stable, and each app takes 1 month to get
> > there, and one starts immediately on release day, one now has 14 months
> > to recoup that time investment before one must start again. The only
> > real answer that makes sense is to continuously deploy on unstable, but
> > then you will suffer when a massive breaking transition begins.
> 
> > Those 5 year cycles just give users more cushion.
> 
> Not that it helps with our marketing posture here, but my experience in
> seeing what people actually *do* with Ubuntu LTS is that they run it for
> five years with exactly the software that shipped with it.  They do *not*
> maintain their own versions of non-core software that has had security
> problems.  Rather, they just blindly assume that LTS having security
> support for five years means that, as long as they regularly upgrade, they
> don't have to worry about security.
> 
> They therefore end up running various non-core software with open security
> vulnerabilities.
> 

Indeed, that is consistent with the anecdotal evidence I have for Ubuntu
as well. Most of mine comes from triaging bugs and answering questions
for Ubuntu users.

However for a high-tech business in the same class as Dreamhost, even core
components of the OS come under scrutiny when they affect the bottom line.

> This is mostly neither here nor there, since we're not Ubuntu and can't
> change anything about their model.  However, as a Debian Developer, I
> would be extremely uncomfortable about having tiers of security support
> for our packages were we to try to duplicate something like LTS.  I
> believe the actual effect on the users (unintended though it may be) is to
> deceive them into thinking they have security support when they don't.
> Debian currently provides security support for the whole archive as best
> as we can for the life of our stable release, and I don't think we should
> relax that standard to increase the lifetime of stable.
> 

It is misleading and many users fall into the trap. However, those who
care enough to read their manuals and/or contact either Canonical or
another Ubuntu developer before building their entire business on top
of it usually understand the difference.

I am not suggesting any changes to Debian. I hope that I can bring some
perspective to the discussion, nothing more.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1376947589-sup-5...@fewbar.com



Re: Dreamhost dumps Debian

2013-08-19 Thread Clint Byrum
Excerpts from Vincent Bernat's message of 2013-08-19 14:12:25 -0700:
>  ❦ 19 août 2013 22:19 CEST, Clint Byrum  :
> 
> >> Many people seem to justify a switch to Ubuntu LTS with the argument of
> >> 5-year security support. This support only applies for packages in
> >> main. A common example is nginx which is in universe. Packages in
> >> universe are just unsupported. They may or may not get any security
> >> support. If you need to advocate for Debian vs Ubuntu, I think this is a
> >> strong argument.
> >
> > Most places as large and tech-savvy as Dreamhost are happy to maintain
> > something at the core of their business like a webserver (i.e. nginx). It
> > is glibc, gcc, sshd, the kernel, bash, etc., that they don't want to
> > have to think about.
> >
> > The 2 year cadence has left users with very little time to actually
> > capitalize on their investment when upgrading. If one has 10 apps to
> > test and roll out on the new stable, and each app takes 1 month to get
> > there, and one starts immediately on release day, one now has 14 months
> > to recoup that time investment before one must start again. The only
> > real answer that makes sense is to continuously deploy on unstable,
> > but then you will suffer when a massive breaking transition begins.
> >
> > Those 5 year cycles just give users more cushion.
> 
> Russ already replied and I agree with its reply. Just to say that Debian
> usually has a 3 year support. This is the kind of misguiding that I
> usually hear when people promotes Ubuntu over Debian.
> 

My bad. It is misleading because I put the support cadence of Ubuntu in
a comparison with the development cadence of Debian (~2 years).

> > Also, if you're going to argue Debian vs. Ubuntu, you are going to argue
> > that volunteer maintainers on _all_ packages are more desirable than
> > paid maintainers on the core OS that you don't want to care about. I am
> > not sure that is an argument that I could win, but maybe you are more
> > persuasive than I am.
> 
> Please, this is FUD. Stick to the facts. What core packages is of lesser
> quality in Debian than in Ubuntu?

I did not claim that there is less quality. I am claiming that I
personally cannot argue with a business that there is less risk.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1376947916-sup-4...@fewbar.com



Re: arm laptops and d-i

2013-08-19 Thread Shawn
I'm writing this from the Samsung ARM chromebook, running Debian

https://wiki.debian.org/InstallingDebianOn/Samsung/ARMChromebook


On Tue, Aug 13, 2013 at 3:54 PM, Adam Borowski  wrote:

> I loathe laptops, and thus didn't own one.  Needing one for DebConf (and
> this time no friend had a working one for me to borrow), instead of getting
> an used x86 one, I bought a $150 13.3" android thing.  Because, you know,
> installing a certain universal operating system should be easy, especially
> if it's a popular SoC (Allwinner) and graphics chip (Mali 400), right?
> Oh naive me.
>
> It took me way too much time to figure it out, and I'm not exactly a
> Debian newbie (although no experience with laptops or arm bootloaders).
> The main block was no way to reflash the machine to a working state,
> making me afraid to touch the nand bootloader in a non-obvious way.  That
> is, until I learned that Allwinners boot first from a sd card; all you
> need to do is to put an ubooted kernel into the right place and copy
> appropriate code into sectors before the first partition.  Sounds...
> familiar.  That's not enough, of course, as without a module "lcd" there's
> no display, etc -- debugging which requires moving the sd card, plopping
> qemu-static-arm onto it and installing sshd.  Same for trying anything
> else.
>
> Now imagine a regular user trying that...
>
> So, whom do I beat with this laptop to get d-i working?
>
> Looks like a substantial part of Allwinner drivers got converted to DT in
> 3.8, 3.10 and 3.11 kernels, so it might work without a device-specific
> kernel.
>
> Thus, if anyone would like to play with such an exotic laptop, feel free
> to either catch me on debconf, or send me d-i images to test...  It's an
> Omega OAN133, not a widespread piece of hardware, but we need to do
> something with incoming flood of Chromebooks and so on.
>
> --
> ᛊᚨᚾᛁᛏᚣ᛫ᛁᛊ᛫ᚠᛟᚱ᛫ᚦᛖ᛫ᚹᛖᚨᚲ
>
>
> --
> To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive: http://lists.debian.org/20130813225427.gd3...@angband.pl
>
>


-- 

---
Shawn Landden
+1 360 389 3001 (SMS preferred)


Re: Dreamhost dumps Debian

2013-08-19 Thread Charles Plessy
Le Mon, Aug 19, 2013 at 11:12:25PM +0200, Vincent Bernat a écrit :
> 
> Just to say that Debian usually has a 3 year support.

Hi Vincent,

this actually misleading for systems that have a long lifetime, where the
turnover matters more, and in Debian it is 2 years.  In some workplaces It
means that every second year, some people would have to discuss and reach an
agreement on whether it is doable to upgrade a service, how much it will cost,
or should it be discontinued or not, etc.  There, the 5-year or longer turnover
in Ubuntu or CentOS is a winning point.

A long term support for core packages would definitely help me to advocate
Debian in my workplace (and therefore use it on our servers instead of CentOS).
Also, I do not think that it is relaxing our standards, since it is an
additional service: there is no reduction in the current support.

For the potential confusion, it is also a matter of documentation and
communication.  Since experience shows that people are mislead by the LTS
brand, my conclusion is that we would need to find a better name, and a better
mechanism than an implicit choice in the sources.list file.

However, one difficulty that was not mentionned in this thread is that if we
aim at both long term support and frequent releases, then we need to support
users skipping releases or upgrading multiple releases in a row.

Altogether, it is a lot of work, but if we have enough people for doing it, I
think that it would be very positive for us.

Cheers,

-- 
Charles Plessy
Tsurumi, Kanagawa, Japan


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2013082440.ga25...@falafel.plessy.net



Re: arm laptops and d-i

2013-08-19 Thread Adam Borowski
On Mon, Aug 19, 2013 at 04:27:31PM -0700, Shawn wrote:
> I'm writing this from the Samsung ARM chromebook, running Debian
> 
> https://wiki.debian.org/InstallingDebianOn/Samsung/ARMChromebook

Ouch... that's substantially less pleasant than Omega Oan, with respect to
both installation and usability once installed.  And also there's a load of
magical key combinations that you can't figure on your own.

In the end, the only thing I was lacking was a "battery_lid" control that
gives a battery meter (a nice thing to have on a laptop...) and notifies
about closing/opening the lid.

Another minor glitch was the proprietary graphics driver causing visual
corruption during scrolling; installing it was pointless as I never once
ran a GLES program, I lost track of steps I would need to undo though.
If I knew, I'd run entirely free software.

In all other regards, it's a regular laptop, just with a badly underpowered
CPU.  But hey, $150 new for a full-sized laptop, enough for a thin client if
you have a server in a hacklab or ssh home.  And then you're back to the
land of comfortable keyboards and multiple large screens.  (Some of you
might not hate laptops as much as I do.)

[Wookey: those keyboard problems were my fault, I force-unglued stuff inside
trying to take a look at the innards; the glue turned out to be structurally
important for not letting the keyboard buckle up.  I just had to get some
glue from a shop in Neuchatel to fix it.]

-- 
ᛊᚨᚾᛁᛏᚣ᛫ᛁᛊ᛫ᚠᛟᚱ᛫ᚦᛖ᛫ᚹᛖᚨᚲ


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130820005723.ga17...@angband.pl



Re: Bug#720202: ITP: qreator -- utility for creating QR codes

2013-08-19 Thread Chow Loong Jin
Greetings Thomas,

On Mon, Aug 19, 2013 at 10:16:11PM +0200, Thomas Preud'homme wrote:
> [...]
> Since it seems there is already a qr generator in Debian (qrencode), I 
> suppose 
> qreator has some feature that are lacking in qrencode. Could you develop 
> those? That would be especially useful in the long description so that a user 
> looking for a tool creating a qr code have enough information to choose 
> between these two packages.

Whoops, I've uploaded it already. You're right, the description is a little
vague when trying to choose between the two utilities. I'll amend the
description and reupload soon.

-- 
Kind regards,
Loong Jin


signature.asc
Description: Digital signature


Re: Dreamhost dumps Debian

2013-08-19 Thread Andrew Starr-Bochicchio
On Mon, Aug 19, 2013 at 5:05 PM, Pau Garcia i Quiles
 wrote:
> Also, many advanced users of Ubuntu end up contacting the Debian packager
> for updates, fixes, backports, etc Even through Launchpad directly (the
> Debian maintainer is shown as the package maintainer and receives e-mail
> automatically)

Ubuntu had to make a decision on how to best handle the maintainer
information for packages synced directly from Debian. On the one hand,
you want to acknowledge the work of others. On the other, you don't
want the Debian maintainer blamed/bothered by users for issues with
the package that are Ubuntu specific. This is the resulting
compromise: https://wiki.ubuntu.com/DebianMaintainerField

That said, Debian maintainers should not be receiving automatic emails
without explicitly opting in. If they do, that is a bug that should be
fixed.

Thanks,

-- Andrew Starr-Bochicchio

   Ubuntu Developer 
   Debian Developer 
   PGP/GPG Key ID: D53FDCB1


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cal6k_axy_tf5m9acfqskyrbfbt08ufyby6ek54jmnqhjzfm...@mail.gmail.com



Bug#720282: ITP: python-nine -- Python 2 / 3 compatibility, like six, but favouring Python 3

2013-08-19 Thread TANIGUCHI Takaki
Package: wnpp
Owner: tak...@debian.org
Severity: wishlist

* Package name: python-nine
  Version : 0.3.3
  Upstream Author : Nando Florestan
* URL or Web page : https://pypi.python.org/pypi/nine
* License : Public Domain
  Description : Python 2 / 3 compatibility, like six, but favouring Python 3
 When thou writeth Python, thou shalt write Python 3 and, just for a
 while, ensure that the thing worketh on Python 2.7 and, possibly, even
 2.6.
 .
 Just before Python 2 is finally phased out, thine codebase shall look
 more like 3 than like 2.
 .
 nine facilitates this new point of view. You can write code that is
 as 3ish as possible while still supporting 2.6. Very comfortable for
 writing new projects.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87zjsdce93.wl%tak...@debian.org



Re: Dreamhost dumps Debian

2013-08-19 Thread Michael Gilbert
On Mon, Aug 19, 2013 at 5:12 PM, Vincent Bernat wrote:
>  ❦ 19 août 2013 22:19 CEST, Clint Byrum
>
>>> Many people seem to justify a switch to Ubuntu LTS with the argument of
>>> 5-year security support. This support only applies for packages in
>>> main. A common example is nginx which is in universe. Packages in
>>> universe are just unsupported. They may or may not get any security
>>> support. If you need to advocate for Debian vs Ubuntu, I think this is a
>>> strong argument.
>>
>> Most places as large and tech-savvy as Dreamhost are happy to maintain
>> something at the core of their business like a webserver (i.e. nginx). It
>> is glibc, gcc, sshd, the kernel, bash, etc., that they don't want to
>> have to think about.
>>
>> The 2 year cadence has left users with very little time to actually
>> capitalize on their investment when upgrading. If one has 10 apps to
>> test and roll out on the new stable, and each app takes 1 month to get
>> there, and one starts immediately on release day, one now has 14 months
>> to recoup that time investment before one must start again. The only
>> real answer that makes sense is to continuously deploy on unstable,
>> but then you will suffer when a massive breaking transition begins.
>>
>> Those 5 year cycles just give users more cushion.
>
> Russ already replied and I agree with its reply. Just to say that Debian
> usually has a 3 year support. This is the kind of misguiding that I
> usually hear when people promotes Ubuntu over Debian.

I know already that this isn't a popular idea, but another option
would be to release less often.  If releases were every 3 years, then
the support window would be 4 years, which almost gets to the apparent
sweet spot of 5.

Also, if freeze trends continue (10 months for wheezy), this has the
benefit of reducing the freeze/development ratio; 10/24 = 42% is a
rather large percentage :(.

Plus, Ben Hutchings is putting together a plan to add support for
newer hardware in stable releases:
http://lists.debian.org/debian-boot/2013/08/msg00090.html

Presumably, continuing to support newer hardware will improve the
useful lifetime of releases.

Best wishes,
Mike


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CANTw=MPS7nStpVOP+nwmZMZ68Vi6w1_X9uVzX7G8oajVe_Bt=g...@mail.gmail.com



Bug#720291: ITP: puppet-module-puppetlabs-concat -- Puppet module that can construct files from fragments

2013-08-19 Thread Thomas Bechtold
Package: wnpp
Severity: wishlist
Owner: Thomas Bechtold 

* Package name: puppet-module-puppetlabs-concat
  Version : 1.0.0
  Upstream Author : Puppet Labs Inc 
* URL : http://forge.puppetlabs.com/puppetlabs/concat
* License : Apache 2.0
  Programming Lang: Ruby
  Description : Puppet module that can construct files from fragments

 Puppet lets you centrally manage every important aspect of your system
 using a cross-platform specification language that manages all the
 separate elements normally aggregated in different files, like users,
 cron jobs, and hosts, along with obviously discrete elements like
 packages, services, and files.
 .
 Puppet's simple declarative specification language provides powerful
 classing abilities for drawing out the similarities between hosts while
 allowing them to be as specific as necessary, and it handles dependency
 and prerequisite relationships between objects clearly and explicitly.
 .
 This package contains a Puppet module that can construct files from
 fragments.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130820055645.9953.52276.report...@avocado.fritz.box



Bug#720294: ITP: puppet-module-puppetlabs-vswitch -- Puppet module for vSwitches

2013-08-19 Thread Thomas Bechtold
Package: wnpp
Severity: wishlist
Owner: Thomas Bechtold 

* Package name: puppet-module-puppetlabs-vswitch
  Version : 0.1.1
  Upstream Author : Puppet Labs Inc 
* URL : http://forge.puppetlabs.com/puppetlabs/vswitch
* License : Apache 2.0
  Programming Lang: Ruby
  Description : Puppet module for vSwitches
 Puppet lets you centrally manage every important aspect of your system
 using a cross-platform specification language that manages all the
 separate elements normally aggregated in different files, like users,
 cron jobs, and hosts, along with obviously discrete elements like
 packages, services, and files.
 .
 Puppet's simple declarative specification language provides powerful
 classing abilities for drawing out the similarities between hosts while
 allowing them to be as specific as necessary, and it handles dependency
 and prerequisite relationships between objects clearly and explicitly.
 .
 This package contains a Puppet module for vSwitches.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130820064313.10726.42042.report...@avocado.fritz.box