Re: Let's remove mips, mipsel, s390, ... (Was: [Fwd: Re: GTK+2.0 2.6.2-3 and buildds running out of space])
On Tue, Feb 22, 2005 at 04:39:22AM +, Dirk Eddelbuettel wrote: Matthew Palmer mpalmer at debian.org writes: On Tue, Feb 22, 2005 at 03:15:58AM +, Dirk Eddelbuettel wrote: undisputed: essentially all users are on i386 clearly dominating all other arches, with a fraction of users in maybe two, three, four other arches --- and comparitively nobody in the other fringe arches we keep around for no good reason. And I still believe it delays our releases. As you say, there You can believe in the tooth fairy, too, but it doesn't make it true. Since you're trying to convince others to join your tooth fairy worshipping religion, it might be useful to provide some evidence to back your belief. Sorry, you just scored against your own team. Why, by asking for evidence that multiple architectures delays releases? You have a really oddball scoring system. I believe we haven't seen any evidence that all our architectures has delayed any release. DI was a potential sticking point, but it's already sorted due to the hard work by the relevant porters while we're still waiting for other technical issues to work themselves out. It delays our releases in the sense that it affects our resources: - available maintainer and developer time, What's to say that someone who spends time on a minority architecture would spend it on Debian proper if that architecture wasn't in Debian? I would say that the inverse is the case: developers with an interest in minority architecture come to Debian and help out with non-arch-specific things as well as their pet arch, while if Debian didn't support that arch they'd probably go elsewhere. - cpu cycles (witness Wouter's request to compile big packages rarely), More computers wastes CPU cycles? - network bandwith (witness the discussion on mirror efficiency), Do you have any actual evidence that lower bandwidth would benefit Debian in any material way? - mirrror capacity (witness the sad state of amd64), So you're saying that we need to reduce our architecture count to increase our architecture count? - security response time (more builds to do) Security autobuilders are on their way. You could make the argument that if we only had a couple of architectures we wouldn't really need security autobuilders, but I think that automating everything that can be automated is a Good Thing. and that it - increases the load on infrastructure (t-p-u, security) WTF? t-p-u would be needed if we had one arch. - scarce resource such as release managers, ftp admins, ... RMs and ftpmasters aren't arch-specific, apart from the odd occasion when an ftpmaster needs to remove out-of-date binaries for unbuilt architectures. Note, however, that two ftpmasters are presidios of their own niche architecture. If we dropped them, they'd probably go off and do their own (non-Debian) thing. As you say so cogently: it might be useful to provide some evidence to back your belief. Consider the ball in your court, and please prove with tangible numbers You'll need to go and collect the ball from behind you where it landed after you missed it before you send it back to me. - Matt signature.asc Description: Digital signature
Re: Let's remove mips, mipsel, s390, ... (Was: [Fwd: Re: GTK+2.0 2.6.2-3 and buildds running out of space])
On Sun, Feb 20, 2005 at 10:57:47PM +, Dirk Eddelbuettel wrote: Clint Byrum cbyrum at spamaps.org writes: Now, can someone please tell me how messages like the one below, and others, aren't indicative that debian should drop s390, mipsel, and maybe hppa from the list of architectures? How about we release for i386, sparc, and powerpc, and let the others release on their own schedule? This business of supporting 11 architectures and making sure they're all 100% right before releasing is just about the worst idea ever. Still, the hours we maste on fixing, building, maintaining, ... code on unused platforms is hysterical waste of resources. Resources we don't really have. I'd like to see your numbers on how many manhours have been wasted in the past, say, 6 months on fixing code on unused platforms which would have gone into other things had those architectures not been in Debian. - Matt signature.asc Description: Digital signature
Re: apt-src cannot build
On Thu, Feb 17, 2005 at 04:26:12PM +0200, Marcus Sundman wrote: On Thursday 17 February 2005 21:32, Michael Koch wrote: On Thu, Feb 17, 2005 at 03:09:41PM +0200, Marcus Sundman wrote: On Thursday 17 February 2005 13:18, Bartosz Fenski aka fEnIo wrote: On Thu, Feb 17, 2005 at 06:19:59AM +0200, Marcus Sundman wrote: I do the following (irrelevant output omitted): 8 /usr/src/tmp$ apt-src install foo /usr/src/tmp$ cd foo-version /usr/src/tmp/foo-version$ apt-src build foo E: Not installed /usr/src/tmp/foo-version$ 8 Any idea what might be wrong? You don't have to enter to foo-version directory. Anyway it should work even with that... both ways works for me. I tried that, too, but it still just says E: Not installed. What's E and what's not installed? (This must be one of the least helpful error messages I've ever seen.) E means error. Ah, ok.. (If the author tried to be confusing he could have made it say Blue: No roof or something. Although on a second thought that probably would have been too obvious and made ppl check out the source, and this way he got it actually more confusing by being less confusing. Clever.) The addition of one compound-word (Build-dependencies) would have solved all of your ills. The BTS is --- over there. (It would be nice if the man page of apt-src would state that build requires doing an apt-get build-dep.) Again, BTS --- over there, and besides, it's not required to do an apt-get build-dep if you've already got all of the relevant packages installed. - Matt signature.asc Description: Digital signature
Re: Bug#295328: general: Help messages to stderr should be banned
On Tue, Feb 15, 2005 at 10:19:12AM +0100, Marco d'Itri wrote: On Feb 15, Justin Pryzby [EMAIL PROTECTED] wrote: I suppose I will start filing minor bugs against packages that do this. I'd like to hear other people's opinions, though. (It occurs to me that help output to stderr is arguably appropriate if an invalid option is given). Part of the problem is that its fairly depressing WTF? This is a long-time UNIX tradition, So your best rebuttal is It's tradition!? Strong argument you've got there. I'd summarily close such a bug opened on one of my packages. Good for you. - Matt signature.asc Description: Digital signature
Re: Bug#295328: general: Help messages to stderr should be banned
On Tue, Feb 15, 2005 at 03:06:19PM +0100, Francesco P. Lovergine wrote: On Tue, Feb 15, 2005 at 07:38:08AM -0600, John Hasler wrote: Francesco P. Lovergine writes: It depends on programs, sometimes the same usage function is used for either --help or invalid options. Sure, but the output should still be directed correctly. Quite difficult if the function is the same. In both cases it uses stderr. So you change the program to take a file descriptor into the help-printing function, or provide some other means of determining where to send the output. - Matt signature.asc Description: Digital signature
Re: mkchroot scripts
On Fri, Feb 04, 2005 at 09:28:19AM +0100, Wouter Verhelst wrote: On Thu, Feb 03, 2005 at 10:58:55PM +0300, Sergei I. Kononov wrote: On Thu, Feb 03 at 20:23:20 (+0100), Christoph Berg wrote: What's the difference to makejail and debootstrap? 1. Created chroot enviroment use less disk space, and does not include not needed files/dirs (like: passwd, Actually, that /is/ a needed file. Some programs look up the name of a user before doing stuff (or look up the UID of a username), and without that file they do very strange things Surely nsswitch should be able to handle things across a chroot, providing the relevant communication channels are available. IMO, any program that directly accesses /etc/passwd to find a user has a bug. - Matt signature.asc Description: Digital signature
Re: Bug#293167: ITP: request-tracker3.4 -- Extensible trouble-ticket tracking system
On Thu, Feb 03, 2005 at 10:04:33AM +0100, Florian Weimer wrote: * Matthew Palmer: As a user, I think this is very convenient. The ability to switch back to a known-to-work version by tweaking a few configuration files is reassuring, even if you've tested the new software version on an indepedent machine. So archive bloat is not a problem for you, No, it's not. If we have incremental Packages files, it's a complete non-issue for me. But we don't, so your problem still exists. There's also the problem that an archive which doubled in size would, almost certainly, cause a problem for a number of mirrors. Mirrors are kind of important for a distribution the size of Debian. and apt-get dist-upgrade not actually providing upgrades to the latest versions of everything is perfectly fine? In quite a few cases, yes. For example, if data formats change, it's usually better not to try to upgrade automatically. Some maintainers ignore this problem entirely (look at the recent libberkeleydb-perl breakage for an example of the consequences). I'm not familiar with the problem, but ignoring the problem is not the correct means of dealing with it, and I'm not quite sure why you're advocating doing so. The proper action is to make your system robust enough to withstand simple data file format changes. There's no guarantee that apt-get dist-upgrade will in fact install the latest version of anything, so I don't really understand your criticism. Are you happy with having to find *all* of the applications in use on your system and typing 'apt-get install list of applications with new version numbers' every time you want to upgrade your systems? Because that is the end game. I've already identified two of my packages that I'd like to put onto a versioned package name basis. I'm sure that *plenty* of maintainers would love to do the same thing with their not-trivial-to-upgrade packages. - Matt signature.asc Description: Digital signature
Re: Bug#293167: ITP: request-tracker3.4 -- Extensible trouble-ticket tracking system
On Wed, Feb 02, 2005 at 02:38:10PM +0100, Florian Weimer wrote: * Matthew Palmer: On Tue, Feb 01, 2005 at 06:27:30PM +0100, Florian Weimer wrote: * Lars Wirzenius: ti, 2005-02-01 kello 15:25 +, Stephen Quinney kirjoitti: This is the 3.4 series of RT, it can be installed alongside the 3.0 and 3.2 series without any problems. This release is a big improvement over previous versions and features many new features, substantial performance improvements and a significant cleanup and restructuring of the codebase. What is the a reason every version series of Request Tracker needs to be packaged, instead of having a single request-tracker package that gets updated with newer versions? Request Tracker is a development framework for trouble ticket systems. Users are encouraged to add new code to its (Perl) packages, and there's an overlay mechanism to support this. Unfortunately, this makes updates non-trivial, at least sometimes. So you do a bit of testing before madly apt-get dist-upgrading your production servers. What a concept. As Andrew noted, we already do similar things for library packages. There's a growing trend to provide different version which can be installed in parallel for other infrastructure packages, too (IIRC, PostgreSQL is heading in this direction, too). As a user, I think this is very convenient. The ability to switch back to a known-to-work version by tweaking a few configuration files is reassuring, even if you've tested the new software version on an indepedent machine. So archive bloat is not a problem for you, and apt-get dist-upgrade not actually providing upgrades to the latest versions of everything is perfectly fine? Ability to switch back is provided by backups and planning, not by having a million versions of a package in the archive. If you really want this, work out a way of installing multiple versions of the same package through path redirection. Libraries are the way they are because they are the way they are. If they weren't the way they are they wouldn't be the way they are. If RT's a library, start defining API compatibility and package it like a library -- lib* prefix and all, so people know what they're getting into. - Matt signature.asc Description: Digital signature
Re: Bug#293167: ITP: request-tracker3.4 -- Extensible trouble-ticket tracking system
On Wed, Feb 02, 2005 at 07:04:40PM -0600, Steve Greenland wrote: On 02-Feb-05, 18:31 (CST), Matthew Palmer [EMAIL PROTECTED] wrote: So archive bloat is not a problem for you, and apt-get dist-upgrade not actually providing upgrades to the latest versions of everything is perfectly fine? In the case of RT, yes. I was discussing the issue in a wider sense in that paragraph, as Florian was saying that multiple versions of random applications is a good thing. I notice that there are several different versions of gcc in the archive, and nobody seems to be bothered by that. Likewise, there are several versions of python. There are, of course, good reasons for both. Yeah, lots of people write bug-ridden C and C++ code, and Python upstream has never heard of backward-compatibility. Another example is PHP, which is another example of a lack of planning taken to a horrible extreme. I'm not happy about any of them. But pointing to them and saying they can do it, why can't we is poor form. RT likewise. It changes a *lot* between minor releases. Add-on tools have to be updated, local scripts checked and fixed, etc. etc. etc. Best Practical makes new bugfix releases to older versions, so they obviously don't expect everybody to upgrade all at once. RT is not an application. RT is a framework. It's quite reasonable to have multiple versions of that framework available. So package it as the library it apparently is. The description of the request-tracker3 package makes it sound like it's a ready-to-run application. It doesn't even *mention* that it's a development platform (unless you count the word 'Extensible', which is a now a content-free weasel-word ever since XML arrived on the corporate scene). If there *is* a front-end app ready for immediate use, then make that the request-tracker package, and build the underlying libraries as a bunch of lib*-perl packages with appropriate API versioning. As an added bonus, someone else can then package their own RT-based trouble-ticketing system and use your libraries, without needing to have the whole RT frontend installed, a la the Mozilla Mess. - Matt signature.asc Description: Digital signature
Re: Bug#293167: ITP: request-tracker3.4 -- Extensible trouble-ticket tracking system
On Tue, Feb 01, 2005 at 04:46:51PM +, Stephen Quinney wrote: On Tue, Feb 01, 2005 at 06:17:50PM +0200, Lars Wirzenius wrote: ti, 2005-02-01 kello 15:25 +, Stephen Quinney kirjoitti: This is the 3.4 series of RT, it can be installed alongside the 3.0 and 3.2 series without any problems. This release is a big improvement over previous versions and features many new features, substantial performance improvements and a significant cleanup and restructuring of the codebase. What is the a reason every version series of Request Tracker needs to be packaged, instead of having a single request-tracker package that gets updated with newer versions? The changes between major versions of Request Tracker are typically substantial and one usually wants the opportunity to test an installation of the new version alongside the old version. If a user has made lots of local alterations (via RT's overlay system) they probably won't work without being updated to the new API. This method gives people a much easier upgrade path. The same could be said of a lot of packages in Debian. Why can't users do roughly the same thing as they do for every other application in Debian -- test new releases of software separately before they go running around dumping them on production boxes? - Matt signature.asc Description: Digital signature
Re: Bug#293167: ITP: request-tracker3.4 -- Extensible trouble-ticket tracking system
On Tue, Feb 01, 2005 at 06:27:30PM +0100, Florian Weimer wrote: * Lars Wirzenius: ti, 2005-02-01 kello 15:25 +, Stephen Quinney kirjoitti: This is the 3.4 series of RT, it can be installed alongside the 3.0 and 3.2 series without any problems. This release is a big improvement over previous versions and features many new features, substantial performance improvements and a significant cleanup and restructuring of the codebase. What is the a reason every version series of Request Tracker needs to be packaged, instead of having a single request-tracker package that gets updated with newer versions? Request Tracker is a development framework for trouble ticket systems. Users are encouraged to add new code to its (Perl) packages, and there's an overlay mechanism to support this. Unfortunately, this makes updates non-trivial, at least sometimes. So you do a bit of testing before madly apt-get dist-upgrading your production servers. What a concept. - Matt signature.asc Description: Digital signature
Re: shell script sniplets in /usr/bin?
On Sat, Jan 29, 2005 at 05:40:05PM +0100, Santiago Vila wrote: On Sat, 29 Jan 2005, Jochen Voss wrote: [...] My question: does anybody have further references for the question whether it is ok or maybe even preferable to install non-programs in /usr/bin? You forgot to quote last thing I said when closing the bug. So I'll repeat: Please read the logs for non-bug Bug#292759, where the author explains the rationale for putting gettext.sh in /usr/bin. Because I don't wanna play by the rules! is not a rationale. So you have to specify a path -- so what? The way things stand at the moment, if I were to drop a gettext.sh in my ~/bin (which is quite likely, except that I don't like to put a .sh on my helper scripts) your shell scripts would suddenly go tits-up in a most unpleasant fashion. Personally, *that* would be enough to make me want to hardcode the path. - Matt signature.asc Description: Digital signature
Re: Bug#292759: shell script sniplets in /usr/bin?
On Sun, Jan 30, 2005 at 12:28:53AM +0100, Santiago Vila wrote: On Sun, 30 Jan 2005, Matthew Palmer wrote: Because I don't wanna play by the rules! is not a rationale. You are mistaken. I want to play by the rules, but the rules say executables should go to /usr/bin, *not* that everything in /usr/bin should be executable. So if I say that you're a reasonable individual, that doesn't mean that you're *not* a fuckwit? Typically, in English, when you specify a certain criteria for something, you implicitly exclude anything not mentioned. Otherwise I'm going to recommend that we add /usr/include to the default path, since the FHS doesn't say I can't put executable commands there -- /usr/bin is only the primary directory of executable commands, not the only directory, and /usr/include doesn't say you can't put commands in there. Or, alternately, we could read the FHS with our brains set to reasonable interpretation instead of whatever-as-long-as-I-don't-have-to-do-any-work and decide that gettext.sh belongs in /usr/share. So you have to specify a path -- so what? The way things stand at the moment, if I were to drop a gettext.sh in my ~/bin (which is quite likely, except that I don't like to put a .sh on my helper scripts) your shell scripts would suddenly go tits-up in a most unpleasant fashion. Personally, *that* would be enough to make me want to hardcode the path. The same could be said for an executable called ls. Exactly the same. Horseshit. If I do 'man ls' I can get the semantics for the ls command. No such benefit is provided me by gettext.sh. Hmm, time to report a bug against gettext-base for not having a manual page for gettext.sh... The name gettext.sh should be distinctive enough to avoid namespace pollution. Bwahahaha. It's the name of a common utility with '.sh' on the end. You don't think that *someone* isn't going to write a helper script called gettext.sh? OTOH, if you are really worried about namespace pollution, then please press the tab key twice while running bash. And, your point being? - Matt signature.asc Description: Digital signature
Accepted irm 1.5.1.1-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Jan 2005 23:17:03 +1100 Source: irm Binary: irm Architecture: source all Version: 1.5.1.1-1 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: irm- Web-based asset tracking system for IT departments and help desks Closes: 284536 284537 Changes: irm (1.5.1.1-1) unstable; urgency=low . * New upstream release. * Redid much of the initial config/upgrade stuff due to rationalisations in upstream's idea of configuration management. * Copy style.css into the package. Closes: #284537. * Do more intelligent things with server installs, including checking for the apache2 directory and installing in there if possible. Closes: #284536. Files: 8a12033e765c12716e4074bb232ac0cc 561 web optional irm_1.5.1.1-1.dsc ccce8ba48dd77476a246d984f2f591f1 124014 web optional irm_1.5.1.1.orig.tar.gz b5acb4581dedb342bd04ae0aa685016b 11477 web optional irm_1.5.1.1-1.diff.gz 540a912219634bd10d3d341be145dba0 128016 web optional irm_1.5.1.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFB+O9TBEnrTWk1E4cRAi5+AJ9bUrp1sY8NqxaFAkEtPftF02BqTACeKZNz 1LXCv9zkiPWX0xJpM5jCfZs= =cS4F -END PGP SIGNATURE- Accepted: irm_1.5.1.1-1.diff.gz to pool/main/i/irm/irm_1.5.1.1-1.diff.gz irm_1.5.1.1-1.dsc to pool/main/i/irm/irm_1.5.1.1-1.dsc irm_1.5.1.1-1_all.deb to pool/main/i/irm/irm_1.5.1.1-1_all.deb irm_1.5.1.1.orig.tar.gz to pool/main/i/irm/irm_1.5.1.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted irm 1.5.1.1-2 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 28 Jan 2005 15:16:25 +1100 Source: irm Binary: irm Architecture: source all Version: 1.5.1.1-2 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: irm- Web-based asset tracking system for IT departments and help desks Changes: irm (1.5.1.1-2) unstable; urgency=low . * Add a cut-down MDB implementation until php-mdb reaches the archive. * Fix an include_path problem in the init-db script. Files: 6c00c8c931a1825db8b082d7b60b72e2 561 web optional irm_1.5.1.1-2.dsc fd42407b7b748c745d605ee827c8d48f 90054 web optional irm_1.5.1.1-2.diff.gz 7a12459b8e337c87ae2f067ba36515d0 208146 web optional irm_1.5.1.1-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFB+cUeBEnrTWk1E4cRAqMfAJ4sGIfUHq6Op3A38mR4oVeLrxsi5gCgrWGp SUKT+kxNau0/e0Pu+BbeJR4= =qk1k -END PGP SIGNATURE- Accepted: irm_1.5.1.1-2.diff.gz to pool/main/i/irm/irm_1.5.1.1-2.diff.gz irm_1.5.1.1-2.dsc to pool/main/i/irm/irm_1.5.1.1-2.dsc irm_1.5.1.1-2_all.deb to pool/main/i/irm/irm_1.5.1.1-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: scripts to download porn in Debian?
On Tue, Jan 25, 2005 at 08:15:29PM +0100, Wim De Smet wrote: And splitting does indeed change something. If his kids are not root they cannot install the offensive part. Absolutely false. But thanks for playing. - Matt signature.asc Description: Digital signature
Re: apply to NM? ha!
On Mon, Jan 24, 2005 at 07:59:59PM -0500, SR, ESC wrote: Le lun 2005-01-24 a 19:26:34 -0500, Helen Faulkner [EMAIL PROTECTED] a dit: I do not believe that being thick-skinned enough to cope with people who are very agressive or insulting should be a requirement for involvement in Debian. Sadly, it seems to me that this is effectively the case. Shouldn't we be more interested in someone's technical skills, and their ability to work well with others? while i don't appeciate gunnar's comments - seems to me he's just trying to lessening the issue i brought up. and i do have a thick skin, i just don't see the need to have one if people are going to work together in a cooperative fashion. attacking people isn't the way to do things, Like, for instance, saying this: fuck off, and grow the fuck up in a public mailing list, without even identifying the individuals you wish to abuse? we have enough of it going on in the world, we don't need to bring any more of it in here. You owe me a new irony meter. You overloaded this one. Who started this thread, again? it? tough. judging a person based on a reaction and having had enough of crap from people is no way to judge someone. i barely post here, how dare you exclude me based on a raving rant like i did? i see Because when 100% of the observed phenomenon suggests idiot, it's sometimes tricky to sit back and calmly assess confidence intervals. many people rant, if you were to exclude people based on that, you would've excluded them already. We're happy to accept the occasional rant from people who have shown themselves to be otherwise useful contributors. Several examples of that have already been posted in this thread. get a clue. attacking people isn't the way to do things - Matt signature.asc Description: Digital signature
Re: not starting packages at boot
On Tue, Jan 25, 2005 at 08:15:52AM +0100, Marc Haber wrote: On Mon, 24 Jan 2005 18:01:46 -0600, Steve Greenland [EMAIL PROTECTED] wrote: On 24-Jan-05, 03:45 (CST), Marc Haber [EMAIL PROTECTED] wrote: Last time I looked, invoke-rc.d was not yet a requirement to be used by packages. As far as I remember, it is for sarge, but not for woody and thus unuseable on woody, right? Do we already have packages that provide policy-rc.d? A quick apt-get search didn't show any. At present, the standard way to control this to edit the symlinks (or runlevel.conf, if using file-rc). This is good, because '/etc/init.d/foo start' still works. The standard for the future is invoke-rc.d. If a package doesn't support this, then the thing to do is to submit a wishlist bug for invoke-rc.d support, NOT create some new ad-hoc method. I am not a native speaker, but to me it looks like your message doesn't fit the questions I asked. Steve answered your first question. The second question makes no sense, since policy-rc.d is supposed to be written by the administrator to fit their local policy. - Matt signature.asc Description: Digital signature
Re: Trying to come back...
On Sun, Jan 23, 2005 at 02:40:43PM -0300, Nicol?s Lichtmaier wrote:
I've checked debian-keyring's changelog and I seem to have been marked
as emeritus:
~ Emeritus \E*meri*tus\, n.; pl. {Emeriti}. [L.]
~ A veteran who has honorably completed his service.
I certainly appreciate such an honorable title (!), but is there any
way of coming back from there? (I've already tried emailing
[EMAIL PROTECTED])
Have a look at the post from James Troup on the subject of different
developer states,
http://lists.debian.org/debian-devel-announce/2003/05/msg6.html. Should
explain most of your questions.
- Matt
signature.asc
Description: Digital signature
Accepted phpreports 0.3.6-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 19 Jan 2005 15:15:35 +1100 Source: phpreports Binary: phpreports Architecture: source all Version: 0.3.6-1 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: phpreports - XML-based report generator for PHP Closes: 289204 Changes: phpreports (0.3.6-1) unstable; urgency=low . * New upstream release (Closes: #289204). Files: 0d03b7de19e17cf42848417ec5bfc5ee 582 web optional phpreports_0.3.6-1.dsc 9fcead4cf6ca424656704b2b42dc2425 102292 web optional phpreports_0.3.6.orig.tar.gz 17fccaa00ec65a6a44e690c1373b317a 7460 web optional phpreports_0.3.6-1.diff.gz 4bcac19a1a0bb51661e70dc1f4b9e576 51432 web optional phpreports_0.3.6-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFB7ya3BEnrTWk1E4cRAmLtAJ0Qs+i44RLQ82zq5QuHhO+wl3Fl6wCfYe3X KZKsLMj6z5EEPphx97isLhU= =XZVv -END PGP SIGNATURE- Accepted: phpreports_0.3.6-1.diff.gz to pool/main/p/phpreports/phpreports_0.3.6-1.diff.gz phpreports_0.3.6-1.dsc to pool/main/p/phpreports/phpreports_0.3.6-1.dsc phpreports_0.3.6-1_all.deb to pool/main/p/phpreports/phpreports_0.3.6-1_all.deb phpreports_0.3.6.orig.tar.gz to pool/main/p/phpreports/phpreports_0.3.6.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: PHP application packaging policy/best practice?
On Wed, Jan 12, 2005 at 10:13:05AM +0100, Pierre Habouzit wrote: Le Mer 12 Janvier 2005 01:31, Matthew Palmer a ?crit : [No Cc needed, as per list policy] On Tue, Jan 11, 2005 at 11:47:42PM +0100, Pierre Habouzit wrote: it's _quite_ true that you don't need to play with include_path. your library has to know it's installed into /usr/share/php/app-or-library-name and either : * use some __FILE__ magic in its requires/includes * already use requires on app-or-library-name/*php files And I assume a lots of intern libraries are do not know how to do that. even some that ARE packaged into /usr/share/php/app-or-library-name what a mess. new try : It's only half-true that putting a lib into /usr/share/php/libname is fine. the lib has to be able to manage such a thing, and it's a requirement for a lib put into /usr/share/php/libname to be able to live there, without having to change anything in the include_path what I meant is that : libfile1.php live in /usr/share/php/mylib if libfile2.php has a : require 'libfile1.php'; anywhere, then it's not valid to package that lib in /usr/share/php/mylib, because libfile2.php NEEDS /usr/share/php/mylib to be in the include_path. So you patch libfile2.php to require_once 'mylib/libfile1.php' instead of just 'libfile1.php'. We've learnt to do this with C include files, why can't people work out the same thing for PHP? It's probably because of PHP's history as an easy, quick-hack language, that a lot of people with very little idea of even the basics of writing software have made an awful lot of really bad decisions... sure, but in C, you find the problem really quick : one compilation and you know if pathes are OK. in php, you cannot know ... you have to be really more careful. I'm sure you'll get user feedback quickly enough... and a quick grep and scan usually picks up most of the problems. - Matt signature.asc Description: Digital signature
Re: PHP application packaging policy/best practice?
[No Cc please, as per list policy] On Wed, Jan 12, 2005 at 10:16:43AM +0100, Pierre Habouzit wrote: Le Mer 12 Janvier 2005 01:31, Matthew Palmer a ?crit : So you patch libfile2.php to require_once 'mylib/libfile1.php' instead of just 'libfile1.php'. oh and btw, the suggestion I did is better (IMHO) : replace require_once 'libfile.php'; with require dirname(__FILE__).'/'.'libfile1.php'; because you are robust to _any_ mess done by the user with the include_path (for a zero cost). You even not assume that /usr/share/php is in the include_path. But it has two giant downsides: 1) It's ugly as all hell; and 2) Once people start getting into that habit, they forget all about other libraries, and where they might be, and start complaining bitterly and/or bundling other peoples' libraries into their libraries, which creates a mess. There's also the issue of how to get to the library in the first place from your application -- you then either need to hard-code the path somewhere in your app (which, if you do, I *will* beat you with a stick) or you're back to needing the include_path, which means that all of your dirname() magic isn't needed anyway. Oh, another useful tidbit -- file namespaces are useful. library/libfile1.php isn't very likely to conflict with another library/libfile1.php that someone wants to install, whereas libfile1.php could very well conflict. - Matt signature.asc Description: Digital signature
Re: Manpages licensed under GFDL without the license text included
On Tue, Jan 11, 2005 at 11:45:21PM +1300, Nick Phillips wrote: On Mon, Jan 10, 2005 at 10:57:56PM +0100, Francesco Poli wrote: On Mon, 10 Jan 2005 14:25:37 +1300 Nick Phillips wrote: The fact that we have conveniently ignored this problem when dealing with the GPL and BSD licenses so far does not make it go away. It is my understanding that Debian packages refer to the GPL text in /usr/share/common-licenses/ because the GPL license requires us to *accompany* the compiled form with the license text, rather than going beyond and requiring that the license text be *included* in the compiled form (that is fairly more demanding). Right. And when the .deb gets distributed on its own? Then whoever does the distributing should ensure that they comply with the terms of the licence of the software they're distributing, just as they need to now (eg distributing source for GPL'd stuff). - Matt signature.asc Description: Digital signature
Accepted fbpanel 4.0-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 23 Dec 2004 19:53:00 +1100 Source: fbpanel Binary: fbpanel Architecture: source i386 Version: 4.0-1 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: fbpanel- A lightweight X11 desktop panel Changes: fbpanel (4.0-1) unstable; urgency=low . * New upstream release. Files: e352ea194285ae184bfcf95de262bc61 591 x11 optional fbpanel_4.0-1.dsc 98851979577c1d53de45766117f81fbe 84161 x11 optional fbpanel_4.0.orig.tar.gz 56332cd3313973f7c4f9b7b3b6fd9583 4657 x11 optional fbpanel_4.0-1.diff.gz 6a9565d099b96ef6ada0380eb175f60e 90512 x11 optional fbpanel_4.0-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBypocBEnrTWk1E4cRAmleAKCueHRh46/zAwtOigmEUXFWOoVy7wCfRmh5 huu4Qm6NE7lairiBy/sRgcI= =6bQ4 -END PGP SIGNATURE- Accepted: fbpanel_4.0-1.diff.gz to pool/main/f/fbpanel/fbpanel_4.0-1.diff.gz fbpanel_4.0-1.dsc to pool/main/f/fbpanel/fbpanel_4.0-1.dsc fbpanel_4.0-1_i386.deb to pool/main/f/fbpanel/fbpanel_4.0-1_i386.deb fbpanel_4.0.orig.tar.gz to pool/main/f/fbpanel/fbpanel_4.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libapache-mod-auth-mysql 4.3.9-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 24 Dec 2004 00:30:40 +1100 Source: libapache-mod-auth-mysql Binary: libapache-mod-auth-mysql libapache2-mod-auth-mysql Architecture: source i386 Version: 4.3.9-1 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: libapache-mod-auth-mysql - Apache module for MySQL authentication libapache2-mod-auth-mysql - Apache 2 module for MySQL authentication Changes: libapache-mod-auth-mysql (4.3.9-1) unstable; urgency=low . * New upstream release, which codifies the way that multiple require statements are meant to work. Files: df6933bdb4e9e913a7a4ee7ccd0d4c2b 724 web optional libapache-mod-auth-mysql_4.3.9-1.dsc 9c1ecbe5fb64d4c93444311ff34bfe35 48479 web optional libapache-mod-auth-mysql_4.3.9.orig.tar.gz e79614e64edf4c92a341a544e49eb0fd 6794 web optional libapache-mod-auth-mysql_4.3.9-1.diff.gz f6548f692152721fca83d262297c5285 21518 web optional libapache-mod-auth-mysql_4.3.9-1_i386.deb 7ce917b8504e05b5e58b1f2c3dc6bc93 21932 web optional libapache2-mod-auth-mysql_4.3.9-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBytC3BEnrTWk1E4cRArfOAJ4gsZt7ArVgx4u2k15fzXJb3mCTmgCgouZw FBEPyFpUUie9cXvpBHp2zH0= =VJz8 -END PGP SIGNATURE- Accepted: libapache-mod-auth-mysql_4.3.9-1.diff.gz to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.9-1.diff.gz libapache-mod-auth-mysql_4.3.9-1.dsc to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.9-1.dsc libapache-mod-auth-mysql_4.3.9-1_i386.deb to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.9-1_i386.deb libapache-mod-auth-mysql_4.3.9.orig.tar.gz to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.9.orig.tar.gz libapache2-mod-auth-mysql_4.3.9-1_i386.deb to pool/main/liba/libapache-mod-auth-mysql/libapache2-mod-auth-mysql_4.3.9-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: LCC and blobs
On Fri, Dec 17, 2004 at 09:53:51AM +0100, Peter Van Eynde wrote: I'm stunned. So anything in a Debian package is software. With alien I can convert a tar.gz into a debian package, so all tar files are software. With tar I can create a tar.gz from any file, so all electronic data is software? And you restrictions that any package that depends on non-DFSG software to work cannot be in main means that after releasing sarge we have to remove from main: [Several rather absurd overgeneralisations] Should I go on? No, I think you've adequately demonstrated that you don't have the foggiest idea what you're talking about. - Matt signature.asc Description: Digital signature
Re: LCC and blobs
On Fri, Dec 17, 2004 at 10:45:07AM +0100, Peter Van Eynde wrote: Matthew Palmer wrote: Should I go on? No, I think you've adequately demonstrated that you don't have the foggiest idea what you're talking about. Ok. I'm game. Why? Where is the error my in applying your rules? Primary purpose, for a start. Perl can't go in main because it's useless without some non-free, perl-using app is ridiculous. - Matt signature.asc Description: Digital signature
Re: add Date: field to Packages files
On Sun, Dec 12, 2004 at 06:06:59PM -0500, Stephen Gran wrote: This one time, at band camp, Dan Jacobson said: Off line with just the Packages file, you can't tell a dusty 1997 package from an up to the minute state of the art package. You have the changelogs. Use them. You must have a magical Packages file -- I can't seem to find the changelogs in mine... - Matt signature.asc Description: Digital signature
Re: On the freeness of a BLOB-containing driver
On Sun, Dec 12, 2004 at 11:39:30PM +1100, Hamish Moffatt wrote: On Sat, Dec 11, 2004 at 04:43:48PM -0800, Bruce Perens wrote: [..] There are a number of reasons that a device's firmware won't generally be opened to us: 1. The manufacturer's concerns regarding the proprietary nature of information about their device that is below the bus. 2. The fact that misprogramming the device at that level can damage the hardware. 3. They aren't going to want to support more firmware versions than they have to. And 4. They're not allowed to by regulations, eg wireless hardware whose firmware cannot be distributed by FCC rule. I'm pretty sure that FUD got killed last time someone (perhaps you, even) raised it. From memory, the FCC rules only state that there must be a means for effectively preventing the modification of the firmware used in the device. Obscurity is not the only means of doing that. - Matt signature.asc Description: Digital signature
Re: On the freeness of a BLOB-containing driver
On Sun, Dec 12, 2004 at 02:30:51PM +0100, Wouter Verhelst wrote: Op za, 11-12-2004 te 20:12 -0500, schreef Glenn Maynard: On Sat, Dec 11, 2004 at 04:43:48PM -0800, Bruce Perens wrote: What about the rest of the driver? I think that if you remove the BLOB, it's Free Software. It talks to a bus interface, which is a natural demarcation between our Free Software and the proprietary hardware design. It loads an arbitrary firmware file into the device. The device might not work without the BLOB, but the driver's still free as long as it does not incorporate the BLOB. It's free, but it has a non-optional dependency on non-free software, If it does, then Samba depends on non-free software as well. Why? Samba can talk to Samba. I'm not aware of too many device drivers that can do something useful by talking to another device driver of the same type instead of the real hardware device... - Matt signature.asc Description: Digital signature
Re: LCC and blobs
On Fri, Dec 10, 2004 at 01:20:32PM +0100, Marco d'Itri wrote: On Dec 09, Bruce Perens [EMAIL PROTECTED] wrote: The whole system has to be DFSG-free. Debian won't compromise on that. Which DFSG? The original one or the clarified one? Give it up, Marco. Your little tantrums aren't cute. I have been thinking about the blob problem for a while. I propose to remove blobs from the driver, and store them as files in initramfs (the kernel-internal filesystem created by the stuff in /usr/src/linux*/usr) or initrd.img. At boot time, the drivers would look for the blobs and You may want to take a look at debian-legal, because some people there think that even free drivers for hardware devices which need an externally loaded firmware are not acceptable for main. I presume you're referring to drivers which are useless without a non-free firmware blob. We should treat them exactly the same way as any other Free software which is useless without some non-free component, and stick it in contrib. - Matt signature.asc Description: Digital signature
Re: Linux Core Consortium
On Thu, Dec 09, 2004 at 02:33:30PM -0600, John Hasler wrote: Why don't standard ABIs suffice? Not that I'm necessarily arguing in favour of a set of common packages, but defining an ABI is not a sufficient condition to ensure compatibility. Consider a function int s(int, int) -- you can have two ABI-compatible versions of this, one that adds it's arguments and one that multiplies them. ABI compatible, but different results. I'm not expecting that there'll be anything different to that degree in the LCC-defined packages, but pretty much any change in a library would have the effect of changing the way that library operates in some fashion -- and who's to say that some program isn't relying on the former (buggy) operation of the library? - Matt signature.asc Description: Digital signature
Re: Bug#283578: ITP: hot-babe -- erotic graphical system activitymonitor
On Mon, Dec 06, 2004 at 04:13:08PM +0100, Jonas Meurer wrote: On 06/12/2004 Steve Langasek wrote: Publishing houses never let writers edit their own work -- at least until they're famous and have mindless followers who'll buy and read any formulaic tripe they slap together. I don't think I like the idea of Debian becoming the Stephen King of the Open Source world. then we should reconsider the Social Contract and the GR, as these claim data to be software in our (debians) point of view. i personally always disliked the idea of all data in debian being software, as there are to many grey areas about that topic. And the award for greatest disjoint between mail and reply goes to Jonas Meurer. Other awards for this post include best hijacking of an unrelated thread to reignite dead topics, and The Non-sequitur award for cognative dissonance. - Matt signature.asc Description: Digital signature
Re: Bug#283578: ITP: hot-babe -- erotic graphical system activitymonitor
On Mon, Dec 06, 2004 at 04:28:51PM +1100, Brian May wrote: Manoj == Manoj Srivastava [EMAIL PROTECTED] writes: ManojWell, remember to exclude the Linux kernel, then. It Manoj is certainly not minor friendly. How many children look at the Linux kernel source code? How many children even know that it exists? I was a legal minor the first time I looked at the kernel sources. I know of several other people who are currently minors and in control of servers running Debian, and the number of people who say I first started using Debian at high school or equivalent suggests that my experience is in no way unique. Also, to the best my knowledge the kernel doesn't contain any pictures of naked people either. I might be mistaken. It does have language which qualifies as obscene. - Matt signature.asc Description: Digital signature
Re: Bug#283578: ITP: hot-babe -- erotic graphical system activitymonitor
On Sun, Dec 05, 2004 at 09:53:00PM -0800, Thomas Bushnell BSG wrote: Matthew Palmer [EMAIL PROTECTED] writes: Also, to the best my knowledge the kernel doesn't contain any pictures of naked people either. I might be mistaken. It does have language which qualifies as obscene. Not in the United States, at least, where obscene, as a matter of constitutional law, cannot describe text. Pfft, constitution. Like that'll ever hold up in court. - Matt signature.asc Description: Digital signature
Re: Bug#283994: ITP: glastree -- builds live backup trees, with branches for each day
On Fri, Dec 03, 2004 at 07:02:38PM +0100, Marc Haber wrote: On Fri, 3 Dec 2004 15:00:22 +1100, Matthew Palmer [EMAIL PROTECTED] wrote: 3314kB, including pdumpfs itself. I'll donate a 32MB USB key to store it all on for anyone that is *truly* that starved of space. Low-Memory systems are unlikely to have USB. I've got a pile of 1GB and 2GB HDDs here too, or will low memory systems not have IDE either? - Matt signature.asc Description: Digital signature
Re: Bug#283994: ITP: glastree -- builds live backup trees, with branches for each day
On Fri, Dec 03, 2004 at 07:17:45PM -0500, Anthony DeRobertis wrote: Matthew Palmer wrote: The advantage of using glastree over pdumpfs is that it is implemented in Perl rather than Ruby (this is in fact the reason that I encountered it in the first place). How is that an advantage of use? We're talking about free software. Modifying it to fit your needs is a perfectly valid, indeed encouraged use. Personally, I know perl, but not ruby. Sounds like you need to expand your repertoire a bit. I learnt Perl for exactly this reason -- I wanted to modify debconf, so I learnt (enough of) the language to do so. I didn't feel a need to reimplement it in a language I was familiar with first just so I could make my modifications. Can you imagine a world in which your argument was taken at face value? There would be a reimplementation of basically everything in every language under the sun, just so that some random person could avoid learning a new language. Ghods what a hideous mess that would be. - Matt signature.asc Description: Digital signature
Re: Bug#283994: ITP: glastree -- builds live backup trees, with branches for each day
On Thu, Dec 02, 2004 at 03:04:15PM -0500, Charles Fry wrote: The poor man's daily snapshot, glastree builds live backup trees, with branches for each day. Users directly browse the past to recover older documents or retrieve lost files. Hard links serve to compress out unchanged files, while modified ones are copied verbatim. A prune utility effects a constant, sliding window. Similar to pdumpfs; inspired by Plan9. In what ways is this package different to, say, dirvish, which I use in a manner which is, AFAICS, identical to the way this package operates? - Matt signature.asc Description: Digital signature
Re: Bug#283994: ITP: glastree -- builds live backup trees, with branches for each day
On Thu, Dec 02, 2004 at 05:59:09PM -0500, Charles Fry wrote: In what ways is this package different to, say, dirvish, which I use in a manner which is, AFAICS, identical to the way this package operates? glastree provides a subset of the functionality of dirvish. It is actually most closely related pdumpfs. Like pdumpfs, glastree works locally and not (explicitely) remotely. Is there any benefit to using glastree over dirvish or pdumpfs? - Matt signature.asc Description: Digital signature
Re: Bug#283994: ITP: glastree -- builds live backup trees, with branches for each day
On Thu, Dec 02, 2004 at 07:58:17PM -0500, Charles Fry wrote: On Thu, Dec 02, 2004 at 05:59:09PM -0500, Charles Fry wrote: In what ways is this package different to, say, dirvish, which I use in a manner which is, AFAICS, identical to the way this package operates? glastree provides a subset of the functionality of dirvish. It is actually most closely related pdumpfs. Like pdumpfs, glastree works locally and not (explicitely) remotely. Is there any benefit to using glastree over dirvish or pdumpfs? The advantage of using glastree over pdumpfs is that it is implemented in Perl rather than Ruby (this is in fact the reason that I encountered it in the first place). How is that an advantage of use? - Matt signature.asc Description: Digital signature
Re: Bug#283994: ITP: glastree -- builds live backup trees, with branches for each day
On Thu, Dec 02, 2004 at 10:30:05PM -0500, Charles Fry wrote: Is there any benefit to using glastree over dirvish or pdumpfs? The advantage of using glastree over pdumpfs is that it is implemented in Perl rather than Ruby (this is in fact the reason that I encountered it in the first place). How is that an advantage of use? Well, if one had a small system and desired not to install ruby, it would still be possible to obtain pdumpfs' functionality. Of course that could be called an installation issue rather than a usability issue. 3314kB, including pdumpfs itself. I'll donate a 32MB USB key to store it all on for anyone that is *truly* that starved of space. Meanwhile, what's the total installed space for glastree if you're not a Perl lover? - Matt signature.asc Description: Digital signature
Re: Bug#283994: ITP: glastree -- builds live backup trees, with branches for each day
On Fri, Dec 03, 2004 at 04:10:01AM +, Henning Makholm wrote: Scripsit Matthew Palmer [EMAIL PROTECTED] Meanwhile, what's the total installed space for glastree if you're not a Perl lover? Perl-base is 'Proirity: required' and 'Essential: yes'. It doesn't even have to be depended on. So? There's lots more to Perl than perl-base. Glastree may require a pile of extra modules and bits and pieces to run, all of which chew space which you wouldn't need otherwise. This is what I wanted to know. - Matt signature.asc Description: Digital signature
Re: Bug#283751: ITP: fakepop -- fake pop3 server to warn users that only pop3-ssl is available
On Wed, Dec 01, 2004 at 12:12:12PM +0100, Petter Reinholdtsen wrote: [Steve McIntyre] So, let me get this straight - fakepop will allow people to log in (using their username and password) in the clear and THEN tell them that they should have used POP over SSL instead. Quite how is this better than connection refused? connection refused generate a support request from the user, and increases the load on the support organisation. The users will ask what the error message mean, and will have to get the explanations individually. A message poping up every time the user connect to the wrong service will normally change the users behaviour without any extra work for the support organisation. It appears that you have missed the point. One of the primary reasons why you would use pops rather than pop3 (I presume) is so that your authentication credentials aren't sent in the clear. This daemon allows the user to send their credentials en clair before telling them that they need to reconfigure their mail client. To quote the Guinness ad, Brilliant! - Matt signature.asc Description: Digital signature
Re: Bug#283751: ITP: fakepop -- fake pop3 server to warn users that only pop3-ssl is available
On Wed, Dec 01, 2004 at 05:17:33AM -0600, Ron Johnson wrote: On Wed, 2004-12-01 at 11:04 +, Steve McIntyre wrote: So, let me get this straight - fakepop will allow people to log in (using their username and password) in the clear and THEN tell them that they should have used POP over SSL instead. Quite how is this better than connection refused? Read the description: You can customize messages in /etc/fakepop/ directory to teach your users how they should configure their mail clients to use pop3-ssl instead of pop3 So I can put All your mail is belong to us in my /etc/fakepop/ directory, so that people know that their passwords *have* been successfully sent in the clear before being told to reconfigure their mail client? Well, *I'm* comforted. - Matt signature.asc Description: Digital signature
Re: Bug#283578: ITP: hot-babe -- erotic graphical system activitymonitor
On Wed, Dec 01, 2004 at 08:50:08PM +0200, Kalle Kivimaa wrote: Yes, hotbabe is sexist (at least in it's current incarnation - if it included a male theme then it would only be sexually offensive to some) Anyone who feels that hot-babe would become less sexually offensive because it included naked male images as well as naked female images really does need to rethink their ideas about offensiveness. Somehow putting more offensive images into a package doesn't strike me as being the way to make something less offensive. Personally, I don't have a problem with the package as-is -- the pictures aren't exactly the most graphic thing that's likely to pop up unannounced in a web-browser window, but the authorities frown on distributing anything tittilating to minors in a lot of places, so I'd vote for making it a series of pictures of a tree shedding it's leaves or something in the default incarnation. - Matt signature.asc Description: Digital signature
Re: Bug#283578: ITP: hot-babe -- erotic graphical system activity monitor
On Thu, Dec 02, 2004 at 02:38:54AM +0100, Cesar Martinez Izquierdo wrote: I can volunteer to provide some naked photos of myself, but I guess they will be more suitable for section fun than section erotic. There was discussion on IRC in the last few days about a Men of Debian calendar. That'd provide plenty of images suitable for this sort of thing... - Matt signature.asc Description: Digital signature
Accepted cyrus-imapd 1.5.19-20 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 11 Aug 2004 14:35:43 +1000 Source: cyrus-imapd Binary: cyrus-imapd cyrus-common cyrus-pop3d cyrus-dev cyrus-admin cyrus-news-spool Architecture: source i386 Version: 1.5.19-20 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: cyrus-admin - CMU Cyrus mail system (administration tool) cyrus-common - CMU Cyrus mail system (common files) cyrus-dev - CMU Cyrus mail system (developer files) cyrus-imapd - CMU Cyrus mail system (IMAP support) cyrus-news-spool - CMU Cyrus mail system (News spool support) cyrus-pop3d - CMU Cyrus mail system (POP3 support) Changes: cyrus-imapd (1.5.19-20) unstable; urgency=low . * Guarded a couple of potentially problematic character pointers in imap/mboxlist.c. * Fixed up the cyrus-news-spool debhelper control files so that the package actually has something useful in it. * Security fix for buffer overflows in argument parser for partial and fetch, and an exploitable overflow in OOM situations. (CAN-2004-1012, CAN-2004-1013). From the Ubuntu security advisory for cyrus21-imapd for the same CVEs. Files: a0332089309fbd96b38b4199ed85952c 703 mail extra cyrus-imapd_1.5.19-20.dsc e7804252e8af3c828e8492023b2a3b25 36904 mail extra cyrus-imapd_1.5.19-20.diff.gz 467cbfab1fbfe4db761dd181b77ab087 394012 mail extra cyrus-common_1.5.19-20_i386.deb d82e1da1122da4448f6584c9ea45ce5b 130064 mail extra cyrus-imapd_1.5.19-20_i386.deb 330a44009b1b5f390c4e616cd194ee9f 62364 mail extra cyrus-pop3d_1.5.19-20_i386.deb d430a41ec8e685916415c9195cd6b35f 131256 mail extra cyrus-news-spool_1.5.19-20_i386.deb e9d8576634d162ef6a557f1480e3d823 42612 mail extra cyrus-admin_1.5.19-20_i386.deb ec98879ff29ac8101b632b17ea40eecb 79712 devel extra cyrus-dev_1.5.19-20_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBpVwSBEnrTWk1E4cRArB6AJ0b93aSgApzgRtXgaxHq+FmW9ADPACfTCNl Iz0Iv7Klp9C5fvk4KnNahPM= =zrf2 -END PGP SIGNATURE- Accepted: cyrus-admin_1.5.19-20_i386.deb to pool/main/c/cyrus-imapd/cyrus-admin_1.5.19-20_i386.deb cyrus-common_1.5.19-20_i386.deb to pool/main/c/cyrus-imapd/cyrus-common_1.5.19-20_i386.deb cyrus-dev_1.5.19-20_i386.deb to pool/main/c/cyrus-imapd/cyrus-dev_1.5.19-20_i386.deb cyrus-imapd_1.5.19-20.diff.gz to pool/main/c/cyrus-imapd/cyrus-imapd_1.5.19-20.diff.gz cyrus-imapd_1.5.19-20.dsc to pool/main/c/cyrus-imapd/cyrus-imapd_1.5.19-20.dsc cyrus-imapd_1.5.19-20_i386.deb to pool/main/c/cyrus-imapd/cyrus-imapd_1.5.19-20_i386.deb cyrus-news-spool_1.5.19-20_i386.deb to pool/main/c/cyrus-imapd/cyrus-news-spool_1.5.19-20_i386.deb cyrus-pop3d_1.5.19-20_i386.deb to pool/main/c/cyrus-imapd/cyrus-pop3d_1.5.19-20_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Select which conffiles shall be raplaced an which not
On Tue, Nov 16, 2004 at 01:29:38PM +0100, Free Ekanayaka wrote: When running apt-get dist-upgrade I'd like to be able to set a list of packages whose confiles shall be replaced by the newer versions supplied by the package (if any) , while other packages' confiles should be keep the locally modified version. Is this possible? Not that I know of, but it would be an interesting modification to make to dpkg (which is the program that manages the replacement of modified conffiles). - Matt signature.asc Description: Digital signature
Accepted phpunit 1.1.1-2 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 16 Nov 2004 15:19:32 +1100 Source: phpunit Binary: phpunit Architecture: source all Version: 1.1.1-2 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: phpunit- Unit testing suite for PHP4 Changes: phpunit (1.1.1-2) unstable; urgency=low . * Improved the message generation, including some refactoring and improved message passing. Files: c57cd55df4d4892f99c21a35195ed3b8 569 web optional phpunit_1.1.1-2.dsc 333f11c89111732981735a857bd58cd8 3757 web optional phpunit_1.1.1-2.diff.gz 04ecc4e4603102bb280ff08bd241bec9 16838 web optional phpunit_1.1.1-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBmYHzBEnrTWk1E4cRArg3AKCQ3FsDHFmaiMD4McCfBDCE6InS2wCfZKIn dCKKVnaZoKy+OGyaKGsZa9w= =t7U0 -END PGP SIGNATURE- Accepted: phpunit_1.1.1-2.diff.gz to pool/main/p/phpunit/phpunit_1.1.1-2.diff.gz phpunit_1.1.1-2.dsc to pool/main/p/phpunit/phpunit_1.1.1-2.dsc phpunit_1.1.1-2_all.deb to pool/main/p/phpunit/phpunit_1.1.1-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted phpunit 1.1.1-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 6 Nov 2004 18:05:58 +1100 Source: phpunit Binary: phpunit Architecture: source all Version: 1.1.1-1 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: phpunit- Unit testing suite for PHP4 Closes: 273649 Changes: phpunit (1.1.1-1) unstable; urgency=low . * Initial release. Closes: #273649. Nice version number, don't you think? Files: 608148c8406ca70cca343e0b74fc403d 569 web optional phpunit_1.1.1-1.dsc b7c732b20cd379faad9a0121417562e0 15412 web optional phpunit_1.1.1.orig.tar.gz 85b2c12d7dfeb598a3c853da54f9e996 2624 web optional phpunit_1.1.1-1.diff.gz 8d515e80693bd4adf39adfa5b1373d8f 16494 web optional phpunit_1.1.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBjM2vBEnrTWk1E4cRAp+7AJ9NcG/1OVUIPAUzrP8C9psI7s/RBQCeKlwy Oidz+WMYGASrfidYnAhqI+E= =325K -END PGP SIGNATURE- Accepted: phpunit_1.1.1-1.diff.gz to pool/main/p/phpunit/phpunit_1.1.1-1.diff.gz phpunit_1.1.1-1.dsc to pool/main/p/phpunit/phpunit_1.1.1-1.dsc phpunit_1.1.1-1_all.deb to pool/main/p/phpunit/phpunit_1.1.1-1_all.deb phpunit_1.1.1.orig.tar.gz to pool/main/p/phpunit/phpunit_1.1.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Use CVS/Subversion/... as a fast way to update apt lists?
On Thu, Nov 11, 2004 at 12:31:18PM +0300, Nikita V. Youshchenko wrote: On the topic of all those talks about reducing network traffic caused by apt-get update, without putting too high load into server (as rsync does). Can't CVS (or Subversion or other similar tool) solve this problem? Seems that if apt-get update will turn into 'cvs update', it will save network traffic, and not put too much load into server. The cost is the This is really just the apt patch idea. You're just pushing the multi-patch problem off onto CVS rather than apt. - Matt signature.asc Description: Digital signature
Accepted fbpanel 3.16-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 11 Nov 2004 21:45:09 +1100 Source: fbpanel Binary: fbpanel Architecture: source i386 Version: 3.16-2 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: fbpanel- A lightweight X11 desktop panel Closes: 280648 Changes: fbpanel (3.16-2) unstable; urgency=low . * Remove bollocks dpatch Build-dep * Fix a erroneous warning pointing users to an incorrect config location. Closes: #280648. Files: 42fcff68204fcc686c41e3bbadb5e9fb 594 x11 optional fbpanel_3.16-2.dsc e8ea9a2f0f4395c9db5865f53d2664bc 4770 x11 optional fbpanel_3.16-2.diff.gz 835269c95d62ab07e7ec647de8e959a8 88324 x11 optional fbpanel_3.16-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBk1TBBEnrTWk1E4cRAo7hAJ9otYd6FqgZ6Yxn3e8KRafuOFiYXQCeOpGY pyBYi3E5Gu7x3dvxOe8R16g= =rn94 -END PGP SIGNATURE- Accepted: fbpanel_3.16-2.diff.gz to pool/main/f/fbpanel/fbpanel_3.16-2.diff.gz fbpanel_3.16-2.dsc to pool/main/f/fbpanel/fbpanel_3.16-2.dsc fbpanel_3.16-2_i386.deb to pool/main/f/fbpanel/fbpanel_3.16-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Company launch with Linux system
On Sun, Oct 10, 2004 at 07:27:06PM +0200, Hartmut Rummel wrote: This is cory yearwood from Exsis. Please can you remove the e-mail from your website.. And yet the name in your From: line is Hartmut Rummel, and you're using a totally different e-mail address. Either way, I doubt that post will be taken off the archive. - Matt signature.asc Description: Digital signature
Accepted fbpanel 3.16-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 7 Nov 2004 16:14:03 +1100 Source: fbpanel Binary: fbpanel Architecture: source i386 Version: 3.16-1 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: fbpanel- A lightweight X11 desktop panel Closes: 279525 Changes: fbpanel (3.16-1) unstable; urgency=low . * New upstream release. (Closes: #279525) * Discontinued use of dpatch; we now use feature branches for that sort of thing. Files: 13c2fad8722bd7d9a76a03e00a1ad3a0 602 x11 optional fbpanel_3.16-1.dsc 447292dbb0ccb5bb2e266d98e11536bc 79824 x11 optional fbpanel_3.16.orig.tar.gz d336beda34829a8e807c4856a1a5b975 4398 x11 optional fbpanel_3.16-1.diff.gz b6c1a5efb33bb2dd61cbb5dba704d5ad 88498 x11 optional fbpanel_3.16-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBjbMmBEnrTWk1E4cRAmGMAJ9lBzPQDEdxX3ubxwjc4Pi6lIWlCACgm63Q L78S2NpmQXyIP+g41H6011Y= =7Yi1 -END PGP SIGNATURE- Accepted: fbpanel_3.16-1.diff.gz to pool/main/f/fbpanel/fbpanel_3.16-1.diff.gz fbpanel_3.16-1.dsc to pool/main/f/fbpanel/fbpanel_3.16-1.dsc fbpanel_3.16-1_i386.deb to pool/main/f/fbpanel/fbpanel_3.16-1_i386.deb fbpanel_3.16.orig.tar.gz to pool/main/f/fbpanel/fbpanel_3.16.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian.org e-mail address and SPF/SRS
On Fri, Nov 05, 2004 at 11:48:29AM -0200, Gustavo Franco wrote: On Fri, 5 Nov 2004 16:38:20 +1100, Matthew Palmer [EMAIL PROTECTED] wrote: That's a question you'll have to ask of Yahoo and the SPF people. My guess is that the pushers of these schemes want their thing adopted for whatever reason (corporate greed, personal gratification, whatever), but they know that random people don't care enough about e-mail forgery to really take it up. However, most everyone online seems to be pretty pissed off about spam, so saying this stops spam will get people interested in the scheme, and they're hoping that people kinda forget that the system was supposed to stop spam when people work out, definitively, that it doesn't actually do squat to stop spam. this stops spam ? It isn't what they're saying, please read: We've done this dance before. I don't get as far as the FAQ, because the misinformation starts right on the front page (http://spf.pobox.com, What is SPF?, third paragraph): SMTP receivers verify the envelope sender address against this information, and can distinguish legitimate mail from spam before any message data is transmitted. That is a big leap from can verify if a message is being sent from a server which has been listed as being legitimate for the domain. Burying the real facts in the bowels of some FAQ doesn't stop the popular misconception being this is an anti-spam solution. Find 10 people off the street who know what SPF is, ask them what SPF is for, and I reckon probably at least 8 of them will say it's for stopping spam. They got that impression from somewhere, and I don't see the SPF guys madly running around trying to change that impression of their software. Last time this came up, someone posted an interview with one of the SPF authors, who was quite happy to let the interviewer prattle on about SPF being the FUSSP, without any correction. - Matt signature.asc Description: Digital signature
Accepted libapache-mod-auth-mysql 4.3.8-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 5 Nov 2004 22:07:14 +1100 Source: libapache-mod-auth-mysql Binary: libapache-mod-auth-mysql libapache2-mod-auth-mysql Architecture: source i386 Version: 4.3.8-1 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: libapache-mod-auth-mysql - Apache module for MySQL authentication libapache2-mod-auth-mysql - Apache 2 module for MySQL authentication Changes: libapache-mod-auth-mysql (4.3.8-1) unstable; urgency=low . * Now converted to a non-native package, as I've got a user who is not a Debianite. * Fixed the configure script to properly detect whether libcrypt needs to be a separate library. * Guarded all instances of CRYPT_DES_ENCRYPTION_FLAG, so you can build the module without crypt() being present. Files: e2b85a3f88423798b042d3a981c4ccee 724 web optional libapache-mod-auth-mysql_4.3.8-1.dsc 84a248cd69cb4e5380dba0ca7a7b3b84 53080 web optional libapache-mod-auth-mysql_4.3.8.orig.tar.gz cfe9090d912bb9f4fdb889d1587bc59d 6725 web optional libapache-mod-auth-mysql_4.3.8-1.diff.gz 26aea81a9cfa982ff187fc390b8cf6d8 21072 web optional libapache-mod-auth-mysql_4.3.8-1_i386.deb 9bdab1bdec74d1e38d83406e24da1bfa 21474 web optional libapache2-mod-auth-mysql_4.3.8-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBi23nBEnrTWk1E4cRAs6+AJ4pnjCwha56I8zlzkz1IaofFDGzvgCePivM OenRx5UqJHBbGcrrjZfDODw= =Cog4 -END PGP SIGNATURE- Accepted: libapache-mod-auth-mysql_4.3.8-1.diff.gz to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.8-1.diff.gz libapache-mod-auth-mysql_4.3.8-1.dsc to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.8-1.dsc libapache-mod-auth-mysql_4.3.8-1_i386.deb to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.8-1_i386.deb libapache-mod-auth-mysql_4.3.8.orig.tar.gz to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.8.orig.tar.gz libapache2-mod-auth-mysql_4.3.8-1_i386.deb to pool/main/liba/libapache-mod-auth-mysql/libapache2-mod-auth-mysql_4.3.8-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian.org e-mail address and SPF/SRS
On Thu, Nov 04, 2004 at 09:59:44AM +0100, Tollef Fog Heen wrote: * Osamu Aoki | If you know easy way to avoid this problem exists, please let me know. | (Changing ISP is certainly an option.) Use BSTMP to gluck. (If your ISP can't be whacked into turning it off/Implementing yahoo's DomainKeys proposal, which looks fairly sane to me; http://antispam.yahoo.com/domainkeys ) Uhm, having just read through the supplied URL, I can't agree with the sanity of the proposal. It appears to require that headers not be modified at all in transit (which means that forwarding becomes impossible), and suffers from the same problem as most mail server crypto issues -- domain names (and the associated keys) are trivial to obtain. It's just too easy to get a new domain to spam from, and rejecting mail from unknown domains reduces the system to a fancy whitelist. If the signed headers problem isn't as bad as I think it is, then it certainly looks saner than SPF, but the FAQ question How does DomainKeys work with mailing lists? give me chills (and not the good kind). Oh damn, I think I've just started the flamewar again... - Matt signature.asc Description: Digital signature
Re: debian.org e-mail address and SPF/SRS
On Thu, Nov 04, 2004 at 12:11:07PM +0100, Tollef Fog Heen wrote: * Matthew Palmer | Uhm, having just read through the supplied URL, I can't agree with the | sanity of the proposal. | It appears to require that headers not be modified at all in transit | (which means that forwarding becomes impossible), Uhm, which headers are modified by a forwarding agent? New headers can be prepended just fine, and you don't have to sign all the headers. See, that's the thing that the FAQ was unclear on. If you don't have to sign all headers, then you're OK. I was thinking the attachment of Received: headers as being particularly problematic. To quote the FAQ: Mailing lists that do not change the content or re-arrange or append headers will be DomainKey compatible with no changes required. Mailing lists that change the message and headers should re-sign the message with their own private key and claim authorship of the message. That suggests to me that sticking new headers into the mix would screw up the signature. | and suffers from the same problem as most mail server crypto issues | -- domain names (and the associated keys) are trivial to obtain. | It's just too easy to get a new domain to spam from, and rejecting | mail from unknown domains reduces the system to a fancy whitelist. It gives you traceability and it can be used to prevent joe-jobs. It's not a silver bullet solution against spam. And yet it's being touted as one. I predict that the effect of this system on spam levels will be about as detectable on a spam vs time graph as a fart in a hurricane. | If the signed headers problem isn't as bad as I think it is, then it | certainly looks saner than SPF, but the FAQ question How does DomainKeys | work with mailing lists? give me chills (and not the good kind). Which mailing list systems do you know of that change headers and don't claim the message (basically using themselves as the envelope sender). I can certainly imagine there being such beasts out there, but most of the larger ones certainly don't, as they would then have no way to catch bouncing members. DomainKeys, by my reading, doesn't use the envelope sender, but instead uses the visible headers (such as From:) to work out what to authenticate. Again, to quote the FAQ: What does DomainKeys verify? DomainKeys examines the From: and Sender: headers' domain to protect the user and deliver the best possible user experience. Desktop mail clients like Microsoft Outlook show these headers in their user interfaces. If the user establishes their trust based on the these domains, then so should any system built to verify whether that trust is warranted. If I examine the message you sent, both the From: and Sender: point to your domain, but many headers have presumably been added by the Debian mailing list software, which would require a remade header signature. That signature would then fail to verify because the From: and Sender: lines aren't pointing at Debian. I'll reiterate that I haven't read the spec, so if the FAQ is contradicted by the actual spec, I'll stand corrected, but on the basis of what I've read in the FAQ, I have no interest in the spec itself, because it's not going to be any better than SPF in practice. Which is a pity, because the initial idea is quite a decent one. - Matt signature.asc Description: Digital signature
Re: debian.org e-mail address and SPF/SRS
On Fri, Nov 05, 2004 at 03:15:09PM +1100, Rob Weir wrote: On Thu, Nov 04, 2004 at 10:37:08PM +1100, Matthew Palmer said On Thu, Nov 04, 2004 at 12:11:07PM +0100, Tollef Fog Heen wrote: It gives you traceability and it can be used to prevent joe-jobs. It's not a silver bullet solution against spam. And yet it's being touted as one. I predict that the effect of this system on spam levels will be about as detectable on a spam vs time graph as a fart in a hurricane. I'm not sure why it's being touted as one; SPF has the same issue. Encouraging adoption of something by misrepresenting its use seems rather pointless in the end. That's a question you'll have to ask of Yahoo and the SPF people. My guess is that the pushers of these schemes want their thing adopted for whatever reason (corporate greed, personal gratification, whatever), but they know that random people don't care enough about e-mail forgery to really take it up. However, most everyone online seems to be pretty pissed off about spam, so saying this stops spam will get people interested in the scheme, and they're hoping that people kinda forget that the system was supposed to stop spam when people work out, definitively, that it doesn't actually do squat to stop spam. - Matt signature.asc Description: Digital signature
Re: debian.org e-mail address and SPF/SRS
On Thu, Nov 04, 2004 at 12:15:19AM +0100, Osamu Aoki wrote: I am facing a problem with my ISP started filtering incoming mails with SPF. Since AOL adopted it, it seems becoming quite popular as I see it. [...] SPF has known issue with e-mail forwarder such as pobox.com. I think debian.org mail address is no exception. This is expected behavior. Since debian.org address is used frequently used to receive debian bug report, this is not a desirable situation. Unless some serious concern was raised here, I think implementing SRS[3] type infrastructure will be nice. If you know easy way to avoid this problem exists, please let me know. (Changing ISP is certainly an option.) That's more or less your option. Your current ISP feels that it is market-advantageous to do that for all it's customers, seemingly without a means for you to turn it off if you don't want it. As such, your option would be to firstly talk to your ISP about their practice, and explain that you, as a customer, do not want this service. If they are not amenable to providing you with the service you want, then you would be well advised to move to an ISP that will provide you with the service you want. Only time will tell if SPF will be a great marketing draw-card or not. - Matt signature.asc Description: Digital signature
Re: Apt-Torrent project
On Sat, Oct 30, 2004 at 10:35:53AM +0200, Arnaud Kyheng wrote: I love the Debian project, and I have worked on a new development for it: Apt-Torrent :) Apt-Torrent is an apt proxy to the Bittorrent network. For security, the package listing, and the .torrent files are downloaded from a regular http server, as usual for a package, but then the whole package is fetched via bittorrent protocol and forwarded to apt :) [...] I would like to know what do you think of it :) Well, I don't do P2P myself so much, but from what I know of it, this sounds like a pretty cool thing, if it gets off the ground and gets a lot of users. If we can get individually-signed .debs, you won't even need to worry so much about getting the torrent files off a trusted mirror... At any rate, it looks good, and I, for one, hope to see a lot more about it in the future. - Matt signature.asc Description: Digital signature
Re: Apt-Torrent project
On Sat, Oct 30, 2004 at 12:00:16PM +0200, Marc 'HE' Brockschmidt wrote: Matthew Palmer [EMAIL PROTECTED] writes: [...] If we can get individually-signed .debs, you won't even need to worry so much about getting the torrent files off a trusted mirror... dpkg-sig exists. Use it :) Thanks for that, and I know all about it and sign all of my internally-generated .debs for work. However, I don't bother doing it for my Debian-uploaded ones because (a) anything built by an autobuilder won't have any sigs in it, (b) most other developers aren't signing, and (c) at this point in time, signed Release files and tracking down from there is the best way of verifying packages, and it's the only way that has much of a chance (from picking a package at random) of working. - Matt signature.asc Description: Digital signature
Re: Ubuntu discussion at planet.debian.org
On Sat, Oct 23, 2004 at 02:40:24PM -0500, Manoj Srivastava wrote: On Sat, 23 Oct 2004 11:54:05 +0200, J?r?me Marant [EMAIL PROTECTED] said: Manoj Srivastava [EMAIL PROTECTED] writes: Okay, that's what t-p-u is roughly for, but the fact is that it's quite painful. Could you elaborate on that? Why is it so painful? Probably because you need maintain packages for both unstable and testing at the same time. That is a simple branching issue in the version control system, no? A huge rush of air fills the list as hundreds of developers fill their lungs to collectively say I don't use version control... - Matt signature.asc Description: Digital signature
Accepted phpreports 0.3.4-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Oct 2004 16:30:28 +1000 Source: phpreports Binary: phpreports Architecture: source all Version: 0.3.4-1 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: phpreports - An XML-based report generator for PHP Changes: phpreports (0.3.4-1) unstable; urgency=low . * New upstream release. Functionality unchanged. Files: c50cf716c6ea71c24bff7f7d52bc5d27 581 web optional phpreports_0.3.4-1.dsc 61624294791d1bdbccc48e8fb1ece57e 99376 web optional phpreports_0.3.4.orig.tar.gz 0960a81a09ff42ec740e2d87b2956f52 2540 web optional phpreports_0.3.4-1.diff.gz 0b423026901651b24c520de3d97324dd 49422 web optional phpreports_0.3.4-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBeKf3BEnrTWk1E4cRAtxeAJ9NA2r72oA28l2JYeX62u1irXtEiACggsvC jzn9EXYn+oOi1v0FHPSZ33w= =m1Fu -END PGP SIGNATURE- Accepted: phpreports_0.3.4-1.diff.gz to pool/main/p/phpreports/phpreports_0.3.4-1.diff.gz phpreports_0.3.4-1.dsc to pool/main/p/phpreports/phpreports_0.3.4-1.dsc phpreports_0.3.4-1_all.deb to pool/main/p/phpreports/phpreports_0.3.4-1_all.deb phpreports_0.3.4.orig.tar.gz to pool/main/p/phpreports/phpreports_0.3.4.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Python executables inside libraries
On Thu, Oct 21, 2004 at 11:41:09PM +0200, Magnus Therning wrote: On Thu, Oct 21, 2004 at 10:53:32PM +1000, Matthew Palmer wrote: On Thu, Oct 21, 2004 at 09:25:41AM +0200, Magnus Therning wrote: I have a silly little problem with getting Python's distutils to play nice with Debian packaging. The library I am packaging (PyGGy) has a few python files that double as executable scripts (in short they have '#! /usr/bin/python' at the top of the file, while still being part of a library, and they are executable, I am sure you know what I mean ;-). Distutils insists on leaving them non-executable after a './setup.py build'. However, since they contain that first line lintian complains that they are scripts, but non-executable: [...] Do I leave it them the way they are, or is there a nice way of resolving this? Resolve the problem by making up your mind -- are they scripts (and hence need +x and quite possibly a home in /usr/bin) or are they library files, and hence no #! and a -x. Well, they can't go into /usr/bin, they are part of the library. However, for some reason upstream decided to put the python equivalent of a main() in some of the files that make up the library. The package I am trying to Debianise is PyGgy (bug #277567). It's a lexer/parser for Python. Upstream decided that the parser package (pyggy.pyggy) should double as an executable script (it creates parser tables for all parser description files it's given on the command line). This sort of thing isn't uncommon in Python, I believe. Would you reasonably want to execute those scripts in and of themselves from another program? If yes, then +x. If not, s/^#!.*$//. - Matt
Accepted libapache-mod-auth-mysql 4.3.7 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 20 Sep 2004 10:26:41 +1000 Source: libapache-mod-auth-mysql Binary: libapache-mod-auth-mysql libapache2-mod-auth-mysql Architecture: source i386 Version: 4.3.7 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: libapache-mod-auth-mysql - Apache module for MySQL authentication libapache2-mod-auth-mysql - Apache 2 module for MySQL authentication Closes: 271730 Changes: libapache-mod-auth-mysql (4.3.7) unstable; urgency=low . * Added a new encryption type, SHA1Sum, using a patch kindly prepared by Joseph Walton. Closes: #271730. Files: 0c17513bcb7d9c0c5812abaa9a6ab167 637 web optional libapache-mod-auth-mysql_4.3.7.dsc 1c4c0d50a248ef16baffc105f9e6f87d 54530 web optional libapache-mod-auth-mysql_4.3.7.tar.gz 98c355cf5a9e68db0bd99fda223d9e78 20892 web optional libapache-mod-auth-mysql_4.3.7_i386.deb ea752cd246b1d8a4641d74b6b3f46048 21294 web optional libapache2-mod-auth-mysql_4.3.7_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBTkRWBEnrTWk1E4cRAs1pAJ9HvW8JnblyxlF0C9zSZxTivT0AjQCfcGlu R1998kPrZRJLpcuB/ry9g1I= =v+3c -END PGP SIGNATURE- Accepted: libapache-mod-auth-mysql_4.3.7.dsc to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.7.dsc libapache-mod-auth-mysql_4.3.7.tar.gz to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.7.tar.gz libapache-mod-auth-mysql_4.3.7_i386.deb to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.7_i386.deb libapache2-mod-auth-mysql_4.3.7_i386.deb to pool/main/liba/libapache-mod-auth-mysql/libapache2-mod-auth-mysql_4.3.7_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libapache-mod-auth-mysql 4.3.6 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 15 Sep 2004 10:59:26 +1000 Source: libapache-mod-auth-mysql Binary: libapache-mod-auth-mysql libapache2-mod-auth-mysql Architecture: source i386 Version: 4.3.6 Distribution: unstable Urgency: high Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: libapache-mod-auth-mysql - Apache module for MySQL authentication libapache2-mod-auth-mysql - Apache 2 module for MySQL authentication Closes: 271721 Changes: libapache-mod-auth-mysql (4.3.6) unstable; urgency=high . * Fixed a security bug where an error in the execution of mysql_check_group() causes the group check to succeed. Closes: #271721. Thanks to Joseph Walton for finding the problem and providing a patch. Files: 4ede7a9fb4b770532510fa51d0e422ab 637 web optional libapache-mod-auth-mysql_4.3.6.dsc 03984dc552e35f8501ae617242123e14 54164 web optional libapache-mod-auth-mysql_4.3.6.tar.gz da9f3c1b59b30c676ccbae96dbe7aba6 20580 web optional libapache-mod-auth-mysql_4.3.6_i386.deb b1d77e36722d5fd4e1c8c2f2cbb7d6ef 20946 web optional libapache2-mod-auth-mysql_4.3.6_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBSFuvBEnrTWk1E4cRAmjKAJwIy+UUqB240qFtKGPS5l9ytTTqxACePJkT 5V7bbW5PGNF7mfylklyIynE= =v9aT -END PGP SIGNATURE- Accepted: libapache-mod-auth-mysql_4.3.6.dsc to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.6.dsc libapache-mod-auth-mysql_4.3.6.tar.gz to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.6.tar.gz libapache-mod-auth-mysql_4.3.6_i386.deb to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.6_i386.deb libapache2-mod-auth-mysql_4.3.6_i386.deb to pool/main/liba/libapache-mod-auth-mysql/libapache2-mod-auth-mysql_4.3.6_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libapache-mod-auth-mysql 4.3.5 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 22 Aug 2004 21:08:58 +1000 Source: libapache-mod-auth-mysql Binary: libapache-mod-auth-mysql libapache2-mod-auth-mysql Architecture: source i386 Version: 4.3.5 Distribution: unstable Urgency: high Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: libapache-mod-auth-mysql - Apache module for MySQL authentication libapache2-mod-auth-mysql - Apache 2 module for MySQL authentication Closes: 267354 Changes: libapache-mod-auth-mysql (4.3.5) unstable; urgency=high . * High urgency on the request of Adam Conrad to try and get Apache2 through for Sarge. * Rebuild to back out the ill-fated apache2 LFS transition (so much for comprehensive testing...) Closes: #267354. * Bumped the apache2-*-dev build-dep and apache2 dep to = 2.0.50-10. Files: a0f99687262f04392da266f7390e07bd 637 web optional libapache-mod-auth-mysql_4.3.5.dsc 688c555ad53fc84b2fc54c8bfc721e8a 54043 web optional libapache-mod-auth-mysql_4.3.5.tar.gz c516c165e6c46757b7adc7d0605239be 20454 web optional libapache-mod-auth-mysql_4.3.5_i386.deb 4f7f095061763ec2d48baccd06cdff73 20828 web optional libapache2-mod-auth-mysql_4.3.5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBKUASBEnrTWk1E4cRAm24AJ9gCyJk3GwKr2GnKji+U4unAFFOnwCfQ9lb nAgQr5OLWQAa1IGRg5hI+zo= =J1Lz -END PGP SIGNATURE- Accepted: libapache-mod-auth-mysql_4.3.5.dsc to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.5.dsc libapache-mod-auth-mysql_4.3.5.tar.gz to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.5.tar.gz libapache-mod-auth-mysql_4.3.5_i386.deb to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.5_i386.deb libapache2-mod-auth-mysql_4.3.5_i386.deb to pool/main/liba/libapache-mod-auth-mysql/libapache2-mod-auth-mysql_4.3.5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libapache-mod-auth-mysql 4.3.4 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 17 Aug 2004 10:01:34 +1000 Source: libapache-mod-auth-mysql Binary: libapache-mod-auth-mysql libapache2-mod-auth-mysql Architecture: source i386 Version: 4.3.4 Distribution: unstable Urgency: medium Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: libapache-mod-auth-mysql - Apache module for MySQL authentication libapache2-mod-auth-mysql - Apache 2 module for MySQL authentication Closes: 266177 Changes: libapache-mod-auth-mysql (4.3.4) unstable; urgency=medium . * Rebuild to support new Apache2 ABI. Closes: #266177. Files: 0e7619f409efdc98b5adee00d2e82fa9 636 web optional libapache-mod-auth-mysql_4.3.4.dsc 078886c1b350146bdcb4457c15fdcae7 54727 web optional libapache-mod-auth-mysql_4.3.4.tar.gz befef24a09b3e4d5923dab58736cefc2 20286 web optional libapache-mod-auth-mysql_4.3.4_i386.deb 1e2d4432848a5e8d4f2f9604f80f1d20 20640 web optional libapache2-mod-auth-mysql_4.3.4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBIVglBEnrTWk1E4cRAgv1AJ4zO+0RYpo8tufJnLWYLofz4j+UdQCfQwip T3cxluLz7CguM2g2rC6oZTo= =WhbD -END PGP SIGNATURE- Accepted: libapache-mod-auth-mysql_4.3.4.dsc to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.4.dsc libapache-mod-auth-mysql_4.3.4.tar.gz to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.4.tar.gz libapache-mod-auth-mysql_4.3.4_i386.deb to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.4_i386.deb libapache2-mod-auth-mysql_4.3.4_i386.deb to pool/main/liba/libapache-mod-auth-mysql/libapache2-mod-auth-mysql_4.3.4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fbpanel 3.8-4 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 13 Aug 2004 19:36:38 +1000 Source: fbpanel Binary: fbpanel Architecture: source i386 Version: 3.8-4 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: fbpanel- A lightweight X11 desktop panel Closes: 264881 Changes: fbpanel (3.8-4) unstable; urgency=low . * Changed the XTerm tool item to run x-terminal-emulator, and the Emacs button to run x-www-browser instead. Closes: #264881. Files: 2f2c677c8c5ae685c61b5d5096a8c4a6 599 x11 optional fbpanel_3.8-4.dsc 79f667d7d9a474dfa0d00049e7374464 6255 x11 optional fbpanel_3.8-4.diff.gz b602ecd5f4704ea1de9c5bb3ad15ec7d 64562 x11 optional fbpanel_3.8-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBHJAgBEnrTWk1E4cRAh0OAKCYDQ8hImnQxL0lmI6TfmIyO2heNACZAbeO /yop1LJlBblYpt1YrU4IH/Q= =MqY7 -END PGP SIGNATURE- Accepted: fbpanel_3.8-4.diff.gz to pool/main/f/fbpanel/fbpanel_3.8-4.diff.gz fbpanel_3.8-4.dsc to pool/main/f/fbpanel/fbpanel_3.8-4.dsc fbpanel_3.8-4_i386.deb to pool/main/f/fbpanel/fbpanel_3.8-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fbpanel 3.8-5 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 14 Aug 2004 13:49:59 +1000 Source: fbpanel Binary: fbpanel Architecture: source i386 Version: 3.8-5 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: fbpanel- A lightweight X11 desktop panel Changes: fbpanel (3.8-5) unstable; urgency=low . * Fixed up another instance of explicit binary names in the default config file. Files: 570060594b306dbe04c790440395df9c 599 x11 optional fbpanel_3.8-5.dsc 0cfe1051ad38f8c3b29802998b2fd54f 6314 x11 optional fbpanel_3.8-5.diff.gz cc27ca395259434dbce11c7350d0371a 64612 x11 optional fbpanel_3.8-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBHY3lBEnrTWk1E4cRAmPzAJsHMYU+FLNNBxnSnjTPU6xlKNxZkACeOlLS V0oenmjAWfIE1elnx+3/SZU= =phSO -END PGP SIGNATURE- Accepted: fbpanel_3.8-5.diff.gz to pool/main/f/fbpanel/fbpanel_3.8-5.diff.gz fbpanel_3.8-5.dsc to pool/main/f/fbpanel/fbpanel_3.8-5.dsc fbpanel_3.8-5_i386.deb to pool/main/f/fbpanel/fbpanel_3.8-5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libapache-mod-auth-mysql 4.3.3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 13 Aug 2004 00:23:02 +1000 Source: libapache-mod-auth-mysql Binary: libapache-mod-auth-mysql libapache2-mod-auth-mysql Architecture: source i386 Version: 4.3.3 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: libapache-mod-auth-mysql - Apache module for MySQL authentication libapache2-mod-auth-mysql - Apache 2 module for MySQL authentication Closes: 257879 Changes: libapache-mod-auth-mysql (4.3.3) unstable; urgency=low . * Really fixed the multi-group checking. Seems I put the you're not invited return at the wrong scope. Where's my dwim() function, dammit. Closes: #257879 (I promise). Files: c714482105cc75e15f2793d46ecc928c 622 web optional libapache-mod-auth-mysql_4.3.3.dsc fb5a03ef8a6fed88e9aaf7a21a52a1a0 53828 web optional libapache-mod-auth-mysql_4.3.3.tar.gz 9f31379a5d3e6a0ded7690ea2cf8c449 20242 web optional libapache-mod-auth-mysql_4.3.3_i386.deb 08b8e224ca51a6b8c3edcfee77db5cb9 20604 web optional libapache2-mod-auth-mysql_4.3.3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBG4IPBEnrTWk1E4cRAmguAJwP3YpvKR1RKsyCXUSbzMF8oDm0fQCgnDgq UPWHgc/fX7fb0UkMGgPET34= =8z9z -END PGP SIGNATURE- Accepted: libapache-mod-auth-mysql_4.3.3.dsc to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.3.dsc libapache-mod-auth-mysql_4.3.3.tar.gz to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.3.tar.gz libapache-mod-auth-mysql_4.3.3_i386.deb to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.3_i386.deb libapache2-mod-auth-mysql_4.3.3_i386.deb to pool/main/liba/libapache-mod-auth-mysql/libapache2-mod-auth-mysql_4.3.3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libapache-mod-auth-mysql 4.3.2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 6 Aug 2004 20:19:43 +1000 Source: libapache-mod-auth-mysql Binary: libapache-mod-auth-mysql libapache2-mod-auth-mysql Architecture: source i386 Version: 4.3.2 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: libapache-mod-auth-mysql - Apache module for MySQL authentication libapache2-mod-auth-mysql - Apache 2 module for MySQL authentication Closes: 257879 258030 Changes: libapache-mod-auth-mysql (4.3.2) unstable; urgency=low . * Fixed multi-group checking; if multiple groups are listed in the 'require group' directive, the code only checked for the first one. Thanks to Karsten Richter for finding the bug and fixing it. Closes: #257879. * Cleaned up a define and associated bits to allow compilation under gcc-2.95. And we didn't even need a versioned build-depends. Closes: #258030. Files: 0884b25f9a80c55231aa03ad34e58527 622 web optional libapache-mod-auth-mysql_4.3.2.dsc 1f3090b9317cebfe8782f3ae8bb899d3 53712 web optional libapache-mod-auth-mysql_4.3.2.tar.gz 780147306059a60c7d28304622dc80a7 20164 web optional libapache-mod-auth-mysql_4.3.2_i386.deb 9e73451d1987ffd100a7eac0925400a9 20536 web optional libapache2-mod-auth-mysql_4.3.2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBGchMBEnrTWk1E4cRApgfAJ4779NWWAz+6u8GxZ9fVmjWg0KU5gCfRGRZ 2fPRVSAZZvR8dclRsU3d99A= =aApm -END PGP SIGNATURE- Accepted: libapache-mod-auth-mysql_4.3.2.dsc to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.2.dsc libapache-mod-auth-mysql_4.3.2.tar.gz to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.2.tar.gz libapache-mod-auth-mysql_4.3.2_i386.deb to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.2_i386.deb libapache2-mod-auth-mysql_4.3.2_i386.deb to pool/main/liba/libapache-mod-auth-mysql/libapache2-mod-auth-mysql_4.3.2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cyrus-imapd 1.5.19-19 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 7 Aug 2004 22:53:07 +1000 Source: cyrus-imapd Binary: cyrus-imapd cyrus-common cyrus-pop3d cyrus-dev cyrus-admin cyrus-news-spool Architecture: source i386 Version: 1.5.19-19 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: cyrus-admin - CMU Cyrus mail system (administration tool) cyrus-common - CMU Cyrus mail system (common files) cyrus-dev - CMU Cyrus mail system (developer files) cyrus-imapd - CMU Cyrus mail system (IMAP support) cyrus-news-spool - CMU Cyrus mail system (News spool support) cyrus-pop3d - CMU Cyrus mail system (POP3 support) Closes: 264127 Changes: cyrus-imapd (1.5.19-19) unstable; urgency=low . * Removed an empty switch default: to get a clean build on GCC 3.4. Closes: #264127. Files: e99fa95d3cd0f815b4b257962d69450f 703 mail extra cyrus-imapd_1.5.19-19.dsc 5ca63222b6050872a70106897795faf0 36337 mail extra cyrus-imapd_1.5.19-19.diff.gz f3a03eecbe9fb93a109e24a1375ed79a 393768 mail extra cyrus-common_1.5.19-19_i386.deb 3ff74822bcaa6de5e82354cfee71a7af 129780 mail extra cyrus-imapd_1.5.19-19_i386.deb 78dffb214aa981a9e62bd8d2fdd9b90d 62166 mail extra cyrus-pop3d_1.5.19-19_i386.deb 63098499a9cf532de5e1fc594149a2ab 16148 mail extra cyrus-news-spool_1.5.19-19_i386.deb 611b15ac4f24e8f163ad1f9f86320268 42400 mail extra cyrus-admin_1.5.19-19_i386.deb ac00eff3310d837b504e20ac36cb1034 79480 devel extra cyrus-dev_1.5.19-19_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBFNKFBEnrTWk1E4cRAiS4AJ9y+9M0w3qY/CDRWTVIpMSc3PpWKgCdGFw0 CdUqANO9alJ47iVPSXHWsvM= =zh9p -END PGP SIGNATURE- Accepted: cyrus-admin_1.5.19-19_i386.deb to pool/main/c/cyrus-imapd/cyrus-admin_1.5.19-19_i386.deb cyrus-common_1.5.19-19_i386.deb to pool/main/c/cyrus-imapd/cyrus-common_1.5.19-19_i386.deb cyrus-dev_1.5.19-19_i386.deb to pool/main/c/cyrus-imapd/cyrus-dev_1.5.19-19_i386.deb cyrus-imapd_1.5.19-19.diff.gz to pool/main/c/cyrus-imapd/cyrus-imapd_1.5.19-19.diff.gz cyrus-imapd_1.5.19-19.dsc to pool/main/c/cyrus-imapd/cyrus-imapd_1.5.19-19.dsc cyrus-imapd_1.5.19-19_i386.deb to pool/main/c/cyrus-imapd/cyrus-imapd_1.5.19-19_i386.deb cyrus-news-spool_1.5.19-19_i386.deb to pool/main/c/cyrus-imapd/cyrus-news-spool_1.5.19-19_i386.deb cyrus-pop3d_1.5.19-19_i386.deb to pool/main/c/cyrus-imapd/cyrus-pop3d_1.5.19-19_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted irm 1.4.3-2 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 6 Aug 2004 16:34:06 +1000 Source: irm Binary: irm Architecture: source all Version: 1.4.3-2 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: irm- Web-based asset tracking system for IT departments and help desks Closes: 258727 263506 Changes: irm (1.4.3-2) unstable; urgency=low . * Improved install_package.dpatch to actually display the existing install package, and remove irm.inc.orig from the patch (how did that get in there?) * Added a new displaykey.dpatch, to show the licence key for the software next to the record of it being installed. * Added French Debconf translation, thanks to Jean-Luc Coulon. Closes: #258727. * Added German Debconf translation, thanks to Erik Schanze. Closes: #263506. Files: 7d81a9c63f90f98372c7ce80ac84dba4 563 web optional irm_1.4.3-2.dsc b6993a08943a7f643790ada2a53827ee 19163 web optional irm_1.4.3-2.diff.gz 52958ccb334d0629a68413136b5f988b 130756 web optional irm_1.4.3-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBEy/1BEnrTWk1E4cRArLjAJ4vV58VC6x72aUU2RelGgrlrq2tWwCgjdmZ F6JeReg1XRsJhjvpxZf8x04= =CswB -END PGP SIGNATURE- Accepted: irm_1.4.3-2.diff.gz to pool/main/i/irm/irm_1.4.3-2.diff.gz irm_1.4.3-2.dsc to pool/main/i/irm/irm_1.4.3-2.dsc irm_1.4.3-2_all.deb to pool/main/i/irm/irm_1.4.3-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cyrus-imapd 1.5.19-18 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 6 Aug 2004 18:09:38 +1000 Source: cyrus-imapd Binary: cyrus-imapd cyrus-common cyrus-pop3d cyrus-dev cyrus-admin cyrus-news-spool Architecture: source i386 Version: 1.5.19-18 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: cyrus-admin - CMU Cyrus mail system (administration tool) cyrus-common - CMU Cyrus mail system (common files) cyrus-dev - CMU Cyrus mail system (developer files) cyrus-imapd - CMU Cyrus mail system (IMAP support) cyrus-news-spool - CMU Cyrus mail system (News spool support) cyrus-pop3d - CMU Cyrus mail system (POP3 support) Closes: 257648 Changes: cyrus-imapd (1.5.19-18) unstable; urgency=low . * Updated package descriptions to note that this is an older version and people should look elsewhere for their shiny! new! IMAP service needs. Closes: #257648. * Changes to comply with version 3.6.1 of Policy -- removed prompting from cyrus-common's maintainer scripts. We now hope that the admin will read README.Debian, and understands that purge == purge. * Added an override for CVS directories in the source, since they're never going to be removed. Files: 675b752531e1b42b36cd3d873f35aab2 703 mail extra cyrus-imapd_1.5.19-18.dsc 6b93accdfe2bb0e26d852c59eb88eb05 36208 mail extra cyrus-imapd_1.5.19-18.diff.gz 2aea0ceb8a62fd42f426f727f782be65 393712 mail extra cyrus-common_1.5.19-18_i386.deb 49afb67a4dd254374f00d328bf6d37bf 129722 mail extra cyrus-imapd_1.5.19-18_i386.deb f4bb7cd46733ca3a08db2dee3fba229f 62108 mail extra cyrus-pop3d_1.5.19-18_i386.deb 9340ff3f4db5c334bab0a9757e5e9aa3 16094 mail extra cyrus-news-spool_1.5.19-18_i386.deb 53355c664af6feb7fba8fb3593631509 42342 mail extra cyrus-admin_1.5.19-18_i386.deb 90c2d8935ab6ff48fbb9866d38bcb2fe 79424 devel extra cyrus-dev_1.5.19-18_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBE0D4BEnrTWk1E4cRAksaAJ0WTdA4BnZlDbUCZU7ZwkiYBiwu9gCfeuQq ZsovfuxUZZxtGXmBy4zIY3U= =o0nK -END PGP SIGNATURE- Accepted: cyrus-admin_1.5.19-18_i386.deb to pool/main/c/cyrus-imapd/cyrus-admin_1.5.19-18_i386.deb cyrus-common_1.5.19-18_i386.deb to pool/main/c/cyrus-imapd/cyrus-common_1.5.19-18_i386.deb cyrus-dev_1.5.19-18_i386.deb to pool/main/c/cyrus-imapd/cyrus-dev_1.5.19-18_i386.deb cyrus-imapd_1.5.19-18.diff.gz to pool/main/c/cyrus-imapd/cyrus-imapd_1.5.19-18.diff.gz cyrus-imapd_1.5.19-18.dsc to pool/main/c/cyrus-imapd/cyrus-imapd_1.5.19-18.dsc cyrus-imapd_1.5.19-18_i386.deb to pool/main/c/cyrus-imapd/cyrus-imapd_1.5.19-18_i386.deb cyrus-news-spool_1.5.19-18_i386.deb to pool/main/c/cyrus-imapd/cyrus-news-spool_1.5.19-18_i386.deb cyrus-pop3d_1.5.19-18_i386.deb to pool/main/c/cyrus-imapd/cyrus-pop3d_1.5.19-18_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fbpanel 3.8-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 6 Aug 2004 18:48:22 +1000 Source: fbpanel Binary: fbpanel Architecture: source i386 Version: 3.8-2 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: fbpanel- A lightweight X11 desktop panel Closes: 263465 Changes: fbpanel (3.8-2) unstable; urgency=low . * Fixed up the menu-method file so it builds it's menus in the right places. Closes: #263465. Files: 6ec801d708160857024e179e541196ff 599 x11 optional fbpanel_3.8-2.dsc e4a6396b89465db2718573814333a79a 6048 x11 optional fbpanel_3.8-2.diff.gz 9710b3c52dc7fc2eb099815c348776eb 64368 x11 optional fbpanel_3.8-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBE0tDBEnrTWk1E4cRAkOJAJ4vNi9LqOIOvzKiNXbznDtv+nWVJACeMfq1 1heWLczErjN5GyLm077P/1s= =IxwP -END PGP SIGNATURE- Accepted: fbpanel_3.8-2.diff.gz to pool/main/f/fbpanel/fbpanel_3.8-2.diff.gz fbpanel_3.8-2.dsc to pool/main/f/fbpanel/fbpanel_3.8-2.dsc fbpanel_3.8-2_i386.deb to pool/main/f/fbpanel/fbpanel_3.8-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fbpanel 3.8-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 7 Aug 2004 09:52:56 +1000 Source: fbpanel Binary: fbpanel Architecture: source i386 Version: 3.8-3 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: fbpanel- A lightweight X11 desktop panel Closes: 263944 Changes: fbpanel (3.8-3) unstable; urgency=low . * Added outputencoding=UTF-8 so that accented characters appear right in the generated menus. Closes: #263944. Files: b93e26e4fbe5a8d41144e4061c3d3efc 599 x11 optional fbpanel_3.8-3.dsc 393d822889603d9fd8d85fea35609bf2 6125 x11 optional fbpanel_3.8-3.diff.gz 0d342fa29f9675fad27b98a58a749f9f 64454 x11 optional fbpanel_3.8-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBFBsSBEnrTWk1E4cRArNyAJ9y12MwYVV9gWqMcKScQJc+EnBNrQCfRi8m mWcJ3Q/+nFkAUhuGrEqfFoE= =J3Kl -END PGP SIGNATURE- Accepted: fbpanel_3.8-3.diff.gz to pool/main/f/fbpanel/fbpanel_3.8-3.diff.gz fbpanel_3.8-3.dsc to pool/main/f/fbpanel/fbpanel_3.8-3.dsc fbpanel_3.8-3_i386.deb to pool/main/f/fbpanel/fbpanel_3.8-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted phpwiki 1.3.7-3 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 30 Jun 2004 21:25:29 +1000 Source: phpwiki Binary: phpwiki Architecture: source all Version: 1.3.7-3 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: phpwiki- An informal collaborative website manager Closes: 227953 245586 245812 249772 256813 Changes: phpwiki (1.3.7-3) unstable; urgency=low . * Added more guards to the postinst to ensure we don't invoke an apache's init script unless it's rooly trooly there. Closes: #249772, #245586. * Renamed the 'RecentChanges' page in the german translation from FricheSeiten to NeuesteÄnderungen. Closes: #245812. * Cherry-picked pgsrc/TestFormattingRules#1.32 from upstream CVS, documenting the proper use of tilde in polite Wikiing. Closes: #227953. * Bumped php4-sqlite and sqlite to Required: because it effectively does (legacy dba systems notwithstanding). Closes: #256813. Files: 26c0c18e3058b9fbf5ac5575334fca70 580 web optional phpwiki_1.3.7-3.dsc 95bd6c03e08f9e9c8e724bfb17b5742a 26873 web optional phpwiki_1.3.7-3.diff.gz faa3e333ff66a148827544a67b07f79a 1268372 web optional phpwiki_1.3.7-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFA4ql+BEnrTWk1E4cRAl1/AJ9iga1boWHMQ+eAU7NE+UXU6USXTgCfd/zB cpaLyFV661nwEo0gKlyTSgA= =wuMT -END PGP SIGNATURE- Accepted: phpwiki_1.3.7-3.diff.gz to pool/main/p/phpwiki/phpwiki_1.3.7-3.diff.gz phpwiki_1.3.7-3.dsc to pool/main/p/phpwiki/phpwiki_1.3.7-3.dsc phpwiki_1.3.7-3_all.deb to pool/main/p/phpwiki/phpwiki_1.3.7-3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libapache-mod-auth-mysql 4.3.1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 27 Jun 2004 21:34:59 +1000 Source: libapache-mod-auth-mysql Binary: libapache-mod-auth-mysql libapache2-mod-auth-mysql Architecture: source i386 Version: 4.3.1 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: libapache-mod-auth-mysql - Apache module for MySQL authentication libapache2-mod-auth-mysql - Apache 2 module for MySQL authentication Closes: 255985 Changes: libapache-mod-auth-mysql (4.3.1) unstable; urgency=low . * Determined that safe_mysql_query() wasn't retrying on some retryable errors, and fixed it up so that it retries once if the server wandered off before we started. Closes: #255985. Files: e43da95a1f4cd8e36a34d44674088e5d 622 web optional libapache-mod-auth-mysql_4.3.1.dsc 00f10f670f89db3b5ac60bc4720bbeb7 56247 web optional libapache-mod-auth-mysql_4.3.1.tar.gz 613d9408d7dda976dec9c8acc218587b 19990 web optional libapache-mod-auth-mysql_4.3.1_i386.deb 456bf8a1a62448acb39ca88920a3af37 20378 web optional libapache2-mod-auth-mysql_4.3.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFA3rtXBEnrTWk1E4cRAlaPAKCj0NAiZgU1PiMXwE4IZmGo6cakawCgsY0z AN0pXA4PRqpZn13zkOjwHsI= =kD60 -END PGP SIGNATURE- Accepted: libapache-mod-auth-mysql_4.3.1.dsc to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.1.dsc libapache-mod-auth-mysql_4.3.1.tar.gz to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.1.tar.gz libapache-mod-auth-mysql_4.3.1_i386.deb to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.1_i386.deb libapache2-mod-auth-mysql_4.3.1_i386.deb to pool/main/liba/libapache-mod-auth-mysql/libapache2-mod-auth-mysql_4.3.1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fbpanel 3.8-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Jun 2004 22:01:53 +1000 Source: fbpanel Binary: fbpanel Architecture: source i386 Version: 3.8-1 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: fbpanel- A lightweight X11 desktop panel Closes: 252825 255412 Changes: fbpanel (3.8-1) unstable; urgency=low . * New upstream release. Closes: #252825. * Modified default config to not reference any image files in $HOME. Closes: #255412. * Removed the examples, because they're duplicated by the default config file and images in /usr/share/fbpanel/images. Files: c4721acefa66d0917100b494ff928a1e 599 x11 optional fbpanel_3.8-1.dsc 95e43a2c201feb5e272bbd9a4f78ad6e 72121 x11 optional fbpanel_3.8.orig.tar.gz 6142460aaa51600a22c6eaebd2affdd7 5986 x11 optional fbpanel_3.8-1.diff.gz bc238fc21846243cb030f2e641a8389f 64768 x11 optional fbpanel_3.8-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFA3B7qBEnrTWk1E4cRAszIAJ4pyAmrJmF5tLbf4y3g86liS4RaMgCfdSDk Fxk9STzmqSQlR377jjjuLws= =8+CH -END PGP SIGNATURE- Accepted: fbpanel_3.8-1.diff.gz to pool/main/f/fbpanel/fbpanel_3.8-1.diff.gz fbpanel_3.8-1.dsc to pool/main/f/fbpanel/fbpanel_3.8-1.dsc fbpanel_3.8-1_i386.deb to pool/main/f/fbpanel/fbpanel_3.8-1_i386.deb fbpanel_3.8.orig.tar.gz to pool/main/f/fbpanel/fbpanel_3.8.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted irm 1.4.3-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 22 Jun 2004 22:55:02 +1000 Source: irm Binary: irm Architecture: source all Version: 1.4.3-1 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: irm- Web-based asset tracking system for IT departments and help desks Closes: 221640 235169 244609 Changes: irm (1.4.3-1) unstable; urgency=low . * New upstream version. Closes: #244609. * We now use ucf instead of our homebrand config file check. Closes: #221640. * Apply a patch from Martin Quinson to convert to po-debconf. Closes: #235169. * Added a quick patch to save details of an 'install package' name for software items. Consider it an identifier for different software programs -- mostly useful for automated installations. * Renamed the db_name variable to db_host (because it's a hostname). * Changed the WWW directory back to the right thing. * Added a watch file. Files: 8be88ea280cfae85aa3c4b4ebdf6cd21 563 web optional irm_1.4.3-1.dsc 77cc4c414c480046e628ffd0660c0a18 134929 web optional irm_1.4.3.orig.tar.gz df90e6797772941895283c1d64d7b63e 36321 web optional irm_1.4.3-1.diff.gz 5fa50eb3f8a0d55005bb1ad7b748ec06 129272 web optional irm_1.4.3-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFA2X/oBEnrTWk1E4cRAgEJAJ9hCn4rYeC8PrB03vQdn3pbZms1OgCfXWyf b7yu6XBifPmssFuv6psD25s= =Lwzw -END PGP SIGNATURE- Accepted: irm_1.4.3-1.diff.gz to pool/main/i/irm/irm_1.4.3-1.diff.gz irm_1.4.3-1.dsc to pool/main/i/irm/irm_1.4.3-1.dsc irm_1.4.3-1_all.deb to pool/main/i/irm/irm_1.4.3-1_all.deb irm_1.4.3.orig.tar.gz to pool/main/i/irm/irm_1.4.3.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted php4-sqlite 1.0.2-5 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 16 Jun 2004 18:09:44 +1000 Source: php4-sqlite Binary: php4-sqlite Architecture: source i386 Version: 1.0.2-5 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: php4-sqlite - PHP4 bindings to SQLite, a file-based SQL engine Closes: 254508 Changes: php4-sqlite (1.0.2-5) unstable; urgency=low . * We now use restart instead of force-reload to kick apache in the nuts. This is fucking stupid, because if the service isn't running I don't think it should be started, but in the absence of an init.d option to restart-if-running-but-not-otherwise, I'll stick with this. Closes: #254508. Files: f345c66dbdd94f6a7dd309886b65eb84 600 web optional php4-sqlite_1.0.2-5.dsc f1d46d13e998a142953a767fc8c59585 6896 web optional php4-sqlite_1.0.2-5.diff.gz f7c01257f0fec6126c787f6fee10d243 19364 web optional php4-sqlite_1.0.2-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFA0AM2BEnrTWk1E4cRAslYAKCVlOufM3jF2k28/yFBD5jRw4oNWQCffPBY OWzPElDtZ5XMsdg8yy+ExpY= =xiFR -END PGP SIGNATURE- Accepted: php4-sqlite_1.0.2-5.diff.gz to pool/main/p/php4-sqlite/php4-sqlite_1.0.2-5.diff.gz php4-sqlite_1.0.2-5.dsc to pool/main/p/php4-sqlite/php4-sqlite_1.0.2-5.dsc php4-sqlite_1.0.2-5_i386.deb to pool/main/p/php4-sqlite/php4-sqlite_1.0.2-5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libapache-mod-auth-mysql 4.3.0 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 16 Jun 2004 17:39:10 +1000 Source: libapache-mod-auth-mysql Binary: libapache-mod-auth-mysql libapache2-mod-auth-mysql Architecture: source i386 Version: 4.3.0 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: libapache-mod-auth-mysql - Apache module for MySQL authentication libapache2-mod-auth-mysql - Apache 2 module for MySQL authentication Closes: 251704 Changes: libapache-mod-auth-mysql (4.3.0) unstable; urgency=low . * Two new directives, Auth_MySQL_DefaultPort and Auth_MySQL_DefaultSocket. * Related to the above, the specification of port or socket as part of the hostname is no longer permitted. Hopefully nobody got too attached to that, as it wasn't documented as such anyway. * Straightened out various bits of twisty code. * Removed the crazy host/port/socket parsing code which (I believe) was causing all the screwed up hostname grief. Closes: #251704. Files: 7e811b4e7897827393f52b04d25ca91b 622 web optional libapache-mod-auth-mysql_4.3.0.dsc e5f1fd8261b699f2f2a337ceb94777b4 55447 web optional libapache-mod-auth-mysql_4.3.0.tar.gz f693cc139079244f6ec7eb40e816d5ca 19658 web optional libapache-mod-auth-mysql_4.3.0_i386.deb 09aa797316e9b429605d6f9b44137dfe 20046 web optional libapache2-mod-auth-mysql_4.3.0_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAz//wBEnrTWk1E4cRAsUiAKCGKilHtg8j/fhcpshAURbjWarzsQCcDOOK Wzilvjx9ZIl8dkcq94V5pr0= =JtLx -END PGP SIGNATURE- Accepted: libapache-mod-auth-mysql_4.3.0.dsc to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.0.dsc libapache-mod-auth-mysql_4.3.0.tar.gz to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.0.tar.gz libapache-mod-auth-mysql_4.3.0_i386.deb to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.3.0_i386.deb libapache2-mod-auth-mysql_4.3.0_i386.deb to pool/main/liba/libapache-mod-auth-mysql/libapache2-mod-auth-mysql_4.3.0_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted php4-sqlite 1.0.2-4 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 8 Jun 2004 20:27:05 +1000 Source: php4-sqlite Binary: php4-sqlite Architecture: source i386 Version: 1.0.2-4 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: php4-sqlite - PHP4 bindings to SQLite, a file-based SQL engine Changes: php4-sqlite (1.0.2-4) unstable; urgency=low . * Fiddled dh_pecl's prerm template so it actually works. Thanks to Fabio Massimo Di Nitto for not laughing at me too hard. Files: b67d991114452b078e3c8c388c349165 600 web optional php4-sqlite_1.0.2-4.dsc b4c8b14d3b3fda66b84dc06bcd3d92f8 6736 web optional php4-sqlite_1.0.2-4.diff.gz e02221732ac06ee7f6c2d68b466f5f49 19172 web optional php4-sqlite_1.0.2-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAxagIBEnrTWk1E4cRAmALAKComNSQHkb71RzshyiMkWym3LVHQwCcD0VF V+wKbhd2B4TSHVo9MIYnMvw= =Jqe2 -END PGP SIGNATURE- Accepted: php4-sqlite_1.0.2-4.diff.gz to pool/main/p/php4-sqlite/php4-sqlite_1.0.2-4.diff.gz php4-sqlite_1.0.2-4.dsc to pool/main/p/php4-sqlite/php4-sqlite_1.0.2-4.dsc php4-sqlite_1.0.2-4_i386.deb to pool/main/p/php4-sqlite/php4-sqlite_1.0.2-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libapache-mod-auth-mysql 4.2.0 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 11 May 2004 15:09:07 +1000 Source: libapache-mod-auth-mysql Binary: libapache-mod-auth-mysql libapache2-mod-auth-mysql Architecture: source i386 Version: 4.2.0 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: libapache-mod-auth-mysql - Apache module for MySQL authentication libapache2-mod-auth-mysql - Apache 2 module for MySQL authentication Closes: 231667 243995 248415 Changes: libapache-mod-auth-mysql (4.2.0) unstable; urgency=low . * Applied a patch from Takeshi Murakami to add Apache 2 support and the ability to specify a port number or socket file (for those times you just gotta do it). Closes: #231667. Many thanks to Takeshi for taking the time to do the Apache2 conversion (which appears to have been a fair bit of work). - Updated DIRECTIVES for the new port/socket specifiers. - Added new --with-apache and --with-apache2 ./configure options to enable/disable build support for both modules. - New binary package, libapache2-mod-auth-mysql, to provide the apache2-compiled version of m-a-m. Closes: #248415. Also updated build-deps and all that sort of thing. Small parts shamelessly stolen from libapache2-mod-auth-pgsql. * Bumped standards version; no changes needed. * Reversed the sense of the persistent check on connection close; the program now behaves like it's documentation. Closes: #243995. Files: d0b75ae83e5c931ed2841e8f9e1ca266 622 web optional libapache-mod-auth-mysql_4.2.0.dsc 30aacbfbdab2c0f238f34b6980f5ad46 54988 web optional libapache-mod-auth-mysql_4.2.0.tar.gz 891ff1f04a3f7057cce91f33a10463e7 19096 web optional libapache-mod-auth-mysql_4.2.0_i386.deb 74db445bfcda8b79d2251bb18f759f0b 19346 web optional libapache2-mod-auth-mysql_4.2.0_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAoGdFBEnrTWk1E4cRAjkxAJ9cfXJScpy9JYkDE82snAOgmKuqbgCeN5pb u4cFl5PJ5xM0Kbqo6GWeoU4= =vcZl -END PGP SIGNATURE- Accepted: libapache-mod-auth-mysql_4.2.0.dsc to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.2.0.dsc libapache-mod-auth-mysql_4.2.0.tar.gz to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.2.0.tar.gz libapache-mod-auth-mysql_4.2.0_i386.deb to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.2.0_i386.deb libapache2-mod-auth-mysql_4.2.0_i386.deb to pool/main/liba/libapache-mod-auth-mysql/libapache2-mod-auth-mysql_4.2.0_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fbpanel 3.7-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 24 May 2004 18:44:55 +1000 Source: fbpanel Binary: fbpanel Architecture: source i386 Version: 3.7-3 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: fbpanel- A lightweight X11 desktop panel Closes: 249169 250562 Changes: fbpanel (3.7-3) unstable; urgency=low . * Applied a great patch from Vincenzo Demasi [EMAIL PROTECTED]: - Added Debian menu support. - Added a new 'include' stanza for fbpanel config files, which is used by the Debian menu support. Thanks to Vincenzo for putting it all together. Closes: #249169. * Applied a patch from Shyamal Prasad [EMAIL PROTECTED]: - Modified fbpanel.1 and panel.c for configs in /etc/fbpanel - Placed a default config file in /etc/fbpanel/default, in case there there is no user-specific one. Thanks to Shyamal for spending the time on this issue. Closes: #250562. This patch is extra-wonderful considering Vincenzo's, because we've now got a complete, no-user-intervention-required panel. Files: 348649bf90e5c7779b01f63de3b84130 599 x11 optional fbpanel_3.7-3.dsc d55ebbb277e527c33288c15725ccde73 5696 x11 optional fbpanel_3.7-3.diff.gz 030d6ebe913370f443e297696af07eaa 84856 x11 optional fbpanel_3.7-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAsb0lBEnrTWk1E4cRAlE2AKCTv/SiIxrbikSQ1ZhnQuemxl1lkQCgo/5s bZDNbbQaBFnmBNQX9AcEa9I= =wnAB -END PGP SIGNATURE- Accepted: fbpanel_3.7-3.diff.gz to pool/main/f/fbpanel/fbpanel_3.7-3.diff.gz fbpanel_3.7-3.dsc to pool/main/f/fbpanel/fbpanel_3.7-3.dsc fbpanel_3.7-3_i386.deb to pool/main/f/fbpanel/fbpanel_3.7-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fbpanel 3.7-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 11 May 2004 20:27:19 +1000 Source: fbpanel Binary: fbpanel Architecture: source i386 Version: 3.7-2 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: fbpanel- A lightweight X11 desktop panel Closes: 248452 Changes: fbpanel (3.7-2) unstable; urgency=low . * We now copy the default images into their proper location. Closes: #248452. Files: 14fecc275c345ec2686f46727502d1ce 591 x11 optional fbpanel_3.7-2.dsc 25f4920373099473ccf89ca2a3ae4051 2290 x11 optional fbpanel_3.7-2.diff.gz a73fdb6b704f19655907b544a5a06cde 81882 x11 optional fbpanel_3.7-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAoLZOBEnrTWk1E4cRAv4mAKCay38hpRfvy1JwiHgsA+dvnN1tEgCbBQsX tHBa66i447m0SYXrPZ+DkWo= =7O9g -END PGP SIGNATURE- Accepted: fbpanel_3.7-2.diff.gz to pool/main/f/fbpanel/fbpanel_3.7-2.diff.gz fbpanel_3.7-2.dsc to pool/main/f/fbpanel/fbpanel_3.7-2.dsc fbpanel_3.7-2_i386.deb to pool/main/f/fbpanel/fbpanel_3.7-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fbpanel 3.7-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 10 May 2004 17:32:27 +1000 Source: fbpanel Binary: fbpanel Architecture: source i386 Version: 3.7-1 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: fbpanel- A lightweight X11 desktop panel Closes: 247625 Changes: fbpanel (3.7-1) unstable; urgency=low . * New upstream version. Closes: #247625. Files: 8ac73a651037ea8993dac634949d 567 x11 optional fbpanel_3.7-1.dsc a0da1489ce17df17251ade3263544a00 69581 x11 optional fbpanel_3.7.orig.tar.gz ab00b8d2278a8bf0afcae7a28c7e7436 2195 x11 optional fbpanel_3.7-1.diff.gz aac1dd469b83541a3c493663219bb1cc 64386 x11 optional fbpanel_3.7-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAn2O4BEnrTWk1E4cRAj74AJ9dAJKDiEVXasaDhlM+GnLDyzuRMgCcC2QD 0x0YD297XFkVrrmBvtS7Fd4= =Sjh4 -END PGP SIGNATURE- Accepted: fbpanel_3.7-1.diff.gz to pool/main/f/fbpanel/fbpanel_3.7-1.diff.gz fbpanel_3.7-1.dsc to pool/main/f/fbpanel/fbpanel_3.7-1.dsc fbpanel_3.7-1_i386.deb to pool/main/f/fbpanel/fbpanel_3.7-1_i386.deb fbpanel_3.7.orig.tar.gz to pool/main/f/fbpanel/fbpanel_3.7.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted phpwiki 1.3.7-2 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 20 Apr 2004 21:27:31 +1000 Source: phpwiki Binary: phpwiki Architecture: source all Version: 1.3.7-2 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: phpwiki- An informal collaborative website manager Closes: 225977 228115 228735 232361 233213 233599 236342 237016 237145 237254 238744 238845 240923 Changes: phpwiki (1.3.7-2) unstable; urgency=low . * Moved the PHPWIKI_VERSION define from index.php to lib/prepend.php, since it really isn't something user configurable. Closes: #233599. * As above, moved COPYRIGHTPAGE_TITLE, COPYRIGHTPAGE_URL, AUTHORPAGE_TITLE, and AUTHORPAGE_URL. Closes: 238845. * Applied revised patch to not use the button tag (from Norman Rasmussen) so that random password creation in passencrypt.php works in IE. Closes: #236342. * Use invoke-rc.d according to policy 9.3.3.2. Closes: #237145. * Explicitly disable output compression, since it apparently causes problems with PHP4 in CGI mode. Closes: #228735. * Modified dependcy information. No longer depend on apache or equivalent (Closes: #237016), remove version restriction on php4 (why was that ever even in there? PHPWiki runs fine on 4.1.2), and add php4-cgi as an alternative to php4, as it can be run on apache2 (I presume). * Symlink the apache config into /etc/srv/conf.d if possible instead of screwing with httpd.conf directly. Closes: #237254. * Remove the webservers config option from use. No need for it, as we should be able to automatically detect which webservers are available to install into. * Converted all of my upstream-able patches to use dpatch. Much cleaner diff now. Closes: #233213. That package needs a HOWTO to explain the simplest way of splitting out and converting patches - it wasn't a nice experience. * Explicitly disabled the wiki admin account, as there's no reasonable way to enable it without requiring user intervention at install, and the package works without it. Closes: #225977. * Converted new installation script to use SQLite instead of stupid, broken DB4. Closes: #232361. * Imported several upstream changes to better support SQLite: - Revision 1.41 of lib/WikiDB/backend/PearDB.php - Revision 1.42 of lib/WikiDB/backend/PearDB.php - schemas/sqlite.sql - lib/WikiDB/backend/sqlite.php * Imported CVS revision 1.3 of lib/imagecache.php to fix problems therein. Hopefully imagecaching will now work right, which makes the VisualWiki stuff work. Closes: #240923. * Added the pages FullTextSearch and FuzzyPages to the Italian localisation version, so that the searches will (apparently) work right. Committed upstream 9/04/2004. Closes: #228115. * Split out the postinst into several independent subroutines. * Added a new french debconf translation. Closes: #238744. * Now using the ucf --sum_file option on index.php so that upgrades might be a bit smoother. * Bumped standards-version to 3.6.1. No changes necessary. Files: bc7739465dc9bf65d4adda7394655e4a 580 web optional phpwiki_1.3.7-2.dsc 478be5f6c34897901ece679947649048 25105 web optional phpwiki_1.3.7-2.diff.gz ba00e423ba14e77f9d44a9faffb5b86e 1267448 web optional phpwiki_1.3.7-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAhwgFBEnrTWk1E4cRAl8RAJ49QB147GuOc8wt4yiYHaLXaGDCVACdFBvE lLFf3uveehhrNV6TfmGv3PQ= =Wu1W -END PGP SIGNATURE- Accepted: phpwiki_1.3.7-2.diff.gz to pool/main/p/phpwiki/phpwiki_1.3.7-2.diff.gz phpwiki_1.3.7-2.dsc to pool/main/p/phpwiki/phpwiki_1.3.7-2.dsc phpwiki_1.3.7-2_all.deb to pool/main/p/phpwiki/phpwiki_1.3.7-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fbpanel 3.5-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 20 Apr 2004 20:49:20 +1000 Source: fbpanel Binary: fbpanel Architecture: source i386 Version: 3.5-1 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: fbpanel- A lightweight X11 desktop panel Closes: 243495 Changes: fbpanel (3.5-1) unstable; urgency=low . * New upstream release. Closes: #243495. Files: 1a32e41ba553a5207ce0adc38f6603c2 567 x11 optional fbpanel_3.5-1.dsc 3935f4ca0aeeb25c3615eebeaca87eaa 68364 x11 optional fbpanel_3.5.orig.tar.gz d5b7314d9b78d42dda4801f7d8b30011 2107 x11 optional fbpanel_3.5-1.diff.gz 819dda6e468de0b8d792ea6618b8335e 61566 x11 optional fbpanel_3.5-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAhQUzBEnrTWk1E4cRAvgrAJ4s7xO63/okDt5LI0TIhNbYaaHj4ACfR1Fv CLvV0gLff4TzufrjdUPqZ8E= =Pfo9 -END PGP SIGNATURE- Accepted: fbpanel_3.5-1.diff.gz to pool/main/f/fbpanel/fbpanel_3.5-1.diff.gz fbpanel_3.5-1.dsc to pool/main/f/fbpanel/fbpanel_3.5-1.dsc fbpanel_3.5-1_i386.deb to pool/main/f/fbpanel/fbpanel_3.5-1_i386.deb fbpanel_3.5.orig.tar.gz to pool/main/f/fbpanel/fbpanel_3.5.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fbpanel 3.5-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 20 Apr 2004 21:20:36 +1000 Source: fbpanel Binary: fbpanel Architecture: source i386 Version: 3.5-2 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: fbpanel- A lightweight X11 desktop panel Closes: 235353 Changes: fbpanel (3.5-2) unstable; urgency=low . * Added the manual page to the installation. Closes: #235353. Files: 4e695be92469348fca36b283448171e7 567 x11 optional fbpanel_3.5-2.dsc cc13b1fa7e6eff85411aa0eb88d67dcd 2155 x11 optional fbpanel_3.5-2.diff.gz e929325ebe7b8d8847c0415d40049d2f 62802 x11 optional fbpanel_3.5-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAhQi+BEnrTWk1E4cRAqrbAJ0RKnPC+SREC1LLlLsRY/snmXdE8gCgpOjZ lJTy/X8n7sVIuIp/OlGk4XE= =xT2s -END PGP SIGNATURE- Accepted: fbpanel_3.5-2.diff.gz to pool/main/f/fbpanel/fbpanel_3.5-2.diff.gz fbpanel_3.5-2.dsc to pool/main/f/fbpanel/fbpanel_3.5-2.dsc fbpanel_3.5-2_i386.deb to pool/main/f/fbpanel/fbpanel_3.5-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted php4-sqlite 1.0.2-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 16 Mar 2004 22:54:44 +1100 Source: php4-sqlite Binary: php4-sqlite Architecture: source i386 Version: 1.0.2-2 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: php4-sqlite - PHP4 bindings to SQLite, a file-based SQL engine Changes: php4-sqlite (1.0.2-2) unstable; urgency=low . * Added an explicit path to phpize and specified the --with-php-config option to ./configure, to avoid problems if there's another version of PHP lying around, as suggested by Uwe Steinmann. * Totally reworked the build system to use my new dh_pecl debhelper script. Automagically generates dependencies and postinst code. W00t! Files: dc61acfe89d142bb08eae170abb7d329 600 web optional php4-sqlite_1.0.2-2.dsc 4545635dcab44b5f428863aaa346e399 6407 web optional php4-sqlite_1.0.2-2.diff.gz 99f9fd61fa989a3f74fe2e1b3cd06acc 1 web optional php4-sqlite_1.0.2-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAVu1SBEnrTWk1E4cRAhZ+AJsH0DgXYpqQNbcnS6BxHPK8Owlu4gCgguoG Cc5xRGRqQwQ/04ySnIkFNB8= =1xWE -END PGP SIGNATURE- Accepted: php4-sqlite_1.0.2-2.diff.gz to pool/main/p/php4-sqlite/php4-sqlite_1.0.2-2.diff.gz php4-sqlite_1.0.2-2.dsc to pool/main/p/php4-sqlite/php4-sqlite_1.0.2-2.dsc php4-sqlite_1.0.2-2_i386.deb to pool/main/p/php4-sqlite/php4-sqlite_1.0.2-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted php4-sqlite 1.0.2-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 17 Mar 2004 09:22:48 +1100 Source: php4-sqlite Binary: php4-sqlite Architecture: source i386 Version: 1.0.2-3 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: php4-sqlite - PHP4 bindings to SQLite, a file-based SQL engine Changes: php4-sqlite (1.0.2-3) unstable; urgency=low . * Modified dh_pecl to make dependencies for both the old and new API pseudo-packages. Thanks for Uwe for beating me over the head with this until my clue light *finally* came on. * Changed the extension dir handling to use php-config instead of guessing at it by hand. Files: ea2bd89dcc19e3bacd0dacfb83d9058a 600 web optional php4-sqlite_1.0.2-3.dsc e0f44152c1f78d74c35b31c4aae65920 6629 web optional php4-sqlite_1.0.2-3.diff.gz 68a10740d3710a2408104ba8a26f7b07 19084 web optional php4-sqlite_1.0.2-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAV6+TBEnrTWk1E4cRArd+AJ9rzCmp8w3z5SkbLKn02csY311ywgCfTA5P aEhMT6FjXPxwowGUYSYZEvk= =0PGV -END PGP SIGNATURE- Accepted: php4-sqlite_1.0.2-3.diff.gz to pool/main/p/php4-sqlite/php4-sqlite_1.0.2-3.diff.gz php4-sqlite_1.0.2-3.dsc to pool/main/p/php4-sqlite/php4-sqlite_1.0.2-3.dsc php4-sqlite_1.0.2-3_i386.deb to pool/main/p/php4-sqlite/php4-sqlite_1.0.2-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cyrus-imapd 1.5.19-17 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 1 Mar 2004 16:19:34 +1100 Source: cyrus-imapd Binary: cyrus-imapd cyrus-common cyrus-pop3d cyrus-dev cyrus-admin cyrus-news-spool Architecture: source i386 Version: 1.5.19-17 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: cyrus-admin - CMU Cyrus mail system (administration tool) cyrus-common - CMU Cyrus mail system (common files) cyrus-dev - CMU Cyrus mail system (developer files) cyrus-imapd - CMU Cyrus mail system (IMAP support) cyrus-news-spool - CMU Cyrus mail system (News spool support) cyrus-pop3d - CMU Cyrus mail system (POP3 support) Closes: 233985 234780 Changes: cyrus-imapd (1.5.19-17) unstable; urgency=low . * Added an example adduser.local for people to base automatic mailbox creation on. * Documented potential problems with pwcheck_standard. I don't want to change the default pwcheck, though, because it looks like it'd be hard work. grin Closes: 233985. * Applied minor bugfix to fix segfault if the deliverdb isn't available. Thanks to Paul Cannon for finding and fixing the bug. Closes: #234780. Files: 37c5165761489b097b69aacce559e7c7 703 mail extra cyrus-imapd_1.5.19-17.dsc e09a24304916c6bedd2ae9b37ba5ce20 36121 mail extra cyrus-imapd_1.5.19-17.diff.gz 73323d4ced859f1f45b13a30be85462e 395396 mail extra cyrus-common_1.5.19-17_i386.deb 8ef8a99160a9882b4360e0e490cfb3ff 129690 mail extra cyrus-imapd_1.5.19-17_i386.deb 64ab9d52ba9edf6b14b8807b81c52bdd 61972 mail extra cyrus-pop3d_1.5.19-17_i386.deb 6275fabaf5649f86744d913f9e5d48a7 15750 mail extra cyrus-news-spool_1.5.19-17_i386.deb c26d0f16cb0dbb38a685767459313062 42202 mail extra cyrus-admin_1.5.19-17_i386.deb 9344a4dd99fd3c8aba3e6abe0daf9641 79178 devel extra cyrus-dev_1.5.19-17_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAQtIaBEnrTWk1E4cRAicfAJ9I+yWOXFRqIk3p6nYLC2oTWYEUowCgr5kE 3LqlS1By8SR9umXBMp0c+wE= =xP1s -END PGP SIGNATURE- Accepted: cyrus-admin_1.5.19-17_i386.deb to pool/main/c/cyrus-imapd/cyrus-admin_1.5.19-17_i386.deb cyrus-common_1.5.19-17_i386.deb to pool/main/c/cyrus-imapd/cyrus-common_1.5.19-17_i386.deb cyrus-dev_1.5.19-17_i386.deb to pool/main/c/cyrus-imapd/cyrus-dev_1.5.19-17_i386.deb cyrus-imapd_1.5.19-17.diff.gz to pool/main/c/cyrus-imapd/cyrus-imapd_1.5.19-17.diff.gz cyrus-imapd_1.5.19-17.dsc to pool/main/c/cyrus-imapd/cyrus-imapd_1.5.19-17.dsc cyrus-imapd_1.5.19-17_i386.deb to pool/main/c/cyrus-imapd/cyrus-imapd_1.5.19-17_i386.deb cyrus-news-spool_1.5.19-17_i386.deb to pool/main/c/cyrus-imapd/cyrus-news-spool_1.5.19-17_i386.deb cyrus-pop3d_1.5.19-17_i386.deb to pool/main/c/cyrus-imapd/cyrus-pop3d_1.5.19-17_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted php4-sqlite 1.0.2-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 24 Jan 2004 16:08:44 +1100 Source: php4-sqlite Binary: php4-sqlite Architecture: source i386 Version: 1.0.2-1 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: php4-sqlite - PHP4 bindings to SQLite, a file-based SQL engine Closes: 187133 Changes: php4-sqlite (1.0.2-1) unstable; urgency=low . * Initial Release. Closes: #187133. Files: 0f7e0275b199c71d1f98ef2519fb9dec 600 web optional php4-sqlite_1.0.2-1.dsc d78102cd5d53adf08d9ff6eb0e80 16741 web optional php4-sqlite_1.0.2.orig.tar.gz 9546f096db66030deea0235ece942db5 4823 web optional php4-sqlite_1.0.2-1.diff.gz 28fc4403b6c22e25917a518c81100465 18146 web optional php4-sqlite_1.0.2-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAMUYOBEnrTWk1E4cRAp1fAJ9QXaSsdGoykMuo/n7/GNFOaU/c1gCdFuQQ FXh0EFca3kSDmSllsnoa3LQ= =jobe -END PGP SIGNATURE- Accepted: php4-sqlite_1.0.2-1.diff.gz to pool/main/p/php4-sqlite/php4-sqlite_1.0.2-1.diff.gz php4-sqlite_1.0.2-1.dsc to pool/main/p/php4-sqlite/php4-sqlite_1.0.2-1.dsc php4-sqlite_1.0.2-1_i386.deb to pool/main/p/php4-sqlite/php4-sqlite_1.0.2-1_i386.deb php4-sqlite_1.0.2.orig.tar.gz to pool/main/p/php4-sqlite/php4-sqlite_1.0.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted phpwiki 1.3.7-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 12 Feb 2004 20:55:20 +1100 Source: phpwiki Binary: phpwiki Architecture: source all Version: 1.3.7-1 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: phpwiki- An informal collaborative website manager Closes: 224149 227680 228497 228504 231101 231772 Changes: phpwiki (1.3.7-1) unstable; urgency=low . * New upstream version. Closes: #227680. * Included passencrypt.php in /usr/share/phpwiki, and ensured that the non-existent passwordencrypt.php isn't mentioned anywhere. Relates to: #225977. * Transitioned apache.conf to use ucf. Closes: #228497. * After much thrashing, made URL rewriting to my satisfaction, so we no longer get index.php's in the middle of our URLs (a long standing peeve of mine). Thanks to Andreas Krueger for giving me the gist of it all. Closes: #228504. * Automatically create a new database file, to work around blecherisms in PHP4's DB4 implementation. Closes: #224149. * New config file, debian-config.php, to set defaults for all those things that postinst needs to screw with in index.php. * Added a lock tables grant to INSTALL.mysql. Closes: #231101. * Added a brazilian debconf translation. Closes: #231772. * Made the upgrade detector a little less brutal. Files: 3c457238d90691b1ddf248c950eafe11 572 web optional phpwiki_1.3.7-1.dsc 05ea97d16cae4dfee3668ed038c835ce 1389983 web optional phpwiki_1.3.7.orig.tar.gz f9cc211a25705f1353ed6317a3fe9ea6 18126 web optional phpwiki_1.3.7-1.diff.gz a8dd6fd50dc2825dcf240d202e40fe5c 1264850 web optional phpwiki_1.3.7-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAK1EyBEnrTWk1E4cRAkIpAJ9E132U6LEF4yMowC1O/n9t6mBz3gCfcdRC BALkJijUzaVHmwpIfZNrF9c= =gcTS -END PGP SIGNATURE- Accepted: phpwiki_1.3.7-1.diff.gz to pool/main/p/phpwiki/phpwiki_1.3.7-1.diff.gz phpwiki_1.3.7-1.dsc to pool/main/p/phpwiki/phpwiki_1.3.7-1.dsc phpwiki_1.3.7-1_all.deb to pool/main/p/phpwiki/phpwiki_1.3.7-1_all.deb phpwiki_1.3.7.orig.tar.gz to pool/main/p/phpwiki/phpwiki_1.3.7.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cyrus-imapd 1.5.19-16 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 22 Jan 2004 14:02:44 +1100 Source: cyrus-imapd Binary: cyrus-imapd cyrus-common cyrus-pop3d cyrus-dev cyrus-admin cyrus-news-spool Architecture: source i386 Version: 1.5.19-16 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: cyrus-admin - CMU Cyrus mail system (administration tool) cyrus-common - CMU Cyrus mail system (common files) cyrus-dev - CMU Cyrus mail system (developer files) cyrus-imapd - CMU Cyrus mail system (IMAP support) cyrus-news-spool - CMU Cyrus mail system (News spool support) cyrus-pop3d - CMU Cyrus mail system (POP3 support) Closes: 219129 221952 228573 Changes: cyrus-imapd (1.5.19-16) unstable; urgency=low . * Applied patch from Bill Sidhipong to properly format dump_deliverdb dates. Closes: #221952. * Modified the default attributes of several critical directories to request synchronous writes. This may cause significant performance degradation, so if you have problems, please let me know and I'll reassess the impact. Closes: #219129. * Changed deps to exim4 to ease transition. Closes: #228573. Files: 6f37334c946135730d22a7781689efa7 703 mail extra cyrus-imapd_1.5.19-16.dsc 4db589c2c7c6e5206772648753c12897 35737 mail extra cyrus-imapd_1.5.19-16.diff.gz 1cb02bcdfeb76d1f9c4dd76febe1cf86 394860 mail extra cyrus-common_1.5.19-16_i386.deb 34937d587c20376a27e4d90efdf315f6 129514 mail extra cyrus-imapd_1.5.19-16_i386.deb 6130e408b34b46bf3f25b6271a76fc6f 61790 mail extra cyrus-pop3d_1.5.19-16_i386.deb b4764d4c96a4d9679de2edf5894c8392 15566 mail extra cyrus-news-spool_1.5.19-16_i386.deb bb64ac6b0eeac5925d32d1e3353764b0 42006 mail extra cyrus-admin_1.5.19-16_i386.deb 1fbe17dc9569050c49f0906cad9fa7f5 78982 devel extra cyrus-dev_1.5.19-16_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAD0qJBEnrTWk1E4cRAo02AJ9J1OFRYJdhIzMRzaOF+sC0F/t22QCeISOI 53f6nB9/b9MD5nXqcjWHeNg= =nyQn -END PGP SIGNATURE- Accepted: cyrus-admin_1.5.19-16_i386.deb to pool/main/c/cyrus-imapd/cyrus-admin_1.5.19-16_i386.deb cyrus-common_1.5.19-16_i386.deb to pool/main/c/cyrus-imapd/cyrus-common_1.5.19-16_i386.deb cyrus-dev_1.5.19-16_i386.deb to pool/main/c/cyrus-imapd/cyrus-dev_1.5.19-16_i386.deb cyrus-imapd_1.5.19-16.diff.gz to pool/main/c/cyrus-imapd/cyrus-imapd_1.5.19-16.diff.gz cyrus-imapd_1.5.19-16.dsc to pool/main/c/cyrus-imapd/cyrus-imapd_1.5.19-16.dsc cyrus-imapd_1.5.19-16_i386.deb to pool/main/c/cyrus-imapd/cyrus-imapd_1.5.19-16_i386.deb cyrus-news-spool_1.5.19-16_i386.deb to pool/main/c/cyrus-imapd/cyrus-news-spool_1.5.19-16_i386.deb cyrus-pop3d_1.5.19-16_i386.deb to pool/main/c/cyrus-imapd/cyrus-pop3d_1.5.19-16_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libapache-mod-auth-mysql 4.1.8 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 16 Jan 2004 12:47:46 +1030 Source: libapache-mod-auth-mysql Binary: libapache-mod-auth-mysql Architecture: source i386 Version: 4.1.8 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: libapache-mod-auth-mysql - Apache module for MySQL authentication Closes: 221923 226425 Changes: libapache-mod-auth-mysql (4.1.8) unstable; urgency=low . * Added conditionals and more calls to modules-config so that the module will install nicely into all apache flavours. Closes: #226425. * Applied a functionality improvement from Jakub Stachowski to add some arbitrary SQL to the end of a query, to improve matching. Closes: #221923. Files: e5130e18d795bc8ab2f67f5b84e8607d 573 web optional libapache-mod-auth-mysql_4.1.8.dsc d7681b7a7ed8de581002f6ab38fa49d8 50033 web optional libapache-mod-auth-mysql_4.1.8.tar.gz fbeedc08b1c5d6326f987f907da36d81 17754 web optional libapache-mod-auth-mysql_4.1.8_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAB0rvBEnrTWk1E4cRAvvbAJ9WbfT+e+itnqXP+K56fgHC01vTFgCfcn2b J/lcUP0VUtYyx7YiGWZfo6k= =qZb9 -END PGP SIGNATURE- Accepted: libapache-mod-auth-mysql_4.1.8.dsc to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.1.8.dsc libapache-mod-auth-mysql_4.1.8.tar.gz to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.1.8.tar.gz libapache-mod-auth-mysql_4.1.8_i386.deb to pool/main/liba/libapache-mod-auth-mysql/libapache-mod-auth-mysql_4.1.8_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libarr 0.1-50 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 12 Jan 2004 12:16:25 +1030 Source: libarr Binary: libarr0 libarr-dev Architecture: source i386 Version: 0.1-50 Distribution: unstable Urgency: low Maintainer: Matthew Palmer [EMAIL PROTECTED] Changed-By: Matthew Palmer [EMAIL PROTECTED] Description: libarr-dev - A small, fast console drawing library. libarr0- A small, fast console drawing library Changes: libarr (0.1-50) unstable; urgency=low . * QA Upload. * Fixed Maintainer field as per qa.d.o/orphaned.html. * Updated standards-version. * Fiddled lots and lots of little build warnings (includes). Files: 0ac6f5d01839d828b95991525c355684 538 libs optional libarr_0.1-50.dsc e70f00a10d28a6c78ccf0517b633c684 52420 libs optional libarr_0.1-50.tar.gz 2432914dc7d87e746179f0bc60ff930f 37882 devel optional libarr-dev_0.1-50_i386.deb c73e34f9ef2a03e3453e9ffd6b253e99 17868 libs optional libarr0_0.1-50_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAAuBNBEnrTWk1E4cRAj+sAJ4ma2rWnMUdQT/r3x6BfKpJknqDXgCgpeuR n3x/WhLjuoXZ4wS+oQqsrk4= =0jgV -END PGP SIGNATURE- Accepted: libarr-dev_0.1-50_i386.deb to pool/main/liba/libarr/libarr-dev_0.1-50_i386.deb libarr0_0.1-50_i386.deb to pool/main/liba/libarr/libarr0_0.1-50_i386.deb libarr_0.1-50.dsc to pool/main/liba/libarr/libarr_0.1-50.dsc libarr_0.1-50.tar.gz to pool/main/liba/libarr/libarr_0.1-50.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
