![jui f chief maulana fazlur rehman photo online file jui f chief maulana fazlur rehman photo online file](https://i.tribune.com.pk/media/images/fazlurrehmanonlinefile1636812891-0/fazlurrehmanonlinefile1636812891-0.jpg)
Jamiat Ulema-e-Islam Fazl (JUI-F) chief Maulana Fazlur Rehman has said that his party will restart work on China-Pakistan Economic Corridor (CPEC) once his party is voted to power.
Fazl also removed the inauguration plank of the Halka-DI Khan Motorway constructed under CPEC and held a large rally at Yark Interchange.
He was addressing the rally at Yark Interchange in DI Khan in connection with the local bodices’ polls despite the fact that Election Commission of Pakistan (ECP) and district administration had not allowed JUF-F rally in the district. Deputy Commissioner (DC) had turned down the JUI-F request for a public rally on February 5 and 7, terming it violation of the code of conduct as polling are scheduled for February 13.
Fazl blamed the current government of stopping work on a strategic project like CEPC.
He said that development of the backward areas is the priority of his party and blamed that announcing development package ahead of the election is like buying votes which is unjust but still practiced by the government.
He said that the contest was not between Kafil Nizami (JUI-F candidate) and Gandapur (PTI’s federal minister) but between the PTI and JUI-F, saying that those who would vote for bat would contribute towards the destruction of the country.
“In the three years of PTI rule a common man is unable to buy medicines,” he said, adding that holding the local government polls in two phases is aimed at turning the tide towards the PTI.
“We defeated them in the first phase and we will do it in the second phase too,” he said.
Fazl hit out at the PTI government and said that it introduced four mini budgets in three years of rule.
Published in The Express Tribune, February 6th, 2022.
COMMENTS (2)
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ