Accepted c2html 0.9.5-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 30 Oct 2002 11:16:05 -0600 Source: c2html Binary: c2html Architecture: source i386 Version: 0.9.5-1 Distribution: unstable Urgency: low Maintainer: Ashley Clark [EMAIL PROTECTED] Changed-By: Ashley Clark [EMAIL PROTECTED] Description: c2html - Highlight C sources for WWW presentation Closes: 161228 164183 Changes: c2html (0.9.5-1) unstable; urgency=low . * New upstream version. * Standards Version: 3.5.7 * Eliminate extra lines when blocks have CRLF line terminators. Closes: #164183 * Adds options to configure tabsize and number all lines. Closes: #161228 Files: 8991886cb8c6509ebd220517f4fdf5d3 602 web optional c2html_0.9.5-1.dsc 324cd6c50dd611607e3366840bbc61f2 55326 web optional c2html_0.9.5.orig.tar.gz 4b627aaf6e524053029291a6d9c53c77 2356 web optional c2html_0.9.5-1.diff.gz cd6d4b91cf97ce7650488e22c77b4a97 75602 web optional c2html_0.9.5-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Finger [EMAIL PROTECTED] for public key iD8DBQE9wLqk/GKzBErg8u4RAp3hAJ4ybG0VxETPlYLLHmZBsYobbXx6cACeKrFu zQXmRVII3VEWQ4lkP8gOxU4= =uQmw -END PGP SIGNATURE- Accepted: c2html_0.9.5-1.diff.gz to pool/main/c/c2html/c2html_0.9.5-1.diff.gz c2html_0.9.5-1.dsc to pool/main/c/c2html/c2html_0.9.5-1.dsc c2html_0.9.5-1_i386.deb to pool/main/c/c2html/c2html_0.9.5-1_i386.deb c2html_0.9.5.orig.tar.gz to pool/main/c/c2html/c2html_0.9.5.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp: ITP: gq - gtk ldap client
* Ond?ej Sur? in wnpp: ITP: gq - gtk ldap client dated 2001/04/27 * 09:48 wrote: Package: wnpp Version: N/A Severity: wishlist GQ is a GTK-based LDAP client. Features include: What's wrong with the current gq package? $ apt-cache show gq Package: gq Priority: optional Section: net Installed-Size: 281 Maintainer: Cord Beermann [EMAIL PROTECTED] Architecture: i386 Version: 0.4.0-1 Depends: libc6 (= 2.2.1), libglib1.2 (= 1.2.0), libgtk1.2 (= 1.2.8-3), libldap2 (= 2.0.2-2), xlibs (= 4.0.1-11) Filename: pool/main/g/gq/gq_0.4.0-1_i386.deb Size: 93850 MD5sum: ee802c5db7cce9d582a67c4d9caad234 Description: GTK-based LDAP client GQ is GTK+ LDAP client and browser utility. It can be used for searching LDAP directory as well as browsing it using a tree view. Features include: - browse and search modes - LDAPv3 schema browser - template editor - edit and delete entries - add entries with templates - export subtree or whole server to LDIF file - use any number of servers - search based on single argument or LDAP filter - TLS support for LDAPv3 -- creaky halls pgp3gUeJ3892i.pgp Description: PGP signature
Re: Strange messages...
* Dale Scheetz in Strange messages... dated 2000/08/30 04:17 wrote: Since my last upgrade to potato I've been getting a lot of messages like the following: DEBUG: --Relation pg_rules-- DEBUG: Pages 0: Changed 0, Reapped 0, Empty 0, New 0; Tup 0: Vac 0, Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen 0, MaxLen 0; Re-using: Free/Avail. Space 0/0; EndEmpty/Avail. Pages 0/0. Elapsed 0/0 sec. [snip] There doesn't seem to be any real information here. Can anyone tell me what is triggering these messages? They are courtesy of PostgreSQL, the behaviour of the config file has changed between two of the versions. You can add PGDEBUG=0 to your /etc/postgresql/postmaster.init file and they will disappear. -- hackers ally pgpnMLidb4d2b.pgp Description: PGP signature
Re: [OT] logcheck and fetchnews
* Andreas Tille in [OT] logcheck and fetchnews dated 2000/08/21 14:05 * wrote: Hello, sorry for posting this to devel but I failed while asking other lists. I just want to make sure that it is a bug of logcheck and not my own before I file a bug-report: ...snip... Seems strange why I did define some rules which are stronger than others but they are just all my trials which failed to block the following messages. I hoped that the first rule should have deleted all fetchnews entries but I continueally get the follwoing type of messages: Security Violations =-=-=-=-=-=-=-=-=-= Aug 21 11:03:39 wr-linux02 fetchnews[19687]: illegal article: /var/spool/news/interbase/public/general/1096: Illegal seek Aug 21 11:03:39 wr-linux02 fetchnews[19687]: illegal article: /var/spool/news/interbase/public/general/1097: Illegal seek Aug 21 11:03:39 wr-linux02 fetchnews[19687]: illegal article: /var/spool/news/interbase/public/kinobi/jdbc-odbc-oledb/54: Illegal seek Aug 21 11:03:39 wr-linux02 fetchnews[19687]: illegal article: /var/spool/news/mers/interbase/list/1147: Illegal seek Could anybody help me out of this boring messages? Is this a bug of logcheck? No, just someone who didn't read the documentation. You need to create lines to ignore violations in logcheck.violations.ignore, if you'd read the documentation in /usr/share/doc/logcheck though you'd know that. Check INSTALL.gz and it clearly defines the purpose of each of the files in the /etc/logcheck hierarchy. -- shaky cellar pgp17bW84HEO4.pgp Description: PGP signature
Re: possible problem with new perl, libc6 on Sep 23rd
On Fri, 24 Sep 1999, Branden Robinson wrote: [1] 1013 apocalypse ~ ls -dl /usr/bin/perl lrwxrwxrwx 1 root root 10 Sep 23 22:02 /usr/bin/perl - perl-5.005 [0] 1014 apocalypse ~ ls -dl /usr/bin/perl-5.005 -rw--- 1 root root 534844 Aug 19 04:29 /usr/bin/perl-5.005 I had this same problem upgrading my system last night. I manually chmod'ed the perl executable and finished configuring. Probably would have been safer to change the link in /etc/alternatives though to the old perl which was still on my system. Strange. -- Ashley Clark
Re: sash
On Wed, 22 Sep 1999, Taketoshi Sano wrote: In article [EMAIL PROTECTED] [EMAIL PROTECTED] (Raul Miller) writes: I think you should just use useradd to edit the password file. You mean without ensuring that the password is useful? I've already elected to give the admin a choice (whether or not to add the account -- that'll be in the next release). The problem with password prompting is that it doesn't fit well into an automated or gui install. Under these circumstances do you still feel it's useful to add a locked account? How about to include following small script (maybe /sbin/sashpasswd with permission 0700 or 0744): #! /bin/sh PATH=/usr/bin passwd root passwd sashroot Couldn't sash include a PAM module that would change the password to match root's password whenever it was changed? Or am I oversimplifying things? -- Ashley Clark
