Bug#864760: ITP: weechat-el -- Emacs client for weechat IRC relay
Package: wnpp Severity: wishlist Owner: =?utf-8?q?R=C3=A9mi_Vanicat?= * Package name: weechat-el Version : 0.3.1 Upstream Author : Moritz Ulrich * URL : https://github.com/the-kenny * License : GPL Programming Lang: Elisp Description : Chat via weechat's relay protocol in Emacs WeeChat is a fast and light chat client, that can be controlled remotely. weechant.el is an Emacs mode that do it. I will maintain this package as part of the Debian Emacs addons team (pkg-emacsen-add...@lists.alioth.debian.org). -- Rémi Vanicat
Re: Why IceApe?
Jeremy Morton writes: > I know Firefox was rebranded IceWeasel because of the problems with > the Mozilla trademark for Firefox, but as far as I know there is no > such trademark for SeaMonkey and if there is, it's not owned by > Mozilla, it's owned by the SeaMonkey project. SeaMonkey and the SeaMonkey logo are registered trademarks of the Mozilla Foundation. (say seamonkey web site: http://www.seamonkey-project.org/), see http://www.seamonkey-project.org/legal/trademark for their trademarks policy, they follow the "Mozilla Trademark Policy", and as such have the same limitation. -- Rémi Vanicat -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87habv9edl@debian.org
Re: [OT] NM vs. wicd
Svante Signell writes: > On Sun, 2012-04-01 at 16:16 +0800, Paul Wise wrote: >> On Sat, Mar 31, 2012 at 11:42 AM, Carlos Alberto Lopez Perez wrote: >> >> > I had problems with my laptop also waking up mysteriously randomly on >> > unknown events and I managed to solve it just disabling all wakeup >> > events except PBTN >> >> That sounds like an hack. Wouldn't it be better to log the resume >> reason and figure out and fix the core issue? > > Adding to the problems with NM, it is not even possible to edit or add a > connection: Failed to add new connection: (32) Insufficient > privileges. in /etc/NetworkManager/system-connections you will find file describing the connections available at system level. You can edit them, and restart NM to use them. [...] -- Rémi Vanicat -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87bonbclru@debian.org
Re: Wanted: maintainer for git's emacs support
David Bremner writes: > On Fri, 18 Feb 2011 21:18:38 -0600, Jonathan Nieder > wrote: > >> None of the current Debian git maintainers seem to use emacs. This >> means git's emacs support[1] does not get as much care as it deserves: >> see for example bugs #611936, #611931, #611932, #611933, #611934, >> #577834, and #611935. > > FWIW, if I was going to put energy into something related to git and > emacs, it would be into magit [1], which I use daily, and which is also > pretty out of date in Debian. If there should be a change in maintenance of magit, I would be very interested because I'm one of the main upstream developer. About the .el of the git package, I might look at it this week, but I'm not sure if I want to take responsibilities for them as I don't use them. -- Rémi Vanicat -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/877hctr0ya@debian.org
Re: before starting ...
Tony Peña writes: > Hi, > 1st place, sorry by my english, i expected be understood :-) > > i wanna be future DM so have to get some things before right!?, i read it > many docs before start like debian policy, the machine, and the others > and now have to always tab the guide-maint, to see all steps, have the gpg > sign key at subkeys.gpg.net and made account at mentors You probably should ask those kind of question on the debian-mentor, not here. > > but have some questions to prepare the build enviroment. > > 1. i have amd64 debian installed in the laptop, what's happend here if i > adopt the 1st package to start? it's will be created only for amd64 or have > to install ia32 to mantain the packages ori into i386? Maintainer have to build the package for one architecture before uploading because there are so many of then. Then the Debian autobuilder will build it for all other "interested" arch. If there is a problem on a specific arch, then you will have to try to build it for this arch and look what append. > 2. i'm suscribe to debian-devel, debian-amd64, debian-mentors, and others > like security and user but in 3 1st list where i ask to obtain help > specifically for build package? or packages keeping made in arch orig > extrict? debian-mentor is the place for asking beginner question. > 3. if i like some orphaned package, to start mantain and the upstream author > won't will be devel , and it's wrote in C can i do this options? >3.1 can't continues upload the package because for me no exist more new > versions to packages and have to select other ones Main work for a debian maintainer consist in packaging the software. Some software are feature complete, and need no more development, but this do not mean they must disappeared. So you can That say if you don't know C, you will have problem to fix a security hole or any bug, even more if upstream development is dead. Learning some C will be a very good thing. >3.2 i can rewrite in other language for example python, build and upload > again, and in this time keep existing This is rally creating a new software, a clone of the first one. This is a more difficult things to do than it may seem, and you should name it differently than the old software. And this is upstream development, that should be preferably made outside of Debian, and should be included in Debian only when it will be mature enough. > or have for better secure enviroment have my amd64 system and > virtualize a machine as i386 and do the builds into? If there is something specific in your package with regard to i386. Otherwise using pbuilder/cowbuilder or something like that for finals building of your package might be a good idea, but you could use an amd64 as well than a i386 chroot. -- Rémi Vanicat -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8739oqadxm@debian.org
Re: Marius Vollmer [magit] MIA?
Timo Juhani Lindfors writes: > Miles Bader writes: >> He's the maintainer of the "magit" package, which doesn't seem to have >> received any attention in a long time. > > Teemu Hukkanen and me are working on packaging a new upstream > release. We sent a few patches upstream and upstream agreed to change > the build system. [...] Note that I'm both a debian developer and an magit active contributor. So If you need help, sponsor or someone to be a co-maintainer, do not hesitate to ask me. -- Rémi Vanicat -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/878w2cfyzn@debian.org
Re: DFSG violations / buyers guide.
Frank Lin PIAT <[EMAIL PROTECTED]> writes: > On Thu, 2008-10-30 at 11:29 +, Robert Lemmen wrote: >> On Thu, Oct 30, 2008 at 12:07:52PM +0100, Josselin Mouette wrote: >> > Wrong. You can help Ben Finney testing his packages. That would be much >> > more useful than useless babbling on mailing lists. >> >> if you are talking about these [0], i certainly do not own any of these >> pieces of hardware... > > I would be very pleased to have a "Buyers guide" on the wiki (i.e list > devices that are current, supported and dfsg-free). the problem with those list is that they often become outdated and incomplete (who know if this no-name cheap card is supported or not ?), but if it is updated regularly, it can be good idea. -- Rémi Vanicat -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
