Bug 1756395 - Invalid unit name
Summary: Invalid unit name
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: syncthing
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Fabio Valentini
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-27 14:21 UTC by Alessio
Modified: 2019-11-14 01:12 UTC (History)
3 users (show)

Fixed In Version: syncthing-1.3.1-1.fc30 syncthing-1.3.1-1.fc31
Clone Of:
Environment:
Last Closed: 2019-11-13 17:56:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Alessio 2019-09-27 14:21:08 UTC
dnf install syncthing on Fedora 31

Running transaction
  Preparing        :                                                                                                                                                               1/1 
  Installing       : syncthing-1.2.2-1.fc31.x86_64                                                                                                                                 1/1 
  Running scriptlet: syncthing-1.2.2-1.fc31.x86_64                                                                                                                                 1/1 
Invalid unit name "syncthing@*.service" was escaped as "syncthing@\x2a.service" (maybe you should use systemd-escape?)

  Verifying        : syncthing-1.2.2-1.fc31.x86_64                                                                                                                                 1/1 

Installed:
  syncthing-1.2.2-1.fc31.x86_64                                                                                                                                                        

Complete!


It is a warn only.

Comment 1 Fabio Valentini 2019-09-28 12:40:21 UTC
It looks like systemd on fedora 31 has slightly different behaviour here than on earlier releases ...

I'll remove the "user session" scriptlets with the next update, since they seem to be no-ops anyway.

Comment 2 Fabio Valentini 2019-10-04 15:40:12 UTC
(In reply to Fabio Valentini from comment #1)
> It looks like systemd on fedora 31 has slightly different behaviour here
> than on earlier releases ...
> 
> I'll remove the "user session" scriptlets with the next update, since they
> seem to be no-ops anyway.

This is no longer true, and this bug affects only the system service. Sorry for the confusion ...
I've asked for help how to resolve this issue.

Comment 3 Fedora Update System 2019-11-05 16:05:10 UTC
FEDORA-2019-120b9af584 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-120b9af584

Comment 4 Fedora Update System 2019-11-05 16:05:36 UTC
FEDORA-2019-ddddc45543 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-ddddc45543

Comment 5 Fedora Update System 2019-11-06 14:03:33 UTC
syncthing-1.3.1-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-ddddc45543

Comment 6 Fedora Update System 2019-11-06 14:13:20 UTC
syncthing-1.3.1-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-120b9af584

Comment 7 Fedora Update System 2019-11-13 17:56:45 UTC
syncthing-1.3.1-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2019-11-14 01:12:18 UTC
syncthing-1.3.1-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.