Skip to main content

Likud Source Reportedly Says Netanyahu May Accept Second Turn in Rotation With Eisenkot

An unnamed Likud source reportedly says Prime Minister Benjamin Netanyahu could accept serving after Yashar chairman Gadi Eisenkot in a rotation arrangement if talks on a unity government begin and reach an agreement. The assessment, published Wednesday morning, envisages Eisenkot taking the first turn as prime minister, followed by Netanyahu. The source said Netanyahu still holds that he should head the government. In the source’s assessment, taking the second turn could nevertheless put Netanyahu in office as prime minister when the next Israeli election is held. Previous assessments attributed to Likud figures had placed Netanyahu first in a rotation and Eisenkot second. On November 16, Netanyahu said a national unity government must include parties that regard Israel as the state of the Jewish people. “In any government that is formed, we will go together with our Haredi partners…,” Netanyahu said in his official statement, translated from Hebrew. He also said the status of Torah students would be regulated through a law agreed with those partners. He called a national unity government the only government capable of dealing with the challenges facing Israel.

Sources

Benjamin NetanyahuSource Language: HebrewOpens in a new tab.Secondary sources:1

People in this story

Courtroom-sketch editorial illustration of the Knesset building in Jerusalem, shown as archival institutional context for government-formation speculation

Commentary

Add Your Voice
Loading comments…

Related articles

  1. Bennett Reportedly Pushes for Unity Government in Talks With Bloc Leaders
  2. Netanyahu Calls for Unity Government and Agreed Law on Torah Students
  3. Likud Accuses Eisenkot and Left Bloc of Blocking a Unity Government
  4. Zohar Says Eisenkot Rejects Unity and Hopes Coalition Effort Fails
  5. Netanyahu Urges Eisenkot to Hold Unity Talks Without Preconditions

Voices

Write about thisPost a clip

Something went wrong

We couldn't complete that action. Check your connection and try again.