Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The project doesn't contain an example systemd .service file for starting the queue runner (only one for init.d). This might be important since debian is switching to systemd and archlinux has switched a while ago.
Comment | File | Size | Author |
---|---|---|---|
#16 | no_systemd_service_file-2347557-15.patch | 1.33 KB | gboudrias |
#3 | no_systemd_service_file-2347557-3.patch | 645 bytes | helmo |
#1 | no_systemd_service_file-2347557-1.patch | 377 bytes | helmo |
Comments
Comment #1
helmo CreditAttribution: helmo at Initfour websolutions commentedfirst draft
Comment #2
helmo CreditAttribution: helmo at Initfour websolutions commentedTesting this in #2493451-5: Puppet and Debian Jessie
Comment #3
helmo CreditAttribution: helmo at Initfour websolutions commentedUpdated with the new drush location... and committed.
We might want to do an extra debian package update for this.
Comment #4
gboudrias CreditAttribution: gboudrias at Praxis Labs Coop commentedNot sure how to test patches to debian packages but manually creating the file in your patch seemed to solve the install issue.
Comment #5
gboudrias CreditAttribution: gboudrias at Praxis Labs Coop commentedThis doesn't seem to simply install yet. I've grep'd the repo for systemd and came up empty.
I've looked at the doc and I'm pretty sure we're missing things:
Most importantly, it seems we need to replace "dh $@" with "dh $@ --with=systemd".
I assume this would mess up the init.d setup so we probably need to detect whether systemd is installed. (I would personally just drop init.d support entirely, but I suspect there are use cases I'm not aware of here.)
I have no idea how to test this :)
Comment #6
helmo CreditAttribution: helmo at Initfour websolutions commentedNot sure what made it work in my previous tests...
Moving to the provision queue as the patch belongs there.
Comment #7
helmo CreditAttribution: helmo at Initfour websolutions commentedComment #9
helmo CreditAttribution: helmo at Initfour websolutions commented:( build failed http://ci.aegirproject.org/view/Debian%20dev%20builds/job/D_aegir-debian...
The CI server is wheezy ... lacking build support for this.
Comment #10
helmo CreditAttribution: helmo at Initfour websolutions commentedI think I tested with a build from my ubuntu dev box before ... guessing that the systemd file was picked up there by default.
Comment #11
helmo CreditAttribution: helmo at Initfour websolutions commentedAs a work around .. create the file manually as /lib/systemd/system/hosting-queued.service
Comment #12
gboudrias CreditAttribution: gboudrias at Praxis Labs Coop commentedComment #13
gboudrias CreditAttribution: gboudrias at Praxis Labs Coop commentedComment #14
anarcat CreditAttribution: anarcat commentednote that even though Debian jessie switched to systemd, it still supports old-style init.d files, so this shouldn't be blocking anything, IMHO.
Comment #15
gboudrias CreditAttribution: gboudrias at Praxis Labs Coop commentedUnless something's changed, we still have the bug, even though we don't need the file, so maybe we should just remove all references to systemd? I'll try to work in that direction.
Comment #16
gboudrias CreditAttribution: gboudrias at Praxis Labs Coop commentedI... I think it worked! Please test against current HEAD :)
(All I did was remove both systemd mentions and the service file, however I don't feel confident enough in my Debian packaging to commit without someone else testing it.)
Comment #18
gboudrias CreditAttribution: gboudrias at Praxis Labs Coop commentedComment #19
helmo CreditAttribution: helmo at Initfour websolutions commentedI'm setting this back to needs work as the current patch clearly breaks the debian build process.
Comment #20
gboudrias CreditAttribution: gboudrias at Praxis Labs Coop commentedLet's try to work on this for 3.2.
Comment #21
helmo CreditAttribution: helmo at Initfour websolutions commentedFor the record...:
On a fresh Debian Jessie:
Comment #22
glenndebacker CreditAttribution: glenndebacker commentedI'm getting the same error as helmo when doing a fresh install. My devops/linux/Aegir kungfu isn't that great so I dare to ask: is there a solution to work around this problem ?
Or is its better to downgrade to Debian Wheezy for the time being ?
Comment #23
tuxick CreditAttribution: tuxick commentedany news on this, or a workaround so i can continue install?
Comment #24
gboudrias CreditAttribution: gboudrias at Praxis Labs Coop commentedOn Jessie you can just run
apt-get install
once it's failed once. If that doesn't fix it you may need to create the service file manually.Comment #25
helmo CreditAttribution: helmo at Initfour websolutions commentedWe now have a Jenkins test that fails on this: http://ci.aegirproject.org/job/P_Aegir_Puppet_Module_functional_test_Aeg...
Comment #28
helmo CreditAttribution: helmo at Initfour websolutions commentedI've committed this again as it shoud go better now that we have #2553221: Build Debian packages in docker container ... but it's not all green yet :(
Comment #29
helmo CreditAttribution: helmo at Initfour websolutions commentedCurrent status: after install the service is available, but not started at boottime.
Notice the status change from 'disabled' to 'enabled'.
To fix this in the Debian package I think we need to add this to the debian/rules file.
dh_systemd_enable --name=hosting-queued
But would that break packages on wheezy again?
Comment #31
helmo CreditAttribution: helmo at Initfour websolutions commentedThis should handle enabling the service ... tested in local vagrant.