Launchpad has imported 12 comments from the remote bug at
http://issues.apache.org/bugzilla/show_bug.cgi?id=55787.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
This bug was fixed in the package apache2 - 2.4.6-2ubuntu2.1
---
apache2 (2.4.6-2ubuntu2.1) saucy; urgency=low
* d/p/ignore-quilt-dir, d/p/itk-rerun-configure.patch: adjust build system so
that it does not use files find inside the .pc directory. This stops a
double module
This bug was fixed in the package apache2 - 2.4.6-2ubuntu2.1
---
apache2 (2.4.6-2ubuntu2.1) saucy; urgency=low
* d/p/ignore-quilt-dir, d/p/itk-rerun-configure.patch: adjust build system so
that it does not use files find inside the .pc directory. This stops a
double module
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1251939
Title:
Chroot fails with Cannot chroot when not started
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251939
Title:
Chroot fails with Cannot chroot when not started as root error
To
I can confirm that Chroot is working in the proposed (2.4.6-2ubuntu2.1 )
Thank you for the fix.
-Arul
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1251939
Title:
Chroot fails
I can confirm that Chroot is working in the proposed (2.4.6-2ubuntu2.1 )
Thank you for the fix.
-Arul
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251939
Title:
Chroot fails with Cannot chroot
Hello Arul, or anyone else affected,
Accepted apache2 into saucy-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/apache2/2.4.6-2ubuntu2.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Arul, or anyone else affected,
Accepted apache2 into saucy-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/apache2/2.4.6-2ubuntu2.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
As 2.4.6-4 hasn't been uploaded to Debian yet, and fixing Trusty blocks
fixing Saucy, I've verified the problem with a dep8 test, verified
Stefan's patch with it and uploaded the fix to Trusty. Thanks!
** Changed in: apache2 (Ubuntu)
Status: Triaged = Fix Committed
** Also affects:
** Description changed:
+ [Impact]
+
+ The Apache ChrootDir doesn't work, causing Apache to fail if you try to
+ use it. This means that it is not possible to run Apache in a chroot,
+ which is a regression from 13.04.
+
+ [Development Fix]
+
+ Adjust build system to not use things inside
This bug was fixed in the package apache2 - 2.4.6-2ubuntu4
---
apache2 (2.4.6-2ubuntu4) trusty; urgency=low
* d/p/ignore-quilt-dir, d/p/itk-rerun-configure.patch: adjust build system so
that it does not use files find inside the .pc directory. This stops a
double module
As 2.4.6-4 hasn't been uploaded to Debian yet, and fixing Trusty blocks
fixing Saucy, I've verified the problem with a dep8 test, verified
Stefan's patch with it and uploaded the fix to Trusty. Thanks!
** Changed in: apache2 (Ubuntu)
Status: Triaged = Fix Committed
** Also affects:
** Description changed:
+ [Impact]
+
+ The Apache ChrootDir doesn't work, causing Apache to fail if you try to
+ use it. This means that it is not possible to run Apache in a chroot,
+ which is a regression from 13.04.
+
+ [Development Fix]
+
+ Adjust build system to not use things inside
This bug was fixed in the package apache2 - 2.4.6-2ubuntu4
---
apache2 (2.4.6-2ubuntu4) trusty; urgency=low
* d/p/ignore-quilt-dir, d/p/itk-rerun-configure.patch: adjust build system so
that it does not use files find inside the .pc directory. This stops a
double module
Any update on when can we get a fix for this?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1251939
Title:
Chroot fails with Cannot chroot when not started as root error
To
Any update on when can we get a fix for this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251939
Title:
Chroot fails with Cannot chroot when not started as root error
To manage notifications
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Looks like we need to cherry-pick this upstream fix if we do not merge
it in first.
** Changed in: apache2 (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of
Since ChrootDir is not a default option, I think Medium priority is
appropriate given the criteria listed at
https://wiki.ubuntu.com/Bugs/Importance. That's not to say we shouldn't
fix it, and an SRU to Saucy isn't out of the question, either.
** Changed in: apache2 (Ubuntu)
Importance:
Thank you for reviewing this bug report and assigning the severity.
While I agree with you on the assigned severity of Medium, I'd like
to point out that though ChrootDir is not a default option, it relates
to the security of apache server. I am not sure how many users simply
use the server w/
If you fix that, you also need to regenerate debian/patches/itk-rerun-
configure.patch after the upstream patch has been applied . I have done
that in the attached patch. I would recommend that you do that for
saucy.
This will also be fixed in 2.4.6-4, which will be uploaded to Debian
soon.
The attachment patch against 2.4.6-2 seems to be a patch. If it
isn't, please remove the patch flag from the attachment, remove the
patch tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Looks like we need to cherry-pick this upstream fix if we do not merge
it in first.
** Changed in: apache2 (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of
Since ChrootDir is not a default option, I think Medium priority is
appropriate given the criteria listed at
https://wiki.ubuntu.com/Bugs/Importance. That's not to say we shouldn't
fix it, and an SRU to Saucy isn't out of the question, either.
** Changed in: apache2 (Ubuntu)
Importance:
Thank you for reviewing this bug report and assigning the severity.
While I agree with you on the assigned severity of Medium, I'd like
to point out that though ChrootDir is not a default option, it relates
to the security of apache server. I am not sure how many users simply
use the server w/
If you fix that, you also need to regenerate debian/patches/itk-rerun-
configure.patch after the upstream patch has been applied . I have done
that in the attached patch. I would recommend that you do that for
saucy.
This will also be fixed in 2.4.6-4, which will be uploaded to Debian
soon.
The attachment patch against 2.4.6-2 seems to be a patch. If it
isn't, please remove the patch flag from the attachment, remove the
patch tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
27 matches
Mail list logo
