debian:forky disabled across all Jenkinsfiles — re-enable once full stack is available

Open
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
debian, groovy

Research direction

Start with the commented debian:forky entries in the Jenkinsfiles and use the provided grep command to enumerate affected repositories. Verify the listed packages install and that multiflexi-cli and a representative multiflexi-abraflexi-revolut stack build pass on Forky. Done means uncommenting the entries and removing the disable comments across all affected Jenkinsfiles.

Written by the indexing model from the issue text.

Description

Summary

debian:forky (Debian 14) has been commented out in Jenkinsfiles across all VitexSoftware/MultiFlexi/SpojeNetIT repos. This issue tracks the conditions required to re-enable it.

Why it was disabled

Forky is still in the unstable/research-only phase. The full Debian package ecosystem is not yet available for Forky, causing cascading build and install failures:

  • multiflexi-common — not yet available/installable on Forky
  • php-symfony-dependency-injection — not installable
  • php-phplucidframe-console-table — not installable
  • php-symfony-yaml → replaced by php-yaml, but transitive deps still missing
  • Any package depending on multiflexi-cli (e.g. multiflexi-abraflexi-revolut) fails postinst because multiflexi-cli itself cannot be installed

These unmet dependency chains make Forky builds universally non-functional across the stack at this time.

Scope

debian:forky was commented out in ~211 Jenkinsfiles across all repos in May 2026. Each disabled entry includes an inline comment explaining the reason, for example:

// 'debian:forky', // Disabled: Forky is still unstable/research-only.
//                 // The full Debian package ecosystem is not yet available for Forky.
//                 // Re-enable once the stack builds cleanly for Forky.

Conditions to re-enable

Re-enable debian:forky in Jenkinsfiles once all of the following are true on Forky:

  • multiflexi-common is installable
  • php-symfony-dependency-injection is installable
  • php-phplucidframe-console-table is installable
  • multiflexi-cli builds and installs cleanly (postinst succeeds)
  • A representative stack build (e.g. multiflexi-abraflexi-revolut) passes on debian:forky end-to-end

How to re-enable

Once the above conditions are met, run a bulk search across repos:

grep -rl "debian:forky" */debian/Jenkinsfile | xargs grep -l "Disabled"

Then uncomment the 'debian:forky', lines and remove the disable comments.

Related commits

  • VitexSoftware/AbraFlexi-Revolut — forky disabled (multiflexi-cli postinst failure)
  • MultiFlexi/multiflexi-cli — forky disabled (multiflexi-common cascade)
  • ~209 other repos — bulk disable May 2026

Co-Authored-By: Claude Sonnet 4.6 noreply@anthropic.com

Dominant language
Groovy
Stars
6
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.