disable assertion arguments
|Deletions are marked like this.||Additions are marked like this.|
|Line 17:||Line 17:|
|* You're right - we should do what upstream does by default. Maybe we should ask them though, if the default is a good one.|
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://email@example.com 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]
- 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
I see two arguments for no. a) Upstream default is no and b) it seems to annoy users. I'm unsure which POV should weight more and I don't know how high the risk to loose data really is. --SvenHoexter
- You're right - we should do what upstream does by default. Maybe we should ask them though, if the default is a good one.
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