Yannis ROSSETTO (rossettoy)2017-01-17 15:43 The changelogs folder (and some others) are no more packaged. These are development tools and must not be delivered in RPM packages. Those tools are still available in Tuleap git repository.
Jeff CLAY (jeffclay)2017-01-17 13:25 Yes, I was able to update to latest version and all seems to be working. I do have a concern. I moved the tools/utils/changelogs to a backup folder in order to get the previous version to work. I moved the folder then installed the rpm's and then ran the update command and it gave the result that everything is up to date. When I just updated to the latest version yesterday, i moved the changelog folder from backup back to its original location and ran the update command. It once again ran the udpate command and said everything was up to date. I just want to make sure that nothing was messed up by moving the changelogs directory. Thanks
Yannis ROSSETTO (rossettoy)2017-01-17 08:53 Hello, Is it possible for you to retry the update to the last version ? The packaging must be fixed.
Yannis ROSSETTO (rossettoy)2017-01-16 09:09 Hello @jeffclay Thanks for sharing this with us. I will open a new request to deal with this packaging issue.
Jeff CLAY (jeffclay)2017-01-14 00:09 I think I may have made matters worse trying to fix the issue on my own. Please see https://gist.github.com/jeffclay/1b43e899584b23b365a2a3dfaf477324 for a full log of what I have done and the results. I noticed that every time yum tried to install the tuleap package it was creating a new changelog item in /usr/share/tuleap/tools/utils/ ad was appending a version number each time which created things like "changelogs;5879485b". I backed up all of those as well as the actual changelogs directory and installed the tuleap package again. The results were: Running Transaction Updating : tuleap-9.3.99.44-1.el6.noarch 1/2 info Invalidate Restler cache info Invalidate language cache info Invalidate WSDL info Invalidate Plugin hooks Cleanup : tuleap-9.3.99.32-1.el6.noarch 2/2 warning: erase unlink of /usr/share/tuleap/tools/utils/changelogs/insert_lines_in_plugin_changelog.php failed: No such file or directory warning: erase unlink of /usr/share/tuleap/tools/utils/changelogs/insert_line_in_core_changelog.php failed: No such file or directory Verifying : tuleap-9.3.99.44-1.el6.noarch 1/2 Verifying : tuleap-9.3.99.32-1.el6.noarch 2/2 Updated: tuleap.noarch 0:9.3.99.44-1.el6 When I went to run the update script, it gave the message "[root@projects utils]# /usr/lib/forgeupgrade/bin/forgeupgrade --config=/etc/tuleap/forgeupgrade/config.ini update INFO - System up-to-date" The changelogs folder was recreated by the installation, but it is empty.
Jeff CLAY (jeffclay)2017-01-13 22:42 I was going to open another request for this, but it seems that isn't working properly. You get an error "The transition to the value "New" is not valid." Sorry for putting two new issues into a Follow-Up, I didn't know what else to do. When I was attempting to upgrade Tuleap to the latest version, the package has errors and will not install. [root@projects utils]# yum update Loaded plugins: fastestmirror Setting up Update Process Determining fastest mirrors epel/metalink | 14 kB 00:00 * base: repos.forethought.net * epel: fedora-epel.mirror.lstn.net * extras: repos.dfw.quadranet.com * updates: mirror.us.oneandone.net Tuleap | 951 B 00:00 Tuleap/primary | 41 kB 00:00 Tuleap 146/146 base | 3.7 kB 00:00 base/primary_db | 4.7 MB 00:00 epel | 4.3 kB 00:00 epel/primary_db | 5.9 MB 00:01 extras | 3.4 kB 00:00 extras/primary_db | 37 kB 00:00 updates | 3.4 kB 00:00 updates/primary_db | 4.3 MB 00:01 Resolving Dependencies --> Running transaction check ---> Package tuleap.noarch 0:9.3.99.32-1.el6 will be updated ---> Package tuleap.noarch 0:9.3.99.44-1.el6 will be an update --> Finished Dependency Resolution Dependencies Resolved ====================================================================================================================================================================================================================================================================================== Package Arch Version Repository Size ====================================================================================================================================================================================================================================================================================== Updating: tuleap noarch 9.3.99.44-1.el6 Tuleap 12 M Transaction Summary ====================================================================================================================================================================================================================================================================================== Upgrade 1 Package(s) Total download size: 12 M Is this ok [y/N]: y Downloading Packages: tuleap-9.3.99.44-1.el6.noarch.rpm | 12 MB 00:03 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Updating : tuleap-9.3.99.44-1.el6.noarch 1/2 Error unpacking rpm package tuleap-9.3.99.44-1.el6.noarch error: unpacking of archive failed on file /usr/share/tuleap/tools/utils/changelogs: cpio: rename Verifying : tuleap-9.3.99.44-1.el6.noarch 1/2 tuleap-9.3.99.32-1.el6.noarch was supposed to be removed but is not! Verifying : tuleap-9.3.99.32-1.el6.noarch 2/2 Failed: tuleap.noarch 0:9.3.99.32-1.el6 tuleap.noarch 0:9.3.99.44-1.el6 Complete! I ran yum clean all and tried again a few times, same issue.
Joris MASSON (jmasson)2017-01-13 18:02 gerrit #7399 integrated in Tuleap 9.3.99.43 Status changed from New to ClosedConnected artifacts Added Fixed in: rel #9810Close date set to 2017-01-13
Marie Ange Garnier (marieange)2017-01-13 09:51 Hello, I have reproduced your issue, I'm gonna work on a fix. Best regards
Jeff CLAY (jeffclay)2017-01-12 17:27 Yes I have. I also just updated tuleap again and the problem still persists. I followed the instructions from http://tuleap-documentation.readthedocs.io/en/latest/installation-guide/update.html both times.
Marie Ange Garnier (marieange)2017-01-10 11:06 Hello, Did you run the forgeupgrade script? Best regards