(rather than having to also factor in
packages that use transitive dependencies)?
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
to hear other opinions on this, though. I may be missing
something.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
.
Could you add support to dput and dupload to see if the Distribution in
the *.changes file is set to UNRELEASED and reject the upload if so?
After that's done, we'll make the change to lintian.
Thanks!
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle
with a fix.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
are not
required to support oldstable, it's not necessary any longer to avoid
POSIX tar.
Unless someone disagrees, my inclination is to remove this tag entirely.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
in the next upload.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
is a policy violation, it has not historically
been an RC bug. Not all policy violations are RC.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Thomas Huriaux [EMAIL PROTECTED] writes:
Russ Allbery [EMAIL PROTECTED] (13/09/2006):
W: dpkg-www source: unknown-po-debconf-file debian/po/cs.po.Miroslav_Kure
This is an example of an extra file that, on its surface, seems
legitimate.
This looks more like an old translation that could
in any runlevel, and
only be used in runlevel S, and thus do not need any required-stop
values either:
Yeah, sorry about that. It's already fixed in Subversion.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
easier.)
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
, although we'll see if we get any
pushback after the next lintian release.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
as well, right? Not
just select and multiselect?
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
of action
may be to reassign this bug to doc-base (or to both doc-base and lintian)
and ask the doc-base maintainer to clarify the specification.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe
are fairly apparent, though.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
you
mention the specific wildcards that are supported and let me know so that
I can update lintian accordingly?
Thanks!
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
that the tests in
postinst can be written as case statements or if statements and in many
different formats and syntaxes and simply missing the word reconfigure
doesn't mean that the postinst is wrong.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
package is ever updated to change its
dependencies. Even if this seems unlikely, please always add explicit
build dependencies on every non-essential, non-build-essential package
that is used directly during the build.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org
circumstances, one can
always make a copy of the root directory, modify it however, and then
point lintian at it.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
of maintainer scripts.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
directory (although far less common than
installing a zero-length README file or the like).
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
supposed to work at some
point, but I won't have time to do that for some time yet, probably not
before the etch release.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
fromt eh beginning.
Yeah, info-priority messages are filling this need for right now, and this
one is already info-priority. Eventually this will get better.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
Damyan Ivanov [EMAIL PROTECTED] writes:
Russ Allbery написа:
I can't do that because no version of msgcmp prior to 0.16 supports
that flag and 0.16 is only in experimental. Making that change would
require a dependency on 0.16, which would make lintian uninstallable in
unstable.
gettext
be
smooth (expect, maybe, the new msgcmp behaviour).
That the msgcmp change is annoying for lintian is, I think, an artifact of
the fact that lintian is doing something weird and not really the fault of
gettext. Okay, I'll ponder how best to fix lintian.
Thanks for the information!
--
Russ Allbery
going on.)
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
-debianchangelog-perl?
That's the package that does the syntax checking of the changelog file
rather than lintian itself.
Thanks!
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
is using for their shell and we may inadvertantly produce
something that's unreadable. That looks like it's a fairly simple change
to your patch.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
is for the 'dpkg-source -q' issue.
Don't you also have to patch around the msgcmp thing that just went into
the current version?
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble
Loïc Minier [EMAIL PROTECTED] writes:
On Sun, Dec 03, 2006, Russ Allbery wrote:
The one thing that I think should probably be changed is that lintian
should probably default to not using color and support
--color={never,always,auto} similar to ls. The problem with defaulting
to using color
that. The real check here is done by
ftp-master; lintian is just helping maintainers catch problems that save a
round-trip with ftp-master. Maybe it would be better to defer the
subtleties to that check.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle
predates that virtual package. I'll make
this change.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
for that
3) Appeal to tech-ctte if the above fails
Otherwise, I'll close this bugreport by the end of the year.
I was about to just close it, so I completely agree with this evaluation.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email
information about why this
is the case, and let me know if, after reading that, you still think the
message is wrong.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
to this with the next upload.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
don't object to adding a lintian check, but from a lintian
perspective this is just aesthetics since either form is valid.)
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble
that
because the syntax check is done on the binary package.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
what you're talking about, lintian already
does this and has for quite a while.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
, it may be that some package
that doesn't use debhelper is using it for an entirely different purpose.
And I can't think of what bug this would catch.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
with doing this is the high risk of false positives. There
are a lot of non-native packages for which a watch file is not meaningful.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble
sometimes correct to ship an empty directory, but not
one of the regular system directories like usr/bin or usr/sbin. (Shipping
empty directories in /var is quite common, though, and not an error.)
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE
the missing hyphen in first message is not very obvios.
Or, there could be some leverage to match some obvious strings that
look like the correct string:
/[*].*(Non[- \t]Maintainer upload|NMU[ \t]upload)/i
A combination of both of these approaches sounds good to me.
--
Russ Allbery ([EMAIL
?
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
, but the basic idea is sound. I've thought about
implementing this a few times but haven't gotten around to it.
This is one of the checks I had in mind when I started the new
checks/rules file.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email
The recommended order:
- debhelper
- dpatch
- autotools-dev
- others in alphabetical order
I don't agree with this check or this suggested order. I think
alphabetical order is reasonable, as is order based on the Autoconf
script, as is putting debhelper and similar internal checks last.
--
Russ
: of synchronisation, the package may not build as expected.
N:
N: Refer to the debhelper(7) manual page for details.
Sure, that's fine.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe
a compiled library. It doesn't have to do with whether the
package itself contains a library. (Not to mention that you're searching
for files only included in a dev package, which is something else
entirely.)
I think there's some fundamental misunderstanding here.
--
Russ Allbery ([EMAIL
that are easily overlooked and
they appear in patch. Paying attention to these could help making files
in debian/* more strict.
I think info level is too strong for this. I'd rather wait until we have
better tagging and an explicit aesthetics category.
--
Russ Allbery ([EMAIL PROTECTED
Russ Allbery [EMAIL PROTECTED] writes:
This doesn't make sense. ${shlibs:Depends} is required for any package
that contains a compiled library.
Er, compiled *binary*.
Basically, any package that's not Arch: all needs ${shlibs:Depends}, with
a very small number of exceptions.
--
Russ
that allowing a dependency on libdebconfclient0 without cdebconf is really
what we want, but that's what the current code does.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
Russ Allbery [EMAIL PROTECTED] writes:
Damyan Ivanov [EMAIL PROTECTED] writes:
Package: lintian
Version: 1.23.27
Followup-For: Bug #349616
Thanks for the updated problem description, but it does not solve the
problem.
A Depends: line of debconf (= 1.3.22) | cdebconf (= 0.43) still
exit
Yup, seems like a good idea to me.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
, since
at the least the list in footnote 16 and the list in 5.6.17 should match.
And we should discuss whether the list in 5.6.17 should be normative and
comprehensive; are other urgencies rejected by the archive software?
Anyway, I will also fix lintian.
Thank you!
--
Russ Allbery ([EMAIL PROTECTED
that provide gbx2 or gbr2.
Am I just looking in the wrong place?
(Sorry about the delay in responding to this.)
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
of that sort and I'm not sure that getting into
the business of checking one's debian/* files for consistency with
debhelper dh_* invocations is where we want to go. Seems rife with false
positives and unlikely to catch real bugs.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org
. Okay, making this change now.
Just to confirm, gbx2 should be removed and gbr2 should be added, right?
(The package currently provides both.)
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
that something is doing this.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
is buggy the bug will rarely show up in
practice, but I'm not sure a lintian check is the right approach. (And I
*really* dislike the idea of telling maintainers to obfuscate their code
to avoid a lintian warning.)
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle
version now with a
minimal fix for migration into testing. I added this in the process of
fixing an earlier bug and clearly missed the debugging code when I
committed the fix.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL
?
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
of this and some opinion from
ftp-master about what level they're willing to enforce before we make a
change.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
need to look at which should make this even easier to implement, so I'm
hopeful that it will make it into the next release.
Do you know what verson of cdebconf introduced this feature?
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email
waiting on me to find a few moments of free time, which
have been unexpectedly scarce in the last couple of weeks between an
OpenAFS security vulnerability and a few explosions at work.
I will hopefully get it back up and running normally soon.
--
Russ Allbery ([EMAIL PROTECTED
if we exempt essential
packages from this check (plus things like libc6 that are essential in
practice), that would cut the false positives down sufficiently.
What do you think?
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL
want to be sure that it's really the right thing
to warn about before we do it.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Luk Claes [EMAIL PROTECTED] writes:
According to joeyh it's appropriate to warn for use of DH_COMPAT at the
top of the file (before any Makefile target).
Thank you for checking on this! I'll get this merged for the next
release.
--
Russ Allbery ([EMAIL PROTECTED]) http
and what's the canonical path to the
interpretor? Also, is there no jruby interpretor? Is it always jruby0.9?
What happens when 1.0 comes out?
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe
that this is a bug. It saves a small
amount of space to link the binaries, but when the binaries are small,
it's not immediately obvious that deviation from upstream practice is
worth it.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email
in the binary-without-manpage tag.
These changes will be in the next release.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
, or
is it more a best practice kind of thing?
This feels like the kind of thing that, if lintian is going to warn about
it, should also be in either Policy or the DevRef.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
, but
it's finally starting to clear up.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
that goes well, will switch lintian.debian.org over and start up
the nightly cron job again.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
architectures during
the etch release cycle while lintian.debian.org was not updating. It
would have taken me much longer to get lintian.debian.org back up and
running without him.
- --
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
-BEGIN PGP SIGNATURE-
Version
cannot
see any reason why it would be, or even how you could usefully do so.
Indeed. Will be fixed in the next release.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
example is the php5 binary package, which only contains a few
directories and a symlink (/usr/share/doc/php5 - php5-common).
Good catch. Thanks. Will be fixed in the next release.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL
what string in the license I should
use to recognize it?
Thanks!
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
! Will be fixed in the next release.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
on itself. But the suggested check would make this
necessary to avoid an error :) Maybe the check should contain an
unless (($pkg eq $package) || ...
at the start too, to make sure, we don't try to check for a dependency
on ourselves.
Good idea. Added.
--
Russ Allbery ([EMAIL PROTECTED
.
Sounds right to me. This will be in the next release.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
grep -vH `echo $f | sed 's/\.shlibs//'` $f | grep -v udeb | grep -v '\#'
done
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: lintian
Version: 1.23.29
Severity: wishlist
Per the message from Mike Hommey [EMAIL PROTECTED] on debian-devel:
It would be great if developer lintian report would should not only
directly maintained packages but also co-maintained ones.
This will require some work on the data formats
important and needs to be preserved. The
question is how far to go back beyond stable.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
out this possible bug, but in that
case the bug only triggers if the symlink replaces something that was
previously a file, and lintian doesn't have a way of knowing that.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
. As-is, it will require libmodule-build-perl
in Build-Depends and error if it's not there, which *seems* right, but
we'll see.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
people do.
I was under the impression that automake as of 1.10 had dropped the
versioned thing, but I see that didn't happen. Okay, I'll go back and add
the individual versions.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
lines are fine, so I'm
fixing the test so that it doesn't produce a false positive on blank
lines. Thanks for the report!
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
how far to go back.
(Although I suppose one could do the same check against the changelog
entry included in the *.changes file, which would be an interesting route
to take. I'll have to think about doing it that way.)
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle
Thijs Kinkhorst [EMAIL PROTECTED] writes:
On Thursday 10 May 2007 17:28, Russ Allbery wrote:
However, it's not correct that only the top-most changelog entries are
relevant.
That's true in some cases, and indeed the .changes file might address
that. But I wonder whether there will be many
packages should be unpacked with dpkg-source or with a
program that performs the same operations. Since you're repackaging the
upstream source anyway, you can certainly fix it if you so choose, but
there's no need to do so.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle
with packages
that are unaffected (like libglib2.0-doc).
Yeah, this is already fixed in Subversion and will be in the next upload.
(Sorry to have not responded before you spent time tracking it down; I'm
mostly off-line this weekend.)
--
Russ Allbery ([EMAIL PROTECTED]) http
in the lintian output?
If the full path isn't used, that will still need to be fixed; lintian
expects all command interpreters to be used with the full path.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
this, but a
lintian error is going to be more effective. ;)
Sorry for not providing a patch, I hope to have time and submit one
this week.
No problem on the lack of patch; it's easy enough to implement. It'll be
in the next release.
--
Russ Allbery ([EMAIL PROTECTED]) http
Jörg Sommer [EMAIL PROTECTED] writes:
Russ Allbery schrieb am Sun 03. Jun, 20:09 (-0700):
That warning seems to indicate that the script isn't using the full
path to jed-script in the #! line. Is that correct, or is there also
some sort of bug in the lintian output?
Yes
(in different
forms), which might be good to refactor into common_data.pm or
something.
Good idea. I'll take a look at doing this.
The patch will be in the next version of lintian. Thank you!
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email
of the web-application.
Should the lintian check only be excluding files that end in *.pt?
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
/no? If so, I think
you're right and this is a false positive. (If it's installed directly in
/usr/share/man, there's a different answer.)
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
Sebastian Harl [EMAIL PROTECTED] writes:
Package: lintian
Version: 1.23.8
Severity: wishlist
Hi,
Please add /usr/bin/octave (currently provided by the octave2.X
packages) to the list of known interpreters. It is used by the
(upcoming) pfstools package.
Thanks, added.
--
Russ Allbery
Bernd Zeimetz [EMAIL PROTECTED] writes:
Should the lintian check only be excluding files that end in *.pt?
*.dtml, *.pt and *.cpt are Zope template extensions, it should be enough
to exclude only those files.
Thanks, I've done that.
--
Russ Allbery ([EMAIL PROTECTED]) http
this bug.
I think you're misreading the code -- lintian skips this check for any
file that isn't a shared library, which is what the SONAME check is for.
But I'm not positive. Could you provide more details on where you think
lintian is confused?
--
Russ Allbery ([EMAIL PROTECTED
properly with -module, but I'm not sure with
-avoid-version. I'm not sure that I've used that option. Is the source
package exhibiting the problem available anywhere? I'd poke at the
current unstable version, but it appears to not have this issue.
--
Russ Allbery ([EMAIL PROTECTED
101 - 200 of 2537 matches
Mail list logo
