Your message dated Mon, 31 Aug 2015 21:29:29 +0000
with message-id <[email protected]>
and subject line Bug#794897: fixed in maven-scm 1.3-7
has caused the Debian Bug report #794897,
regarding maven-scm: 1.3-6 FTBFS without libmaven-scm-providers-java which was
created in this version
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 [email protected]
immediately.)
--
794897: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794897
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: maven-scm
Version: 1.3-6
Severity: important
Dear Maintainer,
I saw that 1.3-6 was synced from Debian unstable to the development
version of Ubuntu [1], but it failed to build [2]. Oddly enough it
didn't ran into problems before it started with javadoc, but looked
like some missing build dependency.
So I took a look in my Sid vm to check whether this issue was
reproducible there as well. Now, I wasn't able to reproduce the same
issue, so the Ubuntu issue might be caused by some packages out of
sync with Debian... However, I ran into a similar issue on Debian:
[INFO] Building Maven SCM CVS Provider - Parent
[INFO] task-segment: [javadoc:jar]
[INFO]
------------------------------------------------------------------------
[INFO] [javadoc:jar {execution: default-cli}]
[INFO] Not executing Javadoc as the project is not a Java
classpath-capable package
[INFO]
------------------------------------------------------------------------
[INFO] Building Maven SCM CVS Provider TCK tests
[INFO] task-segment: [javadoc:jar]
[INFO]
------------------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
----------
1) org.apache.maven.scm:maven-scm-test:jar:1.3
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven.scm
-DartifactId=maven-scm-test -Dversion=1.3 -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.apache.maven.scm
-DartifactId=maven-scm-test -Dversion=1.3 -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.apache.maven.scm:maven-scm-provider-cvstest:jar:1.3
2) org.apache.maven.scm:maven-scm-test:jar:1.3
----------
1 required artifact is missing.
for artifact:
org.apache.maven.scm:maven-scm-provider-cvstest:jar:1.3
The missing artifact is provided by maven-scm, used to reside
in libmaven-scm-java [3], but is now part of
libmaven-scm-providers-java [4]. I am not quite sure why it failed to
find this artifact from the current build, but after installing
libmaven-scm-providers-java 1.3-6 it built succesfully. So it looks
like this might be a circular dependency or at least somethin odd
going on.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.0.0-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
[1] https://launchpad.net/ubuntu/+source/maven-scm/1.3-6
[2]
https://launchpadlibrarian.net/213866379/buildlog_ubuntu-wily-amd64.maven-scm_1.3-6_BUILDING.txt.gz
[3] https://packages.debian.org/stretch/all/libmaven-scm-java/filelist
[4]
https://packages.debian.org/sid/all/libmaven-scm-providers-java/filelist
--
mvh / best regards
Hans Joachim Desserud
http://desserud.org
--- End Message ---
--- Begin Message ---
Source: maven-scm
Source-Version: 1.3-7
We believe that the bug you reported is fixed in the latest version of
maven-scm, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Emmanuel Bourg <[email protected]> (supplier of updated maven-scm package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Mon, 31 Aug 2015 23:02:13 +0200
Source: maven-scm
Binary: libmaven-scm-java libmaven-scm-providers-java libmaven-scm-java-doc
Architecture: source all
Version: 1.3-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers
<[email protected]>
Changed-By: Emmanuel Bourg <[email protected]>
Description:
libmaven-scm-java - Maven SCM - Common API for SCM operations (Core API)
libmaven-scm-java-doc - Maven SCM - Common API for SCM operations
(Documentation)
libmaven-scm-providers-java - Maven SCM - Common API for SCM operations
(Providers)
Closes: 794897
Changes:
maven-scm (1.3-7) unstable; urgency=medium
.
* Team upload.
* Fixed the build failure when generating the javadoc (Closes: #794897)
Checksums-Sha1:
1d13d050bc800e6a5d870062f59fa31e28b6df39 2511 maven-scm_1.3-7.dsc
76675c008d2960825490f02e44fb75d44b1dc62c 5140 maven-scm_1.3-7.debian.tar.xz
797c871454c9b8a25ae68247bf7a9b87d90d6826 3784540
libmaven-scm-java-doc_1.3-7_all.deb
d6c0f5f62c0d8e5aa7f307abaf5cb8c56869ad09 76250 libmaven-scm-java_1.3-7_all.deb
ce5c0c829fc394fd41931e2dfb421c45bf0266ee 785746
libmaven-scm-providers-java_1.3-7_all.deb
Checksums-Sha256:
e33236199813515a81ed3bd408034a8d771586d6062a1d0ea1dacba9ff884656 2511
maven-scm_1.3-7.dsc
d312525edad2f83ad6dc2cdea59f7ef52b7248667843229fa6eaa4668aa62a83 5140
maven-scm_1.3-7.debian.tar.xz
6ce59bc7811b3875c7a9a04db7669947624f20518f8a8aecc1ae008d80c62c55 3784540
libmaven-scm-java-doc_1.3-7_all.deb
9a0afadd9452ede99574ef74a4dac6aa7202ead23a455001dba23d56f0c22573 76250
libmaven-scm-java_1.3-7_all.deb
f830fec74219385b8792361e9828dd368f0fbd81f40a919b5f1eeff9415749ee 785746
libmaven-scm-providers-java_1.3-7_all.deb
Files:
43910d13a4a819b0de3de35be63966a7 2511 java optional maven-scm_1.3-7.dsc
e0a06b75c869c05bd7998430bf8e3459 5140 java optional
maven-scm_1.3-7.debian.tar.xz
0d39deed60368b2963015c565c1ecca6 3784540 doc optional
libmaven-scm-java-doc_1.3-7_all.deb
891a8c08c8157f117b0654cbbe4df1c1 76250 java optional
libmaven-scm-java_1.3-7_all.deb
319bade4df75541b38a41f6434bc9d31 785746 java optional
libmaven-scm-providers-java_1.3-7_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJV5MJBAAoJEPUTxBnkudCsXtUQAI1/9612gWPFRg4ahVfPufaP
p5sSFoQHI5UgNqk4Q40khSSg5rF1zG7aeJeZcweOu25w+qLiqp+kJoIPCJ+9hA/7
HYGp0StcAHlbZLZh88p1puDSziZQjCvUVf+W/y3X+egXurnhgw+nfm51sGKtqJcF
mo2pdCyyJfgAJkHsttvttxHDnFkKGQ6BQtjT/pVpJzJYq7cqQy77hzyjCMOGV9dn
v+4/CWbmOR9nM587WXpbj6e6TDvo6Gogq1FfaCRKg7kglLTUE2uQxBxfFRH5mBZp
ixrw55F7KAwQdVA7qZufuGFlSG1UuEPkKArp36XZs847/h6fzn+0/36DSvG110Mu
Yu/guGVpdGppjVtduWhy3LFvjJmE2BI7ELk1n50uFqi7AESBHQiP8N643FjFAOHj
Ravw4NxXznJo+H4e0jewTDqP0wmd75dO31MwRqWrjYfTXPuXZbkbXYag1yHT9wG9
2mBvuqCMFcXvVdErFMZekb8TTSk6LBzB1HGj0mT8qAUX+MBbqLe2Q09zaTJIbDT3
UCUPEVY8kTieUPBxWy9nLCXTSZQ0vGAjz9wJCq2s7GACp1io1PnMvduBrtk9prnC
Pco+loMH4OGdw2g1Y0anZs5qoY/7L1WQgZtOPRm+5k7JabSrg97KqAK3jJ+Cg/CD
Ab+paayaEuN5t2owDybl
=Nu3d
-----END PGP SIGNATURE-----
--- End Message ---
