Author: djpig
Date: 2004-02-22 15:01:29 +0100 (Sun, 22 Feb 2004)
New Revision: 57
Modified:
branches/1.22.11+udeb/checks/binaries.desc
branches/1.22.11+udeb/checks/files
branches/1.22.11+udeb/checks/files.desc
branches/1.22.11+udeb/collection/file-info.desc
Package: lintian
Version: 1.22.10
Severity: wishlist
A lintian warning about a missing debian/watch file should be added and perhaps
poiting to developers manual with instructions of the watch format and how to
add and use them
filippo
--
Filippo Giunchedi
GNU/PG key: 6B79D401
Random signature
Author: djpig
Date: 2004-02-22 16:24:32 +0100 (Sun, 22 Feb 2004)
New Revision: 58
Modified:
branches/1.22.11+udeb/checks/common_data.pm
branches/1.22.11+udeb/checks/control-files
branches/1.22.11+udeb/checks/control-files.desc
branches/1.22.11+udeb/checks/debconf.desc
Author: djpig
Date: 2004-02-22 21:55:14 +0100 (Sun, 22 Feb 2004)
New Revision: 60
Modified:
branches/1.22.11+udeb/checks/shared-libs
Log:
udebs don't contain shlib control files
Modified: branches/1.22.11+udeb/checks/shared-libs
Page is loading..
Image not loading? View message
here.Dis-c-o-n-t-i-n-u-e POxXO0MDU8b.JTiaY/4d2CP.ayiuk.zFZR/0
nwya bcu, syrwm, jtzlwz . aruld qlkehi fkicm, afzo, ihgtg . tiypte
mplsyw gijiu, kbn, jxi . tozowz rfhfu zvq, byjlu, xxmv . jfye
ztrzzl gsb, syr, bpb . majjm qxo cjqx, rwqy, ibccz .
On Mon, Feb 16, 2004 at 10:03:12PM +0100, Jeroen van Wolffelaar wrote:
Now that this tar-check thing is cleared up, I've prepared a RC 2 of
1.22.11.
Available via:
deb(-src) http://jeroen.A-Eskwadraat.nl/sw/debian EXPERIMENTAL lintian
Changes w.r.t. previous testrelease:
- changelog typo
lintian_1.22.11_powerpc.changes uploaded successfully to localhost
along with the files:
lintian_1.22.11.dsc
lintian_1.22.11.tar.gz
lintian_1.22.11_all.deb
Greetings,
Your Debian queue daemon
Accepted:
lintian_1.22.11.dsc
to pool/main/l/lintian/lintian_1.22.11.dsc
lintian_1.22.11.tar.gz
to pool/main/l/lintian/lintian_1.22.11.tar.gz
lintian_1.22.11_all.deb
to pool/main/l/lintian/lintian_1.22.11_all.deb
Announcing to debian-devel-changes@lists.debian.org
Closing bugs: 188095
Your message dated Sun, 22 Feb 2004 19:47:08 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#230182: fixed in lintian 1.22.11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 22 Feb 2004 19:47:07 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#215234: fixed in lintian 1.22.11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 22 Feb 2004 19:47:07 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#210576: fixed in lintian 1.22.11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 22 Feb 2004 19:47:07 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#207529: fixed in lintian 1.22.11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 22 Feb 2004 19:47:07 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#200802: fixed in lintian 1.22.11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 22 Feb 2004 19:47:07 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#200046: fixed in lintian 1.22.11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 22 Feb 2004 19:47:07 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#199341: fixed in lintian 1.22.11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 22 Feb 2004 19:47:07 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#194787: fixed in lintian 1.22.11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 22 Feb 2004 19:47:07 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#194257: fixed in lintian 1.22.11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 22 Feb 2004 19:47:07 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#188095: fixed in lintian 1.22.11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 22 Feb 2004 19:47:07 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#195201: fixed in lintian 1.22.11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 22 Feb 2004 19:47:07 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#202856: fixed in lintian 1.22.11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 22 Feb 2004 19:47:07 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#208945: fixed in lintian 1.22.11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 22 Feb 2004 19:47:07 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#214949: fixed in lintian 1.22.11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 22 Feb 2004 19:47:07 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#217384: fixed in lintian 1.22.11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 22 Feb 2004 19:47:08 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#231884: fixed in lintian 1.22.11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 22 Feb 2004 19:47:08 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#232875: fixed in lintian 1.22.11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Author: djpig
Date: 2004-02-23 02:35:56 +0100 (Mon, 23 Feb 2004)
New Revision: 62
Modified:
branches/1.22.11/checks/standards-version
Log:
Update standards-version parts, too (spotted by cjwatson)
Modified: branches/1.22.11/checks/standards-version
Author: djpig
Date: 2004-02-23 02:39:55 +0100 (Mon, 23 Feb 2004)
New Revision: 63
Added:
releases/1.22.11/
Removed:
branches/1.22.11/
Log:
1.22.11 was uploaded
Copied: releases/1.22.11 (from rev 62, branches/1.22.11)
Author: djpig
Date: 2004-02-23 03:13:44 +0100 (Mon, 23 Feb 2004)
New Revision: 64
Modified:
trunk/checks/standards-version
Log:
merge in change from 1.22.11 branch
Modified: trunk/checks/standards-version
===
---
Author: djpig
Date: 2004-02-23 03:18:08 +0100 (Mon, 23 Feb 2004)
New Revision: 65
Modified:
branches/1.22.11+udeb/checks/standards-version
Log:
merge in change from 1.22.11 branch
Modified: branches/1.22.11+udeb/checks/standards-version
29 matches
Mail list logo
