Bug#925200: missing warning for wrong path

2019-03-21 Thread Osamu Aoki
ce/help Then use this new path for doc-base. PS sixerjman: I think your concern is addressed with lintian now. >From 30479d72937d84fbd501f2f61d40cb1169cb35bd Mon Sep 17 00:00:00 2001 From: Osamu Aoki Date: Thu, 21 Mar 2019 20:43:22 +0900 Subject: [PATCH 1/1] Add check for doc-base-file-referenc

Bug#925200: doc-base-file-references-missing-file: false positive and missing warning when symlinks are involved

2019-03-20 Thread Osamu Aoki
Package: lintian Version: 2.11.0 Severity: normal Requested action for /usr/share/lintian/checks/menus.pm: * add feature to "delink" to follow relative symlink --> /usr/share/lintian/checks/menus.pm around line 566-592 rela

Bug#505857: tagging 505857

2018-01-12 Thread Osamu Aoki
control: tags 505857 - pending thanks Osamu

Bug#505857: lintian: false positive debian-watch-file-should-mangle-version

2018-01-12 Thread Osamu Aoki
Hi, Bug: https://bugs.debian.org/505857 https://bugs.debian.org/884880 (cloned bug of above) I just updated manpage of uscan to reduce stress of our fellow DDs for Bug #884880. I agree with > 3.- Long term solution: > Turn some portions of uscan into a perl module[1] and use it to extract the

Re: debian/upstream/signing-key.asc in policy 4.1.0

2017-08-28 Thread Osamu Aoki
Hi, On Sun, Aug 27, 2017 at 08:51:49PM -0300, Henrique de Moraes Holschuh wrote: > On Wed, 23 Aug 2017, Russ Allbery wrote: > > Note that this Policy language is carefully written to make it perfectly > > fine for uscan to support all the things it currently supports, since it > > only talks about

Re: debian/upstream/signing-key.asc in policy 4.1.0

2017-08-27 Thread Osamu Aoki
Oops. On Sun, Aug 27, 2017 at 12:55:26AM +0900, Osamu Aoki wrote: > Hi, > > On Wed, Aug 23, 2017 at 09:27:25AM -0700, Russ Allbery wrote: > > Osamu Aoki writes: > > > The updated uscan will support debian/upstream/signing-key.asc only and > > > internally con

Re: debian/upstream/signing-key.asc in policy 4.1.0

2017-08-26 Thread Osamu Aoki
Hi, On Wed, Aug 23, 2017 at 09:27:25AM -0700, Russ Allbery wrote: > Osamu Aoki writes: > > The updated uscan will support debian/upstream/signing-key.asc only and > > internally convert it /signing-key.gpg. I will make uscan to > > convert other formats to this policy c

debian/upstream/signing-key.asc in policy 4.1.0

2017-08-23 Thread Osamu Aoki
Hi, After all the discussion, Policy 4.1.0 goes as: | 4.11. Optional upstream source location: debian/watch¶ | | This is an optional, recommended configuration file for the uscan | utility which defines how to automatically scan ftp or http sites for | newly available updates of the package. Thi

Bug#833585: lintian: Check presence of upstream signature if signing key available

2017-08-21 Thread Osamu Aoki
Hi, (This is RFH) On Mon, Aug 21, 2017 at 09:43:13AM +0200, Kurt Roeckx wrote: > On Mon, Aug 21, 2017 at 09:30:41AM +0200, Vincent Bernat wrote: > > ❦ 15 juillet 2017 23:06 +0100, Chris Lamb  : ... > > Integration with uscan is not done either. The stretch uscan has download and verification inc

Re: Upstream Tarball Signature Files

2017-08-19 Thread Osamu Aoki
Hi, On Fri, Aug 18, 2017 at 12:02:27PM +0200, Guillem Jover wrote: .. > Adding support for more signature formats or filename variations is > not hard, but it increases the amount of those extensions and perhaps > the additional sanity checks we have to support and perform on them on > multiple t

How to handle upstream tarbell signature

2017-08-19 Thread Osamu Aoki
Hi, I was trying to update uscan and realized few problems which are not addressed by the discussion here. There are many things to consider. On Fri, Aug 18, 2017 at 02:43:58PM +0200, Mattia Rizzolo wrote: > On Fri, Aug 18, 2017 at 07:48:24AM -0400, Daniel Kahn Gillmor wrote: > > I confess that

Re: Upstream Tarball Signature Files

2017-08-18 Thread Osamu Aoki
Hi, On Fri, Aug 18, 2017 at 12:08:02PM +0200, Guillem Jover wrote: > Hi! > > On Wed, 2017-08-16 at 00:22:43 -0700, Paul Hardy wrote: > > On Tue, Aug 8, 2017 at 1:48 AM, Guillem Jover wrote: > > > On Mon, 2017-08-07 at 20:26:41 -0700, Paul Hardy wrote: > > > > Also, where signature files are desi

Re: Upstream Tarball Signature Files

2017-08-15 Thread Osamu Aoki
Hi, On Mon, Aug 14, 2017 at 10:13:10AM -0700, Russ Allbery wrote: > Henrique de Moraes Holschuh writes: > > > We do when the binary sig is small enough to be stored along with the > > inode, instead of requiring an entire filesystem block (4KiB), and the > > armored signature is not small enough

Bug#743532: lintian: when to say: old-fsf-address-in-copyright-file

2014-04-05 Thread Osamu Aoki
Hi, On Thu, Apr 03, 2014 at 06:45:25PM +0200, Jakub Wilk wrote: > * Osamu Aoki , 2014-04-04, 01:16: > >License: GPL-2.0+ with incorrect FSF address, and with autoconf exception > > FWIW, this line does not conform to the copyright format specification. What is the offending part

Bug#743532: lintian: when to say: old-fsf-address-in-copyright-file

2014-04-03 Thread Osamu Aoki
Package: lintian Version: 2.5.22.1 Severity: normal Please do not make lintian report this warning of W: old-fsf-address-in-copyright-file if the license synopsis line has "with incorrect FSF address". Here is an example. Lintian reports as: W: ... old-fsf-address-in-copyright-file for debian/c

Bug#733733: wrong complaint about missing python b-d when python*:any is given.

2014-01-16 Thread Osamu Aoki
Package: lintian Version: 2.5.21 Followup-For: Bug #733733 lintian is confused by additional ":any" added to the package name of dependency check logic. Please allow additional ":any" to be added. Here is my case: After realizing python3-all is one of the few new M-A:allowed packages, I put pyt

Bug#708138: lintian: python-script-but-no-python-dep should accept python3.3

2013-05-18 Thread Osamu Aoki
On Sat, May 18, 2013 at 03:58:48PM +0200, Jakub Wilk wrote: > * Jakub Wilk , 2013-05-17, 19:05: > >>override_dh_auto_install: > >> set -ex; for python in $(PYTHON3); do \ > >> $$python setup.py install \ > >> --root=debian/debmake\ > >> --install-layout=deb; \

Bug#708138: lintian: python-script-but-no-python-dep should accept python3.3

2013-05-17 Thread Osamu Aoki
Hi, I am a bit sick today ... but I got around fixing issues in VCS and build again: I attach its build log as xz. debmake_4.0.0-2_amd64.build.xz Description: Binary data

Bug#708138: lintian: python-script-but-no-python-dep should accept python3.3

2013-05-14 Thread Osamu Aoki
Hi, Excuse me, I did not put this to alioth yet. On Mon, May 13, 2013 at 04:25:59PM +0200, Jakub Wilk wrote: ... > If you showed me the source package, I'd try to explain why that > happened. (I tried to use links from Vcs-* fields for the package > that is in NEW, but they are broken.) Hmmm...

Bug#708138: lintian: python-script-but-no-python-dep should accept python3.3

2013-05-13 Thread Osamu Aoki
Package: lintian Version: 2.5.10.4 Severity: normal This may be somewhat similar to bug#673734. I had script started as: #!/usr/bin/python3 The python3 setup.py with dh --with python3 seems to convert this to: #! /usr/bin/python3.3 (Please note space.) I guess, it substitute with the current de

Bug#659574: lintian: legally wrong statement: copyright-with-old-dh-make-debian-copyright

2012-02-13 Thread Osamu Aoki
Hi, Thanks for your quick response. In retrospect, my initial bug report may have had some skewed view on the copyright law since Japan being more like French law on this subject. I still think that this lintian report is *pedantic* to nitpick on one requirement and misses other requirements. L

Bug#659574: lintian: legally wrong statement: copyright-with-old-dh-make-debian-copyright

2012-02-12 Thread Osamu Aoki
Package: lintian Version: 2.5.4 Severity: important Tags: patch Summary: copyright-with-old-dh-make-debian-copyright is giving a legally incorrect statement to lintian users in very annoying way. It is best removed immediately. -p0 patch attached. Explanation: copyright-with-old-dh-make-debian

Bug#613002: lintian: Please convert SGML to DocBook XML

2011-02-11 Thread Osamu Aoki
Package: lintian Version: 2.4.3 Severity: wishlist User: debian-...@lists.debian.org Usertags: docbook-xml-transition Please consider to convert document to DocBook XML using debiandoc2dbk command in the upcoming debiandoc-sgml package in wheezy. I think working on this later after the release

Bug#575661: [checks/manpages] manpage-has-errors for multibyte issue on col must be skipped?

2010-07-24 Thread Osamu Aoki
tags 575661 moreinfo thanks Hi, It looks like you reopened this bug originally filed by me. It felt to me this my bug is closed in my environment. (I must confess I did not do much test...) For people wondering, please see the URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=55;bug=5756

Bug#575661: lintian: Fix to col command error

2010-04-10 Thread Osamu Aoki
On Sat, Apr 10, 2010 at 07:43:39AM -0700, Russ Allbery wrote: > Osamu Aoki writes: > > > Since this test should work in all environment, I think whoever created > > this test must have chosen LANG=C with reason. I am not even sure if > > en_US.UTF-8 exists in the test e

Bug#575661: lintian: Fix to col command error

2010-04-10 Thread Osamu Aoki
On Sat, Apr 10, 2010 at 08:15:57AM -0700, Russ Allbery wrote: > Osamu Aoki writes: > > On Sat, Apr 10, 2010 at 07:43:39AM -0700, Russ Allbery wrote: > > >> My understanding of how man is supposed to work with character > >> encodings says that we should not nee

Bug#575661: lintian: Fix to col command error

2010-04-10 Thread Osamu Aoki
Package: lintian Version: 2.3.4 Severity: normal Tags: patch Since this test should work in all environment, I think whoever created this test must have chosen LANG=C with reason. I am not even sure if en_US.UTF-8 exists in the test environment. Then I also realized there are manpages in many ol

Bug#575661: lintian: manpage-has-errors-from-man "Invalid or incomplete multibyte or wide character" when OK.

2010-03-27 Thread Osamu Aoki
Package: lintian Version: 2.3.4 Severity: normal I think lintian is wrong in testing encoding issue for manapage. I have installed hello-debhelper (2.5-1). then I downloaded its binary package hello-debhelper_2.5-1_amd64.deb and extracted to hello.1 into a working directry. In short, instead

Re: Bits from the Lintian maintainers

2010-01-03 Thread Osamu Aoki
Hi, (I am noty yet subscribed. Plese CC me) On Sat, Jan 02, 2010 at 11:34:53AM -0800, Russ Allbery wrote: > Wow, two volunteers within a day! That's excellent. I'm replying to this > message since it goes into detail on the conversion process and copying > Osamu Aoki on thi

Re: Bits from the Lintian maintainers

2010-01-02 Thread Osamu Aoki
Hi, On Fri, Jan 01, 2010 at 08:11:58PM -0800, Russ Allbery wrote: > We're also looking for someone who would like to tackle converting the > Lintian manual to Docbook instead of DebianDoc-SGML and working on > updates. There's quite a bit about Lintian that isn't currently > documented. If you'r

Bug#405840: lintian: "build-depends-indep-should-be-build-depends debhelper" with version

2007-01-06 Thread Osamu Aoki
severity 405840 wishlist retitle 405840 lintian: "build-depends-indep-should-be-build-depends debhelper" confusing thanks Hi, On Sat, Jan 06, 2007 at 11:27:01AM -0800, Russ Allbery wrote: > Osamu Aoki <[EMAIL PROTECTED]> writes: > > > Package: lintian > > Ver

Bug#405840: lintian: "build-depends-indep-should-be-build-depends debhelper" with version

2007-01-06 Thread Osamu Aoki
ebconf information -- ~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ + Osamu Aoki <[EMAIL PROTECTED]> Yokohama Japan, GPG-key: A8061F32 .''`. Debian Reference: post-installation user's guide for non-developers : :' : http://qref.sf.net and http:

Bug#288568: Description field starting check ...

2005-01-27 Thread Osamu Aoki
ation, it could have implimented simple exception list dictionary: GNU X Debian X11 Gnome KDE PERL, PHP, Apache, Scheme, Tcl, Tk, Python, Emacs, Ocmel, C, C++, STL, ...) -- ~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ + Osamu Aoki <[EMAIL PROTECTED]> Bruss