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

Bug#660504: marked as done (O: mnemosyne-blog -- Maildir-to-blog compiler with XML templating and Python extensions)

Your message dated Mon, 09 May 2016 18:16:59 +0000
with message-id <E1azpjn-0005SF-GG@franck.debian.org>
and subject line Bug#823707: Removed package(s) from unstable
has caused the Debian Bug report #660504,
regarding O: mnemosyne-blog -- Maildir-to-blog compiler with XML templating and Python extensions
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.)


-- 
660504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660504
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: normal
X-Debbugs-CC: Decklin Foster <decklin@red-bean.com>

The current maintainer of mnemosyne-blog, Decklin Foster <decklin@red-bean.com>,
is apparently not active anymore.  Therefore, I orphan this package
now.  If you want to be the new maintainer, please take it -- see
http://www.debian.org/devel/wnpp/index.html#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: mnemosyne-blog
Binary: mnemosyne-blog
Version: 0.12-2
Maintainer: Decklin Foster <decklin@red-bean.com>
Build-Depends: debhelper (>= 7), python, python-support (>= 0.5.3)
Architecture: all
Standards-Version: 3.8.0
Format: 1.0
Files: 46c187f0b7a111eabe4108c20de98111 1079 mnemosyne-blog_0.12-2.dsc
 542bbd3c6fffd5c59a3fae050adb6872 16500 mnemosyne-blog_0.12.orig.tar.gz
 62e22bb18fba4c40a46ca2d291c8d147 7627 mnemosyne-blog_0.12-2.diff.gz
Checksums-Sha1: be385bec4b7d96883e6863620526e512fa3b0f1d 1079
mnemosyne-blog_0.12-2.dsc
 5b03f9992be9fe06611ccdfb0915b8b3d4f160ce 16500 mnemosyne-blog_0.12.orig.tar.gz
 b0a951262e91a0222850de4228837dbba8ae61ff 7627 mnemosyne-blog_0.12-2.diff.gz
Checksums-Sha256:
de8cd2c1d4b0ea94699f86d4cf6cc03b911c1896dfb819434dd47838aaa561cb 1079
mnemosyne-blog_0.12-2.dsc
 97ad393ee92670505ef3f9e26283cbd5b8988d2ddf3a4558a3b213c33d2274ab
16500 mnemosyne-blog_0.12.orig.tar.gz
 04f06fe84ed396fe29befe2c1b33359a060a6bae524bdc6f4869b64afa9a95ac 7627
mnemosyne-blog_0.12-2.diff.gz
Homepage: http://www.red-bean.com/decklin/mnemosyne/
Directory: pool/main/m/mnemosyne-blog
Priority: source
Section: web

Package: mnemosyne-blog
Version: 0.12-2
Installed-Size: 104
Maintainer: Decklin Foster <decklin@red-bean.com>
Architecture: all
Depends: python, python-kid
Recommends: python-docutils | python-markdown
Description: Maildir-to-blog compiler with XML templating and Python extensions
Homepage: http://www.red-bean.com/decklin/mnemosyne/
Description-md5: 3b3c81a2087f88d4cdc2e7461b31a39e
Section: web
Priority: extra
Filename: pool/main/m/mnemosyne-blog/mnemosyne-blog_0.12-2_all.deb
Size: 13332
MD5sum: 2c8a84c698a80cb021d7b6fc9833faa7
SHA1: 2869732dfaa2ee0181fe9820475fad9998640876
SHA256: cf1b9d45d7e75dea55063e1d9a568b089577209101715ccafbc51da85d162d87


-- 
Regards,
Aron Xu

--- End Message ---
--- Begin Message --- 
Version: 0.12-3+rm

Dear submitter,

as the package mnemosyne-blog 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 https://bugs.debian.org/823707

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@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---
Reply to: