Re: wrong configuration in daemon
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 2:40 PM, "Luca Filipozzi" wrote: > > > 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 provide > > both, > > > in a pop.conf and imap.conf. > > > > > > How should the daemon ideally fail in case one of the two configuration > > files > > > is incorrect but the other is fine? > > > > > > Should it log the situation and start the service that it's able to > > start? Or > > > should it just not start at all? > > > > If it's a single process that listens on two ports (POP & IMAP) then I > > would > > not start at all. > > > > A system administrator is likely to interpret that a running process > > indicates > > success start. What would trigger him to check that the process is > > listening > > on both ports. > > > > Also, in the start up script, how would you indicate that the daemon is > > 'half > > started'. > > > > Hope this helps, > > > > Luca > > > > -- > > Luca Filipozzi > > http://www.crowdrise.com/SupportDebian > > > > > > -- > > 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/20130616183946.ga4...@emyr.net > > > > -- Luca Filipozzi http://www.crowdrise.com/SupportDebian -- 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/20130617071058.ga14...@emyr.net
7.0-> 7.1: any reasons for switching from {4,5,6}.0.x scheme?
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] http://www.debian.org/News/2013/20130615 -- പ്രവീണ് അരിമ്പ്രത്തൊടിയില് You have to keep reminding your government that you don't get your rights from them; you give them permission to rule, only so long as they follow the rules: laws and constitution. -- 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/caoo+evphpywhb5pwufh9bq0friuqctdcdaqo+bqmcyd8whn...@mail.gmail.com
Re: RFH: two base wheezy bugs
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 Intel graphics drivers on Thinkpads. Leave that one with me, I'll try and triage and reassign as appropriate. Neil -- signature.asc Description: Digital signature
Re: RFH: two base wheezy bugs
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 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 Intel graphics drivers on Thinkpads.
>
> Leave that one with me, I'll try and triage and reassign as appropriate.
ok, thanks, Neil!
cheers,
Holger
signature.asc
Description: This is a digitally signed message part.
Bug#712571: ITP: opam -- package manager for OCaml
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 OCaml PAckage Manager. It aims to suit to a vast number of users and use cases, and has unique features: * Powerful handling of dependencies: versions constraints, optional dependencies, conflicts, etc. * Multiple repositories backends: HTTP, rsync, git * Ease to create packages and repositories * Ability to switch between different compiler versions . Typically, OPAM will probably make your life easier if you recognize yourself in at least one of these profiles: * You use multiple versions of the OCaml compiler, or you hack the compiler yourself and needs to frequently switch between compiler versions. * You use or develop software that needs a specific and/or modified version of the OCaml compiler to be installed. * You use or develop software that depends on a specific version of an OCaml library, or you just want to install a specific version of a package, not just the latest one. * You want to create your own packages yourself, put them on your own repository, with minimal effort. -- 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/20130617110719.3194.39088.reportbug@krypton
Re: 7.0-> 7.1: any reasons for switching from {4,5,6}.0.x scheme?
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 reminding your government that you don't get your rights from them; you give them permission to rule, only so long as they follow the rules: laws and constitution. -- 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/caoo+evphzc4maw+3cy15pvc1cgwwzwdnh1+o54fozj0kh5f...@mail.gmail.com
Re: 7.0-> 7.1: any reasons for switching from {4,5,6}.0.x scheme?
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. > 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 -- 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/20130617111457.gg22...@halon.org.uk
Re: Current and upcoming toolchain changes for jessie
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 time after the transition. The libc6.1 should (likely) > depend on libunwind8 after that in order to guarantee that libunwind8 is > installed. unless some ia64 porter steps up, it doesn't make sense to invest time into the ia64 port. So better drop ia64 now, and don't bother with libunwind on ia64. Matthias -- 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/51bf06cd.3070...@debian.org
Re: 7.0-> 7.1: any reasons for switching from {4,5,6}.0.x scheme?
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 release or did we change the version scheme? Any > > pointers would be welcome. > > > > Hi, > > Given that the middle '0' was redundant, and we now do X.0 for all > major releases, it was simply removed. #712586 Christoph -- c...@df7cb.de | http://www.df7cb.de/ -- 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/20130617151732.gd4...@msgid.df7cb.de
Re: 7.0-> 7.1: any reasons for switching from {4,5,6}.0.x scheme?
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 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. > > > > > > > Hi, > > > > Given that the middle '0' was redundant, and we now do X.0 for all > > major releases, it was simply removed. > > #712586 > So... why is postgres relying on an undocumented numbering schema, and breaking when it doesn't match what it expects? Neil -- signature.asc Description: Digital signature
Re: RFH: two base wheezy bugs
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 more than one computer, then it's easy as a submitter to forget on which machine you experienced the bug, later on down the line. I did try to address this once using a usertags scheme as part of work on 'debgtd' which I've since abandoned (or at least parked for a long time.) -- 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/20130617160805.GC28337@debian
Re: 7.0-> 7.1: any reasons for switching from {4,5,6}.0.x scheme?
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, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CALL-Q8zboJsyFzYck27ZUA-PT1OnVwHkiVeds5ZE=wtmqua...@mail.gmail.com
Re: 7.0-> 7.1: any reasons for switching from {4,5,6}.0.x scheme?
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 -- -- !! No courtesy copies, please !! - Marc Haber | " Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/ Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834 -- 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/e1uocmg-00073p...@drop.zugschlus.de
Re: 7.0-> 7.1: any reasons for switching from {4,5,6}.0.x scheme?
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. 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/51bf3ce6.7040...@debian.org
Re: 7.0-> 7.1: any reasons for switching from {4,5,6}.0.x scheme?
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 removed. >> #712586 > So... why is postgres relying on an undocumented numbering schema, and > breaking when it doesn't match what it expects? 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 point release announcement. Our users have learned to understand that 3.0.0r1 means a point release. This was changed with Lenny, so they've now learned that 5.0.1 is a point release. And with Wheezy they suddenly are confronted with 7.1, yet another change, and which means something vastly different from what 3.1 meant to them. To add to the confusion the Release Team refers to Wheezy as "7.0" and Jessie as "8.0". So 8.1 may or may not be "Jessie"? Who knows. 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. Cheers, Thijs -- 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/3b5cd8fa794b622acb4787040475390c.squir...@aphrodite.kinkhorst.nl
VIDEO - Une journée avec la géoloc de 3ème génération
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éolocalisation et de gestion de personnels itinérants. Cette solution vous permet de rester connecté en permanence avec vos équipes. Son logiciel de navigation et de localisation d’appareils connectés est accessible sur tous supports (smartphone, tablette, etc…) et s’installe à distance, en quelques minutes. GeoCoordinate est avant tout un formidable outil de gestion de la mobilité qui optimise chaque journée de travail et améliore significativement la productivité. GeoCoordinate s’adapte aux mouvements de votre personnel itinérant et vous permet un pilotage à distance efficace en toutes circonstances. Comment ça marche ? GeoCoordinate est une application professionnelle de géolocalisation et de gestion des ressources itinérantes qui permet en temps réel de voir, gérer et communiquer facilement avec vos équipes sur le terrain. Facile à installer et à déployer Aucun frais d’installation, pas d'immobilisation de vos véhicules, on installe l'application sur les Smartphone de vos personnels itinérants (Commerciaux, Techniciens, Équipier de chantier ...), et on met à disposition du chef ou du gestionnaire d'équipe un portail sécurisé. Contactez-nous au 01 83 64 23 57 Vous avez reçu ce courriel car vous êtes peut-être intéressé par la gestion géolocalisé du personnel Pour vous désinscrire de cette liste, cliquez sur le lien: http://www.smartplace.fr/mailing_unsubscribe/1814/1167165/eb96417bb65f33b396b5e9e7c9794286
Re: 7.0-> 7.1: any reasons for switching from {4,5,6}.0.x scheme?
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 point release announcement. That was an oversight on my part, for which I apologise. The change had been planned for a while and I was sure that it had been announced (outside of being mentioned on #debian-release several times); I was obviously mistaken. To add to the confusion the Release Team refers to Wheezy as "7.0" and Jessie as "8.0". So 8.1 may or may not be "Jessie"? Who knows. We're trying to stop doing so. Old habits die hard, as this thread demonstrates. (To the extent that we still tend to refer to a release as "r0", even though that scheme hasn't been used for years now.) Regards, Adam -- 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/5334308ec225a27a71cc4d53114bd...@mail.adsl.funky-badger.org
Re: 7.0-> 7.1: any reasons for switching from {4,5,6}.0.x scheme?
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, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130617170434.ga10...@scru.org
Re: Bug#712539: ITP: encuentro -- Access the content of the Encuentro channel, and others
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 : GPL-3 > Programming Lang: Python > Description : Access the content of the Encuentro channel, and others > > Encuentro is a small program that allows you to search, download and watch > videos from the Encuentro argentinian channel. Since the content of the > channel is completely in Spanish, so is this program. We already have a few video download programs in the archive. Maybe upstream could be convinced to contribute to the upstream of one of the following packages instead of writing its own program: cclive, clive, get-flash-videos, nomnom, youtube-dl, nicovideo-dl, get-iplayer, mediathekview Regards, Thomas Koch, http://www.koch.ro -- 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/4143820.dfPBnk4KjF@x121e
Debian naming scheme
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 (7.0, 7.1)'. Debian 7.0 and Debian 7.1 are the same operating system in essence anyhow. As is Windows 'XP BUILD 1XXX' and 'Windows XP BUILD 2XXX'. Regards, Nikolas Kallis -- 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/51bf4e8b.5030...@nikolaskallis.com
Re: Debian naming scheme
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 applications that run on > Debian when I have to write it supports I.E 'Debian (7.0, 7.1)'. Could your documentation state, 'Debian 7.X' ? -mz -- 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/CAOLfK3WHo+Wr=lzbumlcb1wpicxtuuzksft2spdg331cdwk...@mail.gmail.com
Re: Bug#712539: ITP: encuentro -- Access the content of the Encuentro channel, and others
¡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 few video download programs in the archive. Maybe upstream > could be convinced to contribute to the upstream of one of the following > packages instead of writing its own program: > cclive, clive, get-flash-videos, nomnom, youtube-dl, nicovideo-dl, > get-iplayer, mediathekview Most of them are are command line downloaders. encuentro is closer to miro, but instead of regular podcast the "conectate" network uses its own distribution protocol. By looking at the packages' descriptions mediathekview is specific to the German public internet television, encuentro would be a similar thing but for Argentinian public television. -- "Email is a wonderful thing for people whose role in life is to be on top of things. But not for me; my role is to be on the bottom of things. What I do takes long hours of studying and uninterruptible concentration." -- Donald Knuth Saludos /\/\ /\ >< `/ -- 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/1568698.EprvTtiykC@amadeus
Re: jessie release goal: verbose build logs
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 building in parallel". > > Debian Perl Group >libconvert-binary-c-perl Fixed and uploaded. >libhtml-template-pro-perl False positive. >libwx-scintilla-perl Fixed in git. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Bruce Springsteen: I'm Goin' Down signature.asc Description: Digital signature
Re: Bug#712539: ITP: encuentro -- Access the content of the Encuentro channel, and others
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 content of the Encuentro channel, and > > > others > > > We already have a few video download programs in the archive. Maybe upstream > > could be convinced to contribute to the upstream of one of the following > > packages instead of writing its own program: > > cclive, clive, get-flash-videos, nomnom, youtube-dl, nicovideo-dl, > > get-iplayer, mediathekview > > Most of them are are command line downloaders. encuentro is closer to miro, > but instead of regular podcast the "conectate" network uses its own > distribution protocol. > > By looking at the packages' descriptions mediathekview is specific to the > German public internet television, encuentro would be a similar thing but for > Argentinian public television. Are any of these service-specific downloader/viewer programs endorsed by the operators of the service that they work with? If not, is there not a risk of trademark infringement by including the service name in the program and package names? Ben. -- Ben Hutchings The generation of random numbers is too important to be left to chance. - Robert Coveyou signature.asc Description: This is a digitally signed message part
Re: wrong configuration in daemon
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 provide > > both, in a pop.conf and imap.conf. > > > > How should the daemon ideally fail in case one of the two configuration > > files is incorrect but the other is fine? > > > > Should it log the situation and start the service that it's able to start? > > Or should it just not start at all? > > If it's a single process that listens on two ports (POP & IMAP) then I would > not start at all. > > A system administrator is likely to interpret that a running process > indicates success start. What would trigger him to check that the process > is listening on both ports. Yes I thought so, but on the other hand, it might be better for the overall system to still run some services than none at all. Anyway I guess I'll see the code and send a patch upstream for that, and see what happens. > Also, in the start up script, how would you indicate that the daemon is > 'half started'. You couldn't, you would just hope that the administrator should go through the logs once he notices that one specific service is not working properly. -- Salvo Tomaselli http://web.student.chalmers.se/~saltom/ -- 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/2980479.IsSa8mBKkS@hal9000
Recommend documentation
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 states: > Recommends > This declares a strong, but not absolute, dependency. > The Recommends field should list packages that would be found together with this one in all but > unusual installations. Are they to be considered bugs? Which priority should they have? Personally I find the practice of recommending packages without a strong reason to be bad, what it usually does is to lead people who don't have lots of space (such as me on some other machines) to disable the automatic installation of recommended packages, then leading to problems in the cases when the recommend actually had a reason to be there. But what I want to know is if there is a way those should be handled. Bye -- Salvo Tomaselli http://web.student.chalmers.se/~saltom/ signature.asc Description: This is a digitally signed message part.
Re: RFH: two base wheezy bugs
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 do this. As most hardware-specific bugs are kernel bugs, whatever the kernel team finds most useful is what should be done.[1] 1: Kernel team: if this means adding user-values or some other additional feature to the BTS, please let me know. -- Don Armstrong http://www.donarmstrong.com Certainly the game is rigged. Don't let that stop you. If you don't bet, you can't win. -- Robert Heinlein _Time Enough For Love_ p240 -- 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/20130617220307.gk12...@teltox.donarmstrong.com
Bug#712630: ITP: pyqt5 -- Python bindings for Qt5
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 Description : Python bindings for Qt5 PyQt5 exposes the Qt5 API to Python and Python3. The following modules are supported: * QtCore * QtDBus * QtGui * QtNetwork * QtXmlPatterns * QtSvg * QtTest * QtWebKit * QtPrintSupport * QtWidgets * QtWebKitWidgets * QtHelp * QtTest * QtDesigner * QtOpenGL * QtSql * phonon This will have binaries for both python and python3 as both are supported. DPMT will be the maintainer and I'll be an uploader. Anyone who wants to work on putting this together, please let me know. -- 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/20130618041253.8520.81368.reportbug@Scott-Latitude-E6320
