Processing commands for cont...@bugs.debian.org:
# p.s. the real submitter is:
submitter 638278 t.gla...@tarent.de
Bug #638278 [lintian] lintian: errors if only numerical owner/group info is
available
Changed Bug submitter to 't.gla...@tarent.de' from 'Niels Thykier
ni...@thykier.net'
thanks
Package: lintian
Severity: normal
On 2011-08-18 10:15, Thorsten Glaser wrote:
Hi,
no idea whether you knew it, but lintian warns with Error
severity if files in {control,data}.tar.gz have only the
numerical user and group ID filled in, i.e. are owned by
0/0 instead of root/root.
The
Processing commands for cont...@bugs.debian.org:
# that was probably a bad bug name
retitle 638278 lintian: errors if only numerical owner/group info is available
Bug #638278 [lintian] Bits from the Lintian maintainers
Changed Bug title to 'lintian: errors if only numerical owner/group info is
On 2011-08-18 13:50, Thorsten Glaser wrote:
Niels Thykier dixit:
Package: lintian
Hm, don’t find it, did you Cc submit@b.d.o?
(I usually file against Source for changes like this one…)
Hi,
I did (BCC it), the bug is #638278. I took the liberty of marking you
as the submitter.
Hi,
As the subject suggests, I updated lintian.d.o to using lintian 2.5.2.
I saw no initialized warnings, so I have closed #633887. However there
was a missing an import in reporting/harness (oops! my bad), which I
fixed in the master branch (and have cherry-picked on lintian.d.o
without the
Your message dated Thu, 18 Aug 2011 15:02:32 +0200
with message-id 4e4d0d68.2060...@thykier.net
and subject line Not present in 2.5.2
has caused the Debian Bug report #633887,
regarding lintian: Perl warnings from reporting/harness -f
to be marked as done.
This means that you claim that the
Niels Thykier dixit:
I did (BCC it), the bug is #638278. I took the liberty of marking you
as the submitter.
OK, no problem.
Emails in my inbox has a way of disappearing even if I tag them TODO
etc, so when I can I file bugs if I cannot handle them immediately.
Yeah, still before doing all
The following commit has been merged in the master branch:
commit a6144a09f2ece3ffb36bac669de674c061181e10
Author: Niels Thykier ni...@thykier.net
Date: Thu Aug 18 16:28:21 2011 +0200
Renamed ignore-overrides to non-overridable-tags
Renamed variables and methods to better reflect
The following commit has been merged in the master branch:
commit 45b90f13d3a5017bd4ddac950a2c351fa288b204
Author: Niels Thykier ni...@thykier.net
Date: Thu Aug 18 17:18:57 2011 +0200
Inform the user if overrides have been ignored
Lintian will now print an informal message if it
The following commit has been merged in the master branch:
commit da492134d7d154823eb1afa052f4798139f0a447
Author: Niels Thykier ni...@thykier.net
Date: Thu Aug 18 13:52:57 2011 +0200
Removed a duplicate allowed to in doc/lintian.xml
diff --git a/debian/changelog b/debian/changelog
index
The following commit has been merged in the master branch:
commit d9b8a0d9de50e709b1702dfcbb86bd6fcc21fe71
Author: Niels Thykier ni...@thykier.net
Date: Thu Aug 18 13:46:13 2011 +0200
Added missing import statement in reporting/harness
diff --git a/debian/changelog b/debian/changelog
index
The following commit has been merged in the master branch:
commit 5606b4ff5b6fe5ddc0f58b81d43c6dc57c6a9557
Author: Niels Thykier ni...@thykier.net
Date: Thu Aug 18 10:57:41 2011 +0200
Mentioned that the umask problem with the tests are now fixed
This has been fixed for a while
Niels Thykier ni...@thykier.net writes:
Upgrading was slightly complicated by two things;
reporting/checkout-release did not quite work for me (mostly due to a
merge-conflict). I think a git merge -s recursive -X theirs could
help the automation here.
Yeah, I don't think I usually actually
Hi
I have been working a bit on debugging the dead-lock issue in t/runtests
and I have found something interesting. Unfortunately I cannot
pin-point the issue...
When I see a dead-lock it, I noticed that we tend to have two lintian
proceses (ps: [lintian] defunct) and two /usr/bin/sort. Do we
The following commit has been merged in the master branch:
commit ccf06f9f483e5a2c1855ca93c6458af683f419db
Author: Niels Thykier ni...@thykier.net
Date: Thu Aug 18 22:20:18 2011 +0200
flush messages via a sub rather than sending messages to self
The message handler now uses a sub
The following commit has been merged in the master branch:
commit f85156c2469de1f9637f444a4c4e8dd9396ee106
Author: Niels Thykier ni...@thykier.net
Date: Thu Aug 18 22:23:18 2011 +0200
Do not use Lintian::Command (or IPC::Run) in t/runtests
Testing suggested that the dead-lock test
On 2011-08-18 21:24, Niels Thykier wrote:
Hi
I have been working a bit on debugging the dead-lock issue in t/runtests
and I have found something interesting. Unfortunately I cannot
pin-point the issue...
When I see a dead-lock it, I noticed that we tend to have two lintian
proceses (ps:
17 matches
Mail list logo
