Bug#357119: [Pkg-lyx-devel] Bug#357119: fixed in current upstream version 1.4.1
Sven Hoexter: On Sat, May 27, 2006 at 03:08:02PM +0200, Martin Michlmayr wrote: When will this be uploaded? Is there a set timeframe for the gcc 4.0.x - 4.1 transition? Right now I need to work on some aehm urgent things for my studies. (yes sometimes I'm lazy and things pile up :( ) So it might take a week or two to get something final usefull uploaded. Since it seems that it would be good to have the bug fixed pretty soon, I can try to package the latest version for now so we can get the transition done. I'm not sure I will have the time, but I'll try. At least I'm going to import the sources into the SVN repository. -- Pelle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#357119: fixed in current upstream version 1.4.1
* Georg Baum [EMAIL PROTECTED] [2006-05-12 22:18]: This bug is fixed in the current upstream version 1.4.1. It compiles fine with gcc 4.1. When will this be uploaded? -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#357119: fixed in current upstream version 1.4.1
Am Samstag, 27. Mai 2006 15:08 schrieb Martin Michlmayr: * Georg Baum [EMAIL PROTECTED] [2006-05-12 22:18]: This bug is fixed in the current upstream version 1.4.1. It compiles fine with gcc 4.1. When will this be uploaded? Probably soon (by NMU). See http://lists.alioth.debian.org/pipermail/pkg-lyx-devel/2006-May/000757.html Georg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#357119: fixed in current upstream version 1.4.1
On Sat, May 27, 2006 at 05:04:45PM +0200, Martin Michlmayr wrote: * Georg Baum [EMAIL PROTECTED] [2006-05-27 15:54]: This bug is fixed in the current upstream version 1.4.1. It compiles fine with gcc 4.1. When will this be uploaded? Probably soon (by NMU). See http://lists.alioth.debian.org/pipermail/pkg-lyx-devel/2006-May/000757.html Good. Why as an NMU though? Cannot you/Sven adopt the package? Erinn is no longer working on it, and Rob Weir is not around. Oh missed that point by Georg. I'm going to adopt it with Per as sponsor and we're working on it as a pkg-lyx group. So forget about the NMU thing ;) You can find some information about the current state here: http://wiki.debian.org/PkgLyx Georg: You're still invited to join us. I hope to come up with a svn repo as the next step. 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] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#357119: fixed in current upstream version 1.4.1
* Georg Baum [EMAIL PROTECTED] [2006-05-27 15:54]: This bug is fixed in the current upstream version 1.4.1. It compiles fine with gcc 4.1. When will this be uploaded? Probably soon (by NMU). See http://lists.alioth.debian.org/pipermail/pkg-lyx-devel/2006-May/000757.html Good. Why as an NMU though? Cannot you/Sven adopt the package? Erinn is no longer working on it, and Rob Weir is not around. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#357119: fixed in current upstream version 1.4.1
* Sven Hoexter [EMAIL PROTECTED] [2006-05-27 17:14]: Oh missed that point by Georg. I'm going to adopt it with Per as sponsor and we're working on it as a pkg-lyx group. So forget about the NMU thing ;) Ok, good. Would be great if this could happen in the next week or so. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#357119: fixed in current upstream version 1.4.1
This bug is fixed in the current upstream version 1.4.1. It compiles fine with gcc 4.1. Georg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
