OK I have now regression tested on the latest 19.10, with the above
^^software stack. All except incrementing the kernel from 5.8.11 to
5.8.13.
I can now confirm that the old bug has also re-appeared on 19.10 too. So
it is not only exclusive to 20.04.
To myself, I really don know what to try.
It would be nice to understand what is going on here. Currently on 19.10
and have not upgraded to 20.04 yet... because of this very same bug! It
took so long to get rid of the last time around. Many months.
Should also do a regression test here back on 19.10 too? It seems I can
install both the
Did you see it work on previous ubuntu version (19.10)? Or is 20.04 the
first version you tested here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820832
Title:
[xorg] multiple monitors: limits
Oh hi there Jean... reading that debian bug report there was this
comment from 2 years ago saying:
> > So, any other ideas how to integrate the ZFS support?
> Not beside parsing `zpool`'s output, which I'm afraid I still object to.
Those guys finally realized they cannot put CDDL in the GPL for
I too am also affected,
https://github.com/cockpit-project/cockpit/issues/13343
Please fix this if you can
Many thanks,
** Bug watch added: github.com/cockpit-project/cockpit/issues #13343
https://github.com/cockpit-project/cockpit/issues/13343
--
You received this bug notification because
Thanks for pointing that out because I also had
__GL_SYNC_DISPLAY_DEVICE=DP-0 in /etc/environment as completely forgot
to mention that in my previous comment to yours here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello there. Good news for a change:
Re-tested this bug today on latest linux 5.3.1 kernel and nvidia 435.21
binary (closed) drivers. And it seems like there might be some
improvement now.
What I noticed this time:
* Enabled 120hz overclock on my high refresh 120hz monitor, and rebooted this
well by that logic, then somebody with an amd ryzen APU (such as 3200G
or whichever with the integrated Vega graphics). Would also not be
affected by this bug.
But the other reason would be that intel's linux igp drivers are not
affected. That is a different reason as to whether the gpu is being
Public bug reported:
Hi there,
There is a missing functionality in the following file: /usr/share
/initramfs-tools/hooks/cryptroot
resulting in the following error message:
cryptsetup: ERROR: Couldn't resolve device
cryptsetup: WARNING: Couldn't determine root device
under the following
Oh sorry. Didn't upload the patch correctly (as an attachment). Here it
is then...
** Patch added: "Use however you please"
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1830110/+attachment/5265807/+files/cryptsetup-initramfs__1830110__cryptroot.patch
--
You received this bug
> As luck would have it, one user upstream found a solution for NVIDIA
> documented here:
>
> https://gitlab.gnome.org/GNOME/mutter/issues/503#note_463305
>
Hello. Tried this suggestion today (setting "__GL_MaxFramesAllowed=1" in
/etc/environment, and rebooting). It might have decreased my CPU
Public bug reported:
multiple monitors on xorg
=
Was recently discussed over on
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892
Another user + myself have the following issue:
The slowest connected display limits the FPS. The test case we used is
over
multi-monitor FPS bug for xorg, discussion moved to --->
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820832
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730460
Title:
Very poor
Thank you Daniel. The new bug is
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820832
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but mutter seems
multiple monitors on xorg
=
Was recently discussed over on
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892
Another user + myself have the following issue:
The slowest connected display limits the FPS. The test case we used is
over at the top of the
Hello again. Well this is promising news. Because I am also using xorg
with multiple monitors. And observing the same exact issue. Taking that
discussion over to the other bug then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> I'm on 18.10 with dual monitors, and I'm still capped at 60hz on my
144hz display. However, if I disable my second display (it only supports
60hz), I my main gets 144hz as expected.
Is that with both dislays attached to an nvidia graphics card ? If so,
then what version of the nvidia driver,
there is also this:
https://github.com/solus-project/budgie-desktop/pull/1591
however just not sure if it's something that they need to rebuild there
also with these changes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Installed new mutter from proposed today and... Well it didn't crash my
system. Due to other complications (which were mentioned previously in
may last comment)/ I cannot confirm if it actually fixes the 120/144hz
issue in my specific environment. However the changes seems safe enough
to me.
Thanks Daniel for your recent comments. They are very helpful. As
someone who upgraded to Cosmic specifically to fix this bug. I found it
still wasn't working and simple was not sure the reason (as have other
factors at play on my system, including Budgie Desktop, multiple
monitors, and nvidia
Hi there. Sorry but I'm a bit confused as to which branches will be
getting this fix and which ones will not be. Specifically I as wondering
if a fix might be back-ported to 18.04. Because I need to stay on LTS
release for the canonical kernel live patching service. Otherwise I
really would not
But there's more.
Goto ---> Oliver comment #26
=
> (along with the fact that you can always roll back to any former snap
or snapd version and due to the fully transactional nature of snaps this
needs to be fully backwards compatible as zyga mentioned above)
Yes
I also found these previous comments (by developers maybe?). They were
phrased Rhetorically, as examples. However it feels constructive to
actually try to answer them. To see what other work is required.
Goto ---> Jamie comment #29
> The problem is all the other
Actually my above example is far from ideal. But those would be the
general kinds of ideas to convey to people.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Please move the
Example:
Just enough for them to understand with enough clarity what this folder
actually is. What it is for.
Written in plain english (--> then translated / Localized, assuming that is
possible for the other languages).
~/.snaps/README.txt:
=
* This folder contains your
It seems from prior comments, that while this system was still being
developed... well it was not clear yet precisely how apps might be using
this folder. What stuff they could be writing in there. So might have
been considered instead from the outset?
The suggestion was already discussed of
I am with comment #73 to #76 entirely. Anyhow. Not sure to what degree
this suggestion is still relevant, but I would like to add a tiny bit
more to it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi. Just to say thanks for fixing this. However the bug has occured for
me very recently on 16.04 LTS. Both 16.04.1 (4.4 kernel) and 16.04.2
(4.8 kernel).
So at this time this was not fixed for 16.04. Which aligns with the 'no
fix target' here for '16.04' in the bug description. Anyhow regardless
Public bug reported:
Hi there,
This is an independantly confirmed upstream bug, which occurs in version
6.0.3 of syslinux / plxelinux upsteram sources. The fix has already been
committed to upstream, and can be found here:
http://www.syslinux.org/archives/2015-September/024305.html
If you read
Also: the suggested workaround didnt actually work for me. on 15.10 /
wily
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1384394
Title:
/etc/network/interfaces: "dns-nameservers"
Also: the suggested workaround didnt actually work for me. on 15.10 /
wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384394
Title:
/etc/network/interfaces: "dns-nameservers" entries for bridge
So why isnt br* already listed by default in the file /etc/resolvconf
/interface-order ? There are many other entries for everything else. And
presumably it should do no harm / detriment.
Should that not be the fix here?
br* bridge interfaces are a common class of network devices and are
being
So why isnt br* already listed by default in the file /etc/resolvconf
/interface-order ? There are many other entries for everything else. And
presumably it should do no harm / detriment.
Should that not be the fix here?
br* bridge interfaces are a common class of network devices and are
being
Public bug reported:
Right.
Well this bug is something I stumbled into today. It turns out that:
Whenever I have invalid /etc/fstab entries, the system fails to start
with systemd.
This can be seen in the debian bug tracker as bug #765586:
Public bug reported:
This isn't supposed to happen...
id@emachines-e520:~$ sudo sh -x /etc/init.d/procps reload
+ PATH=/sbin:/bin
+ SYSCTL=/sbin/sysctl
+ test -x /sbin/sysctl
+ . /lib/lsb/init-functions
+ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
+ [ -r
Hello. This seems to affect me too, on 14.10, docker 1.5.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1423047
Title:
Apport throws Invalid process ID exception and no coredump output
when a
The most logical thing to do would be port the OpenSolaris source code
to linux. It is available here:
http://src.illumos.org/source/xref/illumos-
gate/usr/src/cmd/fs.d/udfs/fsck/
AFAICT it is pretty self-contained. This should really be made a
priority first of all.
2nd priority after that,
The Debian PHP maint have previously stated that they have either no or
only a little interest in adding php-fpm to Debian. There is no vision
or leadership from the Debian side which embraces the fpm sapi. Which is
a shame as it is already a very popular sapi.
Therefore if canoical wants this
Staying focussed, If what Ondrej is saying today is actually more
representative of the official Debian position, then thats positive
news on Debians part. And we should be grateful for that. Its quite
welcome for Ondrej here to bring the matter up within Debian after
Php-5.4, and / or the formal
Staying focussed, If what Ondrej is saying today is actually more
representative of the official Debian position, then thats positive
news on Debians part. And we should be grateful for that. Its quite
welcome for Ondrej here to bring the matter up within Debian after
Php-5.4, and / or the formal
The Debian PHP maint have previously stated that they have either no or
only a little interest in adding php-fpm to Debian. There is no vision
or leadership from the Debian side which embraces the fpm sapi. Which is
a shame as it is already a very popular sapi.
Therefore if canoical wants this
Sorry - that comment (#3) was meant for a different bug, #411890
--
autoconf should print a warning notice when switching autoconf version
https://bugs.launchpad.net/bugs/412448
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
If it's a timestamps issue:
# When patching files like configure.in, aclocal.m4, configure can run twice.
Later the compilation
# finishes with an error. If this happens use the debugging mode of the make
command:
# `$(MAKE) --debug` instead of just `$(MAKE)` in the build targets below.
#
** Changed in: php-fpm
Importance: Undecided = High
--
[needs-packaging] php-fpm
https://bugs.launchpad.net/bugs/397721
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in ubuntu.
--
Ubuntu-server-bugs mailing list
** Changed in: php-fpm
Importance: Undecided = High
--
[needs-packaging] php-fpm
https://bugs.launchpad.net/bugs/397721
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
LiteSpeed SAPI is now included with php-5.3.0 and greater. It would be a
good idea to do this when upgrading the php source package.
** Package changed: ubuntu = php5 (Ubuntu)
--
[needs-packaging] php5-litespeed
https://bugs.launchpad.net/bugs/371612
You received this bug notification because
** Bug watch added: Debian Bug tracker #547534
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547534
** Also affects: php5 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547534
Importance: Unknown
Status: Unknown
--
[needs-packaging] php5-litespeed
LiteSpeed SAPI is now included with php-5.3.0 and greater. It would be a
good idea to do this when upgrading the php source package.
** Package changed: ubuntu = php5 (Ubuntu)
--
[needs-packaging] php5-litespeed
https://bugs.launchpad.net/bugs/371612
You received this bug notification because
** Bug watch added: Debian Bug tracker #547534
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547534
** Also affects: php5 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547534
Importance: Unknown
Status: Unknown
--
[needs-packaging] php5-litespeed
to compile fpm from the
standalone project.
dreamcat4
dreamc...@gmail.com
--
[needs-packaging] php-fpm
https://bugs.launchpad.net/bugs/397721
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in ubuntu.
--
Ubuntu-server-bugs mailing list
to compile fpm from the
standalone project.
dreamcat4
dreamc...@gmail.com
--
[needs-packaging] php-fpm
https://bugs.launchpad.net/bugs/397721
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
if they care
about all this same project / seperate project dilemma. They may come
back either way.
We would still need this exception for karmic however.
Best regards,
dreamcat4
dreamc...@gmail.com
--
[FFe] Feature Freeze Exception Request for php5-fpm
https://bugs.launchpad.net/bugs/423872
** Also affects: gnome-desktop (Ubuntu)
Importance: Undecided
Status: New
--
Gnome session fails on login
https://bugs.launchpad.net/bugs/424370
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Karmic should be set as the 'release'.
--
Gnome session fails on login
https://bugs.launchpad.net/bugs/424370
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
On Fri, Sep 4, 2009 at 4:25 PM, Scott Kittermanubu...@kitterman.com wrote:
What is PHP upstream's position on this? Why isn't it shipped as part of PHP?
Good questions - keep them coming!
Perhaps these concerns are about official support to help understand
risks of incompatibilities /
these efforts any
way we can.
Best regards,
dreamcat4
dreamc...@gmail.com
--
[FFe] Feature Freeze Exception Request for php5-fpm
https://bugs.launchpad.net/bugs/423872
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Branch linked: lp:ubuntu/karmic/php5
--
[needs-packaging] php-fpm
https://bugs.launchpad.net/bugs/397721
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in ubuntu.
--
Ubuntu-server-bugs mailing list
** Branch linked: lp:ubuntu/karmic/php5
--
[needs-packaging] php-fpm
https://bugs.launchpad.net/bugs/397721
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Summary changed:
- Feature Freeze Exception Request for php5-fpm
+ [FFe] Feature Freeze Exception Request for php5-fpm
--
[FFe] Feature Freeze Exception Request for php5-fpm
https://bugs.launchpad.net/bugs/423872
You received this bug notification because you are a member of Ubuntu
Bugs,
Feature Freeze Exception Request for php5-fpm: Bug #423872
--
[needs-packaging] php-fpm
https://bugs.launchpad.net/bugs/397721
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
believe the package is ready. php5-fpm comes as a patch file, and new
build target to the existing php5 source package.
Now that we have a newer upstream version:
https://code.launchpad.net/~dreamcat4/php-fpm/master, we will now be
able to support php5-fpm as an ubuntu package. The new upstream
REVU: http://revu.ubuntuwire.com/p/php5
--
[needs-packaging] php-fpm
https://bugs.launchpad.net/bugs/397721
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in ubuntu.
--
Ubuntu-server-bugs mailing list
REVU: http://revu.ubuntuwire.com/p/php5
--
[needs-packaging] php-fpm
https://bugs.launchpad.net/bugs/397721
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: php-fpm
Status: New = Confirmed
--
[needs-packaging] php-fpm
https://bugs.launchpad.net/bugs/397721
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in ubuntu.
--
Ubuntu-server-bugs mailing list
** Changed in: php-fpm
Status: New = Confirmed
--
[needs-packaging] php-fpm
https://bugs.launchpad.net/bugs/397721
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Hi guy's,
The build ubuntu3~pre10 seems to be working allright, since making a fix for
that segfault bug its all working again. I just loaded it up with a whole bunch
of extensions and ran phpinfo (file attached). Needs 1 more PDO warning
message supressed, and that will be available as
** Attachment added: php5_5.2.10.dfsg.1-2ubuntu3~pre12.diff.gz
http://launchpadlibrarian.net/31013724/php5_5.2.10.dfsg.1-2ubuntu3%7Epre12.diff.gz
--
[needs-packaging] php-fpm
https://bugs.launchpad.net/bugs/397721
You received this bug notification because you are a member of Ubuntu
Server
** Attachment added: php5_5.2.10.dfsg.1-2ubuntu3~pre12.debdiff
http://launchpadlibrarian.net/31013765/php5_5.2.10.dfsg.1-2ubuntu3%7Epre12.debdiff
--
[needs-packaging] php-fpm
https://bugs.launchpad.net/bugs/397721
You received this bug notification because you are a member of Ubuntu
Server
** Attachment added: php5_5.2.10.dfsg.1-2ubuntu3~pre12.dsc
http://launchpadlibrarian.net/31013699/php5_5.2.10.dfsg.1-2ubuntu3%7Epre12.dsc
--
[needs-packaging] php-fpm
https://bugs.launchpad.net/bugs/397721
You received this bug notification because you are a member of Ubuntu
Server Team,
Hi guy's,
The build ubuntu3~pre10 seems to be working allright, since making a fix for
that segfault bug its all working again. I just loaded it up with a whole bunch
of extensions and ran phpinfo (file attached). Needs 1 more PDO warning
message supressed, and that will be available as
** Attachment added: php5_5.2.10.dfsg.1-2ubuntu3~pre12.dsc
http://launchpadlibrarian.net/31013699/php5_5.2.10.dfsg.1-2ubuntu3%7Epre12.dsc
--
[needs-packaging] php-fpm
https://bugs.launchpad.net/bugs/397721
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: php5_5.2.10.dfsg.1-2ubuntu3~pre12.debdiff
http://launchpadlibrarian.net/31013765/php5_5.2.10.dfsg.1-2ubuntu3%7Epre12.debdiff
--
[needs-packaging] php-fpm
https://bugs.launchpad.net/bugs/397721
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: php5_5.2.10.dfsg.1-2ubuntu3~pre12.diff.gz
http://launchpadlibrarian.net/31013724/php5_5.2.10.dfsg.1-2ubuntu3%7Epre12.diff.gz
--
[needs-packaging] php-fpm
https://bugs.launchpad.net/bugs/397721
You received this bug notification because you are a member of Ubuntu
Bugs,
1. The php-fpm 0.6 is not compatible with PDO = shared. I believe this
is important enough to issue document in the FPM project's FAQ. This
incompatibility is with PDO=shared only. Normal (build-in) PDO works.
Its for such a difficult link to make from the error in the log file,
that we need to
1. The php-fpm 0.6 is not compatible with PDO = shared. I believe this
is important enough to issue document in the FPM project's FAQ. This
incompatibility is with PDO=shared only. Normal (build-in) PDO works.
Its for such a difficult link to make from the error in the log file,
that we need to
Good news: The issue for loading zend extensions is now fixed.
Bad news: Theres some other problem the child workers keep dying.
Details on jottit:
http://dreamcat4.jottit.com/new_php5-fpm_testing_candidate
--
[needs-packaging] php-fpm
https://bugs.launchpad.net/bugs/397721
You received
Good news: The issue for loading zend extensions is now fixed.
Bad news: Theres some other problem the child workers keep dying.
Details on jottit:
http://dreamcat4.jottit.com/new_php5-fpm_testing_candidate
--
[needs-packaging] php-fpm
https://bugs.launchpad.net/bugs/397721
You received
** Branch linked: lp:~dreamcat4/php-fpm/master
--
[needs-packaging] php-fpm
https://bugs.launchpad.net/bugs/397721
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs
** Branch linked: lp:~dreamcat4/php-fpm/master
--
[needs-packaging] php-fpm
https://bugs.launchpad.net/bugs/397721
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
Hello,
I have now a TESTING package for ubuntu.
Instructions and guide available at:
http://dreamcat4.jottit.com/new_php5-fpm_testing_candidate
Checklist:
- Operation with sqlite, mysql and pgsql databases
- Check inter-operability with apache2 webserver
- Look for and possible conflicts
Hello,
I have now a TESTING package for ubuntu.
Instructions and guide available at:
http://dreamcat4.jottit.com/new_php5-fpm_testing_candidate
Checklist:
- Operation with sqlite, mysql and pgsql databases
- Check inter-operability with apache2 webserver
- Look for and possible conflicts
On Fri, Aug 14, 2009 at 12:26 PM, James Westbyjw+deb...@jameswestby.net wrote:
Why did you drop the dependency on automake1.4?
That's a rookie mistake as i had believed that autoconf2.13 depends
upon automake1.4. But automake is not a dependancy - its a
'recommends'. Thanks for picking that up.
Wow - that's impressive! Very pleased to find out. Hopefully one day
this information will get its way into the package description field, of
the main autoconf package.
--
autoconf should print a warning notice when switching autoconf version
https://bugs.launchpad.net/bugs/412448
You received
On Wed, Aug 12, 2009 at 8:27 AM, Andreas Olssonandr...@arrakis.se wrote:
autoconf) does make php5 build nicely. I generated new source packages
with this change, and built it without any trouble inside a pbuilder
chroot.
Well, this is fantastic. I've been puzzled and frustrated over this
error
** Attachment added: php5_5.2.10.dfsg.1-1ubuntu2.debdiff
http://launchpadlibrarian.net/3049/php5_5.2.10.dfsg.1-1ubuntu2.debdiff
--
karmic: Compiling php fails with autoconf 2.64
https://bugs.launchpad.net/bugs/411890
You received this bug notification because you are a member of Ubuntu
built it, then im building it too. My compile has
passed the buildconf stage ok now so i think we can consider that
verified.
https://launchpad.net/~dreamcat4/+archive/ppa
php5 (5.2.10.dfsg.1-1ubuntu2) karmic; urgency=low
* debian/control: (autoconf) Update build dependancies (closes: 411890
Public bug reported:
Binary package hint: autoconf2.13
https://launchpad.net/ubuntu/karmic/i386/autoconf
The page says:
This version of autoconf is not compatible with scripts meant for
Autoconf 2.13 or earlier. If you need support for such scripts,
you must also install the autoconf2.13
On Wed, Aug 12, 2009 at 8:27 AM, Andreas Olssonandr...@arrakis.se wrote:
autoconf) does make php5 build nicely. I generated new source packages
with this change, and built it without any trouble inside a pbuilder
chroot.
Well, this is fantastic. I've been puzzled and frustrated over this
error
** Attachment added: php5_5.2.10.dfsg.1-1ubuntu2.debdiff
http://launchpadlibrarian.net/3049/php5_5.2.10.dfsg.1-1ubuntu2.debdiff
--
karmic: Compiling php fails with autoconf 2.64
https://bugs.launchpad.net/bugs/411890
You received this bug notification because you are a member of Ubuntu
built it, then im building it too. My compile has
passed the buildconf stage ok now so i think we can consider that
verified.
https://launchpad.net/~dreamcat4/+archive/ppa
php5 (5.2.10.dfsg.1-1ubuntu2) karmic; urgency=low
* debian/control: (autoconf) Update build dependancies (closes: 411890
** Tags added: verification-done
** Changed in: php5 (Ubuntu)
Status: Triaged = Fix Committed
--
karmic: Compiling php fails with autoconf 2.64
https://bugs.launchpad.net/bugs/411890
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Binary package hint: php5
On a fresh 9.10 (karmic) system, php5 (5.2.10) source package will not
compile.
Steps:
# Install brand new Ubuntu karmic release (alpha 3)
sudo pbuilder --create --distribution karmic
dget -xu
** Attachment added: Build log
http://launchpadlibrarian.net/30155338/karmic-php5-5.2.10-build.log
** Description changed:
Binary package hint: php5
On a fresh 9.10 (karmic) system, php5 (5.2.10) source package will not
compile.
Steps:
# Install brand new Ubuntu karmic
Notifying Andrew Mitchell
Andrew can we get some people to take a look at this? Its a stopper for
[needs-packaging] php-fpm
https://bugs.launchpad.net/bugs/397721
--
karmic: Compiling php fails with autoconf 2.64
https://bugs.launchpad.net/bugs/411890
You received this bug notification
Hi,
There is a stopper for this.
Please see the bug description for details.
karmic: Compiling php fails with autoconf 2.64
https://bugs.launchpad.net/bugs/411890
--
[needs-packaging] php-fpm
https://bugs.launchpad.net/bugs/397721
You received this bug notification because you are a member of
https://launchpad.net/ubuntu/karmic/i386/autoconf
This page says:
This version of autoconf is not compatible with scripts meant for
Autoconf 2.13 or earlier. If you need support for such scripts,
you must also install the autoconf2.13 package.
If you choose install autoconf2.13 package in
Public bug reported:
Binary package hint: php5
On a fresh 9.10 (karmic) system, php5 (5.2.10) source package will not
compile.
Steps:
# Install brand new Ubuntu karmic release (alpha 3)
sudo pbuilder --create --distribution karmic
dget -xu
** Attachment added: Build log
http://launchpadlibrarian.net/30155338/karmic-php5-5.2.10-build.log
** Description changed:
Binary package hint: php5
On a fresh 9.10 (karmic) system, php5 (5.2.10) source package will not
compile.
Steps:
# Install brand new Ubuntu karmic
** Summary changed:
- karmic: configure fails with cat: confdefs.h: No such file or directory
+ karmic: Compiling php fails with autoconf 2.64
** Description changed:
Binary package hint: php5
- On a fresh 9.10 (karmic) system, php5 (5.2.10) source package will not
- compile.
+ On a fresh
Notifying Andrew Mitchell
Andrew can we get some people to take a look at this? Its a stopper for
[needs-packaging] php-fpm
https://bugs.launchpad.net/bugs/397721
--
karmic: Compiling php fails with autoconf 2.64
https://bugs.launchpad.net/bugs/411890
You received this bug notification
1 - 100 of 113 matches
Mail list logo
