Bug#531538: another dangling symlink

2009-07-17 Thread Savvas Radevic
I was informed that Rafael Laboissiere, the maintainer, is not involved in Debian development. This package is too import for me to play with (since I'm still a beginner at packaging). If you know someone that wishes to take over, please do! Also, it's too risky to include a patch for older

Bug#531538: another dangling symlink

2009-07-17 Thread Savvas Radevic
I was informed that Rafael Laboissiere, the maintainer, is not involved in Debian development. This package is too import for me to play with (since I'm still a beginner at packaging). If you know someone that wishes to take over, please do! Typos: I was informed that Rafael Laboissiere, the

Bug#531538: another dangling symlink

2009-06-03 Thread Raphael Hertzog
On Tue, 02 Jun 2009, Rafael Laboissiere wrote: The libmtp7 package contains the file /etc/udev/rules.d/libmtp7.rules. This file is not touched by libmtp8, AFAIK. On the other hand, libmtp5 seems to be affected by the following offending code in postinst: if dpkg --compare-versions $2

Bug#531538: another dangling symlink

2009-06-03 Thread Rafael Laboissiere
* Raphael Hertzog hert...@debian.org [2009-06-03 08:54]: On Tue, 02 Jun 2009, Rafael Laboissiere wrote: The libmtp7 package contains the file /etc/udev/rules.d/libmtp7.rules. This file is not touched by libmtp8, AFAIK. On the other hand, libmtp5 seems to be affected by the following

Bug#531538: another dangling symlink

2009-06-03 Thread Savvas Radevic
@Sean: thank you for the tip, didn't know that! :) Sean, can you reply with the output of: apt-cache policy libmtp5 libmtp6 apt-cache rdepends libmtp5 libmtp6 I really need to see where they came from, if they were manually installed (or from another source) and if any packages depend on it.

Bug#531538: another dangling symlink

2009-06-03 Thread Savvas Radevic
Rafael, you are right, it probably will. But I'm worried about these: (1) Is the remaining /etc/udev/libmtp.rules (and symlink /etc/udev/rules.d/libmtp.rules) going to affect libmtp8? We'll have to ask upstream I guess.

Bug#531538: another dangling symlink

2009-06-03 Thread sean finney
hi savvas, On Wed, Jun 03, 2009 at 11:13:11AM +0200, Savvas Radevic wrote: @Sean: thank you for the tip, didn't know that! :) Sean, can you reply with the output of: apt-cache policy libmtp5 libmtp6 libmtp5: Installed: (none) Candidate: (none) Version table: 0.1.5-2 0 100

Bug#531538: another dangling symlink

2009-06-03 Thread Rafael Laboissiere
* Savvas Radevic vice...@gmail.com [2009-06-03 12:51]: Rafael, you are right, it probably will. But I'm worried about these: (1) Is the remaining /etc/udev/libmtp.rules (and symlink /etc/udev/rules.d/libmtp.rules) going to affect libmtp8? We'll have to ask upstream I guess.

Bug#531538: another dangling symlink

2009-06-03 Thread Savvas Radevic
CC'ed the bug report 2009/6/3 Savvas Radevic vice...@gmail.com: Sean, thank you, very helpful! Rafael: That said, i am wondering why the libmtp.rules files should be versioned, as we are doing currently.  Perhaps, the 45-libmpt8.rules files would work just fine with previous versions (5, 6,

Bug#531538: another dangling symlink

2009-06-02 Thread Savvas Radevic
That's quite an old package, I don't see it in the supported releases: http://packages.debian.org/libmtp5 Can you explain how did this happen? I can only assume that you upgraded, but from which older release to which one, using which commands? :) Also, reply with the output of: apt-cache policy

Bug#531538: another dangling symlink

2009-06-02 Thread Savvas Radevic
I'm not completely sure, but I think the package is missing Conflicts and Replaces for older libmtp* packages? Something like: Conflicts: libmtp7, libmtp6, libmtp5 Replaces: libmtp7, libmtp6, libmtp5 ..in debian/control.in and debian/control files. Thoughts? -- To UNSUBSCRIBE, email to

Bug#531538: another dangling symlink

2009-06-02 Thread Rafael Laboissiere
* Savvas Radevic vice...@gmail.com [2009-06-02 12:50]: I'm not completely sure, but I think the package is missing Conflicts and Replaces for older libmtp* packages? Something like: Conflicts: libmtp7, libmtp6, libmtp5 Replaces: libmtp7, libmtp6, libmtp5 ..in debian/control.in and

Bug#531538: another dangling symlink

2009-06-02 Thread Savvas Radevic
I think this is related to bug #525094 - the reporter probably has not updated to the latest available package: libmtp8 0.3.7-7 Sean, is my assumption true? Ah wait, now I get it. Rafael, is Breaks allowed on older libmtp* packages? It seems like libmtp5-7 might require the older rules (not

Bug#531538: another dangling symlink

2009-06-02 Thread Savvas Radevic
In sum: never, ever try to implement Conflicts/Replaces as proposed above. Noted! :) I think this is related to bug #525094 - the reporter probably has not updated to the latest available package: libmtp8 0.3.7-7 Sean, is my assumption true? -- To UNSUBSCRIBE, email to

Bug#531538: another dangling symlink

2009-06-02 Thread Rafael Laboissiere
[Cc:ing to the BTS, this time, sorry.] * Savvas Radevic vice...@gmail.com [2009-06-02 15:51]: Ah wait, now I get it. Rafael, is Breaks allowed on older libmtp* packages? No, for the same reason Replaces is not allowed. It seems like libmtp5-7 might require the older rules (not in /lib) The

Bug#531538: another dangling symlink

2009-06-02 Thread Savvas Radevic
* Savvas Radevic vice...@gmail.com [2009-06-02 15:51]: Ah wait, now I get it. Rafael, is Breaks allowed on older libmtp* packages? No, for the same reason Replaces is not allowed. It seems like libmtp5-7 might require the older rules (not in /lib) The libmtp7 package contains the file

Bug#531538: another dangling symlink

2009-06-02 Thread Savvas Radevic
2009/6/2 Savvas Radevic vice...@gmail.com: ..which is removed by debian/libmtp.postinst.in: rm -f /etc/udev/libmtp.rules Correction: ..which is removed by debian/libmtp.preinst.in: rm -f /etc/udev/libmtp.rules -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a

Bug#531538: another dangling symlink

2009-06-02 Thread sean finney
hiya, On Tue, Jun 02, 2009 at 03:49:42PM +0200, Savvas Radevic wrote: I think this is related to bug #525094 - the reporter probably has not updated to the latest available package: libmtp8 0.3.7-7 Sean, is my assumption true? note sure for the last email whether you still needed this, but