IoK police arrest newspaper publisher in midnight raid

Daily Afaaq publisher taken into custody from his Srinagar home


Reuters June 25, 2019
Ghulam Jeelani Qadri, a journalist and the publisher of the Urdu-language newspaper Daily Afaaq, leaves after a court granted him bail, in Srinagar, June 25, 2019. PHOTO: REUTERS

SRINAGAR: Police arrested the publisher of one of the most widely read newspapers in Indian occupied Kashmir (IoK) in a midnight raid over a decades-old case, the police and his brother said on Tuesday, highlighting the difficulties facing media in the region.

Ghulam Jeelani Qadri, 62, a journalist and the publisher of the Urdu-language newspaper Daily Afaaq, was arrested at his home in the region’s main city of Srinagar, half an hour before midnight on Monday.

“It is harassment,” his brother, Mohammad Morifat Qadri said. “Why is a 1993 arrest warrant executed today? And why against him only?”

Qadri was released on bail after a court appearance on Tuesday.

The case dates from 1990, when Qadri was one of nine journalists to publish a statement by a group fighting against Indian occupation in the region. An arrest warrant for Qadri was issued in 1993, but it was never served.

Hurriyat leaders agree on talks with Indian government

Qadri had visited the police station involved in the arrest multiple times since the warrant was issued, most recently in 2017 to apply for a passport, his brother added.

Asked why Qadri was arrested at night, Srinagar police chief Haseeb Mughal  said that police were busy during the day.

The Kashmir Union of Working Journalists condemned the arrest, saying it seemed to be aimed at muzzling the press.

“Qadri was attending the office.

India is one of the world’s worst places to be a journalist, ranked 138th among 180 countries on the press freedom index of international monitor Reporters Without Borders, with conditions in IoK cited as a key reason.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ