Packaging is bailing because of 2 root causes.

D7 core migration does not take responsibility for moving rows from files to the files_managed table, that is up to the modules. This wasn't implemented for l10n_packager, so it is repackaging old releases. We should populate files_managed. japery is working on this.

This also shows an underlying issue, for some time in the past, distribution releases got recorded 3 times:

mysql> SELECT * FROM l10n_server_release WHERE pid = 30798 AND title = '7.x-1.0-rc1';
+--------+-------+-------------+-------------------------------------------------------------------------+------------+----------------------------------+-------------+--------+-----------+
| rid    | pid   | title       | download_link                                                           | file_date  | file_hash                        | last_parsed | weight | sid_count |
+--------+-------+-------------+-------------------------------------------------------------------------+------------+----------------------------------+-------------+--------+-----------+
| 354463 | 30798 | 7.x-1.0-rc1 | http://ftp.drupal.org/files/projects/cartaro-7.x-1.0-rc1.tar.gz         | 1373029856 | 629678b98c983bc3fcabb1ac397a887d |  1373030284 |      0 |        35 |
| 354468 | 30798 | 7.x-1.0-rc1 | http://ftp.drupal.org/files/projects/cartaro-7.x-1.0-rc1-no-core.tar.gz | 1373029878 | 458f4aa4cc9ed9ce6e42b1c84c23f5ff |  1373032215 |      0 |      5149 |
| 354473 | 30798 | 7.x-1.0-rc1 | http://ftp.drupal.org/files/projects/cartaro-7.x-1.0-rc1-core.tar.gz    | 1373029889 | 8c5aaf0af4dfcb13e2308267d73014a1 |  1373034848 |      0 |      9463 |
+--------+-------+-------------+-------------------------------------------------------------------------+------------+----------------------------------+-------------+--------+-----------+
3 rows in set (0.00 sec)

The -no-core and -core rows should not be there, as they are causing duplicate rows. I am working on this.

Comments

drumm created an issue. See original summary.

gábor hojtsy’s picture

gábor hojtsy’s picture

BTW is it true that the work from japerry will fix the emptyness of https://localize.drupal.org/translate/languages/de (top downloads) and the like? The files are obviously still available at http://ftp.drupal.org/files/translations/7.x/drupal/, etc, but the site is not aware of them (which is why it is attempting to rebuild them I guess).

drumm’s picture

Project: Localization server » localize.drupal.org

Moving because this is where the commits happened.

  • drumm committed d8b20b0 on 7.x-1.x
    Issue #2549799: Restore files_managed update
    
drumm’s picture

Status: Active » Needs review

fix the emptyness of https://localize.drupal.org/translate/languages/de (top downloads)

Yes, staging currently is working on running the update. https://localize.staging.devdrupal.org/translate/languages/de already looks much better.

drumm’s picture

Status: Needs review » Fixed
Issue tags: +needs drupal.org deployment

This looks okay on staging.

drumm’s picture

Issue tags: -needs drupal.org deployment

Now deployed.

gábor hojtsy’s picture

Yay, thanks, looks good :)

drumm’s picture

Status: Fixed » Active

This started failing again. https://localize.drupal.org/translate/projects/uc_ca_sms/releases has 2 records for Ubercart Conditional actions SMS integration 6.x-1.0. I'll query to see if there are others.

gábor hojtsy’s picture

The file names of the two are strange:

http://ftp.drupal.org/files/projects/ubercart-6.x-1.0.tar.gz
http://ftp.drupal.org/files/projects/uc_ca_sms-6.x-1.0.tar.gz

How would this project release with the ubercart machine name? The number of files/strings look comparable, so it seems to be some machine name snafu back in the day?

drumm’s picture

Yep, I've deleted the strange one. There is one other weirdness I can see. https://localize.drupal.org/translate/projects/gallery_assist/releases has 2 of Gallery Assist 6.x-1.8

drumm’s picture

Status: Active » Fixed

Of those 2, I deleted the older one. The file names were okay there.

The packaging cron is running again.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.