Re: maven2 broken deps? (Re: rawhide report: 20090830 changes)
* Alex Lancaster [2009-08-31 04:21]: > > Rawhide Report writes: > > [...] > > A whole slew of broken deps caused by a new maven2 have been sitting > in rawhide for about the last week with no attempted rebuilds to fix > it. Anybody know what's going on? This was my fault. Sorry. I mistakenly added some versioned dependencies on things that I have yet to have a chance to rebuild. I didn't notice it with my local builds and was progressing on the rest of the work hoping to finish very soon. It will be done this week but I can untag the latest build if it's bothering people. Andrew -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: maven2 broken deps? (Re: rawhide report: 20090830 changes)
> > "AK" == Alexander Kurtakov writes: > >> > Rawhide Report writes: > >> > >> [...] > >> > >> A whole slew of broken deps caused by a new maven2 have been sitting > >> in rawhide for about the last week with no attempted rebuilds to fix > >> it. Anybody know what's going on? > > AK> We are working on update of maven2 to not so ancient version. Progress > can be AK> tracked at http://fedoraproject.org/wiki/MavenUpdate . Currently > we are just 2 AK> guys working on this so any help is welcome. Anybody can > pick whatever task AK> he/she wants and help us getting it done. > AK> P.S. Broken deps will be fixed when we manage to update maven-shared. > > Since this requires an interconnected set of dependencies, it should > probably have been done by requesting a special build tag from > rel-eng, like dist-f12-maven2. > > Then all rebuilds could be done against the new tag and once all was > working correctly, then you would request a retagging back into the > regular dist-f12 in one hit. That way you get all the packages > updated to the new maven2 in one hit and it can be rolled back easily > if the entire maven doesn't make the release date.This is how > major updates to Python and Perl are done. > > The way it's currently done means that because you don't know how long > it will take to update all the relevant packages, the brokeness might > be around until F-12 and makes it harder to roll back to a last known > good version. Yeah, you're right but there is no last known good version - maven 2.0.4 is unusable to build anything(with really small exceptions) nowadays so we have nothing to lose. Hopefully making the problem more visible will get someone to help us and F-12 version will be better than the F-11 version for sure :) Alex > > Alex -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: maven2 broken deps? (Re: rawhide report: 20090830 changes)
> "AK" == Alexander Kurtakov writes: >> > Rawhide Report writes: >> >> [...] >> >> A whole slew of broken deps caused by a new maven2 have been sitting >> in rawhide for about the last week with no attempted rebuilds to fix >> it. Anybody know what's going on? AK> We are working on update of maven2 to not so ancient version. Progress can be AK> tracked at http://fedoraproject.org/wiki/MavenUpdate . Currently we are just 2 AK> guys working on this so any help is welcome. Anybody can pick whatever task AK> he/she wants and help us getting it done. AK> P.S. Broken deps will be fixed when we manage to update maven-shared. Since this requires an interconnected set of dependencies, it should probably have been done by requesting a special build tag from rel-eng, like dist-f12-maven2. Then all rebuilds could be done against the new tag and once all was working correctly, then you would request a retagging back into the regular dist-f12 in one hit. That way you get all the packages updated to the new maven2 in one hit and it can be rolled back easily if the entire maven doesn't make the release date.This is how major updates to Python and Perl are done. The way it's currently done means that because you don't know how long it will take to update all the relevant packages, the brokeness might be around until F-12 and makes it harder to roll back to a last known good version. Alex -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: maven2 broken deps? (Re: rawhide report: 20090830 changes)
> > Rawhide Report writes: > > [...] > > A whole slew of broken deps caused by a new maven2 have been sitting > in rawhide for about the last week with no attempted rebuilds to fix > it. Anybody know what's going on? We are working on update of maven2 to not so ancient version. Progress can be tracked at http://fedoraproject.org/wiki/MavenUpdate . Currently we are just 2 guys working on this so any help is welcome. Anybody can pick whatever task he/she wants and help us getting it done. P.S. Broken deps will be fixed when we manage to update maven-shared. Thanks, Alex > > > Broken deps for i386 > > -- > > [...] > > > maven2-plugin-antrun-2.0.8-1.3.fc12.noarch requires maven-embedder > > maven2-plugin-antrun-2.0.8-1.3.fc12.noarch requires > > maven-shared-reporting-impl maven2-plugin-assembly-2.0.8-1.3.fc12.noarch > > requires maven-shared-archiver > > maven2-plugin-assembly-2.0.8-1.3.fc12.noarch requires jmock >= 0:1.0.1 > > maven2-plugin-assembly-2.0.8-1.3.fc12.noarch requires > > maven-shared-test-tools maven2-plugin-assembly-2.0.8-1.3.fc12.noarch > > requires maven-shared-common-artifact-filters > > maven2-plugin-assembly-2.0.8-1.3.fc12.noarch requires > > maven-shared-repository-builder > > maven2-plugin-assembly-2.0.8-1.3.fc12.noarch requires > > maven-shared-plugin-testing-tools > > maven2-plugin-changelog-2.0.8-1.3.fc12.noarch requires > > maven-doxia-sitetools >= 0:1.0 > > maven2-plugin-changelog-2.0.8-1.3.fc12.noarch requires > > maven-shared-reporting-impl maven2-plugin-changes-2.0.8-1.3.fc12.noarch > > requires glassfish-javamail maven2-plugin-changes-2.0.8-1.3.fc12.noarch > > requires maven-shared-reporting-impl > > maven2-plugin-checkstyle-2.0.8-1.3.fc12.noarch requires > > maven-shared-reporting-impl > > maven2-plugin-dependency-2.0.8-1.3.fc12.noarch requires > > maven-shared-dependency-tree > > maven2-plugin-dependency-2.0.8-1.3.fc12.noarch requires > > maven-shared-dependency-analyzer > > maven2-plugin-docck-2.0.8-1.3.fc12.noarch requires > > maven-shared-plugin-tools-java >= 0:2.2 > > maven2-plugin-docck-2.0.8-1.3.fc12.noarch requires > > maven-shared-plugin-tools-api maven2-plugin-docck-2.0.8-1.3.fc12.noarch > > requires maven-shared-reporting-impl > > maven2-plugin-docck-2.0.8-1.3.fc12.noarch requires > > maven-shared-plugin-tools-beanshell >= 0:2.2 > > maven2-plugin-ear-2.0.8-1.3.fc12.noarch requires maven-shared-verifier > > maven2-plugin-eclipse-2.0.8-1.3.fc12.noarch requires jmock >= 0:1.0.1 > > maven2-plugin-eclipse-2.0.8-1.3.fc12.noarch requires > > maven-shared-test-tools maven2-plugin-eclipse-2.0.8-1.3.fc12.noarch > > requires maven-shared-plugin-testing-tools > > maven2-plugin-enforcer-2.0.8-1.3.fc12.noarch requires > > maven-enforcer-rule-api maven2-plugin-help-2.0.8-1.3.fc12.noarch requires > > maven-shared-plugin-tools-api maven2-plugin-idea-2.0.8-1.3.fc12.noarch > > requires jmock >= 0:1.0.1 maven2-plugin-jar-2.0.8-1.3.fc12.noarch > > requires maven-shared-archiver >= 0:2.3 > > maven2-plugin-javadoc-2.0.8-1.3.fc12.noarch requires > > maven-shared-reporting-impl maven2-plugin-one-2.0.8-1.3.fc12.noarch > > requires maven-shared-model-converter > > maven2-plugin-plugin-2.0.8-1.3.fc12.noarch requires > > maven-shared-plugin-tools-java >= 0:2.2 > > maven2-plugin-plugin-2.0.8-1.3.fc12.noarch requires > > maven-shared-reporting-impl maven2-plugin-plugin-2.0.8-1.3.fc12.noarch > > requires maven-shared-plugin-tools-beanshell >= 0:2.2 > > maven2-plugin-pmd-2.0.8-1.3.fc12.noarch requires > > maven-shared-reporting-impl > > maven2-plugin-project-info-reports-2.0.8-1.3.fc12.noarch requires > > maven-shared-jar maven2-plugin-project-info-reports-2.0.8-1.3.fc12.noarch > > requires maven-doxia-sitetools >= 0:1.0 > > maven2-plugin-project-info-reports-2.0.8-1.3.fc12.noarch requires > > maven-shared-dependency-tree > > maven2-plugin-project-info-reports-2.0.8-1.3.fc12.noarch requires > > maven-shared-reporting-impl -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
