|
Hello Vincent, I have uploaded a new manually packed tarball of the Bzr trunk, with version 1.0.3+bzr152-1 instead of the +14.04.20140109 Ubuntu had in its repository. I didn't make that clear, but a bad version number could accidentally replace the package they have AFAIK. As for the package truly being orphaned, I assume that the people who filed the report already knew what was going on. The LDAP database didn't find anything for Karolina Kalic or karolina@resenje.org, and the package has been orphaned for almost 2 years now. Two of their packages appear to have new maintainers already (curtain and spotlighter). Either way, I'll Cc them on this conversation now. I'm not sure what has been done already, and what still has to be done. Best, James On 12/05/2015 1:09 AM, Vincent Cheng
wrote:
Control: tag -1 + moreinfo Hi James, On Sun, May 10, 2015 at 11:52 AM, James Lu <GLolol1@hotmail.com> wrote:Hi, Okay. Forget what I said about quilt, I don't think it'd fix this particular issue either. Right now, the problem is in the original source (aka the .orig.tar). The INSTALL file isn't even installed in the final binary, but just having a symlink in the original source is enough to make Lintian complain. Adding a debian/clean file only removes the INSTALL file from the extracted tree, but not the .orig.tar.gz. I could add a Lintian override if this is appropriate.Just from what you've said above, I'd ignore the lintian error entirely; if INSTALL is never used during the build process or installed into any of the binary packages produced by your source package, then source-contains-unsafe-symlink is quite harmless. It _is_ a valid lintian error though, since the orig tarball upstream presumably contains an INSTALL file symlinked above the root of the source package, and removing it via debian/clean doesn't change that. Where did you obtain this orig tarball? I can't seem to find a tarball versioned as 1.0.3+14.04.20140109 at [1]; if you actually are rolling your own tarball instead of using one provided upstream, then why not get rid of that symlink in your tarball? Also, this may seem to be a formality, but is this package actually orphaned? Neither the maintainer nor the MIA team filed #717044; a random user deciding to ITA the package out of the blue is more or less "hijacking" the package. Please follow the steps outlined in devref 5.9.4/5.9.5 [2] to properly orphan a package and adopt it. Regards, Vincent [1] https://launchpad.net/unico [2] https://www.debian.org/doc/manuals/developers-reference/pkgs.html#orphaning |