I am trying to use pbuilder but it keeps failing with this error:
The following packages will be REMOVED:
liblzma1{u}
The following partially installed packages will be configured:
pbuilder-satisfydepends-dummy
0 packages upgraded, 377 newly installed, 1 to remove and 0 not upgraded.
Need to get 281MB of archives. After unpacking 888MB will be used.
The following packages have unmet dependencies:
gcj-jre-headless: Conflicts: java-gcj-compat-headless (< 1.0.80-6)
but 1.0.80-5.1 is to be installed.
libjpeg8-dev: Conflicts: libjpeg62-dev but 6b-16 is to be installed.
The following actions will resolve these dependencies:
Remove the following packages:
1) pbuilder-satisfydepends-dummy
Keep the following packages at their current version:
2) java-gcj-compat [Not Installed]
3) java-gcj-compat-headless [Not Installed]
4) libjpeg62-dev [Not Installed]
5) libtiff4-dev [Not Installed]
6) libvtk5-dev [Not Installed]
Tier: Safe actions, Remove packages (10000)
Does anyone knows what I need to do to make it work again ?
Thanks
--
Mathieu
--
To UNSUBSCRIBE, email to debian-ment...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
> I am trying to use pbuilder but it keeps failing with this error:
>
>
> The following packages will be REMOVED:
> liblzma1{u}
> The following partially installed packages will be configured:
> pbuilder-satisfydepends-dummy
> 0 packages upgraded, 377 newly installed, 1 to remove and 0 not upgraded.
> Need to get 281MB of archives. After unpacking 888MB will be used.
> The following packages have unmet dependencies:
> gcj-jre-headless: Conflicts: java-gcj-compat-headless (< 1.0.80-6)
> but 1.0.80-5.1 is to be installed.
This looks like you've been hit by bug #566514�.
> libjpeg8-dev: Conflicts: libjpeg62-dev but 6b-16 is to be installed.
This might be because your package build-depends on both libjpeg-dev
(which is now provided by libjpeg8-dev) and libjpeg62-dev (pulled in by
some other package). Try to find out which package pulls in
libjpeg62-dev.
Sven
� http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566514
On Mon, Feb 8, 2010 at 1:17 PM, Sven Joachim <sven...@gmx.de> wrote:
>> gcj-jre-headless: Conflicts: java-gcj-compat-headless (< 1.0.80-6)
>> but 1.0.80-5.1 is to be installed.
>
> This looks like you've been hit by bug #566514น.
So I guess I have to wait a couple of days for this one.
>> libjpeg8-dev: Conflicts: libjpeg62-dev but 6b-16 is to be installed.
>
> This might be because your package build-depends on both libjpeg-dev
> (which is now provided by libjpeg8-dev) and libjpeg62-dev (pulled in by
> some other package). Try to find out which package pulls in
> libjpeg62-dev.
This is weird. I think this may be caused by libvtk-java:
$ apt-cache depends libvtk-java | grep jpeg
Depends: libjpeg62
However the Build-Dep seems alright:
http://patch-tracker.debian.org/patch/debianonly/view/vtk/5.4.2-4
...
+Build-Depends: debhelper (>= 7), libgl1-mesa-dev | libgl-dev,
libglu1-mesa-dev | libglu-dev, libosmesa6-dev,
+ libx11-dev, libxt-dev, xvfb, x11proto-core-dev, tcl8.5-dev,
tk8.5-dev, python-dev, cmake (>> 2.4),
+ libexpat-dev, libjpeg-dev, libpng-dev, libtiff-dev, zlib1g-dev, default-jdk,
...
Any suggestions ?
Thanks
--
Mathieu
ref:
http://packages.debian.org/sid/libvtk-java
Hi Mathieu,
libjpeg8-dev does not provide libjpeg-dev…
Have a nice day,
--
Charles Plessy
Debian Med packaging team,
http://www.debian.org/devel/debian-med
Tsurumi, Kanagawa, Japan
> This is weird. I think this may be caused by libvtk-java:
>
> $ apt-cache depends libvtk-java | grep jpeg
> Depends: libjpeg62
>
> However the Build-Dep seems alright:
>
> http://patch-tracker.debian.org/patch/debianonly/view/vtk/5.4.2-4
>
> ...
> +Build-Depends: debhelper (>= 7), libgl1-mesa-dev | libgl-dev,
> libglu1-mesa-dev | libglu-dev, libosmesa6-dev,
> + libx11-dev, libxt-dev, xvfb, x11proto-core-dev, tcl8.5-dev,
> tk8.5-dev, python-dev, cmake (>> 2.4),
> + libexpat-dev, libjpeg-dev, libpng-dev, libtiff-dev, zlib1g-dev, default-jdk,
> ...
>
> Any suggestions ?
Which package are you trying to build?
Sven
> libjpeg8-dev does not provide libjpeg-dev…
The latest version (8-2) does.
Sven
http://packages.qa.debian.org/g/gdcm.html
I have some changes I'd like to test before upload. If anyone is interested:
svn co svn.debian.org/svn/debian-med/trunk/packages/gdcm/trunk
cheers
--
Mathieu
So Matthieu only has to wait for version 8-2 to propagate to his favorite
mirror…
Have a nice day,
--
Charles Plessy
Tsurumi, Kanagawa, Japan
> Le Mon, Feb 08, 2010 at 02:28:38PM +0100, Sven Joachim a écrit :
>> On 2010-02-08 14:25 +0100, Charles Plessy wrote:
>>
>> > libjpeg8-dev does not provide libjpeg-dev…
>>
>> The latest version (8-2) does.
>
> So Matthieu only has to wait for version 8-2 to propagate to his favorite
> mirror…
Um, I think you're wrong. Most likely his problem is that it has
already propagated -- this transition is responsible for the conflict
between libjpeg-dev and libjpeg62-dev.
Sven
Sorry I do not understand that part. Can I work around bug #566514 ?
Can I work around the libjpeg8 / libjpeg62 issue ?
Thanks
--
Mathieu
> On Mon, Feb 8, 2010 at 4:06 PM, Sven Joachim <sven...@gmx.de> wrote:
>> On 2010-02-08 15:43 +0100, Charles Plessy wrote:
>>
>>> Le Mon, Feb 08, 2010 at 02:28:38PM +0100, Sven Joachim a écrit :
>>>> On 2010-02-08 14:25 +0100, Charles Plessy wrote:
>>>>
>>>> > libjpeg8-dev does not provide libjpeg-dev…
>>>>
>>>> The latest version (8-2) does.
>>>
>>> So Matthieu only has to wait for version 8-2 to propagate to his favorite
>>> mirror…
>>
>> Um, I think you're wrong. Most likely his problem is that it has
>> already propagated -- this transition is responsible for the conflict
>> between libjpeg-dev and libjpeg62-dev.
>
> Sorry I do not understand that part.
What I mean is that since the latest libjpeg8 upload libjpeg-dev and
libjpeg62-dev are now provided by different packages, and they
conflict. Before that, libjpeg62-dev used to provide libjpeg-dev.
> Can I work around bug #566514 ?
> Can I work around the libjpeg8 / libjpeg62 issue ?
You can switch the build dependency of your package to libjpeg-dev, but
I think you had already done this before you asked. And you could try
to install sbuild and see if you can build your package with that.
If sbuild also gets unresolvable conflicts, there is probably not much
point in uploading anyway, because the buildds will not be able to build
your package either for the time being.
You can also ask the Debian GCC maintainers if they have plans to remove
the java-gcj-compat package from unstable to resolve #566514.
Sven
I get the same problem trying to build the latest version of Qt (4.6.1
upstream + packaging files from pkg-kde's git repository).
Qt build-deps include libgtk2.0-dev and libjpeg-dev.
According to "aptitude why" inside the pbuilder chroot:
libgtk2.0-dev Depends libcairo2-dev (>= 1.6.4-6.1)
libcairo2-dev Depends libdirectfb-dev (>= 0.9.25)
libdirectfb-dev Depends libjpeg62-dev
--
Nicolas
(I read mailing lists through Gmane. Please don't Cc me on replies; it makes
me get one message on my newsreader and another on email.)