Your message dated Thu, 24 Sep 2009 12:39:33 +0200
with message-id <[email protected]>
and subject line Re: Bug#528630: depends on libevent1 which is unavailable
has caused the Debian Bug report #528630,
regarding depends on libevent1 which is unavailable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
528630: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528630
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: scanssh
Version: 2.0-4+b1
Severity: serious

Hi,

scanssh depends on libevent1 package which is unavailable.

Regards,
Raf

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: powerpc (ppc)

Kernel: Linux 2.6.29-2-powerpc
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages scanssh depends on:
ii  libc6                         2.9-12     GNU C Library: Shared libraries
ii  libdumbnet1                   1.8-2      A dumb, portable networking librar
ii  libevent1                     1.3e-3     An asynchronous event notification
ii  libpcap0.8                    1.0.0-1    system interface for user-level pa

scanssh recommends no packages.

scanssh suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Version: 2.0-4+b2

Hi,

scanssh was rebuild against the new libevent library:

scanssh (2.0-4+b2) unstable; urgency=low

  * Binary-only non-maintainer upload for powerpc; no source changes.
  * Rebuild against new libevent.

 -- PPC Build Daemon <[email protected]>  Fri, 22 May 
2009 06:56:29 +0000

Regards,
Ansgar


--- End Message ---

Reply via email to