<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Permissions in pynrfjprog are broken</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/85616/permissions-in-pynrfjprog-are-broken</link><description>Hello, we came across a recurring issue: 
 There are no executable permission for Linux + macOS for the packed binary: 
 
 jlinkarm_nrf_worker_linux 
 jlinkarm_nrf_worker_osx 
 
 The issue was fixed in pynrfjprog v10.15.2 , but returned back in v10.15</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 24 May 2022 18:51:14 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/85616/permissions-in-pynrfjprog-are-broken" /><item><title>RE: Permissions in pynrfjprog are broken</title><link>https://devzone.nordicsemi.com/thread/369371?ContentTypeID=1</link><pubDate>Tue, 24 May 2022 18:51:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ec9aa7b4-6e9e-4f32-a7e6-6d326ada516e</guid><dc:creator>hubpav</dc:creator><description>&lt;p&gt;Re-reading this discussion again, I think there is a misunderstanding between us. I wanted to set executable bit just to these two binaries listed in my original report:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;jlinkarm_nrf_worker_linux&lt;/li&gt;
&lt;li&gt;jlinkarm_nrf_worker_osx&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I did not intend to give executable bits on all files in the folder - of course, that would be a plain wrong approach. Can you please re-evaluate this thread and come back to me? Thanks. P.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Permissions in pynrfjprog are broken</title><link>https://devzone.nordicsemi.com/thread/361342?ContentTypeID=1</link><pubDate>Sat, 02 Apr 2022 05:52:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d7df9e48-027b-4147-99f6-f12094dc07d8</guid><dc:creator>hubpav</dc:creator><description>&lt;p&gt;Thanks for the feedback, though I do not understand why is it undesirable? There is an obvious issue because the library calls `exec` system call on one of the binaries&amp;nbsp;inside your package but that cannot be executed. The system call fails on it and your package is unusable on both Linux and macOS. It is a serious deployment bug.&lt;/p&gt;
&lt;p&gt;You have fixed the issue in&amp;nbsp;v10.15.2 but&amp;nbsp;re-introduced this&amp;nbsp;in the next version.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Permissions in pynrfjprog are broken</title><link>https://devzone.nordicsemi.com/thread/357463?ContentTypeID=1</link><pubDate>Thu, 10 Mar 2022 15:00:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cc4fc853-1e24-4f7f-bceb-b67d79bea4ba</guid><dc:creator>msliv</dc:creator><description>&lt;p&gt;I can confirm this issue. Giving up 755 permission to all files in lib_x64 directory removes an issue. However this is undesirable to give such an access to files.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Permissions in pynrfjprog are broken</title><link>https://devzone.nordicsemi.com/thread/357456?ContentTypeID=1</link><pubDate>Thu, 10 Mar 2022 14:50:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:41465e6c-d033-44d2-8f69-b090f4ef6fea</guid><dc:creator>Priyanka</dc:creator><description>&lt;p&gt;Hi Pavel,&lt;/p&gt;
&lt;p&gt;Thank you very much for informing and I have alerted the experts regarding the issue. I will inform you as soon as I get an update.&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Priyanka&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>