Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-hide-security-enhancer domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/tabadul/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the akismet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/tabadul/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the formidable domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/tabadul/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the formidable-pro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/tabadul/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-formidable-uikit-master domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/tabadul/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the iwp-client domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/tabadul/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the libyanspider-base domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/tabadul/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the google-site-kit domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/tabadul/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-2fa domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/tabadul/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-security-audit-log domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/tabadul/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-mail-smtp domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/tabadul/public_html/wp-includes/functions.php on line 6114
قوة حماية طرابلس تطالب بتوضيح أسباب تأخر تنفيذ اتفاق سرت – تبادل
Skip to main content
|

قوة حماية طرابلس تطالب بتوضيح أسباب تأخر تنفيذ اتفاق سرت

طالبت قـوة حـمـايـة طـرابـلـس رؤساء وأعضاء اللجنة العسكرية المشتركة 5+5 بتوضيح أسباب تأخير تنفيذ بنود اتفاق اللجنة العسكرية المشتركة بسرت المتعلق بوقف إطلاق النار. معربة عن استغرابها من هذا التأخير المتعمد تبعا لما ورد في بيانها على فيسبوك.

هذا وتساءلت قوة حماية طرابلس في بيانها “هل هناك أيادي خفية وراء هذا التأخير المتعمد ؟ ومن المستفيد من وراء كل هذا التأخير ؟” مضيفة “للأسف بنود أو نقاط اتفاق اللجنة، كانت واضحة وصريحة، وتصب في صالح الشعب وترضي جميع الأطراف، وكانت أهم النقاط التي لو طبقت لقطع الطريق أمام أي نزاع من الممكن أن يقع وذلك بتشكيل “قوة عسكرية مشتركة” من قبل لجنة إخلاء خطوط التماس، لتقوم بفتح الطريق وتأمينه للمواطنين، وتشرف على إبعاد الأسلحة الثقيلة من المدن، وترحيل “المرتزقة” خارج بلادنا.” 

ورجحت القوة أن الحوار المقام برعاية أممية بتونس، فشل ضمنيا، مشيرة إلى احتقان الشارع الليبي ضد سياسات الحكومتين نتيجة تعنت أغلب الأطراف.

مشاركة الخبر