Bug#998646: RFP: rtpmidid -- RTP MIDI (AppleMIDI) daemon for Linux
Package: wnpp Severity: wishlist Source code at: https://github.com/davidmoreno/rtpmidid License is LGPL 2.1 (library) and GPL3+. Has preliminary deb packaging using `dpkb-buildpackage`. If there is something that I could do to help to package this program, please contact me (dmor...@coralbits.com), or add a bug report at github. Some description: rtpmidid allows you to share ALSA sequencer devices on the network using RTP MIDI, and import other network shared RTP MIDI devices. rtpmidid is an user daemon, and when a RTP MIDI device is announced using mDNS (also known as Zeroconf, Avahi, and multicast DNS) it exposes this ALSA sequencer port.
Bug#920937: 20190502-1?
Is this also happening with 20190502-1 from Sid?
Bug#773249: lists.debian.org: New list: debian-dug-washington-dc
On Mon, Dec 15, 2014 at 07:11:58PM -0500, Aaron M. Ucko wrote: > Package: lists.debian.org > Severity: wishlist > > Greetings! > > On behalf of the Washington, DC, US Debian developer community, I > would like to request an official debian-dug-* list to supplant our > current teams.debian.net list. (I'm sending a copy of this request to > the list to solicit seconds from other members.) Last I checked, we > had roughly a dozen full DDs, and several more who were going through > various stages of NM. I do not have access to the current subscriber > list, but perhaps the teams.d.n listmasters (Cc:ed as well) can share > it with you; in the worst case, we can just fully reboot the list and > ask everyone to resubscribe. > > I propose calling the new list debian-dug-washington-dc, but am open > to alternative suggestions. (That said, please note that the area has > three airports, so I'd rather not single out one.) > > We have not historically had a web archive, but I for one would be > open to establishing one; subscription has always been public anyway. > I can reconstruct only partial archives of the current list, but > perhaps other members (or the teams.d.n listmasters) have more > complete records. > > Here are the formal parameters, which correspond to what we have now > modulo the addition of a web archive: > > Name: debian-dug-washington-dc > Rationale: See above. > Description: Discussion list for Debian community in Greater Washington > Discussion list for the Debian Community in Washington, DC, US and > surrounding areas. > Category: Miscellaneous Debian > Subscription Policy: open > Post Policy: open > Web Archive: yes > > Thanks in advance for considering this request; please let me know if > you need anything else from me. Hello, Thanks for filling your interest to create a new mailing list. What's the current status of your community? It's been a few months since you requested the mailing list and I want to see if the interest is still current, etc. Also, did you confirm the availability of the archives? Thanks, damog, your listmaster for the day. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744119: help with and sponsoring onion upload
Hi, sorry to bother again, but it seems this RFP has become stalled. Is there anything I can do to resume the process to try to be incuded in debian? I would love to be included in Debian Jessie, and time is running out. Regards, David 2014-05-13 21:46 GMT+02:00 David Moreno Montero : > Hi Thomas and Laszlo, > > its been some time with no news about next step to help getting onion into > Debian, Is there something I can do to help? > > Regards, > David > > > 2014-05-02 1:11 GMT+02:00 David Moreno Montero : > >> Hi, >> >> I just pushed to the debian branch the change to try to use the system >> wide jquery. >> >> jQuery is used at runtime, but it also need to check jQuery file exists >> at compile time, so both dependencies are added to control file. >> >> Regards, >> >> >> 2014-05-01 20:01 GMT+02:00 Thomas Goirand : >> >> On 05/01/2014 06:13 PM, David Moreno Montero wrote: >>> > I will check how to do the jquery but it might be dificult as onion >>> > should be compilable on non debian as well. Is is ok if at compilation >>> > time it is decided to use the onion provided one, or the system one? If >>> > the system one is used then its is not compiled in (jquery is converted >>> > to a C file to be used as static data). >>> >>> Yes, that's fine, as long as in Debian, it does the right thing. >>> >>> > About systemd, onion will never force the user to use it. The support >>> is >>> > just to compile the functionallity to be able to cooperate better with >>> > systemd, if the developer decides so. It is always optional to use >>> > systemd, but the library must be prepared. Even if the developer of >>> > whatever uses onion decides to support systemd, it still can be used >>> > without it. http://0pointer.de/blog/projects/socket-activation.html >>> >>> Great. >>> >>> Thomas >>> >>> >> >> >> -- >> David Moreno Montero >> >> dmor...@coralbits.com >> +34 658 18 77 17 >> <http://www.coralbits.com/> >> http://www.coralbits.com >> >> >> > > > -- > David Moreno Montero > > dmor...@coralbits.com > +34 658 18 77 17 > <http://www.coralbits.com/> > http://www.coralbits.com > > > -- David Moreno Montero dmor...@coralbits.com +34 658 18 77 17 <http://www.coralbits.com/> http://www.coralbits.com
Bug#744119: help with and sponsoring onion upload
Hi Thomas and Laszlo, its been some time with no news about next step to help getting onion into Debian, Is there something I can do to help? Regards, David 2014-05-02 1:11 GMT+02:00 David Moreno Montero : > Hi, > > I just pushed to the debian branch the change to try to use the system > wide jquery. > > jQuery is used at runtime, but it also need to check jQuery file exists at > compile time, so both dependencies are added to control file. > > Regards, > > > 2014-05-01 20:01 GMT+02:00 Thomas Goirand : > > On 05/01/2014 06:13 PM, David Moreno Montero wrote: >> > I will check how to do the jquery but it might be dificult as onion >> > should be compilable on non debian as well. Is is ok if at compilation >> > time it is decided to use the onion provided one, or the system one? If >> > the system one is used then its is not compiled in (jquery is converted >> > to a C file to be used as static data). >> >> Yes, that's fine, as long as in Debian, it does the right thing. >> >> > About systemd, onion will never force the user to use it. The support is >> > just to compile the functionallity to be able to cooperate better with >> > systemd, if the developer decides so. It is always optional to use >> > systemd, but the library must be prepared. Even if the developer of >> > whatever uses onion decides to support systemd, it still can be used >> > without it. http://0pointer.de/blog/projects/socket-activation.html >> >> Great. >> >> Thomas >> >> > > > -- > David Moreno Montero > > dmor...@coralbits.com > +34 658 18 77 17 > <http://www.coralbits.com/> > http://www.coralbits.com > > > -- David Moreno Montero dmor...@coralbits.com +34 658 18 77 17 <http://www.coralbits.com/> http://www.coralbits.com
Bug#744119: help with and sponsoring onion upload
Hi, I just pushed to the debian branch the change to try to use the system wide jquery. jQuery is used at runtime, but it also need to check jQuery file exists at compile time, so both dependencies are added to control file. Regards, 2014-05-01 20:01 GMT+02:00 Thomas Goirand : > On 05/01/2014 06:13 PM, David Moreno Montero wrote: > > I will check how to do the jquery but it might be dificult as onion > > should be compilable on non debian as well. Is is ok if at compilation > > time it is decided to use the onion provided one, or the system one? If > > the system one is used then its is not compiled in (jquery is converted > > to a C file to be used as static data). > > Yes, that's fine, as long as in Debian, it does the right thing. > > > About systemd, onion will never force the user to use it. The support is > > just to compile the functionallity to be able to cooperate better with > > systemd, if the developer decides so. It is always optional to use > > systemd, but the library must be prepared. Even if the developer of > > whatever uses onion decides to support systemd, it still can be used > > without it. http://0pointer.de/blog/projects/socket-activation.html > > Great. > > Thomas > > -- David Moreno Montero dmor...@coralbits.com +34 658 18 77 17 <http://www.coralbits.com/> http://www.coralbits.com
Bug#744119: help with and sponsoring onion upload
I will check how to do the jquery but it might be dificult as onion should be compilable on non debian as well. Is is ok if at compilation time it is decided to use the onion provided one, or the system one? If the system one is used then its is not compiled in (jquery is converted to a C file to be used as static data). About systemd, onion will never force the user to use it. The support is just to compile the functionallity to be able to cooperate better with systemd, if the developer decides so. It is always optional to use systemd, but the library must be prepared. Even if the developer of whatever uses onion decides to support systemd, it still can be used without it. http://0pointer.de/blog/projects/socket-activation.html 2014-05-01 10:00 GMT+02:00 Thomas Goirand : > On 04/25/2014 10:43 PM, David Moreno Montero wrote: > > Just a quick note to inform that I just removed the sd-daemon.[ch] files > > and I depend on system provided ones (at libsystemd-daemon-dev). > > > > Also fixed jquery, I added the uncompressed one. > > Shipping non-minified javascript in your source is a requirement of > Debian for all source packages, so what you did is a good thing. > However, we also require that you use all libraries that are packaged in > the system. So you must use the jquery which is in Debian. And yes, you > must comply with both rules, which means even if you don't use the > jquery which you ship in your source code, it must *not* be minified. > Just wanted to make this clear. > > > Currently its not in control / depends, as I want to make my head if it > > should be enforced or not, but as systemd is on Debian's future, I guess > > it fits. > > You shouldn't force your users to use systemd if you can avoid it. We > have chosen systemd as default, but our users may not like it and prefer > another init system. Please respect the user choices if possible. > > Cheers, > > Thomas Goirand (zigo) > > -- David Moreno Montero dmor...@coralbits.com +34 658 18 77 17 <http://www.coralbits.com/> http://www.coralbits.com
Bug#744119: help with and sponsoring onion upload
Just a quick note to inform that I just removed the sd-daemon.[ch] files and I depend on system provided ones (at libsystemd-daemon-dev). Also fixed jquery, I added the uncompressed one. Currently its not in control / depends, as I want to make my head if it should be enforced or not, but as systemd is on Debian's future, I guess it fits. Regads, 2014-04-24 18:44 GMT+02:00 David Moreno Montero : > You are right about sd-daemon.[ch] file, I forgot about it. I think I can > remove it as its included in libsystemd-daemon-dev. I add the bug to the > onion issue tracker to do it asap. > > The proper license for src (except that files) is both GPLv2 and Apache2. > I just changed the README.rst. > > > 2014-04-24 18:19 GMT+02:00 László Böszörményi (GCS) : > > On Thu, Apr 24, 2014 at 5:40 PM, David Moreno Montero >> wrote: >> > If you agree, you may branch the onion source at github, and pull >> request me the changes. >> OK, will do. >> >> > About jquery, is it ok to include it non-minified? Also could be used >> straight from the jquery CDN, but somehow I feel users would feel more >> secure if its using only local resources. >> Better if not. 1) Not all users will have internet access for CDN. 2) >> jQuery may have performance / security issues anytime. Just depend on >> the needed version, as it's already packaged and taken care of. >> >> > About library versioning, I just added it, but I got a bug report that >> its not following proper libtool standards. I'm still fixing that, but the >> current solution should be on the debian branch. >> OK, waiting for that. >> >> > About manpages, I can try to prepare them ASAP, but some tips are >> welcome about how to create great manpages: which programs/commands? is >> groff the recomended way? >> For a start you may use 'apt-get install help2man; man help2man'. >> >> One more problem btw. LICENSE.txt states: "Contents of the src folder >> (the Library) is licensed under both GPLv2+ and Apache 2." while >> README.rst states: "The library is under the LGPL license, [...]" >> (which one?), then see a file, for example src/onion/block.c which has >> only Apache 2.0 license header. Which one is correct? Then you link >> together everything with src/onion/sd-daemon.[ch] which is licensed >> under MIT. I'm not a license expert and don't know what the result >> will be. Does linking MIT with (L)GPL code allowed? Where's / how MIT >> license vanished from the resulting library? >> >> Laszlo/GCS >> > > > > -- > David Moreno Montero > > dmor...@coralbits.com > +34 658 18 77 17 > +44 74 23 21 01 57 > <http://www.coralbits.com/> > http://www.coralbits.com > > > -- David Moreno Montero dmor...@coralbits.com +34 658 18 77 17 +44 74 23 21 01 57 <http://www.coralbits.com/> http://www.coralbits.com
Bug#744119: help with and sponsoring onion upload
You are right about sd-daemon.[ch] file, I forgot about it. I think I can remove it as its included in libsystemd-daemon-dev. I add the bug to the onion issue tracker to do it asap. The proper license for src (except that files) is both GPLv2 and Apache2. I just changed the README.rst. 2014-04-24 18:19 GMT+02:00 László Böszörményi (GCS) : > On Thu, Apr 24, 2014 at 5:40 PM, David Moreno Montero > wrote: > > If you agree, you may branch the onion source at github, and pull > request me the changes. > OK, will do. > > > About jquery, is it ok to include it non-minified? Also could be used > straight from the jquery CDN, but somehow I feel users would feel more > secure if its using only local resources. > Better if not. 1) Not all users will have internet access for CDN. 2) > jQuery may have performance / security issues anytime. Just depend on > the needed version, as it's already packaged and taken care of. > > > About library versioning, I just added it, but I got a bug report that > its not following proper libtool standards. I'm still fixing that, but the > current solution should be on the debian branch. > OK, waiting for that. > > > About manpages, I can try to prepare them ASAP, but some tips are > welcome about how to create great manpages: which programs/commands? is > groff the recomended way? > For a start you may use 'apt-get install help2man; man help2man'. > > One more problem btw. LICENSE.txt states: "Contents of the src folder > (the Library) is licensed under both GPLv2+ and Apache 2." while > README.rst states: "The library is under the LGPL license, [...]" > (which one?), then see a file, for example src/onion/block.c which has > only Apache 2.0 license header. Which one is correct? Then you link > together everything with src/onion/sd-daemon.[ch] which is licensed > under MIT. I'm not a license expert and don't know what the result > will be. Does linking MIT with (L)GPL code allowed? Where's / how MIT > license vanished from the resulting library? > > Laszlo/GCS > -- David Moreno Montero dmor...@coralbits.com +34 658 18 77 17 +44 74 23 21 01 57 <http://www.coralbits.com/> http://www.coralbits.com
Bug#744119: help with and sponsoring onion upload
Great! you are more than welcome! I'm strugling with some parts of it. If you agree, you may branch the onion source at github, and pull request me the changes. About jquery, is it ok to include it non-minified? Also could be used straight from the jquery CDN, but somehow I feel users would feel more secure if its using only local resources. About library versioning, I just added it, but I got a bug report that its not following proper libtool standards. I'm still fixing that, but the current solution should be on the debian branch. About manpages, I can try to prepare them ASAP, but some tips are welcome about how to create great manpages: which programs/commands? is groff the recomended way? About license, add myself to debian/*, if you use part of whatever is there right now. Thank you very much! 2014-04-24 16:13 GMT+02:00 László Böszörményi (GCS) : > Hi David, Thomas, > > Wanted to package onion myself and while David may or may not would > like me as a co-maintainer, I'm here to help him get onion properly > packaged and uploaded. > I don't have problems with upstream have debian/ in its tree. Source > format 3.0 (quilt) is here to replace with the official Debian one. > > But there are important upstream bugs. > First, the source needs to be repackaged to be DFSG, as > examples/oterm/static/jquery-1.4.3.min.js is minified and needs to be > removed. > Then libraries are not versioned. Only *.so's are produced. :( Please > read point 3.1.1 [1] to understand why this is important. > > Other problems are there. For example no manpages for the binaries. > The current standards-version is 3.9.5 . Also, debian/copyright is > just a template. Attached a mostly finished one, which still doesn't > cover the examples, tests or tools (those are AGPLv3+) nor > src/onion/sd-daemon.[ch] (MIT). > > Regards, > Laszlo/GCS > [1] http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html > -- David Moreno Montero dmor...@coralbits.com +34 658 18 77 17 +44 74 23 21 01 57 <http://www.coralbits.com/> http://www.coralbits.com
Bug#744119: RFP: libonion -- lightweight and easy to use HTTP server library
Hi, I just commited the changes to the debian branch ( https://github.com/davidmoreno/onion/tree/debian). About not using the debian directory, just now is to ease the compilation by third parties. I would really love to keep the debian packaging there at least by the moment, to help on current debian installations to easy create the packages. If you see any other necesary change, please contact me. Regards, David. 2014-04-12 3:50 GMT+02:00 Thomas Goirand : > On 04/11/2014 03:34 PM, Andrei POPESCU wrote: > > Control: reassign -1 wnpp > > Control: retitle -1 RFP: libonion -- lightweight and easy to use HTTP > server library > > > > On Jo, 10 apr 14, 14:07:07, David Moreno Montero wrote: > >> Package: libonion, libonion-dev, libonion-tools, libonion-examples > >> Severity: wishlist > >> > >> I'm the developer of libonion, a C HTTP server library with bindings for > >> C++. I would love to see it packaged for Debian. It has a working debian > >> directory that packages all needed files. > >> > >> https://github.com/davidmoreno/onion > >> > >> License is both GPLv2+ and Apache2 for the main library. AGPLv3 for the > >> examples and tools. > >> > >> --David Moreno Montero > > Hi David, > > It is a bad practice to ship a debian folder upstream. I would advice > you to at least rename it as something like "debian-upstream", so that > it doesn't conflict with the debian folder that will be worked on by the > maintainer of the package. > > Now, a few remarks about your packaging. > > 1/ If you want to have your package in Debian, please clean the > debian/changelog, and write a single entry: > > * Intial release (Closes: #XX) > > with XX the number of the ITP (Intention To Package) bug number (you > can open such a bug using "reportbug -b wnpp"). > > 2/ There's no need to use debian/compat level 7 anymore. Increase this > to 9, as well as debhelper build-depends. > > 3/ Standards-Version: is now 3.9.5, fix that. > > 4/ Please rewrite your debian/copyright file in DEP5 format: > http://dep.debian.net/deps/dep5/ > > 5/ The debian/libonion-dev.dirs is useless, remove it. Same for > debian/libonion.dirs > > 6/ The files usr/bin/interactive, usr/bin/fileserver, usr/bin/crl have a > way too much generic names, and may conflicts with other packages. > Please rename them (and possibly other files too). > > 7/ Switch to 3.0 (quilt) format for your debian source. To do so: > > mkdir debian/source > echo "3.0 (quilt)" >debian/source/format > > 8/ Remove the comments in debian/rules, these are useless. > > 9/ Remove debian/README, there's nothing interesting there. Same with > README.source. There's a Homepage: field for this. > > 10/ Vcs-Git: and Vcs-Browser: are fields for the *packaging* urls, not > for your upstream source code. > > 11/ libonion-dev should depend on libonion (= ${binary:Version} > > 12/ libonion should be rename with as the soname. For example: libonion2 > > 13/ libonion should use ${shlibs:Depends}, therefore there's no reason > that you even manually write the dependencies. > > If you correct the above, I may sponsor your package upload in Debian. > > Cheers, > > Thomas Goirand (zigo) > > -- David Moreno Montero dmor...@coralbits.com +34 658 18 77 17 +44 74 23 21 01 57 <http://www.coralbits.com/> http://www.coralbits.com
Bug#744119: RFP: libonion - HTTP server library in C designed to be lightweight and easy to use
Package: libonion, libonion-dev, libonion-tools, libonion-examples Severity: wishlist I'm the developer of libonion, a C HTTP server library with bindings for C++. I would love to see it packaged for Debian. It has a working debian directory that packages all needed files. https://github.com/davidmoreno/onion License is both GPLv2+ and Apache2 for the main library. AGPLv3 for the examples and tools. --David Moreno Montero dmor...@coralbits.com +34 658 18 77 17 +44 74 23 21 01 57 <http://www.coralbits.com/> http://www.coralbits.com
Bug#681375: Current interest?
Hello guys, Thanks for filing interest on creating an special mailing list for the Debian community in Colombia. Since it has been more than a year now from the last support message on the request, I'd like to ask and know what the current status of the previous list is, and if the interest is still current. Cheers, dm -- http://damog.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668953: Public interest
Hello, Thanks for filing a request to create a new mailing list. I'm unsure whether we should host this mailing list within Debian due to being spefically for packaging and co-maintainers communication. A lot of other package teams consolidate these efforts through alioth projects which makes it even easier to collaborate together. Have you guys tried that? Feel free to disagree and prove a point for the need of this mailing list, though. However, since it's been almost two years of this request, chances are the real need for the mailing list might be unfounded. Let me know what you think, dm. -- http://damog.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#741538: debian-astro mailing list created
close 741538 stop Hello, Thanks for your interest on creating a new mailing list within Debian. Thanks also for your support on the astronomy field and effort to specialize it for the project. The mailing list has been created: https://lists.debian.org/debian-astro/ https://lists.debian.org/debian-astro/2014/03/msg1.html If there's anything else I can help you guys with, please do let me know. -- http://damog.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#734203: Public archives
Hello, Thanks for filling a request to create a new mailing list. Do you have public archives for your current mailing list showing present activity in this project? Thanks, dm, wearing his listmaster hat. -- http://damog.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#741538: Request for a debian-astro mailing list
On Thu, Mar 13, 2014 at 04:38:22PM +0100, Ole Streicher wrote: > Dear list maintainers, > > Please create the mailing list debian-as...@lists.debian.org: Hello, Thanks for filling this request. As stated here: https://www.debian.org/MailingLists/HOWTO_start_list ...please have other people interested on this mailing list post to the bug to record public interest. -- http://damog.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#730262: Thanks for your interest
Hello, Thanks for your interest on reactivating this list. I must ask what's really the rationale behind activating back the list? Will activating them list mean the community will kickstart again? Because I believe the other way around would be more natural. I would like to see more formal activity somewhere that would probe that this efforts deserve a new mailing list. Let me know what you think, -- http://damog.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#733349: ITP: kbdlight -- simple application that changes MacBooks' keyboard backlight level
Guus Sliepen wrote: > First of all, this application is so simple, it can easily be written as a > architecture independent shell script. Furthermore, the package name is very > generic, it would be nice if it worked for other brands of laptops as well. My > Samsung for example has the same interface to change the backlight, except the > sysfs file is called /sys/class/leds/samsung::kbd_backlight instead of > smc::kbd_backlight. And I think the FTP masters will ask you if it wouldn't be > possible to have the functionality merged with an existing Debian package that > has to do with backlight or ACPI. This is true. And actually someone else did it also as a shell script, with a similar name as well: https://github.com/mkouhei/scripts/blob/master/kbdlight.sh However, the point is that somebody put effort on doing this is a small C application and somebody thought it was also useful. I don't see why it should not be included in Debian, maybe it'll be useful for even more people. signature.asc Description: Digital signature
Bug#733349: ITP: kbdlight -- simple application that changes MacBooks' keyboard backlight level
Package: wnpp Severity: wishlist Owner: David Moreno * Package name: kbdlight Version : 1.2 Upstream Author : Hugo Osvaldo Barrera * URL : https://github.com/hobarrera/kbdlight * License : ISC Programming Lang: C Description : simple application that changes MacBooks' keyboard backlight level kbdlight is very simple application that changes MacBooks' keyboard backlight level. . While usable standalone, the main goal is for it to be used by other applications, including things like sxhkd or xbindkeys. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#673973: Updated
Author has just released version 5.00 of this. I continue to second this RFP :) https://metacpan.org/release/WWW-Tumblr -- http://damog.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#673973: RFP: libwww-tumblr-perl -- Perl interface for the Tumblr API
I second this RFP :) On Tue, May 22, 2012 at 6:00 AM, Mathieu Roy wrote: > Package: wnpp > Severity: wishlist > > * Package name: libwww-tumblr-perl > Version : 4.1 > Upstream Author : David Moreno > * URL : http://search.cpan.org/dist/WWW-Tumblr/ > * License : Same as Perl (GPLv1 or later or Artistic License) > Programming Lang: Perl > Description : Perl interface for the Tumblr API > > Provides an interface to Tumblr API (post, delete, edit). > > > -- http://damog.net
Bug#568037: Your Email ID Was Awarded 1,000,000.00GBP In The Tobacco Online Promo.Send Your:
NamesAddressTel.
Bug#577045: libmodern-perl-perl vs libmodern-perl
On Sun, Apr 18, 2010 at 2:49 PM, gregor herrmann wrote: > On Sun, 18 Apr 2010 11:18:00 -0700, Ivan Kohler wrote: > > > Originally I had uploaded libmodern-perl-perl by accident and was > > surprised it made it through NEW. I was planning on asking for removal > > (and for libmodern-perl to be renamed to or Provide: > > libmodern-perl-perl). > > > > However it seems that David Moreno may be MIA-ish? > > (The most recent activity I can find is an upload of libxml-treepp-perl > > on 2009-08-26?) > > > > So I am considering just running with libmodern-perl-perl (via pkg-perl > > svn) and asking for libmodern-perl's removal. > > I agree with the proposal, still damog's thoughts would be > interesting; adding a CC to the email address found on his blog. > Do whatever you feel is right :) -- http://twitter.com/damog http://stereonaut.net/
Bug#523937: News?
Any news wrt this ITP? David Moreno http://stereonaut.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#488753: Uploaded passenger
On Jul 27, 2009, at 7:33 PM, Micah Anderson wrote: David Moreno and I spent some time at Debconf preparing a new version of Passenger to address the various issues that ftp master had, and upgraded it to a new version. We uploaded it last night, and it is now in the NEW queue, we'll have to close this ITP after (or if) it is accepted, as well as move it to the proper area in the debian-ruby-extras team area. Yes, and after a couple of weeks or so, it's still on NEW, along with packages waiting on the queue for up to a month. For the impatient: http://log.damog.net/2009/08/phusion-passenger%E2%84%A2-on-debian/ Beer, anyone? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#488753: Status?
Hello, In repeated ocassions people have been asking what's going on with Passenger on Debian regarding this bug. Some of us are a bit impatient and frustrated that this cannot be finished by the packagers who take care of this at the beginning. Given the situation, I was able to include the changes Mr. Micah already sent to this bug and clarified most of the issues on debian/copyright, so there isn't really any other issues stopping Passenger to go into Debian and the NEW queue. So, if the maintainers are not doing anything to finish this job in the weekend, I will incorporate Micah's and my own changes into WIP on pkg-ruby-extras and take care of the package and upload it on June 1st. Thanks, David Moreno http://twitter.com/damog -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#524840: ITP
retitle 524840 ITP: libkiokudb-perl -- Object Graph storage engine for Perl owner 524840 David Moreno -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#512780: Follow up
On 13:54 Sat 21 Mar 2009, Adeodato Simó wrote: > > As a follow-up, Adeodato and I spoke briefly last week about the proper > > name that this list should take. From a listmaster point of view (and > > also Joey's), I believe the list could be best suitable to be named > > either debian-wanna-build, debian-wannabuild, debian-wb-admin or a > > similar variation. This is mainly to avoid confusion on a little known > > name such as "wbadm" for not-involved developers: just to make a bit > > less cryptic. > > I don’t want to be increasingly difficult by refusing other names than > the one listmaster founds problematic. I’m sorry about that. > > David, how do you feel about “debian-wb-team”? This is similar to your > proposed debian-wb-admin, but matches the current public address of the > team (wb-t...@buildd.debian.org). > > Thoughts? Hello Adeodato, Yes, it wasn't also my intention to add stoppers on any team doing work in favor of Debian, it's just naming policy as listmasters we have/want to follow so it doesn't involve any problems later. I feel "debian-wb-team" is a great name, and if no one thinks otherwise, I'll be creating the list later today. Yours, D. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514023: Archive not taken over
On 21:56 Wed 18 Mar 2009, Andreas Tille wrote: > thanks to David Moreno the debian-custom list was renamed to debian-blends > list to be able to profit from the old archives. Unfortunately the archive > was not taken over. So the subscribers are now recieving mail from > debian-blends list (and have to adapt their procmail rules) but the > archive was not moved and is continuosely available at > >http://lists.debian.org/debian-custom/ > > while the archive at > >http://lists.debian.org/debian-blends/ > > does show only March 09. Is there any problem with renaming the archive? > Please keep us informed if there is any problem with the renaming process. > > Kind regards and BTW, thanks for your patience with this issue which > lays work on you which was not really intended Hello Andreas, That's correct, the mailing list has been renamed and /most/ of its services have been migrated. As you say, yes, the web archives still need to be moved. I hadn't spoken about this since the main reason for not finishing it was lacking time on my side. Hopefully, during this weekend, I'll find some time and finish the archive migration. This is also why I hadn't closed the request bug or sent any notification. Kind regards, D. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514039: backscatter on the debian-edu list, again
On 12:42 Sun 01 Mar 2009, Holger Levsen wrote: > On Sonntag, 1. März 2009, Don Armstrong wrote: > > I've already droped in rules to deal with this; the previous ones > > hadn't taken effect due to a warning that I didn't catch. > > Thanks. > > > It doesn't really matter to me what you folks decide, but since you > > decided as a group not to do moderation, some how claiming that > > listmaster@ is the nefarious party is rather disingenuous. > > I didnt claim that. I claimed that filtering backscatter will not work in the > long run and didnt work in the last week. The latter is definitly true, for > the former I am very happy to be proven wrong. > > (I just doubt it will be the case in the long run: there will be always new > backscatter (new languages, new wordings) which is something which can > hardled without redesigning email and people, thats why I think we will go to > moderation some day, just because keeping subscribed people is more > importannt than a delay in posting appearance (and the potential of loss due > to bad moderation) of unsubscribed posters.) > > > It certainly doesn't motivate this listmaster to have anything more to > > deal with this issue. Best of luck. > > I'm sorry that my frustration about a problem you're fighting well has > demotivated you. You're work is very much appreciated. > > (Sigh, _I_ can deal with such backscatter, mental ignore works just fine _for > me_ with the tiny amount your filters let through. The lists just doesnt seem > to want to / aint able.) > > To bring this back to something more constructive again, as I want to help > improve the filters, I'd still like to know the answer to this: > > Do you also requiere three backscatter reports like you do for spam submitted > over the webinterface? So, what is the outcome of this bug report? As far as it can be seen from the bug log, there's no more need for list moderation, is that correct? If so, this ticket could closed. Just checking in order to have listmasters' TODO list as short as possible :-) D. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514023: lists.debian.org: Request for debian-blends mailing list
On 09:24 Fri 13 Mar 2009, Andreas Tille wrote: > No. The main reason for the renaming is that the former name was > missleading and people used the custom list for discussion about things > which was not the original target of the former CDD now Blends effort. > The list was used for discussion about how to customise your private > Debian customisation and things like that. This was perfectly reasonable > and interesting discussion but leaded to endless missunderstandings > especially for newcomers. > > So a simple renaming of the list would leave people into this topic > alone and they would not find a reasonable place to discuss these > issues. The perfect solution would be to manually investigate all > the past mails and tag those who are Blends related and move only > these to the new list. I would even spend some time on this issue > if this is technically possible and would not be to complicated. > But IMHO just renaming the list is not a good solution. > >> I see no difference on renaming the list and re-start using it as Pure >> Blends. It makes not too much sense to just drop other list which >> archive could be useful for other people too and pretend that the CDD >> list was never there. > > Well, we definitely have a loss of information on the new Blends list > but I try to solve this by some links to important threads (if the > chance to take over some mails from the past just is to expensive. I understand it. So, this is what I think. Given that the debian-custom mailing list was created for the same purpose and reason why Blends was born, which is providing a discussion forum for Debian-based distribution, it's a bit a difficult right now to take into account those users who started taking the list as a forum for Debian pimping. Given that this is only a matter of a general more global naming confusion, I strongly support the outcome of renaming the list now and redirecting and pointing users who still think it's a forum for Debian customization to the appropiate mailing list, such as debian-user (or its localized variations). If we created a different mailing list for Blends, this would lead us to have similar discussions (both -user and -custom) on two different places whereas they certainly belong to a single one (-user). If by any chance, there's an specific need for a customization talk mailing list, such a list would have to follow the usual list-creation procedure as any other new mailing list and the listmasters would consider it, but as of now, it really makes not much sense to me. D. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#515864: please clarify -release is a special kind of list
On 14:03 Tue 03 Mar 2009, Adeodato Simó wrote: > To the listmasters: I'll try to provide an updated description for this > list at some point in the future, to ease your work. Hey Adeodato, Whenever you feel like writing an updated description, please send it over so we can include it. I appreciate your concern, work and time :-) Cheers, D. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#512780: Follow up
Hello, As a follow-up, Adeodato and I spoke briefly last week about the proper name that this list should take. From a listmaster point of view (and also Joey's), I believe the list could be best suitable to be named either debian-wanna-build, debian-wannabuild, debian-wb-admin or a similar variation. This is mainly to avoid confusion on a little known name such as "wbadm" for not-involved developers: just to make a bit less cryptic. In order to speed the creation up, other listmasters' opinion is welcome. Cheers, David. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514023: lists.debian.org: Request for debian-blends mailing list
On 23:00 Wed 04 Feb 2009, Andreas Tille wrote: > Rationale: The rationale behind this is that > the debian-custom list is overloaded with to in principle > different topics: > > 1. Issues concerning Custom Debian Distributions which > are now renamed to Debian Pure Blends. This fact > itself might be a valid reason to register a new > list - but the old list might have worked so far if > the list description would have been fixed. > 2. Issues regarding SimpleCDD and ways how to customize > your very own customized Debian. This discussion is > orthogonal to the sense of Debian Pure Blends and is > finally the main reason for this whole stupid renaming > business: Bluring the topic because of missunderstandings > of the concept. It's my understanding that Debian Pure Blends is the rename of the CDD project. Is that correct? If it's basically the same thing, I believe renaming the list would suffice, unless there's an actual reason why to leave -custom orphaned and unattended. > While the discussion of issues of type 2 is perfectly valid > we just would leave the old list which was intended to serve > as discussion forum for CDDs / Blends to those who like to > do other things and ask for a new mailing list debian-blends. I see no difference on renaming the list and re-start using it as Pure Blends. It makes not too much sense to just drop other list which archive could be useful for other people too and pretend that the CDD list was never there. Please consider my opinions above. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#335459: ITP: flock -- mozilla-firefox based social web browser
On Feb 20, 2009, at 8:54 PM, Savvas Radevic wrote: Any progress? There's an Ubuntu request as well: https://bugs.edge.launchpad.net/debian/+bug/332312 None. Feel free to take over if interested. David Moreno http://damog.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#512780: More input desirable
On Feb 17, 2009, at 5:17 AM, Adeodato Simó wrote: Gentle ping? --- Adeodato Simó [Sat, 07 Feb 2009 16:52:45 +0100]: * David Moreno [Sat, 31 Jan 2009 13:46:19 -0500]: Hello. Hello David. Sorry for the late reply, but I was seemingly not CC'ed on your mail, and I just thought today I'd take a look at the bug just in case somebody had said something there. I'm sorry for not copying you back on the previous mail. After filing the request, it would be very much appreciated if several other people interested in the new list would send a mail to the bug, in order to record their interest. I asked on the IRC a couple times if we needed the "people send mail" dance for this list. Cord just asked me how many people were there in the wbadm group (6), and if there was consensus about this among us (there is such consensus). To get this request move forward, what kind of interest would you like recorded in the bug? From people in the wbadm group, to record our own wish and consensus about using a public role address, or from any other developers, to express if they think having a public role address for wbadm would be a good thing? Yes, that's our usual procedure for creating new lists, just collect or record other people's interest on the bug and see why it'd be suitable for lists.debian.org, etc. I'm not involved on the wanna-build admins, but as a listmaster, I think it would make more sense to set the address for the mailing list as debian-wanna-build. This list is to be a role address, so I'd really appreciate if it could be called debian-wbadm, to clearly indicate association with the "wbadm" Unix group. "wanna-build" is the name of a piece of software, and that would not reflect the main intention of the list. After discussing it with a couple of other members of the listmaster team, we believe that the list would be best suitable if hosted under teams.debian.net, which is a service maintained and provided exactly for this kind of activities. We are unable to find deeper reasons why this list would have to be under lists.debian.org, according to the rationale that has been provided on the request. So, please consider using teams.d.n. David. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#515231: RFP: libmodern-perl-perl
Package: wnpp Severity: wishlist URL: http://search.cpan.org/dist/Modern-Perl/ Modern::Perl - enable all of the features of Modern Perl with one command -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#513772: RFP: libvitacilina-perl -- feed aggregation library
Package: wnpp Severity: wishlist Upstream Author: David Moreno URL: http://search.cpan.org/~damog/Vitacilina-0.1/lib/Vitacilina.pm License: Perl's Programming Lang: Perl Description: feed aggregation library A simple feeds engine exporter that uses YAML to get list of feeds and TT as templating system. Some people would call it an aggregator. It was intended to be a reliable Planet alternative, then some development ideas evolved into rFeed. Vitacilina runs on production services on a few of systems. David Moreno http://damog.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#513771: RFP: openx -- open source advertising server
Package: wnpp Severity: wishlist Upstream Author: http://www.openx.org/en/about/management-team URL: http://www.openx.org/ License: GPL Programming Lang: PHP Description: open source advertising server OpenX is an open-source advertising server (written in PHP and using a MySQL or PostgreSQL database) that is licensed under the GNU General Public License. It features an integrated banner management interface and tracking system for gathering statistics. The product enables web site administrators to rotate banners from both in-house advertisement campaigns as well as from paid or third-party sources, such as Google's AdSense. OpenX is the latest reincarnation of the product's brand, following the name OpenAds, itself following the name phpAdsNew. David Moreno http://damog.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#512780: More input desirable
Hello. After filing the request, it would be very much appreciated if several other people interested in the new list would send a mail to the bug, in order to record their interest. I'm not involved on the wanna-build admins, but as a listmaster, I think it would make more sense to set the address for the mailing list as debian-wanna-build. Cheers, David Moreno http://damog.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#512172: RFP: dbslayer -- lightweight database abstraction layer suitable for high-load websites
Package: wnpp Severity: wishlist * Package name: dbslayer Version : beta-12 Upstream Author : Derek Gottfrid * URL : http://code.nytimes.com/projects/dbslayer * License : MIT Programming Lang: C/others Description : lightweight database abstraction layer suitable for high-load websites DBSlayer is a lightweight database abstraction layer suitable for high-load websites where you need the scalable advantages of connection pooling. Written in C for speed, DBSlayer talks to clients via JSON over HTTP, meaning it's simple to monitor and can swiftly interoperate with any web framework you choose. The DBSlayer originated as an internal tool at the New York Times. The typical LAMP strategy for scaling up data-driven applications is to replicate slave databases to every web server, but this approach can hit scaling limitations for high-volume websites, where processes can overwhelm their given backend DB's connection limits. Quite frankly, we wanted to scale the front-end webservers and backend database servers separately without having to coordinate them. We also needed a way to flexibly reconfigure where our backend databases were located and which applications used them without resorting to tricks of DNS or other such "load-balancing" hacks. Plus, it just seemed really cool to have a JSON-speaking DB layer that all our scriptable content could talk to. Thus, the DBSlayer was born. -- System Information: Architecture: i386 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#512171: RFP: libapache2-embedflv-perl -- embed FLV videos into a templated web interface using Flowplayer
Package: wnpp Severity: wishlist * Package name: libapache2-embedflv-perl Version : 0.2 Upstream Author : David Moreno * URL : http://axiombox.com/apache2-embedflv * License : Perl's Programming Lang: Perl Description : embed FLV videos into a templated web interface using Flowplayer Apache2::EmbedFLV enables Apache to show FLV videos using Flowplayer. This will ease any deployment of FLV video galleries you'd need to do since you could just put the FLVs on an Apache accessible location, and they will be presented on a proper way to your final user. -- System Information: Architecture: i386 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#510660: http://www.debian.org/security/2009 is broken
Package: www.debian.org Severity: important Security advisories linked from the front page www.debian.org appear to be broken because http://www.debian.org/security/2009 does not exist. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.27.7 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#510278: RFP: libfeedbag-ruby -- feed auto-discovery Ruby library/tool
Package: wnpp Severity: wishlist * Package name: libfeedbag-ruby Version : 0.3 Upstream Author : David Moreno * URL : http://axiombox.com/feedbag * License : GPL Programming Lang: Ruby Description : feed auto-discovery Ruby library/tool Feed auto-discovery Ruby library/tool. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#508732: RFP: libdata-format-html-perl -- format Perl data structures into simple HTML
Package: wnpp Severity: wishlist * Package name: libdata-format-html-perl Version : 0.3 Upstream Author : David Moreno * URL : http://search.cpan.org/~damog/Data-Format-HTML-0.3/ * License : Perl's and WTFPL Programming Lang: Perl Description : format Perl data structures into simple HTML In theory you can pass any kind of Perl data structure to format and you will get its data HTML-formatted. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#508580: RFP: libapache2-archive-perl -- expose archive files through the Apache web server
Package: wnpp Severity: wishlist * Package name: libapache2-archive-perl Version : 0.1 Upstream Author : J. Peterson David Moreno * URL : http://search.cpan.org/~damog/Apache2-Archive-0.1/lib/Apache2/Archive.pm * License : Perl's Programming Lang: Perl Description : expose archive files through the Apache web server Apache2::Archive is a mod_perl 2 extension that allows the Apache HTTP server to expose tar and tar.gz archives on the fly. When a client requests such an archive file, the server will return a page displaying information about the file that allows the user to view or download individual files from within the archive. Apache2::Archive is an almost fidedign port of the Apache2::Archive module by Jon Peterson. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#508516: RFP: libxml-validate-perl -- an XML validator factory
Package: wnpp Severity: wishlist * Package name: libxml-validate-perl Version : 1.025 Upstream Author : Nathan Carr, Colin Robertson * URL : http://search.cpan.org/~bbc/XML-Validate-1.025/lib/XML/Validate.pm * License : Perl's Programming Lang: Perl Description : an XML validator factory XML::Validate is a generic interface to different XML validation backends. For a list of backend included with this distribution see the README. If you want to write your own backends, the easiest way is probably to subclass XML::Validate::Base. Look at the existing backends for examples. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#508503: RFP: libdata-validate-email-perl -- common email validation methods
Package: wnpp Severity: wishlist * Package name: libdata-validate-email-perl Version : 0.04 Upstream Author : Richard Sonnen . * URL : http://search.cpan.org/~sonnen/Data-Validate-Email-0.04/Email.pm * License : Perl's Programming Lang: Perl Description : common email validation methods This module collects common email validation routines to make input validation, and untainting easier and more readable. All functions return an untainted value if the test passes, and undef if it fails. This means that you should always check for a defined status explicitly. Don't assume the return will be true. (e.g. is_username('0')) The value to test is always the first (and often only) argument. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#481322: lists.debian.org: debian-l10n-belarusian
On Thu, 2008-05-15 at 12:22 +0300, Pavel Piatruk wrote: > Suggestion to create debian-l10n-belarusian > > Name: debian-l10n-belarusian > > Rationale: For communicating about Debian belarusian localization. > > Long description: Now we are have our own maillist located on > d-i.tanatos.org, but we want have general name for our list inside > domain debian.org. After such maillist has been created we'll transfer > our subscribers to the new list. > > Subscription policy: open > > Post policy: open > > Web-archive: yes > > Short description: Debian l10n in Belarusian Christian, Can you please comment on this ticket? I'd like your comments on the work you've followed by the Belarusian community with regards to Debian and if it's worth to create an official mailing list for such tasks. David. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#502326: firmware update
I can also confirm (2) that given the provided firmware by Zhu Yi the issue is fixed on the same 2.6.27.7 kernel I built and talked about before (1) for Lenny, using the iwl4965 driver. 1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502326#41 2: http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1703#c53 David. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#502326: Confirm for 2.6.27.7
I can confirm that this is still present on a homegrown 2.6.27.7. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#504110: ajaxterm: fails to install and start of no zlib python module is found
Package: ajaxterm Version: 0.9-2 Severity: important devbox:/home/david# aptitude install ajaxterm Reading package lists... Done Building dependency tree... Done Reading extended state information Initializing package states... Done Reading task descriptions... Done Building tag database... Done The following NEW packages will be installed: ajaxterm 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 38.6kB of archives. After unpacking 254kB will be used. Writing extended state information... Done Get:1 http://ftp.egr.msu.edu etch/main ajaxterm 0.9-2 [38.6kB] Fetched 38.6kB in 0s (82.0kB/s) Selecting previously deselected package ajaxterm. (Reading database ... 38404 files and directories currently installed.) Unpacking ajaxterm (from .../ajaxterm_0.9-2_all.deb) ... Setting up ajaxterm (0.9-2) ... Starting web based terminal: ajaxtermTraceback (most recent call last): File "/usr/share/ajaxterm/ajaxterm.py", line 11, in import qweb File "/usr/share/ajaxterm/qweb.py", line 109, in import cgi,datetime,email,email.Message,errno,gzip,os,random,re,socket,sys,tempfile,time,types,urllib,urlparse,xml.dom File "/usr/local/lib/python2.5/gzip.py", line 9, in import zlib ImportError: No module named zlib /etc/init.d/ajaxterm: line 37: return: can only `return' from a function or sourced script failed! invoke-rc.d: initscript ajaxterm, action "start" failed. dpkg: error processing ajaxterm (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: ajaxterm E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up ajaxterm (0.9-2) ... Starting web based terminal: ajaxtermTraceback (most recent call last): File "/usr/share/ajaxterm/ajaxterm.py", line 11, in import qweb File "/usr/share/ajaxterm/qweb.py", line 109, in import cgi,datetime,email,email.Message,errno,gzip,os,random,re,socket,sys,tempfile,time,types,urllib,urlparse,xml.dom File "/usr/local/lib/python2.5/gzip.py", line 9, in import zlib ImportError: No module named zlib /etc/init.d/ajaxterm: line 37: return: can only `return' from a function or sourced script failed! invoke-rc.d: initscript ajaxterm, action "start" failed. dpkg: error processing ajaxterm (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: ajaxterm -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-powerpc Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages ajaxterm depends on: ii adduser 3.102 Add and remove users and groups ii python2.4.4-2An interactive high-level object-o ii python-support0.5.6 automated rebuilding support for p Versions of packages ajaxterm recommends: ii apache2 2.2.3-4+etch5 Next generation, scalable, extenda ii apache2-mpm-prefork [http 2.2.3-4+etch5 Traditional model for Apache HTTPD ii openssh-server1:4.3p2-9etch3 Secure shell server, an rshd repla -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#498243: xine-lib: multiple heap overflows
tags 498243 + upstream severity 498243 important stop Issues 3A-3G haven't been addressed yet by Xine, not even in release 1.1.15, tagging upstream. As Reinhard Tartler suggests, the severity can be downgraded now; the remaining issues subjected "unexpected process termination and other issues" are not considered to be grave-wise anymore since they are not representing security holes exposing user data or data loss, but only random different problems prone to unexpected crashes or segmentation faults: 'important' severity. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#501154: sympa: diff for NMU version 5.3.4-5.3
tags 501154 + patch thanks Hi, Attached is the diff for my sympa 5.3.4-5.3 NMU. diff -u sympa-5.3.4/src/sympa.pl sympa-5.3.4/src/sympa.pl --- sympa-5.3.4/src/sympa.pl +++ sympa-5.3.4/src/sympa.pl @@ -159,7 +159,7 @@ $log_level = $main::options{'log_level'} if ($main::options{'log_level'}); -my @parser_param = ($*, $/); +my @parser_param = ($/); my %loop_info; my %msgid_table; @@ -337,15 +337,15 @@ # Set the UserID & GroupID for the process -$( = $) = (getgrnam('--GROUP--'))[2]; -$< = $> = (getpwnam('--USER--'))[2]; +$( = $) = (getgrnam('sympa'))[2]; +$< = $> = (getpwnam('sympa'))[2]; ## Required on FreeBSD to change ALL IDs(effective UID + real UID + saved UID) -&POSIX::setuid((getpwnam('--USER--'))[2]); -&POSIX::setgid((getgrnam('--GROUP--'))[2]); +&POSIX::setuid((getpwnam('sympa'))[2]); +&POSIX::setgid((getgrnam('sympa'))[2]); ## Check if the UID has correctly been set (usefull on OS X) -unless (($( == (getgrnam('--GROUP--'))[2]) && ($< == (getpwnam('--USER--'))[2])) { +unless (($( == (getgrnam('sympa'))[2]) && ($< == (getpwnam('sympa'))[2])) { &fatal_err("Failed to change process userID and groupID. Note that on some OS Perl scripts can't change their real UID. In such circumstances Sympa should be run via SUDO."); } @@ -890,7 +890,7 @@ my ($t_listname, $t_robot); # trying to fix a bug (perl bug ??) of solaris version - ($*, $/) = @parser_param; + ($/) = @parser_param; ## test ever if it is an old bad file if ($t_filename =~ /^BAD\-/i){ diff -u sympa-5.3.4/wwsympa/wwsympa.fcgi sympa-5.3.4/wwsympa/wwsympa.fcgi --- sympa-5.3.4/wwsympa/wwsympa.fcgi +++ sympa-5.3.4/wwsympa/wwsympa.fcgi @@ -665,9 +665,9 @@ &Language::SetLang($Language::default_lang); ## Check effective ID - unless ($> eq (getpwnam('--USER--'))[2]) { + unless ($> eq (getpwnam('sympa'))[2]) { &report::reject_report_web('intern_quiet','incorrect_server_config',{},'',''); - &wwslog('err','Config error: wwsympa should run with UID %s (instead of %s)', (getpwnam('--USER--'))[2], $>); + &wwslog('err','Config error: wwsympa should run with UID %s (instead of %s)', (getpwnam('sympa'))[2], $>); } unless (&List::check_db_connect()) { diff -u sympa-5.3.4/debian/changelog sympa-5.3.4/debian/changelog --- sympa-5.3.4/debian/changelog +++ sympa-5.3.4/debian/changelog @@ -1,3 +1,10 @@ +sympa (5.3.4-5.3) unstable; urgency=low + + * Non-maintainer upload. + * Updating to comply with current versions of Perl (Closes: #501154). + + -- David Moreno Garza <[EMAIL PROTECTED]> Sat, 04 Oct 2008 19:47:33 -0400 + sympa (5.3.4-5.2) unstable; urgency=low * Non-maintainer upload. only in patch2: unchanged: --- sympa-5.3.4.orig/sympa.conf +++ sympa-5.3.4/sympa.conf @@ -0,0 +1,170 @@ +## Configuration file for Sympa +## many parameters are optional (defined in src/Conf.pm) +## refer to the documentation for a detailed list of parameters + +### Directories and file location ### + +## Directory containing mailing lists subdirectories +home /var/lib/sympa/expl + +## Directory for configuration files ; it also contains scenari/ and templates/ directories +etc /etc/sympa + +## File containing Sympa PID while running. +## Sympa also locks this file to ensure that it is not running more than once. Caution : user sympa need to write access without special privilegee. +pidfile /var/run/sympa/sympa.pid + +## Umask used for file creation by Sympa +umask 027 + +## The main spool containing various specialized spools +## All spool are created at runtime by sympa.pl +spool /var/spool/sympa + +## Incoming spool +queue /var/spool/sympa/msg + +## Bounce incoming spool +queuebounce /var/spool/sympa/bounce + +## The directory where Sympa stores static contents (CSS, members pictures, documentation) directly delivered by Apache +static_content_path /usr/lib/sympa/static_content + +## The URL mapped with the static_content_path directory defined above +static_content_url /static-sympa + +### Syslog ### + +## The syslog facility for sympa +## Do not forget to edit syslog.conf +syslog LOCAL1 + +## Communication mode with syslogd is either unix (via Unix sockets) or inet (use of UDP) +log_socket_type unix + +## Log intensity +## 0 : normal, 2,3,4 for debug +log_level 0 + +### General definition ### + +## Main robot hostname +domain minina + +## Listmasters email list comma separated +## Sympa will associate listmaster privileges to these email addresses (mail and web interfaces). Some error reports may also be sent to these addresses. +listmaster [EMAIL PROTECT
Bug#478512: Supporting people needed
Hello, I've seen the current debian-research mailing hosted at madduck's server. It has barely seen activity during this year, because of this, I would like to see more people supporting this proposal by replying to this bug. If more people adds rationale for a go to the subject, I think we could create and import the existing mailing list right away. David.
Bug#481322: Updates?
Any fish? No more news.
Bug#486799: Support needed
Hello, We do need more people supporting the proposal of creating this mailing list by replying to this bug, which hasn't happened yet. Please proceed to do so, or we will have to deny this request. David.
Bug#488418: Additional information
Hello John, On Sat, 2008-06-28 at 14:06 -0500, John Goerzen wrote: > Per http://www.debian.org/MailingLists/HOWTO_start_list, here is some > additional information: > > Name: > debian-haskell > > Rationale: > The Debian Haskell developers have collaborated for several years in a > non-official list. We would like to have an official debian.org list > to make things easier for the community and for others in Debian > that need to coordinate with us (such as release managers). We would > also like the stability of the Debian archives. > > Short description: > Haskell packages and maintenance > > Long description: > Discussion of issues related to Haskell on Debian systems, with an > emphasis towards coordinating Haskell packaging standards. Relevant > for anyone packaging Haskell compilers, libraries, or programs on > Debian. > > Category: > Developers > > Subscription Policy: > Open > > Post Policy: > Open > > Web Archive: > Yes > > Existing List: > mbox archives are at > http://urchin.earth.li/pipermail/debian-haskell/ > > I will ask the existing list admin about mail forwarding and subscriber > lists, but do not see this as an obstacle to creating a new list After filing the request, it would be very much appreciated if several other people interested in the new list would send a mail to the bug, in order to record their interest. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#481322: debian-l10n-belarusian
Hello, After filing the request, it would be very much appreciated if several other people interested in the new list would send a mail to the bug, in order to record their interest. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#436305: lists.debian.org: Please create debian-georgian
Hello Aiet, On Sun, 2008-09-07 at 01:39 +0400, Aiet Kolkhi wrote: > I would think there are enough people willing to support > debian-l10n-georgian, but feel free to suggest creating the less > formal [EMAIL PROTECTED] should you think otherwise. Well, it's been even more than a year now and no other people supported the request or commented any more on this bug. I also suggest and insist on creating the team.debian.net mailing list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#455918: WNPP bug retitle
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#454201: WNPP bug retitle
retitle 454201 O: systeminstaller -- Creates Linux distribution images from a set of packages noowner 454201 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 454201 ITA: systeminstaller -- Creates Linux distribution images from a set of packages owner 454201 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#454200: WNPP bug retitle
retitle 454200 O: systemconfigurator -- Unified Configuration API for Linux Installation noowner 454200 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 454200 ITA: systemconfigurator -- Unified Configuration API for Linux Installation owner 454200 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#391473: WNPP bug retitle
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#352440: WNPP bug retitle
retitle 352440 O: wmshutdown -- Allow you to shutdown or reboot your machine noowner 352440 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 352440 ITA: wmshutdown -- Allow you to shutdown or reboot your machine owner 352440 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#418808: WNPP bug retitle
retitle 418808 O: uclibc -- micro C library noowner 418808 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 418808 ITA: uclibc -- micro C library owner 418808 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#450492: WNPP bug retitle
retitle 450492 O: gnuwash.app -- Configurable timer with alarm for GNUstep noowner 450492 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 450492 ITA: gnuwash.app -- Configurable timer with alarm for GNUstep owner 450492 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#450489: WNPP bug retitle
retitle 450489 O: poe.app -- Vorbis comment editor noowner 450489 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 450489 ITA: poe.app -- Vorbis comment editor owner 450489 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#447064: WNPP bug retitle
retitle 447064 O: libapache2-mod-auth-plain -- Module for Apache2 which provides plaintext authentication noowner 447064 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 447064 ITA: libapache2-mod-auth-plain -- Module for Apache2 which provides plaintext authentication owner 447064 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#447067: WNPP bug retitle
retitle 447067 O: libapache2-mod-auth-pam -- module for Apache2 which authenticate using PAM noowner 447067 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 447067 ITA: libapache2-mod-auth-pam -- module for Apache2 which authenticate using PAM owner 447067 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#407652: WNPP bug retitle
retitle 407652 O: html2ps -- HTML to PostScript converter noowner 407652 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 407652 ITA: html2ps -- HTML to PostScript converter owner 407652 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#361346: WNPP bug retitle
retitle 361346 O: astrolog -- Customizable astrology chart calculation program noowner 361346 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 361346 ITA: astrolog -- Customizable astrology chart calculation program owner 361346 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#429513: WNPP bug retitle
retitle 429513 O: netdude -- NETwork DUmp data Displayer and Editor for tcpdump trace files noowner 429513 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 429513 ITA: netdude -- NETwork DUmp data Displayer and Editor for tcpdump trace files owner 429513 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#442045: WNPP bug retitle
retitle 442045 O: matanza -- Space ascii war game noowner 442045 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 442045 ITA: matanza -- Space ascii war game owner 442045 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#374125: WNPP bug retitle
retitle 374125 O: gnurobots -- Program a robot to explore a world noowner 374125 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 374125 ITA: gnurobots -- Program a robot to explore a world owner 374125 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#317063: WNPP bug retitle
retitle 317063 O: secpanel -- A graphical user interface for SSH and SCP noowner 317063 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 317063 ITA: secpanel -- A graphical user interface for SSH and SCP owner 317063 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#369130: WNPP bug retitle
retitle 369130 O: gnome-libs -- GNOME Libraries noowner 369130 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 369130 ITA: gnome-libs -- GNOME Libraries owner 369130 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#414526: WNPP bug retitle
retitle 414526 O: gnome-apt -- graphical package inspection tool noowner 414526 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 414526 ITA: gnome-apt -- graphical package inspection tool owner 414526 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#379258: WNPP bug retitle
retitle 379258 O: openmotif -- Open Motif noowner 379258 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 379258 ITA: openmotif -- Open Motif owner 379258 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#411685: WNPP bug retitle
retitle 411685 O: pike7.7 -- Powerful interpreted programming language, development version noowner 411685 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 411685 ITA: pike7.7 -- Powerful interpreted programming language, development version owner 411685 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#474261: Ditto
Same here. -- Big D. * http://damog.net/ * http://axiombox.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#391196: WNPP bug retitle
retitle 391196 O: cassbeam -- A program for Cassegrain antenna modelling noowner 391196 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 391196 ITA: cassbeam -- A program for Cassegrain antenna modelling owner 391196 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#412610: WNPP bug retitle
retitle 412610 O: gdb-m68hc1x -- GNU Debugger for the Motorola noowner 412610 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 412610 ITA: gdb-m68hc1x -- GNU Debugger for the Motorola owner 412610 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#412609: WNPP bug retitle
retitle 412609 O: newlib-m68hc1x -- newlib library built for noowner 412609 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 412609 ITA: newlib-m68hc1x -- newlib library built for owner 412609 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#472636: lists.debian.org: request for debian-testing-security-announce list
On Tue, Mar 25, 2008 at 9:32 AM, Nico Golde <[EMAIL PROTECTED]> wrote: > Package: lists.debian.org > Severity: wishlist > > Name: debian-testing-security-announce > Rationale: Since beta1 of the lenny installer the testing-security > repository is included in the apt-sources. We already have > a list for sending updates about the security status in > testing but because of this it would be nice to get them to > a more "official" place like we already have debian-security-announce > for example. I strongly disagree. At least to this rationale, I don't really think the creation of a Debian mailing list should be done on how "nice" it would be to get "more official", but in real need for a mailing list and its purpose. There are currently three security mailing lists (-security, -security-announce, -security-tracker) and two testing ones (-testing and -testing-changes), why not use one of those? What about using -security-announce or -testing-changes? I still don't see the real rationale for this mailing list to be created. -- David Moreno - http://www.damog.net/ Yes, you can. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#424715: WNPP bug retitle
retitle 424715 O: labrea -- a sticky honeypot and IDS noowner 424715 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 424715 ITA: labrea -- a sticky honeypot and IDS owner 424715 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#313183: WNPP bug retitle
retitle 313183 O: eterm-themes -- Themes for Eterm, the Enlightened noowner 313183 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 313183 ITA: eterm-themes -- Themes for Eterm, the Enlightened owner 313183 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#370080: WNPP bug retitle
retitle 370080 O: gamix -- Graphical sound mixer for ALSA noowner 370080 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 370080 ITA: gamix -- Graphical sound mixer for ALSA owner 370080 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#349997: comments of eva's ITP
On Sun, Mar 9, 2008 at 1:58 AM, Zhengpeng Hou <[EMAIL PROTECTED]> wrote: > actrually, eva has been uploaded two time last month, but due to the > GFDL issue, rejected by ftp-master. So, how can we track the works > releate to a specific ITP? You should mail the ITP bug and that's it. -- David Moreno - http://www.damog.net/ Yes, you can. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#470538: lists.debian.org: Request for a debian-l10n-basque mailing list
On Tue, Mar 11, 2008 at 4:44 PM, Piarres Beobide <[EMAIL PROTECTED]> wrote: > Package: lists.debian.org > Severity: wishlist > Tags: l10n > > > Name: debian-l10n-basque > > Rationale : We want this new list to coordinate our effor in debian around > transtaion to basque, until now we have been using the > librezale.org main list for debian around work but now in other to avoid > problems we want to create a new list and we think the > best site is lists.debian.org. I asked in debian-i18n about to create > *user-basque or l10n-basque and they suggest me > debian-l10n-basque is better [1]. > > Short description : Basque localization > > Long Description: Discussing Basque localization issues, mainly translating > Debian docs and programs to Basque. > > Category: Internationalization and Translations > > Subscription Policy: Open > > Post Policy : Open > > Web Archive : Yes > > [1] - http://lists.debian.org/debian-i18n/2008/03/msg00036.html Hello, Some months ago I asked on some mailing list (I don't remember which one, to be honest), asking if there were developers or maintainer in the Basque country. I got no reply at all. This leads me to wonder how is the Basque localization doing or what is the real progress you have made and achieved with your work. Thanks, -- David Moreno - http://www.damog.net/ Yes, you can. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#404376: WNPP bug retitle
retitle 404376 O: texmacs-extra-fonts -- extra fonts for the noowner 404376 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 404376 ITA: texmacs-extra-fonts -- extra fonts for the owner 404376 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#377923: WNPP bug retitle
retitle 377923 O: cl-tclink -- Common Lisp bindings to the TrustCommerce transaction system noowner 377923 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 377923 ITA: cl-tclink -- Common Lisp bindings to the TrustCommerce transaction system owner 377923 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#382750: WNPP bug retitle
retitle 382750 O: mined -- Powerful text editor with extensive Unicode noowner 382750 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 382750 ITA: mined -- Powerful text editor with extensive Unicode owner 382750 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#358614: WNPP bug retitle
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#384656: WNPP bug retitle
retitle 384656 O: libphp-pclzip -- zip archive manager class for PHP noowner 384656 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 384656 ITA: libphp-pclzip -- zip archive manager class for PHP owner 384656 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#422163: WNPP bug retitle
retitle 422163 O: gtkpbbuttons -- GTK client for pbbuttonsd noowner 422163 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 422163 ITA: gtkpbbuttons -- GTK client for pbbuttonsd owner 422163 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#422164: WNPP bug retitle
retitle 422164 O: powerprefs -- Client to configure pbbuttonsd noowner 422164 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 422164 ITA: powerprefs -- Client to configure pbbuttonsd owner 422164 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#419075: WNPP bug retitle
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#419083: WNPP bug retitle
retitle 419083 O: eukleides -- a Euclidean geometry drawing language noowner 419083 stop Hello, This is an automatic mail sent to retitle the ITA you have reported or are involved with. Your ITA wnpp bug is being orphaned because of the following reasons: - It is, as of today, older than 250 days. - It hasn't had any activity recently. As this is an automatic procedure, it could of course have something wrong and probably it would be managing some bugs that are not intended by owners and submitters (like you) to be orphaned, for example if the ITA is still of your interest, or there has been some kind of activity around it. In that case, please retitle the bug, do it, DO IT NOW! (I don't want to be blamed because of mass closing and not let people know that they can easily recover their bugs ;-). To retitle it, you simply have to mail <[EMAIL PROTECTED]> with a body text like this: retitle 419083 ITA: eukleides -- a Euclidean geometry drawing language owner 419083 ! stop Further comments on the work done in the bug sent to [EMAIL PROTECTED] would be truly welcomed. Anyway, if you have any kind of problems when dealing with the BTS, feel free to contact me and I'd be more than happy to help you on this: <[EMAIL PROTECTED]>. A similar process is being applied to other kind of wnpp bugs. Thanks for your cooperation, -- David Moreno Garza <[EMAIL PROTECTED]>. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]