Re: Packaging new library very similar to another library
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-jpeg2000_4.2.0.orig.tar.{bz2,gz,lzma,xz}
> > > > Where is it looking for the tarball ?
> > > Just like it tells you, in the parent directory. Did you put it there?
> > > Note that it needs to have a specific name.
> > >
> >
> > Thanks, solved via
> >
> > dpkg-buildpackage -b -rfakeroot -us -uc
> This way you skipped creating a source package.
> You cannot upload this to Debian.
>
Thanks, dpkg-buildpackage let me work out the build issues.
I will now take a look at pbuilder
>
> --
> WBR, wRAR
>
Re: Packaging new library very similar to another library
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 tarball ?
> > Just like it tells you, in the parent directory. Did you put it there?
> > Note that it needs to have a specific name.
> >
>
> Thanks, solved via
>
> dpkg-buildpackage -b -rfakeroot -us -uc
This way you skipped creating a source package.
You cannot upload this to Debian.
--
WBR, wRAR
signature.asc
Description: PGP signature
Re: Packaging new library very similar to another library
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!
> > > > > Get a sid system (chroot is probably fine). Install and configure
> > > pbuilder
> > > > > or sbuild there. You will also need this system to actually test
> the
> > > > > resulting package and act on bug reports, if you want to maintain
> this
> > > > > package in sid.
> > > > > I don't recommend running any packaging tools on non-sid,
> especially on
> > > > > Ubuntu, unless you know the difference in behavior.
> > > > >
> > > >
> > > > Thanks, Andrey. I have followed steps to set up sid system with
> schroot.
> > > > How can I test package build using rules file ?
> > > Install and configure pbuilder or sbuild there. Build your package
> using
> > > that.
> > >
> >
> > Thanks, I am using
> >
> > dpkg-buildpackage -us -uc
> I told you to use pbuilder or sbuild. They would give the same error, but
> still.
>
> > 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 tarball ?
> Just like it tells you, in the parent directory. Did you put it there?
> Note that it needs to have a specific name.
>
Thanks, solved via
dpkg-buildpackage -b -rfakeroot -us -uc
>
> --
> WBR, wRAR
>
Re: Packaging new library very similar to another library
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 configure
> > pbuilder
> > > > or sbuild there. You will also need this system to actually test the
> > > > resulting package and act on bug reports, if you want to maintain this
> > > > package in sid.
> > > > I don't recommend running any packaging tools on non-sid, especially on
> > > > Ubuntu, unless you know the difference in behavior.
> > > >
> > >
> > > Thanks, Andrey. I have followed steps to set up sid system with schroot.
> > > How can I test package build using rules file ?
> > Install and configure pbuilder or sbuild there. Build your package using
> > that.
> >
>
> Thanks, I am using
>
> dpkg-buildpackage -us -uc
I told you to use pbuilder or sbuild. They would give the same error, but
still.
> 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 tarball ?
Just like it tells you, in the parent directory. Did you put it there?
Note that it needs to have a specific name.
--
WBR, wRAR
signature.asc
Description: PGP signature
Re: Packaging new library very similar to another library
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 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 will also need this system to actually test the
> > > resulting package and act on bug reports, if you want to maintain this
> > > package in sid.
> > > I don't recommend running any packaging tools on non-sid, especially on
> > > Ubuntu, unless you know the difference in behavior.
> > >
> >
> > Thanks, Andrey. I have followed steps to set up sid system with schroot.
> > How can I test package build using rules file ?
> Install and configure pbuilder or sbuild there. Build your package using
> that.
>
Thanks, I am using
dpkg-buildpackage -us -uc
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 tarball ?
> --
> WBR, wRAR
>
Re: Packaging new library very similar to another library
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 doing this? I am on > > > Ubuntu Eoan. Thanks! > > Get a sid system (chroot is probably fine). Install and configure pbuilder > > or sbuild there. You will also need this system to actually test the > > resulting package and act on bug reports, if you want to maintain this > > package in sid. > > I don't recommend running any packaging tools on non-sid, especially on > > Ubuntu, unless you know the difference in behavior. > > > > Thanks, Andrey. I have followed steps to set up sid system with schroot. > How can I test package build using rules file ? Install and configure pbuilder or sbuild there. Build your package using that. -- WBR, wRAR signature.asc Description: PGP signature
Re: Packaging new library very similar to another library
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 is probably fine). Install and configure pbuilder > or sbuild there. You will also need this system to actually test the > resulting package and act on bug reports, if you want to maintain this > package in sid. > I don't recommend running any packaging tools on non-sid, especially on > Ubuntu, unless you know the difference in behavior. > Thanks, Andrey. I have followed steps to set up sid system with schroot. How can I test package build using rules file ? > > -- > WBR, wRAR >
Re: Packaging new library very similar to another library
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 will also need this system to actually test the resulting package and act on bug reports, if you want to maintain this package in sid. I don't recommend running any packaging tools on non-sid, especially on Ubuntu, unless you know the difference in behavior. -- WBR, wRAR signature.asc Description: PGP signature
Re: Packaging new library very similar to another library
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 >> > >> > 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 ? >> >> There are some tools, you can check >> https://wiki.debian.org/CopyrightReviewTools >> But you will need to check manually also to verify what the tool has >> given is actually correct. >> > > 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
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 automatically parsing all > > .cpp/.h files in the project and generating a list of the copyrights ? > > There are some tools, you can check > https://wiki.debian.org/CopyrightReviewTools > But you will need to check manually also to verify what the tool has > given is actually correct. > Thanks, I will try that.
Re: Packaging new library very similar to another library
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 list of the copyrights ? There are some tools, you can check https://wiki.debian.org/CopyrightReviewTools But you will need to check manually also to verify what the tool has given is actually correct. -- Regards Sudip
Re: Packaging new library very similar to another library
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 Mukherjee wrote: > 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. > 2. Standards-Version is also old. current is 4.5.0 > 3. You can not use the name "grok" as source, its already taken. > (https://tracker.debian.org/pkg/grok) > 4. I am hoping you will be maintaining the package, so Maintainer should > be you. > 5. You can drop the Uploaders unless it is team maintained. > (https://www.debian.org/doc/debian-policy/ch-controlfields.html#uploaders) > 6. Vcs-* should have the link to the repo where the debian package > source will live. It can be github if you want. > 7. Since there is no patch, you can drop the d/patch folder. > > -- > Regards > Sudip >
Re: Packaging new library very similar to another library
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. 2. Standards-Version is also old. current is 4.5.0 3. You can not use the name "grok" as source, its already taken. (https://tracker.debian.org/pkg/grok) 4. I am hoping you will be maintaining the package, so Maintainer should be you. 5. You can drop the Uploaders unless it is team maintained. (https://www.debian.org/doc/debian-policy/ch-controlfields.html#uploaders) 6. Vcs-* should have the link to the repo where the debian package source will live. It can be github if you want. 7. Since there is no patch, you can drop the d/patch folder. -- Regards Sudip
Re: Packaging new library very similar to another library
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, 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.org/Packaging/SourcePackage > > > Great, thank you ! > > > >
Re: Packaging new library very similar to another library
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 the .deb. > Packaging is in the source packages: > https://wiki.debian.org/Packaging/SourcePackage Great, thank you !
Re: Packaging new library very similar to another library
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.org/Packaging/SourcePackage -- WBR, wRAR signature.asc Description: PGP signature
Re: Packaging new library very similar to another library
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 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 OpenJPEG to do that ? > Yes, though you should mention the copyright for debian/* in your > debian/copyright. > > -- > WBR, wRAR >
Re: Packaging new library very similar to another library
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 to package my library and add it to debian - can I re-use the > packaging from OpenJPEG to do that ? Yes, though you should mention the copyright for debian/* in your debian/copyright. -- WBR, wRAR signature.asc Description: PGP signature
Re: Packaging new library very similar to another library
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/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 OpenJPEG to do that ? > > > > Thank you! > > Aaron Boxer According to the packages debian/copyright file [1] you can as long as you follow the terms of the BSD 2 clause license (there is a copy of the license there too). Scott K [1] https://tracker.debian.org/media/packages/o/openjpeg2/copyright-2.3.1-1 signature.asc Description: This is a digitally signed message part.
Re: Packaging new library very similar to another library
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 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 OpenJPEG to do that ? > > Thank you! > Aaron Boxer >
Packaging new library very similar to another library
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 OpenJPEG to do that ? Thank you! Aaron Boxer
