Thousands of Sikh pilgrims from across the globe gathered in the Nankana Sahib district of Punjab to celebrate the 552nd birth anniversary of Baba Guru Nanak, the founder of their religion.
The 10-day celebrations began on Wednesday in Nankana Sahib – the birthplace of Baba Guru Nanak with Akhand Path, a reading of 1,430 pages of the holy book of Sikhism, the Granth Sahib.
Pakistan is home to some of the most important pilgrimage sites for Sikhs. They include the birthplace of Baba Guru Nanak, who was born in 1469, Kartarpur Sahib Gurdwara, and Gurdwara Panja Sahib in Hasan Abdal.
Read Opening of Kartarpur Corridor good development: FM Qureshi
To participate in the celebrations, thousands of Sikh yatrees reached Pakistan from India through the Wagah border crossing. The Pakistan High Commission in New Delhi issued 3,000 visas to the pilgrims, whereas New Delhi reopened the visa-free Kartarpur crossing.
Kartarpur crossing was opened in November 2019 but it was shut last year due to the coronavirus pandemic. Pakistan reopened the corridor for the Sikhs but New Delhi delayed its permission until this week.
Shiromani Gurdwara Parbandhak Committee Dehli leader Sardar Balvinder Singh told the media on arrival in Pakistan that the Sikh yatrees were contented with the opening of the Kartarpur Corridor, and thanked Pakistan for the protection of Gurdwaras in Pakistan.
Also read Indian govt decides to reopen Kartarpur Corridor for Sikh pilgrims
Foreign Minister Shah Mahmood Qureshi extended a warm welcome to the Sikh pilgrims in a statement issued in Islamabad. “Pakistan looks forward to welcoming Sikh pilgrims visiting Gurdwara Darbar Sahib through the Kartarpur Corridor from November 17,” he said.
Qureshi added that Pakistan had reopened the Kartarpur Corridor on June 29, 2020, after a temporary suspension of about three months due to pandemic. However, India kept the corridor closed from its side for nearly 20 months.
Agencies
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ