Seex Worker and Idus In Bangladesh is Vulnerable of HIV/AIDS
<>
Re: Bug#529624: netbase: networking should not be stopped on reboot or halt
On Fri, May 22, 2009 at 08:12:59AM +0200, Gabor Gombas wrote: > The justification in the bug report is completely bogus. If the > clients did not shut down by the time the UPS master goes down then > you have bigger problems. Making the UPS daemon available for half a > second more does not make sense. My reading of the original bug report was that the UPS master daemon postpones the final steps of shutdown until slaves are off or battery condition becomes critical. -- Lionel -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Artha - Handy off-line English thesaurus with regex search feature released!
Dear friends, I am glad to announce release 0.9.1 of Artha ~ A handy off-line English thesaurus/dictionary based on WordNet with regular expressions based search feature added to it with this release. Artha houses distinct features like global hot key look-ups, regular expressions based search to locate a vaguely known word, passive desktop notifications, suggestions for misspelled words, etc. Once executed, it sits on the system tray monitoring for a pre-set hot key combination. When the user selects text from any window and presses this hot key, Artha pops-up with the word looked up. Should the user prefer passive notifications over the app. popping-up, Artha's 'Notify' option does this. Apart from showing definitions, it also shows Synonyms, Antonyms, Derivatives, Similar Terms, Attributes, Domain Terms, Pertainyms and 5 more. When a word is misspelled, it shows spelling suggestions too. Download (src and binaries): http://sourceforge.net/project/showfiles.php?group_id=250410 Code (release 0.9.1): svn co http://artha.svn.sourceforge.net/svnroot/artha/tags/0.9.1 Thanks! P.S.: This is my first open-source application. Thanks for all the support you guys gave me! Best Regards Sundaram
Bug#529871: Dependency mismatch for nautilus-filename-repairer and nautilus-image-converter
reopen 529871 clone 529871 -1 reassign -1 nautilus-image-converter severity -1 serious retitle -1 nautilus-image-converter: upload of experimental packages to unstable required reassign 529871 nautilus-filename-repairer severity 529871 serious retitle 529871 nautilus-filename-repairer upload of experimental packages to unstable required thanks + Michal Pomorski (Fri, 22 May 2009 00:55:07 +0200): > Package: general > Severity: important > Cant install the these two nautilus plugins. All other plugins installed > corerctly. > I tried several mirrors. > $ sudo aptitude install nautilus-filename-repairer nautilus-image-converter > Reading package lists... Done > Building dependency tree > Reading state information... Done > Reading extended state information > Initializing package states... Done > Reading task descriptions... Done > The following packages are BROKEN: > libnautilus-extension1 > The following NEW packages will be installed: > nautilus-filename-repairer nautilus-image-converter > 0 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded. > Need to get 36.7kB of archives. After unpacking 258kB will be used. > The following packages have unmet dependencies: > libnautilus-extension1: Breaks: nautilus-filename-repairer (< 0.0.5-2) but > 0.0.5-1 is to be installed. > Breaks: nautilus-image-converter (< 0.3) but > 0.2.1-2 is to be installed. -- - Are you sure we're good? - Always. -- Rory and Lorelai -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#529871: Dependency mismatch for nautilus-filename-repairer and nautilus-image-converter
Processing commands for cont...@bugs.debian.org: > reopen 529871 Bug#529871: Dependency mismatch for nautilus-filename-repairer and nautilus-image-converter Bug reopened, originator not changed. > clone 529871 -1 Bug#529871: Dependency mismatch for nautilus-filename-repairer and nautilus-image-converter Bug 529871 cloned as bug 529936. > reassign -1 nautilus-image-converter Bug#529936: Dependency mismatch for nautilus-filename-repairer and nautilus-image-converter Bug reassigned from package `general' to `nautilus-image-converter'. > severity -1 serious Bug#529936: Dependency mismatch for nautilus-filename-repairer and nautilus-image-converter Severity set to `serious' from `important' > retitle -1 nautilus-image-converter: upload of experimental packages to > unstable required Bug#529936: Dependency mismatch for nautilus-filename-repairer and nautilus-image-converter Changed Bug title to `nautilus-image-converter: upload of experimental packages to unstable required' from `Dependency mismatch for nautilus-filename-repairer and nautilus-image-converter'. > reassign 529871 nautilus-filename-repairer Bug#529871: Dependency mismatch for nautilus-filename-repairer and nautilus-image-converter Bug reassigned from package `general' to `nautilus-filename-repairer'. > severity 529871 serious Bug#529871: Dependency mismatch for nautilus-filename-repairer and nautilus-image-converter Severity set to `serious' from `important' > retitle 529871 nautilus-filename-repairer upload of experimental packages to > unstable required Bug#529871: Dependency mismatch for nautilus-filename-repairer and nautilus-image-converter Changed Bug title to `nautilus-filename-repairer upload of experimental packages to unstable required' from `Dependency mismatch for nautilus-filename-repairer and nautilus-image-converter'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
how package app selinux policy?
Hello, I am trying to find docs teaching how to package (The Right Debian Way) an application SELinux custom policy. Could you point some urls to study this packaging procedure (policy, dev helper scripts, etc)? At the [1], I found somewhat vague instructions (for a newbie) regarding custom policies debian packaging *proposal* from the ubuntu people. I am trying to package the selinux policy of php-java-bridge [2]. Regards. Andre Felipe Machado [0] http://wiki.debian.org/SELinux [1] https://wiki.ubuntu.com/HardySELinux [2] http://php-java-bridge.sourceforge.net -- http://www.techforce.com.br
Bug#529955: ITP: iguanair -- IguanaWorks Infrared Tranceiver support tools
Package: wnpp Severity: wishlist Owner: Stefanos Harhalakis * Package name: iguanair Version : 0.99 Upstream Author : IguanaWorks Inc. * URL : http://iguanaworks.net/ * License : GPLv2 and LGPLv2 Programming Lang: C and Python Description : IguanaWorks Infrared Tranceiver support tools This is a package for iguanaworks support tools and development files. It adds the required tools to manage IgianaWorks IR transceivers and the appropriate development files (library and headers) for adding iguaunaIR support to lirc (see bug #524403) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#530004: ITP: r-cran-g.data -- GNU R package for delayed-data packages
Package: wnpp Severity: wishlist Owner: Steffen Moeller * Package name: r-cran-g.data Version : 2.0 Upstream Author : David Brahm * URL : http://cran.r-project.org/web/packages/g.data * License : GPL Programming Lang: R Description : GNU R package for delayed-data g.data creates and maintains delayed-data packages (DDP's). Data stored in a DDP are available on demand, but do not take up memory until requested. You attach a DDP with g.data.attach(), then read from it and assign to it in a manner similar to S-Plus, except that you must run g.data.save() to actually commit to disk. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#530007: ITP: r-other-mott-happy -- GNU R package for fine-mapping complex diseases
Package: wnpp Severity: wishlist Owner: Steffen Moeller * Package name: r-other-mott-happy Version : 2.1 Upstream Author : Richard Mott * URL : http://www.well.ox.ac.uk/happy/happyR.shtml. * License : GPL-2+ Programming Lang: C,R Description : GNU R package for fine-mapping complex diseases The idea behind this package is that when multiple strains of animals that differ in their susceptibility to multiple diseases are bread over multiple generations, then one can analyse the contribution that a particular genetic locus has to each of those diseases. While in the past this approach has been performed for one disease at a time, this tool extends the statistics for allowing multiple crosses and thus save animal lifes. A larger stock of animals with more generations to keep them will further help producing larger numbers of observable cross-over events and thus help increasing the resolution of the mapping. . happy is an R interface into the HAPPY C package for fine-mapping Quantitative Trait Loci (QTL) in Heterogenous Stocks (HS). An HS is an advanced intercross between (usually eight) founder inbred strains of mice. HS are suitable for fine-mapping QTL. The happy package is an extension of the original C program happy; it uses the C code to compute the probability of descent from each of the founders, at each locus position, but the happy packager allows a much richer range of models to be fit to the data. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Should we remove OpenMotif?
On Thu, May 21, 2009 at 10:23:16PM +0200, Andreas Tille wrote: > I admit that keeping OpenMotif for one single package with a > low popcon seems not very effective and it is probably not really > the most up to date GUI library. But there are some users of > Arb (and their number is growing as I know from the Arb user > list). Unfortunately I'm unable to work on OpenMotif myself > to support my wish to keep OpenMotif. Also, note that there are heaps of legacy-applications which either predate the FLOSS movement and have a almost-free license or are just plain non-free. In any case they are not in Debian, but are using Motif (and possibly work better with Motif than with Lesstif). Michael -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Who uses @packages.d.o mail?
Hello Stephen, On Friday 22 May 2009 16:30:03 Stephen Gran wrote: [...] > If this is actually the case, I'd like to close the domain down to only > accept mail from other debian.org machines. If it's not, I'd like to work > with people who do use it to either make it possible to send their mail > from debian.org machines or from a short whitelist of machines elsewhere. @packages.d.o is known to be "the easiest way to get in touch with a maintainer," and is often used when CC'ing maintainers of multiple packages. Cheers, -- Raphael Geissert - Debian Maintainer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Who uses @packages.d.o mail?
Much appreciated. Thanks. On Fri, May 22, 2009 at 10:30:03PM +0100, Stephen Gran wrote: > Hello all, > > So I've looked through a few weeks of mail logs to packages.debian.org, > and it looks like it collects some useful mail from automated scripts > on various debian.org machines (primarily ries), and about 1000 spams a > day from elsewhere. I haven't done an exhaustive survey, but it seems > pretty clear so far that the domain does not get any significant amount > of legitimate mail from machines other than the debian.org hosts. > > If this is actually the case, I'd like to close the domain down to only > accept mail from other debian.org machines. If it's not, I'd like to work > with people who do use it to either make it possible to send their mail > from debian.org machines or from a short whitelist of machines elsewhere. > If this isn't possible, we'll of course continue to offer it as a public > service if it's needed. It's just that if it doesn't need to be a > public facing mail domain, we all get a little less spam in our inbox, > and the service becomes easier to administer. > > In the large scheme of things, of course, 1000 spams a day is pretty > minimal. The amount of processing power that goes into turning away > the other 6 mails/day and then resending the 1000 spams that do get > through, though, does approach significance, and I'd like to make it > simple to admin and more friendly to the final recipients. > > Cheers, > -- > - > | ,''`.Stephen Gran | > | : :' :sg...@debian.org | > | `. `'Debian user, admin, and developer | > |`- http://www.debian.org | > - -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all." -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Who uses @packages.d.o mail?
* Stephen Gran [2009-05-22 23:30:03 CEST]: > If this is actually the case, I'd like to close the domain down to only > accept mail from other debian.org machines. If it's not, I'd like to work > with people who do use it to either make it possible to send their mail > from debian.org machines or from a short whitelist of machines elsewhere. Not everyone has access to an debian.org machine, and @packages.debian.org is the address used in debconf po files for reporting messageID bugs to. A canonical easy way to reach the maintainer(s) of a package without digging around in various fields though is appreciated, and this is the one. So long, Rhonda -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Who uses @packages.d.o mail?
On Fri, 22 May 2009 22:30:03 +0100 Stephen Gran wrote: > Hello all, > > So I've looked through a few weeks of mail logs to > packages.debian.org, and it looks like it collects some useful mail > from automated scripts on various debian.org machines (primarily > ries), and about 1000 spams a day from elsewhere. I haven't done an > exhaustive survey, but it seems pretty clear so far that the domain > does not get any significant amount of legitimate mail from machines > other than the debian.org hosts. It does save creating a specific alioth mailing list for a group of maintainers and uploaders. It's started being used for svn-buildpack...@p.d.o It's only a convenience thing for discussions that aren't actually related to existing bug reports. > If this is actually the case, I'd like to close the domain down to > only accept mail from other debian.org machines. If it's not, I'd > like to work with people who do use it to either make it possible to > send their mail from debian.org machines or from a short whitelist of > machines elsewhere. If this isn't possible, we'll of course continue > to offer it as a public service if it's needed. It's just that if it > doesn't need to be a public facing mail domain, we all get a little > less spam in our inbox, and the service becomes easier to administer. Maybe a list of packages that do use it and an address to email for those who want to start using it at a later date? -- Neil Williams = http://www.data-freedom.org/ http://www.linux.codehelp.co.uk/ http://e-mail.is-not-s.ms/ pgpaCrIvNHkC0.pgp Description: PGP signature
Re: Who uses @packages.d.o mail?
On Fri, May 22, 2009 at 10:30:03PM +0100, Stephen Gran wrote: > If this is actually the case, I'd like to close the domain down to only > accept mail from other debian.org machines. If it's not, I'd like to work > with people who do use it to either make it possible to send their mail > from debian.org machines or from a short whitelist of machines elsewhere. The debian-l10n-english team, and perhaps others, use this domain to keep the maintainer in the loop during Smith English-language reviews and the subsequent translations. These mails almost certainly won't come from debian.org hosts (and not being a DD, mine couldn't do anyway). -- Jonathan Wiltshire PGP/GPG: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 signature.asc Description: Digital signature
Re: Who uses @packages.d.o mail?
> I haven't done an exhaustive survey, but it seems pretty clear so far > that the domain does not get any significant amount of legitimate mail > from machines other than the debian.org hosts. As I understand it, @packages.d.o is the standard way of contacting the maintainers of a package in an easy and efficient way. I use it all the time when eg. reassigning a bug (reassign mails are supposed to be CC'ed to the destination maintainers), rather than go up and look who's listed as maintainer and uploader and CC them all. Plus, fortunately, packages.d.o has been sending a copy to the PTS for some time now, so even interested people who are not listed as maintainer/uploader will be able to read them. Personally, I think we should keep it open. If it becomes unsustainable, we could require a whitelist header for mail sent from non debian.org machines, like the PTS does. But if we do that, we could ditch it altogether and just use the PTS (for me, one of the main advantages of packages.d.o is not having to include the whitelist header). Does somebody know if the PTS is mailing the maintainers already? Cheers, -- - Are you sure we're good? - Always. -- Rory and Lorelai -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Who uses @packages.d.o mail?
On Friday 22 May 2009, Stephen Gran wrote: > So I've looked through a few weeks of mail logs to packages.debian.org, I always use it to CC the maintainer(s) of a package I reassign a bug to, or if I want to CC a package maintainer on some discussion. For me it's the most natural address to use, much more natural than @p.qa.d.o. Cheers, FJP signature.asc Description: This is a digitally signed message part.
Re: Who uses @packages.d.o mail?
On Friday 22 May 2009, Neil Williams wrote: > Maybe a list of packages that do use it and an address to email for > those who want to start using it at a later date? That would defeat its purpose. It is not about which maintainers use it, but about who uses it to contact maintainers. Cheers, FJP signature.asc Description: This is a digitally signed message part.
Re: Who uses @packages.d.o mail?
On May 22, Raphael Geissert wrote: > @packages.d.o is known to be "the easiest way to get in touch with a > maintainer," and is often used when CC'ing maintainers of multiple packages. Then it needs to be fixed, soon, because it the last few weeks I started receiving a huge quantity of trivially rejectable pills spam from it. -- ciao, Marco signature.asc Description: Digital signature
Re: Who uses @packages.d.o mail?
This one time, at band camp, Jonathan Wiltshire said: > The debian-l10n-english team, and perhaps others, use this domain to > keep the maintainer in the loop during Smith English-language reviews > and the subsequent translations. This one time, at band camp, Adeodato Simó said: > I use it all the time when eg. reassigning a bug (reassign mails are > supposed to be CC'ed to the destination maintainers), rather than go up > and look who's listed as maintainer and uploader and CC them all. These are the sort of helpful answers that make it clear that people do at least sporadically use the service. I didn't see anything useful in the week of logs I reviewed, but activity like that described above is probably reasonably 'spiky' and I'm not surprised I missed it. It sounds like the service should probably stay open. I would have been happy to restrict something that is only a spam attractor, but if it's more than that, than I'm happy people find it a useful service. If the teams who do use it think it can still be useful and be restricted, that's a discussion I still think is worth having, but I don't think we need to rush towards it. Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Re: Who uses @packages.d.o mail?
On Fri, May 22, 2009 at 10:30:03PM +0100, Stephen Gran wrote: > So I've looked through a few weeks of mail logs to > packages.debian.org, (...) it seems pretty clear so far that the > domain does not get any significant amount of legitimate mail from > machines other than the debian.org hosts. I always give it to upstreams as a contact address for any issue around the package. In that way, even if I'm not the maintainer anymore, it will reach the right person. -- Lionel -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#530022: ITP: vmfs-tools -- Tools to access VMFS filesystems
Package: wnpp Severity: wishlist Owner: Mike Hommey * Package name: vmfs-tools Version : 0.1.0 soon to be released Upstream Author : Christophe Fillot Mike Hommey * URL : none yet * License : GPLv2+ Programming Lang: C Description : Tools to access VMFS filesystems VMFS is a clustered filesystem designed to store virtual machine disks for VMware ESX or ESXi Server hosts. This set of tools allows to access these filesystems from some other non ESX/ESXi host for e.g. maintenance tasks. Only read access is available at the moment, but write access is under works. Multiple extents are supported. The VMFS can be accessed with a command line tool or mounted through a userspace filesystem (FUSE-based). -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Who uses @packages.d.o mail?
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 On Fri, May 22, 2009 at 10:30:03PM +0100, Stephen Gran wrote: >So I've looked through a few weeks of mail logs to packages.debian.org, >and it looks like it collects some useful mail from automated scripts >on various debian.org machines (primarily ries), and about 1000 spams a >day from elsewhere. I haven't done an exhaustive survey, but it seems >pretty clear so far that the domain does not get any significant amount >of legitimate mail from machines other than the debian.org hosts. > >If this is actually the case, I'd like to close the domain down to only >accept mail from other debian.org machines. If it's not, I'd like to >work with people who do use it to either make it possible to send their >mail from debian.org machines or from a short whitelist of machines >elsewhere. If this isn't possible, we'll of course continue to offer it >as a public service if it's needed. It's just that if it doesn't need >to be a public facing mail domain, we all get a little less spam in our >inbox, and the service becomes easier to administer. > >In the large scheme of things, of course, 1000 spams a day is pretty >minimal. The amount of processing power that goes into turning away >the other 6 mails/day and then resending the 1000 spams that do get >through, though, does approach significance, and I'd like to make it >simple to admin and more friendly to the final recipients. Whenever users contact me privately regarding a package, I encourage them to instead target the package email address, so that fellow maintainers of team-maintained packages receive them as well. I am not against dropping/limiting the package email addresses, just saying that in addition to the concrete amount of mail it might also be relevant to take into account the expectation of such account existing, even if used less frequently. And the convenience of telling users to simply _email_ the package, instead of explaining them how to _find_ the email address from packaging metadata. Kind regards, - Jonas P.S. I am subscribed to d-project but not d-devel, so please cc me if replying to d-devel but not to d-project. - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREDAAYFAkoXMdYACgkQn7DbMsAkQLjR7ACeNUJjfnGjvGv3EeTPZT7ODCWN UXwAoJpOGv7d2+QDi9VZMyHrsQciWHnT =sjDR -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
