Re: I resigned in 2004
On Fri, Nov 09, 2018 at 09:29:30PM +0100, Mattia Rizzolo wrote: I would like to start by highlighting one very important line from my last email to you: > > Do not contact me with regard to Debian bullshit. And yet, you did. Fuck you. Do not contact me again. I shall consider any further contact (from you or anyone else in regards to this matter) as harassment, and I shall seek legal counsel. Your email is full of self-justifications and I have not the slightest interest in refuting any of them. You are a computer programmer pretending to be an HR department. You are no good at it. You have to appreciate that I owe you nothing. You don't pay me. It is not incumbent on me to do anything for you. Get a professional to review your procedures, because your procedures are completely inadequate. Causing people who I consider my friends to harass me to do something I find incredibly difficult and painful to do is not OK. You've made them complicit in hurting me. You've dragged up some awful memories from *fourteen* years ago, when I was betrayed by people who I thought were my friends. I don't care that you didn't do it on purpose. You've hurt me. And you made my friends hurt me. Again.
I resigned in 2004
I quit Debian development back in 2004. This was a moral decision, based on the malfeasance of the project secretary over the "Editorial changes" GR. For some reason, Debian as a project failed to notice that I had quit, even though my wi...@debian.org email address was deliberately forwarded to a non-functional email address (in part because of the complete catastrophe that was the Debian spam filtering system at the time). Over the last couple of months, the MIA team has been trying to get me to participate in some inane bureaucracy. I have been ignoring their emails. Today, they took it to a new level by encouraging everybody who knows me to pester me to answer my emails from them. This is not acceptable. Leave me alone. Your project left me long ago. Do not contact me with regard to Debian bullshit.
Accepted kerneloops 0.10-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 08 Apr 2008 06:44:14 -0400 Source: kerneloops Binary: kerneloops Architecture: source i386 Version: 0.10-2 Distribution: unstable Urgency: low Maintainer: Matthew Wilcox [EMAIL PROTECTED] Changed-By: Matthew Wilcox [EMAIL PROTECTED] Description: kerneloops - kernel oops tracker Changes: kerneloops (0.10-2) unstable; urgency=low . * Fixed missing build dependency Files: b4b6acb72f46443295f2c3c18387416f 635 utils optional kerneloops_0.10-2.dsc 1fe6a42a357346a4955247930243e2d3 2424 utils optional kerneloops_0.10-2.diff.gz 34a17bad041da000cead6fc3c9123701 19218 utils optional kerneloops_0.10-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFH+1UiIhjIHo58A/8RAu7gAJ9MIpF3TkRFXGzi8isy9fhHCXIxeACeJR3f 1dVRKWdy1LV5dHj4RyYbWEs= =0vqC -END PGP SIGNATURE- Accepted: kerneloops_0.10-2.diff.gz to pool/main/k/kerneloops/kerneloops_0.10-2.diff.gz kerneloops_0.10-2.dsc to pool/main/k/kerneloops/kerneloops_0.10-2.dsc kerneloops_0.10-2_i386.deb to pool/main/k/kerneloops/kerneloops_0.10-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted kerneloops 0.10-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 09 Jan 2008 20:43:31 -0500 Source: kerneloops Binary: kerneloops Architecture: source i386 Version: 0.10-1 Distribution: unstable Urgency: low Maintainer: Matthew Wilcox [EMAIL PROTECTED] Changed-By: Matthew Wilcox [EMAIL PROTECTED] Description: kerneloops - kernel oops tracker Closes: 459433 Changes: kerneloops (0.10-1) unstable; urgency=low . * New upstream version * Install init.d script (closes: #459433) * Depend on libcurl4-gnutls-dev | libcurl-dev in order to get the same library on all the buildds * Drop our manpage in favour of the one now provided by upstream * Run test suite as part of build Files: b2920c2c48b47fa2cc03248cf79beae3 615 utils optional kerneloops_0.10-1.dsc 676f64d4a01c54f9272e986478be501b 60001 utils optional kerneloops_0.10.orig.tar.gz df115e79f5aa3faab03cf7355d375612 2378 utils optional kerneloops_0.10-1.diff.gz 34b05f7eecaad7978c5f3bdfbfd32228 19170 utils optional kerneloops_0.10-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFH+raAIhjIHo58A/8RAtvGAJ9qvji/h21KHcnZyz/ROsRMsDUH3gCeIOTX USnQSOecfnhtuB1v2CwPeFM= =si++ -END PGP SIGNATURE- Accepted: kerneloops_0.10-1.diff.gz to pool/main/k/kerneloops/kerneloops_0.10-1.diff.gz kerneloops_0.10-1.dsc to pool/main/k/kerneloops/kerneloops_0.10-1.dsc kerneloops_0.10-1_i386.deb to pool/main/k/kerneloops/kerneloops_0.10-1_i386.deb kerneloops_0.10.orig.tar.gz to pool/main/k/kerneloops/kerneloops_0.10.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted kerneloops 0.7-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 29 Dec 2007 13:03:23 -0500 Source: kerneloops Binary: kerneloops Architecture: source i386 Version: 0.7-1 Distribution: unstable Urgency: low Maintainer: Matthew Wilcox [EMAIL PROTECTED] Changed-By: Matthew Wilcox [EMAIL PROTECTED] Description: kerneloops - kernel oops tracker Closes: 458177 Changes: kerneloops (0.7-1) unstable; urgency=low . * New upstream version - Fixes memory leak (closes: #458177) Files: db12baf4e48c7041ca1e0e2704f134b8 575 utils optional kerneloops_0.7-1.dsc 023c8a193d1816b111377ff61ae9916d 42538 utils optional kerneloops_0.7.orig.tar.gz 5f2e1b8e25cbe291459f0f457c391ee0 1839 utils optional kerneloops_0.7-1.diff.gz 91fdf4c64dfc5560eb5e13954c53966a 8770 utils optional kerneloops_0.7-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHdoyQIhjIHo58A/8RAlv2AJ9nzPopAucDKQXNXXVrFE1e5z6ZQgCfbw9C zmMA8WOiMmmJiZZ3dlkNKHk= =ftTk -END PGP SIGNATURE- Accepted: kerneloops_0.7-1.diff.gz to pool/main/k/kerneloops/kerneloops_0.7-1.diff.gz kerneloops_0.7-1.dsc to pool/main/k/kerneloops/kerneloops_0.7-1.dsc kerneloops_0.7-1_i386.deb to pool/main/k/kerneloops/kerneloops_0.7-1_i386.deb kerneloops_0.7.orig.tar.gz to pool/main/k/kerneloops/kerneloops_0.7.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted kerneloops 0.3-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 14 Dec 2007 10:47:41 -0500 Source: kerneloops Binary: kerneloops Architecture: source i386 Version: 0.3-1 Distribution: unstable Urgency: low Maintainer: Matthew Wilcox [EMAIL PROTECTED] Changed-By: Matthew Wilcox [EMAIL PROTECTED] Description: kerneloops - kernel oops tracker Changes: kerneloops (0.3-1) unstable; urgency=low . * New upstream version Files: d55841518283298e4f788c63f23d1460 575 utils optional kerneloops_0.3-1.dsc cf8a4ed6a443528d9619be28ef590254 11823 utils optional kerneloops_0.3.orig.tar.gz 84a42cbc8ce781a378b44159e01bcbff 1782 utils optional kerneloops_0.3-1.diff.gz bde6e38926842f1c7e82491a42f6aad9 7258 utils optional kerneloops_0.3-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHYqo8IhjIHo58A/8RAgepAJ9aAVwnfT6zuV+7wP72HP63ZLLk9wCfYpr2 FZ+WYdw7078VRwnDudvZv1M= =ViRE -END PGP SIGNATURE- Accepted: kerneloops_0.3-1.diff.gz to pool/main/k/kerneloops/kerneloops_0.3-1.diff.gz kerneloops_0.3-1.dsc to pool/main/k/kerneloops/kerneloops_0.3-1.dsc kerneloops_0.3-1_i386.deb to pool/main/k/kerneloops/kerneloops_0.3-1_i386.deb kerneloops_0.3.orig.tar.gz to pool/main/k/kerneloops/kerneloops_0.3.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apache 1.3 will soon be removed from testing/unstable
On Mon, Apr 30, 2007 at 12:56:17PM -0500, Peter Samuelson wrote: Same for apache 1.3 (including apache, apache-ssl, apache-perl); it too will soon disappear from sid and lenny. There are currently only a handful of apache 1.3 module packages in sid, against which bugs will be filed, but there are quite a few packages which depend on things like apache | httpd, which should be updated, though not urgently. Reply-To set to to the debian-apache list. Should apache2 Replace/Provide: apache in Lenny in order to facilitate upgrades from Etch? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lack of a GR proposal explicitly condemning dunc-tank
On Thu, Oct 12, 2006 at 05:34:01PM +0100, Ian Jackson wrote: I wrote: Normally I wouldn't publish private email but I think in this case the abusive nature warrants it. It really doesn't. Wanker. It has been suggested that it would be better to include the context, to avoid any potential or perceived unfairness, given that the context was a debian-private posting by me. So here is the whole of Matthew's message, including the text of my message which he is objecting to: On Wed, Oct 11, 2006 at 02:17:50PM +0100, Ian Jackson wrote: So I'd like to encourage dunc-tank opponents to consider whether they ought to have seconded my resolution too. There's still time to do so I think. I'm so thoroughly disgusted by you and the actions of people like you that I've stopped working on Debian. nice job, wanker. Apparently taking the other side in this controversy is, in Matthew's view, a justification for vitriol. Hey, Ian, you're trebly a wanker. Thanks for confirming my decision. I'm not going to explain my position as you'd only use it as an excuse to debate me. I am sick and fucking tired of the wankery coming from the parts of the debian disorganisation who don't want anything to change. It makes me so fucking angry that I've decided to just stop doing anything Debian related. I'm tempted to propose expulsion for a whole bunch of people, except that would involve dealing with Manoj, who I loathe. So, in summary: ___ / _|_ _ ___| | __ _ _ ___ _ _ | |_| | | |/ __| |/ / | | | |/ _ \| | | | | _| |_| | (__| | |_| | (_) | |_| | |_| \__,_|\___|_|\_\ \__, |\___/ \__,_| |___/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#388805: RFP: please package mod_auth_xradius
reassign 388805 libapache-mod-auth-radius retitle 388805 Please build apache 2 version kthxbye On Fri, Sep 22, 2006 at 07:10:04PM +0200, Ond??ej Sur?? wrote: retitle 388805 RFP: please package mod_auth_xradius reassign 388805 wnpp severity 388805 wishlist thank you You have filled bug at wrong package. Apache 2.X doesn't contain module for radius auth. However I was able to find mod_auth_xradius, so I am changing your bug to RFP (Request For Package) and reassigning it to our WNPP database. Yeah, but that's wrong. libapache-mod-auth-radius contains the source for an apache 2.0 module, it jsut isn't built right now. mod_auth_xradius provides high performance authentication against RFC 2865 RADIUS Servers. Features *Supports popular RADIUS Servers including OpenRADIUS, FreeRADIUS and commercial servers. *Distributed Authentication Cache using apr_memcache. *Local Authentication Cache using DBM. *Uses standard HTTP Basic Authentication, unlike mod_auth_radius which uses cookies for sessions. Kind regards, -- Ond??ej Sur?? [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted pciutils 1:2.2.4~pre4-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 11 Aug 2006 07:34:06 -0400 Source: pciutils Binary: pciutils-dev pciutils pciutils-udeb Architecture: source i386 Version: 1:2.2.4~pre4-1 Distribution: unstable Urgency: low Maintainer: Debian pciutils Maintainers [EMAIL PROTECTED] Changed-By: Matthew Wilcox [EMAIL PROTECTED] Description: pciutils - Linux PCI Utilities pciutils-dev - Linux PCI Utilities (development files) pciutils-udeb - Linux PCI Utilities (udeb) (udeb) Closes: 268031 335665 379407 Changes: pciutils (1:2.2.4~pre4-1) unstable; urgency=low . [ Matthew Wilcox ] * New upstream version - Adds -nn option. Closes: #268031 - Adds deviceclass field. Closes: #335665 - Fixes I/O port access on Hurd. Closes: #379407 Files: 5994e4d05190601677d4a5a0347ddab5 781 admin optional pciutils_2.2.4~pre4-1.dsc 52d9d556c90a9e559128d062742a6fdd 234325 admin optional pciutils_2.2.4~pre4.orig.tar.gz 97207f668bbd49032b811d1820b4a506 32231 admin optional pciutils_2.2.4~pre4-1.diff.gz b0337b0c6a19237fe4634646ced40411 206074 admin optional pciutils_2.2.4~pre4-1_i386.deb 4b3589420a6accdb59ee0bace432c092 31718 devel optional pciutils-dev_2.2.4~pre4-1_i386.deb 5b524297fea8c2bd4a08c14013b68d4f 107660 debian-installer optional pciutils-udeb_2.2.4~pre4-1_i386.udeb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE5YEFHk9mSeopF4URAgW3AKCKcFbpbf53m6cL3OxafLTLUyJiSQCgtsuV 2nxmxGnVWuBJc6K4pwQPWls= =oWV+ -END PGP SIGNATURE- Accepted: pciutils-dev_2.2.4~pre4-1_i386.deb to pool/main/p/pciutils/pciutils-dev_2.2.4~pre4-1_i386.deb pciutils-udeb_2.2.4~pre4-1_i386.udeb to pool/main/p/pciutils/pciutils-udeb_2.2.4~pre4-1_i386.udeb pciutils_2.2.4~pre4-1.diff.gz to pool/main/p/pciutils/pciutils_2.2.4~pre4-1.diff.gz pciutils_2.2.4~pre4-1.dsc to pool/main/p/pciutils/pciutils_2.2.4~pre4-1.dsc pciutils_2.2.4~pre4-1_i386.deb to pool/main/p/pciutils/pciutils_2.2.4~pre4-1_i386.deb pciutils_2.2.4~pre4.orig.tar.gz to pool/main/p/pciutils/pciutils_2.2.4~pre4.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libpci2 2:2.1.11-3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 11 Aug 2006 15:38:36 -0400 Source: libpci2 Binary: libpci2 Architecture: source i386 Version: 2:2.1.11-3 Distribution: unstable Urgency: low Maintainer: Debian pciutils Maintainers [EMAIL PROTECTED] Changed-By: Matthew Wilcox [EMAIL PROTECTED] Description: libpci2- Obsolete shared library for accessing pci devices Closes: 372264 Changes: libpci2 (2:2.1.11-3) unstable; urgency=low . * Apply GNU/kFreeBSD patch. Closes: 372264 * Update to Policy 3.7.2 Files: 0ab3f278c06cc2b90d4268971fa49a2a 729 oldlibs optional libpci2_2.1.11-3.dsc 2523a9675458b1532968cf838bdeb0c0 98226 oldlibs optional libpci2_2.1.11-3.diff.gz b31fb401c09da86b5d0b6d49d5cad6ba 27940 oldlibs optional libpci2_2.1.11-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE5YFDHk9mSeopF4URAkRQAKCDs+w0Pskb4i3xhEaUuwS/CNUDKACfYDJ1 Mbszsd9hJX5LfkBdyMJ9/DA= =malF -END PGP SIGNATURE- Accepted: libpci2_2.1.11-3.diff.gz to pool/main/libp/libpci2/libpci2_2.1.11-3.diff.gz libpci2_2.1.11-3.dsc to pool/main/libp/libpci2/libpci2_2.1.11-3.dsc libpci2_2.1.11-3_i386.deb to pool/main/libp/libpci2/libpci2_2.1.11-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mencal 2.3-6 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 10 Jul 2006 20:03:34 -0400 Source: mencal Binary: mencal Architecture: source all Version: 2.3-6 Distribution: unstable Urgency: low Maintainer: Amaya Rodrigo Sastre [EMAIL PROTECTED] Changed-By: Matthew Wilcox [EMAIL PROTECTED] Description: mencal - A menstruation calendar Closes: 344550 Changes: mencal (2.3-6) unstable; urgency=low . * Added myself to Uploaders, as requested by Amaya * Updated Standards version to 3.7.2 * Merge mencal and mencalnreg, incorporate updated patch. Closes: #344550 * Switch from dh_installmanpges to dh_installman * Fix lintian error by switching debhelper from Build-Depends-Indep to Build-Depends Files: 4850ae711709dfc7d2768b764c3b092e 603 utils optional mencal_2.3-6.dsc fa9d5a8b2d0e7244b1f60b27710ebcec 10493 utils optional mencal_2.3-6.diff.gz 8731af34ca24e04bdebada3b63392de2 14172 utils optional mencal_2.3-6_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEtRu8IhjIHo58A/8RAk3NAJ4jCmiBqbTXxPE5Q41mKihfxRRgrACdEwAK 8k/kMpZv6C0iJ4uSyoJyqEo= =Q+Gw -END PGP SIGNATURE- Accepted: mencal_2.3-6.diff.gz to pool/main/m/mencal/mencal_2.3-6.diff.gz mencal_2.3-6.dsc to pool/main/m/mencal/mencal_2.3-6.dsc mencal_2.3-6_all.deb to pool/main/m/mencal/mencal_2.3-6_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted pciutils 1:2.2.1-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 07 Jun 2006 11:09:11 -0400 Source: pciutils Binary: pciutils-dev pciutils pciutils-udeb Architecture: source i386 Version: 1:2.2.1-2 Distribution: unstable Urgency: low Maintainer: Debian pciutils Maintainers [EMAIL PROTECTED] Changed-By: Matthew Wilcox [EMAIL PROTECTED] Description: pciutils - Linux PCI Utilities pciutils-dev - Linux PCI Utilities (development files) pciutils-udeb - Linux PCI Utilities (udeb) (udeb) Changes: pciutils (1:2.2.1-2) unstable; urgency=low . * Fix Maintainer email address Files: f0f6829f3cced9e603c92d85ef072140 766 admin optional pciutils_2.2.1-2.dsc d7a692d5138146d3deea92851bc17724 46952 admin optional pciutils_2.2.1-2.diff.gz c709c93bab711955f62589f0e4a488f0 195946 admin optional pciutils_2.2.1-2_i386.deb 3be2154ff097028f7020b8f9c72f40b7 30916 devel optional pciutils-dev_2.2.1-2_i386.deb 1919a623ead3527eef03cd68d12370da 103198 debian-installer optional pciutils-udeb_2.2.1-2_i386.udeb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEjkMkHk9mSeopF4URAodrAJ4nqra0y92N+AkMnCYbTxGMtG7n5gCfaYPO K8u2FILeUhIZTs9dJJJ/dYc= =hcua -END PGP SIGNATURE- Accepted: pciutils-dev_2.2.1-2_i386.deb to pool/main/p/pciutils/pciutils-dev_2.2.1-2_i386.deb pciutils-udeb_2.2.1-2_i386.udeb to pool/main/p/pciutils/pciutils-udeb_2.2.1-2_i386.udeb pciutils_2.2.1-2.diff.gz to pool/main/p/pciutils/pciutils_2.2.1-2.diff.gz pciutils_2.2.1-2.dsc to pool/main/p/pciutils/pciutils_2.2.1-2.dsc pciutils_2.2.1-2_i386.deb to pool/main/p/pciutils/pciutils_2.2.1-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted pciutils 1:2.2.1-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 20 Apr 2006 21:01:24 -0400 Source: pciutils Binary: pciutils-dev pciutils pciutils-udeb Architecture: source i386 Version: 1:2.2.1-1 Distribution: unstable Urgency: low Maintainer: Debian pciutils Maintainers [EMAIL PROTECTED] Changed-By: Matthew Wilcox [EMAIL PROTECTED] Description: pciutils - Linux PCI Utilities pciutils-dev - Linux PCI Utilities (development files) pciutils-udeb - Linux PCI Utilities (udeb) (udeb) Closes: 173274 256607 265745 265771 292324 302142 304576 329370 336331 343222 347872 347877 349239 356129 369751 Changes: pciutils (1:2.2.1-1) unstable; urgency=low . [ Matthew Wilcox ] * New upstream version. Closes: #329370 - Builds on HURD. Closes: #349239 - Debian GNU/kFreeBSD should now build. Closes: #292324 - Uses correct header type for PCI-X. Closes: #265745 - u64 is now defined in include/pci/types.h. Closes: #265771 - Subsystem vendors now printed correctly. Closes: #304576 - Error message corrected. Closes: #347872 - nv40 replaced with NV40. Closes: #343222 - Memory window size now reported correctly. Closes: #256607 - The manpage now explains why capabilties are available only to root. Closes: #173274 - Domains are properly supported. Closes: #369751 * New debian maintainers. Thanks to Remco for his years of service. * Added option to use curl (instead of wget or lynx) to retrieve pci.ids * Revert patch to change -m format from #250737. Closes: #347877 * Move /var/lib/pciutils/pci.ids back to /usr/share/misc/pci.ids. Closes: #336331 * Fix typos in pcimodules manpages. Closes: #356129, #302142 * Remove libpci.so.2; depend on libpci2 to provide this for compatibility with sarge. * Build libpci.a with -fPIC for packages which need to build shared libraries. * Remove -X option as upstream has vetoed it. It wasn't actually being used anyway. * Add -D option (which will be in the next upstream release) to always show domains. * Stop installing the pciutils.lsm file. . [ Matt Taggart ] * update debian/copyright date and author email address * Make the pci.ids update a separate debian/rules target that's not invoked in a default build * minor cleanups in debian/rules * get rid of README.debian, it's redundant with upstream info Files: 415618ebb5838d615b7d09927144400c 764 admin optional pciutils_2.2.1-1.dsc c18e2a5f04e9abae5a42439de294f086 194389 admin optional pciutils_2.2.1.orig.tar.gz cee9c8ca933585d32773f2e6f78abbfb 46911 admin optional pciutils_2.2.1-1.diff.gz fb4af90f6e631e75f73b3f403b65b272 196476 admin optional pciutils_2.2.1-1_i386.deb 84511b5cc51b32c081b735edba0972f2 30996 devel optional pciutils-dev_2.2.1-1_i386.deb a6c6f9c291f2185ad2ff59f714b1ef60 102978 debian-installer optional pciutils-udeb_2.2.1-1_i386.udeb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEhSN8Hk9mSeopF4URAsTOAJ9qcVOfQH7Mcg22fwE9Nn0mIk++6gCfRrzZ foQ8YONE+pJT9Pne0SqKMpg= =7AgB -END PGP SIGNATURE- Accepted: pciutils-dev_2.2.1-1_i386.deb to pool/main/p/pciutils/pciutils-dev_2.2.1-1_i386.deb pciutils-udeb_2.2.1-1_i386.udeb to pool/main/p/pciutils/pciutils-udeb_2.2.1-1_i386.udeb pciutils_2.2.1-1.diff.gz to pool/main/p/pciutils/pciutils_2.2.1-1.diff.gz pciutils_2.2.1-1.dsc to pool/main/p/pciutils/pciutils_2.2.1-1.dsc pciutils_2.2.1-1_i386.deb to pool/main/p/pciutils/pciutils_2.2.1-1_i386.deb pciutils_2.2.1.orig.tar.gz to pool/main/p/pciutils/pciutils_2.2.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libpci2 2:2.1.11-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 16 Mar 2006 07:23:22 -0500 Source: libpci2 Binary: libpci2 Architecture: source i386 Version: 2:2.1.11-1 Distribution: unstable Urgency: low Maintainer: Debian pciutils Maintainers [EMAIL PROTECTED] Changed-By: Matthew Wilcox [EMAIL PROTECTED] Description: libpci2- Obsolete shared library for accessing pci devices Changes: libpci2 (2:2.1.11-1) unstable; urgency=low . * New package for static libpci transition Files: 270ca17b172b8984a351b757e25bd782 727 oldlibs optional libpci2_2.1.11-1.dsc 89e8724a48f723a05c1ba4ccb83af790 120932 oldlibs optional libpci2_2.1.11.orig.tar.gz 7b794dd7ce3c05be048b112b68dec701 97905 oldlibs optional libpci2_2.1.11-1.diff.gz 25f4eba2bde622972a28b1cfa6586201 27964 oldlibs optional libpci2_2.1.11-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEWwP6Hk9mSeopF4URAuu4AJ0Wc338Q7KlKrhidFwgXYqz+tS3+wCfVtxO 9Qeh/SHTYNlA+Bww5TrSnHo= =YHuN -END PGP SIGNATURE- Accepted: libpci2_2.1.11-1.diff.gz to pool/main/libp/libpci2/libpci2_2.1.11-1.diff.gz libpci2_2.1.11-1.dsc to pool/main/libp/libpci2/libpci2_2.1.11-1.dsc libpci2_2.1.11-1_i386.deb to pool/main/libp/libpci2/libpci2_2.1.11-1_i386.deb libpci2_2.1.11.orig.tar.gz to pool/main/libp/libpci2/libpci2_2.1.11.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NEW handling: About rejects, and kernels (Was: Re: NEW handling ...)
On Tue, Mar 22, 2005 at 09:06:19AM -0300, Humberto Massa wrote: And I believe that the Vancouver proposal, if implemented as intended up to now, will not only affect what Debian really *is*, but in some ways will *destroy* what Debian is. Debian has already decided to destroy what it is by giving in to the crackpots who insist that everything is software. -- Next the statesmen will invent cheap lies, putting the blame upon the nation that is attacked, and every man will be glad of those conscience-soothing falsities, and will diligently study them, and refuse to examine any refutations of them; and thus he will by and by convince himself that the war is just, and will thank God for the better sleep he enjoys after this process of grotesque self-deception. -- Mark Twain -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NEW handling: About rejects, and kernels (Was: Re: NEW handling ...)
On Mon, Mar 21, 2005 at 03:20:29PM +0100, Sven Luther wrote: Anyway, regarding kernels: I can imagine sometimes, especially with the backlog we have currently, a swift processing of some kernel package might be warranted and help Sarge. If there is such a case, it would help if someone other than yourself from the kernel team contact the right email address[3] about it, I had a hard time distilling from your Why not me ? I would very much like a reason for that, am i in some way Because you are impossible to deal with. I think this mail from you shows all the characteristics which make you such a pain in the fucking arse. See a psychologist. Really. -- Next the statesmen will invent cheap lies, putting the blame upon the nation that is attacked, and every man will be glad of those conscience-soothing falsities, and will diligently study them, and refuse to examine any refutations of them; and thus he will by and by convince himself that the war is just, and will thank God for the better sleep he enjoys after this process of grotesque self-deception. -- Mark Twain -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: *** SPAM *** Re: NEW handling: About rejects, and kernels (Was: Re: NEW handling ...)
On Mon, Mar 21, 2005 at 04:08:19PM +0100, Sven Luther wrote: Thanks. Maybe i should resign from my debian duties then since i am not wanted. Do you volunteer to take over my packages ? Please handle parted for which i am searching a co-maintainer since 6 month, and take over the powerpc kernels as well as do my job in the debian kernel team, as well as the support of powerpc issues in d-i and the maintainance of a big part of the ocaml subset. I think Debian would be better finding someone else to do those tasks, yes. I'm not going to volunteer for them as I intend to leave Debian shortly after sarge releases. I can't believe Debian is so short on skills that it needs you. Not friendly anymore and expecting excuses from you Matthew and the whole ftp-master team for their discrimination of me. Your emails have never had a friendly tone, despite the way you put friendly at the bottom of every one of them. -- Next the statesmen will invent cheap lies, putting the blame upon the nation that is attacked, and every man will be glad of those conscience-soothing falsities, and will diligently study them, and refuse to examine any refutations of them; and thus he will by and by convince himself that the war is just, and will thank God for the better sleep he enjoys after this process of grotesque self-deception. -- Mark Twain -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: *** SPAM *** Re: NEW handling: About rejects, and kernels (Was: Re: NEW handling ...)
On Mon, Mar 21, 2005 at 05:10:12PM +0100, Andreas Barth wrote: * Matthew Wilcox ([EMAIL PROTECTED]) [050321 17:05]: I'm not going to volunteer for them as I intend to leave Debian shortly after sarge releases. Why do you intend to leave Debian? The Vancouver meeting summary upset me, not because of the proposals to drop architectures, but because it contained a reminder of the Social Contract changes. The project is moving to what I believe to be a ridiculously extremist position. I can't support the new Social Contract, and wouldn't sign up for it if I were going through NM right now. So the only honourable thing for me to do is resign at the point when it come into effect. It saddens me greatly that we've come to this situation. I've been proud to be a Debian Developer for the past 6 years. I'd like to say, as others have when resigning, that I will continue to run Debian on my machines, but I can't. Moving documentation to non-free makes Debian a less suitable distribution for me. I shall have to look around and see what other distributions suit my needs. I'd like to thank my friends in Debian who've made it worth working on. Those who've been involved in the PA-RISC port (which I first joined Debian to work on). The Apache team have done a fantastic job, and I'm proud of how that worked out. I didn't realise how emotionally attached I was until I came to write this mail. I really wish things could have worked out better. -- Next the statesmen will invent cheap lies, putting the blame upon the nation that is attacked, and every man will be glad of those conscience-soothing falsities, and will diligently study them, and refuse to examine any refutations of them; and thus he will by and by convince himself that the war is just, and will thank God for the better sleep he enjoys after this process of grotesque self-deception. -- Mark Twain -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted lwm 1.2.1-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 26 Feb 2005 21:18:36 -0500 Source: lwm Binary: lwm Architecture: source i386 Version: 1.2.1-1 Distribution: unstable Urgency: low Maintainer: Matthew Wilcox [EMAIL PROTECTED] Changed-By: Matthew Wilcox [EMAIL PROTECTED] Description: lwm- Lightweight Window Manager Closes: 257251 275836 279410 Changes: lwm (1.2.1-1) unstable; urgency=low . * New upstream release. Closes: #279410 * Change build-dependency from xlibs-dev to the libs we actually depend on * Reword manpage to clarify the button 3 menu. Closes: #275836 * Move setlocale() call after XCreateFontSet(). Closes: #257251 Files: 82a114a64e18ce414442c03a3d20ee79 591 x11 optional lwm_1.2.1-1.dsc 499b2789198e8056f829ab724ad8f541 46309 x11 optional lwm_1.2.1.orig.tar.gz 809765876497bfa1b4005b70177b 3375 x11 optional lwm_1.2.1-1.diff.gz 02d26754557b8a038678d44ed950ca60 34266 x11 optional lwm_1.2.1-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCIiPNIhjIHo58A/8RAmAGAJ96OIoidrAe2StcYSsGn8TEjUs7HQCdHPxo 1SRagSOxrSB6S7aMkQ4Qg2Y= =Jnn8 -END PGP SIGNATURE- Accepted: lwm_1.2.1-1.diff.gz to pool/main/l/lwm/lwm_1.2.1-1.diff.gz lwm_1.2.1-1.dsc to pool/main/l/lwm/lwm_1.2.1-1.dsc lwm_1.2.1-1_i386.deb to pool/main/l/lwm/lwm_1.2.1-1_i386.deb lwm_1.2.1.orig.tar.gz to pool/main/l/lwm/lwm_1.2.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted keyanalyze 0.0.200204-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 19 Jun 2004 13:07:48 -0400 Source: keyanalyze Binary: keyanalyze Architecture: source i386 Version: 0.0.200204-1 Distribution: unstable Urgency: low Maintainer: Matthew Wilcox [EMAIL PROTECTED] Changed-By: Matthew Wilcox [EMAIL PROTECTED] Description: keyanalyze - OpenPGP key analysis Closes: 238140 Changes: keyanalyze (0.0.200204-1) unstable; urgency=low . * Initial release (Closes: #238140) * pgpring: - Fixed key ID generation for ElGamal primary keys - Enabled -W -Wall -g -O2 CFLAGS - Fixed type-punning problems - Fixed implicit declaration of exit() - Wrote manpage * process_keys: - Deleted two unused variables - Wrote manpage * keyanalyze: - Rewrote list handling to solve off-by-one problems - Used an array of structs instead of a lot of arrays - Made it accept -i and -o arguments to override the input and output names. - Wrote manpage Files: 51a98be03580dcffaa2f632526d4097c 584 utils optional keyanalyze_0.0.200204-1.dsc 46c1928c0ed298696f9f06b747fa0e85 69618 utils optional keyanalyze_0.0.200204.orig.tar.gz 3cc760ffc7d6f0944292386e90777492 14571 utils optional keyanalyze_0.0.200204-1.diff.gz 8fdb3ba25210815ba0d821c1a5c4bb66 32608 utils optional keyanalyze_0.0.200204-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFA1HRLIhjIHo58A/8RAhacAJ4hPKEvLrJZajG8b42J27dqsFhWuACfQ7F7 j9Y39l/H/EHQxhYrcz8Ubb0= =uajj -END PGP SIGNATURE- Accepted: keyanalyze_0.0.200204-1.diff.gz to pool/main/k/keyanalyze/keyanalyze_0.0.200204-1.diff.gz keyanalyze_0.0.200204-1.dsc to pool/main/k/keyanalyze/keyanalyze_0.0.200204-1.dsc keyanalyze_0.0.200204-1_i386.deb to pool/main/k/keyanalyze/keyanalyze_0.0.200204-1_i386.deb keyanalyze_0.0.200204.orig.tar.gz to pool/main/k/keyanalyze/keyanalyze_0.0.200204.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Conflicting manpage for queue.3
[ As suggested by Policy 10.1 [1], I am forwarding this issue to debian-devel. Please maintain the cc list in followups. ] Recent versions of manpages-dev include a new manpage queue.3. dqs has been providing a manpage by this name for some time. Therefore there is a file conflict when attempting to install both. manpages-dev is effectively a required package on any system where people do development. Its contents are part of every major Linux distribution. For us to rename the queue.3 manpage in manpages-dev would be a negative user experience for people switching to Debian or using a mixture of Debian and other non-Debian Linux systems. Additionally, dqs is non-free and therefore not part of Debian. It seems doubly foolish for manpages-dev to rename its manpage. I therefore submit that bugs #208294 and #211620 be reassigned to dqs and merged with bug #213526. In addition, I think dqs should probably be added to the RFA: or O: list as it has had a release critical bug open for 211 days as well as several easily-fixable bugs open for much longer and no uploads since woody. [1] 10.1 Binaries Two different packages must not install programs with different functionality but with the same filenames. (The case of two programs having the same functionality but different implementations is handled via alternatives or the Conflicts mechanism. See Maintainer Scripts, Section 3.10 and Conflicting binary packages - Conflicts, Section 7.3 respectively.) If this case happens, one of the programs must be renamed. The maintainers should report this to the debian-devel mailing list and try to find a consensus about which program will have to be renamed. If a consensus cannot be reached, both programs must be renamed. -- Next the statesmen will invent cheap lies, putting the blame upon the nation that is attacked, and every man will be glad of those conscience-soothing falsities, and will diligently study them, and refuse to examine any refutations of them; and thus he will by and by convince himself that the war is just, and will thank God for the better sleep he enjoys after this process of grotesque self-deception. -- Mark Twain
Accepted lwm 1.2.0-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 09 Dec 2003 11:34:24 -0500 Source: lwm Binary: lwm Architecture: source i386 Version: 1.2.0-1 Distribution: unstable Urgency: low Maintainer: Matthew Wilcox [EMAIL PROTECTED] Changed-By: Matthew Wilcox [EMAIL PROTECTED] Description: lwm- Lightweight Window Manager Changes: lwm (1.2.0-1) unstable; urgency=low . * New upstream release. * Remove lesstif-dev from build-depends since it's no longer needed. Files: 268386923a1568a8884fb43385dfd609 559 x11 optional lwm_1.2.0-1.dsc 22e3a008edeccdc3913eec72a4b56b1b 45622 x11 optional lwm_1.2.0.orig.tar.gz 1300dff20a857eaafaf53e3f0826c1f0 2860 x11 optional lwm_1.2.0-1.diff.gz 3d0c5b8edbbab700ea28b035c83caffa 33842 x11 optional lwm_1.2.0-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/1f3tIhjIHo58A/8RAt35AJ9hiAlhOyF1j1CRk+zMvLLEsJza5ACeL3WF MRWua2oyppx3SCBaX+N7Ipw= =OX/a -END PGP SIGNATURE- Accepted: lwm_1.2.0-1.diff.gz to pool/main/l/lwm/lwm_1.2.0-1.diff.gz lwm_1.2.0-1.dsc to pool/main/l/lwm/lwm_1.2.0-1.dsc lwm_1.2.0-1_i386.deb to pool/main/l/lwm/lwm_1.2.0-1_i386.deb lwm_1.2.0.orig.tar.gz to pool/main/l/lwm/lwm_1.2.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted lwm 1.1.5-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 05 Nov 2003 12:33:41 -0500 Source: lwm Binary: lwm Architecture: source i386 Version: 1.1.5-1 Distribution: unstable Urgency: low Maintainer: Matthew Wilcox [EMAIL PROTECTED] Changed-By: Matthew Wilcox [EMAIL PROTECTED] Description: lwm- Lightweight Window Manager Closes: 215193 215194 219063 Changes: lwm (1.1.5-1) unstable; urgency=low . * New maintainer. Closes: #219063 * New upstream version. Closes: #215194 * New upstream location. Closes: #215193 * Repackage, based on William's work. - Replace the manual page with upstream. - Drop support for /usr/sbin/register-window-manager - Bump priority to 80 (20 base + 20 for menu + 40 for EWMH). - Use debhelper v4. - Don't ship INSTALL -- we already did that bit for you. * Standards-Version 3.6.1 * Somewhere, the patch to use x-terminal-emulator got lost. Reinstate it. * Depend on x-terminal-emulator, we do invoke it after all. Files: c04d2b9a63ae843ff9db8dc12b19e193 572 x11 optional lwm_1.1.5-1.dsc 94e356dc7280ae5f708c0771e7328631 44155 x11 optional lwm_1.1.5.orig.tar.gz 451c2adc781801e4dd5f456a586efc00 2805 x11 optional lwm_1.1.5-1.diff.gz 91956c2d1d03fcb57d595890963300a3 32648 x11 optional lwm_1.1.5-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/qTTzIhjIHo58A/8RAh8BAJ4y2Zs0+KjYRQUE2JBVz6V+693wywCgmjzq 9KlwJoWZcoJ9UXwZm2BSsis= =tuAa -END PGP SIGNATURE- Accepted: lwm_1.1.5-1.diff.gz to pool/main/l/lwm/lwm_1.1.5-1.diff.gz lwm_1.1.5-1.dsc to pool/main/l/lwm/lwm_1.1.5-1.dsc lwm_1.1.5-1_i386.deb to pool/main/l/lwm/lwm_1.1.5-1_i386.deb lwm_1.1.5.orig.tar.gz to pool/main/l/lwm/lwm_1.1.5.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
G++ 3.x transition
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wotcha. Those who read deban-devel may remember me announcing http://people.debian.org/~willy/gcc-transition/ about six weeks ago. That generated a certain amount of interest, and indeed activity. Which was great, but it's slacked off a bit recently. So if we want to hit this release goal, it's time to get working on these packages. Since there's over 120 maintainers who have packages that're affected, here's a URL for those with packages that still depend on libstdc++2.10: http://people.debian.org/~willy/gcc-transition/maint-packages-2.95 I know our esteemed Release Manager hasn't published a release schedule for Sarge yet, but some packages can prove problematic and you don't want to be fixing them on a tight schedule. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/OviVIhjIHo58A/8RAuQtAJ9I8OJtOWV2VfYpEbaOeKKwKo3KUQCdHSXk 6aA4TzSf59/sevNMja5l/oY= =7xgC -END PGP SIGNATURE-
G++ 3.2 transition: How're we doing?
badly. http://people.debian.org/~willy/gcc-transition/ i think technically these are all worthy of an RC bug, but i don't want to file them and you don't want to see them. if your name's on the list: http://people.debian.org/~willy/gcc-transition/maint-packages-2.95 then figure out which of your packages needs to be fixed http://people.debian.org/~willy/gcc-transition/src-packages-2.95 and just try recompiling them with gcc 3.3. if they haven't been uploaded in that long, you could probably take the opportunity to update to the latest Standards-Version while you're at it. yeah, this should probably go to d-d-a, but let's see what kind of response this gets. -- It's not Hollywood. War is real, war is primarily not about defeat or victory, it is about death. I've seen thousands and thousands of dead bodies. Do you think I want to have an academic debate on this subject? -- Robert Fisk
Accepted db3 3.2.9-19 (all source ia64)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 16 Jun 2003 12:03:10 -0400
Source: db3
Binary: libdb3++c102 libdb3-util db3-doc libdb3++-dev libdb3-dev libdb3 libdb3-tcl
Architecture: source ia64 all
Version: 3.2.9-19
Distribution: unstable
Urgency: high
Maintainer: Matthew Wilcox [EMAIL PROTECTED]
Changed-By: Matthew Wilcox [EMAIL PROTECTED]
Description:
db3-doc- Berkeley v3 Database Documentation [html]
libdb3 - Berkeley v3 Database Libraries [runtime]
libdb3++-dev - Berkeley v3 Database Libraries for C++ [development]
libdb3++c102 - Berkeley v3 Database Libraries for C++ [runtime]
libdb3-dev - Berkeley v3 Database Libraries [development]
libdb3-tcl - Berkeley v3 Database Libraries for TCL [module]
libdb3-util - Berkeley v3 Database Utilities
Closes: 195049
Changes:
db3 (3.2.9-19) unstable; urgency=high
.
* Update config.{sub,guess}. Closes: #195049
Files:
bce97eaf43bc98950991fdb491bcbbf9 731 libs optional db3_3.2.9-19.dsc
935fb99d7cd4d2f419229b42b519ee8d 46490 libs optional db3_3.2.9-19.diff.gz
8ce1034548e2095901946c995e9f78d2 74028 utils optional libdb3-util_3.2.9-19_ia64.deb
f7469e947d2e7513ea5e291acdc475d6 438358 libs required libdb3_3.2.9-19_ia64.deb
948d8d4575e4741dd3c60da51783a779 560486 devel optional libdb3-dev_3.2.9-19_ia64.deb
fe916192198825e9e930c8318d107143 30146 libs optional libdb3++c102_3.2.9-19_ia64.deb
5ef74d4d4f8e47887db2309d567e6d1b 45626 devel optional libdb3++-dev_3.2.9-19_ia64.deb
8bdafd6e5a16fb1c9527307290887085 493288 interpreters extra
libdb3-tcl_3.2.9-19_ia64.deb
534f0c0b63450952f4e4f289cba8bb38 721696 doc extra db3-doc_3.2.9-19_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE+7fKsIhjIHo58A/8RAvtDAJ9eI7zapgJfdpAkI6rc9FWYQFG9uACePbH2
tkaMpjhUtv8ERxZYAHMdu5I=
=LBtZ
-END PGP SIGNATURE-
Accepted:
db3-doc_3.2.9-19_all.deb
to pool/main/d/db3/db3-doc_3.2.9-19_all.deb
db3_3.2.9-19.diff.gz
to pool/main/d/db3/db3_3.2.9-19.diff.gz
db3_3.2.9-19.dsc
to pool/main/d/db3/db3_3.2.9-19.dsc
libdb3++-dev_3.2.9-19_ia64.deb
to pool/main/d/db3/libdb3++-dev_3.2.9-19_ia64.deb
libdb3++c102_3.2.9-19_ia64.deb
to pool/main/d/db3/libdb3++c102_3.2.9-19_ia64.deb
libdb3-dev_3.2.9-19_ia64.deb
to pool/main/d/db3/libdb3-dev_3.2.9-19_ia64.deb
libdb3-tcl_3.2.9-19_ia64.deb
to pool/main/d/db3/libdb3-tcl_3.2.9-19_ia64.deb
libdb3-util_3.2.9-19_ia64.deb
to pool/main/d/db3/libdb3-util_3.2.9-19_ia64.deb
libdb3_3.2.9-19_ia64.deb
to pool/main/d/db3/libdb3_3.2.9-19_ia64.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
GCC 3.2 transition
I got sick of listening to people discuss the gcc 3.2 transition in an uninformed manner. So I've whipped up a transition plan which will hopefully get us from A to B without causing too much pain. Haha. I'm entirely fallible and I don't pretend to understand all the issues involved with doing the transition. But by writing down a plan at least it can be updated and fixed before we have to start _doing_ the transition. Comments and corrections welcomed. The most up to date version of this document is at http://people.debian.org/~willy/c++transition.html The following is the output from lynx -dump. - The Debian GCC 3.2 Transition Plan This is a proposal. You will be notified when this is a real plan Note! m68k and arm have not yet uploaded gcc-3.2. Until they do, we cannot start this transition! Note! We need to check glibc and binutils work properly with gcc-3.2 on all architectures! Until this is done, we cannot start this transition! Why do we need one? Because GCC 3.2 changed the C++ ABI. You can't mix a C++ library compiled with GCC 3.2 and a C++ application compiled with an earlier version, or vice versa. Transitions are painful. This will be no exception. The rules here are designed to make it as smooth as possible, but it's still going to be unpleasant. We have to do it, we can't stay with g++ 2.95 for ever. This is a proposal. You will be notified when this is a real plan So what're we going to do? * If your package contains no C++, do nothing. One fine day, gcc-defaults will be changed to gcc-3.2 and you'll start using GCC 3.2 with no work by yourself. * If you maintain a library written in C++, add a `c' to the end of the name of your .deb, eg libdb4.0++.deb - libdb4.0++c.deb. This is similar in spirit to the glibc transition adding `g' to the end of libraries. * You should not add a `c' to your -dev package. * The exact placement of the `c' can be tricky. It's not terribly important; the important thing is that the new package conflicts with the old and has a different name. Stylistically, we prefer to keep the `c' adjacent to the soname number, eg libqt3c-mt-odbc, but if your package ends in a ++, put the `c' after that. * Add a Conflict with the non-`c' version of the package. * Ensure that you're using g++-3.2 to build your library (setting CXX in the environment will normally do the trick). * Add a build-dependency on g++-3.2 in your control file (this can be removed after gcc-defaults is changed). * Wait until all your dependencies have been uploaded in `c' versions. * Upload and rejoice! At some point in the future, we will change gcc-defaults to make gcc-3.2 the default on all architectures. At that time, you should remove the setting of CXX and the explicit dependency on g++-3.2. You should not rename your package to remove the `c' suffix until upstream change their soname. This is a proposal. You will be notified when this is a real plan Why don't we just change the sonames? Because upstream chooses the soname to match their API. If we change the soname then we render ourselves binary-incompatible with other distros and vendor-supplied binaries. This is important because the LSB intend to standardise the GCC 3.2 ABI; for Debian to become binary-incompatible at this point would be the height of perversity. Of course, when your upstream does bump the soname, you can drop the `c' from the package name, just like very few libs still have a `g' on the end. How about versioned symbols? Versioned symbols don't even pretend to solve ABI transition problems. Not to mention there's the other-distro compatibility issue -- binaries compiled on Debian would not run on other distros. Why don't we put the libs in a different directory? Basically, it's too complex. For the glibc transition, we could do this because they used different dynamic linkers. What about other architectures? The rules I've outlined above should make the autobuilders build your packages with GCC 3.2. Help! My package doesn't build with GCC 3.2 Typically this is because your package isn't actually written in C++ but some extended subset of it. You may want to talk to upstream about getting it converted. Fortunately, due to hppa using GCC 3.0 for woody, you've probably had a bug filed against your package for at least six months, so this is no surprise to you. If you really can't get your package fixed, you should change to build-depend on g++-2.95. If you depend on a library other than libstdc++ (or libg++), you're not likely to release with sarge. We recommend you statically link to any C++ libraries (other than libg++) which you use. This is a proposal. You will be notified when this is a real
Re: GCC 3.2 transition
On Fri, Aug 16, 2002 at 09:59:28AM -0700, Sean 'Shaleh' Perry wrote: * Add a Conflict with the non-`c' version of the package. why can't we have both installed, just like the libfoo6 and libfoo6g situation?? i explained this elsewhere... Why don't we put the libs in a different directory? Basically, it's too complex. For the glibc transition, we could do this because they used different dynamic linkers. Or can you think of a good way of having them both install without having conflicting files? -- Revolutions do not require corporate support.
Re: GCC 3.2 transition
On Fri, Aug 16, 2002 at 08:38:53PM +0200, Martin v. Loewis wrote: In Jeff's plan: All C++ packages will be uploaded via NMUs. The package maintainer can upload their packages afterwards if they have to make other corrections. All of them? I sw someone do a count and there were around 1000 packages currently in the archive. 10%. Per architecture. Is Jeff really going to bNMU all of these packages on the same day for all architectures? What will that do to auric's disc space and our network traffic? This doesn't sound like a plan, it sounds like the absence of a plan. -- Revolutions do not require corporate support.
Any CAML people want to take over efuns?
Brent Fulgham put efuns up for adoption over a year ago. It's got 3 release critical bugs open against it. I considered adopting it, but as I don't know CAML and don't like emacs, it would be a bad choice. Please, could someone who knows CAML adopt this package and look it over? Otherwise, let's purge it from the archive. It doesn't even build any more on x86: /usr/bin/ocamlc -I ../ocamlsrc/version/include -c options.ml File options.ml, line 113, characters 4-6: Syntax error make[2]: *** [options.cmo] Error 2 -- Revolutions do not require corporate support. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Immutable files
From a security point of view, it might be considered worthwhile to install system executables (particularly the suid ones) and then mark them immutable. This does stop some common attacks from succeeding, and it might prevent some stupid things accidentally done as root. My Debian 1.2.10 system (okay, it was an oldish CD-ROM..) has no files marked as immutable. Has this been considered for the hamm release? -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
