On Tue, 2025-05-06 at 20:26 +0100, Peter B wrote: > On 05/05/2025 20:48, Phil Wyett wrote: > > ..... > > swift/Examples/SwiftUI/ExoplanetExplorer/ExplorerApp.swift > > MIT | Expat tools/swift/duckdb-swift/LICENSE > > MIT | Expat tools/swift/duckdb- > > swift/Sources/DuckDB/Appender.swift > > <snip some 'lrc' output> > > swift/Tests/DuckDBTests/DatabaseTests.swift > > MIT | Expat tools/swift/duckdb- > > swift/Tests/DuckDBTests/DecimalUtilityTests.swift > > MIT | Expat tools/swift/duckdb- > > swift/Tests/DuckDBTests/ExtensionTests.swift > > MIT | Expat tools/swift/duckdb- > > swift/Tests/DuckDBTests/LogicalTypeTests.swift > > MIT | Expat tools/swift/duckdb- > > swift/Tests/DuckDBTests/PreparedStatementTests.swift > > MIT | Expat tools/swift/duckdb- > > swift/Tests/DuckDBTests/TypeConversionTests.swift > > > > Summary > > ======= > > > > Needs some hard work especially on 'debian/copyright'. > > Hi Phil, > > Just an F.Y.I. > You can run lrc with the --terse (-t) option. > I would recommend that here on Mentors. > > There is still a clear indication of whether or not there are issues, > and the output would be less noisy. > > The maintainer can always run the full report themselves. > > Regards, > peter > Hi Peter and all, I made the decision to run 'lrc' without '-t' in response to the message below. https://lists.debian.org/debian-mentors/2024/08/msg00391.html It is easier for me to give 'lrc' output. -- Regards Phil Donate: https://buymeacoffee.com/kathenasorg -- "I play the game for the game’s own sake" Arthur Conan Doyle - The Adventure of the Bruce-Partington Plans -- Internet Relay Chat (IRC): kathenas Website: https://kathenas.org Instagram: https://instagram.com/kathenasorg Threads: https://www.threads.net/@kathenasorg --
Attachment:
signature.asc
Description: This is a digitally signed message part