Re: announce-gen project link and mirrors

Simon Josefsson via Gnulib discussion list writes: >> Here are the compressed sources: >> https://ftp.gnu.org/gnu/diffutils/diffutils-3.11.tar.gz (3.3MB) >> https://ftp.gnu.org/gnu/diffutils/diffutils-3.11.tar.xz (1.9MB) >> >> Here are the GPG detached signatures: >> https://ftp.gnu.org

Re: announce-gen project link and mirrors

Simon Josefsson wrote: > Announce-gen generate this snippet: > > > Here is the GNU libtasn1 home page: > > https://gnu.org/s/libtasn1/ > > Why? Shouldn't we use the canonical URL in the announcement? I think > the above just looks ugly when the real UR

Re: announce-gen project link and mirrors

Jim Meyering writes: > On Thu, Feb 6, 2025 at 3:06 PM Simon Josefsson via Gnulib discussion > list wrote: >> Announce-gen generate this snippet: >> >> > Here is the GNU libtasn1 home page: >> > https://gnu.org/s/libtasn1/ >> >> Why? Should

Re: announce-gen project link and mirrors

On Thu, Feb 6, 2025 at 9:59 PM Jim Meyering wrote: > > On Thu, Feb 6, 2025 at 3:06 PM Simon Josefsson via Gnulib discussion > list wrote: > > Announce-gen generate this snippet: > > > > > Here is the GNU libtasn1 home page: > > > https://gnu.org/s/libta

Re: announce-gen project link and mirrors

On Thu, Feb 6, 2025 at 3:06 PM Simon Josefsson via Gnulib discussion list wrote: > Announce-gen generate this snippet: > > > Here is the GNU libtasn1 home page: > > https://gnu.org/s/libtasn1/ > > Why? Shouldn't we use the canonical URL in the announcement? I

announce-gen project link and mirrors

Announce-gen generate this snippet: > Here is the GNU libtasn1 home page: > https://gnu.org/s/libtasn1/ Why? Shouldn't we use the canonical URL in the announcement? I think the above just looks ugly when the real URL is: https://www.gnu.org/software/libtasn1/ I can see the

Re: [PATCH] announce-gen: Allow 'make release' to work any day.

gt; From: Paul Eggert Date: Fri, 31 Jan 2025 16:24:26 -0800 Subject: [PATCH] announce-gen: add comments * top/maint.mk: Add comments re recent change. --- ChangeLog| 5 + top/maint.mk | 3 +++ 2 files changed, 8 insertions(+) diff --git a/ChangeLog b/ChangeLog index 89674821a0..cc0fe2

[PATCH] announce-gen: Allow 'make release' to work any day.

n From c89cd2fbd3b9f3d7c5a146247256599714c91ec7 Mon Sep 17 00:00:00 2001 From: Simon Josefsson Date: Sat, 1 Feb 2025 00:58:45 +0100 Subject: [PATCH] announce-gen: Allow 'make release' to work any day. * top/maint.mk (today): Use regexp rather than current time. --- ChangeLog| 5 ++

[PATCH] announce-gen: Deal with 'guix --version'.

All, I've pushed this patch so that announce-gen handles 'guix --version' output. It bothered me for some time that randomly this worked and randomly it didn't, the reason was that it happened to work when the guix --version (which is git commit SHA1 identifier) began with 0-

[PATCH] announce-gen: Support VPATH builds better.

-C was simple. I pushed this patch. /Simon From cb48b6cb3aef16d44495f9fbc287c769adb22086 Mon Sep 17 00:00:00 2001 From: Simon Josefsson Date: Sat, 28 Dec 2024 19:42:43 +0100 Subject: [PATCH] announce-gen: Support VPATH builds better. * build-aux/announce-gen: Pass -C$srcdir to git. --

Re: announce-gen: Show an SHA256 sum that can be verified more easily

ot;the fgrep program >is redundant. we would prefer everyone to use 'grep -F' instead"; >such a move has shown to not sit well with users. Another analogy could be the migration from 'gzip -cd FOO | tar xf -' to 'tar xfz FOO' to 'tar xfa FOO&

Re: [PATCH] announce-gen: Mention git commit in release announcement.

e 1.16.5 Makeinfo 6.8 Libtoolize 2.4.6 NEWS * Noteworthy changes in release 4.0.2 (2024-12-10) [alpha] ** EdDSA curve manipulation should use #f for the y parameter of the public-key. /Simon From 45db9fb46adaf2f88529a52f3c94ac4fdc82e33e Mon Sep 17 00:00:00 2001 From: Simon Josefsson D

Re: announce-gen: Show an SHA256 sum that can be verified more easily

On 02/12/2024 21:11, Jeffrey Walton wrote: It turns out that Base64 is malleable. All tools do not produce the same results. Also see . Whether Base64 malleability leads to a vulnerability is another question. This might be an issue for non canonicity, particu

Re: announce-gen: Show an SHA256 sum that can be verified more easily

On Sun, Dec 1, 2024 at 9:04 AM Simon Josefsson via Gnulib discussion list wrote: > > Bruno Haible via Gnulib discussion list writes: > > > The 'announce-gen' script shows SHA256 sums in a way that are hard to verify > > and understand for the users: > > -

Re: announce-gen: Show an SHA256 sum that can be verified more easily

Collin Funk wrote: > I've attached a patch, but I haven't pushed yet in case anyone > disagrees. Thanks for proposing that patch, Collin. Even though the patch does not find my agreement (and also lacks a modification in the --help output), it helped me save time, because Perl is unfamiliar to me.

Re: announce-gen: Show an SHA256 sum that can be verified more easily

;t it be SHA512? But an SHA512 sum needs 2 80-columns lines anyway (128 characters in one case, 88 characters in the other case). So, you effectively win nothing from the base64 output. Bruno >From 146d5f8c83255ceab590facb5520c03b7ba07f24 Mon Sep 17 00:00:00 2001 From: Bruno Haible Date:

Re: announce-gen: Show an SHA256 sum that can be verified more easily

n Sep 17 00:00:00 2001 From: Collin Funk Date: Sun, 1 Dec 2024 21:33:32 -0800 Subject: [PATCH] announce-gen: Add the --hex option. * build-aux/announce-gen (print_checksums_hex): New function. (print_checksums_base64): New function. (print_checksums): Call the new functions. --- ChangeLog

Re: announce-gen: Show an SHA256 sum that can be verified more easily

On Sun, Dec 1, 2024 at 6:04 AM Simon Josefsson via Gnulib discussion list wrote: > Bruno Haible via Gnulib discussion list writes: > > > The 'announce-gen' script shows SHA256 sums in a way that are hard to verify > > and understand for the users: > > - Ve

Re: announce-gen: Show an SHA256 sum that can be verified more easily

Bruno Haible via Gnulib discussion list writes: > The 'announce-gen' script shows SHA256 sums in a way that are hard to verify > and understand for the users: > - Verifying requires a special command that is not easy to remember. > - Verifying requires special tools th

announce-gen: Show an SHA256 sum that can be verified more easily

The 'announce-gen' script shows SHA256 sums in a way that are hard to verify and understand for the users: - Verifying requires a special command that is not easy to remember. - Verifying requires special tools that do not exist on all systems. - Understand why one checksum uses

announce-gen: Fix bug when accessing symlinks

The announce-gen script produced this output for me: Here are the compressed sources: https://ftp.gnu.org/gnu/gettext/gettext-0.23.tar.gz (0 gettext-0.23.tar.gz) https://ftp.gnu.org/gnu/gettext/gettext-0.23.tar.lz (0 gettext-0.23.tar.lz) https://ftp.gnu.org/gnu/gettext

Re: announce-gen: Fix copyright year in --version output.

Bruno Haible writes: > How about deriving the --version output from the copyright notice, for > those programs that consist of a single file and that are not written in C? [...] > + # Extract the last year from this file's copyright notice. > + sed_extract_last_year='s/^.*\([0-9]\{4\}\)[^0-9]*$

Re: announce-gen: Fix copyright year in --version output.

Collin Funk wrote: > The announce-gen and useless-if-before-free scripts have had changes > since their copyright date was updated: How about deriving the --version output from the copyright notice, for those programs that consist of a single file and that are not written in C? Like this:

Re: announce-gen: Fix copyright year in --version output.

Hi Simon, > > The GNU Maintainers Guide and the GNU Coding Standards have different > > sections > > - about the copyright notice in source files > > https://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html > > - about the --version output of programs > > https://www.gnu.org

Re: announce-gen: Fix copyright year in --version output.

Bruno Haible writes: > Simon Josefsson wrote: >> > Maybe, I am misreading but I think using $VERSION makes more sense >> > according to the GNU Coding Standards [1]: >> > >> > This copyright notice only needs to mention the most recent year in >> > which changes were made—there’s no need

Re: announce-gen: Fix copyright year in --version output.

Simon Josefsson wrote: > > Maybe, I am misreading but I think using $VERSION makes more sense > > according to the GNU Coding Standards [1]: > > > > This copyright notice only needs to mention the most recent year in > > which changes were made—there’s no need to list the years for previous

Re: announce-gen: Fix copyright year in --version output.

wonder if something changed here. Can someone remind me why we do the 'make update-copyright' dance? I recall 'make syntax-check' failing when this is not done, so maybe those self tests shouldn't be failing. > The useless-if-before-free script I updated recently to acc

Re: announce-gen: Fix copyright year in --version output.

y needs to mention the most recent year in which changes were made—there’s no need to list the years for previous versions’ changes. The useless-if-before-free script I updated recently to account for nullptr in C23. And I know that announce-gen has been updated since 2022. Does updating the

Re: announce-gen: Fix copyright year in --version output.

Collin Funk writes: > Hi Bruno, > > Bruno Haible writes: > >> Can this be rewritten in a simpler way, that does not use idioms >> from perl's bag of tricks? Something like >> >> my $copyright_year = ; >> >> like one would do it in every other programming language? > > Not sure. I'm not the mos

Re: announce-gen: Fix copyright year in --version output.

Hi Bruno, Bruno Haible writes: > Can this be rewritten in a simpler way, that does not use idioms > from perl's bag of tricks? Something like > > my $copyright_year = ; > > like one would do it in every other programming language? Not sure. I'm not the most knowledgeable perl programmer. Mayb

Re: announce-gen: Fix copyright year in --version output.

Hi Collin, > I've pushed the two attached patches to derive the copyright year from > the time-stamp string. > +(my $copyright_year = $VERSION) =~ s/^(\d*)-.*$/$1/; Can this be rewritten in a simpler way, that does not use idioms from perl's bag of tricks? Something like my $copyright_year =

announce-gen: Fix copyright year in --version output.

The announce-gen and useless-if-before-free scripts have had changes since their copyright date was updated: $ ./build-aux/announce-gen --version announce-gen version 2024-07-04 10:55 Copyright (C) 2022 Free Software Foundation, Inc. I've pushed the two attached patches to deriv

Re: [PATCH] announce-gen: Mention git commit in release announcement.

On 2024-05-12 12:50, Bruno Haible wrote: Your real goal, which is — AFAIU — to allow distros to discard part or all of the tarball and to redo the packaging work done by the release manager in a different way, would be better served with a 1) machine-readable file, 2) somewhere in or in th

Re: [PATCH] announce-gen: Mention git commit in release announcement.

Hi Simon, > including the commit hash provide some additional information that may > be useful further down the line That is a bit weak as a rationale. There are many additional informations that "may be useful" to include. Isn't this move part of a bigger plan of yours, which is to decompose rel

Re: [PATCH] announce-gen: Mention git commit in release announcement.

On 2024-05-12 09:27, Jim Meyering wrote: I like it. Wording and placement are spot on. Looks good to me too. I at first thought to suggest adding announce-gen's own version number to the announcement (to help people who want to check the announcement itself), but there's no need as it's deri

Re: [PATCH] announce-gen: Mention git commit in release announcement.

I like it. Wording and placement are spot on. Thanks. On Sun, May 12, 2024, 08:42 Simon Josefsson via Gnulib discussion list < bug-gnulib@gnu.org> wrote: > All, > > Our release announcements does not mention the git commit hash that was > used to prepare the release. While SHA1 is broken, I sti

[PATCH] announce-gen: Mention git commit in release announcement.

0200 Subject: [PATCH] announce-gen: Mention git commit in release announcement. * build-aux/announce-gen (this_commit_hash): New variable. (main): Print commit hash. --- ChangeLog | 6 ++ build-aux/announce-gen | 6 -- 2 files changed, 10 insertions(+), 2 deletions(-) diff

[PATCH] maintainer-makefile: Silence announce-gen error with GNULIB_REVISION.

er-makefile: Silence announce-gen error with GNULIB_REVISION. * top/maint.mk (gnulib-version): Silence git describe on failure. --- ChangeLog| 5 + top/maint.mk | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/ChangeLog b/ChangeLog index 2e2311e7b2..b6aa21d7f7 100644 -

[PATCH] announce-gen: Improve links.

Hi, I noticed http:// links were used here... patch below is pushed. Happy new year, /Simon * build-aux/announce-gen: Use https:// URLs. --- ChangeLog | 5 + build-aux/announce-gen | 6 +++--- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/ChangeLog b

Re: [PATCH] announce-gen: Allow using local git user.name.

On Mon, Jul 17, 2023 at 1:12 PM Simon Josefsson via Gnulib discussion list wrote: > Hi. I think announce-gen should use the username provided by the > per-repo .git/config rather than the global ~/.gitconfig. > > I hit this corner on build farms where I don't want to modify f

[PATCH] announce-gen: Allow using local git user.name.

Hi. I think announce-gen should use the username provided by the per-repo .git/config rather than the global ~/.gitconfig. I hit this corner on build farms where I don't want to modify files outside of the repository. /Simon From 6928b3b86169bf5d265f745ff5f93eb21181a59e Mon Sep 17 00:00:00

Re: FYI: announce-gen: add more info to the auto-generated announce template

On Sat, Feb 25, 2023 at 11:56 PM Bruno Haible wrote: > Jim Meyering wrote: > > from coreutils-9.2 or openBSD's cksum since 2007. > > It's the first time I see OpenBSD spelled this way. Why not use an > uppercase 'O', like they do themselves [1] ? Thanks. Corrected.

Re: FYI: announce-gen: add more info to the auto-generated announce template

Jim Meyering wrote: > from coreutils-9.2 or openBSD's cksum since 2007. It's the first time I see OpenBSD spelled this way. Why not use an uppercase 'O', like they do themselves [1] ? Bruno [1] http://www.openbsd.org/

FYI: announce-gen: add more info to the auto-generated announce template

nt of this for years. announce-gen: add more info to the auto-generated announce template * build-aux/announce-gen (readable_interval, readable_interval0): New functions. (digest_file_base64_wrap): New function to add padding to the base64-encoded SHA256 checksums. (print

Re: [PATCH] announce-gen: Improve GnuPG verification instructions.

/www.gnu.org/software/gettext/manual/html_node/Locale-Environment-Variables.html Thanks, especially for the pointer, and I'll try to keep it around since I tend to forget about this... /Simon > > 2022-07-10 Bruno Haible > > announce-gen: Fix internationalization in verificatio

Re: [PATCH] announce-gen: Improve GnuPG verification instructions.

s.html 2022-07-10 Bruno Haible announce-gen: Fix internationalization in verification instructions. * build-aux/announce-gen: Set LC_ALL, not LANG, to "C", to force English output from gpg. diff --git a/build-aux/announce-gen b/build-aux/announce-gen index 320cf4

Re: announce-gen usage feedback

On Sat, Jul 9, 2022 at 6:29 AM Simon Josefsson via Gnulib discussion list wrote: > > Bruno Haible writes: > > > Hi Simon, > > > > Two remarks regarding 'announce-gen': > > > > 1) I used the command > >$ $GNULIB_SRCDIR/build-aux/announc

Re: announce-gen usage feedback

Bruno Haible writes: > Hi Simon, > > Two remarks regarding 'announce-gen': > > 1) I used the command > $ $GNULIB_SRCDIR/build-aux/announce-gen --release-type stable \ >--package-name libunistring --previous-version 0.9.10 \ >--current-version

[PATCH] announce-gen: Improve GnuPG verification instructions.

ring: wget -q https://ftp.gnu.org/gnu/gnu-keyring.gpg gpg --keyring gnu-keyring.gpg --verify inetutils-2.3.tar.gz.sig From dfe8fd0f1f00b6c7a8983f6ee5aab82988e3d891 Mon Sep 17 00:00:00 2001 From: Simon Josefsson Date: Sat, 9 Jul 2022 00:32:04 +0200 Subject: [PATCH] announce-gen: Improve GnuPG verifica

Re: [PATCH] build-aux/announce-gen: Use Release keyrings on Savannah for GnuPG

_email="" or gpg_keyring_url="" in cfg.mk to avoid adding these lines to the announcement. * I moved the default URL from announce-gen to maint.mk, mostly to make the code to support the previous point easier. /Simon [1] https://gitlab.co

Re: [PATCH] build-aux/announce-gen: Use Release keyrings on Savannah for GnuPG

because you don't have the required public key, >> then run this command to import it: >> >> - gpg --keyserver keys.gnupg.net --recv-keys $gpg_key_id >> + wget -q -O- '$gpg_keyring_url' | gpg --import - > > Hi. I agree this part of announce-gen is su

Re: [PATCH] build-aux/announce-gen: Use Release keyrings on Savannah for GnuPG

mand to import it: > > - gpg --keyserver keys.gnupg.net --recv-keys $gpg_key_id > + wget -q -O- '$gpg_keyring_url' | gpg --import - Hi. I agree this part of announce-gen is sub-optimal. There were earlier discussions about solutions: https://gitlab.com/libidn/libidn2/-/issues/98#n

[PATCH] build-aux/announce-gen: Use Release keyrings on Savannah for GnuPG

Okay, I decided to take the easy way out and wrote this patch instead. The URL was too long and ugly in the --help output, so I'm glad to remove it from there. -- >8 -- * build-aux/announce-gen: The default SKS Keyserver pool for GnuPG Keys was deprecated and has been offline since th

Re: [PATCH] build-aux/announce-gen: Use Release keyrings on Savannah for GnuPG

the end. It's late at night, and I shouldn't have sent the patch when semi-asleep. I'll fix the issue and send a new version later in the day. On Tue, Mar 8, 2022, at 00:45, Darshit Shah wrote: > * build-aux/announce-gen: The default SKS Keyserver pool for GnuPG Keys was &g

[PATCH] build-aux/announce-gen: Use Release keyrings on Savannah for GnuPG

* build-aux/announce-gen: The default SKS Keyserver pool for GnuPG Keys was deprecated and has been offline since the middle of 2021. The default keyserver: keys.gnupg.net was just a mirror of the SKS Pool and is thus offline as well. Instead, use the Release Keyring on Savannah to list the GnuPG

announce-gen usage feedback

Hi Simon, Two remarks regarding 'announce-gen': 1) I used the command $ $GNULIB_SRCDIR/build-aux/announce-gen --release-type stable \ --package-name libunistring --previous-version 0.9.10 \ --current-version 1.0 --gpg-key-id F5BE8B267C6A406D \ --url-direc

Re: announce-gen and OpenPGP key servers

tis 2021-08-03 klockan 16:51 -0700 skrev Jim Meyering: > On Tue, Aug 3, 2021 at 12:25 PM Paul Eggert > wrote: > > On 8/3/21 12:20 PM, Simon Josefsson via Gnulib discussion list > > wrote: > > > +  print "\nThe SHA256 checksum is base64 encoded and not > > > hexadecimal,\n"; > > > +  print "which i

Re: announce-gen and OpenPGP key servers

On Tue, Aug 3, 2021 at 12:25 PM Paul Eggert wrote: > On 8/3/21 12:20 PM, Simon Josefsson via Gnulib discussion list wrote: > > + print "\nThe SHA256 checksum is base64 encoded and not hexadecimal,\n"; > > + print "which is the default for most checksum tools.\n\n"; > > Perhaps this? > >print

Re: announce-gen and OpenPGP key servers

On 8/3/21 12:20 PM, Simon Josefsson via Gnulib discussion list wrote: + print "\nThe SHA256 checksum is base64 encoded and not hexadecimal,\n"; + print "which is the default for most checksum tools.\n\n"; Perhaps this? print "\nThe SHA256 checksum is base64 encoded, instead of the\n"; pr

Re: announce-gen and OpenPGP key servers

Jim Meyering writes: > Thanks, Simon! I too am all for B64-formatted checksums. Good, it is a trade-off between output readability and code complexity. Aligning 'sha*sum' with OpenBSD's 'sha*' tools would be nice, and base64 support is one missing piece. > You may want to coordinate with Pádrai

Re: announce-gen and OpenPGP key servers

On Tue, Aug 3, 2021 at 8:40 AM Simon Josefsson wrote: > Jim Meyering writes: > > > Feel free to make the script generate a full fingerprint and even > > (though it feels a little like giving up) add a checksum or two. > > I think checksums still serve a purpose. > > Many announcement e-mails are

Re: announce-gen and OpenPGP key servers

't like the base64 output format. /Simon From 4adae938b8dbe01750698109bcbf5f1c9eb045b1 Mon Sep 17 00:00:00 2001 From: Simon Josefsson Date: Tue, 3 Aug 2021 17:15:16 +0200 Subject: [PATCH 1/2] announce-gen: Print SHA1/B64(SHA256) instead of MD5/SHA1. * build-aux/announce-gen (%digest_classes): Removed. (usage): Doc fix. (pr

Re: announce-gen and OpenPGP key servers

sön 2021-08-01 klockan 17:47 +0200 skrev Bernhard Voelker: > On 7/27/21 11:38 AM, Simon Josefsson via Gnulib discussion list > wrote: > > Let's discuss and see what we can do. > Isn't this what the "release GPG keys" on Savannah are for? > > Each project maintainer can set them up correctly under

Re: announce-gen and OpenPGP key servers

On 7/27/21 11:38 AM, Simon Josefsson via Gnulib discussion list wrote: > Let's discuss and see what we can do. Isn't this what the "release GPG keys" on Savannah are for? Each project maintainer can set them up correctly under "Edit public info": "https://savannah.gnu.org/project/admin/editgroup

Re: announce-gen and OpenPGP key servers

On Tue, Jul 27, 2021 at 2:38 AM Simon Josefsson via Gnulib discussion list wrote: > Hi. Our announce-gen contains: > > If that command fails because you don't have the required public key, > then run this command to import it: > gpg --keyserver keys.gnupg.net --r

Re: announce-gen and OpenPGP key servers

I agree that the current situation is bad and that your suggestions would be improvement. Particularly the part about involving the ftp-upload people. My impression is that they're quite conservative about changing things (and rightly so) but we really need a more-reliable distribution mechani

announce-gen and OpenPGP key servers

Hi. Our announce-gen contains: If that command fails because you don't have the required public key, then run this command to import it: gpg --keyserver keys.gnupg.net --recv-keys $gpg_key_id Given recent OpenPGP key server issues, that doesn't work reliably any more, and behave

Re: maint.mk: announce-gen with --no-print-checksums?

On 5/12/21 1:15 PM, Simon Josefsson via Gnulib discussion list wrote: I'm somewhat inclined to follow their path and add support for base64 encoded hashes in 'sha256sum', and then use that in announcen-gen. Sounds good to me. I suppose it would be a --base64 option? At some point we might want

maint.mk: announce-gen with --no-print-checksums?

Hi! I just made a new release of libidn2, and after posting the announcement I noticed that hash checksums was missing from my announcement. It appears maint.mk's announce-gen rules always were like this, I just didn't use them before. May I suggest the patch below as a starting po

announce-gen: add support for dist-lzip

I installed this. Cheers! commit 4f4779e15adb7f1c61e8e13ab2bdf08974e33945 Author: Akim Demaille Date: Sun May 10 18:11:04 2020 +0200 announce-gen: add support for dist-lzip * build-aux/announce-gen (@archive_suffixes): Add tar.lz. diff --git a/ChangeLog b/ChangeLog index

Re: [PATCH] announce-gen: avoid failure when Digest::SHA is installed

On 07/14/2014 10:04 AM, Daiki Ueno wrote: > Hi, > > Daiki Ueno writes: > >> The 'announce-gen' script fails when Digest::SHA (not Digest::SHA1) is >> installed: >> >> Can't locate object method "new" via package "Digest::S

Re: [PATCH] announce-gen: avoid failure when Digest::SHA is installed

Hi, Daiki Ueno writes: > The 'announce-gen' script fails when Digest::SHA (not Digest::SHA1) is > installed: > > Can't locate object method "new" via package "Digest::SHA1" (perhaps you > forgot to load "Digest::SHA1"?) at

Re: [PATCH] announce-gen: avoid perl warnings

On 07/10/2014 12:26 AM, Assaf Gordon wrote: > Hello, > > When running "./build-aux/announce-gen" without any parameters, there are > three "use of uninitialized value" warnings: > ==== > $ ./build-aux/announce-gen > announce-gen: release type not s

[PATCH] announce-gen: avoid perl warnings

Hello, When running "./build-aux/announce-gen" without any parameters, there are three "use of uninitialized value" warnings: $ ./build-aux/announce-gen announce-gen: release type not specified announce-gen: package name not specified announce-gen: previous version

[PATCH] announce-gen: avoid failure when Digest::SHA is installed

Hi, The 'announce-gen' script fails when Digest::SHA (not Digest::SHA1) is installed: Can't locate object method "new" via package "Digest::SHA1" (perhaps you forgot to load "Digest::SHA1"?) at ../gnulib/build-aux/announce-gen line 165. zs

Re: announce-gen: minor issues

Akim Demaille wrote: > Hi Jim! > > Le 23 mai 2012 à 10:34, Jim Meyering a écrit : > >>>> * build-aux/announce-gen: When parsing command line options, >>>> prefer "announce-gen: option --release-type requires an argument" >>>> to &q

Re: announce-gen: minor issues

Hi Jim! Le 23 mai 2012 à 10:34, Jim Meyering a écrit : >>> * build-aux/announce-gen: When parsing command line options, >>> prefer "announce-gen: option --release-type requires an argument" >>> to "Option release-type requires an argument". > &g

Re: announce-gen: minor issues

Akim Demaille wrote: > Le 23 mai 2012 à 10:02, Akim Demaille a écrit : > >> The two attached patches provide minor improvements to >> announce-gen. The first one was prompted by the fact >> that I had an error message whose origin was unclear. Hi Akim, Thanks for the

Re: announce-gen: minor issues

Le 23 mai 2012 à 10:02, Akim Demaille a écrit : > The two attached patches provide minor improvements to > announce-gen. The first one was prompted by the fact > that I had an error message whose origin was unclear. > > * build-aux/announce-gen: When parsing command line op

announce-gen: minor issues

The two attached patches provide minor improvements to announce-gen. The first one was prompted by the fact that I had an error message whose origin was unclear. * build-aux/announce-gen: When parsing command line options, prefer "announce-gen: option --release-type requires an argumen

Re: Problem with Digest::SHA and announce-gen

Reuben Thomas wrote: > I have Digest::SHA installed, but I still get an error about being > unable to find Digest::SHA1: > > $ perl -e 'use Digest::SHA;' > $ perl build-aux/announce-gen > Can't locate Digest/SHA1.pm in @INC (@INC contains: > /home/rrt/local/x8

Problem with Digest::SHA and announce-gen

I have Digest::SHA installed, but I still get an error about being unable to find Digest::SHA1: $ perl -e 'use Digest::SHA;' $ perl build-aux/announce-gen Can't locate Digest/SHA1.pm in @INC (@INC contains: /home/rrt/local/x86_64-linux-gnu-thread-multi/lib/perl/5.14.2 /home/rrt/l

announce-gen: require perl-5.9.3

Eric Wong wrote: > How about using the generic Digest module instead? > > Something like this (totally untested) patch: > > diff --git a/build-aux/announce-gen b/build-aux/announce-gen > index 3ca90a9..c453d44 100755 > --- a/build-aux/announce-gen > +++ b/build-aux/annou

Re: Revised announce-gen patch

Reuben Thomas wrote: > Implementing Jim's suggestions. > >>From 3e6c32b5834341ee8d1870f7b85db546b1a1f2d8 Mon Sep 17 00:00:00 2001 > From: Reuben Thomas > Date: Tue, 20 Mar 2012 20:17:22 +0000 > Subject: [PATCH] announce-gen: make it use Digest::SHA where available. &g

Re: Revised announce-gen patch

How about using the generic Digest module instead? Something like this (totally untested) patch: diff --git a/build-aux/announce-gen b/build-aux/announce-gen index 3ca90a9..c453d44 100755 --- a/build-aux/announce-gen +++ b/build-aux/announce-gen @@ -29,8 +29,7 @@ my $VERSION = '2012-01-06

Revised announce-gen patch

Implementing Jim's suggestions. >From 3e6c32b5834341ee8d1870f7b85db546b1a1f2d8 Mon Sep 17 00:00:00 2001 From: Reuben Thomas Date: Tue, 20 Mar 2012 20:17:22 + Subject: [PATCH] announce-gen: make it use Digest::SHA where available. * build-aux/announce-gen: Use either Digest::SHA1 o

Re: Fix build-aux/announce-gen for Perl 5.14

20 Mar 2012 20:17:22 + > Subject: [PATCH] announce-gen: make it work with Perl 5.14. ... > use Getopt::Long; > use Digest::MD5; > -use Digest::SHA1; > +if (!$^V or $^V lt v5.14.0) { > + require Digest::SHA1; > + Digest::SHA1->import(); > +} else { >

Fix build-aux/announce-gen for Perl 5.14

The following patch copes with a renamed module: >From 670ec3363bbbfefe927de0100a4be6f5f556a332 Mon Sep 17 00:00:00 2001 From: Reuben Thomas Date: Tue, 20 Mar 2012 20:17:22 + Subject: [PATCH] announce-gen: make it work with Perl 5.14. * build-aux/announce-gen: Use either Digest::SHA1

Re: [PATCH] announce-gen: fix `cmd' typo in diagnostic

Paul Eggert wrote: > I found this one while looking for `quoting' issues: > > * build-aux/announce-gen (print_changelog_deltas): Fix typo in > diagnostic: a missing '$' meant that the command was not output. ... ># The exit code should be 1. ># Allow in cas

[PATCH] announce-gen: fix `cmd' typo in diagnostic

I found this one while looking for `quoting' issues: * build-aux/announce-gen (print_changelog_deltas): Fix typo in diagnostic: a missing '$' meant that the command was not output. --- ChangeLog |6 ++++++ build-aux/announce-gen |4 ++-- 2 files changed, 8 i

[PATCH] announce-gen: be more concise when there's only one URL+tarball

The generated announcement for coreutils-8.14 was adjusted manually to make it more concise, now that there is only one (.xz) tarball. This change to announce-gen makes it generated what I did manually, and in addition (when you set in cfg.mk, url_dir_list = http://ftp.gnu.org/gnu/$(PACKAGE)) it

[PATCH] announce-gen: fail if the NEWS delta is empty

:00 2001 From: Jim Meyering Date: Tue, 17 May 2011 22:24:59 +0200 Subject: [PATCH] announce-gen: fail if the NEWS delta is empty If there's nothing noteworthy in NEWS, then either you forgot or you shouldn't be releasing. * build-aux/announce-gen: Die if the NEWS delta is effec

Re: announce-gen

Reuben Thomas wrote: > On 29 April 2011 21:48, Jim Meyering wrote: >> >> Please make that a separate change. > > Attached a patch made with vc-dwim :) ... > Subject: [PATCH] announce-gen: cosmetic improvement > > * build-aux/announce-gen: strip any leading ./ from t

Re: announce-gen

If no one else feels strongly enough about this to speak up, I'm willing to drop the "-", I don't feel strongly about it either way, but FWIW, the majority of Subject: lines in the info-gnu archives for this month use the real package name and a space. So, as long as we're talking "coreu

Re: announce-gen

release is in gnulib, so that > you can make the same cosmetic change in that file, too. Sure. -- http://rrt.sc3d.org 0001-announce-gen-cosmetic-improvement.patch Description: Binary data

Re: announce-gen

ble]", too. >> >> Yet you prefer to use a space in place of the "-"? > > Yes, because the subject of an email should be human language, not > computerese. I am releasing, for example, "zile 2.3.24", not > "zile-2.3.24". Really, even that is not i

Re: announce-gen

guage, not computerese. I am releasing, for example, "zile 2.3.24", not "zile-2.3.24". Really, even that is not ideal. In autoconf terms, I would rather have PACKAGE_NAME VERSION (in this case, "Zile 2.3.24"). But removing the space gets almost all of the effect intended for

Re: announce-gen

Reuben Thomas wrote: > I'm trying to prepare a small cosmetic patch to fix up a couple of > things I find myself manually fixing up: > > 1. "./NEWS". I considered replacing this with the basename of the NEWS > file, but in fact it seems to me it's better to use the literal "NEWS" > since that makes

Re: announce-gen

curr_version than >>> $my_distdir. >>> >>> I would already have sent this patch, but there's another problem: I >>> use whitespace-mode, and it stumbles because, although I've now set >>> indent-tabs-mode to t in the file announce-gen (this will

Re: announce-gen

On 04/29/2011 02:02 PM, Jim Meyering wrote: > Hmm... vc-list-files has the same problem, > though in its case I'll convert only the leading TABs, > since some are used to align backslashes, and I have > a slight preference for TABs there. Leading tab indentation is different than mid-line tab usag

  1   2   >