Debian Bug report logs - #835376
lilyterm: please make the build 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: lilyterm: please make the build reproducible

Date: Thu, 25 Aug 2016 00:24:08 +0100

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

Source: lilyterm
Version: 0.9.9.4+git20150208.f600c0-3
Severity: wishlist
Tags: patch
User: reproducible-builds@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], I noticed
that lilyterm could not be built reproducibly.

Patch attached.

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


Regards,

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

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

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

From: Chris Lamb <lamby@debian.org>

To: 835376@bugs.debian.org

Subject: Re: Bug#835376: lilyterm: please make the build reproducible

Date: Mon, 24 Oct 2016 06:42:17 +0100

Dear Maintainer,

> Source: lilyterm
> Version: 0.9.9.4+git20150208.f600c0-3
> Tags: patch

There hasn't seem to be any update on this bug in 60 days, in which
time the Reproducible Builds effort has come on a long way. :)

Would you consider applying this patch and uploading?


Regards,

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

Message #15 received at 835376-close@bugs.debian.org (full text, mbox, reply):

From: ChangZhuo Chen (陳昌倬) <czchen@debian.org>

To: 835376-close@bugs.debian.org

Subject: Bug#835376: fixed in lilyterm 0.9.9.4+git20150208.f600c0-4

Date: Mon, 24 Oct 2016 11:42:22 +0000

Source: lilyterm
Source-Version: 0.9.9.4+git20150208.f600c0-4

We believe that the bug you reported is fixed in the latest version of
lilyterm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 835376@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
ChangZhuo Chen (陳昌倬) <czchen@debian.org> (supplier of updated lilyterm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 24 Oct 2016 18:52:52 +0800
Source: lilyterm
Binary: lilyterm
Architecture: source
Version: 0.9.9.4+git20150208.f600c0-4
Distribution: unstable
Urgency: medium
Maintainer: ChangZhuo Chen (陳昌倬) <czchen@debian.org>
Changed-By: ChangZhuo Chen (陳昌倬) <czchen@debian.org>
Description:
 lilyterm   - Light and eazy-to-use terminal emulator for X
Closes: 835376
Changes:
 lilyterm (0.9.9.4+git20150208.f600c0-4) unstable; urgency=medium
 .
   * Make the build reproducible.
     Thanks to Chris Lamb (Closes: #835376)
   * Bump Standards-Version to 3.9.8.
   * Update Vcs-* fields.
Checksums-Sha1:
 e34a3780d82196bdf25c20cd99e92652134e76de 2044 lilyterm_0.9.9.4+git20150208.f600c0-4.dsc
 cf3ae8ae2657927e858b9144e7501c3644ecf60f 3308 lilyterm_0.9.9.4+git20150208.f600c0-4.debian.tar.xz
Checksums-Sha256:
 68946c093542cb422785e69883d0837fb5e841c5c5be63908bfdcb0a9b4df869 2044 lilyterm_0.9.9.4+git20150208.f600c0-4.dsc
 42bc465957d446a5ea5e672dd8c0ded4a5f064df5a062aacd0d3e969f74494ee 3308 lilyterm_0.9.9.4+git20150208.f600c0-4.debian.tar.xz
Files:
 bc862732805fcaf8e2868c57b452f824 2044 x11 optional lilyterm_0.9.9.4+git20150208.f600c0-4.dsc
 480395ebb31618881cf113eedb92cb1e 3308 x11 optional lilyterm_0.9.9.4+git20150208.f600c0-4.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJYDejaAAoJELTYlw90nD9qmMQQAM92A76kscQM+iBmx8artwlH
Lt8nQJAxY9E30evV4R1DjsKPWplSAdKSEjr55yNIeaFIrHbuEdvNKcv5zG+vrluK
hk/RrWcmgCvNOTF5h9dkwUgmxpHfO9IUVJdYAaYSlDS497UvJuTrqcthD44V3jVS
aptIXFMpcBEfN61Jp25fOkE+9pAOA0bkGwIHY9Vtuo8v+nMhzioDNGHaT2lHf5s2
4e43OQx1N6hxfuFlSAx1DD9UZwLRBq9OpsHz1D0Fv56Vl4jTamZmhl6XziC4fsGc
doBopKwJ9SH+zaZBGezpv7pK8vHAhuT2fpz/oE8YAnOLMcLgRWU4DR3uVTUv4/NN
vN5SQNyKpVcuvpKHuWcbIsW83vlWnL+/Zf2qmt4b6YVATGRYfQmvRiaFOdpwUtpg
qlzUs53wUZIkDX4BvJe5AIWG6oWFvOZZ/WGoINPcGFDPxbrp6ERPbB/LogQI4ci9
Qvp4q1i34SlKiQarnCY5LdluNYlg6kXbRlNisbMzzD3Py2a1Rng4J48nUPJIaJPL
qzai3usD03o2Fq3MZCd1gVSQw4FduoamQhwphsuSASKjX8ySgKqXwFLMmZeGs73S
nNynWSVQXW48Jq5Xr1c0hHfdPhn/pKrK70JPV4o0L+nmN3xz3kp0EP/LxXJnHWK3
5hvfr0aY6MhcqLMYOWch
=iPx3
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.