Sign me up Login

Details about package byacc

Name: byacc (PTS)
Uploader: Thomas Dickey <dickey@his.com> (Debian QA page)
Description: byacc - public domain Berkeley LALR Yacc parser generator

Package uploads

Upload #5

Information

Version: 1:2.0.20220114-1
Uploaded: 2022-01-26 01:30
Source package: byacc_2.0.20220114-1.dsc
Distribution: unstable
Section: devel
Priority: optional
Homepage: https://invisible-island.net/byacc/
Vcs-Browser: https://salsa.debian.org/debian/byacc
Vcs-Git: https://salsa.debian.org/debian/byacc.git
Closes bugs: #916894 #955175 #965445 #1002990

Changelog

 byacc (1:2.0.20220114-1) unstable; urgency=medium
 .
   * Use combination of dversionmangle/oversionmangle in watch file to work with
     upstream versioning of tarballs.
   * byacc is now built with back-tracking support; as a side-effect
     debug-output is sent to stderr instead of stdout.
   * Correct versioning using epoch; the previous package version used only the
     date/time, while byacc's major/minor version were omitted from the package
     version.  The program's "-V" option gave that information.
   * Adopt package and set myself as maintainer (Closes: #1002990).
   * New upstream release, upgrading from 2014 to 2022.
   * Update build system (Closes: #965445)
   * Fix usage of two-fonts macros (Closes: #955175)
   * Corrected watch-path to the source files (Closes: #916894)
   * Remove obsolete "README.Debian"
   * Standards-Version: 4.6.0.1.

QA information

Comments

  1. amended changelog entry per suggestion by Andreas Metzler
    Ready Thomas Dickey at Jan. 26, 2022, 1:38 a.m.

Upload #4

Information

Version: 1:2.0.20220114-1
Uploaded: 2022-01-23 17:15
Source package: byacc_2.0.20220114-1.dsc
Distribution: unstable
Section: devel
Priority: optional
Homepage: https://invisible-island.net/byacc/
Vcs-Browser: https://salsa.debian.org/debian/byacc
Vcs-Git: https://salsa.debian.org/debian/byacc.git
Closes bugs: #916894 #955175 #965445 #1002990

Changelog

 byacc (1:2.0.20220114-1) unstable; urgency=medium
 .
   * Use combination of dversionmangle/oversionmangle in watch file to work with
     upstream versioning of tarballs.
   * Combine byacc/byacc2 packages, to produce a single executable with the
     caveat that debug-output from the latter goes to stderr while the former
     goes to stdout.
   * Correct versioning using epoch; the previous package version used only the
     date/time, while byacc's major/minor version were omitted from the package
     version.  The program's "-V" option gave that information.
   * Adopt package and set myself as maintainer (Closes: #1002990).
   * Add new binary "byacc2" to provide the back-tracking variant of byacc.
   * New upstream release, upgrading from 2014 to 2022.
   * Update build system (Closes: #965445)
   * Fix usage of two-fonts macros (Closes: #955175)
   * Corrected watch-path to the source files (Closes: #916894)
   * Remove obsolete "README.Debian"
   * Standards-Version: 4.3.0

QA information

Comments

  1. combined the changelogs for mentors-uploads
    Ready Thomas Dickey at Jan. 23, 2022, 6:24 p.m.

Upload #3

Information

Version: 1:2.0.20220114-1
Uploaded: 2022-01-19 23:45
Source package: byacc_2.0.20220114-1.dsc
Distribution: unstable
Section: devel
Priority: optional
Homepage: https://invisible-island.net/byacc/
Vcs-Browser: https://salsa.debian.org/debian/byacc
Vcs-Git: https://salsa.debian.org/debian/byacc.git

Changelog

 byacc (1:2.0.20220114-1) unstable; urgency=medium
 .
   * combine byacc/byacc2 packages, to produce a single executable with the
     caveat that debug-output from the latter goes to stderr while the former
     goes to stdout.
   * work around git-buildpackage's absence of configurability regarding uscan.
   * fix lintian issues reported in update.

QA information

Comments

  1. Brendan O'Dea suggested using oversionmangle,
    which is less pushback on upstream
    than a custom tarball for Debian packages.
    Ready Thomas Dickey at Jan. 19, 2022, 11:57 p.m.
  2. I investigated the very-long-line warning, but found no override worked.
    There are no Debian changes, because the rules file suffices for customization.
    Ready Thomas Dickey at Jan. 19, 2022, 11:59 p.m.

Upload #2

Information

Version: 1:2.0.20220114-1
Uploaded: 2022-01-15 01:45
Source package: byacc_2.0.20220114-1.dsc
Distribution: unstable
Section: devel
Priority: optional
Homepage: https://invisible-island.net/byacc/
Vcs-Browser: https://salsa.debian.org/debian/byacc
Vcs-Git: https://salsa.debian.org/debian/byacc.git

Changelog

 byacc (1:2.0.20220114-1) unstable; urgency=medium
 .
   * work around git-buildpackage's absence of configurability regarding uscan.
   * fix lintian issues reported in update.

QA information

Comments

  1. D/CI works.
    Ready Thomas Dickey at Jan. 15, 2022, 1:49 a.m.

Upload #1

Information

Version: 1:2.0+20220101-1
Uploaded: 2022-01-05 10:30
Source package: byacc_2.0+20220101-1.dsc
Distribution: unstable
Section: devel
Priority: optional
Homepage: https://invisible-island.net/byacc/
Vcs-Browser: https://salsa.debian.org/dickey/byacc
Vcs-Git: https://salsa.debian.org/dickey/byacc.git
Closes bugs: #916894 #955175 #965445 #1002990

Changelog

 byacc (1:2.0+20220101-1) unstable; urgency=medium
 .
   * Correct versioning using epoch; the previous package version used only the
     date/time, while byacc's major/minor version were omitted from the package
     version.  The program's "-V" option gave that information.
   * Adopt package and set myself as maintainer (Closes: #1002990).
   * Add new binary "byacc2" to provide the back-tracking variant of byacc.
   * New upstream release, upgrading from 2014 to 2022.
   * Update build system (Closes: #965445)
   * Fix usage of two-fonts macros (Closes: #955175)
   * Corrected watch-path to the source files (Closes: #916894)
   * Remove obsolete "README.Debian"
   * Standards-Version: 4.3.0

QA information

Comments

  1. Please use https://salsa.debian.org/debian/byacc to maintain the package and fix the d/watch (see CI result).
    Needs work Bastian Germann at Jan. 7, 2022, 12:02 a.m.
  2. The d/watch warning tells me that there are no Debian changes,
    which I understand to mean that there are no patches.
    That is as expected, because I do all of the fixes in the rules file.
    (Or am I misunderstanding this?).
    
    In my latest upload, I addressed the bindnow warning.
    The very-long lines are expected (I could address the changes-file upstream, but that's a different issue).
    
    I'll follow up on the updated URL before doing another upload.
    Ready Thomas Dickey at Jan. 7, 2022, 1:46 a.m.
  3. Why have you introduced the "1:2.0+" in the version anyway? I do not find any 2.0 at obvious places in the upstream tarball. I would just keep going with the unprefixed version number. Then you do not need all those rewrite rules in d/watch which still do not work.
    Needs work Bastian Germann at Jan. 7, 2022, 8:09 p.m.
  4. Run "byacc -V", and you'll see the version.  "patchdate" is always just part of the complete version.  Since it's been the naming scheme for byacc tarballs for quite a while, changing it would be disruptive.
    
    I'm partway through solving the watch file, but am working on several things.
    Needs work Thomas Dickey at Jan. 7, 2022, 8:23 p.m.
  5. Hm... The naming scheme of the upstream files does not contain "2.0". So please drop the version prefix from d/changelog.
    Needs work Bastian Germann at Jan. 7, 2022, 8:28 p.m.
  6. The upstream version 2.0 is documented here:
    
    https://invisible-island.net/byacc/CHANGES.html#index-t20200910
    
    and byacc -V will print
    
    2.0 20220101
    
    The relevant Debian policy is here:
    
    https://www.debian.org/doc/debian-policy/ch-controlfields.html#version
    
    (and yes, I'm aware that epochs should be used sparingly - but the previous package version causes mis-ordering unless an epoch is used).
    
    Fedora's packager got it right:
    
    https://fedora.pkgs.org/34/fedora-x86_64/byacc-2.0.20210109-2.fc34.x86_64.rpm.html
    
    (uscan's documentation needs improvement)
    Needs work Thomas Dickey at Jan. 7, 2022, 9:13 p.m.
  7. "the previous package version causes mis-ordering unless an epoch is used" - why? Isn't the date in YYYYMMDD format? That is not mis-ordering.
    
    If you want me to sponsor this, please drop the prefix. I do not see a justification for it. If it was a new package being itroduced it would be a different thing.
    Needs work Bastian Germann at Jan. 7, 2022, 9:21 p.m.
  8. And also, the 1.9... versions are littler than the dates.
    Bastian Germann at Jan. 7, 2022, 9:22 p.m.
  9. I'm attempting to package this according to Debian policy.  Upstream is "2.0", and that won't change for a while.  Given that, the policy is pretty clear how to proceed.
    
    The version "2.0+20220101" happens to be less than "20140715", according to apt.
    
    I'd try "2.0.20220101", but recall another pitfall in that area (from my test-packages with ncurses), so I didn't explore it with this package.
    
    (uscan's documentation for uversionmangle and dversionmangle is a little obscure, and I didn't notice filenamemangle until my attention was directed to the CI system -- another documentation opportunity).
    Needs work Thomas Dickey at Jan. 7, 2022, 9:39 p.m.
  10. In the console output, "uscan warn: The directory name package doesn't match the requirement of" seems to show that uscan is being confused by the "package/debian" directory.  The watch file in that directory uses a different regex, which would match on the target of the renaming.
    
    Using the wrong watch file would be a bug in the pipeline script or related utility.
    
    If I were able to run this in verbose mode, I could see what is going on, but don't know where to adjust the pipeline script.
    Needs work Thomas Dickey at Jan. 8, 2022, 1:33 a.m.
  11. Some progress, but more work: I understand why uscan is picking up an incorrect watch-file (that's an omission in the pipeline script which I probably can't fix directly), and can see progress with the version.
    
    However (more work), my exports to git for the "CHANGES" and "MANIFEST" file aren't identical to the original.  I'll address that in the next version of byacc (which will result in a new export, new label, etc).
    
    Since I have a bug report/patch to investigate from a user, that'll be "soon".
    Needs work Thomas Dickey at Jan. 8, 2022, 8:33 p.m.