[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#540649: marked as done (adept: Uses an embedded copy of libept.)



Your message dated Wed, 16 May 2012 17:16:37 +0000
with message-id <[🔎] E1SUhq1-00035X-Gn@franck.debian.org>
and subject line Bug#673085: Removed package(s) from unstable
has caused the Debian Bug report #540649,
regarding adept: Uses an embedded copy of libept.
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 owner@bugs.debian.org
immediately.)


-- 
540649: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540649
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: adept
Version: 3.0~beta5
Severity: important
Tags: security

Hi again.

I read:
| Ship internal copy of libept, remove build-depends: libept-dev.

I'm not sure you have a good reason to do so, but I'm pretty sure it
should be documented in a better way than that.

Mraw,
KiBi.



--- End Message ---
--- Begin Message ---
Version: 3.0~beta7.2+qa2+rm

Dear submitter,

as the package adept has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see http://bugs.debian.org/673085

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@debian.org.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)


--- End Message ---

Reply to: