Processing of guymager_0.5.9-3_amd64.changes

2012-01-14 Thread Debian FTP Masters
guymager_0.5.9-3_amd64.changes uploaded successfully to localhost
along with the files:
  guymager_0.5.9-3.dsc
  guymager_0.5.9-3.debian.tar.gz
  guymager_0.5.9-3_amd64.deb

Greetings,

Your Debian queue daemon (running on host franck.debian.org)

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel


Bug#652170: new libprocps0 package

2012-01-14 Thread Julien Valroff
Le mercredi 11 janv. 2012 à 23:50:12 (+0100 CET), Craig Small a écrit :
 Hello,
   Apologies for the rough ride around the libprocps library change.
 The latest procps now has split out the shared library into its own
 package.  This should mean that there is less of this problem in future.
 You will need to download libprocps0-dev and re-link the program to
 -lprocps. There is also a pkg-config file if you need that.
 
 I've tested it with xmem and it builds fine with 2 small changes.
 
 In future, there will be a large API change but that will be in a new
 library version package so it won't be like the programs suddenly stop
 working like before.

Thanks Craig for your work, I have just built guymager against
libprocps0-dev and uploaded it to the archive.

Cheers,
Julien

-- 
  .''`.   Julien Valroff ~ jul...@kirya.net ~ jul...@debian.org
 : :'  :  Debian Developer  Free software contributor
 `. `'`   http://www.kirya.net/
   `- 4096R/ E1D8 5796 8214 4687 E416  948C 859F EF67 258E 26B1



___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

guymager_0.5.9-3_amd64.changes ACCEPTED into unstable

2012-01-14 Thread Debian FTP Masters



Accepted:
guymager_0.5.9-3.debian.tar.gz
  to main/g/guymager/guymager_0.5.9-3.debian.tar.gz
guymager_0.5.9-3.dsc
  to main/g/guymager/guymager_0.5.9-3.dsc
guymager_0.5.9-3_amd64.deb
  to main/g/guymager/guymager_0.5.9-3_amd64.deb


Override entries for your package:
guymager_0.5.9-3.dsc - source utils
guymager_0.5.9-3_amd64.deb - optional utils

Announcing to debian-devel-chan...@lists.debian.org


Thank you for your contribution to Debian.

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel


Bug#654583: WARNING: gnome-keyring:: no socket to connect to

2012-01-14 Thread Julien Valroff
reassign 654583 gnome-keyring
thanks

Hi,

Le mercredi 11 janv. 2012 à 14:51:32 (+0100 CET), Teodor MICU a écrit :
 2012/1/10 Julien Valroff jul...@debian.org:
  So, on Jan 08 it appeared on two jobs (00logwatch and apt). I'm
  undecided to which package to reassign: cron or gnome-keyring? What do
  you think?
 
  What happens if you run such a cron job by hand when not in an X session?
 
 Today I watched the Cron run without X/gnome/gdm running at all. The
 result was the same:
 
 # Date: Wed, 11 Jan 2012 07:34:27 +0200
 /etc/cron.daily/00logwatch:
 WARNING: gnome-keyring:: no socket to connect to
 
  I have never seen this behaviour, maybe you have any specific configuration?
 
 I don't think so. On all systems (desktops, servers) I have 'ssmtp' to
 provide the 'sendmail' interface, thus no SMTP daemon. One think I've
 noticed a few days ago is that something was changing the hostname
 from the FQDN (frost.DOMAIN -- set from /etc/hostname) to just 'frost'
 but I didn't investigate further.
 
 Also, today I obtained this message while doing packages upgrades:
 | Processing triggers for man-db ...
 | Processing triggers for menu ...
 | Processing triggers for desktop-file-utils ...
 | Processing triggers for gnome-menus ...
 | Processing triggers for hicolor-icon-theme ...
 | Processing triggers for cups ...
 | Starting Common Unix Printing System: cupsd.
 | WARNING: gnome-keyring:: no socket to connect to
 | WARNING: gnome-keyring:: no socket to connect to
 | Updating PPD files for postscript-hp ...
 | Updating PPD files for splix ...
 | Processing triggers for gconf2 ...
 
 Usually this warning appears on the email from Cron. Other ideas?

No idea on my side but given your answers, it seems this is an issue with
gnome-keyring, I hence reassign this bug to the appropriate package.

Cheers,
Julien

-- 
  .''`.   Julien Valroff ~ jul...@kirya.net ~ jul...@debian.org
 : :'  :  Debian Developer  Free software contributor
 `. `'`   http://www.kirya.net/
   `- 4096R/ E1D8 5796 8214 4687 E416  948C 859F EF67 258E 26B1



___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel

Processed: Re: Bug#654583: WARNING: gnome-keyring:: no socket to connect to

2012-01-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reassign 654583 gnome-keyring
Bug #654583 [rkhunter] WARNING: gnome-keyring:: no socket to connect to
Bug reassigned from package 'rkhunter' to 'gnome-keyring'.
Bug No longer marked as found in versions rkhunter/1.3.8-10.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
654583: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel