Re: RFS: zynaddsubfx
On Sat, Dec 22, 2007 at 07:35:48PM +, tim hall wrote: > Joerg Jaspert wrote: >> Its in no way important, not even near to it. Its priority extra, so >> lowest possible priority. > > Sorry, wrong terminology. It's a very useful multimedia application, which > many people use and would expect to find in Debian. Therefore it is worth > making the extra effort to keep it well maintained IMO. The point being > that debian-multimedia should deal with it if group maintenance is needed > rather than QA. I don't know the package myself, but if this is true, it seems that the package should be priority optional, not extra. Extra is for packages which you only want if you have special needs. (There are also no conflicts.) Whoever is going to improve and/or take over this package might want to consider changing this. Thanks, Bas -- I encourage people to send encrypted e-mail (see http://www.gnupg.org). If you have problems reading my e-mail, use a better reader. Please send the central message of e-mails as plain text in the message body, not as HTML and definitely not as MS Word. Please do not use the MS Word format for attachments either. For more information, see http://pcbcn10.phys.rug.nl/e-mail.html signature.asc Description: Digital signature
Re: RFS: zynaddsubfx
Hi, > Sorry, wrong terminology. It's a very useful multimedia application, > which many people use and would expect to find in Debian. Therefore it > is worth making the extra effort to keep it well maintained IMO. The > point being that debian-multimedia should deal with it if group > maintenance is needed rather than QA. > I can take care of uploading it, but it will probably happen after Christmas. Hope it's fine.. Ciao! Free -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: zynaddsubfx
On 2007-12-23, Free Ekanayaka <[EMAIL PROTECTED]> wrote: > Hi, > >> Sorry, wrong terminology. It's a very useful multimedia application, >> which many people use and would expect to find in Debian. Therefore it >> is worth making the extra effort to keep it well maintained IMO. The >> point being that debian-multimedia should deal with it if group >> maintenance is needed rather than QA. >> > I can take care of uploading it, but it will probably happen after Christmas. > Hope it's fine.. As it was said earlier, it is already uploaded to delayed/something. Some days ago to delayed/7, so probably it is in delayed/2 now. /Sune -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: timelimit (updated, add Conflicts)
-=| Peter Pentchev, Sun, Dec 23, 2007 at 04:04:22AM +0200 |=- > I am looking for a sponsor for the new version 1.1-2 of my > package "timelimit". The new revision adds a conflict with > the "netpipes" package since both install /usr/bin/timelimit. > > The upload would fix these bugs: 457444 > > The package can be found on mentors.debian.net: > http://mentors.debian.net/debian/pool/main/t/timelimit/timelimit_1.1-2.dsc I'll take care of this. -- damJabberID: [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: MIME support in Debian.
Le Sat, Dec 22, 2007 at 11:01:21PM +0100, Daniel Leidert a écrit : > > Current GNOME and the upcoming KDE 4 both uses the shared-mime-info > database in /usr/share/mime. > > IMHO you should only try to support the mailcap/metamail and the fd.o > shared-mime-info systems. Hi Daniel, many thanks for your answer, I will do what you suggest : mailcap/metamail and fd.o support. If I understood correctly, to do so, I need to: - Have a MimeType entry in the .desktop file. - Have a debian/packagename.mime file in the source package and call dh_installmime. I did not find the way to associate a file suffix to the program. Is MIME the way to go ? The goal would be that mail user agents and webservers would use the right mime type with attached/downloaded files, and that doubleclicking on local files would make them opened by a relevant program. I have another question: can subcategories starting by x- created freely? The program I am working on is Treeview X, a phylogenetic tree viewer that can read Clustal W format. It is text based, so David Paleino, our collaborator from the Debian-Med packaging team, suggested text/clustalw-tree. But maybe I can submit a wishlist bug on chemical-mime-data to have chemical/clustalw-tree from your namespace ? Have a nice day, -- Charles Plessy http://charles.plessy.org Wakō, Saitama, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#457477: devscripts: [tagpending] Did not tag the bug.
reopen 457477 severity 457477 wishlist retile 457477 Please support the DEBEMAIL environment variable. thanks Le Sat, Dec 22, 2007 at 10:35:07PM +0100, Julien Cristau a écrit : > On Sun, Dec 23, 2007 at 03:04:44 +0900, Charles Plessy wrote: > > > Indeed, here is an extract with the unsuccessful tagpending and the > > successful reportbug. > > 2007-12-22 18:15:37 1J67wm-0003fx-52 ** [EMAIL PROTECTED] R=dnslookup > > T=remote_smtp: SMTP error from remote mail server after RCPT TO:<[EMAIL > > PROTECTED]>: host bugs.debian.org [140.211.166.43]: 550-Verification failed > > for <[EMAIL PROTECTED]>\n550-Unrouteable address\n550 Sender verify failed > > you need to fix your mail setup, to not send mail from unrouteable > addresses. Thanks Julien for your fast answer. Tools like reportbug work out of the box on my machine; I suppose that it is because they recognise the DEBEMAIL environment variable, in which there is a routable email adress to use. Do you think that tagpending could use it? I could try to write a patch for this, but although I know a little bit of Perl, I do not know what is the level of securisation and input sanitisation that would be expected. But if somebody points me to an example where I could find inspiration, I will give it a try. Have a nice day, -- Charles Plessy http://charles.plessy.org Wakō, Saitama, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#457477: devscripts: [tagpending] Did not tag the bug.
On Mon, 24 Dec 2007 02:13:48 +0900, Charles Plessy wrote:
> Tools like reportbug work out of the box on my machine; I suppose that
> it is because they recognise the DEBEMAIL environment variable, in which
> there is a routable email adress to use. Do you think that tagpending
> could use it?
It should.
tagpending just calls "eval bts ${BTS_ARGS}" at the end, and bts
should honour DEBEMAIL.
Cheers,
gregor
--
.''`. http://info.comodo.priv.at/ | gpg key ID: 0x00F3CFE4
: :' : debian: the universal operating system - http://www.debian.org/
`. `' member of https://www.vibe.at/ | how to reply: http://got.to/quote/
`-NP: Status Quo: Ain't Complaining
signature.asc
Description: Digital signature
RFS: poco (updated package - GCC-4.3 patch)
Dear mentors, I am looking for a sponsor for the new version 1.2.9-3 of my package "poco". It builds these binary packages: libpoco-dev - Development files for POCO - The C++ Portable Components libpoco2 - POCO - The C++ Portable Components The package appears to be lintian clean. The upload would fix these bugs: 457356 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/poco - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/poco/poco_1.2.9-3.dsc I would be glad if someone uploaded this package for me. Kind regards, -- Krzysztof Burghardt <[EMAIL PROTECTED]> http://www.burghardt.pl/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ITU: wmanager (update, adopt, fix bugs)
On Thu, Dec 20, 2007 at 05:11:35PM +0200, Peter Pentchev wrote: > On Wed, Dec 19, 2007 at 07:04:25PM -0600, Luis Rodrigo Gallardo Cruz wrote: > > On Mon, Dec 17, 2007 at 02:02:06PM -0600, Luis Rodrigo Gallardo Cruz wrote: > > > On Mon, Dec 17, 2007 at 06:44:23PM +0200, Peter Pentchev wrote: > > > > Dear mentors, > > > > > > > > I am looking for a sponsor for the new version 0.2.1-3 of the "wmanager" > > > > package; I am hereby attempting to adopt it, fix its two bugs, and > > > > bring it > > > > up-to-date with the Debian policy and the modern world in general :) > > > > > > I will review your package. You made quite a few changes, so it might > > > take me several days. > > > > Ok, my (very few) comments: > Done, see below for the updated package. > > However, there just might be a problem here - not with wmanager itself, > but a more general problem. I pretty much copied those rules from the > dpatch manual - the "DPATCH IN DEBIAN PACKAGES" section. The examples > given there will not work with parallel make either. > > Should a bug against dpatch be filed to update the manual? Or should we > wait until people come to at least some sort of agreement on the > parallel make issue before filing any bugs and making changes? :) > (yeah, I guess you can tell I've been following the parallel make > discussion on debian-policy ;) Well, even if we decide not to support paralel builds at all, I see no reason to make them difficult on purpose, so I guess it's still a bug in dpatch to be suggesting this ;) > > 2. It would be nice to pass along at least the makefile patch > > upstream. > Actually I intend to pass *all* the changes upstream ... > On to your actual question - yes, if the upstream author turns out to be > inactive, I do intend to take up maintainership of wmanager Cool. > > 3. Will you be wanting to keep debian/rules as is, or are you planning > > to migrate to some helper package? If the second, be aware that I'm > > not willing to sponsor cdbs based packages. I don't understand it and > > I'm not really willing to learn it. Thus, I'd politely recommend ;) > > you use debhelper. > > Well, I myself like debhelper very much, and both my local packages > (most of which will never see the light of day for work-related reasons) > and the timelimit package that I've RFS'd recently are all done using > debhelper. With wmanager, the situation is somewhat weird - Tommi > Virtanen actually used it in the past, but dropped it in version 0.2-4 > seven years ago. We'll see - there's a very good chance that I will > reintroduce debhelper at some point instead of doing things by hand > (like the md5sums file creation). In this version, I just wanted to > deviate as little as possible from Tommi Virtanen's work. That's good. And it's good you started small, too. > > Other than that, your package is very nicely updated, so as soon as > > you do the patching rules fixes, I can sponsor this version. > > Thanks a lot! :) I uploaded an updated version to mentors.debian.net - > http://mentors.debian.net/debian/pool/main/w/wmanager/wmanager_0.2.1-3.dsc Got it. I'm currently building and testing a final time, and will upload it shortly. Feel free to contact me privately for further sponsoring for this package. -- Rodrigo Gallardo GPG-Fingerprint: 7C81 E60C 442E 8FBC D975 2F49 0199 8318 ADC9 BC28 signature.asc Description: Digital signature
Re: Bug#457477: devscripts: [tagpending] Did not tag the bug.
Le Sun, Dec 23, 2007 at 06:27:59PM +0100, gregor herrmann a écrit :
> On Mon, 24 Dec 2007 02:13:48 +0900, Charles Plessy wrote:
>
> > Tools like reportbug work out of the box on my machine; I suppose that
> > it is because they recognise the DEBEMAIL environment variable, in which
> > there is a routable email adress to use. Do you think that tagpending
> > could use it?
>
> It should.
> tagpending just calls "eval bts ${BTS_ARGS}" at the end, and bts
> should honour DEBEMAIL.
Hi,
indeed, using bts directly produces the same problem : the mail is
rejected by the BTS (while test mails are accepted in my work mail box
for instance). The error message is the following:
2007-12-23 21:49:11 1J6Xl0-0006a2-6Z ** [EMAIL PROTECTED]
R=dnslookup T=remote_smtp: SMTP error from remote mail server after RCPT
TO:<[EMAIL PROTECTED]>: host bugs.debian.org [140.211.166.43]:
550-Verification failed for <[EMAIL PROTECTED]>\n550-Unrouteable
address\n550 Sender verify failed
Also, it is a bit frustrating that unless digging in the logs, it is not
possible to know that the operation failed. If the problem is more the
configuration of the BTS, could at least DEBEMAIL be used to deliver an
error message ?
Have a nice day,
--
Charles Plessy
http://charles.plessy.org
Wakō, Saitama, Japan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#457477: devscripts: [tagpending] Did not tag the bug.
On Mon, Dec 24, 2007 at 06:02:35 +0900, Charles Plessy wrote: > Also, it is a bit frustrating that unless digging in the logs, it is not > possible to know that the operation failed. If the problem is more the > configuration of the BTS, could at least DEBEMAIL be used to deliver an > error message ? > The problem is not bts, or tagpending, or the BTS. The problem is that your MTA is not configured correctly. With exim, which you appear to be using, see /etc/email-addresses. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#457477: devscripts: [tagpending] Did not tag the bug.
Le Sun, Dec 23, 2007 at 09:10:41PM +, Julien Cristau a écrit : > > > The problem is not bts, or tagpending, or the BTS. The problem is that > your MTA is not configured correctly. With exim, which you appear to be > using, see /etc/email-addresses. Le Sun, Dec 23, 2007 at 10:18:01PM +0100, Mohammed Adnène Trojette a écrit : > > And this causes bugs.debian.org to fail sender verification. > So either use an SMTP with *routeable* address or make your mailname a > routeable address. Well, I do understand that I have a poorly configured mail server on my machine. Indeed it is a laptop, not a mail server. Other sites accept the test mails I send from this laptop, and since I am not a system administrator, I strictly have no clue on what to do to get with `bts' the same level of functionality than with `reportbug', that is: installing it on a machine and using it "out of the box" to communicate with the BTS. Apparently I am wrong that the DEBEMAIL environment variable can contain useful information which would make `bts' able to send mails that would not be rejected by the BTS when using a default Debian instalation. I will not bother you further and stop using tools that I can not master because of my lack of interest and skills in the art of mailserver configuration. Have a nice day, -- Charles Plessy http://charles.plessy.org Wakō, Saitama, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#457477: devscripts: [tagpending] Did not tag the bug.
On Mon, 24 Dec 2007, Charles Plessy wrote: Le Sun, Dec 23, 2007 at 09:10:41PM +, Julien Cristau a écrit : The problem is not bts, or tagpending, or the BTS. The problem is that your MTA is not configured correctly. With exim, which you appear to be using, see /etc/email-addresses. Le Sun, Dec 23, 2007 at 10:18:01PM +0100, Mohammed Adnène Trojette a écrit : And this causes bugs.debian.org to fail sender verification. So either use an SMTP with *routeable* address or make your mailname a routeable address. Well, I do understand that I have a poorly configured mail server on my machine. Indeed it is a laptop, not a mail server. Other sites accept the test mails I send from this laptop, and since I am not a system administrator, I strictly have no clue on what to do to get with `bts' the same level of functionality than with `reportbug', that is: installing it on a machine and using it "out of the box" to communicate with the BTS. Apparently I am wrong that the DEBEMAIL environment variable can contain useful information which would make `bts' able to send mails that would not be rejected by the BTS when using a default Debian instalation. I will not bother you further and stop using tools that I can not master because of my lack of interest and skills in the art of mailserver configuration. If your ISP has an SMTP server you can use as a relay, which is almost always the case, configuring your Exim to go through that should be fairly easy. That should eliminate these purplexing issues (by offloading them to your ISPs' system administrators, who have alreaddy solved them!). I hope this helps - feel free to email me privately to ask for more help. -- Asheesh. -- All possibility of understanding is rooted in the ability to say no. -- Susan Sontag
Re: Bug#457477: devscripts: [tagpending] Did not tag the bug.
Le Sun, Dec 23, 2007 at 04:57:12PM -0500, Asheesh Laroia a écrit : > > If your ISP has an SMTP server you can use as a relay, which is almost > always the case, configuring your Exim to go through that should be fairly > easy. That should eliminate these purplexing issues (by offloading them > to your ISPs' system administrators, who have alreaddy solved them!). > > I hope this helps - feel free to email me privately to ask for more help. Thanks a lot for the help. The machine I use is a laptop, that goes from network to network. Is there a way to get the right relay automatically selected when I plug the ethernet cable ? Have a nice day. -- Charles Plessy http://charles.plessy.org Wakō, Saitama, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#457477: devscripts: [tagpending] Did not tag the bug.
On Mon, 24 Dec 2007, Charles Plessy wrote: Le Sun, Dec 23, 2007 at 04:57:12PM -0500, Asheesh Laroia a écrit : If your ISP has an SMTP server you can use as a relay, which is almost always the case, configuring your Exim to go through that should be fairly easy. That should eliminate these purplexing issues (by offloading them to your ISPs' system administrators, who have alreaddy solved them!). I hope this helps - feel free to email me privately to ask for more help. Thanks a lot for the help. The machine I use is a laptop, that goes from network to network. Is there a way to get the right relay automatically selected when I plug the ethernet cable ? What I do is something you'll probably consider a lame hack, but I don't know a better solution: My laptop runs an SMTP server on localhost port 25 that, when it receives mail, opens an SSH tunnel to a machine that *does* know it's ISP's SMTP server, and talks to that ISP SMTP server over the SSH tunnel. If you do have a machine like that (a desktop, or a server shell account) somewhere, then I'm happy to provide more details. Alternately, your home ISP might support sending mail through it using a username and password - that would be easiest; then you could configure your laptop's Exim to talk to your home ISP's SMTP server (or your Mail User Agents could talk to it). -- Asheesh. -- All of a sudden, I want to THROW OVER my promising ACTING CAREER, grow a LONG BLACK BEARD and wear a BASEBALL HAT!! ... Although I don't know WHY!!
Re: MIME support in Debian.
Am Montag, den 24.12.2007, 01:39 +0900 schrieb Charles Plessy: > Le Sat, Dec 22, 2007 at 11:01:21PM +0100, Daniel Leidert a écrit : > > > > Current GNOME and the upcoming KDE 4 both uses the shared-mime-info > > database in /usr/share/mime. > > > > IMHO you should only try to support the mailcap/metamail and the fd.o > > shared-mime-info systems. > > many thanks for your answer, I will do what you suggest : > mailcap/metamail and fd.o support. If I understood correctly, to do so, > I need to: > > - Have a MimeType entry in the .desktop file. - Add MIME tyopes to the shared-mime-info database if necessary via dh_installmime and a .sharedmimeinfo file (or similar). These two things belong to the fd.o system. > - Have a debian/packagename.mime file in the source package and call >dh_installmime. This is metamail/mailcap. > I did not find the way to associate a file suffix to the program. This is done via the MimeType entry in .desktop files. Check out /usr/share/applications. This file contains the information, which file/MIME types can be opened/processed by an application. > Is MIME the way to go ? MIME just gives you a way to classify content via the Internet Content Type aka MIME type. So tell the system, that the suffix belongs to a MIME type (several systems: libmagic, /usr/share/mime, /usr/share/mime-info/*.mime + /etc/gnome-vfs-mime-magic, /usr/share/mimelnk + /etc/kde3/magic/*.magic) and associate your program with this MIME type (also several systems: /usr/share/applications, /usr/share/applnk (obsolete), /usr/share/mimelnk/*.keys (obsolete), /etc/mailcap). > The goal would be that mail user agents and MUAs like evolution use the shared-mime-info database to determine the MIME type of an attachment. I guess that Kmail uses the KDE3-database of MIME types (a mixture of .desktop files in /usr/share/mimelnk and an old version of libmagic, that may be used to determine content pattern for file types). I don't know, what Mutt uses. AFAIK it does not use libmagic. But I may be wrong. > webservers This is a question of configuring the web-server. You can use the mime-support (/etc/mime.types) and/or libmagic (man 5 magic) system for .g. the apache web server. Both cannot be extended easily during a package installation. So it's more or less the system administrators job. > would use the right mime type with attached/downloaded files, > and that doubleclicking on local files would make them opened by a > relevant program. The MIME type (often used to represent the file type) of local files is determined depending on the desktop used. KDE 3 has its own system. XFCE4 and current GNOME AFAIK both use the shared-mime-info database (KDE 4 will use it too and drop its own solution). > I have another question: can subcategories starting by x- created > freely? The `x-' in e.g. $primary_type/x-foo means, that this is not an official/registered MIME type. See RFC 2045 and 2048. > The program I am working on is Treeview X, a phylogenetic tree > viewer that can read Clustal W format. It is text based, so David > Paleino, our collaborator from the Debian-Med packaging team, suggested > text/clustalw-tree. If it is unofficial use text/x-clustalw-tree or application/x-clustalw-tree (depends). To define this MIME type, add an entry to the shared-mime-info database by writing a file similar to those found in /usr/share/mime/packages (dh_installmime/.sharedmimeinfo). The syntax is described in the related fd.o specification, also shipped with the shared-mime-info packages. Then associate your program via a .desktop file in /usr/share/applications. Put the created MIME type in the MimeType filed in the .desktop file and call dh_desktop in your debian/rules. The MIME type detection should now work on current GNOME and XFCE desktops. The program<->MIME type association should work on GNOME, XFCE and KDE. However, KDE 3 uses its own way to add MIME type definitions to the system. Say you called your MIME type application/x-clustalw-tree, then install a file x-clustalw-tree.desktop into /usr/share/mimelnk/applications (the directories under /usr/share/mimelnk follow the syntax of MIME types). To support this MIME type via libmagic, add your entries to /etc/magic(.mime). To associate your program via /etc/mailcap, use dh_installmime/.mime. > But maybe I can submit a wishlist bug on > chemical-mime-data to have chemical/clustalw-tree from your namespace ? Well, chemical is not a registered primary type. It just spread all over the world after it had been suggested in 1995. However, it has never been registered and we had some discussions about the future of chemical/* in the past. It would be better to use one of the official primary types like text/ or application/ if possible. But I don't know the content of this file type, so I cannot suggest anything here. Maybe you can attach an example file to one of your mails? PS: Even if I shall add it to chemical-mime-data, it would be chemica
