Re: Let's get the Lyx Debian pkg back in sync with upstream
On Fri, May 12, 2006 at 12:58:18PM +0200, Georg Baum wrote: Sven Hoexter wrote: Hi, I'll take a look at your changes aswell but aehm why do you need to compile with gcc/g++ 4.1? I believe that this is the default compiler in unstable. Not yet. At the moment it's still 4.0.3. Regarding g++ 4.1 I found this FTBFS bug in the Debian BTS http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357119 IIRC this is a boost bug that is fixed in 1.4.x. Ok. Sven -- If you won't forgive me the rest of my life Let me apologize while I'm still alive I know it's time to face all of my past mistakes [Less than Jake - Rest Of My Life]
Re: Let's get the Lyx Debian pkg back in sync with upstream
On Fri, May 12, 2006 at 03:12:43PM +0200, Charles de Miramon wrote: Sven Hoexter wrote: On Fri, May 12, 2006 at 11:29:15AM +0200, Charles de Miramon wrote: Hi, NOTE: I think it's getting quite off-topic here. IMHO wie should move the package related discussion to this mailinglist: http://lists.alioth.debian.org/mailman/listinfo/pkg-lyx-devel If you guys prefer to have it on the lyx mailinglist that's ok for me. Just wanted to ask before someone complains about off-topic traffic on a user list. I've started from Georg Baum's version but I made an ugly hack in debian/rules to force it to compile with gcc 4.1. I don't know how you should do it properly in Debian. I've updated the dependence fields also and made some little changes. IIRC setting CXX = g++-4.1 in the rules should work. I wanted something that would work for sarge and sid, so we could keep one file. A rule, saying on sarge use gcc 3.3 and on sid gcc 4.1 Indeed, that's ugly. A better way would be to force the unstable version to use g++ 4.1 (if realy needed) and then create a backport for backports.org that uses the default compiler or any other special compiler version needed. I'll take a look at your changes aswell but aehm why do you need to compile with gcc/g++ 4.1? A pointer to the thread would be enough so that I can catch up on that problem aswell. I've uploaded the total source package here : Thanks. (wow now I've at least 3 different versions to compare 8-) Sven -- If you won't forgive me the rest of my life Let me apologize while I'm still alive I know it's time to face all of my past mistakes [Less than Jake - Rest Of My Life]
Re: Let's get the Lyx Debian pkg back in sync with upstream
On Fri, May 12, 2006 at 12:58:18PM +0200, Georg Baum wrote: Sven Hoexter wrote: Hi, I'll take a look at your changes aswell but aehm why do you need to compile with gcc/g++ 4.1? I believe that this is the default compiler in unstable. Not yet. At the moment it's still 4.0.3. Regarding g++ 4.1 I found this FTBFS bug in the Debian BTS http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357119 IIRC this is a boost bug that is fixed in 1.4.x. Ok. Sven -- If you won't forgive me the rest of my life Let me apologize while I'm still alive I know it's time to face all of my past mistakes [Less than Jake - Rest Of My Life]
Re: Let's get the Lyx Debian pkg back in sync with upstream
On Fri, May 12, 2006 at 03:12:43PM +0200, Charles de Miramon wrote: Sven Hoexter wrote: On Fri, May 12, 2006 at 11:29:15AM +0200, Charles de Miramon wrote: Hi, NOTE: I think it's getting quite off-topic here. IMHO wie should move the package related discussion to this mailinglist: http://lists.alioth.debian.org/mailman/listinfo/pkg-lyx-devel If you guys prefer to have it on the lyx mailinglist that's ok for me. Just wanted to ask before someone complains about off-topic traffic on a user list. I've started from Georg Baum's version but I made an ugly hack in debian/rules to force it to compile with gcc 4.1. I don't know how you should do it properly in Debian. I've updated the dependence fields also and made some little changes. IIRC setting CXX = g++-4.1 in the rules should work. I wanted something that would work for sarge and sid, so we could keep one file. A rule, saying on sarge use gcc 3.3 and on sid gcc 4.1 Indeed, that's ugly. A better way would be to force the unstable version to use g++ 4.1 (if realy needed) and then create a backport for backports.org that uses the default compiler or any other special compiler version needed. I'll take a look at your changes aswell but aehm why do you need to compile with gcc/g++ 4.1? A pointer to the thread would be enough so that I can catch up on that problem aswell. I've uploaded the total source package here : Thanks. (wow now I've at least 3 different versions to compare 8-) Sven -- If you won't forgive me the rest of my life Let me apologize while I'm still alive I know it's time to face all of my past mistakes [Less than Jake - Rest Of My Life]
Re: Let's get the Lyx Debian pkg back in sync with upstream
On Fri, May 12, 2006 at 12:58:18PM +0200, Georg Baum wrote: > Sven Hoexter wrote: Hi, > > I'll take a look at your changes aswell but aehm why do you need to > > compile with gcc/g++ 4.1? > > I believe that this is the default compiler in unstable. Not yet. At the moment it's still 4.0.3. > > Regarding g++ 4.1 I found this FTBFS bug in the Debian BTS > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357119 > > IIRC this is a boost bug that is fixed in 1.4.x. Ok. Sven -- If you won't forgive me the rest of my life Let me apologize while I'm still alive I know it's time to face all of my past mistakes [Less than Jake - Rest Of My Life]
Re: Let's get the Lyx Debian pkg back in sync with upstream
On Fri, May 12, 2006 at 03:12:43PM +0200, Charles de Miramon wrote: > Sven Hoexter wrote: > > On Fri, May 12, 2006 at 11:29:15AM +0200, Charles de Miramon wrote: Hi, NOTE: I think it's getting quite off-topic here. IMHO wie should move the package related discussion to this mailinglist: http://lists.alioth.debian.org/mailman/listinfo/pkg-lyx-devel If you guys prefer to have it on the lyx mailinglist that's ok for me. Just wanted to ask before someone complains about off-topic traffic on a user list. > >> I've started from Georg Baum's version but I made an ugly hack in > >> debian/rules to force it to compile with gcc 4.1. I don't know how you > >> should do it properly in Debian. I've updated the dependence fields also > >> and made some little changes. > > IIRC setting "CXX = g++-4.1" in the rules should work. > I wanted something that would work for sarge and sid, so we could keep one > file. A rule, saying on sarge use gcc 3.3 and on sid gcc 4.1 Indeed, that's ugly. A better way would be to force the unstable version to use g++ 4.1 (if realy needed) and then create a backport for backports.org that uses the default compiler or any other special compiler version needed. > > I'll take a look at your changes aswell but aehm why do you need to > > compile with gcc/g++ 4.1? A pointer to the thread would be enough so that > > I can catch up on that problem aswell. > > I've uploaded the total source package here : Thanks. (wow now I've at least 3 different versions to compare 8-) Sven -- If you won't forgive me the rest of my life Let me apologize while I'm still alive I know it's time to face all of my past mistakes [Less than Jake - Rest Of My Life]
Let's get the Lyx Debian pkg back in sync with upstream
Hello, I'd like to see the Debian package in the archive back in sync with the upstream version. I contacted Erinn Clark yesterday (she's listed in the pkg-lyx[1] project on alioth.debian.org) and she told me that the package is in an orphaned state but just not marked beeing O. The other former maintainer, Rob Weir, is MIA. So I'm willing to take it over BUT my experience with Debian packaging is still quite low and limited to small packages[2]. Additional I've not followed the Lyx development for the last ~2 years. So any help would be highly appreciated. After a first look around I found that several people are hacking their own Debian packages so there must be some demand for new packages and people willing to do some work. Please raise your hand now guys! I would like to see the people interessted joining the pkg-lyx-devel mailinglist provided via alioth. If you don't like to join the mailinglist but like to contact me please do so. You can find information on how to contact me via IRC and several IM networks here [3]. Ok now let's go over to some more technical things :) ATM I'm looking for the lost ends while actualy using Lyx to get some university stuff done. Things I found out so far: - Lyx 1.4 compiles with the /debian/ dir from the 1.3.6 packages in the archive with only minor changes. One is about to change a Build-Dep from libaiksaurus-dev to libaiksaurus-1.2-dev and the other one was the 02. patch not to apply. Then it takes a lot of time to compile on my little bit aged Athlon 1,4Ghz *sigh* but in the end I got a working package for i386 *juhu*. - The /debian/ subdir from 1.3.6 seems to be in a good shape and is using dpatch so I will stay with it. There are some fix me notes in the rules file but that should not matter for the moment. - There is a patch for hppa in the patchlist from an NMU - would be nice to find out to which upstream this patch belongs. - There is a huge amount of old bugs in the Debian BTS which need to be checked. - I've read something about a gtk frontend and found it in the Lyx source but there is no configure option for it and it's not mentioned in the README/INSTALL files. What's that? How can we use it? Is it alpha stuff you should not use? Would be cool if someone could enlight me what's that all about. Things I haven't found out yet: - Is the lyx package maintained in a VCS? I'd like to go with subversion but I've to admit that I haven't had the time lately to find out how svn-buildpackage should be used. Hints for docs I should read are welcome :). - Is there a DD out in the wild internet willing to sponsor a new Lyx package? So I'm now getting back to my university stuff for a few hours and wait for some feedback. Cheers, Sven [1] http://alioth.debian.org/projects/pkg-lyx/ [2] http://qa.debian.org/[EMAIL PROTECTED] [3] http://sven.stormbind.net -- If you won't forgive me the rest of my life Let me apologize while I'm still alive I know it's time to face all of my past mistakes [Less than Jake - Rest Of My Life] signature.asc Description: Digital signature
Re: Let's get the Lyx Debian pkg back in sync with upstream
Sven Hoexter wrote: Hello, I'd like to see the Debian package in the archive back in sync with the upstream version. That would be very nice indeed. I contacted Erinn Clark yesterday (she's listed in the pkg-lyx[1] project on alioth.debian.org) and she told me that the package is in an orphaned state but just not marked beeing O. The other former maintainer, Rob Weir, is MIA. What is MIA? - The /debian/ subdir from 1.3.6 seems to be in a good shape and is using dpatch so I will stay with it. There are some fix me notes in the rules file but that should not matter for the moment. The 1.3.6 debian subdir needs some more fixes for 1.4.x. I did those, and you can see the result at http://wiki.lyx.org/LyX/LyXOnDebian#toc6. Note that small tweaks are needed for 1.4.2svn, I can provide an update if needed. I suggest you start from http://wiki.lyx.org/LyX/LyXOnDebian insetad of the 1.3.6 version. - I've read something about a gtk frontend and found it in the Lyx source but there is no configure option for it and it's not mentioned in the README/INSTALL files. What's that? How can we use it? Is it alpha stuff you should not use? Would be cool if someone could enlight me what's that all about. It is not documented because it is experimental and not ready for use. - Is there a DD out in the wild internet willing to sponsor a new Lyx package? That is the biggest problem. I suggest you find somebody who is willing to do that before doing anything else, because we have enough unofficial packages already. Maybe it would help if Erinn Clark orphaned the package officially. Georg
Re: Let's get the Lyx Debian pkg back in sync with upstream
On Fri, May 12, 2006 at 10:24:06AM +0200, Georg Baum wrote: Sven Hoexter wrote: Hello Georg, Wow that's a fast reply :) I contacted Erinn Clark yesterday (she's listed in the pkg-lyx[1] project on alioth.debian.org) and she told me that the package is in an orphaned state but just not marked beeing O. The other former maintainer, Rob Weir, is MIA. What is MIA? Missing in action, he's not reachable and does not fix bugs. - The /debian/ subdir from 1.3.6 seems to be in a good shape and is using dpatch so I will stay with it. There are some fix me notes in the rules file but that should not matter for the moment. The 1.3.6 debian subdir needs some more fixes for 1.4.x. I did those, and you can see the result at http://wiki.lyx.org/LyX/LyXOnDebian#toc6. Note that small tweaks are needed for 1.4.2svn, I can provide an update if needed. Ah ok. How far is 1.4.2 from beeing released? I would like to stay with the final releases. - I've read something about a gtk frontend and found it in the Lyx source but there is no configure option for it and it's not mentioned in the README/INSTALL files. What's that? How can we use it? Is it alpha stuff you should not use? Would be cool if someone could enlight me what's that all about. It is not documented because it is experimental and not ready for use. Ok so I count that as not relevant for the moment so that the debian package will stay with the qt and xforms frontend. Or is xforms finaly deprecated now? - Is there a DD out in the wild internet willing to sponsor a new Lyx package? That is the biggest problem. I suggest you find somebody who is willing to do that before doing anything else, because we have enough unofficial packages already. Well my intention is definetly not to prepare another package which will finaly end in /dev/null. I'm quite optimistic to find someone who is willing to sponsor it. Maybe it would help if Erinn Clark orphaned the package officially. To my experience not realy. Cheers, Sven -- If you won't forgive me the rest of my life Let me apologize while I'm still alive I know it's time to face all of my past mistakes [Less than Jake - Rest Of My Life]
Re: Let's get the Lyx Debian pkg back in sync with upstream
Sven == Sven Hoexter [EMAIL PROTECTED] writes: Sven Ah ok. How far is 1.4.2 from beeing released? I would like to Sven stay with the final releases. I am not sure yet. We have two or three bad bugs to fix, we are waiting for a brand new windows installer and we have two larger patches that may or may not be applied now or later (view files through windows services; outline-like functionality). But considering that configuration mechanism are changing, I think you should target 1.4.2. JMarc
Re: Let's get the Lyx Debian pkg back in sync with upstream
Sven Hoexter wrote: Wow that's a fast reply :) I was waiting for a simulation to finish when your message came in. I am not always that fast. Ok so I count that as not relevant for the moment so that the debian package will stay with the qt and xforms frontend. Or is xforms finaly deprecated now? xforms works, but will probably not see any big amounts of new development. I expect it to be dropped if continued support would mean to invest much time. I'll upload an updated diff for 1.4.2svn to the wiki tonight. Georg
Re: Let's get the Lyx Debian pkg back in sync with upstream
Georg Baum wrote : I'll upload an updated diff for 1.4.2svn to the wiki tonight. I've got 1.4.1 packages for sid (amd64, i386) and for sarge (i386) for the qt frontend apt-gettable from http://lyxondebian.free.fr I can try to upload the source package tonight. I've started from Georg Baum's version but I made an ugly hack in debian/rules to force it to compile with gcc 4.1. I don't know how you should do it properly in Debian. I've updated the dependence fields also and made some little changes. I can send the files to you, if you want. Cheers, Charles -- http://www.kde-france.org
Re: Let's get the Lyx Debian pkg back in sync with upstream
Charles de Miramon wrote: I've started from Georg Baum's version but I made an ugly hack in debian/rules to force it to compile with gcc 4.1. I don't know how you should do it properly in Debian. I've updated the dependence fields also and made some little changes. I'll have a look at tge gcc 4.1 problem. I can send the files to you, if you want. That would be nice. My intention is to have one diff on the wiki that should be considered semi-official and that works with as many .deb based distros as possible (and of course everybody is encouraged to upload fixes there, too). Georg PS: Thanks for doing the apt stuff.
Re: Let's get the Lyx Debian pkg back in sync with upstream
On Fri, May 12, 2006 at 11:29:15AM +0200, Charles de Miramon wrote: Hi, I've started from Georg Baum's version but I made an ugly hack in debian/rules to force it to compile with gcc 4.1. I don't know how you should do it properly in Debian. I've updated the dependence fields also and made some little changes. IIRC setting CXX = g++-4.1 in the rules should work. I'll take a look at your changes aswell but aehm why do you need to compile with gcc/g++ 4.1? A pointer to the thread would be enough so that I can catch up on that problem aswell. Regarding g++ 4.1 I found this FTBFS bug in the Debian BTS http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357119 Sven -- If you won't forgive me the rest of my life Let me apologize while I'm still alive I know it's time to face all of my past mistakes [Less than Jake - Rest Of My Life]
Re: Let's get the Lyx Debian pkg back in sync with upstream
Sven Hoexter wrote: I'll take a look at your changes aswell but aehm why do you need to compile with gcc/g++ 4.1? I believe that this is the default compiler in unstable. Regarding g++ 4.1 I found this FTBFS bug in the Debian BTS http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357119 IIRC this is a boost bug that is fixed in 1.4.x. Georg
Re: Let's get the Lyx Debian pkg back in sync with upstream
Sven Hoexter wrote: On Fri, May 12, 2006 at 11:29:15AM +0200, Charles de Miramon wrote: Hi, I've started from Georg Baum's version but I made an ugly hack in debian/rules to force it to compile with gcc 4.1. I don't know how you should do it properly in Debian. I've updated the dependence fields also and made some little changes. IIRC setting CXX = g++-4.1 in the rules should work. I wanted something that would work for sarge and sid, so we could keep one file. A rule, saying on sarge use gcc 3.3 and on sid gcc 4.1 I'll take a look at your changes aswell but aehm why do you need to compile with gcc/g++ 4.1? A pointer to the thread would be enough so that I can catch up on that problem aswell. I've uploaded the total source package here : http://mvdlugt.nerim.net/LyX/lyx_1.4.1-1.lyx.org.2.tar.gz (83 M) Only the debian directory : http://mvdlugt.nerim.net/LyX/LyXDebian.tar.gz Looking again at my packages. I found that there are some minor changes to be made to the control files. Cheers, Charles -- http://www.kde-france.org
Re: [Pkg-lyx-devel] Let's get the Lyx Debian pkg back in sync with upstream
On Fri, 12 May 2006, Per Olofsson wrote: - Is there a DD out in the wild internet willing to sponsor a new Lyx package? Yes, I'd be willing to sponsor the package. What is a DD? /Christian -- Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
Re: [Pkg-lyx-devel] Let's get the Lyx Debian pkg back in sync with upstream
[EMAIL PROTECTED] wrote: On Fri, 12 May 2006, Per Olofsson wrote: - Is there a DD out in the wild internet willing to sponsor a new Lyx package? Yes, I'd be willing to sponsor the package. What is a DD? Debian Developper. Debian has a full American-oriented lingo, like 'MIA' which is initially a US military acronym / euphemism for a killed soldier. Cheers, Charles -- http://www.kde-france.org
Let's get the Lyx Debian pkg back in sync with upstream
Hello, I'd like to see the Debian package in the archive back in sync with the upstream version. I contacted Erinn Clark yesterday (she's listed in the pkg-lyx[1] project on alioth.debian.org) and she told me that the package is in an orphaned state but just not marked beeing O. The other former maintainer, Rob Weir, is MIA. So I'm willing to take it over BUT my experience with Debian packaging is still quite low and limited to small packages[2]. Additional I've not followed the Lyx development for the last ~2 years. So any help would be highly appreciated. After a first look around I found that several people are hacking their own Debian packages so there must be some demand for new packages and people willing to do some work. Please raise your hand now guys! I would like to see the people interessted joining the pkg-lyx-devel mailinglist provided via alioth. If you don't like to join the mailinglist but like to contact me please do so. You can find information on how to contact me via IRC and several IM networks here [3]. Ok now let's go over to some more technical things :) ATM I'm looking for the lost ends while actualy using Lyx to get some university stuff done. Things I found out so far: - Lyx 1.4 compiles with the /debian/ dir from the 1.3.6 packages in the archive with only minor changes. One is about to change a Build-Dep from libaiksaurus-dev to libaiksaurus-1.2-dev and the other one was the 02. patch not to apply. Then it takes a lot of time to compile on my little bit aged Athlon 1,4Ghz *sigh* but in the end I got a working package for i386 *juhu*. - The /debian/ subdir from 1.3.6 seems to be in a good shape and is using dpatch so I will stay with it. There are some fix me notes in the rules file but that should not matter for the moment. - There is a patch for hppa in the patchlist from an NMU - would be nice to find out to which upstream this patch belongs. - There is a huge amount of old bugs in the Debian BTS which need to be checked. - I've read something about a gtk frontend and found it in the Lyx source but there is no configure option for it and it's not mentioned in the README/INSTALL files. What's that? How can we use it? Is it alpha stuff you should not use? Would be cool if someone could enlight me what's that all about. Things I haven't found out yet: - Is the lyx package maintained in a VCS? I'd like to go with subversion but I've to admit that I haven't had the time lately to find out how svn-buildpackage should be used. Hints for docs I should read are welcome :). - Is there a DD out in the wild internet willing to sponsor a new Lyx package? So I'm now getting back to my university stuff for a few hours and wait for some feedback. Cheers, Sven [1] http://alioth.debian.org/projects/pkg-lyx/ [2] http://qa.debian.org/[EMAIL PROTECTED] [3] http://sven.stormbind.net -- If you won't forgive me the rest of my life Let me apologize while I'm still alive I know it's time to face all of my past mistakes [Less than Jake - Rest Of My Life] signature.asc Description: Digital signature
Re: Let's get the Lyx Debian pkg back in sync with upstream
Sven Hoexter wrote: Hello, I'd like to see the Debian package in the archive back in sync with the upstream version. That would be very nice indeed. I contacted Erinn Clark yesterday (she's listed in the pkg-lyx[1] project on alioth.debian.org) and she told me that the package is in an orphaned state but just not marked beeing O. The other former maintainer, Rob Weir, is MIA. What is MIA? - The /debian/ subdir from 1.3.6 seems to be in a good shape and is using dpatch so I will stay with it. There are some fix me notes in the rules file but that should not matter for the moment. The 1.3.6 debian subdir needs some more fixes for 1.4.x. I did those, and you can see the result at http://wiki.lyx.org/LyX/LyXOnDebian#toc6. Note that small tweaks are needed for 1.4.2svn, I can provide an update if needed. I suggest you start from http://wiki.lyx.org/LyX/LyXOnDebian insetad of the 1.3.6 version. - I've read something about a gtk frontend and found it in the Lyx source but there is no configure option for it and it's not mentioned in the README/INSTALL files. What's that? How can we use it? Is it alpha stuff you should not use? Would be cool if someone could enlight me what's that all about. It is not documented because it is experimental and not ready for use. - Is there a DD out in the wild internet willing to sponsor a new Lyx package? That is the biggest problem. I suggest you find somebody who is willing to do that before doing anything else, because we have enough unofficial packages already. Maybe it would help if Erinn Clark orphaned the package officially. Georg
Re: Let's get the Lyx Debian pkg back in sync with upstream
On Fri, May 12, 2006 at 10:24:06AM +0200, Georg Baum wrote: Sven Hoexter wrote: Hello Georg, Wow that's a fast reply :) I contacted Erinn Clark yesterday (she's listed in the pkg-lyx[1] project on alioth.debian.org) and she told me that the package is in an orphaned state but just not marked beeing O. The other former maintainer, Rob Weir, is MIA. What is MIA? Missing in action, he's not reachable and does not fix bugs. - The /debian/ subdir from 1.3.6 seems to be in a good shape and is using dpatch so I will stay with it. There are some fix me notes in the rules file but that should not matter for the moment. The 1.3.6 debian subdir needs some more fixes for 1.4.x. I did those, and you can see the result at http://wiki.lyx.org/LyX/LyXOnDebian#toc6. Note that small tweaks are needed for 1.4.2svn, I can provide an update if needed. Ah ok. How far is 1.4.2 from beeing released? I would like to stay with the final releases. - I've read something about a gtk frontend and found it in the Lyx source but there is no configure option for it and it's not mentioned in the README/INSTALL files. What's that? How can we use it? Is it alpha stuff you should not use? Would be cool if someone could enlight me what's that all about. It is not documented because it is experimental and not ready for use. Ok so I count that as not relevant for the moment so that the debian package will stay with the qt and xforms frontend. Or is xforms finaly deprecated now? - Is there a DD out in the wild internet willing to sponsor a new Lyx package? That is the biggest problem. I suggest you find somebody who is willing to do that before doing anything else, because we have enough unofficial packages already. Well my intention is definetly not to prepare another package which will finaly end in /dev/null. I'm quite optimistic to find someone who is willing to sponsor it. Maybe it would help if Erinn Clark orphaned the package officially. To my experience not realy. Cheers, Sven -- If you won't forgive me the rest of my life Let me apologize while I'm still alive I know it's time to face all of my past mistakes [Less than Jake - Rest Of My Life]
Re: Let's get the Lyx Debian pkg back in sync with upstream
Sven == Sven Hoexter [EMAIL PROTECTED] writes: Sven Ah ok. How far is 1.4.2 from beeing released? I would like to Sven stay with the final releases. I am not sure yet. We have two or three bad bugs to fix, we are waiting for a brand new windows installer and we have two larger patches that may or may not be applied now or later (view files through windows services; outline-like functionality). But considering that configuration mechanism are changing, I think you should target 1.4.2. JMarc
Re: Let's get the Lyx Debian pkg back in sync with upstream
Sven Hoexter wrote: Wow that's a fast reply :) I was waiting for a simulation to finish when your message came in. I am not always that fast. Ok so I count that as not relevant for the moment so that the debian package will stay with the qt and xforms frontend. Or is xforms finaly deprecated now? xforms works, but will probably not see any big amounts of new development. I expect it to be dropped if continued support would mean to invest much time. I'll upload an updated diff for 1.4.2svn to the wiki tonight. Georg
Re: Let's get the Lyx Debian pkg back in sync with upstream
Georg Baum wrote : I'll upload an updated diff for 1.4.2svn to the wiki tonight. I've got 1.4.1 packages for sid (amd64, i386) and for sarge (i386) for the qt frontend apt-gettable from http://lyxondebian.free.fr I can try to upload the source package tonight. I've started from Georg Baum's version but I made an ugly hack in debian/rules to force it to compile with gcc 4.1. I don't know how you should do it properly in Debian. I've updated the dependence fields also and made some little changes. I can send the files to you, if you want. Cheers, Charles -- http://www.kde-france.org
Re: Let's get the Lyx Debian pkg back in sync with upstream
Charles de Miramon wrote: I've started from Georg Baum's version but I made an ugly hack in debian/rules to force it to compile with gcc 4.1. I don't know how you should do it properly in Debian. I've updated the dependence fields also and made some little changes. I'll have a look at tge gcc 4.1 problem. I can send the files to you, if you want. That would be nice. My intention is to have one diff on the wiki that should be considered semi-official and that works with as many .deb based distros as possible (and of course everybody is encouraged to upload fixes there, too). Georg PS: Thanks for doing the apt stuff.
Re: Let's get the Lyx Debian pkg back in sync with upstream
On Fri, May 12, 2006 at 11:29:15AM +0200, Charles de Miramon wrote: Hi, I've started from Georg Baum's version but I made an ugly hack in debian/rules to force it to compile with gcc 4.1. I don't know how you should do it properly in Debian. I've updated the dependence fields also and made some little changes. IIRC setting CXX = g++-4.1 in the rules should work. I'll take a look at your changes aswell but aehm why do you need to compile with gcc/g++ 4.1? A pointer to the thread would be enough so that I can catch up on that problem aswell. Regarding g++ 4.1 I found this FTBFS bug in the Debian BTS http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357119 Sven -- If you won't forgive me the rest of my life Let me apologize while I'm still alive I know it's time to face all of my past mistakes [Less than Jake - Rest Of My Life]
Re: Let's get the Lyx Debian pkg back in sync with upstream
Sven Hoexter wrote: I'll take a look at your changes aswell but aehm why do you need to compile with gcc/g++ 4.1? I believe that this is the default compiler in unstable. Regarding g++ 4.1 I found this FTBFS bug in the Debian BTS http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357119 IIRC this is a boost bug that is fixed in 1.4.x. Georg
Re: Let's get the Lyx Debian pkg back in sync with upstream
Sven Hoexter wrote: On Fri, May 12, 2006 at 11:29:15AM +0200, Charles de Miramon wrote: Hi, I've started from Georg Baum's version but I made an ugly hack in debian/rules to force it to compile with gcc 4.1. I don't know how you should do it properly in Debian. I've updated the dependence fields also and made some little changes. IIRC setting CXX = g++-4.1 in the rules should work. I wanted something that would work for sarge and sid, so we could keep one file. A rule, saying on sarge use gcc 3.3 and on sid gcc 4.1 I'll take a look at your changes aswell but aehm why do you need to compile with gcc/g++ 4.1? A pointer to the thread would be enough so that I can catch up on that problem aswell. I've uploaded the total source package here : http://mvdlugt.nerim.net/LyX/lyx_1.4.1-1.lyx.org.2.tar.gz (83 M) Only the debian directory : http://mvdlugt.nerim.net/LyX/LyXDebian.tar.gz Looking again at my packages. I found that there are some minor changes to be made to the control files. Cheers, Charles -- http://www.kde-france.org
Re: [Pkg-lyx-devel] Let's get the Lyx Debian pkg back in sync with upstream
On Fri, 12 May 2006, Per Olofsson wrote: - Is there a DD out in the wild internet willing to sponsor a new Lyx package? Yes, I'd be willing to sponsor the package. What is a DD? /Christian -- Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
Re: [Pkg-lyx-devel] Let's get the Lyx Debian pkg back in sync with upstream
[EMAIL PROTECTED] wrote: On Fri, 12 May 2006, Per Olofsson wrote: - Is there a DD out in the wild internet willing to sponsor a new Lyx package? Yes, I'd be willing to sponsor the package. What is a DD? Debian Developper. Debian has a full American-oriented lingo, like 'MIA' which is initially a US military acronym / euphemism for a killed soldier. Cheers, Charles -- http://www.kde-france.org
Let's get the Lyx Debian pkg back in sync with upstream
Hello, I'd like to see the Debian package in the archive back in sync with the upstream version. I contacted Erinn Clark yesterday (she's listed in the pkg-lyx[1] project on alioth.debian.org) and she told me that the package is in an orphaned state but just not marked beeing O. The other former maintainer, Rob Weir, is MIA. So I'm willing to take it over BUT my experience with Debian packaging is still quite low and limited to small packages[2]. Additional I've not followed the Lyx development for the last ~2 years. So any help would be highly appreciated. After a first look around I found that several people are hacking their own Debian packages so there must be some demand for new packages and people willing to do some work. Please raise your hand now guys! I would like to see the people interessted joining the pkg-lyx-devel mailinglist provided via alioth. If you don't like to join the mailinglist but like to contact me please do so. You can find information on how to contact me via IRC and several IM networks here [3]. Ok now let's go over to some more technical things :) ATM I'm looking for the lost ends while actualy using Lyx to get some university stuff done. Things I found out so far: - Lyx 1.4 compiles with the /debian/ dir from the 1.3.6 packages in the archive with only minor changes. One is about to change a Build-Dep from libaiksaurus-dev to libaiksaurus-1.2-dev and the other one was the 02. patch not to apply. Then it takes a lot of time to compile on my little bit aged Athlon 1,4Ghz *sigh* but in the end I got a working package for i386 *juhu*. - The /debian/ subdir from 1.3.6 seems to be in a good shape and is using dpatch so I will stay with it. There are some fix me notes in the rules file but that should not matter for the moment. - There is a patch for hppa in the patchlist from an NMU - would be nice to find out to which upstream this patch belongs. - There is a huge amount of old bugs in the Debian BTS which need to be checked. - I've read something about a gtk frontend and found it in the Lyx source but there is no configure option for it and it's not mentioned in the README/INSTALL files. What's that? How can we use it? Is it alpha stuff you should not use? Would be cool if someone could enlight me what's that all about. Things I haven't found out yet: - Is the lyx package maintained in a VCS? I'd like to go with subversion but I've to admit that I haven't had the time lately to find out how svn-buildpackage should be used. Hints for docs I should read are welcome :). - Is there a DD out in the wild internet willing to sponsor a new Lyx package? So I'm now getting back to my university stuff for a few hours and wait for some feedback. Cheers, Sven [1] http://alioth.debian.org/projects/pkg-lyx/ [2] http://qa.debian.org/[EMAIL PROTECTED] [3] http://sven.stormbind.net -- If you won't forgive me the rest of my life Let me apologize while I'm still alive I know it's time to face all of my past mistakes [Less than Jake - Rest Of My Life] signature.asc Description: Digital signature
Re: Let's get the Lyx Debian pkg back in sync with upstream
Sven Hoexter wrote: > Hello, > I'd like to see the Debian package in the archive back in sync with the > upstream version. That would be very nice indeed. > I contacted Erinn Clark yesterday (she's listed in the pkg-lyx[1] project > on alioth.debian.org) and she told me that the package is in an orphaned > state but just not marked beeing O. The other former maintainer, Rob Weir, > is MIA. What is MIA? > - The /debian/ subdir from 1.3.6 seems to be in a good shape and is using > dpatch so > I will stay with it. There are some fix me notes in the rules file but > that should not matter for the moment. The 1.3.6 debian subdir needs some more fixes for 1.4.x. I did those, and you can see the result at http://wiki.lyx.org/LyX/LyXOnDebian#toc6. Note that small tweaks are needed for 1.4.2svn, I can provide an update if needed. I suggest you start from http://wiki.lyx.org/LyX/LyXOnDebian insetad of the 1.3.6 version. > - I've read something about a gtk frontend and found it in the Lyx source > but there is > no configure option for it and it's not mentioned in the README/INSTALL > files. What's that? How can we use it? Is it alpha stuff you should not > use? Would be cool if someone could enlight me what's that all about. It is not documented because it is experimental and not ready for use. > - Is there a DD out in the wild internet willing to sponsor a new Lyx > package? That is the biggest problem. I suggest you find somebody who is willing to do that before doing anything else, because we have enough unofficial packages already. Maybe it would help if Erinn Clark orphaned the package officially. Georg
Re: Let's get the Lyx Debian pkg back in sync with upstream
On Fri, May 12, 2006 at 10:24:06AM +0200, Georg Baum wrote: > Sven Hoexter wrote: Hello Georg, Wow that's a fast reply :) > > I contacted Erinn Clark yesterday (she's listed in the pkg-lyx[1] project > > on alioth.debian.org) and she told me that the package is in an orphaned > > state but just not marked beeing O. The other former maintainer, Rob Weir, > > is MIA. > > What is MIA? Missing in action, he's not reachable and does not fix bugs. > > - The /debian/ subdir from 1.3.6 seems to be in a good shape and is using > > dpatch so > > I will stay with it. There are some fix me notes in the rules file but > > that should not matter for the moment. > > The 1.3.6 debian subdir needs some more fixes for 1.4.x. I did those, and > you can see the result at http://wiki.lyx.org/LyX/LyXOnDebian#toc6. Note > that small tweaks are needed for 1.4.2svn, I can provide an update if > needed. Ah ok. How far is 1.4.2 from beeing released? I would like to stay with the final releases. > > - I've read something about a gtk frontend and found it in the Lyx source > > but there is > > no configure option for it and it's not mentioned in the README/INSTALL > > files. What's that? How can we use it? Is it alpha stuff you should not > > use? Would be cool if someone could enlight me what's that all about. > > It is not documented because it is experimental and not ready for use. Ok so I count that as not relevant for the moment so that the debian package will stay with the qt and xforms frontend. Or is xforms finaly deprecated now? > > - Is there a DD out in the wild internet willing to sponsor a new Lyx > > package? > > That is the biggest problem. I suggest you find somebody who is willing to > do that before doing anything else, because we have enough unofficial > packages already. Well my intention is definetly not to prepare another package which will finaly end in /dev/null. I'm quite optimistic to find someone who is willing to sponsor it. > Maybe it would help if Erinn Clark orphaned the package > officially. To my experience not realy. Cheers, Sven -- If you won't forgive me the rest of my life Let me apologize while I'm still alive I know it's time to face all of my past mistakes [Less than Jake - Rest Of My Life]
Re: Let's get the Lyx Debian pkg back in sync with upstream
> "Sven" == Sven Hoexter <[EMAIL PROTECTED]> writes: Sven> Ah ok. How far is 1.4.2 from beeing released? I would like to Sven> stay with the final releases. I am not sure yet. We have two or three bad bugs to fix, we are waiting for a brand new windows installer and we have two larger patches that may or may not be applied now or later (view files through windows services; outline-like functionality). But considering that configuration mechanism are changing, I think you should target 1.4.2. JMarc
Re: Let's get the Lyx Debian pkg back in sync with upstream
Sven Hoexter wrote: > Wow that's a fast reply :) I was waiting for a simulation to finish when your message came in. I am not always that fast. > Ok so I count that as not relevant for the moment so that the debian > package will stay with the qt and xforms frontend. Or is xforms finaly > deprecated now? xforms works, but will probably not see any big amounts of new development. I expect it to be dropped if continued support would mean to invest much time. I'll upload an updated diff for 1.4.2svn to the wiki tonight. Georg
Re: Let's get the Lyx Debian pkg back in sync with upstream
Georg Baum wrote : > > I'll upload an updated diff for 1.4.2svn to the wiki tonight. > I've got 1.4.1 packages for sid (amd64, i386) and for sarge (i386) for the qt frontend apt-gettable from http://lyxondebian.free.fr I can try to upload the source package tonight. I've started from Georg Baum's version but I made an ugly hack in debian/rules to force it to compile with gcc 4.1. I don't know how you should do it properly in Debian. I've updated the dependence fields also and made some little changes. I can send the files to you, if you want. Cheers, Charles -- http://www.kde-france.org
Re: Let's get the Lyx Debian pkg back in sync with upstream
Charles de Miramon wrote: > I've started from Georg Baum's version but I made an ugly hack in > debian/rules to force it to compile with gcc 4.1. I don't know how you > should do it properly in Debian. I've updated the dependence fields also > and made some little changes. I'll have a look at tge gcc 4.1 problem. > I can send the files to you, if you want. That would be nice. My intention is to have one diff on the wiki that should be considered "semi-official" and that works with as many .deb based distros as possible (and of course everybody is encouraged to upload fixes there, too). Georg PS: Thanks for doing the apt stuff.
Re: Let's get the Lyx Debian pkg back in sync with upstream
On Fri, May 12, 2006 at 11:29:15AM +0200, Charles de Miramon wrote: Hi, > I've started from Georg Baum's version but I made an ugly hack in > debian/rules to force it to compile with gcc 4.1. I don't know how you > should do it properly in Debian. I've updated the dependence fields also > and made some little changes. IIRC setting "CXX = g++-4.1" in the rules should work. I'll take a look at your changes aswell but aehm why do you need to compile with gcc/g++ 4.1? A pointer to the thread would be enough so that I can catch up on that problem aswell. Regarding g++ 4.1 I found this FTBFS bug in the Debian BTS http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357119 Sven -- If you won't forgive me the rest of my life Let me apologize while I'm still alive I know it's time to face all of my past mistakes [Less than Jake - Rest Of My Life]
Re: Let's get the Lyx Debian pkg back in sync with upstream
Sven Hoexter wrote: > I'll take a look at your changes aswell but aehm why do you need to > compile with gcc/g++ 4.1? I believe that this is the default compiler in unstable. > Regarding g++ 4.1 I found this FTBFS bug in the Debian BTS > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357119 IIRC this is a boost bug that is fixed in 1.4.x. Georg
Re: Let's get the Lyx Debian pkg back in sync with upstream
Sven Hoexter wrote: > On Fri, May 12, 2006 at 11:29:15AM +0200, Charles de Miramon wrote: > > Hi, > >> I've started from Georg Baum's version but I made an ugly hack in >> debian/rules to force it to compile with gcc 4.1. I don't know how you >> should do it properly in Debian. I've updated the dependence fields also >> and made some little changes. > IIRC setting "CXX = g++-4.1" in the rules should work. I wanted something that would work for sarge and sid, so we could keep one file. A rule, saying on sarge use gcc 3.3 and on sid gcc 4.1 > > I'll take a look at your changes aswell but aehm why do you need to > compile with gcc/g++ 4.1? A pointer to the thread would be enough so that > I can catch up on that problem aswell. I've uploaded the total source package here : http://mvdlugt.nerim.net/LyX/lyx_1.4.1-1.lyx.org.2.tar.gz (83 M) Only the debian directory : http://mvdlugt.nerim.net/LyX/LyXDebian.tar.gz Looking again at my packages. I found that there are some minor changes to be made to the control files. Cheers, Charles -- http://www.kde-france.org
Re: [Pkg-lyx-devel] Let's get the Lyx Debian pkg back in sync with upstream
On Fri, 12 May 2006, Per Olofsson wrote: > > - Is there a DD out in the wild internet willing to sponsor a new Lyx > > package? > > Yes, I'd be willing to sponsor the package. What is a DD? /Christian -- Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
Re: [Pkg-lyx-devel] Let's get the Lyx Debian pkg back in sync with upstream
[EMAIL PROTECTED] wrote: > On Fri, 12 May 2006, Per Olofsson wrote: > >> > - Is there a DD out in the wild internet willing to sponsor a new Lyx >> > package? >> >> Yes, I'd be willing to sponsor the package. > > What is a DD? > Debian Developper. Debian has a full American-oriented lingo, like 'MIA' which is initially a US military acronym / euphemism for a killed soldier. Cheers, Charles -- http://www.kde-france.org
