Re: Proper handling of Lintian warnings due to other packages

2024-02-01 Thread Ian Campbell
On Wed, 2024-01-31 at 10:49 -0500, Scott Talbert wrote: > > Note: I don't discourage usage of debbugs.  It's just that I'm unlikely to > notice bugs immediately due to the way debbugs notifications work. You should be able to use tracker.debian.org to subscribe to teams or individual packages

Re: Proper handling of Lintian warnings due to other packages

2024-02-01 Thread Mathias Behrle
* Scott Talbert: " Re: Proper handling of Lintian warnings due to other packages" (Wed, 31 Jan 2024 13:16:11 -0500 (EST)): > On Wed, 31 Jan 2024, Jonas Smedegaard wrote: > > > Quoting Scott Talbert (2024-01-31 16:49:59) > >> On Wed, 31 J

Re: Proper handling of Lintian warnings due to other packages

2024-01-31 Thread Scott Talbert
On Wed, 31 Jan 2024, Jonas Smedegaard wrote: Quoting Scott Talbert (2024-01-31 16:49:59) On Wed, 31 Jan 2024, Jonas Smedegaard wrote: Unfortunately it is not likely that the package will be catch up soon, because the Haskell team upgrade most Haskell libraries only as a whole. That issue is

Re: Proper handling of Lintian warnings due to other packages

2024-01-31 Thread Jonas Smedegaard
Quoting Scott Talbert (2024-01-31 16:49:59) > On Wed, 31 Jan 2024, Jonas Smedegaard wrote: > > > Unfortunately it is not likely that the package will be catch up soon, > > because the Haskell team upgrade most Haskell libraries only as a whole. > > > > That issue is not tracked in debbugs,

Re: Proper handling of Lintian warnings due to other packages

2024-01-31 Thread Scott Talbert
On Wed, 31 Jan 2024, Jonas Smedegaard wrote: Unfortunately it is not likely that the package will be catch up soon, because the Haskell team upgrade most Haskell libraries only as a whole. That issue is not tracked in debbugs, because those vocal in the Haskell team actively discourages the

Re: Proper handling of Lintian warnings due to other packages

2024-01-31 Thread G. Branden Robinson
package libghc-pandoc-dev tag 1053777 + fixed-upstream thanks Hi Jonas! At 2024-01-31T08:43:18+0100, Jonas Smedegaard wrote: > Quoting G. Branden Robinson (2024-01-31 05:49:00) > > Well, the version of pandoc that resolved the issue was 3.1.7, > > released in August 2023.[1] But the version in

Re: Proper handling of Lintian warnings due to other packages

2024-01-30 Thread Jonas Smedegaard
Quoting G. Branden Robinson (2024-01-31 05:49:00) > At 2024-01-30T19:55:07-0800, Loren M. Lang wrote: > > While building a package preparing for a possible upload, I am getting > > a large number of warnings from groff-message due to invalid fonts for > > C and CB in the manpages that are

Re: Proper handling of Lintian warnings due to other packages

2024-01-30 Thread Peter Pentchev
On Wed, Jan 31, 2024 at 07:38:52AM +0100, Norwid Behrnd wrote: > @Lauren Because of an earlier post by you, I assume you prepare a package > which eventually requires a sponsorship by a DD. If this were true, the > upload > to https://mentors.debian.net/ would allow you to share an intermediate

Re: Proper handling of Lintian warnings due to other packages

2024-01-30 Thread Norwid Behrnd
@Lauren Because of an earlier post by you, I assume you prepare a package which eventually requires a sponsorship by a DD. If this were true, the upload to https://mentors.debian.net/ would allow you to share an intermediate version to document your current progress -- both to replicate

Re: Proper handling of Lintian warnings due to other packages

2024-01-30 Thread G. Branden Robinson
Hi Loren, At 2024-01-30T19:55:07-0800, Loren M. Lang wrote: > While building a package preparing for a possible upload, I am getting > a large number of warnings from groff-message due to invalid fonts for > C and CB in the manpages that are generated from Markdown with pandoc. > From what I

Proper handling of Lintian warnings due to other packages

2024-01-30 Thread Loren M. Lang
While building a package preparing for a possible upload, I am getting a large number of warnings from groff-message due to invalid fonts for C and CB in the manpages that are generated from Markdown with pandoc. From what I understand, this is a known issue with how pandoc generates nroff man