[Pkg-crosswire-devel] [RFS] sword-1.6.1+dfsg-1

[Dmitrijs Ledkovs]

2010/1/22 Jonathan Marsden <jmarsden at fastmail.fm>:
> Roberto C. Sánchez wrote:
>
>>>>> W: sword source: debian-watch-file-should-mangle-version line 2
>
>>>> Thanks for doing these uploads Roberto. I appreciate it so the next
>>>> comment is meant to be constructive criticism as I didn't get to doing
>>>> it myself. But it would be helpful if you could fix these bugs in the
>>>> package you upload and supply a patch to the list, or apply it to the
>>>> repo yourself.
>
> I can look at this, it shouldn't be this hard to get a watch file
> straight.  We add the +dfsg in the package name, so we just need to
> mangle it back out again in the watch file.
>

Already done on launchpad =) See commit mail.

> Thanks to Dmitry for doing this work in the first place; I saw the msg
> asking if I had time... as you can see, I didn't!  I've been busy at
> work and sick with bronchitis, not a good combination.  Bronchitis is
> now "almost" gone, I hope and pray it goes completely and stays away!
>

Well I found some time and did stuff =)

>> Did you also the override disparity email?  That probably ought to be
>> corrected as well.  However, you need to decide whether you want to file
>> a bug asking for the override file to be changed, or whether you want to
>> change the package's control file to match the override.
>
> My two cents and a little history: the diatheke package we inherited was
> web, because it installed the diatheke.cgi.  We stopped installing that,
> except as an example, I think because it had security issues.  So the
> current package is now text, and the section override should (as I
> understand it) therefore be changed to text.  I have a feeling I asked
> about that, back when we first did it, and someone suggested it would be
> sorted out by the archive admins??  Seems like that's not quite the
> case, and we now need to be proactive about sorting this out.
>

I did just now file a request. It should have been forwarded to the
mailing. It failed, now manually forwarded.


> General principle: If anyone gets a package to the point where it works
> but has lintian warnings they know about, IMO it's probably best to post
> to this list saying "how do I get rid of these N warnings?" rather than
> doing an RFS with known warnings left in it.  I'm not perfect in this
> regard myself (sometimes I get things lintian-clean in Ubuntu but not
> Debian sid, for instance)... let's all try to improve on this, and not
> ask sponsors to sponsor things that are "unclean" unless there is a real
> time crunch.
>
> Jonathan
>

Well I was more concerned about Debian Import Freeze for Lucid, which
is on February 11. And the package still needs at least 10 days time
to transition to Testing plus I was afraid we will get stuck behind
some other library transition.


-- 
With best regards


Dmitrijs Ledkovs (for short Dima),
Ледков Дмитрий Юрьевич

()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments