#4885 Trove categories being picked up during upgrade

v1.0.0
closed
Dave Brondsema
support (446) migration (63) p3 (267) sf-1 (616)
General
Cory Johns
2015-08-20
2012-09-07
Chris Tsai
No

[forge:site-support:#464]

Hi,

My project was updated today to the new forge, but we ended up with a lot of new trove things.
I deleted most of them (for example we were wwwhttp/dynamic content aside from being an emulator, we had something with a database, were in alfa/beta/stable state at the same time and one more that I forgot)
At the moment there is still one left
We have other license as license type (aside from our GPL2 license)
Or those tags/settings generated automatic or so ?

Perhaps we're picking up suggested Trove changes in addition to the actual Trove values.

Discussion

  • Dave Brondsema

    Dave Brondsema - 2012-09-07

    We need to check the entity_type on trove_group_link. 3 == project. 21 == entered during project registration (long time ago, I guess). Those are the only values used.

     

  • Dave Brondsema

    Dave Brondsema - 2012-09-07
    • size: --> 1
    • milestone: limbo --> forge-sep-21
     

  • Dave Brondsema

    Dave Brondsema - 2012-09-07
    • status: open --> in-progress
    • assigned_to: Dave Brondsema
     

  • Dave Brondsema

    Dave Brondsema - 2012-09-07
    • status: in-progress --> code-review
    • qa: Cory Johns
     

  • Dave Brondsema

    Dave Brondsema - 2012-09-07

    forge-classic:db/4885

    • run unit tests
    • ensure a manual migration still transfers valid troves to allura
     

  • Anonymous - 2012-09-10

    Originally by: josephj11

    I have a very simple project (duplexpr) that I just converted to Alura. It is GPL. It picked up three extra licenses during the coversion as well as a "uses encryption" flag. Looks like this bug affected me as well. I manually reset the fields.

     

  • Cory Johns - 2012-09-11
    • status: code-review --> closed
     

Log in to post a comment.