Accepted vstream-client 1.2-6 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 29 Aug 2008 06:26:03 +0100 Source: vstream-client Binary: vstream-client vstream-client-dev Architecture: source i386 Version: 1.2-6 Distribution: unstable Urgency: low Maintainer: Paul Hedderly [EMAIL PROTECTED] Changed-By: Paul Hedderly [EMAIL PROTECTED] Description: vstream-client - A library and utility to fetch media streams from a TIVO vstream-client-dev - Development headers for vstream-client Closes: 496884 496884 Changes: vstream-client (1.2-6) unstable; urgency=low . * Replaces older version to (Closes: #496884) * -dev does not need to depend on -client (Closes: #496884) Checksums-Sha1: eacd0ea49ddfcba9b69e8082612baede3b935b80 1166 vstream-client_1.2-6.dsc c350dc6823415a51775ebfc9b6cbd8b59a396a5b 4210 vstream-client_1.2-6.diff.gz ebd2dbd1135b27013f1c570cf5212fd560ec745f 29564 vstream-client_1.2-6_i386.deb 1b34d7c4f7a276b56a341869f9dc57cdcfd8a638 41424 vstream-client-dev_1.2-6_i386.deb Checksums-Sha256: cc1d372eaccf42e3786a56ddaa94442526d87b5585f7425e2e4d1e04eff19edc 1166 vstream-client_1.2-6.dsc cc7ab136700c42012ac02331ae41a64dfb3480abbf8de2e52e8ac03dd35d841f 4210 vstream-client_1.2-6.diff.gz 1288f684fbf7d413341dd7217efc89cb2d3dbf8b3318b62b976eb0583ecb82a2 29564 vstream-client_1.2-6_i386.deb bca0ea0d5aa9cd5bdff96baa70ca5acb80b0b3725ae48862655299c8591a2f3e 41424 vstream-client-dev_1.2-6_i386.deb Files: 765a0ee569b679b2b86117318231df7a 1166 libs extra vstream-client_1.2-6.dsc 62b85a6714dabd79ba61b35a7f69e6b0 4210 libs extra vstream-client_1.2-6.diff.gz 66c574bce87652ec16ec1329e74b9538 29564 libs extra vstream-client_1.2-6_i386.deb 002204a7ff37248acc6db43023a8dc77 41424 libdevel extra vstream-client-dev_1.2-6_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: GNU Privacy Guard iEYEARECAAYFAki3i5EACgkQx5g40ENjN92ytwCeOhC7M3aemrdpScQhjRd0CCcJ 448AoMdWDWn5EE6a1m2PMHyhhnbF7bXM =4a9D -END PGP SIGNATURE- Accepted: vstream-client-dev_1.2-6_i386.deb to pool/main/v/vstream-client/vstream-client-dev_1.2-6_i386.deb vstream-client_1.2-6.diff.gz to pool/main/v/vstream-client/vstream-client_1.2-6.diff.gz vstream-client_1.2-6.dsc to pool/main/v/vstream-client/vstream-client_1.2-6.dsc vstream-client_1.2-6_i386.deb to pool/main/v/vstream-client/vstream-client_1.2-6_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted vstream-client 1.2-5 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 26 Aug 2008 20:35:25 +0100 Source: vstream-client Binary: vstream-client vstream-client-dev Architecture: source i386 Version: 1.2-5 Distribution: unstable Urgency: low Maintainer: Paul Hedderly [EMAIL PROTECTED] Changed-By: Paul Hedderly [EMAIL PROTECTED] Description: vstream-client - A library and utility to fetch media streams from a TIVO vstream-client-dev - Development headers for vstream-client Changes: vstream-client (1.2-5) unstable; urgency=low . * Non-urgent change slipped in - only the creation of a lintian unclean empty dir. Checksums-Sha1: 5e3710ab8e51ac3b68dfdbfd195c09f7e0650ae0 1166 vstream-client_1.2-5.dsc 1bc959c4f2de82ea6b1b1e3a5b903a9760674b66 4159 vstream-client_1.2-5.diff.gz 04276bd1de3c968378050a94a8941f4618008498 29494 vstream-client_1.2-5_i386.deb 0628be02aa43ff47439ff3cd16fbd26eb188f834 41354 vstream-client-dev_1.2-5_i386.deb Checksums-Sha256: 163424a83a82ba87491d32546fe25e72e8c2c361c845670ba7301a381b2403f0 1166 vstream-client_1.2-5.dsc 038118c604986dfa55fd1d9f4aee8d769c9ef4512e36e4360b79346ce6f53770 4159 vstream-client_1.2-5.diff.gz 3b63d61026c5d05478fa197837d26a0fdb4b0ceac024b99d1d9559d1a656d858 29494 vstream-client_1.2-5_i386.deb 48c48185eac6e7b549524f026b889a1a0cb552f3fcc2e8bb9e084414153b322e 41354 vstream-client-dev_1.2-5_i386.deb Files: 3bf5f1b382b740cfe16537504a6b7b66 1166 libs extra vstream-client_1.2-5.dsc 67ff6e2886ba4a4f4f28ecfa5f27b186 4159 libs extra vstream-client_1.2-5.diff.gz 3be7ab24743be00d270f814fc6fdb81b 29494 libs extra vstream-client_1.2-5_i386.deb d92dcb1b6cff143f92d88f9fa4dde934 41354 libdevel extra vstream-client-dev_1.2-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: GNU Privacy Guard iEYEARECAAYFAki0W+gACgkQx5g40ENjN93n/ACeIetuhSnqKIFZzwWJPWa0BWA7 ZcYAoMUue6s9yqtH28su7v1FB+FcVUsZ =k3d/ -END PGP SIGNATURE- Accepted: vstream-client-dev_1.2-5_i386.deb to pool/main/v/vstream-client/vstream-client-dev_1.2-5_i386.deb vstream-client_1.2-5.diff.gz to pool/main/v/vstream-client/vstream-client_1.2-5.diff.gz vstream-client_1.2-5.dsc to pool/main/v/vstream-client/vstream-client_1.2-5.dsc vstream-client_1.2-5_i386.deb to pool/main/v/vstream-client/vstream-client_1.2-5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted vstream-client 1.2-3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 20 Aug 2008 12:42:44 +0100 Source: vstream-client Binary: vstream-client vstream-client-dev Architecture: source i386 Version: 1.2-3 Distribution: unstable Urgency: low Maintainer: Paul Hedderly [EMAIL PROTECTED] Changed-By: Paul Hedderly [EMAIL PROTECTED] Description: vstream-client - A library and utility to fetch media streams from a TIVO vstream-client-dev - Development headers for vstream-client Closes: 494615 Changes: vstream-client (1.2-3) unstable; urgency=low . * Added Conflicts and Replaces libvstream-dev (Closes: Bug#494615) Checksums-Sha1: 1fedef5260a0e1992bf0b29cf808bd32a76611a6 1166 vstream-client_1.2-3.dsc ae77af4c5486a04804f9df0556a08c799f590ac4 4064 vstream-client_1.2-3.diff.gz cef31c3b562172a3c82a667e504c14bd944de563 67198 vstream-client_1.2-3_i386.deb 07eb9623948a10af8e01e7d59b727bfb8cb6bb18 2810 vstream-client-dev_1.2-3_i386.deb Checksums-Sha256: c1e4917a6d0567ef70d69e9486c7af2371e94c22b45f2a959cb6aa085e716f04 1166 vstream-client_1.2-3.dsc 0488a208a29cecb5c1545e64d2a1fb5fe890a1ba5330a0933cad54a5c00e3a67 4064 vstream-client_1.2-3.diff.gz ed4cb2057bde722259fb62b883a706ee070637301d10d1b9c84421eef0bde6d5 67198 vstream-client_1.2-3_i386.deb 9cbbb34d8f69de628663334802b9fce13a02193f4ba367a62a39a8a84140d7b9 2810 vstream-client-dev_1.2-3_i386.deb Files: a758e32be6c3347174280e52cdb7a2f1 1166 libs extra vstream-client_1.2-3.dsc f8c44bf3ed53e96a09a88f41b249f6d1 4064 libs extra vstream-client_1.2-3.diff.gz 5e45d552d269c33fac0a1d6e31fd4d16 67198 libs extra vstream-client_1.2-3_i386.deb c8a24e79d1256634afb8a18f3eddf86f 2810 libdevel extra vstream-client-dev_1.2-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: GNU Privacy Guard iEYEARECAAYFAkisBlgACgkQx5g40ENjN91mKQCg4C/UvI2yo8JZ1KtkJmjoTzCN kLkAoNB/CvH69aYKfJXzwGgnDdQOV4Qb =Ca00 -END PGP SIGNATURE- Accepted: vstream-client-dev_1.2-3_i386.deb to pool/main/v/vstream-client/vstream-client-dev_1.2-3_i386.deb vstream-client_1.2-3.diff.gz to pool/main/v/vstream-client/vstream-client_1.2-3.diff.gz vstream-client_1.2-3.dsc to pool/main/v/vstream-client/vstream-client_1.2-3.dsc vstream-client_1.2-3_i386.deb to pool/main/v/vstream-client/vstream-client_1.2-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted vstream-client 1.2-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 03 Jun 2008 22:19:01 +0100 Source: vstream-client Binary: vstream-client vstream-client-dev Architecture: source i386 Version: 1.2-2 Distribution: unstable Urgency: low Maintainer: Paul Hedderly [EMAIL PROTECTED] Changed-By: Paul Hedderly [EMAIL PROTECTED] Description: vstream-client - A library and utility to fetch media streams from a TIVO vstream-client-dev - Development headers for vstream-client Changes: vstream-client (1.2-2) unstable; urgency=low . * Removed watch.ex and make rules call makshlibs Checksums-Sha1: 8c309b08d901e01abaa5ab2da15583cc7c41f101 1158 vstream-client_1.2-2.dsc f463203cec39e63145a3315ac9aef01c00585064 80871 vstream-client_1.2.orig.tar.gz b395a2df59dda604c393072f7a34be17bd26c1aa 3890 vstream-client_1.2-2.diff.gz 426efbd7144f1d3eb3b3bbeabec6d0be3ed1fcfd 66838 vstream-client_1.2-2_i386.deb 296980168b39f82debb47639d797a332025bde40 2628 vstream-client-dev_1.2-2_i386.deb Checksums-Sha256: d36fe2ba46811a75efa70ebdc2a62aed09ff32a427c5c82ac421a268366e2928 1158 vstream-client_1.2-2.dsc d1a9790d5c3f0b90dec4b92204f801583ff4c2cea8edde3019ce938ce582bf0c 80871 vstream-client_1.2.orig.tar.gz 4a47ca61c131a0d7f2e9c205533378fba7d473593b8901c89326626469df9d30 3890 vstream-client_1.2-2.diff.gz dbb7d6ebedeac0ad29553b29d0453c0cdb87d97cf5eb707af1c22733e57da83b 66838 vstream-client_1.2-2_i386.deb 26bcab2755e3cac0eb3ac8f54baa5273dd37c0af256856ecd9a4d7c29c79fbcb 2628 vstream-client-dev_1.2-2_i386.deb Files: dec35691ec670f10caf74c9620baa92f 1158 libs extra vstream-client_1.2-2.dsc 3809a96241ecb978737cf32a104769cb 80871 libs extra vstream-client_1.2.orig.tar.gz c5f1065941ac86aec2b29d7cf0e91d50 3890 libs extra vstream-client_1.2-2.diff.gz 213e3e639603e9468b6a7239b3c3f29f 66838 libs extra vstream-client_1.2-2_i386.deb b9d6a7759bc7a4eda2cf5edc95ebd6df 2628 libdevel extra vstream-client-dev_1.2-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: GNU Privacy Guard iD8DBQFIRin7x5g40ENjN90RApAuAJ9ZrR9vgTiwZ3ANKDtJuF8CfyCuYQCfY8rL uW3rEIfZmgqHRG+CAi6SwDg= =rpCV -END PGP SIGNATURE- Accepted: vstream-client-dev_1.2-2_i386.deb to pool/main/v/vstream-client/vstream-client-dev_1.2-2_i386.deb vstream-client_1.2-2.diff.gz to pool/main/v/vstream-client/vstream-client_1.2-2.diff.gz vstream-client_1.2-2.dsc to pool/main/v/vstream-client/vstream-client_1.2-2.dsc vstream-client_1.2-2_i386.deb to pool/main/v/vstream-client/vstream-client_1.2-2_i386.deb vstream-client_1.2.orig.tar.gz to pool/main/v/vstream-client/vstream-client_1.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Fwknop and no answer from a DD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Don Armstrong wrote: On Thu, 12 Jun 2008, Franck Joncourt wrote: I was working on fwknop (forgot to mention it to the BTS), then I saw Luciano Bello was interested as well. I sent an email to him and to the BTS in order to know how much work has been achieved, but still no news. You should actually double check with Paul Hedderly who is responsible for it; you'd also want to Cc: them directly, since they won't get information on those bugs unless they're subscribed to them. Don Armstrong Franck - I have not yet done anything with this, so if you have that's great. Shout if you a tester or help in any way. - -- Cheers Paul -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: GNU Privacy Guard Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIUW7tx5g40ENjN90RArj8AJoC96S7OPJKfFJ4zxzYUXk9FnDMxQCfd+rt qRi0F1pm55OQKdATiG0FpOs= =C2v1 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484717: ITP: gibak -- A better backup system based on Git
Package: wnpp Severity: wishlist Owner: Paul Hedderly [EMAIL PROTECTED] * Package name: gibak Version : 0.3.0 Upstream Author : Mauricio Fernandez [EMAIL PROTECTED] * URL : http://eigenclass.org/hiki/gibak-backup-system-introduction * License : GPL = v2 and LGPL v2.1 Programming Lang: OCaml and bash Description : A better backup system based on Git As far as standard tools go, however, git provides a very nice infrastructure that can be used to build your own system, to wit: * it is more space-efficient than most incremental backup schemes, since it does file compression and both textual *and* binary deltas (in particular, it's better than solutions relying on hardlinks or incremental backups à la tar/cpio) * its transport mechanism is more efficient than rsync's * it is fast: recoving your data is *faster* than cp -a * you keep the full revision history * powerful toolset with a rich vocabulary Gibak retains all the advantages from Git, and supplements it in some key areas: * metadata support * management of submodules (nested Git repositories) * automation of common operations; for instance, a commit consists of several steps: o determining if some files which were committed earlier are ignored now and removing them from the index o adding new and modified files to the index o registering new git submodules and copying them to a special area under .git o committing changes in the index o compaction and optimization of the repository [ I will push a git repo onto colab-maint so if anyone wants to work as a team on this then just shout - especially if you are an OCaml wiz. ] -- Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bruce Perens hosts party at OSCON Wednesday night
On Sat, Aug 06, 2005 at 07:38:47PM +0100, Andrew Suffield wrote: On Thu, Aug 04, 2005 at 01:58:15PM -0300, Humberto Massa Guimar?es wrote: And to boot, an e-mail calling for curriculae for a recruiting party is on-topic to a DEVELOPERS list No. This is why the debian-jobs list exists. Andrew is right - there was perhaps a more appropriate list. Sadly - yet again, the real problem was the approach Adam took. Instead of a gentle friendly prod towards using the right list, Adam replied with a public antagonistic slapping. I suspect Bruce will probably not bother offering invitations to DD's in the future... Sad really. Why are we so quick to point fingers and wind each other (and outsiders) up. Will a new DPL be able to break through this barrier of arrogant selfish one-up-manship? Will all Debian devs ever be able to encourage and build each other up instead of bickering over their preferred method and style of protocol? I'm not hopeful - human nature is overwhelmingly self-centered and self-absorbed. I'd love to be surprised. -- Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: switching to vim-tiny for standard vi?
On Sun, Dec 18, 2005 at 08:56:42PM +0200, Lars Wirzenius wrote: I'm one of the people who prefers nvi over vim. I do so quite strongly, because I find that nvi obeys my fingers and vim does not. The Sounds like you should file a bug against your fingers then. differences are minute, of course, but they are really irritating. Unfortunately, I can't enlist them properly, since my fingers don't talk to me: I notice vim's incompatibility from the fact that my fingers have If your fingers aren't talking to you, perhaps you should also list them as MIA. to keep correcting text under vim, but not under nvi. On days when I'm generally annoyed already, if I accidentally use vim instead of nvi, I can get quite lyrical with my cursing. Funny - on days I'm generally annoyed already and I end up on a machine with nvi as the default vi... I can get quite lyrical with my ranting. For me, vim-tiny would be great! -- Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: switching to vim-tiny for standard vi?
On Tue, Dec 20, 2005 at 02:37:59PM +1000, Anthony Towns wrote: Yeah; vi not behaving like vi by default seems like a showstopper. But that is not the case. vi by default not acting like a very old and (imho) broken version of vi... is not a showstopper. I love vi - and I love the progress vim has made to make use of vi quicker/better/easier. I don't see that the world has to be stuck in 1985 - should we still be shipping a linux kernel version 1? -- Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Alternate proposal for Declassification of debian-private archives
My biggest problem with all this is that it's gonna mean a lot of work - for the 'declassifying team' and for people who want to be bothered about commenting on the process is respect of particular email. Thats time that I feel could be better spent. I do understand the motives... -- Paul On Thu, Dec 01, 2005 at 08:32:59AM -0600, Manoj Srivastava wrote: Hi, Rationale: I have been thinking about the kinds of reasons for not wanting to have a post to -private published. I came up with two major (reasonable) scenarios: a) The post contained sensitive material. In this case, if a reasonable case has been made for the material being sensitive, and one that the declassification teams accepted, then the material should be redacted from the post, and every post it has been quoted in. If it is sensitive in one post, it is sensitive in another. b) I do not want to be associated with the post in question In other words, if this showed up in google it may hurt my future job prospects post ;-). In this case, the post can be published, just every identifying bit about the author needs be redacted from this post and the quotes. This latter action would, in my opinion, allow more of some informative, though heated, discussions to be available to posterity grin. Also, we are, in effect, considering retroactively overturning a published privacy policy; I think that we do need to state up front that the copyright holders wishes would be heeded, even when the post in question is quoted in other emails. Here is a diff from AJ's proposal. I am now formally seeking seconds for this modified proposal, which has explicit guidelines for the most common case for not wantng the posts to be published. manoj -- In accordance with principles of openness and transparency, Debian will seek to declassify and publish posts of historical or ongoing significance made to the Debian Private Mailing List. This process will be undertaken under the following constraints: * The Debian Project Leader will delegate one or more volunteers to form the debian-private declassification team. * The team will automatically declassify and publish posts made to that list that are three or more years old, with the following exceptions: - the author and other individuals quoted in messages being reviewed will be contacted, and allowed between four and eight weeks to comment; - posts that reveal financial information about individuals or organisations other than Debian, will have that information removed; - - requests by the author of a post for that post not to be published - will be honoured; + - If the author makes a resonable case that some material is + sensitive, then that material is redacted from that post and any + other post where it has been quoted + + - If the author indicates he does not wish to be associated with a + post, any identifying information is redacted from that post, + and any quotes in subsequent posts, but the rest of the material + is published. - posts of no historical or other relevance, such as vacation - announcements, or posts that have no content after personal + announcements, or posts that have no content after information is removed, will not be published, unless the author requests they be published; - comments by others who would be affected by the publication of the post will also be taken into account by the declassification team; - the list of posts to be declassified will be made available to developers two weeks before publication, so that the decisions of the team may be overruled by the developer body by General Resolution, if necessary -- in the event such a resolution is introduced (ie, proposed and sponsored), the declassification and publication of messages specified by the resolution will be deferred until the resolution has been voted on. --- -- Happiness adds and multiplies as we divide it with others. Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Let's stop feeding the NVidia cuckoo
On Thu, Mar 24, 2005 at 05:33:50PM +, Henning Makholm wrote: Scripsit Paul Hedderly [EMAIL PROTECTED] What we have is source code (yes code that can be compiled) which is unencumbered, we can modify,compile, distribute etc... whether it is _harder_ to modify or not because of choices the _owner/author_ has made or not... is nothing to do with freedom. What you are showing here is that code that can be compiled is not a working defintion of source code. It not only works, but has been used for a long time. What you are showing is that you have a dislike for source that is hard to modify (fair enough) and would like for it not to be called 'source code' if you feel it is hard to read/modify. 'source code' does not mean 'code that came from the original source untouched' (lets face it, define 'original source' when there is more than one person working on code with different trees, working machines etc...) it literally means code that can be used to generate a binary. So please stop making weird claims about the meaning of words and definitions and state plainly that you don't like hard to read/modify (ugly?) source code and would like Debian to ban using such. We can argue and vote on that... -- Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Let's stop feeding the NVidia cuckoo
On Mon, Mar 07, 2005 at 07:31:22AM -0600, John Hasler wrote: Henning Makholm writes: Yes, but we shouldn't act as if it was a _freedom_ problem. If it was deliberately made bloody horribly ugly and painful in order to make changing it difficult, it's a freedom problem. Not really. How NV choose to do stuff is totally up to NV. What we have is source code (yes code that can be compiled) which is unencumbered, we can modify,compile, distribute etc... whether it is _harder_ to modify or not because of choices the _owner/author_ has made or not... is nothing to do with freedom. -- Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: status of buildds?
I can happily provide two Sun SS20's , one or two U1's and an Acorn RiscPC to help build ARM and Sparc. I'd happily give them a basic install, provide broadband access to them and hand over control to the buildd team. -- Paul On Mon, Mar 14, 2005 at 08:43:40PM -0800, Thomas Bushnell BSG wrote: http://buildd.debian.org/stats/graph-week-big.png For the past week, mipsel has been chugging mightily and made huge progress. But s390 has slipped worse and worse, with only a single machine building packages. Meanwhile, arm made a brief, but valiant attempt, but has been plummeting, and is now nearly down to 91% built. Joining the race to the bottom, is sparc, which has also been sliding. For s390 and sparc, it appears that only one machine is in place building these archs. Meanwhile, lists quite a few machines of those four archs. For arm, we have debussy; for s390 we have raptor and trex; for mipsel we hav vaughan, and for sparc we have vore. vore is a buildd, but the other three four are essentially idle. What would be necessary to leverage these processors and have them building? When there is one buildd, adding another *doubles* the progress you can make! Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted drsync 0.4.3-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 9 Aug 2004 19:57:09 +0100 Source: drsync Binary: drsync Architecture: source all Version: 0.4.3-1 Distribution: unstable Urgency: low Maintainer: Paul Hedderly [EMAIL PROTECTED] Changed-By: Paul Hedderly [EMAIL PROTECTED] Description: drsync - Two-way remote file synchronisation Closes: 226285 248200 Changes: drsync (0.4.3-1) unstable; urgency=low . * New upstream release (Closes: #226285) * Changed binary and manpage from drsync.pl to drsync (Closes: #248200) Files: ee8b5e6d631a080c406b02a738d9b83f 586 misc optional drsync_0.4.3-1.dsc 3b4ffb052c732c74850c5569a8a3e20d 16604 misc optional drsync_0.4.3.orig.tar.gz 5bf70e66d49bb78f3112e4090fee8f01 2034 misc optional drsync_0.4.3-1.diff.gz 60f8adf3efe5a369dc21ff47b98f354b 10492 misc optional drsync_0.4.3-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: GNU Privacy Guard iD8DBQFBF8xOx5g40ENjN90RAk32AKCnFVlpK+HZtQ1Gyo9L77tUquZ4rwCeIM0S iMAdp98tSFnRXpJ0cVXWGMo= =Rq6N -END PGP SIGNATURE- Accepted: drsync_0.4.3-1.diff.gz to pool/main/d/drsync/drsync_0.4.3-1.diff.gz drsync_0.4.3-1.dsc to pool/main/d/drsync/drsync_0.4.3-1.dsc drsync_0.4.3-1_all.deb to pool/main/d/drsync/drsync_0.4.3-1_all.deb drsync_0.4.3.orig.tar.gz to pool/main/d/drsync/drsync_0.4.3.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted drsync 0.4.3-2 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 9 Aug 2004 20:17:18 +0100 Source: drsync Binary: drsync Architecture: source all Version: 0.4.3-2 Distribution: unstable Urgency: low Maintainer: Paul Hedderly [EMAIL PROTECTED] Changed-By: Paul Hedderly [EMAIL PROTECTED] Description: drsync - Two-way remote file synchronisation Changes: drsync (0.4.3-2) unstable; urgency=low . * Changed drsync.pl to drsync in all the documentation. Files: a6a88308b503f8e37c2da0434c7fb002 586 misc optional drsync_0.4.3-2.dsc 8b0e30c8f4c9e967c64448a23568ec47 3611 misc optional drsync_0.4.3-2.diff.gz bc05548c969dfe888e371ecf51c6b25e 10526 misc optional drsync_0.4.3-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: GNU Privacy Guard iD8DBQFBF83ox5g40ENjN90RAqxeAKCS07H3j8bH50FQ1oXNGQlg5KOUiwCglGNH Ba4Yc2D+/Pmv/ow7QRYl4mQ= =2+ol -END PGP SIGNATURE- Accepted: drsync_0.4.3-2.diff.gz to pool/main/d/drsync/drsync_0.4.3-2.diff.gz drsync_0.4.3-2.dsc to pool/main/d/drsync/drsync_0.4.3-2.dsc drsync_0.4.3-2_all.deb to pool/main/d/drsync/drsync_0.4.3-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian-installer beta 1
On Mon, Nov 17, 2003 at 01:44:27AM +0100, Goswin von Brederlow wrote: Julian Mehnle [EMAIL PROTECTED] writes: Brian May wrote: I have tried debian-installer, and found it to be great! I just have three feature requests, if they aren't already supported: [...] 3. Software raid support? That would be great! At least if it means ATARAID-style software RAID. No opinion about LVM-style RAID. My goal is lvm2 support but that needs different kernel-images which are a pain to build for 11 archs. The same image would be needed for low-mem installs (if we want to support 48MB ram systems) so there is some incentive to build them. The inclusion of mdadm would at least enable people to go into a shell and setup their MD devices. Then all you'd need to do is make sure some basic MD options are on in the kernel. -- Paul
Re: 2.5/2.6 IPsec stack should live in a kernel-patch!
On Wed, Oct 01, 2003 at 08:31:47PM -0400, Jim Penny wrote: On Thu, 2 Oct 2003 01:38:45 +0200 [EMAIL PROTECTED] (Domenico Andreoli) wrote: On Wed, Oct 01, 2003 at 05:38:51PM -0500, Steve Langasek wrote: [ObPrivate: this doesn't belong on private. Quote me freely.] On Wed, Oct 01, 2003 at 11:56:14PM +0200, martin f krafft wrote: Thus I propose that Herbert should remove the IPsec patch and make it a separate kernel-patch. If anyone has other objections than I won't do it because it's my choice, I don't feel like it, and there is nothing you can do about it, then please speak up. On the other hand, if you agree with me, let your voice be heard! i'm interested only in the debian kernel without 2.5/2.6 IPsec. in my mind this should be vanilla kernel + debian fixes. But 2.5/2.6 include IPSEC in the vanilla kernel! But 2.4 doesn't. And it's not a bug fix. It's a new feature. IMHO... It should not be in the 'vanilla' kernel. -- Paul
Accepted matchbox 1:0.6.2-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 11 Jul 2003 07:40:32 +0100 Source: matchbox Binary: matchbox Architecture: source i386 Version: 1:0.6.2-1 Distribution: unstable Urgency: low Maintainer: Paul Hedderly [EMAIL PROTECTED] Changed-By: Paul Hedderly [EMAIL PROTECTED] Description: matchbox - A X11 Window manager for handheld devices Changes: matchbox (1:0.6.2-1) unstable; urgency=low . * New upstream release. Files: c5fe7e14697bc554e02a3dbcb1ecde28 719 x11 optional matchbox_0.6.2-1.dsc 2a3af1e98149ce5384a8bedab0ab623d 540033 x11 optional matchbox_0.6.2.orig.tar.gz a4bdec8bcfe179a7618de21b1f17adf9 4648 x11 optional matchbox_0.6.2-1.diff.gz 86110b3be6c1cdf88cf0efd099e0db5c 331068 x11 optional matchbox_0.6.2-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) Comment: GNU Privacy Guard iD8DBQE/DmtFx5g40ENjN90RAm0sAKCV31FN5hE94L9JYuEbJzFSUs14BwCglCOx NUPy/9q/E4j6QvPYamJSDlQ= =V9tI -END PGP SIGNATURE- Accepted: matchbox_0.6.2-1.diff.gz to pool/main/m/matchbox/matchbox_0.6.2-1.diff.gz matchbox_0.6.2-1.dsc to pool/main/m/matchbox/matchbox_0.6.2-1.dsc matchbox_0.6.2-1_i386.deb to pool/main/m/matchbox/matchbox_0.6.2-1_i386.deb matchbox_0.6.2.orig.tar.gz to pool/main/m/matchbox/matchbox_0.6.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NEWS.Debian support is here
On Fri, Jul 04, 2003 at 01:01:14AM -0400, Joey Hess wrote: Thanks to Matt Zimmerman and Joe Drew, apt-listchanges will now display NEWS.Debian entries for upgraded packages. They're displayed before the regular changelog entries, and Matt plans to later let it be configured to only display news, if the user wants (more useful for stable users). All that's missing is an automatic debconf notice entry for each NEWS item. That wud be well c00l. -- Paul
Re: /etc/network/interfaces point-to-point ethernet broadcast address
On Sat, Feb 15, 2003 at 07:59:49PM +0100, Marc Haber wrote: I have a package ready that allows ifupdown to do much more magic. That package is in use for one and a half years at the site I work for, but it needs the patch (better said, the current version of that patch) from Bug #88948 applied. What other magic do you do? Could I have a copy? -- Paul
Accepted atmelwlandriver 2.1.1-3 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 24 May 2003 13:59:02 +0100 Source: atmelwlandriver Binary: atmelwlandriver-source atmelwlandriver-tools Architecture: source all i386 Version: 2.1.1-3 Distribution: unstable Urgency: low Maintainer: Paul Hedderly [EMAIL PROTECTED] Changed-By: Paul Hedderly [EMAIL PROTECTED] Description: atmelwlandriver-source - Driver source for Atmel based Wireless adaptors USB/PCI/PCMCIA atmelwlandriver-tools - Driver source for Atmel based Wireless adaptors USB/PCI/PCMCIA Changes: atmelwlandriver (2.1.1-3) unstable; urgency=low . * Fixed the copyright file and noted that fastvnet needs a man page. * Noted that there are a couple of lintian warnings that need to be dealt with soon. Files: 2cea154c2fd7e7b540a4f8ae06e75077 659 net optional atmelwlandriver_2.1.1-3.dsc 377c489c3dd2093213e4c9a67e38480c 806925 net optional atmelwlandriver_2.1.1.orig.tar.gz 7060de6063838c2ab075321de8c5b9f3 5806 net optional atmelwlandriver_2.1.1-3.diff.gz 8cf9b20b7cc230b8303604f441917d08 23926 net optional atmelwlandriver-tools_2.1.1-3_i386.deb a1bc1e3705b6adb6da10f2ae10897818 732862 net optional atmelwlandriver-source_2.1.1-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) Comment: GNU Privacy Guard iD8DBQE+z2z+x5g40ENjN90RAs6WAKDZKAFsza6BHNusy9xvXBzzz2huEACfY2U0 zuot1FvB1HLc3wgaSVYXDyg= =edsH -END PGP SIGNATURE- Accepted: atmelwlandriver-source_2.1.1-3_all.deb to pool/main/a/atmelwlandriver/atmelwlandriver-source_2.1.1-3_all.deb atmelwlandriver-tools_2.1.1-3_i386.deb to pool/main/a/atmelwlandriver/atmelwlandriver-tools_2.1.1-3_i386.deb atmelwlandriver_2.1.1-3.diff.gz to pool/main/a/atmelwlandriver/atmelwlandriver_2.1.1-3.diff.gz atmelwlandriver_2.1.1-3.dsc to pool/main/a/atmelwlandriver/atmelwlandriver_2.1.1-3.dsc atmelwlandriver_2.1.1.orig.tar.gz to pool/main/a/atmelwlandriver/atmelwlandriver_2.1.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xclass 0.6.2-5 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 18 Oct 2002 23:30:39 +0100 Source: xclass Binary: xclass-dev xclass0 Architecture: source i386 Version: 0.6.2-5 Distribution: unstable Urgency: low Maintainer: Paul Hedderly [EMAIL PROTECTED] Changed-By: Paul Hedderly [EMAIL PROTECTED] Description: xclass-dev - C++ GUI toolkit for X xclass0- C++ GUI toolkit for X Changes: xclass (0.6.2-5) unstable; urgency=low . * Couple of fixes suggested by James Troup to copyright and control Files: 91927396675c1b07ac3abe9e7d4526d0 623 - optional xclass_0.6.2-5.dsc c9d5cc01f57e03770afdf16defd32923 483852 - optional xclass_0.6.2.orig.tar.gz 7c3160b424b35d9466753a569db37eb9 23039 - optional xclass_0.6.2-5.diff.gz ccbeec58052ad66df2d29ba7b6901c99 451080 devel optional xclass-dev_0.6.2-5_i386.deb c3611396bbf0683966c5eb210c281393 307212 libs optional xclass0_0.6.2-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) Comment: GNU Privacy Guard iD8DBQE9sIyhx5g40ENjN90RAgI8AKDa6JkfflxGdzKWu+VjQHjFYIVOFgCgnkjG oZI8h1ATf93g6k5/ewVXMwk= =YMe6 -END PGP SIGNATURE- Accepted: xclass-dev_0.6.2-5_i386.deb to pool/main/x/xclass/xclass-dev_0.6.2-5_i386.deb xclass0_0.6.2-5_i386.deb to pool/main/x/xclass/xclass0_0.6.2-5_i386.deb xclass_0.6.2-5.diff.gz to pool/main/x/xclass/xclass_0.6.2-5.diff.gz xclass_0.6.2-5.dsc to pool/main/x/xclass/xclass_0.6.2-5.dsc xclass_0.6.2.orig.tar.gz to pool/main/x/xclass/xclass_0.6.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xstroke 0.5.12-ma5-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 18 Oct 2002 23:32:52 +0100 Source: xstroke Binary: xstroke Architecture: source i386 Version: 0.5.12-ma5-2 Distribution: unstable Urgency: low Maintainer: Paul Hedderly [EMAIL PROTECTED] Changed-By: Paul Hedderly [EMAIL PROTECTED] Description: xstroke- X11 Pen-based Character input Changes: xstroke (0.5.12-ma5-2) unstable; urgency=low . * Fixed some bogus build-depends (suggested by JT) Files: e5bcab8568ccd10047a058553960662c 648 x11 optional xstroke_0.5.12-ma5-2.dsc d34a63fcc822f9b09dd96d589dca67cc 187286 x11 optional xstroke_0.5.12-ma5.orig.tar.gz 5f3fce870b2602849babf7bfff8eb975 17212 x11 optional xstroke_0.5.12-ma5-2.diff.gz b4b57cc01abfbe4388976a8be84d3a90 109924 x11 optional xstroke_0.5.12-ma5-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) Comment: GNU Privacy Guard iD8DBQE9sJBux5g40ENjN90RAiqwAJ9w/TKACfYIdv5DBFFRr2e82dkQyACdEWkk zM0Wsss2VEumtn7IMx1NN6w= =wUvs -END PGP SIGNATURE- Accepted: xstroke_0.5.12-ma5-2.diff.gz to pool/main/x/xstroke/xstroke_0.5.12-ma5-2.diff.gz xstroke_0.5.12-ma5-2.dsc to pool/main/x/xstroke/xstroke_0.5.12-ma5-2.dsc xstroke_0.5.12-ma5-2_i386.deb to pool/main/x/xstroke/xstroke_0.5.12-ma5-2_i386.deb xstroke_0.5.12-ma5.orig.tar.gz to pool/main/x/xstroke/xstroke_0.5.12-ma5.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted rfb 0.6.1-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 16 Oct 2002 13:09:18 +0100 Source: rfb Binary: rfb Architecture: source i386 Version: 0.6.1-2 Distribution: unstable Urgency: low Maintainer: Paul Hedderly [EMAIL PROTECTED] Changed-By: Paul Hedderly [EMAIL PROTECTED] Description: rfb- VNC Server for X11 - exports current dislpay! Closes: 78896 Changes: rfb (0.6.1-2) unstable; urgency=low . * Closes ITA (Closes: Bug#78896) Files: 734b5d816b9cbaf4f040930946e6ea82 639 x11 optional rfb_0.6.1-2.dsc ec08daca94ff5334a247af5059945df3 3218 x11 optional rfb_0.6.1-2.diff.gz 67e3a33288b0593ac380a74f1ad6f069 623940 x11 optional rfb_0.6.1-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) Comment: GNU Privacy Guard iD8DBQE9rVdWx5g40ENjN90RAg/mAKCXZ0/shIbUJ02DGFvWwZgIqnRHCgCfYIO0 2qKB903y0Xs1ytJPPv1OlKk= =8bUo -END PGP SIGNATURE- Accepted: rfb_0.6.1-2.diff.gz to pool/main/r/rfb/rfb_0.6.1-2.diff.gz rfb_0.6.1-2.dsc to pool/main/r/rfb/rfb_0.6.1-2.dsc rfb_0.6.1-2_i386.deb to pool/main/r/rfb/rfb_0.6.1-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted rfb 0.6.1-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 16 Oct 2002 12:03:02 +0100 Source: rfb Binary: rfb Architecture: source i386 Version: 0.6.1-1 Distribution: unstable Urgency: low Maintainer: Paul Hedderly [EMAIL PROTECTED] Changed-By: Paul Hedderly [EMAIL PROTECTED] Description: rfb- VNC Server for X11 - exports current dislpay! Changes: rfb (0.6.1-1) unstable; urgency=low . * Initial Release. Files: 2e25af4cc3dadbe4d6c62a95f544380c 639 x11 optional rfb_0.6.1-1.dsc 25c7ee22bfe6b172a147d40e778221f7 317935 x11 optional rfb_0.6.1.orig.tar.gz 28081a4f2ef39fea9a0343809a4aab79 3174 x11 optional rfb_0.6.1-1.diff.gz ed825d3ddb1290b4efbc46f5cc1786ae 623894 x11 optional rfb_0.6.1-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) Comment: GNU Privacy Guard iD8DBQE9rVUtx5g40ENjN90RAr1qAJ9W5RLdzdhW0R9hf4lzWulFzz4evACeLU2l Sb2og8xXuccAXyHhwvUW9Do= =hza8 -END PGP SIGNATURE- Accepted: rfb_0.6.1-1.diff.gz to pool/main/r/rfb/rfb_0.6.1-1.diff.gz rfb_0.6.1-1.dsc to pool/main/r/rfb/rfb_0.6.1-1.dsc rfb_0.6.1-1_i386.deb to pool/main/r/rfb/rfb_0.6.1-1_i386.deb rfb_0.6.1.orig.tar.gz to pool/main/r/rfb/rfb_0.6.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gloo 20020927-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 13 Oct 2002 22:22:10 +0100 Source: gloo Binary: gloo Architecture: source i386 Version: 20020927-2 Distribution: unstable Urgency: low Maintainer: Paul Hedderly [EMAIL PROTECTED] Changed-By: Paul Hedderly [EMAIL PROTECTED] Description: gloo - Two-way pipes and serial/network to STDIO pipes Closes: 163298 Changes: gloo (20020927-2) unstable; urgency=low . * Typo in doc (Closes: Bug#163298) * Fixed some other oversights in man page. Files: d42889c0e0bb1214c221d216578a3eab 608 utils optional gloo_20020927-2.dsc da7ff40db91587bb36e5aac24de50827 3585 utils optional gloo_20020927-2.diff.gz a8374cf148def3f4821cd471cc474e60 9680 utils optional gloo_20020927-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) Comment: GNU Privacy Guard iD8DBQE9qeQ+x5g40ENjN90RAmuKAJ9INht8IgzNJbZK4tKou6A//OnaYQCeJ/Ki M8zeUXd3oyu/JY9nmdxILF8= =+p7z -END PGP SIGNATURE- Accepted: gloo_20020927-2.diff.gz to pool/main/g/gloo/gloo_20020927-2.diff.gz gloo_20020927-2.dsc to pool/main/g/gloo/gloo_20020927-2.dsc gloo_20020927-2_i386.deb to pool/main/g/gloo/gloo_20020927-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gloo 20020927-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 27 Sep 2002 13:00:34 +0100 Source: gloo Binary: gloo Architecture: source i386 Version: 20020927-1 Distribution: unstable Urgency: low Maintainer: Paul Hedderly [EMAIL PROTECTED] Changed-By: Paul Hedderly [EMAIL PROTECTED] Description: gloo - Two-way pipes and serial/network to STDIO pipes Changes: gloo (20020927-1) unstable; urgency=low . * New upstream release * Fixed a few docs bits, move of my debian manpage into original * Changed copyright notice - now GPL-2 (Cheers James!) Files: e5b66f793374b1212370c83ddcbd7436 608 utils optional gloo_20020927-1.dsc 9c1b1b3fd256cd571290286059baa9de 16687 utils optional gloo_20020927.orig.tar.gz b0c264feca855fdb63aa41cd8101099f 3185 utils optional gloo_20020927-1.diff.gz 60158aee621af2e419c2814df5a1878c 9544 utils optional gloo_20020927-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) Comment: GNU Privacy Guard iD8DBQE9lEnYx5g40ENjN90RAsC6AJwNaICW3dMOVb3tTLw2TaWKmHDg0wCgqH+G fcRy2EUCqPpJaI9vHkHgKQs= =fRhR -END PGP SIGNATURE- Accepted: gloo_20020927-1.diff.gz to pool/main/g/gloo/gloo_20020927-1.diff.gz gloo_20020927-1.dsc to pool/main/g/gloo/gloo_20020927-1.dsc gloo_20020927-1_i386.deb to pool/main/g/gloo/gloo_20020927-1_i386.deb gloo_20020927.orig.tar.gz to pool/main/g/gloo/gloo_20020927.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mmenu 0.8.2-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 11 Sep 2002 10:06:46 +0100 Source: mmenu Binary: mmenu Architecture: source i386 Version: 0.8.2-2 Distribution: unstable Urgency: low Maintainer: Paul Hedderly [EMAIL PROTECTED] Changed-By: Paul Hedderly [EMAIL PROTECTED] Description: mmenu - Simple X11 Debian menu Closes: 160442 Changes: mmenu (0.8.2-2) unstable; urgency=low . * Fix errant build depends... DOH! (Closes: Bug#160442) * Still praying for the families of those who died a year ago. God is all powerful, but He is a gentleman - we have to invite Him to get involved in our world. So invite Him in! Files: 4556d2732dbf10332133a4e98d6714ef 629 x11 optional mmenu_0.8.2-2.dsc 65f7d31a75bf5ac4533928642bf76077 22313 x11 optional mmenu_0.8.2-2.diff.gz d1b234eba6729279b0bf5dc9311f9b3f 20998 x11 optional mmenu_0.8.2-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) Comment: GNU Privacy Guard iD8DBQE9fwjLx5g40ENjN90RAkmRAKCOYDVZ90ZZZRTGV2Ab0e+0751xwQCfeNCI KKvWWihDhOyJUALDjGEflrU= =5jWR -END PGP SIGNATURE- Accepted: mmenu_0.8.2-2.diff.gz to pool/main/m/mmenu/mmenu_0.8.2-2.diff.gz mmenu_0.8.2-2.dsc to pool/main/m/mmenu/mmenu_0.8.2-2.dsc mmenu_0.8.2-2_i386.deb to pool/main/m/mmenu/mmenu_0.8.2-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mmenu 0.8.2-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 6 Sep 2002 11:02:26 +0100 Source: mmenu Binary: mmenu Architecture: source i386 Version: 0.8.2-1 Distribution: unstable Urgency: low Maintainer: Paul Hedderly [EMAIL PROTECTED] Changed-By: Paul Hedderly [EMAIL PROTECTED] Description: mmenu - Simple X11 Debian menu Changes: mmenu (0.8.2-1) unstable; urgency=low . * Initial Release. Files: ee69d2b0c0866c03df0dcc59a8f8832f 618 x11 optional mmenu_0.8.2-1.dsc 6a576dd565ad565aec0477e33f26e63b 94112 x11 optional mmenu_0.8.2.orig.tar.gz da0375a0a52fa6490f9910c97509d539 22006 x11 optional mmenu_0.8.2-1.diff.gz 28645d64a7970def1e30d29ff6b4f3e3 20798 x11 optional mmenu_0.8.2-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) Comment: GNU Privacy Guard iD8DBQE9eI5Dx5g40ENjN90RAlmPAKDEMjBjk4Q3KSFqGWT9rhlC1CAEDgCfcbSI pZNSEJTmIIudPQicWk8VxY0= =Fr69 -END PGP SIGNATURE- Accepted: mmenu_0.8.2-1.diff.gz to pool/main/m/mmenu/mmenu_0.8.2-1.diff.gz mmenu_0.8.2-1.dsc to pool/main/m/mmenu/mmenu_0.8.2-1.dsc mmenu_0.8.2-1_i386.deb to pool/main/m/mmenu/mmenu_0.8.2-1_i386.deb mmenu_0.8.2.orig.tar.gz to pool/main/m/mmenu/mmenu_0.8.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted matchbox 0.3.3-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 6 Sep 2002 10:34:43 +0100 Source: matchbox Binary: matchbox Architecture: source i386 Version: 0.3.3-1 Distribution: unstable Urgency: low Maintainer: Matthew Allum [EMAIL PROTECTED] Changed-By: Paul Hedderly [EMAIL PROTECTED] Description: matchbox - A X11 Window manager for handheld devices Changes: matchbox (0.3.3-1) unstable; urgency=low . * New upstream release Files: b32218808e71a7fc7adc566313ea04f8 610 x11 optional matchbox_0.3.3-1.dsc 1f9c2633a372b01abdc841fbd87aa5f4 196370 x11 optional matchbox_0.3.3.orig.tar.gz 4f7bebef0a069e96ef7fc4f4b35f26da 44361 x11 optional matchbox_0.3.3-1.diff.gz ad05a94d9ecbdda7230d4a948502f671 98720 x11 optional matchbox_0.3.3-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) Comment: GNU Privacy Guard iD8DBQE9eHwxx5g40ENjN90RAg8tAKCxsUGK/QBJa2IK2qCfnco71SXUsgCfQAr/ ObxJBHVNbFlPobT+CD02JxA= =Bd7R -END PGP SIGNATURE- Accepted: matchbox_0.3.3-1.diff.gz to pool/main/m/matchbox/matchbox_0.3.3-1.diff.gz matchbox_0.3.3-1.dsc to pool/main/m/matchbox/matchbox_0.3.3-1.dsc matchbox_0.3.3-1_i386.deb to pool/main/m/matchbox/matchbox_0.3.3-1_i386.deb matchbox_0.3.3.orig.tar.gz to pool/main/m/matchbox/matchbox_0.3.3.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: tenative ITP linux-wlan-ng; soliciting advice
On Fri, Jul 26, 2002 at 03:17:21AM -0400, Joey Hess wrote: Peter Hicks wrote: well, I would hate to dissuade you from packaging the linux-wlan drivers, but I have no trouble using prism2, orinoco, or cisco aironet cards with the stock debian 2.4.18 kernel. Both my lucent card and my smc 2632 use the hermes/orinoco_cs drivers. I tested a cisco card last monday and it worked fine, but I don't have it around to check which drivers it used. As far as I know wlan-ng is the only game in town for pci prism2 cards. And I've done the necessary work to integrate it with /etc/network/interfaces already: No. the hostap dirver is excellent. Written by Jean Tour... something. He works for SSH Corp. google for linux prism2 driver. It does pcmcia and pci brilliantly but doesnt support usb yet. works with prism2/2.5/3 cards - and most orinoco cards too. supports kysmet. -- Paul (Started packaging modules for it a month ago then went away for a month... must finish that) iface wlan0 inet static address 192.168.1.5 gateway 192.168.1.1 netmask 255.255.255.0 # Should be either ad-hoc or managed. Used managed if you have an AP. wireless_mode ad_hoc # Leave this unset to associate with any access point. Set to pick an # access point, or in ad-hoc mode. wireless_essid wortroot # A name for your machine. Required. wireless_nick dragon # For ad-hoc mode, you must specify a channel. wireless_channel 1 # # # To enable WEP, uncomment the next line. # wireless_enc on # To set a WEP key, either use a string, which will be converted to a key: # wlan_ng_priv_genstr foo # (Using the specified key length.) # wlan_ng_priv_key128 false # Or set keys explicitly. # wlan_ng_key0 xx:xx:xx:xx:xx # wlan_ng_key1 xx:xx:xx:xx:xx # wlan_ng_key2 xx:xx:xx:xx:xx # wlan_ng_key3 xx:xx:xx:xx:xx # If you set a key, remember to make the file mode 600! # # In managed mode, set to sharedkey if a shared key is required. # wlan_ng_authtype opensystem # If you are serving as an AP, uncommnent this to require WEP for all STAs. # wlan_ng_exclude_unencrypted true # # Some extra ah-hoc mode settings: # Beacon interval (in Kus) # wlan_ng_bcint 100 # Rates for mgmtctl frames (in 500Kb/s) # wlan_ng_basicrates 2 4 # Supported rates in BSS (in 500Kb/s) # wlan_ng_oprates 2 4 11 22 # # You can set arbitrary MIB items with this directive, separated by # whitespace. Each will then be set. # wlan_ng_user_mibs p2CnfRoamingMode=1 (It also does a really impressive job of getting ad-hoc link quality stats right automatically. Despite the huge complexity, I think I like it..) -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: XFree 4.2.0 - again
On Tue, Apr 16, 2002 at 12:01:10AM -0400, Daniel Burrows wrote: On Tue, Apr 16, 2002 at 06:30:20AM +0300, Lasse Karkkainen [EMAIL PROTECTED] was heard to say: I guess you didn't read my original message: the problem is that I know next to nothing about Debian. Yes, that sums it up pretty well. I'm feeling a bit generous, so I'll hand you a piece of advice, gratis. If I had to say what the fastest way is to get yourself flamed or ignored, it would probably be this: Aw Daniel - Don't go giving him a clue, I was really enjoying read his drivel - haven't read anything quite like it for ages! (At first I really thought he was joking...) -- Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Please test this woody cd image
On Thu, Apr 11, 2002 at 10:12:28AM +0200, Eduard Bloch wrote: Did YOU help introducing ANY new features in boot-floppies? I18n? Kernel 2.4, other filesystems, RAID support, lots of bugfixes in the existing code, etc. etc.? Either you can continue your mission of distruction, or you stop crying about lost time. If we should work out and discuss every feature (needing some weeks), then test it some months, we won't release Woody before 2003. No I didn't. I think this use of isolinux is fantastic. I've been having a gander (unlike some other posters to this thread I suspect) and there is nothing really new here - it really is using just a slightly different syslinux binary and combining the syslinux.cfg's together with access to all the discs in one. I can't see the big deal. What I would provide/recommend is including a smartboot windows and linux binaries - this can write a very simple boot floppy that will boot cdroms on most machines with older non el-torito BIOS's. Thumbs up for Isolinux CD #1. -- Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Linux Progress Patch for Debian available!
On Mon, Jan 01, 2001 at 11:37:17AM -0800, [EMAIL PROTECTED] wrote: -- Ferret Who recalls a cddb access program designed for blind people where cddb.com DENIED a certification because the program couldn't display a graphical logo where the blind people could see it. Presumably no blind person is allowed to use any cddb.com certified program then. Hmm :O) -- Regards, Paul
