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

Bug#976889: marked as done (classpath-contains-relative-path is a false-positive for libX-clojure packages)

Your message dated Thu, 10 Dec 2020 13:13:51 -0500
with message-id <1e6b4833-3837-4dc1-f79a-7484ec9e33da@debian.org>
and subject line closing lintian classpath-contains-relative-path
has caused the Debian Bug report #976889,
regarding classpath-contains-relative-path is a false-positive for libX-clojure packages
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.)


-- 
976889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976889
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: lintian
Version: 2.104.0
Severity: normal

Dear maintainers,

It seems that when packaging a Clojure package that also has a
d/libX-clojure.classpath file, the "classpath-contains-relative-path"
tag is emitted.

The tag's description says:

"Note, Lintian assumes that all (relative) classpaths pointing to
/usr/share/java/ (but not subdirs thereof) are satisfied by dependencies
as long as there is at least one strong libX-java dependency."

Since Clojure packages also push jars in "/usr/share/java" but aren't
named "libX-java", I'm assuming this is a false-positive.

In my opinion, this check should also take for granted classpaths are
satisfied by strong libX-clojure dependencies.

I would like to think I'll have time to submit a patch to fix this
problem this week, but if someone else wants to have a go, I certainly
won't mind.

Cheers,

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   pollo@debian.org / veronneau.org
  ⠈⠳⣄

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message --- 
Upon further investigation, it seems a mistake on my end in the
d/foo.classpath file was responsible for this lintian tag being emitted.

For example, in core-asyn-clojure (previously mentioned), fixing this
mistake made the tag go away:

--- a/debian/libcore-async-clojure.classpath
+++ b/debian/libcore-async-clojure.classpath
@@ -1 +1 @@
-usr/share/java/core.async.jar usr/share/java/clojure.jar
usr/share/java/tools.analyzer.jvm
+usr/share/java/core.async.jar /usr/share/java/clojure.jar
/usr/share/java/tools.analyzer.jvm

Sorry for opening a bug for nothing!

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   pollo@debian.org / veronneau.org
  ⠈⠳⣄

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
Reply to: