Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

upgrade to DSM7 package version #33

Draft
wants to merge 14 commits into
base: gitea
Choose a base branch
from

Conversation

stephengeorgewest
Copy link

@stephengeorgewest stephengeorgewest commented Mar 16, 2023

The first commit resolves "Invalid Package" errors for DSM7

"code":263,"description":"failed to sort spks, the spk might not exist or invalid format

2023-03-16T06:53:02-06:00 DiskStation synopkg[30978]: pkgtool.cpp:1273 Failed to extract package INFO, from=[/tmp/gitea/gitea-spk/gitea-1.18.5-linux-arm64.spk] to=[/volume1/@tmp/synopkg/info.ovODJp]

The tar argument changes do slow down the archiving though.

Still looking into:

2023-03-16T07:09:51-06:00 DiskStation synopkg[20433]: pkginstall.cpp:1058 Failed to install package,
  spk=[/tmp/gitea/gitea-spk/gitea-1.18.5-linux-arm64.spk]
result=
[{
    "action":"install",
    "beta":false,
    "betaIncoming":false,
    "error":{
        "code":319,
        "description":"invalid package privilege content"
      },  
    "installReboot":false,
    "installing":true,
    "language":"enu",
    "last_stage":"prepare_install",
    "package":"Gitea",
    "packageName":"Gitea",
    "spk":"/tmp/gitea/gitea-spk/gitea-1.18.5-linux-arm64.spk",
    "stage":"install_failed",
    "success":false,
    "username":"",
    "version":"1.18.5"
  }]

@stephengeorgewest
Copy link
Author

"description":"invalid package privilege content" was due to missing defaults section in config/privilege :https://help.synology.com/developer-guide/privilege/privilege_config.html, which wasn't listed in breaking changes: https://help.synology.com/developer-guide/breaking_changes.html

next error:

{
  "error":{"code":0},
  "results":[{
    "action":"install",
    "beta":false,
    "betaIncoming":false,
    "error":{
      "code":313,
      "description":"failed to revise file attributes"
    },
    "installReboot":false,
    "installing":true,
    "language":"enu",
    "last_stage":"prepare_install",
    "package":"Gitea",
    "packageName":"Gitea",
    "spk":"/tmp/gitea/gitea-spk/gitea-1.18.5-linux-arm64.spk",
    "stage":"install_failed",
    "success":false,
    "username":"",
    "version":"1.18.5"
  }],
  "success":false
}

@stephengeorgewest
Copy link
Author

/var/log/messages

2023-03-16T16:46:05-06:00 DiskStation synopkg[8177]: privilege_api.cpp:593 Failed to set default owner of Gitea [0x4000 privilege_api.cpp:377]
2023-03-16T16:46:05-06:00 DiskStation synopkg[8177]: pkginstall.cpp:1058 Failed to install package, spk=[/tmp/gitea/gitea-spk/gitea-1.18.5-linux-arm64.spk]

probably related to username: ""

@stephengeorgewest
Copy link
Author

Yeah, username issue. I have installed the published wkobiela version, which changed the username from gitea to sc-gitea and the port from 3000 to 8418 Not sure about commiting those changes yet.

I'll look into the next issue first:

{
  "error":{"code":0},
  "results":[{
    "action":"install",
    "beta":false,
    "betaIncoming":false,
    "error":{
      "code":268,
      "description":"dependent packages are not ready",
      "packages":{"Git":""},
      "unStartPkgList":""
     },
     "installReboot":false,
    "installing":true,
    "language":"enu",
    "last_stage":"prepare_install",
    "package":"gitea",
    "packageName":"Gitea",
    "spk":"/tmp/gitea/gitea-spk/gitea-1.18.5-linux-arm64.spk",
    "stage":"install_failed",
    "success":false,
    "username":"",
    "version":"1.18.5"
  }],
  "success":false
}

@stephengeorgewest
Copy link
Author

image
Huh, not sure how git turns into git-server

@stephengeorgewest
Copy link
Author

removing PKG_DEPS gets past the previous "dependent packages are not ready" error
https://help.synology.com/developer-guide/synology_package/pkgconx.html, DSM version is enforced in the INFO file anyway

New error:

{
  "error":{"code":0},
  "results":[{
    "action":"upgrade",
    "beta":false,
    "betaIncoming":false,
    "error":{"code":277,"description":"failed to run preupgrade script"},
    "finished":true,
    "installReboot":false,
    "installing":true,
    "language":"enu",
    "last_stage":"started",
    "package":"gitea",
    "packageName":"Gitea",
    "pid":28072,
    "scripts":[
      {"code":0,"message":"","type":"stop"},
      {"code":1,"message":"","type":"preupgrade"},
      {"code":0,"message":"","type":"start"}
    ],
    "spk":"/tmp/gitea/gitea-spk/gitea-1.18.5-linux-arm64.spk",
    "stage":"install_failed_and_started",
    "status":"running",
    "status_description":"translate from systemd status",
    "success":false,
    "username":"",
    "version":"1.17.3-10"}],
  "success":false
}

@stephengeorgewest
Copy link
Author

missed some files

New error, I think it fails earlier in the install steps now...

2023-03-25T11:05:59-06:00 DiskStation synopkg[23229]: pkginstall.cpp:1324 Failed to acquire resource after install Gitea [0x2000 bdb_get.c:40]
2023-03-25T11:06:00-06:00 DiskStation synopkg[23229]: pkginstall.cpp:1058 Failed to install package, spk=[/tmp/gitea/gitea-spk/gitea-1.17.4-linux-arm64.spk] result=
[{
  "action":"install",
  "beta":false,
  "betaIncoming":false,
  "broken_by":"install_corruption",
  "error":{"code":276,"description":"failed to acquire postinst worker","worker_msg":[]},
  "finished":true,
  "installReboot":false,
  "installing":true,
  "language":"enu",
  "last_stage":"postreplace",
  "package":"Gitea",
  "packageName":"Gitea",
  "pid":23229,
  "scripts":[
    {"code":0,"message":"","type":"preinst"},
    {"code":0,"message":"","type":"postinst"}
  ],
  "spk":"/tmp/gitea/gitea-spk/gitea-1.17.4-linux-arm64.spk",
  "stage":"install_failed",
  "status":"broken",
  "status_code":150,
  "status_description":"failed to complete installation",
  "success":false,
  "username":"",
  "version":"1.17.4"
}]

@stephengeorgewest
Copy link
Author

"copy all files from synocommunity spk download", probably should have done that once I started having problems. I didn't think so much would change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant