Processed: Re: Bug#804564: doxia: FTBFS: Cannot locate avalon-framework

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 fop 1:2.0+dfsg-3
Bug #804564 [src:doxia] doxia: FTBFS: Cannot locate avalon-framework
Bug reassigned from package 'src:doxia' to 'fop'.
No longer marked as found in versions doxia/1.1.4-3.
Ignoring request to alter fixed versions of bug #804564 to the same values 
previously set
Bug #804564 [fop] doxia: FTBFS: Cannot locate avalon-framework
Marked as found in versions fop/1:2.0+dfsg-3.
> severity -1 important
Bug #804564 [fop] doxia: FTBFS: Cannot locate avalon-framework
Severity set to 'important' from 'serious'

-- 
804564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#804564: doxia: FTBFS: Cannot locate avalon-framework

[Emmanuel Bourg]

Control: reassign -1 fop 1:2.0+dfsg-3
Control: severity -1 important

doxia-sitetools is affected by the same issue.

This was caused by the fop/1:2.0+dfsg-3 upload, its Maven pom has a
dependency on avalon-framework:avalon-framework-api but Avalon in Debian
is installed as org.apache.avalon.framework:avalon-framework-api. It's a
regression since fop in Jessie depends on
org.apache.avalon.framework:avalon-framework-api.

Bug#804564: doxia: FTBFS: Cannot locate avalon-framework

[Daniel Schepler]

Source: doxia
Version: 1.1.4-3
Severity: serious

>From my pbuilder build log:

...
[INFO] 
[INFO] Building Doxia :: FO Module
[INFO]task-segment: [package]
[INFO] 
[INFO] [resources:resources {execution: default-resources}]
[WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered 
resources, i.e. build is platform dependent!
[INFO] Copying 4 resources
[INFO] skip non existing resourceDirectory 
/build/doxia-1.1.4/doxia-modules/doxia-module-fo/target/generated-site/xsd
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Failed to resolve artifact.

Missing:
--
1) avalon-framework:avalon-framework-api:jar:debian

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=avalon-framework 
-DartifactId=avalon-framework-api -Dversion=debian -Dpackaging=jar 
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=avalon-framework 
-DartifactId=avalon-framework-api -Dversion=debian -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.maven.doxia:doxia-module-fo:jar:1.1.4
2) org.apache.xmlgraphics:fop:jar:debian
3) avalon-framework:avalon-framework-api:jar:debian

2) avalon-framework:avalon-framework-impl:jar:debian

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=avalon-framework 
-DartifactId=avalon-framework-impl -Dversion=debian -Dpackaging=jar 
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=avalon-framework 
-DartifactId=avalon-framework-impl -Dversion=debian -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.maven.doxia:doxia-module-fo:jar:1.1.4
2) org.apache.xmlgraphics:fop:jar:debian
3) avalon-framework:avalon-framework-impl:jar:debian

--
2 required artifacts are missing.

for artifact: 
  org.apache.maven.doxia:doxia-module-fo:jar:1.1.4

from the specified remote repositories:
  central (https://repo1.maven.org/maven2)



NOTE: Maven is executing in offline mode. Any artifacts not already in your 
local
repository will be inaccessible.


[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 7 seconds
[INFO] Finished at: Mon Nov 09 16:35:09 UTC 2015
[INFO] Final Memory: 28M/486M
[INFO] 
/usr/share/cdbs/1/class/maven.mk:93: recipe for target 'mvn-build' failed
make: *** [mvn-build] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2

I do see libavalon-framework-java being installed elsewhere in the log; it
would seem /usr/share/maven-repo just no longer has it registered under those
identifiers.
-- 
Daniel Schepler