http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12312 --- Comment #2 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- According to my coworder it did, he had to repeat the process with 'no'. I think because of the change in the permissions. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12312 Magnus Enger <magnus@enger.priv.no> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |magnus@enger.priv.no --- Comment #4 from Magnus Enger <magnus@enger.priv.no> --- Some of the first comments on bug 11404 say we should add the .conf suffix even if you have Apache 2.2, so you won't get surprised when you eventually upgrade to 2.4. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12312 Robin Sheat <robin@catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - low |P1 - high Status|NEW |ASSIGNED See Also| |http://bugs.koha-community. | |org/bugzilla3/show_bug.cgi? | |id=11404 Depends on| |11404 Assignee|koha-bugs@lists.koha-commun |robin@catalyst.net.nz |ity.org | Severity|enhancement |major --- Comment #6 from Robin Sheat <robin@catalyst.net.nz> --- I did a test, and found the issue. It's nothing to do with permissions, it's that if you do: a2ensite foo apache 2.2 will look for /etc/apache2/sites-available/foo and apache 2.4 will look for ..../foo.conf. Our script does a2ensite foo, when it should do a2ensite foo || a2ensite foo.conf to cover both cases. I'll make a patch up for this and role out a new package with it once it's been checked out. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12312 --- Comment #8 from Robin Sheat <robin@catalyst.net.nz> --- Created attachment 28474 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=28474&action=edit Bug 12312 - correctly upgrade under apache 2.2 As the way we need to reference apache instance names has now changed between 2.2 and 2.4, we need to try it out both ways to make sure we get it right. This also allows koha-create/koha-disable to try the .conf version of the name if the first one doesn't work. To test: * Create an instance on an apache 2.2 system with koha < 3.16 * Upgrade to 3.16 with this patch, saying 'yes' to the renaming question ** Make sure you don't see the warning: Warning: problem enabling $site in Apache * Do a 'service apache2 restart' * Make sure you can still access the instance * Make sure that /etc/apache2/sites-enabled/instance.conf exists as a link to /etc/apache2/sites-available/instance.conf * Check that koha-create and koha-remove behave like you'd expect. Note: * If you need to make debconf forget that it asked you the question about renaming so that it'll do it again, then run: echo "unregister koha-common/rename-apache-vhost-files" | sudo debconf-communicate koha-common * 'debconf-show koha-common' will show you the current debconf configuration. -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12312 Robin Sheat <robin@catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.renvoize@ptfs-europe | |.com -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12312 Galen Charlton <gmcharlt@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Signed Off CC| |gmcharlt@gmail.com --- Comment #11 from Galen Charlton <gmcharlt@gmail.com> --- Pushed to master and 3.16.x. Thanks, Robin! -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12312 Galen Charlton <gmcharlt@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Passed QA |Pushed to Master -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12312 --- Comment #12 from Galen Charlton <gmcharlt@gmail.com> --- Robin: I have created a special tag called v3.16.00-pkg for you to use when creating a replacement 3.16.0 package. -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12312 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook@prosentient.com.au --- Comment #14 from David Cook <dcook@prosentient.com.au> --- If I understand this correctly, including the ".conf" suffix will only cause problems with the koha-enable and koha-disable scripts? I ran the upgrade with "yes" and it worked fine on my Debian system, but I didn't/haven't done any enabling/disabling. I would be surprised if including the suffix broke anything else in regards to Apache 2.2, as other systems (like OpenSuse and Fedora) use ".conf" suffixes by default. -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12312 --- Comment #16 from Robin Sheat <robin@catalyst.net.nz> --- It was because the postint script says "a2ensite foo" when it needs to say "a2ensite foo.conf" on 2.2, so the site never got reenabled after the update. Now if just the name fails, it tries with .conf, which hopefully works. -- You are receiving this mail because: You are watching all bug changes.