Your message dated Wed, 05 Dec 2007 20:11:37 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#432959: #432959,lintian: addition to not-binnmuable-any-depends-any check 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 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: lintian Version: 1.23.32 Severity: wishlist Hi, The not-binnmuable-any-depends-any check only looks for arch:any packages who depends with ${source:Version}. While arch:any packages with ${Source-Version} suffers from the same problem. The latter only get reported with to have a substvar-source-version-is-deprecated problem, instead of having issues. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-k7 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages lintian depends on: ii binutils 2.17cvs20070426-8 The GNU assembler, linker and bina ii diffstat 1.43-2 produces graph of changes introduc ii dpkg-dev 1.14.5 package building tools for Debian ii file 4.21-1 Determines file type using "magic" ii gettext 0.16.1-2 GNU Internationalization utilities ii intltool-debian 0.35.0+20060710.1 Help i18n of RFC822 compliant conf ii libparse-debianchangel 1.0-1 parse Debian changelogs and output ii man-db 2.4.4-3 The on-line manual pager ii perl [libdigest-md5-pe 5.8.8-7 Larry Wall's Practical Extraction lintian recommends no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Version: 1.23.33 Russ Allbery wrote: > Lior Kaplan <[EMAIL PROTECTED]> writes: > >>> The not-binnmuable-any-depends-any check only looks for arch:any >>> packages who depends with ${source:Version}. >>> >>> While arch:any packages with ${Source-Version} suffers from the same >>> problem. >>> >>> The latter only get reported with to have a >>> substvar-source-version-is-deprecated problem, instead of having >>> issues. >> Although marked as fixed, packages which use Source-Version for arch:any >> to arch:any packages still isn't reported as not-binnmuable-any-depends-any. > > Right, because they are no problem with such packages because > Source-Version is equivalent to binary:Version. No? That was the whole > reason why source:Version was introduced. Source-Version is actually > binary:Version and was badly misnamed. > > But Source-Version is safe in a library-dev -> library dependency. That > was what it was designed for. > > I'm pretty sure this bug really is closed, but maybe I'm confused. If I'm > confused, I'd appreciate a correction. Agreed. Closing again. -- Lior Kaplan [EMAIL PROTECTED] GPG fingerprint: C644 D0B3 92F4 8FE4 4662 B541 1558 9445 99E8 1DA0
--- End Message ---
