Debian Bug report logs - #972494
libgrokj2k: please make the documentation reproducible

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: "Chris Lamb" <lamby@debian.org>

To: submit@bugs.debian.org

Subject: libgrokj2k: please make the documentation reproducible

Date: Mon, 19 Oct 2020 11:31:58 +0100

[Message part 1 (text/plain, inline)]

Source: libgrokj2k
Version: 7.6.0-1
Severity: wishlist
Tags: patch
User: reproducible-builds@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-bugs@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0] we noticed that
libgrokj2k's documentation could not be built reproducibly.

This is because the doxygen-generated HTML pages reference the
absolute build path due to use of an incorrect STRIP_FROM_PATH
directive in the Doxyfile configuration file.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

--
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org / chris-lamb.co.uk
       `-

[libgrokj2k.diff.txt (text/plain, attachment)]

Message #10 received at submit@bugs.debian.org (full text, mbox, reply):

From: Aaron Boxer <boxerab@gmail.com>

To: Chris Lamb <lamby@debian.org>, 972494@bugs.debian.org

Cc: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: Re: Bug#972494: libgrokj2k: please make the documentation reproducible

Date: Wed, 21 Oct 2020 20:17:45 -0400

[Message part 1 (text/plain, inline)]

Hi Chris,
Thank you very much! I've fixed this in my current master, and it will go
into my next release.
Unless, you think this should be patched in the current version in unstable.
Cheers,
Aaron

On Mon, Oct 19, 2020 at 6:33 AM Chris Lamb <lamby@debian.org> wrote:

> Source: libgrokj2k
> Version: 7.6.0-1
> Severity: wishlist
> Tags: patch
> User: reproducible-builds@lists.alioth.debian.org
> Usertags: buildpath
> X-Debbugs-Cc: reproducible-bugs@lists.alioth.debian.org
>
> Hi,
>
> Whilst working on the Reproducible Builds effort [0] we noticed that
> libgrokj2k's documentation could not be built reproducibly.
>
> This is because the doxygen-generated HTML pages reference the
> absolute build path due to use of an incorrect STRIP_FROM_PATH
> directive in the Doxyfile configuration file.
>
> Patch attached.
>
>  [0] https://reproducible-builds.org/
>
>
> Regards,
>
> --
>       ,''`.
>      : :'  :     Chris Lamb
>      `. `'`      lamby@debian.org / chris-lamb.co.uk
>        `-

[Message part 2 (text/html, inline)]

Message #20 received at 972494@bugs.debian.org (full text, mbox, reply):

From: "Chris Lamb" <lamby@debian.org>

To: 972494@bugs.debian.org, reproducible-bugs@lists.alioth.debian.org

Subject: Re: Bug#972494: libgrokj2k: please make the documentation reproducible

Date: Wed, 20 Jan 2021 15:51:47 +0000

Chris Lamb wrote:

> Thank you very much! I've fixed this in my current master, and it will go
> into my next release.
> Unless, you think this should be patched in the current version in unstable.

As you wish. :)


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org / chris-lamb.co.uk
       `-

Message #25 received at 972494@bugs.debian.org (full text, mbox, reply):

From: Aaron Boxer <boxerab@protonmail.com>

To: "972494@bugs.debian.org" <972494@bugs.debian.org>, Chris Lamb <lamby@debian.org>

Subject: Bug#972494: libgrokj2k: please make the documentation reproducible

Date: Sat, 10 Sep 2022 13:49:08 +0000

[Message part 1 (text/plain, inline)]

Hello,

This bug was fixed long ago, the current unstable version no longer has this issue.
What must happen for this to be closed ?

Thanks,
Aaron

Sent with [Proton Mail](https://proton.me/) secure email.

[Message part 2 (text/html, inline)]

Message #30 received at 972494@bugs.debian.org (full text, mbox, reply):

From: "Chris Lamb" <lamby@debian.org>

To: "Aaron Boxer" <boxerab@protonmail.com>, "972494@bugs.debian.org" <972494@bugs.debian.org>

Subject: Re: Bug#972494: libgrokj2k: please make the documentation reproducible

Date: Sun, 11 Sep 2022 09:59:34 +0100

Aaron Boxer wrote:

> Attachments:
> * pgp-encrypted
> * encrypted.asc

Please could you resend your reply without encryption? Many thanks. :)


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org 🍥 chris-lamb.co.uk
       `-

Message #35 received at 972494@bugs.debian.org (full text, mbox, reply):

From: Aaron Boxer <boxerab@gmail.com>

To: 972494@bugs.debian.org, Chris Lamb <lamby@debian.org>

Subject: RE: Bug#972494: libgrokj2k: please make the documentation reproducible

Date: Sun, 11 Sep 2022 10:47:48 -0400

[Message part 1 (text/plain, inline)]

Hello,

This bug was fixed long ago, the current unstable version 10.0.0.1 no
longer has this issue.
What must happen for this to be closed ?

Thanks,
Aaron

[Message part 2 (text/html, inline)]

Message #40 received at 972494@bugs.debian.org (full text, mbox, reply):

From: "Chris Lamb" <lamby@debian.org>

To: "Aaron Boxer" <boxerab@gmail.com>, 972494@bugs.debian.org

Subject: Re: Bug#972494: libgrokj2k: please make the documentation reproducible

Date: Mon, 12 Sep 2022 07:30:19 +0100

Aaron Boxer wrote:

> Hello,
>
> This bug was fixed long ago, the current unstable version 10.0.0.1 no 
> longer has this issue. What must happen for this to be closed ?

You can find instructions on how to close bugs on this page:

  https://www.debian.org/Bugs/Developer#closing

Specifically:

    Bug reports should be closed by sending email to
    nnn-done@bugs.debian.org. The message body needs to contain an
    explanation of how the bug was fixed.

    With the emails received from the bug tracking system, all you
    need to do to close the bug is to make a Reply in your mail reader
    program and edit the To field to say nnn-done@bugs.debian.org
    instead of nnn@bugs.debian.org (nnn-close is provided as an alias
    for nnn-done).

As it was fixed in a particular version, do look at the next line:

    Where applicable, please supply a Version line in the
    pseudo-header of your message when closing a bug, so that the bug
    tracking system knows which releases of the package contain the
    fix.

... although this should be the Debian package version number (ie.
something ending in "-1") rather than the raw upstream version.

Hope this helps. :)


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org 🍥 chris-lamb.co.uk
       `-

Message #45 received at 972494@bugs.debian.org (full text, mbox, reply):

From: Aaron Boxer <boxerab@protonmail.com>

To: Chris Lamb <lamby@debian.org>, "972494-done@bugs.debian.org" <972494-done@bugs.debian.org>

Cc: Aaron Boxer <boxerab@gmail.com>, 972494@bugs.debian.org

Subject: Re: Bug#972494: libgrokj2k: please make the documentation reproducible

Date: Mon, 12 Sep 2022 12:18:07 +0000

Version 10.0.0.1

Below is patch kindly provided by Chris Lamb to fix the issue:

--- a/debian/patches/reproducible-build.patch	1970-01-01 01:00:00.000000000 +0100
--- b/debian/patches/reproducible-build.patch	2020-10-19 11:22:36.481731173 +0100
@@ -0,0 +1,15 @@
+Description: Make the build reproducible
+Author: Chris Lamb <lamby@debian.org>
+Last-Update: 2020-10-19
+
+--- libgrokj2k-7.6.0.orig/doc/Doxyfile.dox.cmake.in
++++ libgrokj2k-7.6.0/doc/Doxyfile.dox.cmake.in
+@@ -25,7 +25,7 @@ ABBREVIATE_BRIEF       = "The $name clas
+ ALWAYS_DETAILED_SEC    = NO
+ INLINE_INHERITED_MEMB  = NO
+ FULL_PATH_NAMES        = NO
+-STRIP_FROM_PATH        = C://
++STRIP_FROM_PATH        = @GROK_BINARY_DIR@
+ STRIP_FROM_INC_PATH    =
+ SHORT_NAMES            = NO
+ JAVADOC_AUTOBRIEF      = YES
--- a/debian/patches/series	1970-01-01 01:00:00.000000000 +0100
--- b/debian/patches/series	2020-10-19 11:22:34.921708545 +0100
@@ -0,0 +1 @@
+reproducible-build.patch




Sent with Proton Mail secure email.

------- Original Message -------
On Monday, September 12th, 2022 at 02:30, Chris Lamb <lamby@debian.org> wrote:


> Aaron Boxer wrote:
> 
> > Hello,
> > 
> > This bug was fixed long ago, the current unstable version 10.0.0.1 no
> > longer has this issue. What must happen for this to be closed ?
> 
> 
> You can find instructions on how to close bugs on this page:
> 
> https://www.debian.org/Bugs/Developer#closing
> 
> Specifically:
> 
> Bug reports should be closed by sending email to
> nnn-done@bugs.debian.org. The message body needs to contain an
> explanation of how the bug was fixed.
> 
> With the emails received from the bug tracking system, all you
> need to do to close the bug is to make a Reply in your mail reader
> program and edit the To field to say nnn-done@bugs.debian.org
> instead of nnn@bugs.debian.org (nnn-close is provided as an alias
> for nnn-done).
> 
> As it was fixed in a particular version, do look at the next line:
> 
> Where applicable, please supply a Version line in the
> pseudo-header of your message when closing a bug, so that the bug
> tracking system knows which releases of the package contain the
> fix.
> 
> ... although this should be the Debian package version number (ie.
> something ending in "-1") rather than the raw upstream version.
> 
> Hope this helps. :)
> 
> 
> Regards,
> 
> --
> ,''`. : :' : Chris Lamb` . `'` lamby@debian.org 🍥 chris-lamb.co.uk
> `-

Message #51 received at 972494-done@bugs.debian.org (full text, mbox, reply):

From: Aaron Boxer <boxerab@gmail.com>

To: "972494-done@bugs.debian.org" <972494-done@bugs.debian.org>

Cc: Chris Lamb <lamby@debian.org>

Subject: Re: Bug#972494: libgrokj2k: please make the documentation reproducible

Date: Mon, 12 Sep 2022 08:33:06 -0400

[Message part 1 (text/plain, inline)]

Version 10.0.0.1

Below is the patch kindly provided by Chris Lamb to fix the issue:



> --- a/debian/patches/reproducible-build.patch   1970-01-01
> 01:00:00.000000000 +0100
> --- b/debian/patches/reproducible-build.patch   2020-10-19
> 11:22:36.481731173 +0100
> @@ -0,0 +1,15 @@
> +Description: Make the build reproducible
> +Author: Chris Lamb <lamby@debian.org>
> +Last-Update: 2020-10-19
> +
> +--- libgrokj2k-7.6.0.orig/doc/Doxyfile.dox.cmake.in
> ++++ libgrokj2k-7.6.0/doc/Doxyfile.dox.cmake.in
> +@@ -25,7 +25,7 @@ ABBREVIATE_BRIEF       = "The $name clas
> + ALWAYS_DETAILED_SEC    = NO
> + INLINE_INHERITED_MEMB  = NO
> + FULL_PATH_NAMES        = NO
> +-STRIP_FROM_PATH        = C://
> ++STRIP_FROM_PATH        = @GROK_BINARY_DIR@
> + STRIP_FROM_INC_PATH    =
> + SHORT_NAMES            = NO
> + JAVADOC_AUTOBRIEF      = YES
> --- a/debian/patches/series     1970-01-01 01:00:00.000000000 +0100
> --- b/debian/patches/series     2020-10-19 11:22:34.921708545 +0100
> @@ -0,0 +1 @@
> +reproducible-build.patch
>
>
>
>
> Sent with Proton Mail secure email.
>
> ------- Original Message -------
> On Monday, September 12th, 2022 at 02:30, Chris Lamb <lamby@debian.org>
> wrote:
>
>
> > Aaron Boxer wrote:
> >
> > > Hello,
> > >
> > > This bug was fixed long ago, the current unstable version 10.0.0.1 no
> > > longer has this issue. What must happen for this to be closed ?
> >
> >
> > You can find instructions on how to close bugs on this page:
> >
> > https://www.debian.org/Bugs/Developer#closing
> >
> > Specifically:
> >
> > Bug reports should be closed by sending email to
> > nnn-done@bugs.debian.org. The message body needs to contain an
> > explanation of how the bug was fixed.
> >
> > With the emails received from the bug tracking system, all you
> > need to do to close the bug is to make a Reply in your mail reader
> > program and edit the To field to say nnn-done@bugs.debian.org
> > instead of nnn@bugs.debian.org (nnn-close is provided as an alias
> > for nnn-done).
> >
> > As it was fixed in a particular version, do look at the next line:
> >
> > Where applicable, please supply a Version line in the
> > pseudo-header of your message when closing a bug, so that the bug
> > tracking system knows which releases of the package contain the
> > fix.
> >
> > ... although this should be the Debian package version number (ie.
> > something ending in "-1") rather than the raw upstream version.
> >
> > Hope this helps. :)
> >
> >
> > Regards,
> >
> > --
> > ,''`. : :' : Chris Lamb` . `'` lamby@debian.org 🍥 chris-lamb.co.uk
> > `-
>

[Message part 2 (text/html, inline)]

Send a report that this bug log contains spam.