Re: "Bug of the month", or how to get people fixing bugs
On Thursday 29 August 2002 19:45, Andrew Suffield wrote: > [Obey M-F-T or die] > > Here's the basic idea: turn bug-fixing into a game (a counterbalance > to the huge quantities of time which moon-buggy and frozen-bubble have > taken away from Debian development). > > People register to play, and each month, all the players are given > three randomly selected bugs to tackle. Points are awarded to those > whose assigned bugs get fixed during that month, with the idea being > that people would endeavour to ensure their bugs get fixed swiftly, by > whatever means they can (closing spurious bug reports, sending patches > to the BTS, making NMUs, harassing the maintainer, or whatever). > Interesting concept. Does the player score if they post a patch or if the maintainer actually accepts it? Also once you have this more fully fleshed out perhaps announcing this on some place like DebianPlanet would be a good idea. We have plenty of users who have time to fix a bug or two but not become full time devels. Or is this meant as a Debian devels only game?
"Bug of the month", or how to get people fixing bugs
[Obey M-F-T or die] Here's the basic idea: turn bug-fixing into a game (a counterbalance to the huge quantities of time which moon-buggy and frozen-bubble have taken away from Debian development). People register to play, and each month, all the players are given three randomly selected bugs to tackle. Points are awarded to those whose assigned bugs get fixed during that month, with the idea being that people would endeavour to ensure their bugs get fixed swiftly, by whatever means they can (closing spurious bug reports, sending patches to the BTS, making NMUs, harassing the maintainer, or whatever). Clearly some assigned bugs will be simpler than others, but difficulty should average out over time. Also, players with more time to spend on bugs can improve their position the next month by closing all the non-bugs they can find, so that less dedicated players are less likely to get easy bugs and thusly will score less. ;) This is far from a full set of rules; far more details were covered in the IRC discussion which spawned this. Lots of possible abuses were discussed, and solutions found, so please refrain from responding along those lines for now. The interface should be extremely simple - once you've signed up, all you have to do is to fix the bugs you get assigned, and a scoreboard will get posted to some mailing list on a regular basis. But, before I go implementing any of this, I want to know if people are interested. So, if you think you'd like to try it, send mail to [EMAIL PROTECTED] (From: addresses will be fed into the subscription system once it's set up; if you change your mind later, just ignore the confirmation message you get and it'll be the last you hear about it). If I get enough responses over the next few days, I'll write the formal rules and set up the scripts. If you have ideas for a better name, send them to [EMAIL PROTECTED] [Kudos to Richard Braakman for coming up with the idea and helping sketch out most of the details] -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | Dept. of Computing, `. `' | Imperial College, `- -><- | London, UK pgpFnLQSt7ftl.pgp Description: PGP signature
Re: Bug#158683: ITP: oggasm -- MP3 to Ogg converter
On Wed, 2002-08-28 at 18:34, Robert Millan wrote: > Also since this depends on mpg321 it'd have to be in non-US. Certainly not. mpg321 isn't in non-US now, and probably won't ever be. However, if the time comes that we think it's necessary to move mp3 players to non-*FREE*, I'm going to ask that mpg321 be removed from Debian altogether. -- Joe Drew <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> "This particular group of cats is mostly self-herding." -- Bdale Garbee
Re: Bug#158683: ITP: oggasm -- MP3 to Ogg converter
> | To clarify, since the beginning of our mp3 licensing program in 1995, > | Thomson has never charged a per unit royalty for freely distributed software > | decoders. For commercially sold decoders primarily hardware mp3 players > | the per-unit royalty has always been in place since the beginning of the > | program. This is irrelivent since debian is commercially sold. I suppose it would let us put mp3 decoders in non-free or something. -- see shy jo
Bug#158820: ITP: lpairs -- The classical memory card game
Package: wnpp Version: N/A; reported 2002-08-29 Severity: wishlist * Package name: lpairs Version : 1.0 Upstream Author : Michael Speck <[EMAIL PROTECTED]> * URL : http://lgames.sourceforge.net/ * License : GPL Description : The classical memory card game LPairs is like the old childhood board game 'Memory'. This means that you have to find pairs of identical cards that will then be removed. Your time and tries needed are counted but there is no high score file or limit to this. This game is part of the LinuxGames suite available from http://lgames.sourceforge.net/ and, like all LGames programs, provides a menu to configure sound, graphics, and gameplay. -- System Information: Debian Release: testing/unstable Architecture: powerpc Kernel: Linux laecheln 2.4.19-pre7-ben0 #1 Sun Apr 28 21:17:30 EDT 2002 ppc Locale: LANG=C, LC_CTYPE=C -- no debconf information
Spam mail warning notification! (Attachment Removal)
eManager Notification * The following mail was blocked since it contains sensitive content. Source mailbox: Destination mailbox(es): <[EMAIL PROTECTED]> Policy: Attachment Removal Attachment file name: SRC.bat - application/octet-stream Action: Replaced with text eManager has removed a sensitive attachment file in the email. *** End of message * Received: from logs-wl.proxy.aol.com (logs-wl.proxy.aol.com [205.188.199.5]) by rly-ip01.mx.aol.com (v83.35) with ESMTP id RELAYIN1-0829215921; Thu, 29 Aug 2002 21:59:21 -0400 Received: from Pfoxtwl (AC8A7AD5.ipt.aol.com [172.138.122.213]) by logs-wl.proxy.aol.com (8.10.0/8.10.0) with SMTP id g7U1q5Q255356 for <[EMAIL PROTECTED]>; Thu, 29 Aug 2002 21:52:06 -0400 (EDT) Date: Thu, 29 Aug 2002 21:52:06 -0400 (EDT) Message-Id: <[EMAIL PROTECTED]> From: postmaster <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Undeliverable mail--"Language" MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=JUi7j844u6EO6fL9k39 X-Apparently-From: [EMAIL PROTECTED]
×îпÕÔËÔ˼۸ñ=ÉϺ£
您好 本邮件为善意邮件，如果对您产生不良影响 我们在这里像您真心的说一声： 对不起！ 我司《世聚物流有限公司》是从事国际货运代理和物流的专业公司 ,她是一家合作公司。在国外的股东是《SINGLE LOGISTICS LTD》， 他可以提供我们世界各地的代理供我们使用，使我们可以承接传统的 运输的同时，承接到付货/门到门/和内陆中转/清关的一系列服务 在国内的股东是《恒荣国际货运有限公司》 我们拥有接近100人的专业团队，自己的仓库/拖车和报关行， 我们的空运公司可以承接300-400个空港的货物，价格合理 所以我们可以 为您提供 专业的人才，周到的服务，试试就知道！！ 我们的网络遍布世界各地，门道门/中转货使您尽情享受！ * 世聚物流有限公司――上海代表处 * 恒荣国际货运有限公司* * 电话总机: 021-65861818（80线） * 转264/266分机 * 图文传真：021-65869001/65869003 * 快捷电话：（0）13166217040 * 邮箱:[EMAIL PROTECTED] * 联系人：郭志刚 先生 * * 美国空运价格： 货币：人民币 --- 目的空港航空公司+100KGS +300KGS +500KGS 1000KGS以上 --- LAX/SFO MU（直航） 35.735.734.731.7 CA（直航） 35.734.734.731.7 JL（中转） 26 26 26 25 OZ（中转） 26.726.725.725.7 ORD MU（直航） 35.735.734.732.7 CA（直航） 35.535.533.532.5 JL（中转） 27 27 27 26 OZ（中转） 26.726.725.724.7 NYC MU（直航） 35.735.734.732.7 CA（直航） 35.534.534.532.5 JL（中转） 27 27 27 26 OZ（中转） 26.726.725.724.7 SEA MU（直航） 35.735.734.732.7 JL（中转） 28 28 28 27 OZ（中转） 26.726.725.724.7 地面杂费（包干）：200/票超过500公斤免收 航班日期： MU（东航） 二/四/六 CA（国航） 二/四/日 JL（日航） 天天 OZ（韩航） 天天 其他空港价格欢迎来电查询！ 如果得到您的支持，我们将不遗余力的保证您的舱位！！！ 谢谢 邮件内容与以下文字无关= 优联网络 http://www.chinamysql.com 专业提供各类虚拟主机，不满意可获退款。 强势套餐：100M主机送顶级域名，送10个10M企业油箱，加送20个二级域名，仅需318元/年！ 三龙证券投资 http://3long.sayba.com 为您提供专业理财服务。现在购买只需588元，赠送价值超过1800元的礼品！ 说吧网上商城 http://shop.sayba.com 全是厂商直销的新品或折上折的商品，是您网络购物的好去处！ 使用极星邮件群发，无须通过邮件服务器，直达对方邮箱，速度绝对一流！ 软件下载网址：http://www.lovexin.com，更多的超酷软件等你来下载哦！;
Re: bugs.debian.org: ChangeLog closes handling should be changed
Hi .. On Thu, Aug 29, 2002 at 05:45:29PM +1000, Brian May wrote: >On Tue, Aug 27, 2002 at 08:48:31AM +0200, Gerfried Fuchs wrote: >> What we need is a change here: Bugs should just be closed in unstable. >> How to do this? They should be rather be tagged than be closed >> by an upload to unstable. Not unconditionally, of course. The version >> of the bugreport should be compared with the version currently in >> testing. Some sort of algorithm not too complex but able to handle most >> of the cases shouldn't be too hard to do (yes, I volunteer to help >> there). >Then bugs will me marked as sarge, even though they might be bugs >specific to unstable. > >It would be much better to remove the sid tag when it gets uploaded >to unstable, turn off the sarge tag when it goes into testing, and >turn of the woody tag if it is lucky enough to get into stable. I agree, this could solve the problem, Alfie explained ... Regards Jan -- .''`.Jan-Hendrik Palic | : :' : ** Debian GNU/ Linux ** | ** OpenOffice.org ** ,.. ,.. `. `' http://www.debian.org | http://www.openoffice.org ,: ..` ` `- [EMAIL PROTECTED] | ' ` ` pgplVpA6AhJDe.pgp Description: PGP signature
Re: RFC: Handling of certificates in Debian
On Thu, Aug 29, 2002 at 07:39:37PM -0300, Henrique de Moraes Holschuh wrote: > Nope. We should do so, and have it added to the ca-certificates package I > think. > > Right now, every TLS-enabled package tries to screw it up in new and > never-before-tried ways. So it is okay if I do the same? *hide* Sorry, it's late n8 Torsten pgpMKbFOE982E.pgp Description: PGP signature
Re: [ANNOUNCE] Debian Developer Packages Overview
Hi! This tool is great and very useful. However, there is a little bug with some kind of mangling of the version numbers: on "http://qa.debian.org/developer/index.php?package=loadwatch";, loadwatch appears to have 2 different versions in testing and unstable (1.0_1.1alpha1-1 and 1.0+1.1alpha1-1), while this is in fact the same version. Anyway, this tool is great. Thanks for your work. Nicolas
Re: Bug#152778: DBS feature request vs dpkg-source v2
tags 152778 wontfix thanks. On Thu, Aug 22, 2002 at 11:49:41AM -0700, Jeff Bailey wrote: > Hey Brian, sorry about the delay in responding. If you're comfortable > that dpkg-source v2 is actually going to see the light in the next 6 > months or so, I wouldn't worry about it. Because it's in > experimental, I haven't looked at it at all, but I've been intending > to move to it as soon as it's even minimally ready. > > If you have the feeling that it will take longer than 6 months to hit > unstable, then you should maybe nudge me to write a patch for you. =) I will be optimistic for now, and assume that it will be less then 6 months. . -- Brian May <[EMAIL PROTECTED]>
×îпÕÔËÔ˼۸ñ=ÉϺ£
您好 本邮件为善意邮件，如果对您产生不良影响 我们在这里像您真心的说一声： 对不起！ 我司《世聚物流有限公司》是从事国际货运代理和物流的专业公司 ,她是一家合作公司。在国外的股东是《SINGLE LOGISTICS LTD》， 他可以提供我们世界各地的代理供我们使用，使我们可以承接传统的 运输的同时，承接到付货/门到门/和内陆中转/清关的一系列服务 在国内的股东是《恒荣国际货运有限公司》 我们拥有接近100人的专业团队，自己的仓库/拖车和报关行， 我们的空运公司可以承接300-400个空港的货物，价格合理 所以我们可以 为您提供 专业的人才，周到的服务，试试就知道！！ 我们的网络遍布世界各地，门道门/中转货使您尽情享受！ * 世聚物流有限公司――上海代表处 * 恒荣国际货运有限公司* * 电话总机: 021-65861818（80线） * 转264/266分机 * 图文传真：021-65869001/65869003 * 快捷电话：（0）13166217040 * 邮箱:[EMAIL PROTECTED] * 联系人：郭志刚 先生 * * 美国空运价格： 货币：人民币 --- 目的空港航空公司+100KGS +300KGS +500KGS 1000KGS以上 --- LAX/SFO MU（直航） 35.735.734.731.7 CA（直航） 35.734.734.731.7 JL（中转） 26 26 26 25 OZ（中转） 26.726.725.725.7 ORD MU（直航） 35.735.734.732.7 CA（直航） 35.535.533.532.5 JL（中转） 27 27 27 26 OZ（中转） 26.726.725.724.7 NYC MU（直航） 35.735.734.732.7 CA（直航） 35.534.534.532.5 JL（中转） 27 27 27 26 OZ（中转） 26.726.725.724.7 SEA MU（直航） 35.735.734.732.7 JL（中转） 28 28 28 27 OZ（中转） 26.726.725.724.7 地面杂费（包干）：200/票超过500公斤免收 航班日期： MU（东航） 二/四/六 CA（国航） 二/四/日 JL（日航） 天天 OZ（韩航） 天天 其他空港价格欢迎来电查询！ 如果得到您的支持，我们将不遗余力的保证您的舱位！！！ 谢谢 邮件内容与以下文字无关= 优联网络 http://www.chinamysql.com 专业提供各类虚拟主机，不满意可获退款。 强势套餐：100M主机送顶级域名，送10个10M企业油箱，加送20个二级域名，仅需318元/年！ 三龙证券投资 http://3long.sayba.com 为您提供专业理财服务。现在购买只需588元，赠送价值超过1800元的礼品！ 说吧网上商城 http://shop.sayba.com 全是厂商直销的新品或折上折的商品，是您网络购物的好去处！ 使用极星邮件群发，无须通过邮件服务器，直达对方邮箱，速度绝对一流！ 软件下载网址：http://www.lovexin.com，更多的超酷软件等你来下载哦！;
Re: Bug#158683: ITP: oggasm -- MP3 to Ogg converter
Michael a écrit : > On Thu, Aug 29, 2002 at 09:31:39PM +0200, Fabien Penso wrote: [...] > can you please post the "company statement" that is refferred here? [...] Here is the rest of the message. Someone got in touch with us for http://linuxfr.org/ and this should be published tomorrow. , | Statement from Thomson Multimedia, mp3 Licensing | | In a posting appearing Tuesday August 27, 2002 on the Web site | slashdot.org, an individual cited a change in the mp3 license fee | structure of Thomson and Fraunhofer. The writer of the post apparently | misread the mp3 licensing conditions, as Thomsons mp3 licensing policy has | not experienced any change. | | To clarify, since the beginning of our mp3 licensing program in 1995, | Thomson has never charged a per unit royalty for freely distributed software | decoders. For commercially sold decoders primarily hardware mp3 players | the per-unit royalty has always been in place since the beginning of the | program. | | Therefore, there is no change in our licensing policy and we continue to | believe that the royalty fees of .75 cents per mp3 player (on average | selling over $200 dollars) has no measurable impact on the consumer | experience. ` -- Fabien Penso <[EMAIL PROTECTED]> | LinuxFr a toujours besoin de : http://perso.LinuxFr.org/penso/ | http://linuxFr.org/dons/ A PHP Template Engine ? Take the best ! http://templeet.org/ pgpCXQWdoyKfZ.pgp Description: PGP signature
[VAC] Moving and more
Well all, the rest of this week, I'm moving into my new apartment in Eugene, Oregon. If there are any developers in the area, I'd like to get together somewhere for coffee and keysigning, please email off-list! =) I'll leave galen running here as long as I can, but I won't have time to do much of anything at all because the drive between here and there is so long. Once I get moved in, net access may be spotty or non-existant for several days at least. And then the following week, I'll be in Salem for a few days to attend my mom's wedding. =D So you can all count on me being out of touch for a couple of weeks, more or less. NMU's of anything that need it are welcome. SDL needs it - if you've got arts set up, please feel free to go squash the arts bug. A recompile with libarts1-dev _should_ fix it, though I can't myself test that and won't have a chance to coordinate testing with anyone else till I get back. Also removing the call to autogen.sh in the rules file will workaround the libtool issue for now. Beyond that, see everyone in a couple weeks, or maybe sooner! -- Joseph Carter <[EMAIL PROTECTED]> The guy with a rocket launcher Overfiend: many patches on top of 4.0.1 already? Oskuro: a few only 152 megs pgpO6DiOvDSy2.pgp Description: PGP signature
Re: RFC: Handling of certificates in Debian
On Fri, 30 Aug 2002, Torsten Landschoff wrote: > But now I wonder if there is some established procedure for doing > so. I know many users will not have a key signed by verisign or Nope. We should do so, and have it added to the ca-certificates package I think. Right now, every TLS-enabled package tries to screw it up in new and never-before-tried ways. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
RFC: Handling of certificates in Debian
Hi *, Now that the LDAP packages support TLS I would like to do the next step: Get a sane debconf interface on first installation to setup the directory and generate the TLS key and certificate. But now I wonder if there is some established procedure for doing so. I know many users will not have a key signed by verisign or thawte/whatever but instead sign them themselves. I wonder how to support both modes and if I should have the installation do it all automatically for them. And input appreciated Torsten pgpy5mePBGQ2K.pgp Description: PGP signature
Re: need advice on library interface
Joshua Haberman <[EMAIL PROTECTED]> writes: > libsndfile is close to making a 1.0.0 release. As the new maintainer of > the libsndfile Debian package and as an upstream author for software that > uses libsndfile, I'm working with the libsndfile author to iron out all > the remaining issues with his release candidates. > > We've encountered a problem that involves LFS. libsndfile 1.0 supports > LFS, and since libsndfile's interface includes operations like seeking on > a sound file, some of the functions in his external interface take > parameters of type off_t. He compiles libsndfile with > _FILE_OFFSET_BITS=64, which makes off_t 64 bits. He then adds > _FILE_OFFSET_BITS=64 to the CFLAGS of client programs (using pkg-config), > to ensure that off_t is recognized as 64 bits when compiling the client > program. > > This caused a problem for me when I tried to link against wxWindows, > which *also* includes off_t in its interface but *doesn't* compile with > _FILE_OFFSET_BITS=64. > > As I thought about it more, this seems to cause a more general problem > that the ABI of a library that uses off_t in its interface is not stable, > since function signatures vary based on whether LFS is supported and > compiled in. > > I can think of only two solutions: > >1. fix the ABI to use 64 bits in all cases. Drawbacks: > - if LFS support was not compiled in, values are silently > truncated internally. Don't truncate, return an error. Just like you get an error when seeking behind 2GB without LFS. > - the author tells me that libsndfile is portable to many > systems he does not have access to, and there is no > universal way to declare a 64-bit datatype. C99 declares a int64_t and uint64_t in . Using them would create a build-depends on a C99 compatible compiler. That should be a reasonable demand. If you/the author doesn't like it there are enough configure tests out there to look for a int64_t. >2. define two functions for every API function: a 32-bit version > and a 64-bit version. Substitute in the 64-bit version with > the preprocessor if _FILE_OFFSET_BITS=64 is defined. > Drawbacks: > - PITA > - if libsndfile was not compiled with LFS support but > the client application is, there will be linker errors > when the linker cannot find the 64-bit functions. This > seems minor though: if LFS is supported on a target platform, > it will probably be compiled in. Why should there be no LFS support compiled in? 1. stupidity: let them burn 2. not available: no problem there then. won't be available for the app too. > How should this be solved? Personally I would use the C99 types and check for stdint.h in the configure script. MfG Goswin
debbugs: assign someone from a group of willing people to fix a bug
Package: debbugs Version: 2.3-4 Severity: wishlist Hi, Ever notived how many bugs there are? How many don't get fixed, get ignored, get forgotten? A lot of bugs are years old and might not even exist anymore. I know (most :) maintainers do their best to fix bugs but sometimes there just isn't enough time or will. Or the problem is hard to reproduce. Maintainers might also not have the same architecture or setup as the reportie of a bug. What to do? I would like to propose a setup similar to the one used to translate package descriptions: If a bug is not delt with for some time (no mails or status changes indication work being done) a person is selected out of a pool of willing persons and is mailed the bug. He can then check out the bug and fix it if possible and has the right to do an NMU or close the bug etc. If nothing happens to the bug or if the person sends a reject for the bug another person gets drafted and so on. Some comands could be introduced to control what persons gets the bug next. Like selecting the architecture or some capabilities of the person to be drafted next. Also maintainers should be able to force or stop drafting someone, so e.g. if a maintainer things its an alpha related problem he can tell the BTS to restrict the bug to people having an alpha and draft someone immediatly (without some lengthy wait for the drafting to kick in). The easiest way might be to allways draft someone but draft the maintainer first. If he doesn't react, say within a month, the next person is drafted from the pool. Criteria for drafting someone from the pool should be primary workload. Take the person with the lowest number of bugs assigned. Additionally factors like architecture, dist (stable/testing/unstable), kernel should be matched to the bug reportie if possible. Capabilities like knowing perl or C or favorisms like loving games could also be considered. When starting there should probably be a limit of a few bugs per person, otherwise all tousands of open bugs wouldbe reassigned to a few then soon unwilling helpers. Any comment? Maybe something more than "send patch and we think about it"? May the Source be with you. Goswin -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux dual 2.4.16 #19 SMP Sat Jul 6 04:37:14 CEST 2002 i686 Locale: LANG=C, LC_CTYPE=de_DE Versions of packages debbugs depends on: ii ed0.2-19 The classic unix line editor ii exim [mail-transport-agent] 3.35-1 An MTA (Mail Transport Agent) ii libmailtools-perl [mailtools] 1.48-1 Manipulate email in perl programs ii perl [perl5] 5.6.1-7Larry Wall's Practical Extraction -- no debconf information
Bug#158798: ITP: jpilot-backup -- Backup plugin for J-Pilot
Package: wnpp Version: N/A; reported 2002-08-29 Severity: wishlist * Package name: jpilot-backup Version : 0.42 Upstream Author : Jason Day <[EMAIL PROTECTED]> * URL : http://jasonday.home.att.net/code/backup/backup.html * License : GPL Description : Backup plugin for J-Pilot This program enhances jpilot's own backup, making it much more flexible, handling automatic backups, configuring which applications/databases to back up and which to ignore, etc.
Re: Please compile treetool on alpha, arm, hppa, ia64, powerpc and s390
On Thu, 29 Aug 2002, Tomas Pospisek's Mailing Lists wrote: > > On Thu, Aug 29, 2002 at 09:59:36AM +0200, Andreas Tille wrote: > > > unfortunately treetool is non-free because there is neigther a > > > license nor any upstream author available. > > And what about this: > http://www.hgmp.mrc.ac.uk/Registered/Help/treetool/ > (2nd link when you search for treetool on google) Thanks. Just try it. Wish you more luck than I had ... Kind regards Andreas.
Re: Please compile treetool on alpha, arm, hppa, ia64, powerpc and s390
On Thu, 29 Aug 2002, Branden Robinson wrote: > On Thu, Aug 29, 2002 at 09:59:36AM +0200, Andreas Tille wrote: > > unfortunately treetool is non-free because there is neigther a > > license nor any upstream author available. > > Uh, if there's no license we have no business shipping it at all. > > Even in non-free. > > Please ask debian-legal if you need clarification of this. We have explicite permission: Thanks for your interest in treetool. While treetool is "free"; some portions are copyright the University of Illlinois. I am currently working on getting permission from them to obtain clear rights to the package; in the meantime, I cannot place the program under the GNU license (which is my desire). I do have permission to distribute the program, so you are welcome to include it under the "non-free" area of Debian Linux. When these issues are cleared up, I will place the package under the GNU license and let you know. Regards, Mike McCaughey Click! Computer Services, Inc. Thanks for your remark Andreas.
Re: Bug#158683: ITP: oggasm -- MP3 to Ogg converter
On 08/29/2002 02:45:01 PM Michael Cardenas wrote: >> can you please post the "company statement" that is refferred here? Per this web page, http://www.mp3licensing.com/royalty/software.html, it will cost Debian $50K per program or $0.75 per apt-get (?) There is no exception under any circumstances. Oddly enough, regarding streaming, per http://www.mp3licensing.com/royalty/emd.html Note: No license is needed for private, non-commercial activities (e.g., home-entertainment, receiving broadcasts and creating a personal music library), not generating revenue or other consideration of any kind or for entities with an annual gross revenue less than US$ 100 000.00. So, it costs money to make the SW to encode or decode mp3, but in certain circumstances it doesn't cost $3K per year to stream mp3. A streamer would still be in non-free because the license discriminates against various user activities, such as commercial activities. So, per one PR flack whom updates their web page, there is no exception. Per another PR flack, there is "no change". What is the true license? Whom knows. If I can't figure it out, I'm not going to flame slashdot for not figuring it out either.
Re: Bug#158683: ITP: oggasm -- MP3 to Ogg converter
Fabien Penso wrote: > I think you will hear soon than the person who posted that to Slashdot > was wrong and misunderstood the license. > > See the following... > > , > | From: Steve Syatt <[EMAIL PROTECTED]> > | To: [EMAIL PROTECTED] > | Cc: [EMAIL PROTECTED] > | Subject: mp3 licensing > | Date: 28 Aug 2002 11:40:10 -0700 > | > | Dear Patrick, > | > | I am the public relations person for Thomson multimedia (mp3 licensing) and > | was copied on your email. Please take a look below at the company statement > | response from Thmomson multimedia regarding the Slashdot posting - which was > | written by someone who completely misunderstood the mp3 licensing program! > | Most important, there is no change whatsoever to the mp3 licensing program, > | which has pretty much stayed intact since its inception in 1995! Please > | stay with mp3 - it has always been Thomson's biggest objective to be totally > | accessible and fair to the consumer, and always will be! > | > | Sincerely, > | > | Steve Syatt > | SSA Public Relations (for Thomson multimedia, mp3 Licensing) > ` So, once again, we see that the folks at Slashdot are not journalists and have no conception of even the most simple forms of fact-checking. Thank you, Slashdot, specifically Chris di Bona, who posted the original story about this. Okay. So apparently there's no need to drop mp3 decoders from Debian or other Linux distros (certainly not the non-commercial ones, at least). In which case, there is no pressing need for people to convert their mp3 files to some other format just to avoid legal difficulties. Craig pgpieaeKzGgYJ.pgp Description: PGP signature
Re: Bug#158683: ITP: oggasm -- MP3 to Ogg converter
On Thu, Aug 29, 2002 at 09:31:39PM +0200, Fabien Penso wrote: > > , > | From: Steve Syatt <[EMAIL PROTECTED]> > | To: [EMAIL PROTECTED] > | Cc: [EMAIL PROTECTED] > | Subject: mp3 licensing > | Date: 28 Aug 2002 11:40:10 -0700 > | > | Dear Patrick, > | > | I am the public relations person for Thomson multimedia (mp3 licensing) and > | was copied on your email. Please take a look below at the company statement > | response from Thmomson multimedia regarding the Slashdot posting - which was > | written by someone who completely misunderstood the mp3 licensing program! > | Most important, there is no change whatsoever to the mp3 licensing program, > | which has pretty much stayed intact since its inception in 1995! Please > | stay with mp3 - it has always been Thomson's biggest objective to be totally > | accessible and fair to the consumer, and always will be! > | > | Sincerely, > | > | Steve Syatt > | SSA Public Relations (for Thomson multimedia, mp3 Licensing) > ` > can you please post the "company statement" that is refferred here? -- michael cardenas | lead software engineer | lindows.com | hyperpoem.net "Zen is a way of liberation, concerned not with discovering what is good or bad or advantageous, but what is." - Allan Watts pgpKtwz6gfoXY.pgp Description: PGP signature
Re: Bug#158683: ITP: oggasm -- MP3 to Ogg converter
Fabien Penso wrote: > > I think you will hear soon than the person who posted that to Slashdot > was wrong and misunderstood the license. i think the PR firm is trying to cover up something. the license page makes no exception for freely distributed decoders. -john
Re: Bug#158683: ITP: oggasm -- MP3 to Ogg converter
Craig a écrit : > Furthermore, with the recent announcement of patent royalties from > Frauenhofer, it seems that Debian may need to remove all packages that > are covered by the mp3 patents, at which point an mp3-to-vorbis > converter would either be removed, or would be dependent on software > that is no longer part of Debian. I think you will hear soon than the person who posted that to Slashdot was wrong and misunderstood the license. See the following... , | From: Steve Syatt <[EMAIL PROTECTED]> | To: [EMAIL PROTECTED] | Cc: [EMAIL PROTECTED] | Subject: mp3 licensing | Date: 28 Aug 2002 11:40:10 -0700 | | Dear Patrick, | | I am the public relations person for Thomson multimedia (mp3 licensing) and | was copied on your email. Please take a look below at the company statement | response from Thmomson multimedia regarding the Slashdot posting - which was | written by someone who completely misunderstood the mp3 licensing program! | Most important, there is no change whatsoever to the mp3 licensing program, | which has pretty much stayed intact since its inception in 1995! Please | stay with mp3 - it has always been Thomson's biggest objective to be totally | accessible and fair to the consumer, and always will be! | | Sincerely, | | Steve Syatt | SSA Public Relations (for Thomson multimedia, mp3 Licensing) ` -- Fabien Penso <[EMAIL PROTECTED]> | LinuxFr a toujours besoin de : http://perso.LinuxFr.org/penso/ | http://linuxFr.org/dons/ A PHP Template Engine ? Take the best ! http://templeet.org/ pgp4AaaC7qovb.pgp Description: PGP signature
Re: Security notification script
On Mon, Aug 26, 2002 at 09:31:34PM +0100, Rob Bradford wrote:
> I have written a python script that allows you to compares locally
> installed packages with those on security.debian.org. Furthermore it
> provides a description of the problem/DSA name if the package is
> mentioned in the DSA RDF.
>
> The script is intended to be run as a normal user in a crontab, and thus
> produces no output if the system is completely upto date.
>
> You will need to install python2.2 and python2.2-xml prior to using the
> script which can be found at
> http://www.robster.org.uk/files/security-update-check.py
Great.
Except that the DSA RDF starts with
space space newline, which chokes SAX:
[EMAIL PROTECTED] ~/bin]$ ./security-update-check
Traceback (most recent call last):
File "./security-update-check", line 85, in ?
for advisory in parseDSA():
File "./security-update-check", line 23, in parseDSA
dom = xml.dom.minidom.parse(rdf)
File "/usr/lib/python2.1/site-packages/_xmlplus/dom/minidom.py", line 962, in
parse
return _doparse(pulldom.parse, args, kwargs)
File "/usr/lib/python2.1/site-packages/_xmlplus/dom/minidom.py", line 954, in
_doparse
toktype, rootNode = events.getEvent()
File "/usr/lib/python2.1/site-packages/_xmlplus/dom/pulldom.py", line 265, in
getEvent
self.parser.feed(buf)
File "/usr/lib/python2.1/site-packages/_xmlplus/sax/expatreader.py", line
208, in feed
self._err_handler.fatalError(exc)
File "/usr/lib/python2.1/site-packages/_xmlplus/sax/handler.py", line 38, in
fatalError
raise exception
xml.sax._exceptions.SAXParseException: :2:0: xml processing
instruction not at start of external entity
zsh: 12193 exit 1 ./security-update-check
[EMAIL PROTECTED] ~/bin]$
It works just nicely with 2.1; on 2.2 it dies with
[EMAIL PROTECTED] ~/bin]$ python2.2 ./security-update-check
Traceback (most recent call last):
File "./security-update-check", line 85, in ?
for advisory in parseDSA():
File "./security-update-check", line 23, in parseDSA
dom = xml.dom.minidom.parse(rdf)
File "/usr/lib/python2.2/site-packages/_xmlplus/dom/minidom.py", line 962, in
parse
return _doparse(pulldom.parse, args, kwargs)
File "/usr/lib/python2.2/site-packages/_xmlplus/dom/minidom.py", line 954, in
_doparse
toktype, rootNode = events.getEvent()
File "/usr/lib/python2.2/site-packages/_xmlplus/dom/pulldom.py", line 265, in
getEvent
self.parser.feed(buf)
File "/usr/lib/python2.2/site-packages/_xmlplus/sax/expatreader.py", line
194, in feed
self.reset()
File "/usr/lib/python2.2/site-packages/_xmlplus/sax/expatreader.py", line
232, in reset
self._parser = expat.ParserCreate(None, " ", intern = self._interning)
TypeError: 'intern' is an invalid keyword argument for this function
zsh: 12189 exit 1 python2.2 ./security-update-check
[EMAIL PROTECTED] ~/bin]$
--
:(){ :|:&};:
Re: Bug#158756: ITP: vmailmgr -- Powerful qmail addon package for virtual domain email.
Matthew Danish <[EMAIL PROTECTED]> writes: >> I have packages ready and will upload them ASAP. I also intend to package >> some supporting tools (qmail-autoresponder, oMail-admin etc.) > > Is this the same as vchkpw? Nope. vchkpw is older version of vpopmail, which is almost unpackable because there are compile-time parameters as MYSQL_HOST and so. and because Ken Jones (upstream author) is thinking that he is only who can code :( > And there exists a qmail autoresponder: package "autorespond". qmail-autoresponder: This is a simple program to automatically respond to emails. It is based on some ideas (but little or no code) from a similar autoresponder by Eric Huss , and ideas presented in the qmail mailing list. Features: - Limits rate of automatic responses (defaults to a maximum of one message every hour). - Will not respond to nearly every type of mailing list or bulk email. - Will not respond to bounce messages or MAILER-DAEMON. - Bounces looping messages. - Can insert the original subject into the response. - Can copy original message into response. - Can use links in the rate-limiting data directory to limit inode usage to a single inode. And it is really good (we are using it for our customers). O. -- Ondrej Sury - CIO Globe Internet s.r.o. http://globe.cz/ Tel: +420(2)35365000 Fax: +420(2)35365009 Planickova 1, 162 00 Praha 6
Re: Bug#158756: ITP: vmailmgr -- Powerful qmail addon package for virtual domain email.
On Thu, Aug 29, 2002 at 06:40:52PM +0200, Ondrej Sury wrote: > Package: wnpp > Version: N/A; reported 2002-08-29 > Severity: wishlist > > * Package name: vmailmgr > Version : 0.96.9 > Upstream Author : Bruce Guenter <[EMAIL PROTECTED]> > * URL : http://www.vmailmgr.org/ > * License : GPL > Description : Powerful qmail addon package for virtual domain email. > > I have packages ready and will upload them ASAP. I also intend to package > some supporting tools (qmail-autoresponder, oMail-admin etc.) Is this the same as vchkpw? And there exists a qmail autoresponder: package "autorespond". -- ; Matthew Danish <[EMAIL PROTECTED]> ; OpenPGP public key: C24B6010 on keyring.debian.org ; Signed or encrypted mail welcome. ; "There is no dark side of the moon really; matter of fact, it's all dark."
Re: Please compile treetool on alpha, arm, hppa, ia64, powerpc and s390
> On Thu, Aug 29, 2002 at 09:59:36AM +0200, Andreas Tille wrote: > > unfortunately treetool is non-free because there is neigther a > > license nor any upstream author available. And what about this: http://www.hgmp.mrc.ac.uk/Registered/Help/treetool/ (2nd link when you search for treetool on google) >Copyright (c) 1992, 1993, 1994 University of Illinois board of > trustees. All rights reserved. Written by Michael Maciukenas for the > Ribosomal Database Project. > > Preface > > Treetool was written by Mike Maciukenas, for the Ribosomal Database > Project (RDP), with assistance from Gary Olsen, Niels Larsen, and Carl > Woese. The Ribosomal Database Project is at the University of > Illinois. > > Treetool is a copyrighted program, not in the public domain, all > rights are reserved. Permission is granted to copy and distribute the > program, as long as all copyright messages are left intact, and the > program is copied and distributed for free. > > Treetool is currently maintained by Mike McCaughey of the RDP. Bug > reports, questions and comments should be addressed to > [EMAIL PROTECTED] *t -- --- Tomas Pospisek SourcePole - Linux & Open Source Solutions http://sourcepole.ch Elestastrasse 18, 7310 Bad Ragaz, Switzerland Tel: +41 (81) 330 77 11 ---
Bug#158756: ITP: vmailmgr -- Powerful qmail addon package for virtual domain email.
Package: wnpp Version: N/A; reported 2002-08-29 Severity: wishlist * Package name: vmailmgr Version : 0.96.9 Upstream Author : Bruce Guenter <[EMAIL PROTECTED]> * URL : http://www.vmailmgr.org/ * License : GPL Description : Powerful qmail addon package for virtual domain email. I have packages ready and will upload them ASAP. I also intend to package some supporting tools (qmail-autoresponder, oMail-admin etc.) -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux shade 2.4.20-pre4 #1 Wed Aug 21 12:33:34 CEST 2002 i686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 -- no debconf information
Re: Is this still valid?
On Thu, Aug 29, 2002 at 07:51:19AM -0700, Sean 'Shaleh' Perry wrote: > I never saw this get pushed into policy, joeyh just decided to stop > doing it in debhelper. Joey is cutting the Policy Manual's Gordian Knot. That being the conjunction of "policy-is-supposed-to-document-current-practice, not-be-used-as-a-stick-to-beat-maintainers-with" and "policy-reigns-supreme-and-violating-a-must-or-must-not-directive-means- your-package-is-obscenely-broken-and-should-be-removed-from-the- distribution". -- G. Branden Robinson| Never underestimate the power of Debian GNU/Linux | human stupidity. [EMAIL PROTECTED] | -- Robert Heinlein http://people.debian.org/~branden/ | pgpA7D1YtnA0v.pgp Description: PGP signature
Re: Please compile treetool on alpha, arm, hppa, ia64, powerpc and s390
On Thu, Aug 29, 2002 at 09:59:36AM +0200, Andreas Tille wrote: > unfortunately treetool is non-free because there is neigther a > license nor any upstream author available. Uh, if there's no license we have no business shipping it at all. Even in non-free. Please ask debian-legal if you need clarification of this. -- G. Branden Robinson|America is at that awkward stage. Debian GNU/Linux |It's too late to work within the [EMAIL PROTECTED] |system, but too early to shoot the http://people.debian.org/~branden/ |bastards. -- Claire Wolfe pgplFta24PXlv.pgp Description: PGP signature
Re: Is this still valid?
On Thursday 29 August 2002 05:08, Ola Lundqvist wrote: > Hi > > I just wonder if this lintian error is still applicable? > > > Or should I simply ignore it. > > I think that it is due to the /usr/doc /usr/share/doc thing but I'm > not sure. > I never saw this get pushed into policy, joeyh just decided to stop doing it in debhelper.
Re: Is lintian stalled? [Re: Is this still valid?]
On Thursday 29 August 2002 05:14, Jérôme Marant wrote: > On Thu, Aug 29, 2002 at 02:14:12PM +0200, Josip Rodin wrote: > > > Or should I simply ignore it. > > > > You should, for the time being, until Lintian is fixed. > > It seems that Lintian hasn't been updated for a long time now. > However, Sean seems to be responsive in the BTS. > > Sean, are there any plans to update Lintian? > > Thanks. Yes, I am trying to finish up a project so I can devote a good deal of time to lintian. I know it needs it. I hope to be working on lintian by the end of next week. I should have breathing room then.
Re: The harden-*flaws packages.
Hi On Thu, Aug 29, 2002 at 01:39:35PM +0100, Colin Watson wrote: > On Thu, Aug 29, 2002 at 02:35:13PM +0200, Ola Lundqvist wrote: > > I'm the maintainer of the harden-*flaws packages. The idea is to > > have conflicts with packages that are known to have security holes. > > This is not a big problem for unstable (and mostly for testing) > > but now woody have become stable. > > > > So I now ask you what you think. Should I upload updated conflicts > > for woody or should I just let it be as is (the packages are > > then quite useless in woody). Or should I upload new ones. With > > which priority and for what distribution name? "woody-proposed-updates", > > "woody", "woody-security-updates" or what? > > I'm not honestly sure why it helps. Surely in order to see the new > harden-*flaws packages, people will have to update, and at that point > they will see the new packages anyway? I don't understand why somebody > would upgrade harden-*flaws and not the security updates themselves. As Well there is one reason why you could like this (and one of the reasons why I wrote them) and that is if you have a own package repository or a repository that is not a official site. You do probably not want to upgrade everything (if you have such a system) so to check with the *flaws package can be a good thing. > far as I can tell, harden-*flaws is only useful for security holes for > which no fix is available. That is a reason too. I have almost never got any information about any bug that is not fixed. It happens but is not very common. But of course stable should remain stable and this kind of uploads are not very critical (or?). Regards, // Ola > -- > Colin Watson [EMAIL PROTECTED] > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- - Ola Lundqvist --- / [EMAIL PROTECTED] Björnkärrsgatan 5 A.11 \ | [EMAIL PROTECTED] 584 36 LINKÖPING | | +46 (0)13-17 69 83 +46 (0)70-332 1551 | | http://www.opal.dhs.org UIN/icq: 4912500 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / ---
Re: [Mark.Martinec@ijs.si: Re: perl 5.8 breaks amavis]
On Thu, Aug 29, 2002 at 12:00:41PM +0200, Marcelo E. Magallon wrote: > Looking at the dependency line, yes, that seems to be the case. My > guess is the reporter performed a dist-upgrade and that removed the > libunix-syslog-perl package. Something like that.. My mail was bouncing for about 8 hours because of a broken locally-installed amavis. :-( Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Re: The harden-*flaws packages.
On Thu, Aug 29, 2002 at 02:35:13PM +0200, Ola Lundqvist wrote: > I'm the maintainer of the harden-*flaws packages. The idea is to > have conflicts with packages that are known to have security holes. > This is not a big problem for unstable (and mostly for testing) > but now woody have become stable. > > So I now ask you what you think. Should I upload updated conflicts > for woody or should I just let it be as is (the packages are > then quite useless in woody). Or should I upload new ones. With > which priority and for what distribution name? "woody-proposed-updates", > "woody", "woody-security-updates" or what? I'm not honestly sure why it helps. Surely in order to see the new harden-*flaws packages, people will have to update, and at that point they will see the new packages anyway? I don't understand why somebody would upgrade harden-*flaws and not the security updates themselves. As far as I can tell, harden-*flaws is only useful for security holes for which no fix is available. -- Colin Watson [EMAIL PROTECTED]
The harden-*flaws packages.
Hi I'm the maintainer of the harden-*flaws packages. The idea is to have conflicts with packages that are known to have security holes. This is not a big problem for unstable (and mostly for testing) but now woody have become stable. So I now ask you what you think. Should I upload updated conflicts for woody or should I just let it be as is (the packages are then quite useless in woody). Or should I upload new ones. With which priority and for what distribution name? "woody-proposed-updates", "woody", "woody-security-updates" or what? It would be great if this could be updated along with new DSA:s being released (yes I can hopefully help with this) but it also means that I have to move the CVS for the package (and possibly split it to a flaw-related and a non-flaw-related source package. I have prepared new harden packages (for woody, the sid ones is of course already uploaded) with a updated conflict list (mostly based on the DSA:s) that I could upload anytime. But first I have to ask if this is ok. The woody version differs some from the unstable version because of the fact that different versions is applicable and different version was fixed. Regards, // Ola -- - Ola Lundqvist --- / [EMAIL PROTECTED] Björnkärrsgatan 5 A.11 \ | [EMAIL PROTECTED] 584 36 LINKÖPING | | +46 (0)13-17 69 83 +46 (0)70-332 1551 | | http://www.opal.dhs.org UIN/icq: 4912500 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / ---
Re: perl 5.8 breaks autoconf 2.5
On Thu, Aug 29, 2002 at 12:23:06PM +0200, Marek Habersack wrote: > On Thu, Aug 29, 2002 at 11:16:53AM +0100, Colin Watson scribbled: > > $ dlocate bytes.pm > > perl-modules: /usr/share/perl/5.8.0/bytes.pm > > $ dpkg -l perl-modules | grep ^ii > > ii perl-modules 5.8.0-8Core Perl modules. > > [EMAIL PROTECTED]:~$ dpkg -l perl-modules | grep ^ii > ii perl-modules 5.8.0-9 Core > Perl modules. > [EMAIL PROTECTED]:~$ dpkg -L perl-modules | grep bytes.pm > [EMAIL PROTECTED]:~$ Ah, it's moved to perl-base as of 5.8.0-9, but that's currently only in the archive for sparc. Maybe this should be accounted for in perl-modules' dependencies somehow? They currently only demand perl (>= 5.8.0-1). -- Colin Watson [EMAIL PROTECTED]
Is lintian stalled? [Re: Is this still valid?]
On Thu, Aug 29, 2002 at 02:14:12PM +0200, Josip Rodin wrote: > > Or should I simply ignore it. > > You should, for the time being, until Lintian is fixed. It seems that Lintian hasn't been updated for a long time now. However, Sean seems to be responsive in the BTS. Sean, are there any plans to update Lintian? Thanks. -- Jérôme Marant
Re: Is this still valid?
No. Ignore it. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
Re: Is this still valid?
On Thu, Aug 29, 2002 at 02:08:53PM +0200, Ola Lundqvist wrote: > Hi > > I just wonder if this lintian error is still applicable? > > W: harden-tools: prerm-does-not-remove-usr-doc-link > W: harden-tools: postinst-does-not-set-usr-doc-link No, for new distros it's not. > Or should I simply ignore it. You should, for the time being, until Lintian is fixed. > I think that it is due to the /usr/doc /usr/share/doc thing but I'm > not sure. Yes. -- 2. That which causes joy or happiness.
Is this still valid?
Hi I just wonder if this lintian error is still applicable? W: harden-tools: prerm-does-not-remove-usr-doc-link N: N: The technical committee chose the symlink transition method to move N: from FSSTND to FHS. This transition involves setting the link in the N: postinst script and removing it in the prerm script. Here is an N: example (/bin/sh): N:if [ \( "$1" = "upgrade" -o "$1" = "remove" \) -a -L /usr/doc/pkg ]; then N: rm -f /usr/doc/pkg N:fi N: The test for this is not perfect. If you are setting the link, please N: send the line of code to us so we can improve the test. N: W: harden-tools: postinst-does-not-set-usr-doc-link N: N: The technical committee chose the symlink transition method to move N: from FSSTND to FHS. This transition involves setting the link in the N: postinst script and removing it in the prerm script. Here is an N: example (/bin/sh): N:if [ "$1" = "configure" ]; then N: if [ -d /usr/doc -a ! -e /usr/doc/pkg -a -d /usr/share/doc/pkg ]; then N: ln -sf ../share/doc/pkg /usr/doc/pkg N: fi N:fi N: The test for this is not perfect. If you are setting the link, please N: send the line of code to us so we can improve the test. Or should I simply ignore it. I think that it is due to the /usr/doc /usr/share/doc thing but I'm not sure. Regards, // Ola -- - Ola Lundqvist --- / [EMAIL PROTECTED] Björnkärrsgatan 5 A.11 \ | [EMAIL PROTECTED] 584 36 LINKÖPING | | +46 (0)13-17 69 83 +46 (0)70-332 1551 | | http://www.opal.dhs.org UIN/icq: 4912500 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / ---
Re: [Mark.Martinec@ijs.si: Re: perl 5.8 breaks amavis]
"Marcelo E. Magallon" <[EMAIL PROTECTED]> writes: > >> Brian May <[EMAIL PROTECTED]> writes: > > > I don't have an unstable system handy... > > > > So can anybody tell if if perl 5.8 has Unix::Syslog? > > > > Do I need to add an extra depends or something to amavis? > > Uhm... > > http://makeashorterlink.com/?N240364A1 > > Unix::Syslog wasn't part of the perl package even for 5.6.1. Looks > like libunix-syslog-perl need to be recompiled for 5.8. Unix::Syslog is not really necessary since Sys::Syslog (which comes with Perl) provides the same functionality with a very similar interface. -Hilko
Re: perl 5.8 breaks autoconf 2.5
On Thu, Aug 29, 2002 at 11:16:53AM +0100, Colin Watson scribbled: > On Thu, Aug 29, 2002 at 12:10:41PM +0200, Marek Habersack wrote: > > perl-base contains Data/Dumper.pm, that in turn wants to use bytes.pm > > which used to be in perl-modules for perl 5.6 - it doesn't exists in > > perl-modules for 5.8. > > $ dlocate bytes.pm > perl-modules: /usr/share/perl/5.8.0/bytes.pm > $ dpkg -l perl-modules | grep ^ii > ii perl-modules 5.8.0-8Core Perl modules. [EMAIL PROTECTED]:~$ dpkg -l perl-modules | grep ^ii ii perl-modules 5.8.0-9 Core Perl modules. [EMAIL PROTECTED]:~$ dpkg -L perl-modules | grep bytes.pm [EMAIL PROTECTED]:~$ > > Dumper is used by autom4te in autoconf 2.53 - can anybody _please_ fix > > it? > > Works for me, even when forcing it to encounter the piece of code that > does 'use bytes;': Doesn't work for me, sorry... marek pgpHbRBxzR1ji.pgp Description: PGP signature
Re: perl 5.8 breaks autoconf 2.5
On Thu, Aug 29, 2002 at 12:10:41PM +0200, Marek Habersack wrote: > perl-base contains Data/Dumper.pm, that in turn wants to use bytes.pm > which used to be in perl-modules for perl 5.6 - it doesn't exists in > perl-modules for 5.8. $ dlocate bytes.pm perl-modules: /usr/share/perl/5.8.0/bytes.pm $ dpkg -l perl-modules | grep ^ii ii perl-modules 5.8.0-8Core Perl modules. > Dumper is used by autom4te in autoconf 2.53 - can anybody _please_ fix > it? Works for me, even when forcing it to encounter the piece of code that does 'use bytes;': $ perl -MData::Dumper -e '$Data::Dumper::Useqq = 1; print Dumper($^X)' $VAR1 = "/usr/bin/perl"; -- Colin Watson [EMAIL PROTECTED]
perl 5.8 breaks autoconf 2.5
Hello *, perl-base contains Data/Dumper.pm, that in turn wants to use bytes.pm which used to be in perl-modules for perl 5.6 - it doesn't exists in perl-modules for 5.8. Dumper is used by autom4te in autoconf 2.53 - can anybody _please_ fix it? TIA, marek pgpZqS5XXntrp.pgp Description: PGP signature
Re: [Mark.Martinec@ijs.si: Re: perl 5.8 breaks amavis]
On Thu, Aug 29, 2002 at 07:51:20PM +1000, Brian May wrote: > > Unix::Syslog wasn't part of the perl package even for 5.6.1. Looks > > like libunix-syslog-perl need to be recompiled for 5.8. > > I take it that my package is OK then because it depends on > libunix-syslog-perl? Looking at the dependency line, yes, that seems to be the case. My guess is the reporter performed a dist-upgrade and that removed the libunix-syslog-perl package. Marcelo, wondering why amavis is in contrib...
Re: [Mark.Martinec@ijs.si: Re: perl 5.8 breaks amavis]
On Thu, Aug 29, 2002 at 10:34:04AM +0200, Marcelo E. Magallon wrote: > Uhm... > > http://makeashorterlink.com/?N240364A1 > > Unix::Syslog wasn't part of the perl package even for 5.6.1. Looks > like libunix-syslog-perl need to be recompiled for 5.8. I take it that my package is OK then because it depends on libunix-syslog-perl? -- Brian May <[EMAIL PROTECTED]>
Re: Bug#158683: ITP: oggasm -- MP3 to Ogg converter
Craig Dickson <[EMAIL PROTECTED]> writes: > Robert Millan wrote: > > > * Package name: oggasm > > Upstream: Sean Kellogg <[EMAIL PROTECTED]> > > * URL : http://oggasm.sourceforge.net/ > > * License : GPL > > Description : MP3 to Ogg converter > > > > I'm not the ITPer, Sean Kellogg <[EMAIL PROTECTED]> packaged > > orgasm but haven't moved to include it in debian. I'm contacting him. > > Funny you should bring this up today; we've just been debating an ITP > of another mp3->vorbis converter, with several of us arguing that > such programs are > > 1) a bad idea because converting mp3 to vorbis creates bad-quality >vorbis files full of mp3 artifacts; > > and > > 2) unnecessary, because the conversion is trivial. > oggasm also tags the .ogg files based on the MP3 tags and/or filename, so this is not *that* trivial. Regards, Andy -- Andreas Rottmann | [EMAIL PROTECTED]| [EMAIL PROTECTED] | [EMAIL PROTECTED] http://www.8ung.at/rotty | GnuPG Key: http://www.8ung.at/rotty/gpg.asc Fingerprint | DFB4 4EB4 78A4 5EEE 6219 F228 F92F CFC5 01FD 5B62
Re: [Mark.Martinec@ijs.si: Re: perl 5.8 breaks amavis]
On Thu, Aug 29, 2002 at 10:34:04AM +0200, Marcelo E. Magallon wrote: > >> Brian May <[EMAIL PROTECTED]> writes: > > I don't have an unstable system handy... > > > > So can anybody tell if if perl 5.8 has Unix::Syslog? > > > > Do I need to add an extra depends or something to amavis? > > Uhm... > > http://makeashorterlink.com/?N240364A1 > > Unix::Syslog wasn't part of the perl package even for 5.6.1. Looks > like libunix-syslog-perl need to be recompiled for 5.8. Is Graeme Mathieson around? (He's a sponsored maintainer, so there's no "last seen" information in the database.) He has two other packages which also need rebuilt for perl 5.8. If need be I can supply either sponsorship or NMUs. -- Colin Watson [EMAIL PROTECTED]
Re: Bug#158683: ITP: oggasm -- MP3 to Ogg converter
On Thu, Aug 29, 2002 at 12:34:35AM +0200, Robert Millan wrote: > Package: wnpp > Version: N/A; reported 2002-08-29 > Severity: wishlist > > * Package name: oggasm > Upstream: Sean Kellogg <[EMAIL PROTECTED]> > * URL : http://oggasm.sourceforge.net/ > * License : GPL > Description : MP3 to Ogg converter > > I'm not the ITPer, Sean Kellogg <[EMAIL PROTECTED]> packaged > orgasm but haven't moved to include it in debian. I'm contacting him. ^ Nice Freudian slip there ;) -- 2. That which causes joy or happiness.
Re: [Mark.Martinec@ijs.si: Re: perl 5.8 breaks amavis]
>> Brian May <[EMAIL PROTECTED]> writes: > I don't have an unstable system handy... > > So can anybody tell if if perl 5.8 has Unix::Syslog? > > Do I need to add an extra depends or something to amavis? Uhm... http://makeashorterlink.com/?N240364A1 Unix::Syslog wasn't part of the perl package even for 5.6.1. Looks like libunix-syslog-perl need to be recompiled for 5.8. -- Marcelo | "Not a man to mince words. People, yes. But not words." [EMAIL PROTECTED] | -- (Terry Pratchett, Small Gods)
Please compile treetool on alpha, arm, hppa, ia64, powerpc and s390
Hello, unfortunately treetool is non-free because there is neigther a license nor any upstream author available. However, several people showed interest in treetool and so I wan care for this package. It had a bug on alpha architecture on it which is removed from the BTS because it was fixed in an i386 upload (see changelog). Unfortunately it is not compiled for this very architecture: auric:~> madison treetool treetool |2.0.2-1 | oldstable | source, alpha, arm, i386, powerpc, sparc treetool | 2.0.2a-1 |stable | source, alpha, arm, hppa, i386, ia64, m68k, powerpc, s390, sparc treetool | 2.0.2a-1 | testing | source, alpha, arm, hppa, i386, ia64, m68k, powerpc, s390, sparc treetool | 2.0.2a-1 | unstable | alpha, arm, hppa, ia64, powerpc, s390, sparc treetool | 2.0.2a-2 | unstable | source, i386, m68k I copied a binary for sparc to incomming right now but I hope that the other architectures could be builded soon. This raises again the need for a positive list for autobuilders to process packages from non-free. Kind regards Andreas.
[Mark.Martinec@ijs.si: Re: perl 5.8 breaks amavis]
I don't have an unstable system handy... So can anybody tell if if perl 5.8 has Unix::Syslog? Do I need to add an extra depends or something to amavis? -- Brian May <[EMAIL PROTECTED]> --- Begin Message --- | CCed to Mark, the author. Thanks Brian. | > I discovered the hard way that perl 5.8 breaks amavis.. amavis uses | > UNIX::Syslog but it seems to have been renamed Sys:Syslog in 5.8. | | This could be a problem, unless it is possible to make the same | code work under perl 5.6 too... | | (I don't particularly want to upgrade all my machines to Debian unstable | just yet...) | | Then again, there appears to be a Sys::Syslog in perl 5.6.1, so | maybe this won't be so much a problem after all. These are two similar but quite different Perl modules to implement access to syslog, and they are not compatible. amavisd (all branches) use Unix::Syslog, not Sys::Syslog (check man pages for both modules to see the rationale). I have both modules in my perl 5.6.1, as well as in my Perl 5.8.0. Just straight install from CPAN I believe. | > Thus my mail has been bouncing for the last 8 hours. Ouch. | Ouch. I have had mail queued when there is a problem, never been | unlucky enough to have had it bounce though... The Perl 5.8.0 installation here was done by somebody else, so I do not know if he had problems installing Unix::Syslog. When the machine was handed to me it was able to run the same amavisd-new as my 5.6.1, no tweaking needed. My guess is you just need to install Unix::Syslog. Regards Mark --- End Message ---
Re: bugs.debian.org: ChangeLog closes handling should be changed
On Tue, Aug 27, 2002 at 08:48:31AM +0200, Gerfried Fuchs wrote: > What we need is a change here: Bugs should just be closed in unstable. > How to do this? They should be rather be tagged than be closed > by an upload to unstable. Not unconditionally, of course. The version > of the bugreport should be compared with the version currently in > testing. Some sort of algorithm not too complex but able to handle most > of the cases shouldn't be too hard to do (yes, I volunteer to help > there). Then bugs will me marked as sarge, even though they might be bugs specific to unstable. It would be much better to remove the sid tag when it gets uploaded to unstable, turn off the sarge tag when it goes into testing, and turn of the woody tag if it is lucky enough to get into stable. (of course this assumes that the tags were already set, preferably when the bug is first reported) PS. Please look at http://www.debian.org/Bugs/Reporting, and search for "X-Debbugs-CC". -- Brian May <[EMAIL PROTECTED]>
Re: [ANNOUNCE] Debian Developer Packages Overview
On Wed, 28 Aug 2002, Martin Michlmayr wrote: > * Igor Genibel <[EMAIL PROTECTED]> [2002-08-28 17:20]: > > http://qa.debian.org/developer/ > > If you want to have it hosted there, you should really > a) put the files in CVS (module qa), and follow the current standards >for web pages (i.e. have wml files in qa/wml which are build >and then copied to web/) a.1) have your cronjobs in data/cronjobs and the scripts run from it and the data it produces in data// (the extract file for example) > b) give group write permission to the files and chgrp them to qa also make directories g+s please. > c) have a link from the main qa site to them Please also make it clear on each page where each data comes from (Uninstallable for example has no apparent source). Thanks for writing that neat tool. yours, peter -- PGP signed and encrypted | .''`. ** Debian GNU/Linux ** messages preferred.| : :' : The universal | `. `' Operating System http://www.palfrader.org/ | `-http://www.debian.org/ pgp4Qtd5h3xka.pgp Description: PGP signature
Using tftp
Hi all, I am trying to install Debian through TFTP because I can't afford the IBM docking station. I set all the things up. But my computer tell me "TFTP too many packages". I guess the TFTP image has problem. I tried to use program "bc" to translate the tftp image to "client-ip-in-hexcient-architecture"( at least this is the words on the Debian 3.0 installation guide). Does somebody know how to use the program? Or maybe you have some other good ways. Thank you for all your help! River
Re: Migration to /usr/share/doc
On Mon, 2002-08-26 at 23:11, Giorgio Mandolfo wrote: ... > I am trying not to use exclusively the simbolic link to /usr/share/doc/ > but to look directly to the new folder. Well, I there is a (very) > simple and boring fact: the completion locks because there is > /usr/share/doc-base/ too. > I searched for some explanations about it in the Debian Policy, even if > its name is self-explanatory. I did not find anything. > Couri > So my questions/proposals are: > - Why this directory exists? And what is it about? It contains control files for the doc-base package. See /usr/share/doc/doc-base/doc-base.html/index.html > - Is it possible to move their contents to /usr/share/doc/ allowing a > faster search through the filesystem? No. The files in /usr/share/doc-base/ are not documentation and do not belong in /usr/share/doc/ -- Oliver Elphick[EMAIL PROTECTED] Isle of Wight, UK http://www.lfix.co.uk/oliver GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C "Preach the word; be instant in season, out of season; reprove, rebuke, exhort with all longsuffering and doctrine." II Timothy 4:2
Re: fpm - password manager
On Thu, 2002-08-29 at 00:34, Brian May wrote: > * There is an important bug against fpm, where it can currupt user > data, if the user does certain operations in a particular order. > Bug #158016. Actually it's #144895, #158016 is "~/.gpasman not imported on first run"
