Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#35206 - [prosody] /run/prosody paths mismatch
Attached to Project:
Community Packages
Opened by Gustavo Alvarez (sl1pkn07) - Saturday, 11 May 2013, 17:28 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 22 May 2013, 15:35 GMT
Opened by Gustavo Alvarez (sl1pkn07) - Saturday, 11 May 2013, 17:28 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 22 May 2013, 15:35 GMT
|
DetailsHi
- tmpfile don't create /run/prosody (ls: cannot access /run/prosody: No such file or directory). only works if "systemd-tmpfiles --create prosody.conf" is execute by hand - logrotate file point to /var/run/prosody instead run/prosody [2], same like rc.d file [1], and patch file [3] - double slash in [4] (insignificant) [1] https://projects.archlinux.org/svntogit/community.git/tree/trunk/prosody.rcd?h=packages/prosody [2] https://projects.archlinux.org/svntogit/community.git/tree/trunk/prosody.logrotated?h=packages/prosody#n7 [3] https://projects.archlinux.org/svntogit/community.git/tree/trunk/fix-config.patch?h=packages/prosody#n9 [4] https://projects.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/prosody#n62 greetings |
This task depends upon
[1] -> [2]
[2] -> [1]
sorry
https://dl.dropboxusercontent.com/u/6596386/prosody-0.8.2-10.src.tar.gz
for me works
(copy/modify .install structure from [comunity] bitlbee)
greetings
Both of them calls systemd-tmpfiles
https://projects.archlinux.org/svntogit/packages.git/tree/trunk/bitlbee.install?h=packages/bitlbee
https://projects.archlinux.org/svntogit/community.git/tree/trunk/prosody.install?h=packages/prosody
Not sure what is the difference
edited
im not sure. maybe the order?
with your package (install from local or through pacman) don't work, but with modification OK
# rm -rf /run/prosody
# ls -l /run/prosody
ls: cannot access /run/prosody: No such file or directory
# pacman -S prosody
warning: prosody-0.8.2-9 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
Packages (1): prosody-0.8.2-9
Total Installed Size: 0.85 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [###########################################] 100%
(1/1) checking package integrity [###########################################] 100%
(1/1) loading package files [###########################################] 100%
(1/1) checking for file conflicts [###########################################] 100%
(1/1) reinstalling prosody [###########################################] 100%
>> Documentation: http://wiki.archlinux.org/index.php/Prosody
# ls -l /run/prosody
total 0
maybe fixed on systemd-204 (?)
I request reopen issue the same day of the latest prosody update (2013-05-13)
systemd update on 2013-05-12 in [core] and 2013-05-16 in [testing]
this is very weird (I'm clumsy, but not so much)
ok. now fixed (?)
sorry for waste your time
greetings