[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#986142: buster-pu: package h5py/2.8.0-3



Thank Adam. You're right, buster-backports is precisely what is intended.

I was following the procedure at https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable linked from https://www.debian.org/releases/proposed-updates.html . Those pages seem to have a different procedure to the one in https://backports.debian.org/Contribute/. Perhaps https://www.debian.org/releases/proposed-updates.html needs to be updated to be more clear.

I'll check and follow the buster-backports procedure at https://backports.debian.org/Contribute/

Drew

On 2021-03-30 13:41, Adam D. Barratt wrote:
Control: tags -1 + moreinfo

On Tue, 2021-03-30 at 13:18 +0200, Drew Parsons wrote:
[ Reason ]

Bug#984638 has requested a backport of h5py to buster in order to
support other packages used on it.

Usually I'd expect that wording to mean an upload to buster-backports,
rather than p-u, particularly when the difference between the two
versions is not small.

  [✓] *all* changes are documented in the d/changelog
  [✓] I reviewed all changes and I approve them
  [o] attach debdiff against the package in testing
      (debdiff against package in stable is large)


Unfortunately, for a stable update, the debdiff against stable is the
one that's relevant. The diff against a different version of the
package tells us very little about the impact on stable.

In this case, the diff against stable is:

 234 files changed, 12222 insertions(+), 7584 deletions(-)

This really feels like a candidate for a backports update, rather than
a stable update. https://backports.debian.org/Contribute/ has more
information, if you're not familiar with the process.

Regards,

Adam


Reply to: