[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#498370: marked as done (Edos-debcheck has fussy management of version number)

Your message dated Thu, 18 Jun 2009 21:54:45 +0200
with message-id <20090618195445.GC4120@free.fr>
and subject line closed
has caused the Debian Bug report #498370,
regarding Edos-debcheck has fussy management of version number
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 responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
498370: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498370
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: edos-debcheck
Version: 1.0-7

Edos-debcheck, and builddebcheck as well, have problems in parsing non-
policy-compliant version numbers.
I saw some 'strange' versions that make edos break.

Some of this are already corrected in his packages, anyway, there are some 
of them: 

1 - version numbers with stars, such as "1.0.*"
2 -  "[]", without architectures specified.
3 - "(>= ${Source-version})"

These three in particular makes impossible to complete the parsing of the 
other packages. ( workarounds are possible, indeed)

The first is documented in Bug #498175.
The second has this behavior: 

$ edos-builddebcheck Packages  Sources
[....]
Parsing package file...   21630 packagesdeb822.py: WARNING: cannot parse 
package relationship "fastjar []", returning it raw
deb822.py: WARNING: cannot parse package relationship "libmagic-dev []", 
returning it raw
deb822.py: WARNING: cannot parse package relationship "libecj-java (>= 
3.3.0-2) []", returning it raw
deb822.py: WARNING: cannot parse package relationship "zip []", returning 
it raw
deb822.py: WARNING: cannot parse package relationship "libxtst-dev []", 
returning it raw
deb822.py: WARNING: cannot parse package relationship "libxt-dev []", 
returning it raw
deb822.py: WARNING: cannot parse package relationship "libgtk2.0-dev (>= 
2.4.4-2) []", returning it raw
deb822.py: WARNING: cannot parse package relationship "libart-2.0-dev []", 
returning it raw
deb822.py: WARNING: cannot parse package relationship "libcairo2-dev []", 
returning it raw
deb822.py: WARNING: cannot parse package relationship "libgconf2-dev []", 
returning it raw
Fatal error: exception Failure("Bad token in 'dpkg-dev (>= 1.14.15), 
debhelper (>= 5.0.62), gcc-multilib, libc6-dev (>= 2.5), libc6-dev-amd64, 
lib64gcc1, m4, autoconf, autoconf2.13, automake1.9, libtool, autogen, gawk, 
dejagnu, lzma, binutils (>= 2.17cvs20070426) | binutils-mul

For the 3rd, i haven't a log, but it's easy to reproduce, putting ${Source-
version) in place of a correct dependency.

Thanks, 
-- 
-gaspa-
-----------------------------------------------
-------- https://launchpad.net/~gaspa ---------
------ HomePage: iogaspa.altervista.org -------
-Il lunedi'dell'arrampicatore: www.lunedi.org -

--- End Message ---
--- Begin Message --- 
Version: 1.4.2-2

> Edos-debcheck, and builddebcheck as well, have problems in parsing non-
> policy-compliant version numbers.
> I saw some 'strange' versions that make edos break.

this has been fixed with the switch to the edos-distcheck package
which uses a different parser for debian control files.

-Ralf.

--- End Message ---
Reply to: