Your message dated Thu, 17 Apr 2014 19:41:48 +0000
with message-id <[email protected]>
and subject line Bug#743295: Removed package(s) from unstable
has caused the Debian Bug report #613715,
regarding vdkxdb2: should this package be orphaned? invasive NMU proposed
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.)


-- 
613715: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613715
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: vdkxdb2
Version: 2.4.0-3.1
Severity: Important

During my NM process, I picked this package to do some QA work on to
demonstrate packaging ability. Evaluating the package, I found that
this package needs work:

* removed from testing for RC bugs
* 1 Lintian error 15 warnings
* new upstream release
* Not touched by maintainer since 2005 (NMU in 2009, removed from
testing in 2010)

This package also has a low popcon, and is not in squeeze, so we
probably shouldn't put too much time into this, but since I've already
done the work it would be trivial to apply it. I have a proposed NMU
at [1] on the 29th of Nov 2010 [2] which does the following:

  * dh 7 build system to use dh-autoreconf (Closes: #327894)
    - Build system now finds cairo (Closes: #356872)
  * Lintian fixing:
    - E: removed empty manpage
    - W: Updated debian/copyright
    - W: moved libvdkxdb2.so to -dev package
    - W: Debian Policy 3.9.1
    - W: added misc:Depends to debian/control
    - W: dh 7 fixes clean errors
    - W: dh 7 removes call to dh_undocumented
    - W: added source section:libs to debian/control
    - W: debian/compat changed for version 7
    - W: use {binary:Version} in debian/control instead of {Source-version}

Feel free to use any of that if you wish to continue maintaining the software.

If you feel the package should be orphaned, send the following commands
to [email protected] (replace nnnnnn with this bug's number):

severity nnnnnn normal
reassign nnnnnn wnpp
retitle nnnnnn O: <packagename> -- <short package description>
thanks

If you think it should be removed, send the following commands instead:

severity nnnnnn normal
reassign nnnnnn ftp.debian.org
retitle nnnnnn RM: <packagename> -- RoM; <reasons>
thanks


Otherwise I will post the NMU diff and go ahead with that.

Regards,
Scott

[1] 
http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=vdkxdb2
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=327894



--- End Message ---
--- Begin Message ---
Version: 2.4.0-3.4+rm

Dear submitter,

as the package vdkxdb2 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/743295

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
[email protected].

Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to