Bug#514294: lurker && kde4 && mimelib
On Sunday 19 April 2009 04:48:49 Jonas Meurer wrote: > I now have five different versions of mimelib available: > - your debian package from people.debian.org/~bdefreese > - the kdepim3 source package from debian/squeeze > - the source tarball from ftp.crocodile.org > - the source tarball from sourceforge.net/projects/lurker > - the svn snaphost from svn.kde.org > > I could just pick up one, finish the packaging, and upload it. But to be > honest, I would like to first sort out why all these versions do have tens > of thousands of changes each. Mimelib was abandoned by its maintainer around 10 years ago, and people have had different needs. No effort has been made to try unify these. > kdepim3 is gone from debian/unstable now, so it shouldn't be a problem > to upload source package mimelib with binary packages libmimelib1 and > libmimelib1-dev any more. > > The libmimelib1c2a package has libmimelib.so.1 as soname. If I want to > keep the soname, I'll have to ensure abi compatibility. How can I check > that in case that I use a different source than kdepim3? If you want to keep same packagename (and SONAME), you need to check thoroughly that is having the same ABI. You can among other check with objdump wether it is the same symbols that are exported. You can also choose to name it differently, and then you just have to make sure that lurker works. /Sune -- I cannot telnet to the URL to the microprocessor, how does it work? You either can never save on a forward, or cannot install a SIMM over the command prompt in order to log on a 4-bit SCSI line. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514294: lurker && kde4 && mimelib
Hey Barry, On 07/04/2009 Barry deFreese wrote: >>> On Tuesday 17 March 2009 18:29:14 Jonas Meurer wrote: >> i'm willing to maintain it in debian, but some issues remain unclear for >> me, and i'dd highly appreciate your options about them: >> >> - it seems like mimelib doesn't have any real upstream anymore. kdepim >> contains it, and several stanalone tarballs can be found anywhere in >> the web. Barry, how did you find the tarball at ftp.crocodile.org? or >> did you build it on your own? all mimelib versions i can find via >> google (from kde svn, from lurkers sourceforge page, from different >> linux distributions) slightly differ from each other, and i'm really >> unsure about which one is the most recent one. >> for example, i didn't find any mimelib version where the documentation >> files do contain (VCS?) $Revision and $Date entries. Only your version >> from ftp.crocodile.org does have them. >> > Hi Jonas, my apologies, I thought I had responded to your previous > e-mail. I ran into a similar situation. I basically googled around > based on the package and the author. There are mutiple versions flying > around but they are all based on the same lib from the same author. The > ftp.crocodile.org was the most "original" I could find. Then I added > patches based on the modifications that were made in the mimelib stuff > in the kdepim package. I just compared different versions and I have to say it's really a mess. No version is nearly similar to another one. I don't even understand how you built the mimelib packages at people.debian.org from the tarball at ftp.crocodile.org. The diff between your and the ftp.crocodile.org tarball has more than 1 lines. I now have five different versions of mimelib available: - your debian package from people.debian.org/~bdefreese - the kdepim3 source package from debian/squeeze - the source tarball from ftp.crocodile.org - the source tarball from sourceforge.net/projects/lurker - the svn snaphost from svn.kde.org I could just pick up one, finish the packaging, and upload it. But to be honest, I would like to first sort out why all these versions do have tens of thousands of changes each. I don't expect from you to help me with this, the only thing where you could help is: how exactly did you put the package at people.debian.org together? Is it really based on the tarball from ftp.crocodile.org? >> - when I build mimelib from a seperate source-package, how to coordinate >> this with existing mimelib packages from kdepim sources? sure, I'll >> have to conflict and replace them, but how to name the library package? >> and do I need to introduce a new SONAME? >> another possibility would be to stop building mimelib packages from >> kdepim sources and keep both soname and binary package names the same. >> >> > I'm certainly no expert on library packaging yet but I would name the > library package according to the soname if possible. (I think I did that > in my package). kdepim is going to be removed isn't it? If not, we > have a larger problem as mimelib shouldn't be a seperate package and > shipped in kdepim. If the package name and soname differ from the > kdepim one then yes, adding a Provides and Replaces (and possibly even > Conflicts) would be appropriate. Unfortunately, as you mention I can't > even install or build the kdepim mimelib now so I can't even tell you > what the current soname is. :( kdepim3 is gone from debian/unstable now, so it shouldn't be a problem to upload source package mimelib with binary packages libmimelib1 and libmimelib1-dev any more. The libmimelib1c2a package has libmimelib.so.1 as soname. If I want to keep the soname, I'll have to ensure abi compatibility. How can I check that in case that I use a different source than kdepim3? I guess most changes from the other tarballs are just minor fixes, but how can I go sure? greetings, jonas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514294: lurker && kde4 && mimelib
Jonas Meurer wrote: Hey Sune and Barry, I sent you this mail some days ago, and still didn't get a response. Now that kde4 is in unstable and lurker ftbfs I'd really fix the issue, but I don't know how to proceed. A comment from you on the questions below would be very valuable to me. On 17/03/2009 Sune Vuorela wrote: On Tuesday 17 March 2009 18:29:14 Jonas Meurer wrote: on final issue remains: I saw that the package build-depends on kdelibs4, which is from kde3. But I thought that the bugreport was filed by Sune to get rid of kde3 in the long term. It is still unclear wether we can get rid of the kde3 libraries for squeeze. I hope it is, but I don't think it is realistic. But mimelib should be enough self-containing to not require any parts of KDE - and mimelib don't expose any parts of kde abi to the outside. It should be doable, it is just a matter of doing it. Is this build dependency required at all? An if it is, how do you intend to workaround it once kde3 will be removed from debian/unstable? I managed to get rid of the kdelibs build-dependency by simply replacing #else # include # define DW_EXPORT KDE_EXPORT #endif with #else # define DW_EXPORT #endif in mimelib/config.h. So indeed a mimelib source package which is independent from any kde libraries shouldn't be a problem. i'm willing to maintain it in debian, but some issues remain unclear for me, and i'dd highly appreciate your options about them: - it seems like mimelib doesn't have any real upstream anymore. kdepim contains it, and several stanalone tarballs can be found anywhere in the web. Barry, how did you find the tarball at ftp.crocodile.org? or did you build it on your own? all mimelib versions i can find via google (from kde svn, from lurkers sourceforge page, from different linux distributions) slightly differ from each other, and i'm really unsure about which one is the most recent one. for example, i didn't find any mimelib version where the documentation files do contain (VCS?) $Revision and $Date entries. Only your version from ftp.crocodile.org does have them. Hi Jonas, my apologies, I thought I had responded to your previous e-mail. I ran into a similar situation. I basically googled around based on the package and the author. There are mutiple versions flying around but they are all based on the same lib from the same author. The ftp.crocodile.org was the most "original" I could find. Then I added patches based on the modifications that were made in the mimelib stuff in the kdepim package. - when I build mimelib from a seperate source-package, how to coordinate this with existing mimelib packages from kdepim sources? sure, I'll have to conflict and replace them, but how to name the library package? and do I need to introduce a new SONAME? another possibility would be to stop building mimelib packages from kdepim sources and keep both soname and binary package names the same. I'm certainly no expert on library packaging yet but I would name the library package according to the soname if possible. (I think I did that in my package). kdepim is going to be removed isn't it? If not, we have a larger problem as mimelib shouldn't be a seperate package and shipped in kdepim. If the package name and soname differ from the kdepim one then yes, adding a Provides and Replaces (and possibly even Conflicts) would be appropriate. Unfortunately, as you mention I can't even install or build the kdepim mimelib now so I can't even tell you what the current soname is. :( sorry if these questions do sound dump, but i don't have any experience with library packaging yet :-/ greetings, jonas I hope that helps a little. Thanks, Barry -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514294: lurker && kde4 && mimelib
Hey Sune and Barry, I sent you this mail some days ago, and still didn't get a response. Now that kde4 is in unstable and lurker ftbfs I'd really fix the issue, but I don't know how to proceed. A comment from you on the questions below would be very valuable to me. On 17/03/2009 Sune Vuorela wrote: > On Tuesday 17 March 2009 18:29:14 Jonas Meurer wrote: > > on final issue remains: > > I saw that the package build-depends on kdelibs4, which is from kde3. > > But I thought that the bugreport was filed by Sune to get rid of kde3 in > > the long term. > > It is still unclear wether we can get rid of the kde3 libraries for squeeze. > I > hope it is, but I don't think it is realistic. > > But mimelib should be enough self-containing to not require any parts of KDE > - > and mimelib don't expose any parts of kde abi to the outside. It should be > doable, it is just a matter of doing it. > > > Is this build dependency required at all? An if it is, how do you intend > > to workaround it once kde3 will be removed from debian/unstable? I managed to get rid of the kdelibs build-dependency by simply replacing #else # include # define DW_EXPORT KDE_EXPORT #endif with #else # define DW_EXPORT #endif in mimelib/config.h. So indeed a mimelib source package which is independent from any kde libraries shouldn't be a problem. i'm willing to maintain it in debian, but some issues remain unclear for me, and i'dd highly appreciate your options about them: - it seems like mimelib doesn't have any real upstream anymore. kdepim contains it, and several stanalone tarballs can be found anywhere in the web. Barry, how did you find the tarball at ftp.crocodile.org? or did you build it on your own? all mimelib versions i can find via google (from kde svn, from lurkers sourceforge page, from different linux distributions) slightly differ from each other, and i'm really unsure about which one is the most recent one. for example, i didn't find any mimelib version where the documentation files do contain (VCS?) $Revision and $Date entries. Only your version from ftp.crocodile.org does have them. - when I build mimelib from a seperate source-package, how to coordinate this with existing mimelib packages from kdepim sources? sure, I'll have to conflict and replace them, but how to name the library package? and do I need to introduce a new SONAME? another possibility would be to stop building mimelib packages from kdepim sources and keep both soname and binary package names the same. sorry if these questions do sound dump, but i don't have any experience with library packaging yet :-/ greetings, jonas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514294: lurker && kde4 && mimelib
Hi! KDE4 is now in unstable ; lurker is broken. Just for your information. /Sune -- I cannot forward to the terminale, how does it work? From Mac XP you neither can ever reset the shell, nor must get access over the port 38 to the case to a 3D periferic for renaming a coaxial SMTP login. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514294: lurker && kde4 && mimelib
Hello, On 17/03/2009 Sune Vuorela wrote: > On Tuesday 17 March 2009 18:29:14 Jonas Meurer wrote: > > on final issue remains: > > I saw that the package build-depends on kdelibs4, which is from kde3. > > But I thought that the bugreport was filed by Sune to get rid of kde3 in > > the long term. > > It is still unclear wether we can get rid of the kde3 libraries for squeeze. > I > hope it is, but I don't think it is realistic. > > But mimelib should be enough self-containing to not require any parts of KDE > - > and mimelib don't expose any parts of kde abi to the outside. It should be > doable, it is just a matter of doing it. > > > Is this build dependency required at all? An if it is, how do you intend > > to workaround it once kde3 will be removed from debian/unstable? I managed to get rid of the kdelibs build-dependency by simply replacing #else # include # define DW_EXPORT KDE_EXPORT #endif with #else # define DW_EXPORT #endif in mimelib/config.h. So indeed a mimelib source package which is independent from any kde libraries shouldn't be a problem. i'm willing to maintain it in debian, but some issues remain unclear for me, and i'dd highly appreciate your options about them: - it seems like mimelib doesn't have any real upstream anymore. kdepim contains it, and several stanalone tarballs can be found anywhere in the web. Barry, how did you find the tarball at ftp.crocodile.org? or did you build it on your own? all mimelib versions i can find via google (from kde svn, from lurkers sourceforge page, from different linux distributions) slightly differ from each other, and i'm really unsure about which one is the most recent one. for example, i didn't find any mimelib version where the documentation files do contain (VCS?) $Revision and $Date entries. Only your version from ftp.crocodile.org does have them. - when I build mimelib from a seperate source-package, how to coordinate this with existing mimelib packages from kdepim sources? sure, I'll have to conflict and replace them, but how to name the library package? and do I need to introduce a new SONAME? another possibility would be to stop building mimelib packages from kdepim sources and keep both soname and binary package names the same. sorry if these questions do sound dump, but i don't have any experience with library packaging yet :-/ greetings, jonas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514294: lurker && kde4 && mimelib
On Tuesday 17 March 2009 18:29:14 Jonas Meurer wrote: > on final issue remains: > I saw that the package build-depends on kdelibs4, which is from kde3. > But I thought that the bugreport was filed by Sune to get rid of kde3 in > the long term. It is still unclear wether we can get rid of the kde3 libraries for squeeze. I hope it is, but I don't think it is realistic. But mimelib should be enough self-containing to not require any parts of KDE - and mimelib don't expose any parts of kde abi to the outside. It should be doable, it is just a matter of doing it. > Is this build dependency required at all? An if it is, how do you intend > to workaround it once kde3 will be removed from debian/unstable? /Sune -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514294: lurker && kde4 && mimelib
Jonas Meurer wrote: Hey Barry, On 17/03/2009 Barry deFreese wrote: A while back Sune asked me to look at ripping mimelib out. I found the seperated upstream source for it and applied the same patches that kdepim uses. I have put the source package here: http://people.debian.org/~bdefreese/mimelib/ Of course it would mean maintaining another package but you should be able to build/link against it. Thanks for the pointer. Packaging mimelib as a seperate source package in debian seems like a good solution to bug#514294. Do you intend to upload it soon? on final issue remains: I saw that the package build-depends on kdelibs4, which is from kde3. But I thought that the bugreport was filed by Sune to get rid of kde3 in the long term. Is this build dependency required at all? An if it is, how do you intend to workaround it once kde3 will be removed from debian/unstable? greetings, jonas Hmm, probably not, that was probably a mistake on my part. I won't be uploading it at all as I really have no interest in maintaining it, I was just trying to help out. It should be an easy package to maintain as upstream is pretty much inactive I think. Thanks, Barry -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514294: lurker && kde4 && mimelib
Hey Barry, On 17/03/2009 Barry deFreese wrote: > A while back Sune asked me to look at ripping mimelib out. I found the > seperated upstream source for it and applied the same patches that > kdepim uses. > > I have put the source package here: > http://people.debian.org/~bdefreese/mimelib/ > > Of course it would mean maintaining another package but you should be > able to build/link against it. Thanks for the pointer. Packaging mimelib as a seperate source package in debian seems like a good solution to bug#514294. Do you intend to upload it soon? on final issue remains: I saw that the package build-depends on kdelibs4, which is from kde3. But I thought that the bugreport was filed by Sune to get rid of kde3 in the long term. Is this build dependency required at all? An if it is, how do you intend to workaround it once kde3 will be removed from debian/unstable? greetings, jonas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514294: lurker && kde4 && mimelib
Hi, A while back Sune asked me to look at ripping mimelib out. I found the seperated upstream source for it and applied the same patches that kdepim uses. I have put the source package here: http://people.debian.org/~bdefreese/mimelib/ Of course it would mean maintaining another package but you should be able to build/link against it. Hope it helps. Thanks, Barry deFreese Debian QA -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
