F_bintar do not have child builders

s_packages is useless in this context, bintar is already producing
a standalone package used for release

s_bigtest - was never triggered for bintar, if one looks in the history.
If there isn't a special need for it, I suggest removing it to avoid confusion

master-docker-nonstandard/master.cfg

@@ -1417,37 +1417,6 @@ f_bintar.addStep(
 )
 f_bintar.addStep(saveLogs())
 
-## trigger packages
-f_bintar.addStep(
-    steps.Trigger(
-        schedulerNames=["s_packages"],
-        waitForFinish=False,
-        updateSourceStamp=False,
-        alwaysRun=True,
-        set_properties={
-            "parentbuildername": Property("buildername"),
-            "tarbuildnum": Property("tarbuildnum"),
-            "mariadb_version": Property("mariadb_version"),
-            "master_branch": Property("master_branch"),
-        },
-        doStepIf=hasAutobake,
-    )
-)
-## trigger bigtest
-f_bintar.addStep(
-    steps.Trigger(
-        schedulerNames=["s_bigtest"],
-        waitForFinish=False,
-        updateSourceStamp=False,
-        set_properties={
-            "parentbuildername": Property("buildername"),
-            "tarbuildnum": Property("tarbuildnum"),
-            "mariadb_version": Property("mariadb_version"),
-            "master_branch": Property("master_branch"),
-        },
-        doStepIf=hasBigtest,
-    )
-)
 # create package and upload to master
 f_bintar.addStep(
     steps.SetPropertyFromCommand(