Hi Rob,

> What does it mean? Is it fixed in a new release ?

No, not exactly.  In Launchpad a bug report can have multiple "bug
tasks", and in this case I added one to link to the upstream bug report
that you had filed to register it here for reference.  That upstream bug
report was closed as "solved" because you filed the bug with us.  So
that particular task is considered finished.

> I am unfamiliar with reporting bugs in Debian, Do you want me to try
to report it in Debian also? How can I do that?

If you'd like, yes that would help move things forward.  Directions are
at https://www.debian.org/Bugs/Reporting - however since this appears to
be reproducible on our end, if you're not comfortable doing that we
would be able to ourselves.

To explain a bit more, the particular challenge for solving this bug, in
my opinion, is that the mechanics that the nut-server package does to
install this file might need to be broken out as some sort of shared
package, as was suggested by upstream in your referenced link.  That
might be a bit more complicated than something suitable for doing on the
Ubuntu side alone, so I think we'd need to be in consultation with
Debian in order to ensure a solution is arrived at that they could share
with us.  So having a bug report opened with them would be the first
step towards achieving that.  For example, they might prefer rather than
taking this approach, to improve documentation and to make the client
require installation of the server.

---

If you'd like something you can work on to help make progress with this
issue, here are two things that would help:

1.  Write up an explanation of how this *impacts* you.  I.e. did it only
cause confusion, or did it disrupt a production system, or did it break
an upgrade, or...  About a paragraph of well-phrased text would help
communicate what impact is.  In particular, we will want to understand
the likelihood of this issue affecting other many users, or just corner
cases.

2.  Help improve the steps to reproduce this issue on a clean system.
Ultimately we'll need a paint-by-number set of steps.  (Extra credit for
reproducing it in a Debian VM.)

In order to get this fix released to Ubuntu 24.04 users, we'll be
following the "SRU Process" outlined at
https://documentation.ubuntu.com/sru/en/latest/reference/requirements/.
Again, since it appears possible for us to reproduce this on our end, we
can take care of all that, but any parts you help with will most likely
accelerate things.

Btw thanks for following up!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2102107

Title:
  ExecStartPre=/usr/bin/systemd-tmpfiles --create
  /usr/lib/tmpfiles.d/nut-common-tmpfiles.conf (code=exited,
  status=1/FAILURE)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nut/+bug/2102107/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to