The attachment "simple-image-reducer fix" 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
** Patch added: "PIL/Pillow fix"
https://bugs.launchpad.net/ubuntu/+source/simple-image-reducer/+bug/1112496/+attachment/5117196/+files/simple-image-reducer.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Problem still exists in current repository version
** Changed in: simple-image-reducer (Ubuntu)
Status: Invalid => Fix Released
** Changed in: simple-image-reducer (Ubuntu)
Assignee: (unassigned) => ipatrol (ipatrol6010)
--
You received this bug notification because you are a
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: phatch (Ubuntu Raring)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm not that familiar with the package, so I can't tell for certain
whether it has been fixed, but I tried phatch version 0.2.7.1-3 on
Ubuntu 14.04 which installed and started without any error messages.
From what I see from the comments, it seems like phatch would simply
crash on startup, so
@Toshio, how exactly can I apply this patch in Ubuntu ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
python-imaging broken in raring
To manage notifications about this bug go to:
I can't tell if phatch still has this problem from the comments but if
needed, here's a patch for it:
http://pkgs.fedoraproject.org/cgit/phatch.git/plain/phatch-pillow.patch
When Fedora switched over to Pillow about the same time as Ubuntu, a
group of us took care of generating all the patches
#39 - solution worked for me too
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
python-imaging broken in raring
To manage notifications about this bug go to:
me too wyderka-t and I am using raring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
python-imaging broken in raring
To manage notifications about this bug go to:
yes ! it works for me and my father too. The #39 comment is efficient,
thanks !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
python-imaging broken in raring
To manage
Yes it worked for me too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
python-imaging broken in raring
To manage notifications about this bug go to:
Hi, if I cannot change import Image to from PIL import Image in my
application, how should fix this Raring only issue?
I cannot make that change, because I have local file
TiffImagePlugin.py which is modificated version from python-imaging,
and import Image loads this file from local folder too.
Hey all
Here is a method to make symlinks, instead of copy the needed files:
$ sudo su -
# cd /usr/share/phatch/phatch
# for i in /usr/lib/python3/dist-packages/PIL/*.*; do ln -s $i ${i##*/};
done
After that command, you will get this information:
ln: failed to create symbolic link
I fixed my local installation of phatch by editing
/usr/share/phatch/phatch/lib/thumbnail.py and changing import
PngImagePlugin in line 62, to from PIL import PngImagePlugin.
worked for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Still affects me:
Traceback (most recent call last):
File /usr/bin/phatch, line 16, in module
main(config_paths, app_file = __file__)
File /usr/share/phatch/phatch/app.py, line 203, in main
from core.settings import create_settings
File /usr/share/phatch/phatch/core/settings.py,
I get this with phatch, no picture traited : I don't know anything about ; is
it the same subject ? like in
https://bugs.launchpad.net/phatch/+bug/1156583
?
(I hope not to do anyone in lauchnpad waste time)
~$ phatch
Traceback (most recent call last):
File
On Apr 30, 2013, at 06:59 PM, Jan D wrote:
Still affects me:
Traceback (most recent call last):
File /usr/bin/phatch, line 16, in module
main(config_paths, app_file = __file__)
File /usr/share/phatch/phatch/app.py, line 203, in main
from core.settings import create_settings
File
Hi, I tried your command lines in #32, and I added the python-imaging-compat
pakage before too (#21)
I get this problem since my upgrade to raring. Not fixed here, it affects
phatch, wich is running but can't make effective work, and didn't recognize any
picture file.
--
You received this
Any idea if there will be an update?
I switched to Raring and cannot use Phatch :(
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
python-imaging broken in raring
To manage
** Also affects: python-imaging
Importance: Undecided
Status: New
** Also affects: phatch
Importance: Undecided
Status: New
** No longer affects: python-imaging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Found a solution from https://bugs.launchpad.net/phatch/+bug/1156583 by
user KEIII about a broken symlink. Additionally python3-imaging is
*missing* from the depencies of the phatch package. (besides python-
imaging and python-imaging-compat)
1.) sudo apt-get install python3-imaging
2.) User
Still affects me. Not fixed.
phatch
Traceback (most recent call last):
File /usr/bin/phatch, line 16, in module
main(config_paths, app_file = __file__)
File /usr/share/phatch/phatch/app.py, line 203, in main
from core.settings import create_settings
File
Regression in package 1.1.7+2.0.0-1 maybe. As this bug report has status
fix released, I suggest you open a new bug report and refer to it from
here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Christian, just replace it with
from PIL import PngImagePlugin
and check the source for other occurrences. Then attach the patch to
this issue.
** Changed in: phatch (Ubuntu Raring)
Importance: Undecided = High
** Changed in: phatch (Ubuntu Raring)
Status: Invalid = Confirmed
--
This still affects pyolfc, which unsuccessfully tries to import
GifImagePlugin. See bug #1160571.
BTW, Debian has started a transition for PIL - Pillow, see
http://lists.debian.org/debian-devel/2013/02/msg00176.html
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Branch linked: lp:ubuntu/raring-proposed/python-imaging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
python-imaging broken in raring
To manage notifications about this bug go
This bug was fixed in the package python-imaging - 1.1.7+1.7.8-1ubuntu2
---
python-imaging (1.1.7+1.7.8-1ubuntu2) raring; urgency=low
* Add python-imaging-compat modules to get back the old top-level module
names (i.e. not subpackages within PIL) for Python 2 only. (Barry
** Branch linked: lp:ubuntu/python-imaging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
python-imaging broken in raring
To manage notifications about this bug go to:
It works for me. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
python-imaging broken in raring
To manage notifications about this bug go to:
** Also affects: wsjt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
python-imaging broken in raring
To manage notifications
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: wsjt (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
Thanks; the new python-imaging fixed wsjt; thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
python-imaging broken in raring
To manage notifications about this bug go to:
Twas the python-imaging that did it; marking invalid for wsjt.
** Changed in: wsjt (Ubuntu Raring)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
fixed for me too
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
python-imaging broken in raring
To manage notifications about this bug go to:
Fixed for me too
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
python-imaging broken in raring
To manage notifications about this bug go to:
** Changed in: simple-image-reducer (Ubuntu Raring)
Status: Confirmed = Invalid
** Changed in: phatch (Ubuntu Raring)
Status: Confirmed = Invalid
** Changed in: ocrfeeder (Ubuntu Raring)
Status: Confirmed = Invalid
** Changed in: gwibber (Ubuntu Raring)
Status:
** Also affects: ocrfeeder (Ubuntu)
Importance: Undecided
Status: New
** Also affects: comix (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: comix (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ocrfeeder (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
** Also affects: simple-image-reducer (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
python-imaging broken in raring
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: simple-image-reducer (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
I just put the hard-drive from my old (dead) desktop into my new one.
It has raring installed. ocrfeeder worked Ok. It was almost two weeks
since any software updates. After I did the updates, which included
Python, the problem appeared, so it occurred within about the last ten
days. The
Is fixing the broken imports an option? If not, then yeah restoring
PIL's PIL.pth is probably the best approach. We can't do this in Pillow,
but it probably makes sense for Ubuntu to do it as a patch until such
time as the imports can be fixed.
--
You received this bug notification because you
On Feb 08, 2013, at 12:25 PM, Alex Clark wrote:
Is fixing the broken imports an option?
Probably only with enough volunteers to fix upstream and/or provide patches to
the Debian and/or Ubuntu packages. It's always better to fix things as far
upstream as possible of course.
If not, then yeah
just Image doesn't seem to be enough. What about starting with the
modules listed in the PIL handbook?
http://pythonware.com/library/pil/handbook/ (Part II, Module Reference)
The Image Module
The ImageChops Module
The ImageColor Module
The ImageDraw Module
The ImageEnhance Module
The ImageFile
On Feb 06, 2013, at 02:04 PM, Matthias Klose wrote:
just Image doesn't seem to be enough. What about starting with the
modules listed in the PIL handbook?
http://pythonware.com/library/pil/handbook/ (Part II, Module Reference)
The Image Module
The ImageChops Module
The ImageColor Module
The
I like the idea of a compat package. Let me see if I can whip something
up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
python-imaging broken in raring
To manage notifications
As Rachel observes in the bug description, just adding a PIL.pth file
won't be enough. I do not want to modify Pillow to use non-relative
imports.
What I think might work is a PILcompat.pth file and a PILcompat Python
package. Inside there would be files like Image.py that do
from PIL import
** Branch linked: lp:~barry/ubuntu/raring/python-imaging/lp1112496
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
python-imaging broken in raring
To manage notifications about this
Well, something like the linked branch is the idea. It works for
`import Image` (Python 2 only of course), but if there are other modules
that typically get imported from the top-level namespace instead of as a
subpackage of PIL, they'll have to be added individually. I couldn't
figure out a
python-imaging version 1.1.7-4build1 which used to be available in
raring does not have this issue.
** Changed in: python-imaging (Ubuntu)
Status: Confirmed = Triaged
** Changed in: python-imaging (Ubuntu)
Assignee: (unassigned) = Matthias Klose (doko)
** Also affects:
as a long-term solution, every rdepends should be patched as:
try:
from PIL import Image
except ImportError:
import Image
as a midterm solution, maybe ship a python-imaging-compat which holds
the .pth file
as short-term, maybe let python-imaging depend on python-imaging-compat.
The list of
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: phatch (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
The comic reader Comix (installed from software centre) fails to start
(silently!) because of this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
python-imaging broken in raring
To
phatch is broken too
** Changed in: python-imaging (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
python-imaging broken in raring
To manage
** Also affects: gwibber (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
python-imaging broken in raring
To manage notifications
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gwibber (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
Gnome15 is now completely broken as well and fails to start.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
python-imaging broken in raring
To manage notifications about this bug go
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: python-imaging (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Effects me in Gwibber.
Traceback (most recent call last):
File /usr/bin/gwibber-service, line 55, in module
from gwibber.microblog.util.log import setup_logging
File /usr/lib/python2.7/dist-packages/gwibber/microblog/util/__init__.py,
line 2, in module
from gwibber.microblog.util
60 matches
Mail list logo
