Bug#712630: ITP: pyqt5 -- Python bindings for Qt5

2013-06-17 Thread Scott Kitterman
Package: wnpp Severity: wishlist Owner: Scott Kitterman * Package name: pyqt5 Version : 5.0 Upstream Author : Riverbank Computing Limited * URL : http://www.riverbankcomputing.com/software/pyqt/download5 * License : GPLv3 Programming Lang: Python Descriptio

Re: RFH: two base wheezy bugs

2013-06-17 Thread Don Armstrong
On Sun, 16 Jun 2013, Daniel Pocock wrote: > Being able to systematically link bugs to hardware would be useful, > then other owners of the same hardware would (a) be able to check for > outstanding bugs before upgrading (b) try to reproduce and confirm > bugs The summary feature could be used to d

Recommend documentation

2013-06-17 Thread Salvo Tomaselli
I have noticed that a number of packages tend to recommend documentation, which is then by default normally installed. Is there a policy for that? See for example #648443 Using dpkg I found a number of latex -doc packages installed with recommends for the total size of 694MB. The policy state

Re: wrong configuration in daemon

2013-06-17 Thread Salvo Tomaselli
In data domenica 16 giugno 2013 18.39.46, Luca Filipozzi ha scritto: > On Sun, Jun 16, 2013 at 08:28:18PM +0200, Salvo Tomaselli wrote: > > I have a question concerning a bugreport I got, but that could be quite > > general. > > > > Let's say a daemon provides POP and IMAP, and is configured to pr

Re: Bug#712539: ITP: encuentro -- Access the content of the Encuentro channel, and others

2013-06-17 Thread Ben Hutchings
On Mon, 2013-06-17 at 22:30 +0200, Maximiliano Curia wrote: > ¡Hola thomas! > > El Monday, June 17, 2013 a las 19:14 escribiste: > > On Monday, June 17, 2013 12:57:34 AM Maximiliano Curia wrote: > > > * Package name: encuentro > > > Version : 1.0 > > > Description : Access the

Re: jessie release goal: verbose build logs

2013-06-17 Thread gregor herrmann
On Fri, 14 Jun 2013 14:14:39 +0200, Jakub Wilk wrote: > >- File and track issues for packages not enabling verbose builds. > >https://buildd.debian.org/~brlink/bytag/W-compiler-flags-hidden.html > > I attached a dd-list for the lazy. But note that "false positives > are possible, especially when

Re: Bug#712539: ITP: encuentro -- Access the content of the Encuentro channel, and others

2013-06-17 Thread Maximiliano Curia
¡Hola thomas! El Monday, June 17, 2013 a las 19:14 escribiste: > On Monday, June 17, 2013 12:57:34 AM Maximiliano Curia wrote: > > * Package name: encuentro > > Version : 1.0 > > Description : Access the content of the Encuentro channel, and > > others > We already have a fe

Re: Debian naming scheme

2013-06-17 Thread Matt Zagrabelny
On Mon, Jun 17, 2013 at 12:59 PM, Nikolas Kallis wrote: > Hello, > > > > I think Debian should stop releasing products as I.E 'Debian 7.0', and > instead release them simply as I.E 'Debian 7', where its Debian version > would be 7.0. > > It makes it hard for me writing documentation for applicatio

Debian naming scheme

2013-06-17 Thread Nikolas Kallis
Hello, I think Debian should stop releasing products as I.E 'Debian 7.0', and instead release them simply as I.E 'Debian 7', where its Debian version would be 7.0. It makes it hard for me writing documentation for applications that run on Debian when I have to write it supports I.E 'Debian

Re: Bug#712539: ITP: encuentro -- Access the content of the Encuentro channel, and others

2013-06-17 Thread Thomas Koch
On Monday, June 17, 2013 12:57:34 AM Maximiliano Curia wrote: > Package: wnpp > Severity: wishlist > Owner: Maximiliano Curia > > * Package name: encuentro > Version : 1.0 > Upstream Author : Facundo Batista > * URL : http://encuentro.taniquetil.com.ar/ > * License

Re: 7.0-> 7.1: any reasons for switching from {4,5,6}.0.x scheme?

2013-06-17 Thread Clint Adams
On Mon, Jun 17, 2013 at 06:51:30PM +0200, Thijs Kinkhorst wrote: > I'm really not sure what it buys us to change the scheme twice in the span > of four releases. For now I see churn in packages and confusion with our > users. It buys us a non-stupid versioning scheme for once. -- To UNSUBSCRIBE

Re: 7.0-> 7.1: any reasons for switching from {4,5,6}.0.x scheme?

2013-06-17 Thread Adam D. Barratt
On 2013-06-17 17:51, Thijs Kinkhorst wrote: Call it "undocumented" if you will, it is one of the prominent identifiers of a Debian release and doesn't explain to me why this change couldn't have been announced on d-d-a beforehand so people could adapt. The change was also omitted from the poin

VIDEO - Une journée avec la géoloc de 3ème génération

2013-06-17 Thread stephane . lefevre
Gérer et Géolocaliser vos Employés à partir de leur Smartphone iPhone ou Android Booster vos équipes en temps réel grâce à la géoloc de 3ème Génération Accéder à des informations fiables et géolocalisées pour mieux gérer vos équipes terrain   Solution de géolocalis

Re: 7.0-> 7.1: any reasons for switching from {4,5,6}.0.x scheme?

2013-06-17 Thread Thijs Kinkhorst
On Mon, June 17, 2013 18:03, Neil McGovern wrote: > On Mon, Jun 17, 2013 at 05:17:32PM +0200, Christoph Berg wrote: >> Re: Neil McGovern 2013-06-17 <20130617111457.gg22...@halon.org.uk> >> > Given that the middle '0' was redundant, and we now do X.0 for all >> > major releases, it was simply remove

Re: 7.0-> 7.1: any reasons for switching from {4,5,6}.0.x scheme?

2013-06-17 Thread Simon McVittie
On 17/06/13 17:33, Marc Haber wrote: > On Mon, 17 Jun 2013 12:14:57 +0100, Neil McGovern > wrote: >> Given that the middle '0' was redundant, and we now do X.0 for all >> major releases, it was simply removed. > > So sarge was a point release of woody? Neil did say "now". sarge was 8 years ago.

Re: 7.0-> 7.1: any reasons for switching from {4,5,6}.0.x scheme?

2013-06-17 Thread Marc Haber
On Mon, 17 Jun 2013 12:14:57 +0100, Neil McGovern wrote: >Given that the middle '0' was redundant, and we now do X.0 for all >major releases, it was simply removed. > >(additionally, there were never any 4.0.x releases...) So sarge was a point release of woody? Greetings Marc -- ---

Re: 7.0-> 7.1: any reasons for switching from {4,5,6}.0.x scheme?

2013-06-17 Thread Игорь Пашев
2013/6/17 Neil McGovern : >> #712586 >> > > So... why is postgres relying on an undocumented numbering schema, and > breaking when it doesn't match what it expects? Why it checks for version at all? Isn't package dependencies should be used? What about Debian derivatives? -- To UNSUBSCRIBE, e

Re: RFH: two base wheezy bugs

2013-06-17 Thread Jonathan Dowland
On Sun, Jun 16, 2013 at 11:22:50AM +0200, Daniel Pocock wrote: > Being able to systematically link bugs to hardware would be useful, then > other owners of the same hardware would (a) be able to check for outstanding > bugs before upgrading (b) try to reproduce and confirm bugs And if one uses mor

Re: 7.0-> 7.1: any reasons for switching from {4,5,6}.0.x scheme?

2013-06-17 Thread Neil McGovern
On Mon, Jun 17, 2013 at 05:17:32PM +0200, Christoph Berg wrote: > Re: Neil McGovern 2013-06-17 <20130617111457.gg22...@halon.org.uk> > > On Mon, Jun 17, 2013 at 04:32:47PM +0530, Praveen A wrote: > > > Many were curious on diaspora about the change[1]. There is no > > > rationale given in release n

Re: 7.0-> 7.1: any reasons for switching from {4,5,6}.0.x scheme?

2013-06-17 Thread Christoph Berg
Re: Neil McGovern 2013-06-17 <20130617111457.gg22...@halon.org.uk> > On Mon, Jun 17, 2013 at 04:32:47PM +0530, Praveen A wrote: > > Many were curious on diaspora about the change[1]. There is no > > rationale given in release news[2] about this change. Was there some > > major change in this releas

Re: Current and upcoming toolchain changes for jessie

2013-06-17 Thread Matthias Klose
Am 15.06.2013 03:22, schrieb Stephan Schreiber: > GCC-4.8 should become the default on ia64 soon; some other changes are > desirable: > - The transition of gcc-4.8/libgcc1 to libunwind8. > - A removal of the libunwind7 dependency of around 4600 packages on ia64 - > when > they are updated next ti

Re: 7.0-> 7.1: any reasons for switching from {4,5,6}.0.x scheme?

2013-06-17 Thread Neil McGovern
On Mon, Jun 17, 2013 at 04:32:47PM +0530, Praveen A wrote: > Many were curious on diaspora about the change[1]. There is no > rationale given in release news[2] about this change. Was there some > major change in this release or did we change the version scheme? Any > pointers would be welcome. >

Re: 7.0-> 7.1: any reasons for switching from {4,5,6}.0.x scheme?

2013-06-17 Thread Praveen A
2013/6/17 Neil McGovern : > Hi, > > Given that the middle '0' was redundant, and we now do X.0 for all > major releases, it was simply removed. > > (additionally, there were never any 4.0.x releases...) > > Neil Thanks Neil for the clarification! -- പ്രവീണ്‍ അരിമ്പ്രത്തൊടിയില്‍ You have to keep re

Bug#712571: ITP: opam -- package manager for OCaml

2013-06-17 Thread Mehdi
Package: wnpp Severity: wishlist Owner: Mehdi Dogguy * Package name: opam Version : 1.0.0 Upstream Author : OCamlPro * URL : http://opam.ocamlpro.com/ * License : GPL3 Programming Lang: OCaml Description : package manager for OCaml OPAM stands for OC

Re: RFH: two base wheezy bugs

2013-06-17 Thread Holger Levsen
reassign 708158 src:linux thanks Hi, On Sonntag, 16. Juni 2013, Andrei POPESCU wrote: > >#708158 > The submitter has posted a workaround ('options drm_kms_helper poll=N' > in a file under /etc/modprobe.d/). Reassign to src:linux? right, thanks, Andrei! On Montag, 17. Juni 2013, Neil McGovern w

Re: RFH: two base wheezy bugs

2013-06-17 Thread Neil McGovern
On Sun, Jun 16, 2013 at 09:49:41AM +0200, Holger Levsen wrote: > I'm at loss with what to do with #710047. (random freeze since wheezy) > For info, I'm also experiencing this. I'm having quite a bit of trouble tracking it down, though I *suspect* at the moment it may have something to do with the

7.0-> 7.1: any reasons for switching from {4,5,6}.0.x scheme?

2013-06-17 Thread Praveen A
Hi, Many were curious on diaspora about the change[1]. There is no rationale given in release news[2] about this change. Was there some major change in this release or did we change the version scheme? Any pointers would be welcome. Cheers Praveen [1] https://joindiaspora.com/posts/2732429 [2] h

Re: wrong configuration in daemon

2013-06-17 Thread Luca Filipozzi
The hypothetical one you mentioned: Let's say a daemon provides POP and IMAP On Sun, Jun 16, 2013 at 08:57:44PM -0400, Istimsak Abdulbasir wrote: > If the daemon is configured to restart the service, then it will fail to > execute. > > What daemon is servicing both POP and IMAP? > On Jun 16, 2013