If you run drush fserver-package on a git-based project with more than one new tag, the version info at the bottom of .info files is appended to (rather than replaced) with each successive tag.

In other words, if you create two new tags such as 6.x-1.2 and 6.x-1.3, then run drush fserver-update, the bottom of the 6.x-1.2 info file will (correctly) look like:

; Information added by fserver
core = "6.x"
datestamp = ""
project = "rice_cas"
project status url = "http://code.danepowell.com/fserver"
version = "6.x-1.2"

... but the bottom of the 6.x-1.3 info file will (wrongly) look like:

; Information added by fserver
core = "6.x"
datestamp = ""
project = "rice_cas"
project status url = "http://code.danepowell.com/fserver"
version = "6.x-1.2"
; Information added by fserver
core = "6.x"
datestamp = ""
project = "rice_cas"
project status url = "http://code.danepowell.com/fserver"
version = "6.x-1.3"

Comments

eugenmayer’s picture

eugenmayer commented

Jap, known issue. Any patches? :)

eugenmayer’s picture

eugenmayer commented

Suggestion: Enclose those informations into a block rather then a start mark

; --START-- Information added by fserver
core = "6.x"
datestamp = ""
project = "rice_cas"
project status url = "http://code.danepowell.com/fserver"
version = "6.x-1.3"
; --END-- Information added by fserver

This way we could easily parse and remove this block when reding the info file

danepowell’s picture

danepowell commented

I'd love to take a crack at a patch, I just have some higher priorities at the moment. I'm not familiar with the internals, but it doesn't sound like this would be a parsing problem, because the copy in the Git repository doesn't have the info block at all. Also, if you create a tag, run drush fserver-package, create another tag, run drush fserver-package, everything works fine- it's only if you create two or more tags and run drush fserver-package that this bug occurs.

eugenmayer’s picture

eugenmayer commented

any updates on this? Would set this as a goal for 1.3

eugenmayer’s picture

eugenmayer commented
Status: Active » Fixed

fixed that, during bug hunting for http://drupal.org/node/1185366 ... was simply because if you have a projects, which gets generated more then one package during a fserver-package run...the repo gets not reset --hard after the info files have been generated for package...

This actually resulted in that duble / tripel actually ... #packages_of_project_in_this_run

But in addition, see the other ticket, tags in other branches then head could not get generated...details in the other ticket

will be part auf 1.2-beta2

eugenmayer’s picture

eugenmayer commented
Version: 6.x-1.1 » 7.x-1.x-dev
Status: Fixed » Needs work

moving over to 7.x, fixed for 6.x

eugenmayer’s picture

eugenmayer commented
Status: Needs work » Postponed

for now, postponing all all D7 issues, as the branch seems unmaintained by the initial author. PLease suggest using D6 rather for now