Status: New
Owner: ----
Labels: Version-TRUNK Type-Bug Priority-Medium OpSys-Linux Dist-Debian  
Arch-Any Desktop-Any GUI-Any

New issue 503 by computer...@gmail.com: Debian packages: Lintian warning  
debian-changelog-line-too-long
http://code.google.com/p/gambas/issues/detail?id=503

1) Having just built my Gambas project, I see in GDebi (tab lintian output):

W: wikilist: debian-changelog-line-too-long line 21
W: wikilist: debian-changelog-line-too-long line 22
W: wikilist: debian-changelog-line-too-long line 23
W: wikilist: debian-changelog-line-too-long line 29
W: wikilist: debian-changelog-line-too-long line 43

Wikipedia tells me this:
N:   The given line of the latest changelog entry is over 80 columns. Such
N:   changelog entries may look poor in terminal windows and mail messages
N:   and be annoying to read. Please wrap changelog entries at 80 columns
N:   or less where possible.

2) GIVE THE FOLLOWING INFORMATIONS (if they are appropriate):

Version: TRUNK (probably)
Operating system: Linux
Distribution: Ubuntu / Debian
Architecture: All

3) How to solve this bug/warning

Please insert a line break after 80 characters when compiling a Gambas  
project to DEB. Since this affects Debian packages, this warning is also  
present on Ubuntu and its derivatives.

-- 
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Gambas-user mailing list
Gambas-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gambas-user

Reply via email to