1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.DIST

  • Bug#1109810: ITS: cputool

    From Andreas Tille@21:1/5 to All on Thu Jul 24 08:30:01 2025
    Source: cputool
    Version: 0.0.8-2
    Severity: important
    X-Debbugs-Cc: Nigel Kukard <[email protected]>, Package Salvaging Team <[email protected]>, [email protected], [email protected]

    Hi Nigel,

    I'm interested in salvaging the package cputool, in accordance with the
    Package Salvaging procedure outlined in the Developers Reference[1].
    This package meets the criteria for this process, and I would love to
    assist in preserving and maintaining it. As the Salvage process
    suggests, here is a list of the criteria that apply, in my opinion:

    - Bugs filed against the package do not have answers from the
    maintainer.
    - Upstream has released several versions, but despite there being
    a bug entry asking for it, it has not been packaged.
    - There are QA issues with the package.

    I've set up a repository within the salvage-team space[2] to assist you
    with this initial setup on Salsa. I started with an exact clone of your
    old packaging repository and ugraded it to your latest upstream since I realised you are upstream and Debian maintainer in one person. BTW, I
    also created two patches you can find in the freshly created packaging
    Git[3]. You are kindly invited to incorporate these in your next
    upstream release.

    If you decide not to accept the ITS, this repository can easily be moved
    to another location, such as debian/, or any place of your choosing. I
    hope this service helps make the transition to using a Git repository on
    Salsa smoother and more convenient for you.


    This package was highlighted in the Bug of the Day[4] initiative, which
    aims to introduce newcomers to manageable tasks and guide them through
    the workflow to solve them. The focus of this initiative is on migrating packages to Salsa, as it's a great way to help newcomers become familiar
    with a consistent Git-based workflow.

    Kind regards
    Andreas.

    [1] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
    [2] https://salsa.debian.org/salvage-team/cputool
    [3] https://salsa.debian.org/salvage-team/cputool/-/tree/master/debian/patches?ref_type=heads
    [4] https://salsa.debian.org/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks


    -- System Information:
    Debian Release: 13.0
    APT prefers testing
    APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 'experimental'), (1, 'buildd-experimental')
    Architecture: amd64 (x86_64)

    Kernel: Linux 6.12.27-amd64 (SMP w/4 CPU threads; PREEMPT)
    Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:de
    Shell: /bin/sh linked to /usr/bin/dash
    Init: systemd (via /run/systemd/system)
    LSM: AppArmor: enabled

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andreas Tille@21:1/5 to All on Thu Jul 24 10:00:01 2025
    Hi Nigel,

    Am Thu, Jul 24, 2025 at 07:23:25AM +0000 schrieb Nigel Kukard:
    Hi there Andreas,

    I'd just like to thank you for salvaging the cputool package, it is very
    much appreciated.

    Thank you for your super fast and very productive answer. I can tell
    for sure this is a rare exception in the process to care for dormant
    packages and thus really helpful and appreciated.

    I must admit, I don't use Debian myself, but at the same time would definitely like to keep cputool it in the Debian repository.

    In case you might use some derivative it can be helpful indirectly. In
    any case thank you for your support for Debian even if not using it.

    Over the past few years I've watched the d.d mailing list, and I'm a little overwhelmed with the packaging system as it stands now and the process for updating packages to new versions, especially with all the different processes and workflows available. It was never easy to pick something and know it is the "right" choice.

    This is a very hot topic on Debian mailing lists. The effort of the
    Salvage team to pick up dormant packages and provide a consistent
    workflow for these is a tiny contribution to the problem.

    I never really had anyone that helped me with packaging, but I would very much like to continue, and if you're willing to assist as co-maintainer I'd really appreciate it. :)

    I'm willing to do so and I added myself as Uploader to express this.

    I signed up for an account on Salsa in the meantime :)

    Please let me know once this is accepted and I'll add you to the project.

    Kind regards
    Andreas.

    --
    https://fam-tille.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andreas Tille@21:1/5 to All on Thu Jul 24 13:40:01 2025
    Hi Nigel,

    Am Thu, Jul 24, 2025 at 08:06:38AM +0000 schrieb Nigel Kukard:

    I can easily spin up a container for testing package updates or if the workflow absolutely requires it, so it shouldn't be a problem in terms of maintaining.

    That's OK. We can probably manage if you simply ping me in case updates
    are somehow once every year or so. That's perfectly bearable.

    Over the past few years I've watched the d.d mailing list, and I'm a little
    overwhelmed with the packaging system as it stands now and the process for
    updating packages to new versions, especially with all the different processes and workflows available. It was never easy to pick something and
    know it is the "right" choice.
    This is a very hot topic on Debian mailing lists. The effort of the Salvage team to pick up dormant packages and provide a consistent
    workflow for these is a tiny contribution to the problem.

    Very much appreciated :)

    :-)
    ... but it takes time and patience. ;-P

    I never really had anyone that helped me with packaging, but I would very much like to continue, and if you're willing to assist as co-maintainer I'd
    really appreciate it. :)
    I'm willing to do so and I added myself as Uploader to express this.

    Thank you kindly, do you perhaps have a link any docs relating to the workflow you envisage for the package?

    There are lots of newcomer docs - at DebConf we also had a newcomer BoF.
    Since I've seen your packaging made perfectly sense (at the time of
    writing) I think you do not need so much more knowledge. You might like
    to checkout my commits and see what I've changed. This should provide
    you with sufficient information (hopefully). Any question about details
    is perfectly welcome. I'm in favour of learning by example ... and
    there is a pretty obvious example for you.

    My personal workflow on this package for a new upstream version would be:

    $ gbp clone salsa:salvage-team/cputool
    $ cd cputool
    [ $ sudo apt install routine-update # which is installed on my computers ]
    $ routine-update
    remove / adapt patches if needed
    $ git push; git push --tags
    check Salsa CI https://salsa.debian.org/salvage-team/cputool/-/pipelines

    A very good idea for you as upstream would be to have some test. I'd
    volunteer to turn this into some autopkgtest which will ensure the
    package works as expected.

    I signed up for an account on Salsa in the meantime :)
    Please let me know once this is accepted and I'll add you to the project.

    Will do :)

    :-)

    Kind regards
    Andreas.




    --
    https://fam-tille.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)