Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home/mpafbwbr24jp/public_html/wp-includes/functions.php on line 6085

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/mpafbwbr24jp/public_html/wp-includes/functions.php on line 6085

Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home/mpafbwbr24jp/public_html/wp-includes/functions.php on line 6085

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/mpafbwbr24jp/public_html/wp-includes/functions.php on line 6085

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/mpafbwbr24jp/public_html/wp-includes/functions.php on line 6085

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/mpafbwbr24jp/public_html/wp-includes/functions.php on line 6085

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `init` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/mpafbwbr24jp/public_html/wp-includes/functions.php on line 6085
Somalia and Somaliland sign agreement in Djibouti - Al Jasiira News
Site icon Al Jasiira News

Somalia and Somaliland sign agreement in Djibouti

Al Jasiira News
Somalia and Somaliland sign agreement in Djibouti

The discussions between the Somalia and Somaliland technical committees in Djibouti have concluded with the parties agreeing on some points.

The Somalia government and Somaliland have agreed on five points, which are assigned to three sub-committees to work on these issues.

The agreement was read by Djiboutian Foreign Minister Mahmoud Ali Youssouf to the media:

1 – How to proceed to future meetings, beautifully and purposefully

2 – To rebuild mutual trust.

3 – Implementation of the agreements reached in previous conferences that were not implemented, such as International Financial Assistance and Humanitarian Assistance; will host Djibouti.

4 – Both countries  have issued a committee to discuss the Air, which will convene in Djibouti within 15 days.

5 – Developed by a third committee to work together on security issues.

A joint technical committee was also appointed at the ministerial level, and will meet in Djibouti for 45 days to evaluate the performance of the sub committees.

somalia signed the agreement with Interior Minister Abdi Mohamed Sabriye, while Somaliland signed Yassin Haji Mohamud Farato as the Minister of Foreign Affairs.


      

Exit mobile version