Bug#1010378: leds-alix: reproducible builds: source tarball embeds timestamps and umask
Source: leds-alix Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps umask X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org leds-alix-source embeds the timestamp and file permissions determined by umask in the leds-alix source tarball: https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope-results/leds-alix.html /usr/src/leds-alix.tar.bz2 -rw-r--r--···0·root·(0)·root·(0)·3610·2022-04-15·23:37:31.00·modules/leds-alix/leds-alix.c vs. -rw-rw-r--···0·root·(0)·root·(0)·3610·2023-05-19·06:01:18.00·modules/leds-alix/leds-alix.c The attached patch fixes this by passing arguments to tar in debian/rules to ensure consistent timestamp, file permissions, sort order, user, group, uid and gid in the generated tarball. With this patch applied, leds-alix should become reproducible on tests.reproducible-builds.org! live well, vagrant From 7f79cf28e70fdc2c0832f10517f29f7a9be3b61e Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Fri, 29 Apr 2022 21:35:18 + Subject: [PATCH 1/2] debian/rules: Generate tarball reproducibly. Pass arguments to tar to set sort order, timestamps, owner, group and mode. --- debian/rules | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/rules b/debian/rules index 1068a59..59012aa 100755 --- a/debian/rules +++ b/debian/rules @@ -48,7 +48,7 @@ install: build dh_installdirs -p$(psource) usr/src/modules/$(sname)/debian cp Makefile leds-alix.c $(DESTDIR) cp debian/*modules.in* debian/control debian/rules debian/changelog debian/copyright debian/README.Debian $(DESTDIR)/debian - cd debian/$(psource)/usr/src && tar c modules | bzip2 -9 > $(sname).tar.bz2 && rm -rf modules + cd debian/$(psource)/usr/src && tar --sort=name --mtime="@$(SOURCE_DATE_EPOCH)" --owner=0 --group=0 --numeric-owner --mode=go=rX,u+rw,a-s --create modules | bzip2 -9 > $(sname).tar.bz2 && rm -rf modules dh_install binary-indep: build install -- 2.30.2 signature.asc Description: PGP signature
Bug#1010378: marked as done (leds-alix: reproducible builds: source tarball embeds timestamps and umask)
Your message dated Fri, 29 Apr 2022 22:49:49 + with message-id and subject line Bug#1010378: fixed in leds-alix 0.0.1-3 has caused the Debian Bug report #1010378, regarding leds-alix: reproducible builds: source tarball embeds timestamps and umask to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1010378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: leds-alix Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps umask X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org leds-alix-source embeds the timestamp and file permissions determined by umask in the leds-alix source tarball: https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope-results/leds-alix.html /usr/src/leds-alix.tar.bz2 -rw-r--r--···0·root·(0)·root·(0)·3610·2022-04-15·23:37:31.00·modules/leds-alix/leds-alix.c vs. -rw-rw-r--···0·root·(0)·root·(0)·3610·2023-05-19·06:01:18.00·modules/leds-alix/leds-alix.c The attached patch fixes this by passing arguments to tar in debian/rules to ensure consistent timestamp, file permissions, sort order, user, group, uid and gid in the generated tarball. With this patch applied, leds-alix should become reproducible on tests.reproducible-builds.org! live well, vagrant From 7f79cf28e70fdc2c0832f10517f29f7a9be3b61e Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Fri, 29 Apr 2022 21:35:18 + Subject: [PATCH 1/2] debian/rules: Generate tarball reproducibly. Pass arguments to tar to set sort order, timestamps, owner, group and mode. --- debian/rules | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/rules b/debian/rules index 1068a59..59012aa 100755 --- a/debian/rules +++ b/debian/rules @@ -48,7 +48,7 @@ install: build dh_installdirs -p$(psource) usr/src/modules/$(sname)/debian cp Makefile leds-alix.c $(DESTDIR) cp debian/*modules.in* debian/control debian/rules debian/changelog debian/copyright debian/README.Debian $(DESTDIR)/debian - cd debian/$(psource)/usr/src && tar c modules | bzip2 -9 > $(sname).tar.bz2 && rm -rf modules + cd debian/$(psource)/usr/src && tar --sort=name --mtime="@$(SOURCE_DATE_EPOCH)" --owner=0 --group=0 --numeric-owner --mode=go=rX,u+rw,a-s --create modules | bzip2 -9 > $(sname).tar.bz2 && rm -rf modules dh_install binary-indep: build install -- 2.30.2 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: leds-alix Source-Version: 0.0.1-3 Done: Vagrant Cascadian We believe that the bug you reported is fixed in the latest version of leds-alix, 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 1010...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vagrant Cascadian (supplier of updated leds-alix 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 29 Apr 2022 15:28:19 -0700 Source: leds-alix Architecture: source Version: 0.0.1-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Vagrant Cascadian Closes: 1010378 Changes: leds-alix (0.0.1-3) unstable; urgency=medium . * QA upload. * debian/rules: Generate tarball reproducibly (Closes: #1010378). * debian/control: Set Rules-Requires-Root to no. Checksums-Sha1: 91705a87380d14d7aa08a94a3d73a43ec393a593 1285 leds-alix_0.0.1-3.dsc 21edea84a5d736b6aac6dc0010289619a9d72e24 3836 leds-alix_0.0.1-3.debian.tar.xz 25f06896ba308d47ed1413b6e433e018bd591dcb 5228 leds-alix_0.0.1-3_amd64.buildinfo Checksums-Sha256: c641597ad2a731b1368f764c8056b7f6a3b80436eb9f57b46b1c52961fac41b3 1285 leds-alix_0.0.1-3.dsc 4747ef20e49e02d9d7c65dd7480303d433ba97d1e04004d24be74fcad3e9743f 3836 leds-alix_0.0.1-3.debian.tar.xz f261815c6a2f551bc9d555736c09e51836ba949769f30551047d894c8806c454 5228 leds-alix_0.0.1-3_amd64.buildinfo Files: d12c639e3b84915aa49c2138ff729273 1285 utils optional leds-alix_0.0.1-3.dsc d300159a4e14875508008db2ff2db5ff 3836 utils optional leds-alix_0.0.1-3.debian.tar.xz 5f8f71d61e00d16b5e57833
Processing of leds-alix_0.0.1-3_source.changes
leds-alix_0.0.1-3_source.changes uploaded successfully to localhost along with the files: leds-alix_0.0.1-3.dsc leds-alix_0.0.1-3.debian.tar.xz leds-alix_0.0.1-3_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
leds-alix_0.0.1-3_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 29 Apr 2022 15:28:19 -0700 Source: leds-alix Architecture: source Version: 0.0.1-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Vagrant Cascadian Closes: 1010378 Changes: leds-alix (0.0.1-3) unstable; urgency=medium . * QA upload. * debian/rules: Generate tarball reproducibly (Closes: #1010378). * debian/control: Set Rules-Requires-Root to no. Checksums-Sha1: 91705a87380d14d7aa08a94a3d73a43ec393a593 1285 leds-alix_0.0.1-3.dsc 21edea84a5d736b6aac6dc0010289619a9d72e24 3836 leds-alix_0.0.1-3.debian.tar.xz 25f06896ba308d47ed1413b6e433e018bd591dcb 5228 leds-alix_0.0.1-3_amd64.buildinfo Checksums-Sha256: c641597ad2a731b1368f764c8056b7f6a3b80436eb9f57b46b1c52961fac41b3 1285 leds-alix_0.0.1-3.dsc 4747ef20e49e02d9d7c65dd7480303d433ba97d1e04004d24be74fcad3e9743f 3836 leds-alix_0.0.1-3.debian.tar.xz f261815c6a2f551bc9d555736c09e51836ba949769f30551047d894c8806c454 5228 leds-alix_0.0.1-3_amd64.buildinfo Files: d12c639e3b84915aa49c2138ff729273 1285 utils optional leds-alix_0.0.1-3.dsc d300159a4e14875508008db2ff2db5ff 3836 utils optional leds-alix_0.0.1-3.debian.tar.xz 5f8f71d61e00d16b5e57833d2013886f 5228 utils optional leds-alix_0.0.1-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iJYEARYKAD4WIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCYmxoZCAcdmFncmFudEBy ZXByb2R1Y2libGUtYnVpbGRzLm9yZwAKCRDcUY/If5cWquvpAP0UqBhQt8kq0KB5 JeOxUV7kidaxdH4el9rrdtmmhIfkfwD+Prsu00LDfDM1XbURmhx6xZDbjEMIIboU li70z0Kf+w8= =boqQ -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#1010379: snacc: reproducible builds: timestamp embedded in header files
Source: snacc Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Various header files embed the timestamp when it was generated in comments: https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope-results/snacc.html /usr/include/snacc/c/asn-useful.h ·*This·.h·file·was·generated·by·snacc·on·Fri·May·19·17:42:30·2023 vs. ·*This·.h·file·was·generated·by·snacc·on·Sun·Apr·17·13:25:08·2022 The attached patch fixes this by removing the timestamps from the code that generates the header files. With this patch applied, snacc should become reproducible on tests.reproducible-builds.org! live well, vagrant From d44bf7e4857b23f94319aabf0bd3124a9b11ce58 Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Fri, 29 Apr 2022 23:05:46 + Subject: [PATCH] reproducible builds: Remove timestamps from generated comments. https://reproducible-builds.org/docs/timestamps/ --- compiler/back-ends/c++-gen/gen-code.c | 4 ++-- compiler/back-ends/c-gen/gen-code.c | 4 ++-- compiler/back-ends/idl-gen/gen-code.c | 2 +- compiler/core/snacc.c | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/compiler/back-ends/c++-gen/gen-code.c b/compiler/back-ends/c++-gen/gen-code.c index d3632dd..8d15682 100644 --- a/compiler/back-ends/c++-gen/gen-code.c +++ b/compiler/back-ends/c++-gen/gen-code.c @@ -170,7 +170,7 @@ PrintHdrComment PARAMS ((hdr, m), fprintf (hdr, "//\n"); fprintf (hdr, "// %s - class definitions for ASN.1 module %s\n", m->cxxHdrFileName, m->modId->name); fprintf (hdr, "//\n"); -fprintf (hdr, "// This file was generated by snacc on %s", ctime (&now)); +fprintf (hdr, "// This file was generated by snacc"); fprintf (hdr, "// UBC snacc by Mike Sample\n"); fprintf (hdr, "// A couple of enhancements made by IBM European Networking Center\n"); /* 20.8.93 Thomas Meyer */ fprintf (hdr, "\n"); @@ -188,7 +188,7 @@ PrintSrcComment PARAMS ((src, m), fprintf (src, "//\n"); fprintf (src, "// %s - class member functions for ASN.1 module %s\n", m->cxxSrcFileName, m->modId->name); fprintf (src, "//\n"); -fprintf (src, "// This file was generated by snacc on %s", ctime (&now)); +fprintf (src, "// This file was generated by snacc"); fprintf (src, "// UBC snacc written by Mike Sample\n"); fprintf (src, "// A couple of enhancements made by IBM European Networking Center\n"); /* 20.8.93 Thomas Meyer */ fprintf (src, "\n"); diff --git a/compiler/back-ends/c-gen/gen-code.c b/compiler/back-ends/c-gen/gen-code.c index e5c94d9..a198676 100644 --- a/compiler/back-ends/c-gen/gen-code.c +++ b/compiler/back-ends/c-gen/gen-code.c @@ -182,7 +182,7 @@ PrintCSrcComment PARAMS ((src, m), fprintf (src, "/*\n"); fprintf (src, " *%s\n *\n", m->cSrcFileName); fprintf (src, " *\"%s\" ASN.1 module encode/decode/print/free C src.\n *\n", m->modId->name); -fprintf (src, " *This file was generated by snacc on %s *\n", ctime (&t)); +fprintf (src, " *This file was generated by snacc *\n"); fprintf (src, " *UBC snacc written by Mike Sample\n *\n"); fprintf (src, " *NOTE: This is a machine generated file - editing not recommended\n"); fprintf (src, " */\n\n\n"); @@ -231,7 +231,7 @@ PrintCHdrComment PARAMS ((f, m), fprintf (f, "/*\n"); fprintf (f, " *%s\n *\n", m->cHdrFileName); fprintf (f, " *\"%s\" ASN.1 module C type definitions and prototypes\n *\n", m->modId->name); -fprintf (f, " *This .h file was generated by snacc on %s *\n", ctime (&t)); +fprintf (f, " *This .h file was generated by snacc *\n"); fprintf (f, " *UBC snacc written compiler by Mike Sample\n *\n"); fprintf (f, " *NOTE: This is a machine generated file--editing not recommended\n"); fprintf (f, " */\n\n\n"); diff --git a/compiler/back-ends/idl-gen/gen-code.c b/compiler/back-ends/idl-gen/gen-code.c index 9e4c9c2..978e5a6 100644 --- a/compiler/back-ends/idl-gen/gen-code.c +++ b/compiler/back-ends/idl-gen/gen-code.c @@ -70,7 +70,7 @@ PrintComment PARAMS ((idl, m), fprintf (idl, "//\n"); fprintf (idl, "// %s -- IDL for ASN.1 module %s\n", m->idlFileName, m->modId->name); fprintf (idl, "//\n"); -fprintf (idl, "// This file was generated by snacc on %s", ctime (&t)); +fprintf (idl, "// This file was generated by snacc"); fprintf (idl, "// UBC snacc written by Mike Sample\n"); fprintf (idl, "// IDL generator written by Robert Joop\n"); fprintf (idl, "\n"); diff --git a/compiler/core/snacc.c b/compiler/core/snacc.c index 96b2683..9b86b9f 100644 --- a/compiler/core/snacc.c +++ b/compiler/core/snacc.c @@ -1125,7 +1125,7 @@ GenCxxCode PARAMS ((allMods, longJmpVal, genTypes, genValues, genEncoders, genDe fprintf (meta.srcfp, "//\n"); fprintf (meta.srcfp, "// modules
Bug#1010379: marked as done (snacc: reproducible builds: timestamp embedded in header files)
Your message dated Sat, 30 Apr 2022 01:48:44 + with message-id and subject line Bug#1010379: fixed in snacc 1.3.1-9 has caused the Debian Bug report #1010379, regarding snacc: reproducible builds: timestamp embedded in header files to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1010379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010379 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: snacc Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Various header files embed the timestamp when it was generated in comments: https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope-results/snacc.html /usr/include/snacc/c/asn-useful.h ·*This·.h·file·was·generated·by·snacc·on·Fri·May·19·17:42:30·2023 vs. ·*This·.h·file·was·generated·by·snacc·on·Sun·Apr·17·13:25:08·2022 The attached patch fixes this by removing the timestamps from the code that generates the header files. With this patch applied, snacc should become reproducible on tests.reproducible-builds.org! live well, vagrant From d44bf7e4857b23f94319aabf0bd3124a9b11ce58 Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Fri, 29 Apr 2022 23:05:46 + Subject: [PATCH] reproducible builds: Remove timestamps from generated comments. https://reproducible-builds.org/docs/timestamps/ --- compiler/back-ends/c++-gen/gen-code.c | 4 ++-- compiler/back-ends/c-gen/gen-code.c | 4 ++-- compiler/back-ends/idl-gen/gen-code.c | 2 +- compiler/core/snacc.c | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/compiler/back-ends/c++-gen/gen-code.c b/compiler/back-ends/c++-gen/gen-code.c index d3632dd..8d15682 100644 --- a/compiler/back-ends/c++-gen/gen-code.c +++ b/compiler/back-ends/c++-gen/gen-code.c @@ -170,7 +170,7 @@ PrintHdrComment PARAMS ((hdr, m), fprintf (hdr, "//\n"); fprintf (hdr, "// %s - class definitions for ASN.1 module %s\n", m->cxxHdrFileName, m->modId->name); fprintf (hdr, "//\n"); -fprintf (hdr, "// This file was generated by snacc on %s", ctime (&now)); +fprintf (hdr, "// This file was generated by snacc"); fprintf (hdr, "// UBC snacc by Mike Sample\n"); fprintf (hdr, "// A couple of enhancements made by IBM European Networking Center\n"); /* 20.8.93 Thomas Meyer */ fprintf (hdr, "\n"); @@ -188,7 +188,7 @@ PrintSrcComment PARAMS ((src, m), fprintf (src, "//\n"); fprintf (src, "// %s - class member functions for ASN.1 module %s\n", m->cxxSrcFileName, m->modId->name); fprintf (src, "//\n"); -fprintf (src, "// This file was generated by snacc on %s", ctime (&now)); +fprintf (src, "// This file was generated by snacc"); fprintf (src, "// UBC snacc written by Mike Sample\n"); fprintf (src, "// A couple of enhancements made by IBM European Networking Center\n"); /* 20.8.93 Thomas Meyer */ fprintf (src, "\n"); diff --git a/compiler/back-ends/c-gen/gen-code.c b/compiler/back-ends/c-gen/gen-code.c index e5c94d9..a198676 100644 --- a/compiler/back-ends/c-gen/gen-code.c +++ b/compiler/back-ends/c-gen/gen-code.c @@ -182,7 +182,7 @@ PrintCSrcComment PARAMS ((src, m), fprintf (src, "/*\n"); fprintf (src, " *%s\n *\n", m->cSrcFileName); fprintf (src, " *\"%s\" ASN.1 module encode/decode/print/free C src.\n *\n", m->modId->name); -fprintf (src, " *This file was generated by snacc on %s *\n", ctime (&t)); +fprintf (src, " *This file was generated by snacc *\n"); fprintf (src, " *UBC snacc written by Mike Sample\n *\n"); fprintf (src, " *NOTE: This is a machine generated file - editing not recommended\n"); fprintf (src, " */\n\n\n"); @@ -231,7 +231,7 @@ PrintCHdrComment PARAMS ((f, m), fprintf (f, "/*\n"); fprintf (f, " *%s\n *\n", m->cHdrFileName); fprintf (f, " *\"%s\" ASN.1 module C type definitions and prototypes\n *\n", m->modId->name); -fprintf (f, " *This .h file was generated by snacc on %s *\n", ctime (&t)); +fprintf (f, " *This .h file was generated by snacc *\n"); fprintf (f, " *UBC snacc written compiler by Mike Sample\n *\n"); fprintf (f, " *NOTE: This is a machine generated file--editing not recommended\n"); fprintf (f, " */\n\n\n"); diff --git a/compiler/back-ends/idl-gen/gen-code.c b/compiler/back-ends/idl-gen/gen-code.c index 9e4c9c2..978e5a6 100644 --- a/compiler/back-ends/idl-gen/gen-code.c +++ b/compiler/back-
Processing of snacc_1.3.1-9_source.changes
snacc_1.3.1-9_source.changes uploaded successfully to localhost along with the files: snacc_1.3.1-9.dsc snacc_1.3.1-9.debian.tar.xz snacc_1.3.1-9_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
snacc_1.3.1-9_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 29 Apr 2022 18:33:59 -0700 Source: snacc Architecture: source Version: 1.3.1-9 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Vagrant Cascadian Closes: 1010379 Changes: snacc (1.3.1-9) unstable; urgency=medium . * QA upload. * debian/patches: Remove timestamps from generated headers. (Closes: #1010379) * debian/control: Update Vcs-* headers. * debian/control: Set Rules-Requires-Root to "no". * debian/changelog: Remove trailing whitespace. * Update to debhelper-compat 13. * Remove dh-autoreconf, now the default with debhelper compat 13. * debian/rules: Pass --no-parallel to dh. * debian/rules: Add dh_missing override to pass --list-missing. * debian/control: Update Standards-Version to 4.6.0. * snacc-doc: Update location of snacc-a5.ps * debian/control: Drop Build-Depends on autotools-dev, now the default debhelper compat 13. Checksums-Sha1: fd3a833a8d7c90decfca9283531009508c032280 1454 snacc_1.3.1-9.dsc 87a7166b0d70cbd39241ee80d6145a4f6fb8f509 14440 snacc_1.3.1-9.debian.tar.xz dfd99cef7b72993cf90c8dd60ef6802c125a7598 6469 snacc_1.3.1-9_amd64.buildinfo Checksums-Sha256: 4ca98b3e058a323d2ab45f1502803af46340c7eb4eed8ae83c6a046b2d1be717 1454 snacc_1.3.1-9.dsc 83f73ff023f2e5237c090a5e1b3dbff6654234fd443b326abe1715f7181a2423 14440 snacc_1.3.1-9.debian.tar.xz c11eff79b53269e3683dbb89dd25b1db42ec6fc38e39cd9a77229aef26f62ae8 6469 snacc_1.3.1-9_amd64.buildinfo Files: 8204e9b1569f82a9b3af68025295b589 1454 devel optional snacc_1.3.1-9.dsc cd7744838cd06a8e91d00fe85e6a4641 14440 devel optional snacc_1.3.1-9.debian.tar.xz 042a898aa432a90b16423716e349540a 6469 devel optional snacc_1.3.1-9_amd64.buildinfo -BEGIN PGP SIGNATURE- iIkEARYKADEWIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCYmyTVRMcdmFncmFudEBk ZWJpYW4ub3JnAAoJENxRj8h/lxaqnTYA/it/w2a/s719mKJ4lBAeoLWkbzj7HwKT /Zy05nm2aCOyAQDjMkI+7acq470e0QqmUqoN6yb1LfDk+c2G14tAfxg4Bw== =LibX -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#1008569: unar: diff for NMU version 1.10.1-3
Hi all, 在 2022-04-29星期五的 08:20 +0200，Paul Gevers写道： > Dear Boyuan, > > On 25-04-2022 20:44, Sudip Mukherjee wrote: > > > +unar (1.10.1-3) unstable; urgency=medium > > > + > > > + * QA upload. > > > + * Orphan the package (take over package maintenance) via > > > + ITS process. (Closes: #1008569) > > > > I maybe wrong but I was wondering if this is correct. > > > > Section 5.12 in Debian's Developers Reference [1] clearly says: > > Note that the process is only intended for actively taking over > > maintainership. Do not start a package salvaging process when you > > do not intend to maintain the package for a prolonged time. If you > > only want to fix certain things, but not take over the package, you > > must use the NMU process, even if the package would be eligible for > > salvaging. > > > > And, in this case you salavaged the package with the intention to > > orphan it not to maintain it. > > Today I received the 'Work-needing packages report' [1] that notified me > that there are three reverse dependencies of unar. Two are maintained by > me and the a11y team (I didn't realize that when I say the message by > Sudip). The third is maintained by you. It appears to me that you > "salvaged" unar because of that (I could be wrong, please let me know). > I think it would have helped (at least I would have read the message > from Sudip with more sympathy for you) if you would have made that clear > in your original ITS message and/or in a follow-up message to Sudip. > > Do you think it would be a good idea if you co-maintain this package > with the a11y team? That way, you don't need to take the sole ownership > (which you apparently didn't want) but can still easily keep an eye on > it (and continue the work to package 1.10.7). > > Paul > > [1] > https://lists.debian.org/msgid-search/e1nkesg-00066x...@quantz.debian.org Thank you all for the information and offering. Unar is an important package not only because of high popcon and reverse dependencies (including packages in a11y team, KDE's ark, and package bookworm I maintain), it is also the sole sane solution in the Linux world to correctly handle zip files with national encodings AFAIK (especially since unzip-iconv patch never made itself into Debian). That is the basic motivation for me to refresh this package. That being said, having this package team-maintained would be a good idea, better than "maintaining package via QA uploads". I would be happy to co- maintain it under the a11y team, and will reflect team maintenance in the next upload when current icu71 transition is properly dealt. For now my perference is to keep the git packaging repo under salsa.debian.org/debian/ namespace, but please let me know if you have other suggestions. Refreshing this package is expected to be bumpy due to Objective-C source code, non-standard build system, and porting issues ([2][3]). It's likely that I will be seriously using porterbox for the very first time. Any technical suggestions, or even extra hands, would be helpful. Thanks, Boyuan Yang [2] https://ci.debian.net/data/autopkgtest/testing/armhf/u/unar/21226476/log.gz [3] https://bugs.debian.org/746198 signature.asc Description: This is a digitally signed message part
Bug#994976: xtermcontrol: please make the build reproducible
On 2021-09-24, Chris Lamb wrote: > Whilst working on the Reproducible Builds effort [0] we noticed that > xtermcontrol could not be built reproducibly. ... > --- a/debian/rules2021-09-24 09:20:53.800313098 +0100 > --- b/debian/rules2021-09-24 09:35:32.356026521 +0100 > @@ -5,9 +5,15 @@ > > export DEB_BUILD_MAINT_OPTIONS=hardening=+all > > +PACKAGE_YEAR = $(shell date --utc --date=@$(SOURCE_DATE_EPOCH) '+%Y') > +PACKAGE_DATE = $(shell date --utc --date=@$(SOURCE_DATE_EPOCH) +'%B %d, %Y') I think this should use %Y-%m-%d instead, as %B is a locale-dependent month name. > + > %: > dh $@ > > +override_dh_auto_build: > + dh_auto_build -- PACKAGE_YEAR="$(PACKAGE_YEAR)" > PACKAGE_DATE="$(PACKAGE_DATE)" > + > override_dh_auto_test: > ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS))) > xvfb-run xterm -e '( dh_auto_test ; echo $$? ) | tee > debian/xterm_dh_auto_test.log' This package appears to be part of the QA team, so could be uploaded by anyone... I'd consider uploading the fix, unless you'd like to do the honors? live well, vagrant signature.asc Description: PGP signature
