Re: Packaging new library very similar to another library

2020-03-13 Thread Aaron Boxer
On Fri, Mar 13, 2020 at 10:22 AM Andrey Rahmatullin wrote: > On Thu, Mar 12, 2020 at 05:25:48PM -0400, Aaron Boxer wrote: > > > > but I get the following error: > > > > > > > > dpkg-source: error: can't build with source format '3.0 (quilt)': no > > > > upstream tarball found at > > > ../grok-jpe

Re: Packaging new library very similar to another library

2020-03-13 Thread Andrey Rahmatullin
On Thu, Mar 12, 2020 at 05:25:48PM -0400, Aaron Boxer wrote: > > > but I get the following error: > > > > > > dpkg-source: error: can't build with source format '3.0 (quilt)': no > > > upstream tarball found at > > ../grok-jpeg2000_4.2.0.orig.tar.{bz2,gz,lzma,xz} > > > Where is it looking for the t

Re: Packaging new library very similar to another library

2020-03-12 Thread Aaron Boxer
On Thu, Mar 12, 2020 at 3:21 PM Andrey Rahmatullin wrote: > On Thu, Mar 12, 2020 at 02:05:48PM -0400, Aaron Boxer wrote: > > > > > > Besides the copyright file, I would like to test building the > > > package. > > > > > > What's the best way of doing this? I am on > > > > > > Ubuntu Eoan. Thanks

Re: Packaging new library very similar to another library

2020-03-12 Thread Andrey Rahmatullin
On Thu, Mar 12, 2020 at 02:05:48PM -0400, Aaron Boxer wrote: > > > > > Besides the copyright file, I would like to test building the > > package. > > > > > What's the best way of doing this? I am on > > > > > Ubuntu Eoan. Thanks! > > > > Get a sid system (chroot is probably fine). Install and conf

Re: Packaging new library very similar to another library

2020-03-12 Thread Aaron Boxer
On Thu, Mar 12, 2020 at 1:26 PM Andrey Rahmatullin wrote: > On Thu, Mar 12, 2020 at 01:17:29PM -0400, Aaron Boxer wrote: > > On Thu, Mar 12, 2020 at 1:00 PM Andrey Rahmatullin > wrote: > > > > > On Thu, Mar 12, 2020 at 12:49:25PM -0400, Aaron Boxer wrote: > > > > Besides the copyright file, I wo

Re: Packaging new library very similar to another library

2020-03-12 Thread Andrey Rahmatullin
On Thu, Mar 12, 2020 at 01:17:29PM -0400, Aaron Boxer wrote: > On Thu, Mar 12, 2020 at 1:00 PM Andrey Rahmatullin wrote: > > > On Thu, Mar 12, 2020 at 12:49:25PM -0400, Aaron Boxer wrote: > > > Besides the copyright file, I would like to test building the package. > > > What's the best way of doi

Re: Packaging new library very similar to another library

2020-03-12 Thread Aaron Boxer
On Thu, Mar 12, 2020 at 1:00 PM Andrey Rahmatullin wrote: > On Thu, Mar 12, 2020 at 12:49:25PM -0400, Aaron Boxer wrote: > > Besides the copyright file, I would like to test building the package. > > What's the best way of doing this? I am on > > Ubuntu Eoan. Thanks! > Get a sid system (chroot i

Re: Packaging new library very similar to another library

2020-03-12 Thread Andrey Rahmatullin
On Thu, Mar 12, 2020 at 12:49:25PM -0400, Aaron Boxer wrote: > Besides the copyright file, I would like to test building the package. > What's the best way of doing this? I am on > Ubuntu Eoan. Thanks! Get a sid system (chroot is probably fine). Install and configure pbuilder or sbuild there. You

Re: Packaging new library very similar to another library

2020-03-12 Thread Aaron Boxer
On Tue, Mar 10, 2020 at 2:38 PM Aaron Boxer wrote: > > > On Tue, Mar 10, 2020 at 8:46 AM Sudip Mukherjee < > sudipm.mukher...@gmail.com> wrote: > >> On Tue, Mar 10, 2020 at 12:29 PM Aaron Boxer wrote: >> > >> > Thanks, Sudip! I've made those changes, and renamed the library to >> grok-jpeg2000 >

Re: Packaging new library very similar to another library

2020-03-10 Thread Aaron Boxer
On Tue, Mar 10, 2020 at 8:46 AM Sudip Mukherjee wrote: > On Tue, Mar 10, 2020 at 12:29 PM Aaron Boxer wrote: > > > > Thanks, Sudip! I've made those changes, and renamed the library to > grok-jpeg2000 > > > > The only thing missing right now is the copyright file. Is there a way > of automaticall

Re: Packaging new library very similar to another library

2020-03-10 Thread Sudip Mukherjee
On Tue, Mar 10, 2020 at 12:29 PM Aaron Boxer wrote: > > Thanks, Sudip! I've made those changes, and renamed the library to > grok-jpeg2000 > > The only thing missing right now is the copyright file. Is there a way of > automatically parsing all > .cpp/.h files in the project and generating a lis

Re: Packaging new library very similar to another library

2020-03-10 Thread Aaron Boxer
Thanks, Sudip! I've made those changes, and renamed the library to grok-jpeg2000 The only thing missing right now is the copyright file. Is there a way of automatically parsing all .cpp/.h files in the project and generating a list of the copyrights ? On Tue, Mar 10, 2020 at 6:26 AM Sudip Mukherj

Re: Packaging new library very similar to another library

2020-03-10 Thread Sudip Mukherjee
On Mon, Mar 9, 2020 at 11:52 PM Aaron Boxer wrote: > > I've made a first pass at the packaging. If anyone has time to review, it > would be great: > > https://github.com/GrokImageCompression/grok/tree/master/debian Just few things from a quick look. 1. compat level is too old, current one is 12

Re: Packaging new library very similar to another library

2020-03-09 Thread Aaron Boxer
I've made a first pass at the packaging. If anyone has time to review, it would be great: https://github.com/GrokImageCompression/grok/tree/master/debian Thanks! On Mon, Mar 9, 2020 at 2:25 PM Aaron Boxer wrote: > > On Mon, Mar 9, 2020 at 1:42 PM Andrey Rahmatullin wrote: > >> On Mon, Mar 09,

Re: Packaging new library very similar to another library

2020-03-09 Thread Aaron Boxer
On Mon, Mar 9, 2020 at 1:42 PM Andrey Rahmatullin wrote: > On Mon, Mar 09, 2020 at 12:56:41PM -0400, Aaron Boxer wrote: > > Thanks, guys. Another question (first time creating a package): is it > > possible to unpack > > the openjpeg .deb and re-use the packaging ? > No, there is no packaging in

Re: Packaging new library very similar to another library

2020-03-09 Thread Andrey Rahmatullin
On Mon, Mar 09, 2020 at 12:56:41PM -0400, Aaron Boxer wrote: > Thanks, guys. Another question (first time creating a package): is it > possible to unpack > the openjpeg .deb and re-use the packaging ? No, there is no packaging in the .deb. Packaging is in the source packages: https://wiki.debian.o

Re: Packaging new library very similar to another library

2020-03-09 Thread Aaron Boxer
Thanks, guys. Another question (first time creating a package): is it possible to unpack the openjpeg .deb and re-use the packaging ? On Sun, Mar 8, 2020 at 2:41 PM Andrey Rahmatullin wrote: > On Sun, Mar 08, 2020 at 02:30:06PM -0400, Aaron Boxer wrote: > > Hello! > > I maintain an image compres

Re: Packaging new library very similar to another library

2020-03-08 Thread Andrey Rahmatullin
On Sun, Mar 08, 2020 at 02:30:06PM -0400, Aaron Boxer wrote: > Hello! > I maintain an image compression library > > https://github.com/GrokImageCompression/grok > > which is very similar to an existing package in debian: > > https://packages.debian.org/search?keywords=openjpeg > > I would like

Re: Packaging new library very similar to another library

2020-03-08 Thread Scott Kitterman
On Sunday, March 8, 2020 2:32:54 PM EDT Aaron Boxer wrote: > Correction: this is the current package for openjpeg: > > https://tracker.debian.org/pkg/openjpeg2 > > On Sun, Mar 8, 2020 at 2:30 PM Aaron Boxer wrote: > > Hello! > > I maintain an image compression library > > > > https://github.com

Re: Packaging new library very similar to another library

2020-03-08 Thread Aaron Boxer
Correction: this is the current package for openjpeg: https://tracker.debian.org/pkg/openjpeg2 On Sun, Mar 8, 2020 at 2:30 PM Aaron Boxer wrote: > Hello! > I maintain an image compression library > > https://github.com/GrokImageCompression/grok > > which is very similar to an existing package i

Packaging new library very similar to another library

2020-03-08 Thread Aaron Boxer
Hello! I maintain an image compression library https://github.com/GrokImageCompression/grok which is very similar to an existing package in debian: https://packages.debian.org/search?keywords=openjpeg I would like to package my library and add it to debian - can I re-use the packaging from Open