Package: onedrive
Version: 1.1.20161012-1
Severity: normal
Dear Maintainer,
onedrive.service been shipped to installed to /lib/systemd/user/
But it should be in /usr/lib/systemd/user/ to be listed and start by a user's
systemd
Also, the systemd unit's ExecStart is incorrect
it have
On Mon, 14 Dec 2015 23:31:29 +
Simon McVittie wrote:
> Was this done on the correct system? You mentioned 1.18.3 on your
> other bug report, and 1.17.25 is stable's version of dpkg, whereas
> the rest of your packages seem to be from testing/unstable.
>
> S
>
It seems
Package: game-data-packager
Version: 43
Severity: normal
Dear Maintainer,
* What led up to the situation?
run the following command:
'game-data-packager --no-install --no-compress --verbose --debug
spear-of-destiny 2>&1 | tee gdp.log'
to make a package of spear-of-destiny-demo-data package
Package: game-data-packager
Version: 43
Severity: normal
Dear Maintainer,
ran the command:
game-data-packager --no-install --compress --verbose --debug doom3 Doom\ 3/
2>&1 | tee gdp.log
but the command failed, dpkg-deb return 'dpkg-deb: error: ar member size
10892738560 too large'
so I can
LSB Header's Should-Start avahi entry does not work if the system's
init is systemd, the entry should be named avahi-daemon not avahi
so systemd can pick up that avahi-daemon.service should start Before
pulseaudio.service (even thur that pulseaudio triggers
avahi-daemon.socket and starts up avahi
5 matches
Mail list logo