Accepted libneo4j-client 2.2.0-1 (source) into unstable

Leishman <ch...@leishman.org> Changed-By: Chris Leishman <ch...@leishman.org> Description: libneo4j-client-dev - Development files for libneo4j-client, a client library for Neo4j libneo4j-client-doc - Documentation for libneo4j-client, a client library for Neo4j libneo4j-clien

Accepted libcypher-parser 0.6.0-1 (source) into unstable

Leishman <ch...@leishman.org> Changed-By: Chris Leishman <ch...@leishman.org> Description: cypher-lint - Lint tool for the Cypher query language libcypher-parser-dev - Development files for libcypher-parser libcypher-parser-doc - Documentation for libcypher-parser libcypher-parse

Accepted libneo4j-client 2.1.2-1 (source amd64 all) into experimental, experimental

Maintainer: Chris Leishman <ch...@leishman.org> Changed-By: Chris Leishman <ch...@leishman.org> Description: libneo4j-client-dev - Development files for libneo4j-client, a client library for Neo4j libneo4j-client-doc - Documentation for libneo4j-client, a client library for Neo4j libne

Accepted libcypher-parser 0.5.2-1 (source) into unstable

Leishman <ch...@leishman.org> Changed-By: Chris Leishman <ch...@leishman.org> Description: cypher-lint - Lint tool for the Cypher query language libcypher-parser-dev - Development files for libcypher-parser libcypher-parser-doc - Documentation for libcypher-parser libcypher-parse

Accepted libneo4j-client 1.2.1-1 (source amd64 all) into unstable, unstable

: Chris Leishman <ch...@leishman.org> Changed-By: Chris Leishman <ch...@leishman.org> Description: libneo4j-client-dev - Development files for libneo4j-client, a client library for Neo4j libneo4j-client-doc - Documentation for libneo4j-client, a client library for Neo4j libn

Accepted libcypher-parser 0.5.1-1 (source) into unstable

Leishman <ch...@leishman.org> Changed-By: Chris Leishman <ch...@leishman.org> Description: cypher-lint - Lint tool for the Cypher query language libcypher-parser-dev - Development files for libcypher-parser libcypher-parser-doc - Documentation for libcypher-parser libcypher-parse

Accepted libcypher-parser 0.5.0-1 (source amd64 all) into unstable, unstable

Maintainer: Chris Leishman <ch...@leishman.org> Changed-By: Chris Leishman <ch...@leishman.org> Description: cypher-lint - Lint tool for the Cypher query language libcypher-parser-dev - Development files for libcypher-parser libcypher-parser-doc - Documentation for libcypher-parser libcy

Accepted libneo4j-client 1.1.0-1 (source) into unstable

Leishman <ch...@leishman.org> Changed-By: Chris Leishman <ch...@leishman.org> Description: libneo4j-client-dev - Development files for libneo4j-client, a client library for Neo4j libneo4j-client-doc - Documentation for libneo4j-client, a client library for Neo4j libneo4j-client8 - Cl

Accepted libcypher-parser 0.4.0-1 (source amd64 all) into unstable, unstable

Maintainer: Chris Leishman <ch...@leishman.org> Changed-By: Chris Leishman <ch...@leishman.org> Description: cypher-lint - Lint tool for the Cypher query language libcypher-parser-dev - Development files for libcypher-parser libcypher-parser-doc - Documentation for libcypher-parser libcy

Accepted libneo4j-client 1.0.0-2 (source amd64 all) into unstable, unstable

: Chris Leishman <ch...@leishman.org> Changed-By: Chris Leishman <ch...@leishman.org> Description: libneo4j-client-dev - Development files for libneo4j-client, a client library for Neo4j libneo4j-client-doc - Documentation for libneo4j-client, a client library for Neo4j libneo4j-clie

Accepted libcypher-parser 0.3.4-1 (source amd64 all) into unstable, unstable

Maintainer: Chris Leishman <ch...@leishman.org> Changed-By: Chris Leishman <ch...@leishman.org> Description: cypher-lint - Lint tool for the Cypher query language libcypher-parser-dev - Development files for libcypher-parser libcypher-parser-doc - Documentation for libcypher-parser libcy

Accepted libcypher-parser 0.3.3-1 (source amd64 all) into unstable, unstable

Maintainer: Chris Leishman <ch...@leishman.org> Changed-By: Chris Leishman <ch...@leishman.org> Description: cypher-lint - Lint tool for the Cypher query language libcypher-parser-doc - Documentation for libcypher-parser libcypher-parser3 - Parsing library for the Cypher query language libcy

Accepted libneo4j-client 1.0.0-1 (source all amd64) into unstable, unstable

: Chris Leishman <ch...@leishman.org> Changed-By: Chris Leishman <ch...@leishman.org> Description: libneo4j-client-doc - Documentation for libneo4j-client, a client library for Neo4j libneo4j-client8 - Client library for the Neo4j graph database libneo4j-client8-dev - Devel

Accepted libneo4j-client 0.9.2-1 (source) into unstable

Leishman <ch...@leishman.org> Changed-By: Chris Leishman <ch...@leishman.org> Description: libneo4j-client-doc - Documentation for libneo4j-client, a client library for Neo4j libneo4j-client7 - Client library for the Neo4j graph database libneo4j-client7-dev - Development files for lib

Accepted libneo4j-client 0.9.1-1 (source all amd64) into unstable, unstable

: Chris Leishman <ch...@leishman.org> Changed-By: Chris Leishman <ch...@leishman.org> Description: libneo4j-client-doc - Documentation for libneo4j-client, a client library for Neo4j libneo4j-client7 - Client library for the Neo4j graph database libneo4j-client7-dev - Devel

Bug#813443: ITP: libneo4j-client -- Client library and shell for Neo4j

Package: wnpp Severity: wishlist Owner: Chris Leishman <ch...@leishman.org> * Package name: libneo4j-client Version : 0.7.1 Upstream Author : Chris Leishman <ch...@leishman.org> * URL : https://cleishm.github.io/libneo4j-client/ * License

Accepted libxml++2.6 2.6.1-2 (i386 source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 10 Aug 2004 17:27:06 +1000 Source: libxml++2.6 Binary: libxml++2.6 libxml++2.6-doc libxml++2.6-dev Architecture: source i386 all Version: 2.6.1-2 Distribution: unstable Urgency: low Maintainer: Chris Leishman [EMAIL PROTECTED

Accepted libxml++2.6 2.6.1-1 (i386 source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 10 Sep 2000 17:38:04 +1100 Source: libxml++2.6 Binary: libxml++2.6 libxml++2.6-doc libxml++2.6-dev Architecture: source i386 all Version: 2.6.1-1 Distribution: unstable Urgency: low Maintainer: Chris Leishman [EMAIL PROTECTED

Accepted libxml++ 1.0.4-1 (i386 source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 23 May 2004 17:02:35 +1000 Source: libxml++ Binary: libxml++1.0-doc libxml++1.0-dev libxml++1.0 Architecture: source all i386 Version: 1.0.4-1 Distribution: unstable Urgency: low Maintainer: Chris Leishman [EMAIL PROTECTED

Accepted libxml++ 1.0.3-2 (i386 source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 May 2004 19:24:31 +1000 Source: libxml++ Binary: libxml++1.0-doc libxml++1.0-dev libxml++1.0 Architecture: source all i386 Version: 1.0.3-2 Distribution: unstable Urgency: low Maintainer: Chris Leishman [EMAIL PROTECTED

Accepted xmlrpc-c 0.9.10-4 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 17 Mar 2004 21:50:18 +1100 Source: xmlrpc-c Binary: libxmlrpc-c3-dev libxmlrpc-c3 xml-rpc-api2txt xml-rpc-api2cpp Architecture: source i386 Version: 0.9.10-4 Distribution: unstable Urgency: low Maintainer: Chris Leishman [EMAIL

Accepted libxml++ 1.0.2-2 (i386 source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 16 Mar 2004 01:12:30 +1100 Source: libxml++ Binary: libxml++1.0-doc libxml++1.0-dev libxml++1.0 Architecture: source all i386 Version: 1.0.2-2 Distribution: unstable Urgency: low Maintainer: Chris Leishman [EMAIL PROTECTED

Accepted libxml++ 1.0.2-1 (i386 source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 11 Mar 2004 22:59:32 +1100 Source: libxml++ Binary: libxml++1.0-doc libxml++1.0-dev libxml++1.0 Architecture: source all i386 Version: 1.0.2-1 Distribution: unstable Urgency: low Maintainer: Chris Leishman [EMAIL PROTECTED

Accepted libxml++ 1.0.0-2 (i386 source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 11 Jan 2004 11:06:00 +1100 Source: libxml++ Binary: libxml++1.0-doc libxml++1.0-dev libxml++1.0 Architecture: source all i386 Version: 1.0.0-2 Distribution: unstable Urgency: low Maintainer: Chris Leishman [EMAIL PROTECTED

Accepted libxml++ 1.0.0-1 (i386 source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 6 Jan 2004 10:18:10 +1100 Source: libxml++ Binary: libxml++1.0-doc libxml++1.0-dev libxml++1.0 Architecture: source all i386 Version: 1.0.0-1 Distribution: unstable Urgency: low Maintainer: Chris Leishman [EMAIL PROTECTED

Accepted libxml++ 0.27.0-1 (i386 source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 8 Dec 2003 13:23:31 +1100 Source: libxml++ Binary: libxml++-dev libxml++13 libxml++-doc Architecture: source all i386 Version: 0.27.0-1 Distribution: unstable Urgency: medium (blocking other packages) Maintainer: Chris Leishman

Accepted libxml++ 0.27.0-2 (i386 source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 9 Dec 2003 12:52:17 +1100 Source: libxml++ Binary: libxml++13-dev libxml++13 libxml++13-doc Architecture: source all i386 Version: 0.27.0-2 Distribution: unstable Urgency: low Maintainer: Chris Leishman [EMAIL PROTECTED

Accepted libxml++ 0.28.0-1 (i386 source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 9 Dec 2003 14:32:50 +1100 Source: libxml++ Binary: libxml++14 libxml++14-doc libxml++14-dev Architecture: source all i386 Version: 0.28.0-1 Distribution: unstable Urgency: low Maintainer: Chris Leishman [EMAIL PROTECTED

Accepted xmlrpc-c 0.9.10-3 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 8 Dec 2003 16:47:30 +1100 Source: xmlrpc-c Binary: libxmlrpc-c3-dev libxmlrpc-c3 xml-rpc-api2txt xml-rpc-api2cpp Architecture: source i386 Version: 0.9.10-3 Distribution: unstable Urgency: low Maintainer: Chris Leishman [EMAIL

Accepted libxml++ 0.23.0-1 (i386 source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 06 Jun 2003 16:42:12 +0300 Source: libxml++ Binary: libxml++-dev libxml++-doc libxml++9 Architecture: source i386 all Version: 0.23.0-1 Distribution: unstable Urgency: low Maintainer: Chris Leishman [EMAIL PROTECTED] Changed

security in testing

there needs to be some more thought put into exactly how the withdrawal/replacement of packages occurs, and I think others out there will have a better idea of how that could work than I. Regards, Chris Leishman PGP.sig Description: Binary data

Re: security in testing

On Tuesday, May 13, 2003, at 05:20 PM, Matt Zimmerman wrote: Please get this OFF of debian-private and onto -devel. Quote me anywhere. Redirected thread to debian-devel. If you want to see security updates for 'testing', then start preparing security updates for 'testing'. It does not help to

Re: security in testing

On Wednesday, May 14, 2003, at 11:22 AM, Anthony Towns wrote: snip This isn't possible in general; when mysql has a security problem you can't just tell people to (a) not use it, or (b) just run the unstable/stable version anyway, in spite of whatever reasons they based their decision to use

Re: security in testing

On Wednesday, May 14, 2003, at 06:03 PM, Steve Langasek wrote: snip So, I guess I'll be filing with ftp.d.o to have the vulnerable Samba package removed from testing. And I guess this was the point I was trying to suggest. I feel that if there is no other solution ready (eg. there is no fixed

Re: security in testing

On Wednesday, May 14, 2003, at 08:15 PM, Matthias Urlichs wrote: snip - If the build is successful, it's available for apt-getting from testing-updates; otherwise the maintainer gets a helpful ;-) email. I'm just curious why the updates couldn't just go straight into testing itself. It's not as

Re: security in testing

On Wednesday, May 14, 2003, at 10:02 PM, Matt Zimmerman wrote: snip There is no shortage of opinions about what we should do, but there is unlikely to be any action until an I arises who actually does the work. This has been discussed over and over with the same result each time (i.e., no

Re: security in testing

On Wednesday, May 14, 2003, at 10:57 PM, Michael Stone wrote: snip That assumption is both false and absurd. Testing has exactly two advantages over unstable--1) all dependencies are satisfied and 2) known rc bugs don't propagate to testing. In all other respects unstable is better. (Security

Re: security in testing

On Thursday, May 15, 2003, at 12:36 AM, Matt Zimmerman wrote: snip Removing a package from the archive is not very useful as a security measure. Most users who want the package will already have it installed, and it is those users who are most exposed. It's not unusual for a vulnerability to

Re: security in testing

On Thursday, May 15, 2003, at 12:42 AM, Matt Zimmerman wrote: snip The idea being discussed, as I understand it, is to have fewer security vulnerabilities in 'testing'. The only sane way to accomplish this is to fix the bugs. There has been a disproportionate amount of strategizing around this

Accepted libxml++ 0.21.0-2 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 7 Mar 2003 23:42:53 +0200 Source: libxml++ Binary: libxml++0-dev libxml++0-doc libxml++0 Architecture: source i386 Version: 0.21.0-2 Distribution: unstable Urgency: low Maintainer: Chris Leishman [EMAIL PROTECTED] Changed

Accepted libxml++ 0.20.0-1 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 20 Feb 2003 13:40:00 +0200 Source: libxml++ Binary: libxml++0-dev libxml++0-doc libxml++0 Architecture: source i386 Version: 0.20.0-1 Distribution: unstable Urgency: low Maintainer: Chris Leishman [EMAIL PROTECTED] Changed

Accepted libxml++ 0.21.0-1 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 6 Mar 2003 13:40:00 +0200 Source: libxml++ Binary: libxml++0-dev libxml++0-doc libxml++0 Architecture: source i386 Version: 0.21.0-1 Distribution: unstable Urgency: low Maintainer: Chris Leishman [EMAIL PROTECTED] Changed

Accepted xmlrpc-c 0.9.10-2 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 4 Mar 2003 11:37:12 +0300 Source: xmlrpc-c Binary: libxmlrpc-c3-dev libxmlrpc-c3 xml-rpc-api2txt xml-rpc-api2cpp Architecture: source i386 Version: 0.9.10-2 Distribution: unstable Urgency: low Maintainer: Chris Leishman [EMAIL

Accepted libxml++ 0.16.0-4 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 13 Dec 2002 17:00:30 +0200 Source: libxml++ Binary: libxml++0-dev libxml++0-doc libxml++0 Architecture: source i386 Version: 0.16.0-4 Distribution: unstable Urgency: low Maintainer: Chris Leishman [EMAIL PROTECTED] Changed

Accepted libxml++ 0.16.0-3 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 10 Dec 2002 16:45:30 +0200 Source: libxml++ Binary: libxml++0-dev libxml++0-doc libxml++0 Architecture: source i386 Version: 0.16.0-3 Distribution: unstable Urgency: low Maintainer: Chris Leishman [EMAIL PROTECTED] Changed

Package with non-free build-depends

Hi all, The recently released version of libxml++ (0.16.0) includes doxygen documentation produced from the code (to html), so I created a -doc package for this. However, doxygen wanted to use dot to create some of the images for the documentation. Problem with that is that dot is from the

Re: Package with non-free build-depends

On Mon, Dec 02, 2002 at 01:09:54AM +0100, Matthias Klose wrote: snip Look, if doxygen can be configured for your packages not using dot. Or else include a precompiled version of the docs into your diff file. Adapt your rules in a way, that it can fall back to the precompiled version, if the

Accepted libxml++ 0.16.0-2 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 02 Dec 2002 00:12:30 +0200 Source: libxml++ Binary: libxml++0-dev libxml++0-doc libxml++0 Architecture: source i386 Version: 0.16.0-2 Distribution: unstable Urgency: low Maintainer: Chris Leishman [EMAIL PROTECTED] Changed

Accepted libxml++ 0.16.0-1 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Nov 2002 21:51:43 +0200 Source: libxml++ Binary: libxml++0-dev libxml++0-doc libxml++0 Architecture: source i386 Version: 0.16.0-1 Distribution: unstable Urgency: low Maintainer: Chris Leishman [EMAIL PROTECTED] Changed

Accepted libxml++ 0.13-9 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 16 Oct 2002 19:18:43 +0300 Source: libxml++ Binary: libxml++0-dev libxml++0 Architecture: source i386 Version: 0.13-9 Distribution: unstable Urgency: low Maintainer: Chris Leishman [EMAIL PROTECTED] Changed-By: Chris Leishman

Accepted xmlrpc-c 0.9.9-5 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 5 Aug 2002 14:51:22 +0300 Source: xmlrpc-c Binary: libxmlrpc-c3-dev libxmlrpc-c3 xml-rpc-api2txt xml-rpc-api2cpp Architecture: source i386 Version: 0.9.9-5 Distribution: unstable Urgency: low Maintainer: Chris Leishman [EMAIL

Accepted libxml++ 0.13-7 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 28 Aug 2002 12:59:43 +0300 Source: libxml++ Binary: libxml++0-dev libxml++0 Architecture: source i386 Version: 0.13-7 Distribution: unstable Urgency: low Maintainer: Chris Leishman [EMAIL PROTECTED] Changed-By: Chris Leishman

Re: make mutt the `standard' mail reader

On Sat, Jan 16, 1999 at 10:26:06PM +1100, Craig Sanders wrote: On Sat, Jan 16, 1999 at 02:36:47AM -0500, Branden Robinson wrote: On Sat, Jan 16, 1999 at 06:10:09PM +1100, Hamish Moffatt wrote: Well, maybe. I find config menus to be infuriating. elm's config files don't seem to have an

Re: something is f***ed

On Sat, Oct 17, 1998 at 06:07:17PM -0500, Stephen Crowley wrote: Ok, i just apt-get upgraded about an hour ago, to my horror i can no longer login, nor can I su, it just sits there doing nothing. I also cannot telnet to localhost. Someone on irc just upgraded also and got the exact same

pgp = gpg

Hi all, At the moment I am using pgp2i, but I would like to try and change to gnupg. My question is - will I need to generate a new public/private key, or is it possible to use my pgp one with gnupg? I would really prefer to keep my old one, as otherwise I'll have to distribute a new key, not

Bug with xv?

Hi all, I was just working away on my machine, and using xv to display the latest results from my raytracing project. The pic came out too small, and so I went to press shift '' to zoom it up, only I missed and hit shift ''. Low and behold my xserver crashed. I've since tested and found that

shutdown and X

Hi, I just noticed that when my machine gets shut down cleanly, and there was an open X session (which gets terminated), the words crash get inserted into the wtmp, utmp or lastlog (whichever last uses) instead of the normal log out time. Does anyone else experience this? Is it a bug or a

Re: Ropes in stl (was Re: lack of wstring in libstdc++2.8-dev)

On Mon, Oct 12, 1998 at 08:24:49AM +0100, M.C. Vernon wrote: void main(void) snippety BTW, main returns int, not void. See the comp.lang.c FAQ for the bit of the C standard that defines this - main is incorrectly said to return void in a number of texts though. HTH, Matthew