Re: Forwarding bugs upstream
As new (sponsored) mantainer i have a few things to say about this thread. First of all. If i receive a bug report, i do my best to handle it in the rigth way, i am in contact with upstream author and fortunately i have no bugs in my package. I personally don't care to forward bugs to upstream. But i only mantain one package, and it's very simple to handle it. But i am also debian user (looks like some people forgets that DD, DM, and Contributors are also debian users), and as a RESPONSIBLE user i also try to report the bugs i found where they belong. Someone has said that this is comunity project and colaborate is the only way to handle it. Yes, BUT, again, some people think that only DD, DM, and Contributors have to colaborate and not only that, it seems that they are ONLY there to provide a service to the user. If this is really a comunity everyone has to do his little effort. Not only DD or DM. I can underestand Jesus in a way, because time ago i received what i think it was a despective and bad response from a mantainer when i asked some help to adopt one of his packages. But I also have received good words and a lot of help from others (one of them has responsed to this thread). I used to be a really active member of forums but i get tired because i felt that users tend to use forums as a Service of attention to the client instead of a place to exchange knowledge. I see now that it is not only a forums issue. 2011/1/14 Sune Vuorela nos...@vuorela.dk Hi Andreas. Would you like to be delegated to help reporting bugs in packages maintained by Qt/KDE team upstream? /Sune I would be glad if i could help you in that (or any) way sune. Unfortunately mi knowledge is not good enough as i would like to, but anyway feel free to CC me some bugs and i'll see if i am ready enough to help in that way. Iker
Re: Nota sobre el SO
El 3 de diciembre de 2010 17:09, Jose Luis Rivas ghostba...@gmail.comescribió: Disculpen pero esta discusión no es para esta lista, los problemas de capa 8 van a debian-user-span...@lists.debian.org -- *From: * Moises Brenes moises.bre...@gmail.com *Date: *Fri, 3 Dec 2010 09:40:32 -0600 *To: *debian-devel-spanish@lists.debian.org *Subject: *Re: Nota sobre el SO Perdón, pero no, creo que te refieres a debia-tro...@lists.debian.org. Esa quedó desactivada, hacedme el favor de ignorar este tipo de cosas.
Re: Bug#602049: ITP: wicd-client-kde -- qt-kde client for wicd
2010/11/3 David Paleino da...@debian.org On Tue, 02 Nov 2010 22:47:02 +0100, Marc Haber wrote: Has there been any development in wicd in the last months that suggests that packaging new wicd stuff is worth it? Due to time costraints of upstream authors, development somewhat stalled in the last months. However, I've recently been accepted in the upstream team, I hope I can give some help there (starting from merging the patches shipped in the Debian package). And I know Adam Blackburn was preparing a bugfix release versioned 1.7.1 (I saw a beta2 tarball of it, so I suppose it's coming out soonish). Iker, I see many people already reviewed your package. With my wicd-maintainer-hat on, I ask you to add a Provides: wicd-client to your binary package. Excuse me, i am not sure if i underestand well, Provides: wicd-client where? in debian-mentors description? Also, if it only depends on Qt libs, it would be better IMVHO if you (or upstream) named it wicd-qt, to stay consistent with other clients (wicd-gtk and wicd-curses). Otherwise, wicd-kde would be fine -- but it's just a matter of consistency, you can call it whatever you like. yeah, i also thougth about that. I just give that name because it was the original author's given name. But he is very happie with my intention to package it for debian and i know for sure that he doesn't care how i name it. So wicd-qt would be grate. But.. are you talking only about the package name or also the binary name? I'll send an email to him just to be sure, maybe he also wants to change it in upstream if i finally find a sponsor. Thank you, David No, thank you. I really want to make this work and your email motivates me so much. Iker
chromium-browser from experimental has included h.264 by default?
Hi, i didn't know where or how to report this, but i have readed in a forum that an user has tried chromium-browser from experimental and seems that it includes by default those privative codecs. I have tried by myself and i agree with him, but maybe i am wrong. this is the process. Adding ubuntu launchpad repositories to install chromium, you need to install chromium-codecs-ffmpeg-nonfree in order to watch youtube videos in html5 format. Purging those packages and installin chronium-browser from experimental i can watch those videos without installing anything else. Is this correct? does chromium-browser package in debian have h264 codecs included? is this because it is in experimental and they will be separated later? or just a mistake? or maybe those codecs are included in other package installed that i haven't seen? thanks Iker
Re: chromium-browser from experimental has included h.264 by default?
El 10 de mayo de 2010 22:36, Giuseppe Iuculano giuse...@iuculano.itescribió: No, it doesn't contain those, see below Chromium in Debian is built against the system FFmpeg headers via pkg-config. This means when Chromium is launched it will assume that FFmpeg is present in the system library path. In this way you can decide which codecs chromium will use. If you can watch youtube html5 video, probably you have installaed libavcodec52, libavformat52 and libavutil50 from debian-multimedia[1] or other third repositories. Thank you Giusseppe BTW, here[2] you can find instructions how to report a bug in Debian I didn't report as a bug because there wasn't anything wrong with the usability, i tought it was something that goes against debian social contract. Cheers, Giuseppe. Thanks again Cheers Iker
