package: lintian
version: 1.23.44
Hi,
lintian doesnt warn about left over mercurial files in the source package,
like it does with svn or cvs files.
The following files remained unnoticed in my source package:
.hg_archival.txt |2
.hgignore
sony acid pro 6 - 59
conitec gamestudio pro a7 7.05 - 89
Put ''svedsoft. com'' into WEB Brovvser
(w/o '' and space)
adobe photoshop cs2 v 9.0 - 69
avid xpress pro 5.7 - 119
stuffit deluxe 11 for mac - 29
adobe acrobat 3d - 59
ulead photoimpact 12 - 79
sonic scenarist 3.0 - 49
adobe flash cs3
Author: djpig
Date: 2008-02-09 17:18:42 +0100 (Sat, 09 Feb 2008)
New Revision: 1199
Modified:
trunk/checks/control-files
trunk/checks/control-files.desc
trunk/checks/md5sums
trunk/checks/md5sums.desc
trunk/debian/changelog
trunk/testset/tags.binary
trunk/testset/tags.scripts
Processing commands for [EMAIL PROTECTED]:
package lintian
Ignoring bugs not assigned to: lintian
# Fixed in r1198 by djpig
tag 410042 + pending
Bug#410042: lintian: please warn on effectively-empty maintscripts
There were no tags set.
Tags added: pending
thanks
Stopping processing here.
Author: djpig
Date: 2008-02-09 16:58:00 +0100 (Sat, 09 Feb 2008)
New Revision: 1198
Added:
trunk/testset/scripts/debian/preinst
Modified:
trunk/checks/scripts
trunk/checks/scripts.desc
trunk/debian/changelog
trunk/testset/scripts/debian/rules
On Sat, Feb 09, 2008 at 10:54:12AM +0100, Holger Levsen wrote:
lintian doesnt warn about left over mercurial files in the source package,
like it does with svn or cvs files.
The following files remained unnoticed in my source package:
.hg_archival.txt |2
Author: djpig
Date: 2008-02-09 18:23:23 +0100 (Sat, 09 Feb 2008)
New Revision: 1200
Modified:
trunk/checks/cruft
trunk/checks/cruft.desc
trunk/debian/changelog
Log:
Add hg to the list of vcs-control-dir tags
Modified: trunk/checks/cruft
Christian Perrier [EMAIL PROTECTED] writes:
Yet another idea popping up in my mind. I'm in a lintian mood today..:)
Yay! :)
Some debconf templates use variable substitution (along with debconf's
SUBST command) to incorporate context-variable text in debconf
templates.
Description: Do you
While taking a look at #464837 (which is about source packages) I
noticed that checks for mercurial files are also missing for binary
packages. Before I add yet another tag I wanted to ask whether it
wouldn't be better to merge the tags for the different VCS', like so
Index: checks/files
On Sat, 09 Feb 2008 09:27:51 -0800
Russ Allbery [EMAIL PROTECTED] wrote:
I assume that something like the following pseudocode would work:
foreach pofile in debian/po/*.po
foreach msgid, msgstr in pofile
vars_needed = find_variables(msgid)
vars_found =
Frank Lichtenheld [EMAIL PROTECTED] writes:
While taking a look at #464837 (which is about source packages) I
noticed that checks for mercurial files are also missing for binary
packages. Before I add yet another tag I wanted to ask whether it
wouldn't be better to merge the tags for the
Russ Allbery wrote:
Sure, that sounds like a good idea to me. Should we trigger on anything
in a lintian template that looks like ${DISK}? Would $DISK also be
valid, or are the curly braces required?
The braces are required.
I assume that something like the following pseudocode would work:
Hi Frank,
On Saturday 09 February 2008 17:24, Frank Lichtenheld wrote:
.hg_archival.txt |2
Out of curiosity, what is this one for?
I dont really know.
$ cat .hg_archival.txt
repo: 7efd15ce4dab28ef21588ffef8ca00550290bd1d
node:
Author: djpig
Date: 2008-02-09 20:03:58 +0100 (Sat, 09 Feb 2008)
New Revision: 1201
Modified:
trunk/checks/files
trunk/checks/files.desc
trunk/debian/changelog
Log:
Merge all the tags for vcs ignore files and vcs control
dirs. Since the explanations don't actually differ, different
tags
Author: djpig
Date: 2008-02-09 20:29:23 +0100 (Sat, 09 Feb 2008)
New Revision: 1202
Modified:
trunk/testset/tags.filenames
Log:
Upps, forgot the testset changes for my previous commit
Modified: trunk/testset/tags.filenames
===
While doing some lintian work today (yay!) I noticed the following failure
that doesn't seem to have anything to do with my changes, and which is
an area I really am not motivated to debug ;)
Known issue?
Running test on debug 1.0: copying... building... testing... FAILED:
--- testset/tags.debug
Frank Lichtenheld [EMAIL PROTECTED] writes:
While doing some lintian work today (yay!) I noticed the following failure
that doesn't seem to have anything to do with my changes, and which is
an area I really am not motivated to debug ;)
Known issue?
I was accidentally testing a bug in
17 matches
Mail list logo
