1555
Comment:
|
1903
sorry, meant yes
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
LyX is collaboratively maintained in the pkg-lyx Alioth project. | LyX is collaboratively maintained in the pkg-lyx Alioth project. It is currently maintained by PerOlofsson and SvenHoexter. |
Line 3: | Line 3: |
* SvenHoexter is currently working on the package. * PerOlofsson is sponsoring uploads. |
* Subversion repository at Alioth. [http://svn.debian.org/wsvn/pkg-lyx Browse] * [http://packages.qa.debian.org/lyx Package Overview] * [http://bugs.debian.org/src:lyx Bugs], [http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=lyx&users=bts-link-upstream@lists.alioth.debian.org with bts-link usertags] (see [:bts-link]) * [http://lists.alioth.debian.org/mailman/listinfo/pkg-lyx-devel pkg-lyx-devel mailing list] [http://lists.alioth.debian.org/pipermail/pkg-lyx-devel/ Archives] |
Line 7: | Line 9: |
* Fix bugs in the BTS | |
Line 8: | Line 11: |
The aim: Get Lyx 1.4.2 into Debian/sid * Additional package dvipost [done] * Frontends: qt and xforms |
* Send patches upstream. We should aim at having a minimal packaging, as much as possible should be sent upstream. Only Debian-specific and "packaging-specific" stuff should be kept. * lyxclient-man-nonascii-char - should this go upstream? * Solve the rpath problem on amd64. * Decide early if we would like to enable assertions with the next stable Debian release [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=410175 #410175] * I say yes. It's better to catch bugs by having assertions enabled than risking data corruption or similar. --PerOlofsson * Provide a backport of 1.5.2 for etch users? [http://lists.alioth.debian.org/pipermail/pkg-lyx-devel/2007-November/002165.html (discussion)] |
Line 12: | Line 18: |
=== dvipost === * Edit the short description - do not start with "A" http://www.de.debian.org/doc/manuals/developers-reference/ch-best-pkging-practices.en.html#s-bpp-pkg-synopsis * Rework the post* scripts to be only called when really necessary * remove the commented out lines from rules |
=== Bugreports without further feedback === [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=299778 #299778 Math panel icons are unclear] - This one had no further feedback from the reporter |
Line 17: | Line 21: |
=== lyx === * look which changes to the packaging are required - Diff between 1.3.6 packaging and Georgs unoffical package is here: ftp://hxt.homelinux.org/debstuff/136-vs-142georg.diff * sort out the bugreports -> ask for feedback for all others * put the debian dir in subversion and find out how svn-buildpackage works * Which version is the right one unless 1.4.2 is released - 1.3.6+1.4.2svn2006..., 1.4.1+1.4.2svn2006..., 1.4.2svn2006... * Should we recommend rcs and dvipost or depend on them? * Make it binNMU-safe. * Break dependency loop? * lyx-qt and lyx-xforms should only depend directly on the libraries they really use. See http://lists.debian.org/debian-devel-announce/2005/11/msg00016.html |
[http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=439116 #439116 broken link in hebrew tutorial] - No further feedback from the reporter and upstream claims that it's fixed |
Line 28: | Line 26: |
* http://wiki.lyx.org/LyX/LyXOnDebian - Debian pkg Wiki site in the Lyx Wiki * http://lists.alioth.debian.org/mailman/listinfo/pkg-lyx-devel - pkg-lyx mailing list * http://pkg-lyx.alioth.debian.org/devel/ - pkg-lyx arch repo |
* [http://wiki.lyx.org/LyX/LyXOnDebian Debian pkg Wiki site in the Lyx Wiki] * [http://pkg-lyx.alioth.debian.org/devel/ Old pkg-lyx arch repo] |
LyX is collaboratively maintained in the pkg-lyx Alioth project. It is currently maintained by PerOlofsson and SvenHoexter.
Subversion repository at Alioth. [http://svn.debian.org/wsvn/pkg-lyx Browse]
[http://packages.qa.debian.org/lyx Package Overview]
[http://bugs.debian.org/src:lyx Bugs], [http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=lyx&users=bts-link-upstream@lists.alioth.debian.org with bts-link usertags] (see [:bts-link])
[http://lists.alioth.debian.org/mailman/listinfo/pkg-lyx-devel pkg-lyx-devel mailing list] [http://lists.alioth.debian.org/pipermail/pkg-lyx-devel/ Archives]
TODO
- Fix bugs in the BTS
- Send patches upstream. We should aim at having a minimal packaging, as much as possible should be sent upstream. Only Debian-specific and "packaging-specific" stuff should be kept.
- lyxclient-man-nonascii-char - should this go upstream?
- Solve the rpath problem on amd64.
Decide early if we would like to enable assertions with the next stable Debian release [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=410175 #410175]
I say yes. It's better to catch bugs by having assertions enabled than risking data corruption or similar. --PerOlofsson
Provide a backport of 1.5.2 for etch users? [http://lists.alioth.debian.org/pipermail/pkg-lyx-devel/2007-November/002165.html (discussion)]
Bugreports without further feedback
[http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=299778 #299778 Math panel icons are unclear] - This one had no further feedback from the reporter
[http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=439116 #439116 broken link in hebrew tutorial] - No further feedback from the reporter and upstream claims that it's fixed
Links
[http://wiki.lyx.org/LyX/LyXOnDebian Debian pkg Wiki site in the Lyx Wiki]
[http://pkg-lyx.alioth.debian.org/devel/ Old pkg-lyx arch repo]