Re: [aspell-it] introduzione del dizionario friulano nel pacchetto
On Tue, Oct 17, 2006 at 03:36:12PM +0200, Stefano Melchior wrote: dizionario friulano, nè quello sardo, nè qualsivoglia altro dizionario, si può pensare ad un pacchetto a parte che dipende da aspell-it. In fin dei conti è come se si installasse un dizionario secondario. Può essere una soluzione logica, ammesso che sia fattibile o che non ci siano problemi di natura tecnica o di licenze? Io sono assolutamente per metterli, ma possibilmente in un pacchetto diverso da aspell-it. Un pacchetto per tutti i vari dizionari regionali per me andrebbe benissimo. Ciao, Enrico -- GPG key: 1024D/797EBFAB 2000-12-05 Enrico Zini [EMAIL PROTECTED]
Problems in PMDF Mailserv V6.1 command processing
Error in the command: The original message was received at Thu, 19 Oct 2006 14:05:57 +0600 from 177.180.128.188 Unrecognized command verb: THE Subsequent commands ignored because of previous error. Ignored: - The following addresses had permanent fatal errors - Ignored: [EMAIL PROTECTED] Use the HELP command to get a list of legal MAILSERV commands. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Fwd: How can the OS autodetect that a user is a newbie and offer help?
On Wed, Oct 18, 2006 at 10:26:26AM -0200, Yves Junqueira wrote: It may be much cleaner to include help links /etc/motd, adivising the user to read a hipothetical /usr/share/doc/linux-beginners/new-users, or enter a help-mode by typing a certain command. Or we could mimic FreeBSD behaviour: create a fortune-file with helpful tips for newbies, and add a line in the default initialization files (i.e., those in /etc/skel) for different shells that calls fortune for those tips. -- Lo-lan-do Home is where you have to wash the dishes. -- #debian-devel, Freenode, 2004-09-22 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Fwd: How can the OS autodetect that a user is a newbie and offer help?
Wouter Verhelst wrote: Or we could mimic FreeBSD behaviour: create a fortune-file with helpful tips for newbies, and add a line in the default initialization files (i.e., those in /etc/skel) for different shells that calls fortune for those tips. You mean like fortunes-debian-hints[1]? Kind regards T. 1. http://packages.debian.org/fortunes-debian-hints -- Thomas Viehmann, http://thomas.viehmann.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
New source package
Hi, I have developed some new software, an audioscrobbler client for last.fm, which I would like to see included, probably under Multimedia. It consists of two simple C source files - how do I go about getting it included in Debian? Cheers, David. [EMAIL PROTECTED] -- http://dmctek.googlepages.com
Re: Fwd: How can the OS autodetect that a user is a newbie and offer help?
On Thu, Oct 19, 2006 at 10:58:42AM +0200, Thomas Viehmann wrote: Wouter Verhelst wrote: Or we could mimic FreeBSD behaviour: create a fortune-file with helpful tips for newbies, and add a line in the default initialization files (i.e., those in /etc/skel) for different shells that calls fortune for those tips. You mean like fortunes-debian-hints[1]? Probably. So all that is left now is make sure it gets in the default .bashrc -- Lo-lan-do Home is where you have to wash the dishes. -- #debian-devel, Freenode, 2004-09-22 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New source package
On Thu, Oct 19, 2006 at 09:47:10AM +0100, David Moore wrote: Hi, I have developed some new software, an audioscrobbler client for last.fm, which I would like to see included, probably under Multimedia. It consists of two simple C source files - how do I go about getting it included in Debian? Two options: * File an RFP (reportbug wnpp) and hope someone will package it for you. * Read the documentation on how to package something, and try to find a sponsor who will upload it for you. You will have more success on debian-mentors than this mailinglist if you go down that road. -- Lo-lan-do Home is where you have to wash the dishes. -- #debian-devel, Freenode, 2004-09-22 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Fwd: How can the OS autodetect that a user is a newbie and offer help?
#include hallo.h * Thomas Viehmann [Thu, Oct 19 2006, 10:58:42AM]: Wouter Verhelst wrote: Or we could mimic FreeBSD behaviour: create a fortune-file with helpful tips for newbies, and add a line in the default initialization files (i.e., those in /etc/skel) for different shells that calls fortune for those tips. You mean like fortunes-debian-hints[1]? IMO that's a bit too advanced, too administrator/developer specific. I would prefer having a fortunes-newbie-hints which is mixed by fortune, eg. using 90% from newbie-hints and 10% from debian-hints. I would even change that during the runtime, eg. shifting the weights by one percent every day, from newbie-hints to debian-hints. Eduard. -- * Scorpi ist aus dem Amiga-Bereich eher Boards gewöhnt, die man nach dem Rausschrauben nur unter Umgehung physicher Gesetze wieder eingebaut bekommt. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New source package
On Thu, Oct 19, 2006 at 09:47:10AM +0100, David Moore wrote: Hi, I have developed some new software, an audioscrobbler client for _l_a_s_t_._f_m, which I would like to see included, probably under Multimedia. It consists of two simple C source files - how do I go about getting it included in Debian? Cheers, Hi David, In the Debian Bug tracking system, there is a pseudo-package[0] call wnpp[1] that you file a ITP 'bug' (Intent to Package) against which states your intention to create a Debian package. If you are not a Debian Developer, you will need a 'sponsor' for your package. This person will inspect your package for numerous things including trojans, bugs, and Debian policy violation. If its OK, that person will upload it into the 'incoming' server[2] where it will propagate to the 'unstable' branch of Debian. The easiest way to file a wnpp bug is to use the Debian program 'reportbug' for your ITP. Fill in all the required details or it will be rejected. Read the MAN pages for info. You should check out the Debian Developer subsite[3] and start by reading the Debian new maintainers guide[4]. You should also read the Debian developers reference and Debian policy manual for complete detains on how to create a Debian package up to Debian Standards. You can join the debian-mentors list for help with creating a Debian package. Also, when you create your ITP, folks may question the need for the package for various reasons like: are you sure the license is DFSG free? is there already a similar program in Debian? if so, why do we need this one? Could you add it to an existing package, if its a small program? Don't be discouraged if you are asked, as folks want to make sure that software in Debian is not simply a one-line shell script or the 24th version of vi. And if you are really brave and patient, you can join the Debian new maintainer queue and join the ranks as a voting member of Debian. here's to seeing your package in Debian! Kev [0] http://www.debian.org/Bugs/pseudo-packages [1] http://bts.debian.org/wnpp [2] http://incoming.debian.org [3] http://www.debian.org/devel/ [4] http://www.debian.org/doc/maint-guide/ -- | .''`. == Debian GNU/Linux == | my web site: | | : :' : The Universal | debian.home.pipeline.com | | `. `' Operating System| go to counter.li.org and | | `-http://www.debian.org/ |be counted! #238656 | | my keysever: pgp.mit.edu | my NPO: cfsg.org | signature.asc Description: Digital signature
Re: Fwd: How can the OS autodetect that a user is a newbie and offer help?
Em Wed, 18 Oct 2006 10:26:26 -0200 Yves Junqueira [EMAIL PROTECTED] escreveu: It may be much cleaner to include help links /etc/motd, adivising the user to read a hipothetical /usr/share/doc/linux-beginners/new-users, or enter a help-mode by typing a certain command. Much cleaner, but I think newbie users do not really care about command line. Those who care to learn will find one of the tutorials Jason mentioned. Either way, I think it would be a nice thing having motd point to some 'starter guide' tutorial. Here's a nice Progeny contribution that Osamu 'utnubued': http://www.debian.org/doc/manuals/users-guide/users-guide.en.html It's not very translated, granted, but it could become =D See you, -- Gustavo Noronha Silva [EMAIL PROTECTED] http://www.debian.org/ | http://kov.eti.br/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: safe halt/reboot/shutdown
also sprach martin f krafft [EMAIL PROTECTED] [2006.10.17.1618 +0200]:
Thus, unless I get other suggestions, I'll package it up in its
own package, which diverts /sbin/{reboot,halt,shutdown} and puts
my shell script in their place. I'll Enhance whatever init systems
there are and I'll ask them to add Suggests.
http://debian.madduck.net/repo/dists/unstable/main/binary-all/admin/molly-guard_0.1_all.deb
I'll treat this discussion as an ITP and upload directly to NEW
after a few rounds of live tests.
Comments welcome.
--
Please do not send copies of list mail to me; I read the list!
.''`. martin f. krafft [EMAIL PROTECTED]
: :' : proud Debian developer, author, administrator, and user
`. `'` http://people.debian.org/~madduck - http://debiansystem.info
`- Debian - when you have better things to do than fixing systems
windoze is the one-night-stand of operating systems;
you feel so cheap after having used it.
signature.asc
Description: Digital signature (GPG/PGP)
ethstatus: no upstream, RFA or removal?
Dear list... I'm the maintainer of the ethstatus package - a console-based ethernet statistics monitor. You can e.g. run it on your gateway's 9 CRT on the console and see how much bandwidth is currently used in a bar-like view. I'm in the process of RFA'ing the package. But I wonder whether I should even request for this package to get removed. Reasons: (1) No real upstream The former upstream developer - Gabriel Montenegro - has given up development of the package so I accepted to become the intermediate upstream contact in May 2003. I pimped the software a bit, wrote a manpage, fixed the code and copyright. But I did not really intend to stay the upstream developer for all times. After all my C knowledge is not exactly guru like. There is one minor bug filed against the package that I can't reproduce. (2) There are similar packages IMHO iptraf, iftop or nload serve similar purposes. So I wonder if yet another console network monitor is really needed. (3) Few popcon installations Popcon reports 282 installations for ethstatus. iptraf: 2919 installations iftop: 1057 installations nload: 561 installations So I would like to get a few comments before I request its removal. Mainly I'm unhappy with the missing upstream situation. I could also wait for a volunteer to maintain both the software and the maintainer. I'm personally just not that interested in the software any more. Cheers Christoph -- Famous coworker quote: I'm still confused - just on a higher level now. pgpS4ENAMufK0.pgp Description: PGP signature
Bug mass filling
Hi all, I have just run lintian on all the archive (amd64) for both binaries and sources, and the results are a bit scary. It looks like a lot of maintainers are uploading their packages, and don't really care with the policy. Maybe some errors (E:) of lintian could be changed to critical (C:) and uploads containing such critical errors be refused by dak? What do you think? Among all of the bugs reported by lintian, one concerns a lot of packages, the presence of the clean, binary, binary-arch, binary-indep and build targets. This is required by both the section 4.9 of the policy and the Etch release standards [1]. Here is the list of affected packages. What to do with them? E: adeos source: debian-rules-missing-required-target binary-indep E: ale source: debian-rules-missing-required-target binary-indep E: arabtex source: debian-rules-missing-required-target binary-arch E: autoconf source: debian-rules-missing-required-target binary-arch E: babygimp source: debian-rules-missing-required-target binary-arch E: backupninja source: debian-rules-missing-required-target binary-arch E: bamboo source: debian-rules-missing-required-target binary-arch E: bastille source: debian-rules-missing-required-target binary-indep E: bazaar-doc source: debian-rules-missing-required-target binary-indep E: bicyclerepair source: debian-rules-missing-required-target binary-arch E: bitlbee source: debian-rules-missing-required-target binary-indep E: blootbot source: debian-rules-missing-required-target binary-arch E: blootbot source: debian-rules-missing-required-target binary-indep E: boost-build source: debian-rules-missing-required-target binary-arch E: boost-build source: debian-rules-missing-required-target build E: bootcd source: debian-rules-missing-required-target binary-arch E: br2684ctl source: debian-rules-missing-required-target binary-indep E: c-cpp-reference source: debian-rules-missing-required-target build E: c2n source: debian-rules-missing-required-target binary-indep E: cacti source: debian-rules-missing-required-target binary-arch E: camlidl-doc source: debian-rules-missing-required-target binary-arch E: cassbeam source: debian-rules-missing-required-target binary-indep E: check source: debian-rules-missing-required-target binary-indep E: cli-common source: debian-rules-missing-required-target binary-arch E: clips-doc source: debian-rules-missing-required-target build E: coco-cs source: debian-rules-missing-required-target binary-arch E: coco-doc source: debian-rules-missing-required-target binary-arch E: coco-doc source: debian-rules-missing-required-target build E: coco-doc source: debian-rules-missing-required-target clean E: coco-java source: debian-rules-missing-required-target binary-arch E: configure-debian source: debian-rules-missing-required-target binary-arch E: cthumb source: debian-rules-missing-required-target build E: dag2html source: debian-rules-missing-required-target binary-indep E: db4.2 source: debian-rules-missing-required-target binary-indep E: debget source: debian-rules-missing-required-target binary-arch E: debroster source: debian-rules-missing-required-target binary-arch E: dhcp source: debian-rules-missing-required-target binary-indep E: dpkg-ftp source: debian-rules-missing-required-target build E: drbdlinks source: debian-rules-missing-required-target binary-arch E: drgeo-doc source: debian-rules-missing-required-target binary-arch E: dupload source: debian-rules-missing-required-target binary-arch E: dvipng source: debian-rules-missing-required-target binary-indep E: e00compr source: debian-rules-missing-required-target binary-indep E: efp source: debian-rules-missing-required-target binary-arch E: emms source: debian-rules-missing-required-target binary-indep E: enigmail source: debian-rules-missing-required-target build E: fapg source: debian-rules-missing-required-target binary-indep E: fbpanel source: debian-rules-missing-required-target binary-indep E: filler source: debian-rules-missing-required-target binary-arch E: flawfinder source: debian-rules-missing-required-target binary-arch E: flowscan source: debian-rules-missing-required-target binary-arch E: fortunes-ga source: debian-rules-missing-required-target binary-arch E: fortunes-it source: debian-rules-missing-required-target binary-arch E: freeswan source: debian-rules-missing-required-target binary-arch E: freetype1 source: debian-rules-missing-required-target binary-indep E: fv source: debian-rules-missing-required-target binary-indep E: gap-ctbllib source: debian-rules-missing-required-target binary-arch E: gap-matrix-schreiersims source: debian-rules-missing-required-target binary-arch E: gkrellmitime source: debian-rules-missing-required-target binary-indep E: gkrellweather source: debian-rules-missing-required-target binary-indep E: gnoise source: debian-rules-missing-required-target binary-indep E: gnome-lokkit source: debian-rules-missing-required-target binary-indep E: gnucap source:
Re: ethstatus: no upstream, RFA or removal?
Christoph Haas [EMAIL PROTECTED] writes:
I'm unhappy with the missing upstream situation. I could also wait for a
volunteer to maintain both the software and the maintainer.
^^
What kind of maintenance do *you* need?
Matthias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cmake build-depends
Hi all, I maintain the package wormux and my dear upstream devels decided to switch from autotools to cmake, for the best and the worse. Are there people with experiences with it ? Maybe kde packagers are already working on it ? As a side effect, can someone tell me if there is a command to search for packages regarding Build-Depends ? Best regards, Jean -- _ / La théorie est absurde dans la \ | pratique et la pratique est aveugle | \ sans la théorie. -+- Emmanuel Kant -+- / - \ ^__^ \ (--)\___ (__)\ )\/\ ||w | || || -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
[Aurelien Jarno] I have just run lintian on all the archive (amd64) for both binaries and sources, and the results are a bit scary. It looks like a lot of maintainers are uploading their packages, and don't really care with the policy. What is the technical problem triggered by the packages with this lintian message? Is the autobuilders able to build these packages? If the autobuilders fail, I recommend you report that as a important or serious problem, and it it isn't, I recommend you report it as a normal bug. Friendly, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cmake build-depends
On 10/19/06, Jean Parpaillon [EMAIL PROTECTED] wrote: As a side effect, can someone tell me if there is a command to search for packages regarding Build-Depends ? grep-dctrl -sPackage -F Build-Depends,Build-Depends-Indep cmake /var/lib/apt/lists/*Sources Or, see the more elaborate version, by Damián Viano: http://damianv.com.ar/downloads/rbuildepend -- Besos, Marga
Re: Bug mass filling
On 10/19/06, Petter Reinholdtsen [EMAIL PROTECTED] wrote: [Aurelien Jarno] I have just run lintian on all the archive (amd64) for both binaries and sources, and the results are a bit scary. It looks like a lot of maintainers are uploading their packages, and don't really care with the policy. What is the technical problem triggered by the packages with this lintian message? Is the autobuilders able to build these packages? If the autobuilders fail, I recommend you report that as a important or serious problem, and it it isn't, I recommend you report it as a normal bug. Doesn't policy violation warrant Critical severity? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
[Tshepang Lekhonkhobe] Doesn't policy violation warrant Critical severity? Well, policy isn't a stick to beat other maintainers with, it is a tool to make sure our packages are well integrated and work properly. Thus, policy issues are not problems by themselves, they are policy issues because they might cause problems. And in this case, I am not sure what the exact problem caused by the lack of the binary-indep target is, so I ask. If no problem is caused by it, I believe 'normal' or even 'wishlist' severity is the proper severity to use. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
Tshepang Lekhonkhobe wrote: Doesn't policy violation warrant Critical severity? No, it only warrants the lowest RC severity, serious [0], unless the bug in addition makes the package or other software (mostly) unusable, causes data loss, or introduces a security hole. [0] http://www.debian.org/Bugs/Developer#severities regards, -- Kevin B. McCarty [EMAIL PROTECTED] Physics Department WWW: http://www.princeton.edu/~kmccarty/Princeton University GPG: public key ID 4F83C751 Princeton, NJ 08544 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
On Thursday 19 October 2006 18:45, Petter Reinholdtsen wrote: If no problem is caused by it, I believe 'normal' or even 'wishlist' severity is the proper severity to use. s/wishlist/minor/ It _is_ a bug after all. pgp8CuxfBlHbn.pgp Description: PGP signature
Re: Bug mass filling
On Thu, Oct 19, 2006 at 06:45:53PM +0200, Petter Reinholdtsen wrote: Well, policy isn't a stick to beat other maintainers with, it is a tool to make sure our packages are well integrated and work properly. Thus, policy issues are not problems by themselves, they are policy issues because they might cause problems. And in this case, I am not sure what the exact problem caused by the lack of the binary-indep target is, so I ask. If no problem is caused by it, I believe 'normal' or even 'wishlist' severity is the proper severity to use. If there's no problem, change the policy. -- Julien Danjou .''`. Debian Developer : :' : http://julien.danjou.info `. `' http://people.debian.org/~acid `- 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD signature.asc Description: Digital signature
Re: Bug mass filling
* Tshepang Lekhonkhobe ([EMAIL PROTECTED]) [061019 18:09]: On 10/19/06, Petter Reinholdtsen [EMAIL PROTECTED] wrote: [Aurelien Jarno] I have just run lintian on all the archive (amd64) for both binaries and sources, and the results are a bit scary. It looks like a lot of maintainers are uploading their packages, and don't really care with the policy. What is the technical problem triggered by the packages with this lintian message? Is the autobuilders able to build these packages? If the autobuilders fail, I recommend you report that as a important or serious problem, and it it isn't, I recommend you report it as a normal bug. Doesn't policy violation warrant Critical severity? No. Please see the top of http://release.debian.org/etch_rc_policy.txt for which bugs are critical, grave and serious. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
* Aurelien Jarno ([EMAIL PROTECTED]) [061019 15:06]: Among all of the bugs reported by lintian, one concerns a lot of packages, the presence of the clean, binary, binary-arch, binary-indep and build targets. This is required by both the section 4.9 of the policy and the Etch release standards [1]. Here is the list of affected packages. What to do with them? If the bug also affects our autobuilders (especially the package has binary-any-packages), serious. Otherwise, important severity. If a package is totally broken (which might be in this case), serious might also be ok - but that needs to be decided on a case-by-case-basis. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
On Thu, Oct 19, 2006 at 07:36:27PM +0200, Andreas Barth [EMAIL PROTECTED] wrote: Doesn't policy violation warrant Critical severity? No. Please see the top of http://release.debian.org/etch_rc_policy.txt for which bugs are critical, grave and serious. That is irrelevant for the severity of bugs. This is the relevant definition: serious is a severe violation of Debian policy (that is, the problem is a violation of a 'must' or 'required' directive) And in our case, the policy says: Both the binary-arch and binary-indep targets must exist. Don't change severities for releasing-in-time purposes. There is etch-ignore for that. Mike, wondering how many RC bugs will be tagged etch-ignore to reach the 80 bugs before freeze. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
On Thu, Oct 19, 2006 at 07:01:20PM +0200, Frans Pop wrote: On Thursday 19 October 2006 18:45, Petter Reinholdtsen wrote: If no problem is caused by it, I believe 'normal' or even 'wishlist' severity is the proper severity to use. s/wishlist/minor/ It _is_ a bug after all. s/minor/important/, which is the severity used for policy violations that don't qualify as release-critical. And in this case, yes, the bugs should be filed as important rather than serious; the etch RC policy claims they should be serious, but it also does this in the section on autobuilding -- if no one has found any problems autobuilding these packages before now, despite multiple full-archive rebuilds over the past year, then it's a bug in the etch RC policy to suggest that these should be RC when they don't cause practical problems. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
On Thu, 2006-10-19 at 19:51 +0200, Mike Hommey wrote: On Thu, Oct 19, 2006 at 07:36:27PM +0200, Andreas Barth [EMAIL PROTECTED] wrote: Doesn't policy violation warrant Critical severity? No. Please see the top of http://release.debian.org/etch_rc_policy.txt for which bugs are critical, grave and serious. That is irrelevant for the severity of bugs. [...] Don't change severities for releasing-in-time purposes. There is Erm... the release team have been the arbiters of what merits an RC severity since at least before Sarge was released. From http://www.debian.org/Bugs/Developer#severities: Certain severities are considered release-critical, meaning the bug will have an impact on releasing the package with the stable release of Debian. Currently, these are critical, grave and serious. For complete and canonical rules on what issues merit these severities, see the list of Release-Critical Issues for Etch. The top of the latter page reads The purpose of this document is to be a correct, complete and canonical list of issues that merit a serious bug under the clause a severe violation of Debian policy. In addition to the issues listed in this document, an issue is release critical if it: [...] * in the maintainer's opinion, makes the package unsuitable for release (these issues are serious severity) i.e. if it's not in the policy and doesn't meet the above definition, it's *not* severity serious or higher. I'd suggest reading http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=277074;msg=72, in which a current member of [EMAIL PROTECTED] (and at the time an RM) confirms that a member of the ftp-master team was correct in stating the above. Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
On Thu, 2006-10-19 at 10:00 -0700, Kevin B. McCarty wrote: Tshepang Lekhonkhobe wrote: Doesn't policy violation warrant Critical severity? No, it only warrants the lowest RC severity, serious [0], unless the bug in addition makes the package or other software (mostly) unusable, causes data loss, or introduces a security hole. Even then, it's only serious if it violates the release policy [http://release.debian.org/etch_rc_policy.txt]. Hence the reason that [0] http://www.debian.org/Bugs/Developer#severities says [...]roughly, it violates a must or required directive. The final word for what justifies a release-critical severity belongs to the release team (hence also the paragraph on rc-ness at the foot of the documentation). Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
On Thu, Oct 19, 2006 at 07:51:19PM +0200, Mike Hommey wrote: On Thu, Oct 19, 2006 at 07:36:27PM +0200, Andreas Barth [EMAIL PROTECTED] wrote: Doesn't policy violation warrant Critical severity? No. Please see the top of http://release.debian.org/etch_rc_policy.txt for which bugs are critical, grave and serious. That is irrelevant for the severity of bugs. This is the relevant definition: serious is a severe violation of Debian policy (that is, the problem is a violation of a 'must' or 'required' directive) That definition, as listed on http://www.us.debian.org/Bugs/Developer#severities, links straight to the release team's RC bug policy. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
On Thu, Oct 19, 2006 at 11:29:38AM -0700, Steve Langasek [EMAIL PROTECTED] wrote: On Thu, Oct 19, 2006 at 07:51:19PM +0200, Mike Hommey wrote: On Thu, Oct 19, 2006 at 07:36:27PM +0200, Andreas Barth [EMAIL PROTECTED] wrote: Doesn't policy violation warrant Critical severity? No. Please see the top of http://release.debian.org/etch_rc_policy.txt for which bugs are critical, grave and serious. That is irrelevant for the severity of bugs. This is the relevant definition: serious is a severe violation of Debian policy (that is, the problem is a violation of a 'must' or 'required' directive) That definition, as listed on http://www.us.debian.org/Bugs/Developer#severities, links straight to the release team's RC bug policy. Note how subtly the Etch RC policy removes the first alternative of the serious bug description... Anyways, I've always thought the bts severity levels and release criticality were orthogonal things. i.e. it's more complicated than just saying critical, grave and serious levels are RC. There are important or even normal issues (as per definition of the severity levels) that are more release critical than serious (again, as per definition of the severity levels) bugs. But yet, violation of the Debian policy should be granted serious level. etch-ignore is here to make the issue not release critical. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
* Mike Hommey ([EMAIL PROTECTED]) [061019 20:42]: Note how subtly the Etch RC policy removes the first alternative of the serious bug description... Which do you mean? Please read the Etch RC policy. It tells: | In addition to the issues listed in this document, an issue is release | critical if it: | [...] | * in the maintainer's opinion, makes the package unsuitable | for release So, what does the Etch RC policy remove from the bugs.d.o description? Anyways, I've always thought the bts severity levels and release criticality were orthogonal things. i.e. it's more complicated than just saying critical, grave and serious levels are RC. That is wrong. There are important or even normal issues (as per definition of the severity levels) that are more release critical than serious (again, as per definition of the severity levels) bugs. Wrong. A bug is release-critical := the bug has severity serious, grave, critical and has not been given an excemption by the release team But yet, violation of the Debian policy should be granted serious level. etch-ignore is here to make the issue not release critical. Wrong. Etch-ignore is for exemptions for issues that otherwise match the definition of release critical on that page. It is not for normal sorting of issues. A violation of the parts of the debian policy as listed on http://release.debian.org/etch_rc_policy.txt is serious level (that should be the same as the must-directives in policy, but - well, I hope that I have finally time post-etch to sync that finally). Any other policy violation is at most important level (unless it conincides with one of the other criteria for RC bugs, of course). Cheers, Andi Debian Release Manager -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
On Thu, Oct 19, 2006 at 09:06:42PM +0200, Andreas Barth [EMAIL PROTECTED] wrote: * Mike Hommey ([EMAIL PROTECTED]) [061019 20:42]: Note how subtly the Etch RC policy removes the first alternative of the serious bug description... Which do you mean? Please read the Etch RC policy. It tells: | In addition to the issues listed in this document, an issue is release | critical if it: | [...] | * in the maintainer's opinion, makes the package unsuitable | for release So, what does the Etch RC policy remove from the bugs.d.o description? 'is a severe violation of Debian policy (roughly, it violates a must or required directive), or' Anyways, I've always thought the bts severity levels and release criticality were orthogonal things. i.e. it's more complicated than just saying critical, grave and serious levels are RC. That is wrong. There are important or even normal issues (as per definition of the severity levels) that are more release critical than serious (again, as per definition of the severity levels) bugs. Wrong. A bug is release-critical := the bug has severity serious, grave, critical and has not been given an excemption by the release team You may have missed the thought part of the sentence. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
* Mike Hommey ([EMAIL PROTECTED]) [061019 21:14]: On Thu, Oct 19, 2006 at 09:06:42PM +0200, Andreas Barth [EMAIL PROTECTED] wrote: * Mike Hommey ([EMAIL PROTECTED]) [061019 20:42]: Note how subtly the Etch RC policy removes the first alternative of the serious bug description... Which do you mean? Please read the Etch RC policy. It tells: | In addition to the issues listed in this document, an issue is release | critical if it: | [...] | * in the maintainer's opinion, makes the package unsuitable | for release So, what does the Etch RC policy remove from the bugs.d.o description? 'is a severe violation of Debian policy (roughly, it violates a must or required directive), or' The html-code for this part is: DTCODEserious/CODE DDis a a href=http://release.debian.org/etch_rc_policy.txt;severe violation of Debian policy/a (roughly, it violates a must or required directive), or, in the package maintainer's opinion, makes the package unsuitable for release. So, obviously http://www.debian.org/Bugs/Developer#severities defines that severe violation of Debian policy means anything referenced in the etch_rc_policy-document. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
On Thu, Oct 19, 2006 at 09:17:38PM +0200, Andreas Barth [EMAIL PROTECTED] wrote: * Mike Hommey ([EMAIL PROTECTED]) [061019 21:14]: On Thu, Oct 19, 2006 at 09:06:42PM +0200, Andreas Barth [EMAIL PROTECTED] wrote: * Mike Hommey ([EMAIL PROTECTED]) [061019 20:42]: Note how subtly the Etch RC policy removes the first alternative of the serious bug description... Which do you mean? Please read the Etch RC policy. It tells: | In addition to the issues listed in this document, an issue is release | critical if it: | [...] | * in the maintainer's opinion, makes the package unsuitable | for release So, what does the Etch RC policy remove from the bugs.d.o description? 'is a severe violation of Debian policy (roughly, it violates a must or required directive), or' The html-code for this part is: DTCODEserious/CODE DDis a a href=http://release.debian.org/etch_rc_policy.txt;severe violation of Debian policy/a (roughly, it violates a must or required directive), or, in the package maintainer's opinion, makes the package unsuitable for release. So, obviously http://www.debian.org/Bugs/Developer#severities defines that severe violation of Debian policy means anything referenced in the etch_rc_policy-document. Yeah, right, whatever, as soon as etch is release on December 4th... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
Andreas Barth a écrit : A violation of the parts of the debian policy as listed on http://release.debian.org/etch_rc_policy.txt is serious level (that should be the same as the must-directives in policy, but - well, I hope that I have finally time post-etch to sync that finally). Any other policy violation is at most important level (unless it conincides with one of the other criteria for RC bugs, of course). Note that what we are discussing (must have in targets debian/rules) are listed on http://release.debian.org/etch_rc_policy.txt -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
* Mike Hommey ([EMAIL PROTECTED]) [061019 21:25]: On Thu, Oct 19, 2006 at 09:17:38PM +0200, Andreas Barth [EMAIL PROTECTED] wrote: * Mike Hommey ([EMAIL PROTECTED]) [061019 21:14]: On Thu, Oct 19, 2006 at 09:06:42PM +0200, Andreas Barth [EMAIL PROTECTED] wrote: * Mike Hommey ([EMAIL PROTECTED]) [061019 20:42]: Note how subtly the Etch RC policy removes the first alternative of the serious bug description... Which do you mean? Please read the Etch RC policy. It tells: | In addition to the issues listed in this document, an issue is release | critical if it: | [...] | * in the maintainer's opinion, makes the package unsuitable | for release So, what does the Etch RC policy remove from the bugs.d.o description? 'is a severe violation of Debian policy (roughly, it violates a must or required directive), or' The html-code for this part is: DTCODEserious/CODE DDis a a href=http://release.debian.org/etch_rc_policy.txt;severe violation of Debian policy/a (roughly, it violates a must or required directive), or, in the package maintainer's opinion, makes the package unsuitable for release. So, obviously http://www.debian.org/Bugs/Developer#severities defines that severe violation of Debian policy means anything referenced in the etch_rc_policy-document. Yeah, right, whatever, as soon as etch is release on December 4th... What do you intend to say by that? The definition of serious was already that way when I was looking at the release from the very outside, before I was a DD even (ok, it was sarge_rc_policy.txt, and not etch at that time). It has *nothing* whatsoever to do with the planned release date ... But I need to admit that I get sick, seriously sick. If someone doesn't agree with something, he just says you do it wrong just for release of etch on $date. I really hate that. Especially when it's about things that are done that way since ages, but someone just recently has become aware of that. That really takes the fun away from Debian for me. I don't know if that's what you intend, but that's what you achieve. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
* Andreas Barth ([EMAIL PROTECTED]) wrote: * Mike Hommey ([EMAIL PROTECTED]) [061019 21:14]: On Thu, Oct 19, 2006 at 09:06:42PM +0200, Andreas Barth [EMAIL PROTECTED] wrote: * Mike Hommey ([EMAIL PROTECTED]) [061019 20:42]: Note how subtly the Etch RC policy removes the first alternative of the serious bug description... Which do you mean? Please read the Etch RC policy. It tells: | In addition to the issues listed in this document, an issue is release | critical if it: | [...] | * in the maintainer's opinion, makes the package unsuitable | for release So, what does the Etch RC policy remove from the bugs.d.o description? 'is a severe violation of Debian policy (roughly, it violates a must or required directive), or' The html-code for this part is: DTCODEserious/CODE DDis a a href=http://release.debian.org/etch_rc_policy.txt;severe violation of Debian policy/a (roughly, it violates a must or required directive), or, in the package maintainer's opinion, makes the package unsuitable for release. So, obviously http://www.debian.org/Bugs/Developer#severities defines that severe violation of Debian policy means anything referenced in the etch_rc_policy-document. I would have thought that meant a violation of http://www.us.debian.org/doc/debian-policy/. I certainly think it's the release manager's responsibility to mark bugs that are not release blocking etch-ignore, but if it is a violation of policy it should still be serious. -- Eric Dorland [EMAIL PROTECTED] ICQ: #61138586, Jabber: [EMAIL PROTECTED] 1024D/16D970C6 097C 4861 9934 27A0 8E1C 2B0A 61E9 8ECF 16D9 70C6 signature.asc Description: Digital signature
Re: Bug mass filling
* Aurelien Jarno ([EMAIL PROTECTED]) [061019 21:31]: Andreas Barth a écrit : A violation of the parts of the debian policy as listed on http://release.debian.org/etch_rc_policy.txt is serious level (that should be the same as the must-directives in policy, but - well, I hope that I have finally time post-etch to sync that finally). Any other policy violation is at most important level (unless it conincides with one of the other criteria for RC bugs, of course). Note that what we are discussing (must have in targets debian/rules) are listed on http://release.debian.org/etch_rc_policy.txt As vorlon said, that is listed under the heading of 4. Autobuilding, so the scope is buildds must not fail of this rule. That is why I asked to file the cases where buildds failed as serious, and the others as important (and cases where Packages in the archive must not be so buggy [...] we refuse to support them. as serious as well, that is under section 5. General). Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
On Thu, Oct 19, 2006 at 09:35:38PM +0200, Andreas Barth [EMAIL PROTECTED] wrote: But I need to admit that I get sick, seriously sick. If someone doesn't agree with something, he just says you do it wrong just for release of etch on $date. I really hate that. Especially when it's about things that are done that way since ages, but someone just recently has become aware of that. I need to admit that I get sick, seriously sick of all that has been happening in Debian in the last couple of months, between RM funding, dunc-tank, people resigning, release date chosen on odd grounds, do whatever to release on that date, whatever, 42 stupid useless GRs to delay (again) what was delayed in order to release sarge, Sven Luther vs. Sven Luther's enemies, ... ... ... ... I'm not even talking about that stupid Mozilla® affair. That really takes the fun away from Debian for me. Same here. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
On Thu, Oct 19, 2006 at 03:53:56PM -0400, Eric Dorland [EMAIL PROTECTED] wrote: * Andreas Barth ([EMAIL PROTECTED]) wrote: * Mike Hommey ([EMAIL PROTECTED]) [061019 21:14]: On Thu, Oct 19, 2006 at 09:06:42PM +0200, Andreas Barth [EMAIL PROTECTED] wrote: * Mike Hommey ([EMAIL PROTECTED]) [061019 20:42]: Note how subtly the Etch RC policy removes the first alternative of the serious bug description... Which do you mean? Please read the Etch RC policy. It tells: | In addition to the issues listed in this document, an issue is release | critical if it: | [...] | * in the maintainer's opinion, makes the package unsuitable | for release So, what does the Etch RC policy remove from the bugs.d.o description? 'is a severe violation of Debian policy (roughly, it violates a must or required directive), or' The html-code for this part is: DTCODEserious/CODE DDis a a href=http://release.debian.org/etch_rc_policy.txt;severe violation of Debian policy/a (roughly, it violates a must or required directive), or, in the package maintainer's opinion, makes the package unsuitable for release. So, obviously http://www.debian.org/Bugs/Developer#severities defines that severe violation of Debian policy means anything referenced in the etch_rc_policy-document. I would have thought that meant a violation of http://www.us.debian.org/doc/debian-policy/. That was not a link before it was changed before sarge release, in July 2004. Interesting log in the web page cvs: The RM defines what the 'serious' severity means. jvw regarding -a and -o in -test, aj, Kamion and vorlon said on June 8 that it is not considered RC by you guys. Okay to tag bugs with '... uses XSIisms (test ... -a/-o ...) with sarge-ignore? aj jvw: no, it's not okay for them to be marked RC in the first place aj http://people.debian.org/~ajt/sarge_rc_policy.txt is the canonical place to look for the definition of severe policy violation aj sarge-ignore is not possible as it is not an RC issue [...] jvw aj: so you say http://www.debian.org/Bugs/Developer#severities is wrong? aj whatever jvw I'm not going to be able to convince people that http://www.debian.org/Bugs/Developer#severities is wrong, but I might be able to say it isn't a Sarge issue at least, but that involves sarge-ignore, which requires your okay aj it doesn't matter what that page says aj http://people.debian.org/~ajt/sarge_rc_policy.txt is canonical aj if the bug doesn't match the criteria on that page it's not serious grave or critical So, what is written on http://www.debian.org/Bugs/Developer#severities doesn't count (not to say it's crap), and it's not necessary to change it. By the way, reportbug doesn't give anything close to a hint that it could be anything else than than Debian Policy: 3 serious is a severe violation of Debian policy (that is, the problem is a violation of a 'must' or 'required' directive); may or may not affect the usability of the package. Note that non-severe policy violations may be 'normal,' 'minor,' or 'wishlist' bugs. (Package maintainers may also designate other bugs as 'serious' and thus release-critical; however, end users should not do so.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
On Thu, Oct 19, 2006 at 09:56:37PM +0200, Andreas Barth [EMAIL PROTECTED] wrote: * Aurelien Jarno ([EMAIL PROTECTED]) [061019 21:31]: Andreas Barth a écrit : A violation of the parts of the debian policy as listed on http://release.debian.org/etch_rc_policy.txt is serious level (that should be the same as the must-directives in policy, but - well, I hope that I have finally time post-etch to sync that finally). Any other policy violation is at most important level (unless it conincides with one of the other criteria for RC bugs, of course). Note that what we are discussing (must have in targets debian/rules) are listed on http://release.debian.org/etch_rc_policy.txt As vorlon said, that is listed under the heading of 4. Autobuilding, so the scope is buildds must not fail of this rule. That is why I Where does it say the scope for 4. Autobuilding is buildds must not fail ? It does say Packages must autobuild without failure on all architectures on which they are supported, but that's one of the options that make a bug RC. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Is there a need for /usr/lib64/ on a pure i386?
Hello d-dev, I noticed yesterday that after an upgrade I got a /usr/lib64 dir with some (not neded) stuff in it. I am not running any 64 bit arch. $ dpkg -S /usr/lib64 # says: libg2c0-dev, fakeroot, libgfortran1-dev: /usr/lib64 I have found that there is a bug [1] on fakeroot reporting the same. The question is: will it become a common practice that packages for i386 will include 64-bit libraries? After reading the reply of Clint Adams on [1] I have got such an impression. Please correct me if I am wrong. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=344104 -- Станислав
Re: Bug mass filling
* Mike Hommey ([EMAIL PROTECTED]) [061019 22:06]: That was not a link before it was changed before sarge release, in July 2004. The link was added later because people were barking around. The meaning was always the same. Anyways, July 2004 is a *bit* history now, don't you think so? So, what is written on http://www.debian.org/Bugs/Developer#severities doesn't count (not to say it's crap), and it's not necessary to change it. If you disagree with what is written on the page, you might want to ask [EMAIL PROTECTED] for clarification, or you could appeal to the Technical Committee, or you could ask the developers in a GR. Until you succeed at at least one of the ways, the definition as written down by a member of [EMAIL PROTECTED] stays valid. As it is always. Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
* Mike Hommey ([EMAIL PROTECTED]) [061019 22:09]: Where does it say the scope for 4. Autobuilding is buildds must not fail ? There are always bugs in any document. For sarge, we e.g. sarge-ignored some MTAs which didn't provide -bs, though LSB requires that. Now, we adjusted the policy to make it legal (as long as they conflict with lsb of course). Nothing wrong with that, the text isn't written in stone. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
On Thu, Oct 19, 2006 at 10:15:16PM +0200, Andreas Barth [EMAIL PROTECTED] wrote: * Mike Hommey ([EMAIL PROTECTED]) [061019 22:06]: That was not a link before it was changed before sarge release, in July 2004. The link was added later because people were barking around. The meaning was always the same. The meaning of Debian Policy was always something else than http://www.us.debian.org/doc/debian-policy/ ? Come on... Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
On Thu, Oct 19, 2006 at 10:20:46PM +0200, Andreas Barth [EMAIL PROTECTED] wrote: * Mike Hommey ([EMAIL PROTECTED]) [061019 22:09]: Where does it say the scope for 4. Autobuilding is buildds must not fail ? There are always bugs in any document. Be aware that, even if you don't like it, this looks like you bend the rules so that it doesn't alter the release plan. Be also aware that too much bending the rules makes them useless. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: gcc-4.2 build-depends?
Hello, Frank Küster napsal: Jiri Palecek [EMAIL PROTECTED] wrote: Hello, can anyone explain why gcc-4.2 build-depends on libgconf2-dev, libxul-dev, libart-2.0-dev, libgtk2.0-dev, lib32asound2-dev, libcairo2-dev, libqt4-dev and several others? It seems quite strange (well, even more) to me. Well, it builds a couple of binary packages that might well need such libraries. Without looking at the source, names like gappletviewer-4.2 Standalone application to execute Java (tm) applets gcjwebplugin-4.2 Web browser plugin to execute Java (tm) applets sound like good candidates. I don't think this is, er... wise. This means if I want to make a (cross-)compiler, I have to install Qt, GNOME, XUL (which conflicts: mozilla-browser) even if I'll never want to use java. Also, any RC-bug in these will make gcc not suitable for testing. I think the same arguments as in Bug#360881 apply here. Also, the same solution should be used (eg. split the package). Regards Jiri Palecek
Re: Bug mass filling
* Mike Hommey ([EMAIL PROTECTED]) [061019 22:29]: [another agression] Sorry, but enough is enough. I'm fed up about your sudden agressions towards me for no reason at all. Welcome to my killfile. Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
Mike Hommey [EMAIL PROTECTED] wrote: On Thu, Oct 19, 2006 at 10:20:46PM +0200, Andreas Barth [EMAIL PROTECTED] wrote: * Mike Hommey ([EMAIL PROTECTED]) [061019 22:09]: Where does it say the scope for 4. Autobuilding is buildds must not fail ? There are always bugs in any document. Be aware that, even if you don't like it, this looks like you bend the rules so that it doesn't alter the release plan. Be also aware that too much bending the rules makes them useless. What about your proposing a GR to recall the Release Managers? Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
Re: ethstatus: no upstream, RFA or removal?
On Thursday 19 October 2006 13:37, Christoph Haas wrote: I'm the maintainer of the ethstatus package - a console-based ethernet statistics monitor. You can e.g. run it on your gateway's 9 CRT on the console and see how much bandwidth is currently used in a bar-like view. I'm in the process of RFA'ing the package. But I wonder whether I should even request for this package to get removed. Case closed. Aurélien GÉRÔME just adopted the package. Thanks. Christoph -- Famous coworker quote: I'm still confused - just on a higher level now.
Re: Bug mass filling
Mike Hommey [EMAIL PROTECTED] writes: So, what does the Etch RC policy remove from the bugs.d.o description? 'is a severe violation of Debian policy (roughly, it violates a must or required directive), or' Perhaps you should concentrate on the word roughly there. What constitutes a severe violation is in the judgment of the Release Team, and the release goals indicate their judgment in the context of a particular release. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
Mike Hommey [EMAIL PROTECTED] wrote: Be aware that, even if you don't like it, this looks like you bend the rules so that it doesn't alter the release plan. Be also aware that too much bending the rules makes them useless. Don't try to bend the rules, it's impossible. Instead, only realize the truth: there are no rules. JB. -- Julien BLACHE - Debian GNU/Linux Developer - [EMAIL PROTECTED] Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
On Thu, Oct 19, 2006 at 10:37:38PM +0200, Andreas Barth [EMAIL PROTECTED] wrote: * Mike Hommey ([EMAIL PROTECTED]) [061019 22:29]: [another agression] Waw, actually, i was trying to be less aggressive... Anyways, since I'm too pissed and since I see no reason to put myself in that mood any further, I'm taking a few days off Debian, which means my current work on seamonkey^Hiceape will be on hold. All the work in progress on my currently maintained packages will be on hold too. If you want iceape in shape for etch if we are anything near a freeze, well, get your fingers out of your asses, as we say in french. Mike signature.asc Description: Digital signature
Re: Bug mass filling
On Thu, Oct 19, 2006 at 10:37:38PM +0200, Andreas Barth wrote: * Mike Hommey ([EMAIL PROTECTED]) [061019 22:29]: [another agression] Sorry, but enough is enough. I'm fed up about your sudden agressions towards me for no reason at all. Welcome to my killfile. Hi Andi, from my perspective, I see this: DD's trying to use Debian policy as a guide to make all packages pass policy requirement. Is this not what they are tasked to do ? They see inconsistencies between RM's understanding of these and their goals. And they seem to say that if someone would alter, fix, change or clarify policy, they could have a clear goal for them to reach release targets. This way they would not be confused about the unclear judgments that they are reading from RM's and won't bother them for further questions that waste everyones time and patience. I dont see this as an attack on RM's, I see it as folks wanting help to reach release goals and want someone to just clarify policy. Now if nobody clarifies policy, they have to get guidance from the only people who can: RM's. If there is some reason why the RM's are not able/willing to do this, then that leads to only further frustration and no progress, as witnesses by this and other threads. So, if someone can just update, clarify, fix, or in someway address this, please lets focus on the real goal: liw's tattoo! have a nice day! cheers, Kev -- | .''`. == Debian GNU/Linux == | my web site: | | : :' : The Universal | debian.home.pipeline.com | | `. `' Operating System| go to counter.li.org and | | `-http://www.debian.org/ |be counted! #238656 | | my keysever: pgp.mit.edu | my NPO: cfsg.org | signature.asc Description: Digital signature
Re: Bug mass filling
On Thu, Oct 19, 2006 at 10:52:25PM +0200, Mike Hommey wrote: On Thu, Oct 19, 2006 at 10:37:38PM +0200, Andreas Barth [EMAIL PROTECTED] wrote: * Mike Hommey ([EMAIL PROTECTED]) [061019 22:29]: [another agression] Waw, actually, i was trying to be less aggressive... This is a very, very old argument, and it doesn't really come across to me as less aggressive to continue to suggest that the RMs are changing the rules to meet the release deadline, or even that it will *appear* that we are doing so, when these are rules that have governed the use of RC severities in the BTS for at least the past three years and are explicitly sanctioned by the BTS admins. So I'm sorry that this upsets you, but it's not exactly the release team's fault if people are inferring things from the BTS documentation that aren't written there. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How can the OS autodetect that a user is a newbie and offer help?
[Sander Marechal] True, but I meant that an app can kill X, requiring it to be restarted. Newbies get very confused at that point. Look, if you typed startx once, you can type it again. If you didn't, it means you're using a display manager like xdm, and xdm will restart X when it dies. If X just _freezes_ rather than dies, you don't get a shell prompt anyway. What you get is the opportunity to hit Ctrl-Alt-Backspace, so that X will die, and then you're back to the previous cases. I see no case where it is useful to alias startx to start-desktop. Unless X dies and then xdm _also_ dies. Does this ever happen? signature.asc Description: Digital signature
Re: Bug mass filling
On Thu, 19 Oct 2006, Kevin Mark wrote: DD's trying to use Debian policy as a guide to make all packages pass policy requirement. Is this not what they are tasked to do? There's nothing wrong with these goals. Indeed, I'm sure no one would object to patches and bugs being filed to fix these policy issues. The only question is whether the bugs are RC or not. The RMs have the ability to determine which policy issues are RC; the people who can override their decision (by making other bugs RC) are the maintainers for a particular package, by deciding that a particular package is not fit for release. Otherwise, when the RMs have clarified the release policy (as they have just done), then we should go back to fixing bugs instead of arguing about whether or not the bugs are really all that bad or not. Don Armstrong -- Il semble que la perfection soit atteinte non quand il n'y a plus rien a ajouter, mais quand il n'y a plus rien a retrancher. (Perfection is apparently not achieved when nothing more can be added, but when nothing else can be removed.) -- Antoine de Saint-Exupe'ry, Terres des Hommes http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
how can download and run checklib
Hello, There is a link to Checklib [0] in the Packages Overview page of every maintainer. See for example vorlon's page at [1] where you could see that link in the line starting with Reports:. [0] http://rerun.lefant.net/checklib/ [1] http://qa.debian.org/developer.php?login=vorlon I couldn't find checklib in packages.debian.org [2]. [2] http://packages.debian.org/cgi-bin/search_contents.pl?word=checklibsearchmode=searchfilescase=insensitiveversion=unstablearch=i386 I also couldn't find in the FAQ [3] any reference about how to download checklib. [3] http://rerun.lefant.net/checklib/faq.html How can download and run checklib? Mit freundlichen Grüßen, Aníbal Monsalve Salazar -- http://v7w.com/anibal signature.asc Description: Digital signature
Re: how can download and run checklib
On Fri, 20 Oct 2006 08:47:48 +1000, Aníbal Monsalve Salazar wrote: I also couldn't find in the FAQ [3] any reference about how to download checklib. [3] http://rerun.lefant.net/checklib/faq.html How can download and run checklib? On http://rerun.lefant.net/checklib/ the last line says: Source code: available here (and 'available here' is a link leading to http://greek0.net/div/checklib.tar.gz ). 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: Frank Sinatra: I Get A Kick Out Of You signature.asc Description: Digital signature
Re: How can the OS autodetect that a user is a newbie and offer help?
On Friday 20 October 2006 08:06, Peter Samuelson wrote: [Sander Marechal] True, but I meant that an app can kill X, requiring it to be restarted. Newbies get very confused at that point. Look, if you typed startx once, you can type it again. If you didn't, it means you're using a display manager like xdm, and xdm will restart X when it dies. If X just _freezes_ rather than dies, you don't get a shell prompt anyway. What you get is the opportunity to hit Ctrl-Alt-Backspace, so that X will die, and then you're back to the previous cases. I see no case where it is useful to alias startx to start-desktop. I agree. Unless X dies and then xdm _also_ dies. Does this ever happen? Even if it does, that should be recoverable by, at worst, power cycling the machine. The real problem is when someone who has never used the command line before, possibly never even seen the command line, is stranded in a vt because X didn't start during boot, started and immediately crashed, or crashes every time they login. They don't know how to do anything from the command-line. They don't even know how to read a man page/edit a file. They're the users who need basic cli help. A motd message saying type `help-me' for help, and a 3-4 page doc explaining some useful basic commands (man, less, nano, cd, cp, rm, startx etc) and how to reconfigure X might be enough to prevent some of them having to re-install. Just my 2 cents Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Horiny playboy teenie pak
access news: Hot XXX Fuckoing!!! Thebse girls lopve a nice stbiff coyck!! :) GOTO: *** plbrl.zopurar.com *** their capo look really eyes provide soon, after here can, form twice link all form? loose eyes surf add today out forever order; self and, just other they. face online are told, access eyes? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug mass filling
On 10/19/06, Mike Hommey [EMAIL PROTECTED] wrote: Waw, actually, i was trying to be less aggressive... Anyways, since I'm too pissed and since I see no reason to put myself in that mood any further, I'm taking a few days off Debian, which means my current work on seamonkey^Hiceape will be on hold. All the work in progress on my currently maintained packages will be on hold too. If you want iceape in shape for etch if we are anything near a freeze, well, get your fingers out of your asses, as we say in french. I would take it out if it was in there, but please don't be pissed off so soon. Continue hacking away and let's have the best release ever :-) I really want to see Seamonkey in Etch, and you even asked the RM's to allow you to upload it (version 1.1) when released later this month. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: gcc-4.2 build-depends?
[EMAIL PROTECTED] wrote: Hello, Frank Küster napsal: Jiri Palecek [EMAIL PROTECTED] wrote: Hello, can anyone explain why gcc-4.2 build-depends on libgconf2-dev, libxul-dev, libart-2.0-dev, libgtk2.0-dev, lib32asound2-dev, libcairo2-dev, libqt4-dev and several others? It seems quite strange (well, even more) to me. Well, it builds a couple of binary packages that might well need such libraries. Without looking at the source, names like gappletviewer-4.2 Standalone application to execute Java (tm) applets gcjwebplugin-4.2 Web browser plugin to execute Java (tm) applets sound like good candidates. I don't think this is, er... wise. This means if I want to make a (cross-)compiler, I have to install Qt, GNOME, XUL (which conflicts: mozilla-browser) even if I'll never want to use java. No, you haven't. The Build-Depends of a Debian package are not meant to be used for bootstrapping. You could just disable the respective stanzas in the control file, build your cross-compiler or compiler for a new architecture, and once you managed to build Qt and Gnome, you can enable them again. Also, any RC-bug in these will make gcc not suitable for testing. I think the same arguments as in Bug#360881 apply here. Also, the same solution should be used (eg. split the package). This, however, is a strong argument. Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
Accepted gui-apt-key 0.1-4 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 18 Oct 2006 09:07:55 +0200 Source: gui-apt-key Binary: gui-apt-key Architecture: source all Version: 0.1-4 Distribution: unstable Urgency: medium Maintainer: Martin Schulze [EMAIL PROTECTED] Changed-By: Martin Schulze [EMAIL PROTECTED] Description: gui-apt-key - Graphical Key Manager for APT Closes: 391534 391877 Changes: gui-apt-key (0.1-4) unstable; urgency=medium . * New Hungarian translation by Attila SZERVAC [EMAIL PROTECTED] * Updated Spanish translation * Updated Slovak translation * Updated French translation * Updated Basque translation * Added build dependency to gettext (closes: Bug#391877) * Updated Swedish translation (closes: Bug#391534) * Bumped standards version Files: 28c4b4d6472f8cd18b03b195a0713daf 558 admin optional gui-apt-key_0.1-4.dsc 5f965b75922b242f8bfbf2896496681c 5854 admin optional gui-apt-key_0.1-4.diff.gz 63ac3a74f3bae47d9086b2a77114714b 13910 admin optional gui-apt-key_0.1-4_all.deb 11d82cf669cfa2d5253f39513f00a92c 18244 admin optional gui-apt-key_0.1.orig.tar.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFNxXaW5ql+IAeqTIRAtJTAKCFR5f8bgVHPF9dx0dqxe151csqVACdE6ZC d21SNmR9n6B6YbKnPqdBSec= =CiHN -END PGP SIGNATURE- Accepted: gui-apt-key_0.1-4.diff.gz to pool/main/g/gui-apt-key/gui-apt-key_0.1-4.diff.gz gui-apt-key_0.1-4.dsc to pool/main/g/gui-apt-key/gui-apt-key_0.1-4.dsc gui-apt-key_0.1-4_all.deb to pool/main/g/gui-apt-key/gui-apt-key_0.1-4_all.deb gui-apt-key_0.1.orig.tar.gz to pool/main/g/gui-apt-key/gui-apt-key_0.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted galeon 2.0.2-3 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 18 Oct 2006 23:01:42 +0200 Source: galeon Binary: galeon galeon-common Architecture: source i386 all Version: 2.0.2-3 Distribution: unstable Urgency: low Maintainer: Loic Minier [EMAIL PROTECTED] Changed-By: Loic Minier [EMAIL PROTECTED] Description: galeon - GNOME web browser for advanced users galeon-common - GNOME web browser for advanced users Closes: 393982 Changes: galeon (2.0.2-3) unstable; urgency=low . * Suggest mozplugger instead of mozilla-bonobo; thanks Adam C Powell IV closes: #393982. * Provide gnome-www-browser. Files: b6bc76f4a2d366eac049a926792e726d 866 gnome optional galeon_2.0.2-3.dsc 1d548720a1220a57d7adfdcfeb5bc3f0 133104 gnome optional galeon_2.0.2-3.diff.gz 61666ed108556f861dc33d2412663928 2966280 gnome optional galeon-common_2.0.2-3_all.deb 52e01250818591f5e13271a70d1efd2a 728902 gnome optional galeon_2.0.2-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFNxPp4VUX8isJIMARAuFAAJ40vxQAy5kIgY73YGAxmJhwWSfLwQCgkTFU e1YvQzjWRvR5evXE2vsgl/M= =A5q8 -END PGP SIGNATURE- Accepted: galeon-common_2.0.2-3_all.deb to pool/main/g/galeon/galeon-common_2.0.2-3_all.deb galeon_2.0.2-3.diff.gz to pool/main/g/galeon/galeon_2.0.2-3.diff.gz galeon_2.0.2-3.dsc to pool/main/g/galeon/galeon_2.0.2-3.dsc galeon_2.0.2-3_i386.deb to pool/main/g/galeon/galeon_2.0.2-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted swish-e 2.4.3-7 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 18 Oct 2006 17:58:35 +0200 Source: swish-e Binary: swish-e swish-e-dev Architecture: source i386 Version: 2.4.3-7 Distribution: unstable Urgency: high Maintainer: Ludovic Drolez [EMAIL PROTECTED] Changed-By: Ludovic Drolez [EMAIL PROTECTED] Description: swish-e- Simple Web Indexing System for Humans - Enhanced swish-e-dev - Simple Web Indexing System for Humans - Enhanced Changes: swish-e (2.4.3-7) unstable; urgency=high . * The last patch in filter.c could segfault. Files: a7a820c047aeb3e4c78c7bb9cad1238a 644 web optional swish-e_2.4.3-7.dsc e022872da7cefac1d569b5d0c78dae3c 13052 web optional swish-e_2.4.3-7.diff.gz 6fc046ba402387848327b0a106bff5f1 820014 web optional swish-e_2.4.3-7_i386.deb cfd2b82adc5129527a04a6f9994eab7d 130694 web optional swish-e-dev_2.4.3-7_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFNxiEsRlQAP1GppgRAsDOAJ9w9Qw+SwNrg8LrWRSZax8D4PdGyACfavQQ /w4geb0saFWU6qFC8iLUNgM= =C6ls -END PGP SIGNATURE- Accepted: swish-e-dev_2.4.3-7_i386.deb to pool/main/s/swish-e/swish-e-dev_2.4.3-7_i386.deb swish-e_2.4.3-7.diff.gz to pool/main/s/swish-e/swish-e_2.4.3-7.diff.gz swish-e_2.4.3-7.dsc to pool/main/s/swish-e/swish-e_2.4.3-7.dsc swish-e_2.4.3-7_i386.deb to pool/main/s/swish-e/swish-e_2.4.3-7_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mono 1.1.18-3 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 06:58:20 +0200 Source: mono Binary: libmono-peapi1.0-cil libmono-cscompmgd8.0-cil libmono-security2.0-cil libmono-system-runtime2.0-cil libmono-security1.0-cil libmono-relaxng2.0-cil mono-mjs libmono-system-web2.0-cil mono-common libmono-accessibility2.0-cil libmono-bytefx0.7.6.1-cil libmono-system-messaging2.0-cil libmono-system2.0-cil libmono-system-runtime1.0-cil libmono-relaxng1.0-cil libmono-oracle1.0-cil libmono-microsoft7.0-cil libmono-sharpzip0.84-cil mono-gac mono mono-mcs libmono-sqlite1.0-cil libmono-sharpzip0.6-cil libmono-bytefx0.7.6.2-cil libmono-npgsql2.0-cil libmono-data-tds1.0-cil mono-jay libmono-cairo1.0-cil libmono-sharpzip2.6-cil libmono-system1.0-cil libmono-npgsql1.0-cil libmono-system-messaging1.0-cil libmono-accessibility1.0-cil libmono-system-web1.0-cil mono-jit libmono-corlib1.0-cil libmono-microsoft8.0-cil libmono-ldap2.0-cil mono-gmcs libmono2.0-cil libmono1.0-cil mono-devel libmono-system-ldap2.0-cil libmono-peapi2.0-cil libmono-corlib2.0-cil libmono-cairo2.0-cil libmono-sqlite2.0-cil libmono0 libmono-microsoft-build2.0-cil libmono-system-data1.0-cil libmono-dev libmono-system-ldap1.0-cil libmono-sharpzip2.84-cil mono-runtime libmono-winforms1.0-cil libmono-firebirdsql1.7-cil mono-utils libmono-cscompmgd7.0-cil libmono-c5-1.0-cil libmono-ldap1.0-cil libmono-winforms2.0-cil libmono-data-tds2.0-cil libmono-system-data2.0-cil libmono-oracle2.0-cil Architecture: source i386 all Version: 1.1.18-3 Distribution: unstable Urgency: low Maintainer: Debian Mono Group [EMAIL PROTECTED] Changed-By: Debian Mono Group [EMAIL PROTECTED] Description: libmono-accessibility1.0-cil - Mono Accessibility library libmono-accessibility2.0-cil - Mono Accessibility library libmono-bytefx0.7.6.1-cil - Mono ByteFX.Data library libmono-bytefx0.7.6.2-cil - Mono ByteFX.Data library libmono-c5-1.0-cil - Mono C5 library libmono-cairo1.0-cil - Mono Cairo library libmono-cairo2.0-cil - Mono Cairo library libmono-corlib1.0-cil - Mono core library (1.0) libmono-corlib2.0-cil - Mono core library (2.0) libmono-cscompmgd7.0-cil - Mono cscompmgd library libmono-cscompmgd8.0-cil - Mono cscompmgd library libmono-data-tds1.0-cil - Mono Data library libmono-data-tds2.0-cil - Mono Data Library libmono-dev - libraries for the Mono JIT - Development files libmono-firebirdsql1.7-cil - Mono FirebirdSql library libmono-ldap1.0-cil - Mono LDAP library libmono-ldap2.0-cil - Mono LDAP library libmono-microsoft-build2.0-cil - Mono Microsoft.Build libraries libmono-microsoft7.0-cil - Mono Microsoft libraries libmono-microsoft8.0-cil - Mono Microsoft libraries libmono-npgsql1.0-cil - Mono Npgsql library libmono-npgsql2.0-cil - Mono Npgsql library libmono-oracle1.0-cil - Mono Oracle library libmono-oracle2.0-cil - Mono Oracle library libmono-peapi1.0-cil - Mono PEAPI library libmono-peapi2.0-cil - Mono PEAPI library libmono-relaxng1.0-cil - Mono Relaxng library libmono-relaxng2.0-cil - Mono Relaxng library libmono-security1.0-cil - Mono Security library libmono-security2.0-cil - Mono Security library libmono-sharpzip0.6-cil - Mono SharpZipLib library libmono-sharpzip0.84-cil - Mono SharpZipLib library libmono-sharpzip2.6-cil - Mono SharpZipLib library libmono-sharpzip2.84-cil - Mono SharpZipLib library libmono-sqlite1.0-cil - Mono Sqlite library libmono-sqlite2.0-cil - Mono Sqlite library libmono-system-data1.0-cil - Mono System.Data library libmono-system-data2.0-cil - Mono System.Data Library libmono-system-ldap1.0-cil - Mono System.DirectoryServices library libmono-system-ldap2.0-cil - Mono System.DirectoryServices library libmono-system-messaging1.0-cil - Mono System.Messaging library libmono-system-messaging2.0-cil - Mono System.Messaging Library libmono-system-runtime1.0-cil - Mono System.Runtime library libmono-system-runtime2.0-cil - Mono System.Runtime Library libmono-system-web1.0-cil - Mono System.Web library libmono-system-web2.0-cil - Mono System.Web Library libmono-system1.0-cil - Mono System libraries (1.0) libmono-system2.0-cil - Mono System libraries (2.0) libmono-winforms1.0-cil - Mono System.Windows.Forms library libmono-winforms2.0-cil - Mono System.Windows.Forms library libmono0 - libraries for the Mono JIT libmono1.0-cil - Mono libraries (1.0) libmono2.0-cil - Mono libraries (2.0) mono - Mono CLI (.NET) runtime mono-common - common files for Mono mono-devel - Mono CLI runtime with development tools mono-gac - Mono GAC tool mono-gmcs - Mono C# 2.0 compiler mono-jay - LALR(1) parser generator oriented to Java/CLI mono-jit - fast CLI JIT/AOT compiler for Mono mono-mcs - Mono C# compiler mono-mjs - Mono JScript compiler mono-runtime - Mono runtime mono-utils - Mono utilities Changes: mono (1.1.18-3) unstable; urgency=low . * Sebastian 'slomo' Dröge: + debian/patches/gmcs-static-anonmethods.dpatch: - Fix from SVN
Accepted gconf2 2.16.0-2 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 09:01:48 +0200 Source: gconf2 Binary: libgconf2-4 gconf2 gconf2-common libgconf2-dev Architecture: source i386 all Version: 2.16.0-2 Distribution: unstable Urgency: low Maintainer: Josselin Mouette [EMAIL PROTECTED] Changed-By: Loic Minier [EMAIL PROTECTED] Description: gconf2 - GNOME configuration database system (support tools) gconf2-common - GNOME configuration database system (common files) libgconf2-4 - GNOME configuration database system (shared libraries) libgconf2-dev - GNOME configuration database system (development) Changes: gconf2 (2.16.0-2) unstable; urgency=low . * Merge the final 2.14.0-5. * Add CDBS' utils. * Upload to unstable. * Ship sample /etc/gconf/2/evoldap.conf as a conffile as we're unlikely to tweak it a lot for Debian. * Ship the evoldap LDAP schema in /usr/share/doc/gconf2-common. * Drop debian/gconftool-2.1; merged upstream. * Add upstream programming examples to libgconf2-dev. * Ship upstream doc/FAQ.txt and drop our local debian/FAQ. . gconf2 (2.16.0-1) experimental; urgency=low . * New upstream release; no API change. - Drop patch 20_gconftool-2-manpage-typo, merged upstream. - Build-depend on libxml-parser-perl. Files: 316a86e4ec370a56829582a14ae9c83b 1589 libs optional gconf2_2.16.0-2.dsc 80ac4a8490d233b7d817d18f90a4ec3d 14998 libs optional gconf2_2.16.0-2.diff.gz 39ae5a83535bbed1b84cebc909b817a3 1397002 libs optional gconf2-common_2.16.0-2_all.deb 3f880aedf3976595045d8d8f6ce74a52 133032 libs optional gconf2_2.16.0-2_i386.deb 1f8c00af03ccc89efb6e75bb7591944a 235726 libs optional libgconf2-4_2.16.0-2_i386.deb c52406d8a4b9b4a82f0271a748e0d421 269082 libdevel optional libgconf2-dev_2.16.0-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFNyO04VUX8isJIMARAu0QAJ4giiwq3miewRIykMF2MOVdeZvJCQCglpqR 5CCAeLbjSbaHSOHMSRayPwc= =dwOz -END PGP SIGNATURE- Accepted: gconf2-common_2.16.0-2_all.deb to pool/main/g/gconf2/gconf2-common_2.16.0-2_all.deb gconf2_2.16.0-2.diff.gz to pool/main/g/gconf2/gconf2_2.16.0-2.diff.gz gconf2_2.16.0-2.dsc to pool/main/g/gconf2/gconf2_2.16.0-2.dsc gconf2_2.16.0-2_i386.deb to pool/main/g/gconf2/gconf2_2.16.0-2_i386.deb libgconf2-4_2.16.0-2_i386.deb to pool/main/g/gconf2/libgconf2-4_2.16.0-2_i386.deb libgconf2-dev_2.16.0-2_i386.deb to pool/main/g/gconf2/libgconf2-dev_2.16.0-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gcc-m68hc1x 1:3.3.6+3.1+dfsg-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 07:48:13 +0200 Source: gcc-m68hc1x Binary: gcc-m68hc1x Architecture: source amd64 Version: 1:3.3.6+3.1+dfsg-1 Distribution: unstable Urgency: low Maintainer: Aurelien Jarno [EMAIL PROTECTED] Changed-By: Aurelien Jarno [EMAIL PROTECTED] Description: gcc-m68hc1x - GNU C compiler for the Motorola 68HC11/12 processors Closes: 392960 Changes: gcc-m68hc1x (1:3.3.6+3.1+dfsg-1) unstable; urgency=low . * Removed non-free stuff from the package (closes: bug#392960). * Bumped Standard-Versions to 3.7.2 (no changes). Files: a2838a6d34373ec133368afe616de38d 732 devel extra gcc-m68hc1x_3.3.6+3.1+dfsg-1.dsc a01137f07d6958834132ed1f97e2d164 21165350 devel extra gcc-m68hc1x_3.3.6+3.1+dfsg.orig.tar.gz c7d6499e539b4c4cf8c3c6090334f385 137336 devel extra gcc-m68hc1x_3.3.6+3.1+dfsg-1.diff.gz ee7c7ad7da93b5aaa3995196040fd4f1 4510244 devel extra gcc-m68hc1x_3.3.6+3.1+dfsg-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFNyKLw3ao2vG823MRArMKAJ9aetypYdarw2MfvuK/BwmHLV6FqACfSW2Y ZloR6SQNB/owjx0zYzICIf8= =TnkK -END PGP SIGNATURE- Accepted: gcc-m68hc1x_3.3.6+3.1+dfsg-1.diff.gz to pool/main/g/gcc-m68hc1x/gcc-m68hc1x_3.3.6+3.1+dfsg-1.diff.gz gcc-m68hc1x_3.3.6+3.1+dfsg-1.dsc to pool/main/g/gcc-m68hc1x/gcc-m68hc1x_3.3.6+3.1+dfsg-1.dsc gcc-m68hc1x_3.3.6+3.1+dfsg-1_amd64.deb to pool/main/g/gcc-m68hc1x/gcc-m68hc1x_3.3.6+3.1+dfsg-1_amd64.deb gcc-m68hc1x_3.3.6+3.1+dfsg.orig.tar.gz to pool/main/g/gcc-m68hc1x/gcc-m68hc1x_3.3.6+3.1+dfsg.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted tomboy 0.4.1-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 00:02:29 -0700 Source: tomboy Binary: tomboy Architecture: source i386 Version: 0.4.1-2 Distribution: unstable Urgency: low Maintainer: Dave Beckett [EMAIL PROTECTED] Changed-By: Dave Beckett [EMAIL PROTECTED] Description: tomboy - desktop note taking program using Wiki style links Closes: 393484 Changes: tomboy (0.4.1-2) unstable; urgency=low . * Added Build-Depends: on libdbus-glib-1-dev to get D-Bus remote control enabled (Closes: #393484) * Updated Build-Depends: for cli-common-dev to = 0.4.4 Files: 3aed857cacb81f6562478abac4ae0110 962 gnome optional tomboy_0.4.1-2.dsc a8fb4e1f2505bbb28fc414c8af24a979 11398 gnome optional tomboy_0.4.1-2.diff.gz 50a0f56377a778dad7dc2474a8278763 624112 gnome optional tomboy_0.4.1-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFNyNmQ+ySUE9xlVoRAppbAKCoPcdbq8WD0JpgIqmKy3N74d0O7wCghk6U o/4pVeialcPiY3pBjiTK3fE= =p95z -END PGP SIGNATURE- Accepted: tomboy_0.4.1-2.diff.gz to pool/main/t/tomboy/tomboy_0.4.1-2.diff.gz tomboy_0.4.1-2.dsc to pool/main/t/tomboy/tomboy_0.4.1-2.dsc tomboy_0.4.1-2_i386.deb to pool/main/t/tomboy/tomboy_0.4.1-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted hal 0.5.8.1-2 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 18 Oct 2006 23:45:26 +0200 Source: hal Binary: libhal-dev libhal-storage1 hal-doc libhal-storage-dev hal libhal1 hal-device-manager Architecture: source i386 all Version: 0.5.8.1-2 Distribution: unstable Urgency: low Maintainer: Sjoerd Simons [EMAIL PROTECTED] Changed-By: Sjoerd Simons [EMAIL PROTECTED] Description: hal- Hardware Abstraction Layer hal-device-manager - Hardware Abstraction Layer user interface hal-doc- Hardware Abstraction Layer libhal-dev - Hardware Abstraction Layer - development files libhal-storage-dev - Hardware Abstraction Layer - development files libhal-storage1 - Hardware Abstraction Layer - shared library for storage devices libhal1- Hardware Abstraction Layer - shared library Closes: 388558 391124 393203 Changes: hal (0.5.8.1-2) unstable; urgency=low . * 12_pegasus_pmu_crash_fix.patch - Added. Check if power_management.type was set before doing strcmp and detect Pegasos machines as having the desktop formfactor (Closes: #391124) * /debian/patches/13_hal_callout_bashism.patch - Added. Fix some bashisms in the hal callout scripts * debian/patches/02_powerscripts.patch - Updated. Use s2ram instead of s2both to let uswsusp suspend to ram (Closes: #388558) * debian/patches/14_power_suspend_linux_pmu_fix.patch - Added. Use the correct hal property to check the powermanagement type. (Closes: #393203) Files: 39ce500a1745f8368894aaac456013a4 969 admin optional hal_0.5.8.1-2.dsc 263bd1cc38adbe645761860d5010b060 31626 admin optional hal_0.5.8.1-2.diff.gz 6a07df74e4c22766f6a42ec983411a76 311588 admin optional hal-device-manager_0.5.8.1-2_all.deb 8d09c3e8b1a33eb1f6ed07465b12e0ed 256204 doc optional hal-doc_0.5.8.1-2_all.deb a7372f7bb45a536a5b1583f30f6b91af 524052 admin optional hal_0.5.8.1-2_i386.deb 08284c17cbf2d1562ca4c6ead02037c7 269006 libs optional libhal1_0.5.8.1-2_i386.deb 48bf0c05483dd97d22a2fe75934efc75 269144 libs optional libhal-storage1_0.5.8.1-2_i386.deb 1fc6301106735bf873ebc04db27c8de3 274312 libdevel optional libhal-dev_0.5.8.1-2_i386.deb cb71cb552ac3a2e40c349acd0c34ba62 272516 libdevel optional libhal-storage-dev_0.5.8.1-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFNzNXgTd+SodosdIRArasAJ9Npq0uNi+RivQ5QrSgOInoF3q68gCfV3Ho VEhP/0WNMgnBt3WeAbGQc2w= =1KTM -END PGP SIGNATURE- Accepted: hal-device-manager_0.5.8.1-2_all.deb to pool/main/h/hal/hal-device-manager_0.5.8.1-2_all.deb hal-doc_0.5.8.1-2_all.deb to pool/main/h/hal/hal-doc_0.5.8.1-2_all.deb hal_0.5.8.1-2.diff.gz to pool/main/h/hal/hal_0.5.8.1-2.diff.gz hal_0.5.8.1-2.dsc to pool/main/h/hal/hal_0.5.8.1-2.dsc hal_0.5.8.1-2_i386.deb to pool/main/h/hal/hal_0.5.8.1-2_i386.deb libhal-dev_0.5.8.1-2_i386.deb to pool/main/h/hal/libhal-dev_0.5.8.1-2_i386.deb libhal-storage-dev_0.5.8.1-2_i386.deb to pool/main/h/hal/libhal-storage-dev_0.5.8.1-2_i386.deb libhal-storage1_0.5.8.1-2_i386.deb to pool/main/h/hal/libhal-storage1_0.5.8.1-2_i386.deb libhal1_0.5.8.1-2_i386.deb to pool/main/h/hal/libhal1_0.5.8.1-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libgtk-trayicon-ruby 0.1.0-5 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 09:46:48 +0200 Source: libgtk-trayicon-ruby Binary: libgtk-trayicon-ruby libgtk-trayicon-ruby1.8 Architecture: source all amd64 Version: 0.1.0-5 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Michael Ablassmeier [EMAIL PROTECTED] Description: libgtk-trayicon-ruby - system tray protocol library for Ruby libgtk-trayicon-ruby1.8 - system tray protocol library for Ruby 1.8 Closes: 393014 Changes: libgtk-trayicon-ruby (0.1.0-5) unstable; urgency=low . * QA upload. * Set maintainer to QA Group; Orphaned: #391411 * Comment out require call for gtk2 in extconf.rb, otherwise package FTBFS if buildd is not running a X server it could connect to, ugly solution but works (Closes: #393014) * Conforms with latest Standards Version 3.7.2 Files: 5fb505b7f829a3218dd0199e55cdd60b 697 devel optional libgtk-trayicon-ruby_0.1.0-5.dsc 258b1be05523f055603eb56496537826 2120 devel optional libgtk-trayicon-ruby_0.1.0-5.diff.gz fe325c71ea67cda61ccf2ef41b3d066d 2336 devel optional libgtk-trayicon-ruby_0.1.0-5_all.deb e9e6ab31b544deb2ffdcb70e427fa594 9412 devel optional libgtk-trayicon-ruby1.8_0.1.0-5_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFNzJdEFV7g4B8rCURAorEAJ46Ps+rtMBKeQih/L2vd9htS4t5DACghc2G EZJt8pBlgp0FR/hSzuWpWsw= =iF+J -END PGP SIGNATURE- Accepted: libgtk-trayicon-ruby1.8_0.1.0-5_amd64.deb to pool/main/libg/libgtk-trayicon-ruby/libgtk-trayicon-ruby1.8_0.1.0-5_amd64.deb libgtk-trayicon-ruby_0.1.0-5.diff.gz to pool/main/libg/libgtk-trayicon-ruby/libgtk-trayicon-ruby_0.1.0-5.diff.gz libgtk-trayicon-ruby_0.1.0-5.dsc to pool/main/libg/libgtk-trayicon-ruby/libgtk-trayicon-ruby_0.1.0-5.dsc libgtk-trayicon-ruby_0.1.0-5_all.deb to pool/main/libg/libgtk-trayicon-ruby/libgtk-trayicon-ruby_0.1.0-5_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted revolution 0.5-4 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 10:03:57 +0200 Source: revolution Binary: libevolution-ruby libevolution-ruby1.8 Architecture: source all amd64 Version: 0.5-4 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Michael Ablassmeier [EMAIL PROTECTED] Description: libevolution-ruby - revolution, ruby binding for the evolution mail client libevolution-ruby1.8 - revolution, ruby 1.8 binding for the evolution mail client Changes: revolution (0.5-4) unstable; urgency=low . * QA upload. * Set maintainer to QA Group; Orphaned: #391403 * Conforms with latest Standards Version 3.7.2 Files: ed4304d87600f3ea135b864cd88b46e8 657 devel optional revolution_0.5-4.dsc 24ed6902be2a7dce3e80f429514b1d43 2268 devel optional revolution_0.5-4.diff.gz 3fed65050d76c7bb5e593f5e4fe08de2 2626 devel optional libevolution-ruby_0.5-4_all.deb fdc25c6f9f261f5313f14c6e5a26188f 23486 devel optional libevolution-ruby1.8_0.5-4_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFNzKIEFV7g4B8rCURApTEAJ4/bcbq5g5ahIqZRgWLFcUP+ygC3QCZAcOW IIj0wPAVTC4RZcFf3CD2qHM= =7lcT -END PGP SIGNATURE- Accepted: libevolution-ruby1.8_0.5-4_amd64.deb to pool/main/r/revolution/libevolution-ruby1.8_0.5-4_amd64.deb libevolution-ruby_0.5-4_all.deb to pool/main/r/revolution/libevolution-ruby_0.5-4_all.deb revolution_0.5-4.diff.gz to pool/main/r/revolution/revolution_0.5-4.diff.gz revolution_0.5-4.dsc to pool/main/r/revolution/revolution_0.5-4.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gtksourceview 1.8.1-2 (source all i386)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 10:01:31 +0200
Source: gtksourceview
Binary: libgtksourceview-dev libgtksourceview-common libgtksourceview1.0-0
libgtksourceview-doc
Architecture: source all i386
Version: 1.8.1-2
Distribution: unstable
Urgency: low
Maintainer: Andrew Lau [EMAIL PROTECTED]
Changed-By: Loic Minier [EMAIL PROTECTED]
Description:
libgtksourceview-common - common files for the GTK+ syntax highlighting widget
libgtksourceview-dev - development files for the GTK+ syntax highlighting
widget
libgtksourceview-doc - documentation for the GTK+ syntax highlighting widget
libgtksourceview1.0-0 - shared libraries for the GTK+ syntax highlighting
widget
Changes:
gtksourceview (1.8.1-2) unstable; urgency=low
.
* Upload to unstable.
.
gtksourceview (1.8.1-1) experimental; urgency=low
.
* New upstream release; no API change.
* Use HTTP in watch file.
.
gtksourceview (1.8.0-1) experimental; urgency=low
.
* New upstream release.
* Small fix in the -dev depends.
* Require gnome-pkg-tools 0.7.
* Call clean-la.mk and gnome-versions.mk.
* Use ${gnome:Version} and ${gnome:NextVersion} to relax dependencies.
.
gtksourceview (1.7.2-1) experimental; urgency=low
.
* New upstream development releases, with API additions.
- Target at experimental.
- Bump shlibs to = 1.7.2.
- Stop shipping boo.lang, integrated upstream.
* Sync with overrides and set libgtksourceview-common's Section to misc.
* Install gtk-doc documentation in the standard upstream directory.
- Drop --with-html-dir from configure args.
- Drop now useless libgtksourceview-doc.dirs.
- Update libgtksourceview-doc.install, libgtksourceview-doc.doc-base, and
libgtksourceview-doc.links.
- Drop /usr/share/doc/gtksourceview hierarchy.
- Add a preinst to manually drop symlinks on upgrades since dpkg can't
handle switching a pathname from symlink to directory.
- Add a prerm to manually drop the doc dir on downgrades since dpkg can't
handle switching a pathname from directory to symlink either.
* Add ${misc:Depends}.
* Update watch file to track all stable releases.
Files:
e98f2b8cc24eb748aeb8c0740e84e04e 1600 libs optional gtksourceview_1.8.1-2.dsc
a3989911a1064adb35b30eda45cad3dd 6714 libs optional
gtksourceview_1.8.1-2.diff.gz
63cd00b4fd5401f6dee99cde1ebd23ce 422822 misc optional
libgtksourceview-common_1.8.1-2_all.deb
a70833fb8e63fccdca30b4c276acf3ea 8 doc optional
libgtksourceview-doc_1.8.1-2_all.deb
c2ca9e72e3f2b8dc02aa92c3b986ec12 109534 libs optional
libgtksourceview1.0-0_1.8.1-2_i386.deb
a0f7735d8caf38ffed0436de0e4b734f 128120 libdevel optional
libgtksourceview-dev_1.8.1-2_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFNzKA4VUX8isJIMARAtAKAKCCMWe7gXNFiifi/68d+D6SDxepNgCfS2GB
9ahlCZLdLiUHSHGhKmC9UYQ=
=Coyq
-END PGP SIGNATURE-
Accepted:
gtksourceview_1.8.1-2.diff.gz
to pool/main/g/gtksourceview/gtksourceview_1.8.1-2.diff.gz
gtksourceview_1.8.1-2.dsc
to pool/main/g/gtksourceview/gtksourceview_1.8.1-2.dsc
libgtksourceview-common_1.8.1-2_all.deb
to pool/main/g/gtksourceview/libgtksourceview-common_1.8.1-2_all.deb
libgtksourceview-dev_1.8.1-2_i386.deb
to pool/main/g/gtksourceview/libgtksourceview-dev_1.8.1-2_i386.deb
libgtksourceview-doc_1.8.1-2_all.deb
to pool/main/g/gtksourceview/libgtksourceview-doc_1.8.1-2_all.deb
libgtksourceview1.0-0_1.8.1-2_i386.deb
to pool/main/g/gtksourceview/libgtksourceview1.0-0_1.8.1-2_i386.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libform-validator-ruby 0.1.4-3 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 09:41:44 +0200 Source: libform-validator-ruby Binary: libform-validator-ruby1.8 libform-validator-ruby Architecture: source all Version: 0.1.4-3 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Michael Ablassmeier [EMAIL PROTECTED] Description: libform-validator-ruby - html form validation library for ruby libform-validator-ruby1.8 - html form validation library for ruby 1.8 Changes: libform-validator-ruby (0.1.4-3) unstable; urgency=low . * QA upload. * Set maintainer to QA Group; Orphaned: #391416 * Move debhelper from B-D-I to B-D * Conforms with latest Standards Version 3.7.2 Files: b9f5298b47a6f2bbd527ab915d32d699 680 devel optional libform-validator-ruby_0.1.4-3.dsc 3f279d6ef83789c14979ca89c47e6276 1809 devel optional libform-validator-ruby_0.1.4-3.diff.gz d56decea26d199d28a5da93e4f21487e 2018 devel optional libform-validator-ruby_0.1.4-3_all.deb 558d7fa13c9f2172190a8fe1f4d11d90 32330 devel optional libform-validator-ruby1.8_0.1.4-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFNzI9EFV7g4B8rCURAvAGAJ9vAKvSlh0fgYU+VNaeAD9hhnPCQACgumo7 /yvbfmcKvJtY48rGc6ZT8cQ= =kKwp -END PGP SIGNATURE- Accepted: libform-validator-ruby1.8_0.1.4-3_all.deb to pool/main/libf/libform-validator-ruby/libform-validator-ruby1.8_0.1.4-3_all.deb libform-validator-ruby_0.1.4-3.diff.gz to pool/main/libf/libform-validator-ruby/libform-validator-ruby_0.1.4-3.diff.gz libform-validator-ruby_0.1.4-3.dsc to pool/main/libf/libform-validator-ruby/libform-validator-ruby_0.1.4-3.dsc libform-validator-ruby_0.1.4-3_all.deb to pool/main/libf/libform-validator-ruby/libform-validator-ruby_0.1.4-3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted firebird2 1.5.3.4870-11 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 18 Oct 2006 21:52:53 +0300 Source: firebird2 Binary: firebird2-utils-classic libfbclient1 firebird2-super-server libfbembed1 firebird2-dev firebird2-server-common firebird2-utils-super firebird2-examples firebird2-classic-server firebird2-common Architecture: source i386 all Version: 1.5.3.4870-11 Distribution: unstable Urgency: high Maintainer: Francesco Paolo Lovergine [EMAIL PROTECTED] Changed-By: Damyan Ivanov [EMAIL PROTECTED] Description: firebird2-classic-server - Firebird Classic Server - an RDBMS based on InterBase 6.0 code firebird2-common - Common files for firebird clients and servers firebird2-dev - Development files for Firebird - an RDBMS based on InterBase 6.0 firebird2-examples - Examples for Firebird - an RDBMS based on InterBase 6.0 code firebird2-server-common - Common files for Firebird servers firebird2-super-server - Firebird Super Server - an RDBMS based on InterBase 6.0 code firebird2-utils-classic - Utilities for Firebird - an RDBMS based on InterBase 6.0 code firebird2-utils-super - Utilities for Firebird - an RDBMS based on InterBase 6.0 code libfbclient1 - Firebird client library libfbembed1 - Firebird embedded client/server library Changes: firebird2 (1.5.3.4870-11) unstable; urgency=high . * Urgency high to fix FTBFS with gurrent gcc. No bug filed. . * Update gcc4.1.dpatch - Drop parameters for templated destructors to work around gcc 4.1 weirdness (4.0 and 4.2 have no problem with these) Files: 0d0c7fc6490ee7ec9613e2e0052b9d2c 1016 misc optional firebird2_1.5.3.4870-11.dsc 3027d3dca4458daf211e65905fd091d9 401021 misc optional firebird2_1.5.3.4870-11.diff.gz ea71b9dbbef1d2909667fccaa0914cba 235652 misc optional firebird2-common_1.5.3.4870-11_all.deb da488ad6da74f87584c24dd081da99bf 1196374 misc optional firebird2-super-server_1.5.3.4870-11_i386.deb bc62bfba41632ab4113a0fe869fd8c40 382488 misc optional firebird2-classic-server_1.5.3.4870-11_i386.deb 9e286020230eb1c9df8f0a6ca2f774c4 379440 libs optional libfbclient1_1.5.3.4870-11_i386.deb 761de073fb53e82c2bd94078bba4ad1e 1014740 libs optional libfbembed1_1.5.3.4870-11_i386.deb 530c2efb3c0a33bbadae067d00f614cd 522766 misc optional firebird2-server-common_1.5.3.4870-11_i386.deb d3831de6983ea8f0650406a7c6f613b9 1017330 utils optional firebird2-utils-super_1.5.3.4870-11_i386.deb 288222d06fe8e8e0b2177b77a447dc46 992390 utils optional firebird2-utils-classic_1.5.3.4870-11_i386.deb 345cadd7acc94d789f027adb0b6fd2b9 274128 libdevel optional firebird2-dev_1.5.3.4870-11_i386.deb 3fac439691699ff6630cb8a0e08c944f 346008 doc optional firebird2-examples_1.5.3.4870-11_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFNytypFNRmenyx0cRAoHnAJ9Lf9tB5VbbsP1fdP4fua/sEY/+HwCfZ9z7 uS/Hia5mfgedcOwO8syyRJw= =NdLw -END PGP SIGNATURE- Accepted: firebird2-classic-server_1.5.3.4870-11_i386.deb to pool/main/f/firebird2/firebird2-classic-server_1.5.3.4870-11_i386.deb firebird2-common_1.5.3.4870-11_all.deb to pool/main/f/firebird2/firebird2-common_1.5.3.4870-11_all.deb firebird2-dev_1.5.3.4870-11_i386.deb to pool/main/f/firebird2/firebird2-dev_1.5.3.4870-11_i386.deb firebird2-examples_1.5.3.4870-11_i386.deb to pool/main/f/firebird2/firebird2-examples_1.5.3.4870-11_i386.deb firebird2-server-common_1.5.3.4870-11_i386.deb to pool/main/f/firebird2/firebird2-server-common_1.5.3.4870-11_i386.deb firebird2-super-server_1.5.3.4870-11_i386.deb to pool/main/f/firebird2/firebird2-super-server_1.5.3.4870-11_i386.deb firebird2-utils-classic_1.5.3.4870-11_i386.deb to pool/main/f/firebird2/firebird2-utils-classic_1.5.3.4870-11_i386.deb firebird2-utils-super_1.5.3.4870-11_i386.deb to pool/main/f/firebird2/firebird2-utils-super_1.5.3.4870-11_i386.deb firebird2_1.5.3.4870-11.diff.gz to pool/main/f/firebird2/firebird2_1.5.3.4870-11.diff.gz firebird2_1.5.3.4870-11.dsc to pool/main/f/firebird2/firebird2_1.5.3.4870-11.dsc libfbclient1_1.5.3.4870-11_i386.deb to pool/main/f/firebird2/libfbclient1_1.5.3.4870-11_i386.deb libfbembed1_1.5.3.4870-11_i386.deb to pool/main/f/firebird2/libfbembed1_1.5.3.4870-11_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gwget2 0.97-2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 09:34:22 +0200 Source: gwget2 Binary: gwget epiphany-extension-gwget Architecture: source amd64 Version: 0.97-2 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Michael Ablassmeier [EMAIL PROTECTED] Description: epiphany-extension-gwget - Gwget extension for Epiphany web browser gwget - GNOME front-end for wget Changes: gwget2 (0.97-2) unstable; urgency=low . * QA upload. * Set maintainer to QA Group; Orphaned: #391407 * Package has been orphaned, remove Uploaders: field. * Conforms with latest Standards Version 3.7.2 Files: 7ce38d8ffe81bed9981d6ad02e7294df 735 gnome optional gwget2_0.97-2.dsc 8b89031dde7877031e29061c21e63242 160142 gnome optional gwget2_0.97-2.diff.gz 93d34016e57e00a64f05aeb8897d93d6 213550 gnome optional gwget_0.97-2_amd64.deb f3c54cc2d2144e8d292c377bc0dfb494 11888 gnome optional epiphany-extension-gwget_0.97-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFNzISEFV7g4B8rCURAmj6AKDLDXzH8mbEJlPoiWLgHos8u3ScsACgmiOn oVAjfdndKOWoq5H2I1CtvNA= =JpHq -END PGP SIGNATURE- Accepted: epiphany-extension-gwget_0.97-2_amd64.deb to pool/main/g/gwget2/epiphany-extension-gwget_0.97-2_amd64.deb gwget2_0.97-2.diff.gz to pool/main/g/gwget2/gwget2_0.97-2.diff.gz gwget2_0.97-2.dsc to pool/main/g/gwget2/gwget2_0.97-2.dsc gwget_0.97-2_amd64.deb to pool/main/g/gwget2/gwget_0.97-2_amd64.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted dlume 0.2.4-3 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 09:23:52 +0200 Source: dlume Binary: dlume Architecture: source amd64 Version: 0.2.4-3 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Michael Ablassmeier [EMAIL PROTECTED] Description: dlume - handy and easy to use addressbook Closes: 268800 Changes: dlume (0.2.4-3) unstable; urgency=low . * QA upload. (ACK NMU; Closes: #268800) * Set maintainer to QA Group; Orphaned: #391423 * Conforms with latest Standards Version 3.7.2 Files: ac64187e124a06aa467062c920f06cb0 606 utils optional dlume_0.2.4-3.dsc 516cd194fa6e729d857b55763b2bc070 6795 utils optional dlume_0.2.4-3.diff.gz 63fb83029bf840b0605b325d5fe9c1cb 120192 utils optional dlume_0.2.4-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFNzG5EFV7g4B8rCURAiOYAJ469f5dTatjHazwMxVS96oYu6ER6gCfemrx T+ZbmcK0kmprEOjDOhS451M= =jE50 -END PGP SIGNATURE- Accepted: dlume_0.2.4-3.diff.gz to pool/main/d/dlume/dlume_0.2.4-3.diff.gz dlume_0.2.4-3.dsc to pool/main/d/dlume/dlume_0.2.4-3.dsc dlume_0.2.4-3_amd64.deb to pool/main/d/dlume/dlume_0.2.4-3_amd64.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libtermios-ruby 0.9.4-6 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 10:03:02 +0200 Source: libtermios-ruby Binary: libtermios-ruby libtermios-ruby1.8 Architecture: source all amd64 Version: 0.9.4-6 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Michael Ablassmeier [EMAIL PROTECTED] Description: libtermios-ruby - termios simple wrapper for ruby libtermios-ruby1.8 - termios simple wrapper for ruby 1.8 Changes: libtermios-ruby (0.9.4-6) unstable; urgency=low . * QA upload. * Set maintainer to QA Group; Orphaned: #391425 * Conforms with latest Standards Version 3.7.2 Files: 42c807b613aa37f4e53e7d820a98f298 640 devel optional libtermios-ruby_0.9.4-6.dsc b552488fa967c760a59300463bfad29b 1580 devel optional libtermios-ruby_0.9.4-6.diff.gz 7994731de0686406cb25ea8e10350318 1912 devel optional libtermios-ruby_0.9.4-6_all.deb 7eb427ab054c3045ccb953495ce191de 14170 devel optional libtermios-ruby1.8_0.9.4-6_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFNzJzEFV7g4B8rCURAvEwAJ4w2QtiZwSAmimDezbQl2xff4D4DwCeN8PC /2t1NnIQaMChNTt2ERE7MIA= =Olm4 -END PGP SIGNATURE- Accepted: libtermios-ruby1.8_0.9.4-6_amd64.deb to pool/main/libt/libtermios-ruby/libtermios-ruby1.8_0.9.4-6_amd64.deb libtermios-ruby_0.9.4-6.diff.gz to pool/main/libt/libtermios-ruby/libtermios-ruby_0.9.4-6.diff.gz libtermios-ruby_0.9.4-6.dsc to pool/main/libt/libtermios-ruby/libtermios-ruby_0.9.4-6.dsc libtermios-ruby_0.9.4-6_all.deb to pool/main/libt/libtermios-ruby/libtermios-ruby_0.9.4-6_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fpm 0.60-2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 09:31:37 +0200 Source: fpm Binary: fpm Architecture: source amd64 Version: 0.60-2 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Michael Ablassmeier [EMAIL PROTECTED] Description: fpm- Secure password manager Closes: 363418 Changes: fpm (0.60-2) unstable; urgency=low . * QA upload. * Set maintainer to QA Group; Orphaned: #391419 * Fix spelling mistake in Description (Closes: #363418) * Conforms with latest Standards Version 3.7.2 Files: 5c38dbb55f6f000d1d7138b54bac980d 601 gnome optional fpm_0.60-2.dsc db40dbeb806d621588c264607ffc8931 20976 gnome optional fpm_0.60-2.diff.gz 5a37dc636322085a376452459e5fac60 82276 gnome optional fpm_0.60-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFNzHiEFV7g4B8rCURAuK5AJ9wkD7hrsC4oiE/GvJYcDkSOW5leQCg3ryJ pL7JdeZjZO6/XANtw7ExMW8= =wNM/ -END PGP SIGNATURE- Accepted: fpm_0.60-2.diff.gz to pool/main/f/fpm/fpm_0.60-2.diff.gz fpm_0.60-2.dsc to pool/main/f/fpm/fpm_0.60-2.dsc fpm_0.60-2_amd64.deb to pool/main/f/fpm/fpm_0.60-2_amd64.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted nzb 0.1.6-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 15 Oct 2006 14:43:26 +0300 Source: nzb Binary: nzb Architecture: source amd64 Version: 0.1.6-1 Distribution: unstable Urgency: low Maintainer: Mattias Nordstrom [EMAIL PROTECTED] Changed-By: Mattias Nordstrom [EMAIL PROTECTED] Description: nzb- An nzb based Usenet binary grabber Changes: nzb (0.1.6-1) unstable; urgency=low . * New upstream release. * Removed build-dep on libglib2.0-dev, as libqt4-dev now does that as it should. Files: 02e42bc995562f669533eddfc329198e 611 net optional nzb_0.1.6-1.dsc 11aa9c8c8863e9c289ec503e881a5b76 32859 net optional nzb_0.1.6.orig.tar.gz b1ac64b8521badb6d4edb295498d75c9 4125 net optional nzb_0.1.6-1.diff.gz 9a0fa1bffd695b69c55f564a2231c989 98568 net optional nzb_0.1.6-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFNy+9wKTxHeBrP5cRAuNvAKCwmoDIPf+HkjWMiDQGvANz+qN93wCfSxNP YVtuOJKE/aVA0Vq5kM0sMMo= =/SpR -END PGP SIGNATURE- Accepted: nzb_0.1.6-1.diff.gz to pool/main/n/nzb/nzb_0.1.6-1.diff.gz nzb_0.1.6-1.dsc to pool/main/n/nzb/nzb_0.1.6-1.dsc nzb_0.1.6-1_amd64.deb to pool/main/n/nzb/nzb_0.1.6-1_amd64.deb nzb_0.1.6.orig.tar.gz to pool/main/n/nzb/nzb_0.1.6.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted wallpaper-tray 0.4.6-4 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 10:22:18 +0200 Source: wallpaper-tray Binary: wallpaper-tray Architecture: source amd64 Version: 0.4.6-4 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Michael Ablassmeier [EMAIL PROTECTED] Description: wallpaper-tray - wallpaper changing utility for GNOME Changes: wallpaper-tray (0.4.6-4) unstable; urgency=low . * QA upload. * Set maintainer to QA Group; Orphaned: #391406 * Conforms with latest Standards Version 3.7.2 Files: e061360715bb373dc35b5abbb6533807 639 gnome optional wallpaper-tray_0.4.6-4.dsc b664743c637c4c4960a053913c67f774 2264 gnome optional wallpaper-tray_0.4.6-4.diff.gz 63c80770f354d00463b281d2d0aadfbb 24808 gnome optional wallpaper-tray_0.4.6-4_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFNzaTEFV7g4B8rCURArR5AKCcSGBkzqBOhLbhNsysV7lH7PTqHQCgkkkP f1+78BrITeCsFpriZKjjD20= =cFMR -END PGP SIGNATURE- Accepted: wallpaper-tray_0.4.6-4.diff.gz to pool/main/w/wallpaper-tray/wallpaper-tray_0.4.6-4.diff.gz wallpaper-tray_0.4.6-4.dsc to pool/main/w/wallpaper-tray/wallpaper-tray_0.4.6-4.dsc wallpaper-tray_0.4.6-4_amd64.deb to pool/main/w/wallpaper-tray/wallpaper-tray_0.4.6-4_amd64.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted moodle 1.6.3-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 11:37:40 +0200 Source: moodle Binary: moodle Architecture: source all Version: 1.6.3-1 Distribution: unstable Urgency: low Maintainer: Isaac Clerencia [EMAIL PROTECTED] Changed-By: Isaac Clerencia [EMAIL PROTECTED] Description: moodle - Course Management System for Online Learning Changes: moodle (1.6.3-1) unstable; urgency=low . * New upstream release Files: 7e5fc1aaba3255a4d95e98ec3f28f726 652 web optional moodle_1.6.3-1.dsc 2f9f3fcf83ab0f18c409f3a48e07eae2 7465709 web optional moodle_1.6.3.orig.tar.gz 75473f11acff6ce9424db60dbbdd00a8 15624 web optional moodle_1.6.3-1.diff.gz 5239a93c333d7abc10afb7610504a6e7 6530696 web optional moodle_1.6.3-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Signed by Isaac Clerencia [EMAIL PROTECTED] iD8DBQFFN0epQET2GFTmct4RAjI8AKCCKourooiRvmajvrwRgfi6I1XkKwCfUVKB rT87RbVaKvslBdI0tzFpzt8= =Jf3m -END PGP SIGNATURE- Accepted: moodle_1.6.3-1.diff.gz to pool/main/m/moodle/moodle_1.6.3-1.diff.gz moodle_1.6.3-1.dsc to pool/main/m/moodle/moodle_1.6.3-1.dsc moodle_1.6.3-1_all.deb to pool/main/m/moodle/moodle_1.6.3-1_all.deb moodle_1.6.3.orig.tar.gz to pool/main/m/moodle/moodle_1.6.3.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gforge 4.5.14-15 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 11:09:37 +0200 Source: gforge Binary: gforge-lists-mailman gforge-db-postgresql gforge-mta-postfix gforge-shell-ldap gforge gforge-common gforge-web-apache gforge-mta-exim gforge-mta-courier gforge-ftp-proftpd gforge-shell-postgresql gforge-mta-exim4 gforge-dns-bind9 gforge-ldap-openldap Architecture: source all Version: 4.5.14-15 Distribution: unstable Urgency: low Maintainer: Roland Mas [EMAIL PROTECTED] Changed-By: Roland Mas [EMAIL PROTECTED] Description: gforge - collaborative development tool - meta-package gforge-common - collaborative development tool - shared files gforge-db-postgresql - collaborative development tool - database (using PostgreSQL) gforge-dns-bind9 - collaborative development tool - DNS management (using Bind9) gforge-ftp-proftpd - collaborative development tool - FTP management (using ProFTPd) gforge-ldap-openldap - collaborative development tool - LDAP directory (using OpenLDAP) gforge-lists-mailman - collaborative development tool - mailing-lists (using Mailman) gforge-mta-courier - collaborative development tool - mail tools (using Courier) gforge-mta-exim - collaborative development tool - mail tools (using Exim) gforge-mta-exim4 - collaborative development tool - mail tools (using Exim 4) gforge-mta-postfix - collaborative development tool - mail tools (using Postfix) gforge-shell-ldap - collaborative development tool - shell accounts (using LDAP) gforge-shell-postgresql - collaborative development tool - shell accounts (using PostgreSQL gforge-web-apache - collaborative development tool - web part (using Apache) Closes: 394022 Changes: gforge (4.5.14-15) unstable; urgency=low . * [Roland] sql2ldif.pl: Get the user password from nss_shadow, since it cannot be found in nss_passwd any longer due to the recent NSS/PAM reorg, patch from Julien Cristau [EMAIL PROTECTED] (closes: #394022). Files: 46e7601d3f9f16ad138225c11863b164 939 devel optional gforge_4.5.14-15.dsc 6a4e64b4992a9ea3739a15295cf9242e 49045 devel optional gforge_4.5.14-15.diff.gz becb212e2852c04e2e3ea9ed60bca4c8 78682 devel optional gforge_4.5.14-15_all.deb 827c2eb74fb44a1f4dae0f7b8d8e0b28 1008398 devel optional gforge-common_4.5.14-15_all.deb 1e69be7a761abb48c2ddc591e4e1c108 699048 devel optional gforge-web-apache_4.5.14-15_all.deb ce21d62b68935dcb0a25abcd87af5956 205346 devel optional gforge-db-postgresql_4.5.14-15_all.deb d8c7e6ff8b486c094080ab2353dcb97d 85638 devel optional gforge-mta-exim4_4.5.14-15_all.deb 6f9bfd6a70346ff478fb0cc6abde873e 85144 devel optional gforge-mta-exim_4.5.14-15_all.deb e45eab6053ba879aeaa1b923b7c1b9c0 85050 devel optional gforge-mta-postfix_4.5.14-15_all.deb d24ff1462fd6bcbb4e6691215a137008 74500 devel optional gforge-mta-courier_4.5.14-15_all.deb f4401205f1726f1cd07caee79d9b2041 83106 devel optional gforge-shell-ldap_4.5.14-15_all.deb dd8de269d22b16d5eebfef4f8de22bf1 84670 devel optional gforge-shell-postgresql_4.5.14-15_all.deb 8c0083986c31a6d65043da9684351157 83676 devel optional gforge-ftp-proftpd_4.5.14-15_all.deb bcdaa350b6cd5c994d4c2a926f2b3845 92640 devel optional gforge-ldap-openldap_4.5.14-15_all.deb 5f0083e2334db46469903b704595d460 94104 devel optional gforge-dns-bind9_4.5.14-15_all.deb ee96b3c178460a28dfdb739b9f44784f 80596 devel optional gforge-lists-mailman_4.5.14-15_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFN0LyDqdWtRRIQ/URApqVAJwJuRrHt+8EEQEpMsHCHe6OhQmodwCcD+vO gaM2/F4flY8oyQmDDeMKTJQ= =G4I1 -END PGP SIGNATURE- Accepted: gforge-common_4.5.14-15_all.deb to pool/main/g/gforge/gforge-common_4.5.14-15_all.deb gforge-db-postgresql_4.5.14-15_all.deb to pool/main/g/gforge/gforge-db-postgresql_4.5.14-15_all.deb gforge-dns-bind9_4.5.14-15_all.deb to pool/main/g/gforge/gforge-dns-bind9_4.5.14-15_all.deb gforge-ftp-proftpd_4.5.14-15_all.deb to pool/main/g/gforge/gforge-ftp-proftpd_4.5.14-15_all.deb gforge-ldap-openldap_4.5.14-15_all.deb to pool/main/g/gforge/gforge-ldap-openldap_4.5.14-15_all.deb gforge-lists-mailman_4.5.14-15_all.deb to pool/main/g/gforge/gforge-lists-mailman_4.5.14-15_all.deb gforge-mta-courier_4.5.14-15_all.deb to pool/main/g/gforge/gforge-mta-courier_4.5.14-15_all.deb gforge-mta-exim4_4.5.14-15_all.deb to pool/main/g/gforge/gforge-mta-exim4_4.5.14-15_all.deb gforge-mta-exim_4.5.14-15_all.deb to pool/main/g/gforge/gforge-mta-exim_4.5.14-15_all.deb gforge-mta-postfix_4.5.14-15_all.deb to pool/main/g/gforge/gforge-mta-postfix_4.5.14-15_all.deb gforge-shell-ldap_4.5.14-15_all.deb to pool/main/g/gforge/gforge-shell-ldap_4.5.14-15_all.deb gforge-shell-postgresql_4.5.14-15_all.deb to pool/main/g/gforge/gforge-shell-postgresql_4.5.14-15_all.deb gforge-web-apache_4.5.14-15_all.deb to pool/main/g/gforge/gforge-web-apache_4.5.14-15_all.deb gforge_4.5.14-15.diff.gz to pool/main/g/gforge/gforge_4.5.14-15.diff.gz gforge_4.5.14-15.dsc
Accepted gnome-menus 2.16.0-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 11:41:08 +0200 Source: gnome-menus Binary: python-gmenu libgnome-menu2 gnome-menus libgnome-menu-dev Architecture: source i386 Version: 2.16.0-2 Distribution: unstable Urgency: low Maintainer: Sebastien Bacher [EMAIL PROTECTED] Changed-By: Loic Minier [EMAIL PROTECTED] Description: gnome-menus - an implementation of the freedesktop menu specification for GNOME libgnome-menu-dev - an implementation of the freedesktop menu specification for GNOME libgnome-menu2 - an implementation of the freedesktop menu specification for GNOME python-gmenu - an implementation of the freedesktop menu specification for GNOME Changes: gnome-menus (2.16.0-2) unstable; urgency=low . * Upload to unstable. . gnome-menus (2.16.0-1) experimental; urgency=low . * New upstream release; no API change. . gnome-menus (2.15.91-1) experimental; urgency=low . * New upstream development releases, with API additions. - Target at experimental. - Bump up shlibs to = 2.15.4. - Update patches: 03_kde-legacydirs, 04_settings-legacydir, 05_debian_menu, 06_menus_rename, 07_gnomevfs, 70_reautogen. * Add CDBS' utils. Files: 34d6aa68320e0d7a4b2cce6439182f45 1559 gnome optional gnome-menus_2.16.0-2.dsc 7d983812257875ba4c0ea40fb1513eb1 168203 gnome optional gnome-menus_2.16.0-2.diff.gz 93e4a8d3821e45f8d943243f320b9105 141520 gnome optional gnome-menus_2.16.0-2_i386.deb 04ce0a153c7cd87d7c42ba341804a540 60926 gnome optional libgnome-menu2_2.16.0-2_i386.deb c8ad0b1796370ce6d15bce747477a701 70572 libdevel optional libgnome-menu-dev_2.16.0-2_i386.deb 5b7b2fb91a16fbbad2dd1e21af794f45 37732 python optional python-gmenu_2.16.0-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFN0r94VUX8isJIMARAldyAKC7SMLCp9aP6uv+PT1dvGcUWctSVACgnX5c 7U18A5O7mHYnvAB1XRCdAB4= =HM+L -END PGP SIGNATURE- Accepted: gnome-menus_2.16.0-2.diff.gz to pool/main/g/gnome-menus/gnome-menus_2.16.0-2.diff.gz gnome-menus_2.16.0-2.dsc to pool/main/g/gnome-menus/gnome-menus_2.16.0-2.dsc gnome-menus_2.16.0-2_i386.deb to pool/main/g/gnome-menus/gnome-menus_2.16.0-2_i386.deb libgnome-menu-dev_2.16.0-2_i386.deb to pool/main/g/gnome-menus/libgnome-menu-dev_2.16.0-2_i386.deb libgnome-menu2_2.16.0-2_i386.deb to pool/main/g/gnome-menus/libgnome-menu2_2.16.0-2_i386.deb python-gmenu_2.16.0-2_i386.deb to pool/main/g/gnome-menus/python-gmenu_2.16.0-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted texlive-extra 2005.dfsg.2-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 18 Oct 2006 13:01:44 +0200 Source: texlive-extra Binary: texlive-pstricks texlive-plain-extra texlive-formats-extra texlive-latex-extra texlive-latex3 texlive-chemistry texlive-generic-extra texlive-games texlive-publishers texlive-fonts-extra texlive-bibtex-extra texlive-math-extra Architecture: source all Version: 2005.dfsg.2-2 Distribution: unstable Urgency: low Maintainer: Debian TeX Maintainers [EMAIL PROTECTED] Changed-By: Norbert Preining [EMAIL PROTECTED] Description: texlive-bibtex-extra - TeX Live: Extra BibTeX styles texlive-chemistry - TeX Live: Chemical typesetting texlive-fonts-extra - TeX Live: Extra fonts texlive-formats-extra - TeX Live: Extra formats texlive-games - TeX Live: Games typesetting (chess, etc) texlive-generic-extra - TeX Live: Miscellaneous extra generic macros texlive-latex-extra - TeX Live: LaTeX supplementary packages texlive-latex3 - TeX Live: Experiment LaTeX3 packages texlive-math-extra - TeX Live: Advanced math typesetting texlive-plain-extra - TeX Live: Plain TeX supplementary packages texlive-pstricks - TeX Live: PSTricks packages texlive-publishers - TeX Live: Support for publishers Closes: 382870 389467 Changes: texlive-extra (2005.dfsg.2-2) unstable; urgency=low . * remove the invalid conflict tl-latex-extra - latex-beamer, as this was part of tl-latex-recommended, and is now factored out. (Closes: #382870, #389467) Files: da17b351c4e18ef7152ff417665d6e40 1040 tex optional texlive-extra_2005.dfsg.2-2.dsc 16705b5da71bb6dfd340bd94791b5105 246461 tex optional texlive-extra_2005.dfsg.2-2.diff.gz b2a8e3a80a969e4e452a6a56c98d30f1 2668058 tex optional texlive-bibtex-extra_2005.dfsg.2-2_all.deb 304b7113eda8bb3aaafd02ba2c9820d4 1989670 tex optional texlive-formats-extra_2005.dfsg.2-2_all.deb 4fea804ea239cc1cc684a343079c5c6e 1706814 tex optional texlive-generic-extra_2005.dfsg.2-2_all.deb 2d1be60974e28615e75441e1480105ee 2313842 tex optional texlive-math-extra_2005.dfsg.2-2_all.deb 34c0cc5fbb470100b0c820f025e96cdc 1019942 tex optional texlive-plain-extra_2005.dfsg.2-2_all.deb 9bf0162532b8e4ab5d9222725bf18e86 71614278 tex optional texlive-latex-extra_2005.dfsg.2-2_all.deb b2973137365c12a00055158393b87c2e 137020 tex optional texlive-latex3_2005.dfsg.2-2_all.deb 0e67df80d50b024c82fdebb34484f43b 35784464 tex optional texlive-fonts-extra_2005.dfsg.2-2_all.deb ca73c96dfbf83f026d442beb94a94a5b 300556 tex optional texlive-chemistry_2005.dfsg.2-2_all.deb 24b0cee4b51ed5b11be6f9123ef45648 457822 tex optional texlive-games_2005.dfsg.2-2_all.deb 673b4eefc97d2eef3d3e7896869ada26 21840752 tex optional texlive-pstricks_2005.dfsg.2-2_all.deb 35255250df86e59a1ea1901faa1135c2 8909748 tex optional texlive-publishers_2005.dfsg.2-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFN0H60r9KownFsJQRAvhMAJ9uYoi2F2xqNsQvVxpRtvaXJi/clwCghBLU +HI7DBaEbrII5GLz0tJUvOM= =yZKj -END PGP SIGNATURE- Accepted: texlive-bibtex-extra_2005.dfsg.2-2_all.deb to pool/main/t/texlive-extra/texlive-bibtex-extra_2005.dfsg.2-2_all.deb texlive-chemistry_2005.dfsg.2-2_all.deb to pool/main/t/texlive-extra/texlive-chemistry_2005.dfsg.2-2_all.deb texlive-extra_2005.dfsg.2-2.diff.gz to pool/main/t/texlive-extra/texlive-extra_2005.dfsg.2-2.diff.gz texlive-extra_2005.dfsg.2-2.dsc to pool/main/t/texlive-extra/texlive-extra_2005.dfsg.2-2.dsc texlive-fonts-extra_2005.dfsg.2-2_all.deb to pool/main/t/texlive-extra/texlive-fonts-extra_2005.dfsg.2-2_all.deb texlive-formats-extra_2005.dfsg.2-2_all.deb to pool/main/t/texlive-extra/texlive-formats-extra_2005.dfsg.2-2_all.deb texlive-games_2005.dfsg.2-2_all.deb to pool/main/t/texlive-extra/texlive-games_2005.dfsg.2-2_all.deb texlive-generic-extra_2005.dfsg.2-2_all.deb to pool/main/t/texlive-extra/texlive-generic-extra_2005.dfsg.2-2_all.deb texlive-latex-extra_2005.dfsg.2-2_all.deb to pool/main/t/texlive-extra/texlive-latex-extra_2005.dfsg.2-2_all.deb texlive-latex3_2005.dfsg.2-2_all.deb to pool/main/t/texlive-extra/texlive-latex3_2005.dfsg.2-2_all.deb texlive-math-extra_2005.dfsg.2-2_all.deb to pool/main/t/texlive-extra/texlive-math-extra_2005.dfsg.2-2_all.deb texlive-plain-extra_2005.dfsg.2-2_all.deb to pool/main/t/texlive-extra/texlive-plain-extra_2005.dfsg.2-2_all.deb texlive-pstricks_2005.dfsg.2-2_all.deb to pool/main/t/texlive-extra/texlive-pstricks_2005.dfsg.2-2_all.deb texlive-publishers_2005.dfsg.2-2_all.deb to pool/main/t/texlive-extra/texlive-publishers_2005.dfsg.2-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted quota 3.14-3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 09:02:04 +0200 Source: quota Binary: quota Architecture: source i386 Version: 3.14-3 Distribution: unstable Urgency: low Maintainer: Michael Meskes [EMAIL PROTECTED] Changed-By: Michael Meskes [EMAIL PROTECTED] Description: quota - implementation of the disk quota system Closes: 393972 Changes: quota (3.14-3) unstable; urgency=low . * Added missing build dependency on libssl-dev, closes: #393972 Files: 2068fe139e6e7d3843b3133ce1aad2e8 639 admin optional quota_3.14-3.dsc 5d19aae9a2a975974bd920280f5b8fd3 30985 admin optional quota_3.14-3.diff.gz c5138e7436484c5c18059e393726aa7c 462682 admin optional quota_3.14-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFNyXmVkEm8inxm9ERAseiAJwI4ap0/I2P4SoDo4Qw2hkUOeba1QCdGXrm OW894dJEsl85VDVZAl7Eu/0= =bUmD -END PGP SIGNATURE- Accepted: quota_3.14-3.diff.gz to pool/main/q/quota/quota_3.14-3.diff.gz quota_3.14-3.dsc to pool/main/q/quota/quota_3.14-3.dsc quota_3.14-3_i386.deb to pool/main/q/quota/quota_3.14-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libgnome 2.16.0-2 (source all i386)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 11:28:12 +0200
Source: libgnome
Binary: libgnome2-common libgnome2-0 libgnome2-doc libgnome2-dev
Architecture: source all i386
Version: 2.16.0-2
Distribution: unstable
Urgency: low
Maintainer: OndÅej Surý [EMAIL PROTECTED]
Changed-By: Loic Minier [EMAIL PROTECTED]
Description:
libgnome2-0 - The GNOME 2 library - runtime files
libgnome2-common - The GNOME 2 library - common files
libgnome2-dev - The GNOME 2 library - development files
libgnome2-doc - The GNOME 2 library - documentation files
Changes:
libgnome (2.16.0-2) unstable; urgency=low
.
[ Josselin Mouette ]
* libgnome2-common.gconf-defaults: remove the background settings,
they are set by desktop-base now.
.
[ Loic Minier ]
* Upload to unstable.
* Add CDBS' utils.
.
libgnome (2.16.0-1) experimental; urgency=low
.
* New upstream release.
* Correct build-dependency on libesd.
* Use clean-la.mk and gnome-version.mk.
* Use ${gnome:(Next)Version} for the libgnome2-common dependency.
* Build-depend on gnome-pkg-tools 0.7.
* Remove lots of unneeded build-dependencies (libxslt, zlib, libbz2,
libxml).
* Require intltool 0.35.0.
.
libgnome (2.15.2-1) experimental; urgency=low
.
* New upstream development releases; no API changes.
- Target at experimental.
- Drop 05_Makefile.in.in, seems fixed.
Files:
84fed061c5832b3d44cfe71b0478e935 1599 devel optional libgnome_2.16.0-2.dsc
ec532d402adfabf730201198d9ff42ec 9093 devel optional libgnome_2.16.0-2.diff.gz
17762e8638c69e95286d453ab7e27a5e 809820 libs optional
libgnome2-common_2.16.0-2_all.deb
61e40a52065cd41ab05247d1fd1c8504 108348 doc optional
libgnome2-doc_2.16.0-2_all.deb
5475ae471672c5da9364d16be6309e07 109056 libs optional
libgnome2-0_2.16.0-2_i386.deb
0f6cee76affe25343fa41ae09624 109736 libdevel optional
libgnome2-dev_2.16.0-2_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFN0aA4VUX8isJIMARAv28AJ9BPJn7MhddC75vnGOr542W/Ur5hgCgrdsk
uWIVHgkvfNXR5XhIDGHlGKM=
=pPng
-END PGP SIGNATURE-
Accepted:
libgnome2-0_2.16.0-2_i386.deb
to pool/main/libg/libgnome/libgnome2-0_2.16.0-2_i386.deb
libgnome2-common_2.16.0-2_all.deb
to pool/main/libg/libgnome/libgnome2-common_2.16.0-2_all.deb
libgnome2-dev_2.16.0-2_i386.deb
to pool/main/libg/libgnome/libgnome2-dev_2.16.0-2_i386.deb
libgnome2-doc_2.16.0-2_all.deb
to pool/main/libg/libgnome/libgnome2-doc_2.16.0-2_all.deb
libgnome_2.16.0-2.diff.gz
to pool/main/libg/libgnome/libgnome_2.16.0-2.diff.gz
libgnome_2.16.0-2.dsc
to pool/main/libg/libgnome/libgnome_2.16.0-2.dsc
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted coco-cs 20060919-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 18 Oct 2006 18:00:00 +0100 Source: coco-cs Binary: coco-cs Architecture: source all Version: 20060919-2 Distribution: unstable Urgency: low Maintainer: Loeberbauer Markus [EMAIL PROTECTED] Changed-By: Markus Loeberbauer [EMAIL PROTECTED] Description: coco-cs- Coco/R Compiler Generator (C-Sharp Version) Closes: 393811 Changes: coco-cs (20060919-2) unstable; urgency=low . * Update to Debian Policy Standards Version 3.7.2 * Set MONO_SHARED_DIR to temporary directory to enable the build servers to build the package (Closes: #393811). Files: 7900264aedae248c5db13a88893d7d48 528 devel optional coco-cs_20060919-2.dsc 2dcfd53197afa0ecfe481acde7d5f926 49384 devel optional coco-cs_20060919-2.tar.gz d56378e26dde790b6acb8ac22a7376fc 72304 devel optional coco-cs_20060919-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFN0rqq7SPDcPCS94RArTnAJ9B2bEIjcQEkOlU6o44rVBQrAMT9wCgs7au ajJXNTSLrV2jASlR9Y2ztAo= =y4FL -END PGP SIGNATURE- Accepted: coco-cs_20060919-2.dsc to pool/main/c/coco-cs/coco-cs_20060919-2.dsc coco-cs_20060919-2.tar.gz to pool/main/c/coco-cs/coco-cs_20060919-2.tar.gz coco-cs_20060919-2_all.deb to pool/main/c/coco-cs/coco-cs_20060919-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libapache2-mod-encoding 20040616-4.2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 12:31:32 +0200 Source: libapache2-mod-encoding Binary: libapache2-mod-encoding Architecture: source amd64 Version: 20040616-4.2 Distribution: unstable Urgency: medium Maintainer: Tatsuki Sugiura [EMAIL PROTECTED] Changed-By: Michael Ablassmeier [EMAIL PROTECTED] Description: libapache2-mod-encoding - Apache2 module for non-ascii filename interoperability Closes: 391779 393019 Changes: libapache2-mod-encoding (20040616-4.2) unstable; urgency=medium . * Non-maintainer upload. * Fix FTBS, add path to mod_encoding.o to gcc call Closes: #393019 * Replace obsolete dependency on apache2-common with apache2.2-common (Closes: #391779) Files: 95b96acc4def69ebd9234039c07aa38f 762 web optional libapache2-mod-encoding_20040616-4.2.dsc 688396e401c09be27d20a4a53a235dfe 4649 web optional libapache2-mod-encoding_20040616-4.2.diff.gz c2ace6b133ed831996b5a4f785f0fc3e 7736 web optional libapache2-mod-encoding_20040616-4.2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFN1TkEFV7g4B8rCURAsWPAKCBVZJi1F6LomzonLia9+KGFR+bXwCfQ35r C5bwS/Pq7SK8re3Nz5eMIso= =onuL -END PGP SIGNATURE- Accepted: libapache2-mod-encoding_20040616-4.2.diff.gz to pool/main/liba/libapache2-mod-encoding/libapache2-mod-encoding_20040616-4.2.diff.gz libapache2-mod-encoding_20040616-4.2.dsc to pool/main/liba/libapache2-mod-encoding/libapache2-mod-encoding_20040616-4.2.dsc libapache2-mod-encoding_20040616-4.2_amd64.deb to pool/main/liba/libapache2-mod-encoding/libapache2-mod-encoding_20040616-4.2_amd64.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted texlive-bin 2005.dfsg.2-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 10:27:51 +0200 Source: texlive-bin Binary: texlive-extra-utils texlive-pdfetex texlive-lang-indic texlive-omega texlive-font-utils texlive-metapost texlive-base-bin texlive-music Architecture: source i386 Version: 2005.dfsg.2-2 Distribution: unstable Urgency: low Maintainer: Debian TeX Maintainers [EMAIL PROTECTED] Changed-By: Norbert Preining [EMAIL PROTECTED] Description: texlive-base-bin - TeX Live: Essential binaries texlive-extra-utils - TeX Live: TeX auxiliary programs texlive-font-utils - TeX Live: TeX font-related programs texlive-lang-indic - TeX Live: Indic texlive-metapost - TeX Live: MetaPost (and Metafont) drawing packages texlive-music - TeX Live: Music typesetting texlive-omega - TeX Live: Omega texlive-pdfetex - TeX Live: pdfTeX Closes: 392641 393189 394028 Changes: texlive-bin (2005.dfsg.2-2) unstable; urgency=low . * update the debian patch for updmap(.1) (Closes: #393189) * adjust built-in search paths of libkpathsea to the Debian defaults (Closes: #392641) * include patch for pdfetex to support newer TTF fonts (Closes: #394028) Files: 72f578eddec07a8deadf7c134419a2ea 1043 tex optional texlive-bin_2005.dfsg.2-2.dsc 5fb85f5b63d37d8fc0f209d9050418bf 94371 tex optional texlive-bin_2005.dfsg.2-2.diff.gz dae8f9c8c279854a84eb195a331d280f 12020248 tex optional texlive-base-bin_2005.dfsg.2-2_i386.deb 26cf0dba6db00da1316d1db0d8312cc6 732744 tex optional texlive-extra-utils_2005.dfsg.2-2_i386.deb 8dffe401a09732d2c04b8ce5e48a20f4 1379680 tex optional texlive-font-utils_2005.dfsg.2-2_i386.deb 283ffc5441392b9660c90c1ec709695b 6187058 tex optional texlive-metapost_2005.dfsg.2-2_i386.deb 0bd7e63758ba58db414ce360d032e6f8 3060472 tex optional texlive-omega_2005.dfsg.2-2_i386.deb 47631b89ff3912f5864edf0608abfb30 3025128 tex optional texlive-pdfetex_2005.dfsg.2-2_i386.deb 23c29f979eb2c4b1fb442d0d3b1ce806 418258 tex optional texlive-music_2005.dfsg.2-2_i386.deb d5e30f24e14470c20a6610e8c5762478 8817436 tex optional texlive-lang-indic_2005.dfsg.2-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFN0H00r9KownFsJQRAhViAKCEsejt/T+Lj6wEE5mX9ZvUKqyygQCeO2A6 sxF95qbg3rFPehMm+7yaKko= =Hl/B -END PGP SIGNATURE- Accepted: texlive-base-bin_2005.dfsg.2-2_i386.deb to pool/main/t/texlive-bin/texlive-base-bin_2005.dfsg.2-2_i386.deb texlive-bin_2005.dfsg.2-2.diff.gz to pool/main/t/texlive-bin/texlive-bin_2005.dfsg.2-2.diff.gz texlive-bin_2005.dfsg.2-2.dsc to pool/main/t/texlive-bin/texlive-bin_2005.dfsg.2-2.dsc texlive-extra-utils_2005.dfsg.2-2_i386.deb to pool/main/t/texlive-bin/texlive-extra-utils_2005.dfsg.2-2_i386.deb texlive-font-utils_2005.dfsg.2-2_i386.deb to pool/main/t/texlive-bin/texlive-font-utils_2005.dfsg.2-2_i386.deb texlive-lang-indic_2005.dfsg.2-2_i386.deb to pool/main/t/texlive-bin/texlive-lang-indic_2005.dfsg.2-2_i386.deb texlive-metapost_2005.dfsg.2-2_i386.deb to pool/main/t/texlive-bin/texlive-metapost_2005.dfsg.2-2_i386.deb texlive-music_2005.dfsg.2-2_i386.deb to pool/main/t/texlive-bin/texlive-music_2005.dfsg.2-2_i386.deb texlive-omega_2005.dfsg.2-2_i386.deb to pool/main/t/texlive-bin/texlive-omega_2005.dfsg.2-2_i386.deb texlive-pdfetex_2005.dfsg.2-2_i386.deb to pool/main/t/texlive-bin/texlive-pdfetex_2005.dfsg.2-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted clamav 0.88.5-2 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 12:30:07 +0100 Source: clamav Binary: clamav libclamav-dev clamav-dbg clamav-milter clamav-base clamav-freshclam clamav-testfiles clamav-daemon libclamav1 clamav-docs Architecture: source i386 all Version: 0.88.5-2 Distribution: unstable Urgency: high Maintainer: Stephen Gran [EMAIL PROTECTED] Changed-By: Stephen Gran [EMAIL PROTECTED] Description: clamav - antivirus scanner for Unix clamav-base - base package for clamav, an anti-virus utility for Unix clamav-daemon - antivirus scanner daemon clamav-dbg - debug symbols for clamav clamav-docs - documentation package for clamav, an anti-virus utility for Unix clamav-freshclam - downloads clamav virus databases from the Internet clamav-milter - antivirus scanner for sendmail clamav-testfiles - use these files to test that your Antivirus program works libclamav-dev - clam Antivirus library development files libclamav1 - virus scanner library Closes: 393672 Changes: clamav (0.88.5-2) unstable; urgency=high . * Fix FTBFS with nullmailer (closes: #393672) * Urgency high because this was keeping security fixes out of testing * Noted here since they were unavailable at previous upload time: - IDEF1597 is CVE-2006-4182 (libclamav/rebuildpe.c) - IDEF1736 is CVE-2006-5295 (libclamav/chmunpack.c) Files: b4247cb721f87041621af2981db932c2 880 utils optional clamav_0.88.5-2.dsc 69e38220380d6b4eaa5d42408cca2d3e 489856 utils optional clamav_0.88.5-2.diff.gz 181228ffe86966acafb465f0648be3d4 174292 utils optional clamav-base_0.88.5-2_all.deb b990609b4aaa319f135c151726082de8 131418 utils optional clamav-testfiles_0.88.5-2_all.deb 8dc43270ecfc05352a8095f29d526c16 817264 utils optional clamav-docs_0.88.5-2_all.deb cc874b50d5b8c753a3be4e3b629e3371 269654 libs optional libclamav1_0.88.5-2_i386.deb bea49975db1a9f4eb6422fa64dce0739 161764 utils optional clamav_0.88.5-2_i386.deb 5f806e7ac6aa163345f1569832c200df 137212 utils optional clamav-daemon_0.88.5-2_i386.deb 705fd0eee4b47cd0bf5c6754b2f4cf1e 7033522 utils optional clamav-freshclam_0.88.5-2_i386.deb bece35c772ac3f0ff51a5e725d8a43f1 133782 utils extra clamav-milter_0.88.5-2_i386.deb 9777c8e3c6ef48ed418edc11e9bda4b9 261220 libdevel optional libclamav-dev_0.88.5-2_i386.deb 26bb933a94a3b0137d9c8f0c48d87408 449262 utils extra clamav-dbg_0.88.5-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFN2aqSYIMHOpZA44RAnNsAKDRCsnV0NYnxaStRLlJ1tu9zO0hkwCguITA 2FdSySnTaMnMSycxs8p/o6c= =7jwc -END PGP SIGNATURE- Accepted: clamav-base_0.88.5-2_all.deb to pool/main/c/clamav/clamav-base_0.88.5-2_all.deb clamav-daemon_0.88.5-2_i386.deb to pool/main/c/clamav/clamav-daemon_0.88.5-2_i386.deb clamav-dbg_0.88.5-2_i386.deb to pool/main/c/clamav/clamav-dbg_0.88.5-2_i386.deb clamav-docs_0.88.5-2_all.deb to pool/main/c/clamav/clamav-docs_0.88.5-2_all.deb clamav-freshclam_0.88.5-2_i386.deb to pool/main/c/clamav/clamav-freshclam_0.88.5-2_i386.deb clamav-milter_0.88.5-2_i386.deb to pool/main/c/clamav/clamav-milter_0.88.5-2_i386.deb clamav-testfiles_0.88.5-2_all.deb to pool/main/c/clamav/clamav-testfiles_0.88.5-2_all.deb clamav_0.88.5-2.diff.gz to pool/main/c/clamav/clamav_0.88.5-2.diff.gz clamav_0.88.5-2.dsc to pool/main/c/clamav/clamav_0.88.5-2.dsc clamav_0.88.5-2_i386.deb to pool/main/c/clamav/clamav_0.88.5-2_i386.deb libclamav-dev_0.88.5-2_i386.deb to pool/main/c/clamav/libclamav-dev_0.88.5-2_i386.deb libclamav1_0.88.5-2_i386.deb to pool/main/c/clamav/libclamav1_0.88.5-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mod-bt 0.0.19+p4.2213-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 17 Oct 2006 18:27:31 +0100 Source: mod-bt Binary: libbtutil0-dev libbttracker-utils libbttracker0 libapache2-mod-bt libbttracker0-dev php5-apache2-mod-bt libbtutil-utils libbtutil0 php4-apache2-mod-bt libapache2-mod-bt-dev libapache2-modbt-perl libnet-bittorrent-libbt-tracker-perl Architecture: source i386 Version: 0.0.19+p4.2213-1 Distribution: unstable Urgency: low Maintainer: Tyler 'Crackerjack' MacDonald [EMAIL PROTECTED] Changed-By: Tyler 'Crackerjack' MacDonald [EMAIL PROTECTED] Description: libapache2-mod-bt - BitTorrent tracker for the Apache2 web server libapache2-mod-bt-dev - Header files for mod_bt libapache2-modbt-perl - Perl bindings for mod_bt libbttracker-utils - BitTorrent Tracker Library - Utility Programs libbttracker0 - BitTorrent Tracker Library libbttracker0-dev - BitTorrent Tracker library - Development files libbtutil-utils - BitTorrent utility programs libbtutil0 - BitTorrent utility library libbtutil0-dev - BitTorrent utility library - Development files libnet-bittorrent-libbt-tracker-perl - Perl bindings for libbttracker php4-apache2-mod-bt - PHP bindings for mod_bt php5-apache2-mod-bt - PHP bindings for mod_bt Closes: 382688 391636 Changes: mod-bt (0.0.19+p4.2213-1) unstable; urgency=low . * Fall in line with unstable's move to apache-2.2 (Closes: #391636) . * Reduce priority of packages depending on db4 (Closes: #382688) Files: 4203b2e4482e045b730f3f1f6da2d6dd 1023 net optional mod-bt_0.0.19+p4.2213-1.dsc ea369e2f90b0249a83a5c863917f84f9 655403 net optional mod-bt_0.0.19+p4.2213.orig.tar.gz 5e0cbd00c1fd9fc8f85a985d506332c7 5731 net optional mod-bt_0.0.19+p4.2213-1.diff.gz e4ec060f268c4ab56b0da8741e315eab 110856 libs optional libbtutil0_0.0.19+p4.2213-1_i386.deb 9b7fd7b8bdc2583eda7ae7178c19dbdb 25432 libdevel optional libbtutil0-dev_0.0.19+p4.2213-1_i386.deb 612d8c25d42351ca8e197a5001473df6 5944 libs optional libbtutil-utils_0.0.19+p4.2213-1_i386.deb c3050d984d1ee35df22349fef7bd298f 27174 libs optional libbttracker0_0.0.19+p4.2213-1_i386.deb 82d310fbcc15ec9611174fc2221cb1e5 37342 libdevel extra libbttracker0-dev_0.0.19+p4.2213-1_i386.deb 0adbc250989c1c41feb6a50dffdb2230 18218 net optional libbttracker-utils_0.0.19+p4.2213-1_i386.deb 90cb50e3bfc52862a20b69b805d18f17 10064 web optional libapache2-mod-bt_0.0.19+p4.2213-1_i386.deb 4982c8874ada2a4d32a4b686f6c4c4e3 1170 libdevel extra libapache2-mod-bt-dev_0.0.19+p4.2213-1_i386.deb 31b51cef7d82d42a7d47c7032840701e 11226 perl optional libapache2-modbt-perl_0.0.19+p4.2213-1_i386.deb 14b05d3892ce7bb995928adeca7bf627 51542 perl optional libnet-bittorrent-libbt-tracker-perl_0.0.19+p4.2213-1_i386.deb cb4dd8834cd6fa93a4f5857c805df610 48080 web optional php5-apache2-mod-bt_0.0.19+p4.2213-1_i386.deb cbc057be3812138d5abdac5621ed5830 44664 web optional php4-apache2-mod-bt_0.0.19+p4.2213-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFN0MmpGK1HsL+5c0RAmqnAJ9TIJCg8Wz1PAPmwWKooq4Wd+8CWgCdFC6h Cs7Fz4u+7fuZVUttrHQWAmo= =aOEj -END PGP SIGNATURE- Accepted: libapache2-mod-bt-dev_0.0.19+p4.2213-1_i386.deb to pool/main/m/mod-bt/libapache2-mod-bt-dev_0.0.19+p4.2213-1_i386.deb libapache2-mod-bt_0.0.19+p4.2213-1_i386.deb to pool/main/m/mod-bt/libapache2-mod-bt_0.0.19+p4.2213-1_i386.deb libapache2-modbt-perl_0.0.19+p4.2213-1_i386.deb to pool/main/m/mod-bt/libapache2-modbt-perl_0.0.19+p4.2213-1_i386.deb libbttracker-utils_0.0.19+p4.2213-1_i386.deb to pool/main/m/mod-bt/libbttracker-utils_0.0.19+p4.2213-1_i386.deb libbttracker0-dev_0.0.19+p4.2213-1_i386.deb to pool/main/m/mod-bt/libbttracker0-dev_0.0.19+p4.2213-1_i386.deb libbttracker0_0.0.19+p4.2213-1_i386.deb to pool/main/m/mod-bt/libbttracker0_0.0.19+p4.2213-1_i386.deb libbtutil-utils_0.0.19+p4.2213-1_i386.deb to pool/main/m/mod-bt/libbtutil-utils_0.0.19+p4.2213-1_i386.deb libbtutil0-dev_0.0.19+p4.2213-1_i386.deb to pool/main/m/mod-bt/libbtutil0-dev_0.0.19+p4.2213-1_i386.deb libbtutil0_0.0.19+p4.2213-1_i386.deb to pool/main/m/mod-bt/libbtutil0_0.0.19+p4.2213-1_i386.deb libnet-bittorrent-libbt-tracker-perl_0.0.19+p4.2213-1_i386.deb to pool/main/m/mod-bt/libnet-bittorrent-libbt-tracker-perl_0.0.19+p4.2213-1_i386.deb mod-bt_0.0.19+p4.2213-1.diff.gz to pool/main/m/mod-bt/mod-bt_0.0.19+p4.2213-1.diff.gz mod-bt_0.0.19+p4.2213-1.dsc to pool/main/m/mod-bt/mod-bt_0.0.19+p4.2213-1.dsc mod-bt_0.0.19+p4.2213.orig.tar.gz to pool/main/m/mod-bt/mod-bt_0.0.19+p4.2213.orig.tar.gz php4-apache2-mod-bt_0.0.19+p4.2213-1_i386.deb to pool/main/m/mod-bt/php4-apache2-mod-bt_0.0.19+p4.2213-1_i386.deb php5-apache2-mod-bt_0.0.19+p4.2213-1_i386.deb to pool/main/m/mod-bt/php5-apache2-mod-bt_0.0.19+p4.2213-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted kipina 0.1.1-3 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 13:12:05 +0200 Source: kipina Binary: kipina Architecture: source amd64 Version: 0.1.1-3 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Michael Ablassmeier [EMAIL PROTECTED] Description: kipina - training program to log physical activities of athletes Closes: 364161 Changes: kipina (0.1.1-3) unstable; urgency=low . * QA upload. * Set maintainer to QA Group; Orphaned: #391418 * Fix spelling mistake in Package Description Closes: #364161 * Conforms with latest Standards Version 3.7.2 Files: ad91af44cce4121f33ed6b2a1b9aaac3 641 utils optional kipina_0.1.1-3.dsc 5a8d686964a178eb778c50427da68e11 63856 utils optional kipina_0.1.1-3.diff.gz 60874a62f14e8871cdb4be343200fb56 150200 utils optional kipina_0.1.1-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFN154EFV7g4B8rCURAvomAKDtBVfodpOvhdxxLeJ3MwpNTds7iACfemRc Vel+NHTehoL5L4LJZ2lVqkI= =3YMk -END PGP SIGNATURE- Accepted: kipina_0.1.1-3.diff.gz to pool/main/k/kipina/kipina_0.1.1-3.diff.gz kipina_0.1.1-3.dsc to pool/main/k/kipina/kipina_0.1.1-3.dsc kipina_0.1.1-3_amd64.deb to pool/main/k/kipina/kipina_0.1.1-3_amd64.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fai 3.1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 14:46:32 +0200 Source: fai Binary: fai-client fai-server fai-doc fai-quickstart fai-nfsroot Architecture: source all Version: 3.1 Distribution: unstable Urgency: medium Maintainer: Thomas Lange [EMAIL PROTECTED] Changed-By: Thomas Lange [EMAIL PROTECTED] Description: fai-client - Fully Automatic Installation client package fai-doc- Documentation for FAI fai-nfsroot - Fully Automatic Installation nfsroot package fai-quickstart - Fully Automatic Installation quickstart package fai-server - Fully Automatic Installation server package Closes: 390343 390345 390367 390680 391639 392032 Changes: fai (3.1) unstable; urgency=medium . * Makefile: force bash in Makefile, fixes FTBFS in ubuntu * rename action dirinst to dirinstall (closes: #390345) * fai-cd: fix wrong path for sources.list (closes: #391639) * scripts/FAIBASE/10-misc: use ainsl instead of echo ... * lib/create_ramdisk: make /var/discover writeable * make-fai-nfsroot: create directory var/discover, add option -h and usage() subroutine * subroutines: move find's maxdepth option to the left, prevent multiple fai softupdate running simultaneously (closes: #390680), move disk_var.sh from FAI 2.X installation old to new location rename variable sndhostname to sendhostname * get-config-dir*: replace \s and \S in expr with regex using [:space:], so it also works for sarge's version of expr * subroutines-liux: add test if base.tgz exists (closes: #390343), sources.list must be used from /etc/apt during normal installation * fai: add option -u,--hostname (closes: #390367), create /dev/shm/network if directory not already exists (needed for initrd kernels) * LAST/50-misc: do not fail if hardware clock can't be set * fcopy: swap call of postinst and set_mode * install_packages: add missing package list to yum and rpm calls (closes: #392032) * rename sndmon() to sendmon() * fai-start-stop-daemon: start udevd (needed for ubuntu) and do not fake it, add carriage return * package_config/DEMO: remove rstatd since it buggy atm Files: af335a767e91aab7df2bed5c73112f25 591 admin extra fai_3.1.dsc c16a99121db24e37c2df4ea2caab54e1 192226 admin extra fai_3.1.tar.gz 1895a76ec2692ef56a6b81af6799f808 97594 admin extra fai-client_3.1_all.deb a3cd0d4d564c5113feea0ec2b8aabe0e 560830 doc extra fai-doc_3.1_all.deb bd95177d1dfc22cb000474a2ca4ae87a 35628 admin extra fai-server_3.1_all.deb 9990e3a9c98ea21f6adf302a5002b93e 1892 admin extra fai-quickstart_3.1_all.deb a6bda5b80678162973211b645fec609d 44182 admin extra fai-nfsroot_3.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFN3Re3BPlTqubZv0RAoxhAKCAne3R04/aX3PPiXcUx9IP0kglHwCgmXKy BFCoizdp3iwxpdHOnxgk6fA= =oR6i -END PGP SIGNATURE- Accepted: fai-client_3.1_all.deb to pool/main/f/fai/fai-client_3.1_all.deb fai-doc_3.1_all.deb to pool/main/f/fai/fai-doc_3.1_all.deb fai-nfsroot_3.1_all.deb to pool/main/f/fai/fai-nfsroot_3.1_all.deb fai-quickstart_3.1_all.deb to pool/main/f/fai/fai-quickstart_3.1_all.deb fai-server_3.1_all.deb to pool/main/f/fai/fai-server_3.1_all.deb fai_3.1.dsc to pool/main/f/fai/fai_3.1.dsc fai_3.1.tar.gz to pool/main/f/fai/fai_3.1.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ncurses 5.5-5 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 12:01:00 +0200 Source: ncurses Binary: ncurses-base lib64ncurses5 libncursesw5-dev libncursesw5-dbg ncurses-bin libncurses5 libncursesw5 libncurses5-dev ncurses-term lib32ncurses5-dev lib32ncurses5 libncurses5-dbg lib64ncurses5-dev Architecture: source i386 all Version: 5.5-5 Distribution: unstable Urgency: medium Maintainer: Daniel Baumann [EMAIL PROTECTED] Changed-By: Daniel Baumann [EMAIL PROTECTED] Description: lib64ncurses5 - Shared libraries for terminal handling (64-bit) lib64ncurses5-dev - Developer's libraries for ncurses (64-bit) libncurses5 - Shared libraries for terminal handling libncurses5-dbg - Debugging/profiling libraries for ncurses libncurses5-dev - Developer's libraries and docs for ncurses libncursesw5 - Shared libraries for terminal handling (wide character support) libncursesw5-dbg - Debugging/profiling libraries for ncurses libncursesw5-dev - Developer's libraries for ncursesw ncurses-base - Descriptions of common terminal types ncurses-bin - Terminal-related programs and man pages ncurses-term - Additional terminal type definitions Closes: 390169 Changes: ncurses (5.5-5) unstable; urgency=medium . * Fixed /usr/share/doc symlinks (Closes: #390169). Files: ee5f14143a6d5b69447a36828a4e4bfa 970 libs standard ncurses_5.5-5.dsc b84ac188dec53c49c74d6d88601591e8 268281 libs standard ncurses_5.5-5.diff.gz 8345d763df9bf494351f6703a556cd02 300218 libs required libncurses5_5.5-5_i386.deb fba1c4532e18ce58a9422682f75340d0 1396250 libdevel optional libncurses5-dev_5.5-5_i386.deb 4af38f37f0bc890145c091c36596e028 1428066 libdevel extra libncurses5-dbg_5.5-5_i386.deb e4a8bfd90670eb0d7499baa7f6b42b0c 319914 libs important libncursesw5_5.5-5_i386.deb ebf386c0220ab3798643ef90c30c12e8 440212 libdevel optional libncursesw5-dev_5.5-5_i386.deb 0088049e757b5f9f354794f0436dfb85 1592822 libdevel extra libncursesw5-dbg_5.5-5_i386.deb 7719e2a87e17fba8659916a29e98e2b6 321058 libs optional lib64ncurses5_5.5-5_i386.deb dab933a756e118a1c8fb30ba93ff7c55 386860 libdevel optional lib64ncurses5-dev_5.5-5_i386.deb 1c7fb27ca101173bd6c6651244a781cf 214212 utils required ncurses-bin_5.5-5_i386.deb 44a72a29f61cd0d039a1b84ac5e1edc4 12986 utils required ncurses-base_5.5-5_all.deb 488b1566b30059afaaf9f0a6bb641fd6 330824 admin standard ncurses-term_5.5-5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFN1tr+C5cwEsrK54RArzFAKC7vOnnMuHgn5/B6roAS0jhZWsFCQCeIJcI XjfnLQFhuV1ch6gYTDeyEyQ= =4NSE -END PGP SIGNATURE- Accepted: lib64ncurses5-dev_5.5-5_i386.deb to pool/main/n/ncurses/lib64ncurses5-dev_5.5-5_i386.deb lib64ncurses5_5.5-5_i386.deb to pool/main/n/ncurses/lib64ncurses5_5.5-5_i386.deb libncurses5-dbg_5.5-5_i386.deb to pool/main/n/ncurses/libncurses5-dbg_5.5-5_i386.deb libncurses5-dev_5.5-5_i386.deb to pool/main/n/ncurses/libncurses5-dev_5.5-5_i386.deb libncurses5_5.5-5_i386.deb to pool/main/n/ncurses/libncurses5_5.5-5_i386.deb libncursesw5-dbg_5.5-5_i386.deb to pool/main/n/ncurses/libncursesw5-dbg_5.5-5_i386.deb libncursesw5-dev_5.5-5_i386.deb to pool/main/n/ncurses/libncursesw5-dev_5.5-5_i386.deb libncursesw5_5.5-5_i386.deb to pool/main/n/ncurses/libncursesw5_5.5-5_i386.deb ncurses-base_5.5-5_all.deb to pool/main/n/ncurses/ncurses-base_5.5-5_all.deb ncurses-bin_5.5-5_i386.deb to pool/main/n/ncurses/ncurses-bin_5.5-5_i386.deb ncurses-term_5.5-5_all.deb to pool/main/n/ncurses/ncurses-term_5.5-5_all.deb ncurses_5.5-5.diff.gz to pool/main/n/ncurses/ncurses_5.5-5.diff.gz ncurses_5.5-5.dsc to pool/main/n/ncurses/ncurses_5.5-5.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xmms-jess 2.9.1-8.1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 12:55:26 +0200 Source: xmms-jess Binary: xmms-jess Architecture: source amd64 Version: 2.9.1-8.1 Distribution: unstable Urgency: low Maintainer: John Lightsey [EMAIL PROTECTED] Changed-By: Michael Ablassmeier [EMAIL PROTECTED] Description: xmms-jess - visualization plugin for XMMS using various 2D and 3D methods Closes: 392543 Changes: xmms-jess (2.9.1-8.1) unstable; urgency=low . * Non-maintainer upload. * Fix FTBFS, thanks Andreas Jochens for reporting and Patch. Closes: #392543 Files: fcfbcdae14ddd5001d6b31d244380267 625 sound optional xmms-jess_2.9.1-8.1.dsc 5d1b413669e9ee5543c3f8edef0d18de 5192 sound optional xmms-jess_2.9.1-8.1.diff.gz 0fac5e7a9c92abe072c358da9f49b2d6 25294 sound optional xmms-jess_2.9.1-8.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFN1rqEFV7g4B8rCURAsFcAKCmEAhNrITB0pfHfUJKcrqNy/TaZgCg3hTO NLsblWf9PVUqG4O2gty6AFs= =huyq -END PGP SIGNATURE- Accepted: xmms-jess_2.9.1-8.1.diff.gz to pool/main/x/xmms-jess/xmms-jess_2.9.1-8.1.diff.gz xmms-jess_2.9.1-8.1.dsc to pool/main/x/xmms-jess/xmms-jess_2.9.1-8.1.dsc xmms-jess_2.9.1-8.1_amd64.deb to pool/main/x/xmms-jess/xmms-jess_2.9.1-8.1_amd64.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libclass-dbi-perl 3.0.15-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 13:44:12 +0100 Source: libclass-dbi-perl Binary: libclass-dbi-perl Architecture: source all Version: 3.0.15-1 Distribution: unstable Urgency: low Maintainer: Stephen Quinney [EMAIL PROTECTED] Changed-By: Stephen Quinney [EMAIL PROTECTED] Description: libclass-dbi-perl - A convenient abstraction layer to a database Changes: libclass-dbi-perl (3.0.15-1) unstable; urgency=low . * New upstream release * Build-Depends on libdbd-sqlite3-perl (= 1.13-1.1) which fixes a previous FTBFS caused by a bug in the earlier version of that package. Files: ee98f367bb16e76eea3f913f9a6f92bc 899 perl optional libclass-dbi-perl_3.0.15-1.dsc 07a7ab2c8977e50c050767c2ec532df0 105331 perl optional libclass-dbi-perl_3.0.15.orig.tar.gz 1c663ae6fcf5d8ad8cf9338880d4f97d 3107 perl optional libclass-dbi-perl_3.0.15-1.diff.gz e2b4575b6e4516d34b83d2967efa67d4 143042 perl optional libclass-dbi-perl_3.0.15-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFN3VVITGblEwaW+URAmnyAJ4i4UVrOIUa9tgcFWh9bQvsbY9K7ACeP6nF csKFRyY3j4CqWUtWCZfCskM= =BmLG -END PGP SIGNATURE- Accepted: libclass-dbi-perl_3.0.15-1.diff.gz to pool/main/libc/libclass-dbi-perl/libclass-dbi-perl_3.0.15-1.diff.gz libclass-dbi-perl_3.0.15-1.dsc to pool/main/libc/libclass-dbi-perl/libclass-dbi-perl_3.0.15-1.dsc libclass-dbi-perl_3.0.15-1_all.deb to pool/main/libc/libclass-dbi-perl/libclass-dbi-perl_3.0.15-1_all.deb libclass-dbi-perl_3.0.15.orig.tar.gz to pool/main/libc/libclass-dbi-perl/libclass-dbi-perl_3.0.15.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xine-ui 0.99.4+cvs20061019-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 09:50:49 +0200 Source: xine-ui Binary: xine-ui Architecture: source i386 Version: 0.99.4+cvs20061019-1 Distribution: unstable Urgency: low Maintainer: Siggi Langauf [EMAIL PROTECTED] Changed-By: Reinhard Tartler [EMAIL PROTECTED] Description: xine-ui- the xine video player, user interface Closes: 384006 Changes: xine-ui (0.99.4+cvs20061019-1) unstable; urgency=low . * new upstream snapshot: * Bug fix: xine-ui: fails to start, thanks to [EMAIL PROTECTED] (Closes: #384006). Fix committed on Okt 19 * add XS-X-Vcs-Bzr tag in debian/control Files: 93d34e7b31b311fbb2d9183ffc0b3f9e 1133 graphics optional xine-ui_0.99.4+cvs20061019-1.dsc 14ec9e0f076b65ef4bfd2ae9cde75364 2204090 graphics optional xine-ui_0.99.4+cvs20061019.orig.tar.gz a989da20ee1a6fc588e7246d1be18c07 10131 graphics optional xine-ui_0.99.4+cvs20061019-1.diff.gz 2a9ebcfd63719f702637e0a52994fa79 1512368 graphics optional xine-ui_0.99.4+cvs20061019-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFN2YZ+C5cwEsrK54RAr9nAJ9eGF6p6FgUTAedMLr7+06O2mGTjACeN0cV w2AXuaaHo8NdC80AjyaMF6c= =tPR/ -END PGP SIGNATURE- Accepted: xine-ui_0.99.4+cvs20061019-1.diff.gz to pool/main/x/xine-ui/xine-ui_0.99.4+cvs20061019-1.diff.gz xine-ui_0.99.4+cvs20061019-1.dsc to pool/main/x/xine-ui/xine-ui_0.99.4+cvs20061019-1.dsc xine-ui_0.99.4+cvs20061019-1_i386.deb to pool/main/x/xine-ui/xine-ui_0.99.4+cvs20061019-1_i386.deb xine-ui_0.99.4+cvs20061019.orig.tar.gz to pool/main/x/xine-ui/xine-ui_0.99.4+cvs20061019.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted hddtemp 0.3-beta15-30 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 Oct 2006 14:50:09 +0200 Source: hddtemp Binary: hddtemp Architecture: source amd64 Version: 0.3-beta15-30 Distribution: unstable Urgency: medium Maintainer: Aurelien Jarno [EMAIL PROTECTED] Changed-By: Aurelien Jarno [EMAIL PROTECTED] Description: hddtemp- Utility to monitor the temperature of your hard drive Changes: hddtemp (0.3-beta15-30) unstable; urgency=medium . * Remove a space in the printed temperature when a disk is not present in hddtemp.db. Files: 9eb727cf3b01771f38eec49aaef33b1a 618 utils extra hddtemp_0.3-beta15-30.dsc f7c4893c057e6e419b1e9e03d3f6adcd 35830 utils extra hddtemp_0.3-beta15-30.diff.gz c512274093dbe1c3d67513c5fcf5 47288 utils extra hddtemp_0.3-beta15-30_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFN3V8w3ao2vG823MRAlJnAJ0e5dulu/Fpog8QG8tPr7wHXAut9QCcCIhZ Ivj7BBGqAvfXaUcu+dQFCPA= =SENF -END PGP SIGNATURE- Accepted: hddtemp_0.3-beta15-30.diff.gz to pool/main/h/hddtemp/hddtemp_0.3-beta15-30.diff.gz hddtemp_0.3-beta15-30.dsc to pool/main/h/hddtemp/hddtemp_0.3-beta15-30.dsc hddtemp_0.3-beta15-30_amd64.deb to pool/main/h/hddtemp/hddtemp_0.3-beta15-30_amd64.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
