Bug#421893: libtag unnecessarily opens files read-write which fails on read-only smb shares

2007-05-03 Thread Adeodato Simó
* Stefan [Thu, 03 May 2007 12:55:28 +0200]: > Hello Adeodato, > > (Christopher is not actively maintaining the package anymore.) > > I'm reluctant to include any patches that don't come directly from > > upstream. Scott mentions that there is some kind of fix commited in SVN; > > if he can point

Bug#421893: libtag unnecessarily opens files read-write which fails on read-only smb shares

2007-05-03 Thread Stefan
Hello Adeodato, > (Christopher is not actively maintaining the package anymore.) > I'm reluctant to include any patches that don't come directly from > upstream. Scott mentions that there is some kind of fix commited in SVN; > if he can point me to the relevant commits, I can include that instead.

Bug#421893: libtag unnecessarily opens files read-write which fails on read-only smb shares

2007-05-03 Thread Adeodato Simó
* Stefan [Thu, 03 May 2007 12:04:37 +0200]: > Maybe this fix could be included in Debian, Christopher? (Christopher is not actively maintaining the package anymore.) I'm reluctant to include any patches that don't come directly from upstream. Scott mentions that there is some kind of fix commited

Bug#421893: libtag unnecessarily opens files read-write which fails on read-only smb shares

2007-05-03 Thread Stefan
Hello Scott, > That would also require an API change that would break all existing > applications. But there is already a workaround in the SVN version (it > just tries the fopen() call directly and sees if it succeeds). > > -Scott thanks for your answer. I see the problem, I only had a (maybe i

Bug#421893: libtag unnecessarily opens files read-write which fails on read-only smb shares

2007-05-02 Thread Stefan
Package: libtag1c2a Version: 1.4-4 Severity: important --- Please enter the report below this line. --- Hello Christopher, hello Scott, since I could think Amarok had a problem indexing my music collection from a Samba share. Now I looked into this problem and found the following: https://