Bug#656599: default-jdk: Java JDK not installable on squeeze

2012-01-20 Thread Jörg Kurlbaum
Package: default-jdk
Severity: important

On my very basic squeeze installation default-jdk and other java packages are
not installable due to dependecy problems. The packages openjdk-6-jdk is also 
not installable

Output:

root@fff:~# LANG=C apt-get install openjdk-6-jdk
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 openjdk-6-jdk : Depends: openjdk-6-jre (>= 6b18-1.8.10-0+squeeze2) but it is 
not going to be installed
E: Broken packages

I suspect some misconfiguration of apt. But could not find any hints


-- System Information:
Debian Release: 6.0.3
  APT prefers stable
  APT policy: (990, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- 
Jörg Kurlbaum (joerg.kurlb...@neuland-bfi.de)  neuland:::Büro für Informatik
GPG-ID: 10FDA31F   Konsul-Smidt Str. 8g
T: 0421/380107-55  28217 Bremen



--
To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20120120113028.14187.19424.reportbug@hybris-app-live1



Bug#656599: default-jdk: Java JDK not installable on squeeze

2012-01-20 Thread Xerxes Rånby
2012-01-20 12:34, Jörg Kurlbaum skrev:
> Package: default-jdk
> Severity: important
> 
> On my very basic squeeze installation default-jdk and other java packages are
> not installable due to dependecy problems. The packages openjdk-6-jdk is also 
> not installable
> 
> Output:
> 
> root@fff:~# LANG=C apt-get install openjdk-6-jdk
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  openjdk-6-jdk : Depends: openjdk-6-jre (>= 6b18-1.8.10-0+squeeze2) but it is 
> not going to be installed
> E: Broken packages

6b18-1.8.10-0+squeeze2 are currently found in the Debian security repository.
http://security.debian.org/debian-security/pool/updates/main/o/openjdk-6/

> 
> I suspect some misconfiguration of apt. But could not find any hints

try add
deb http://security.debian.org/ squeeze/updates main contrib non-free
to /etc/apt/sources.list

and then re-run
apt-get update
apt-get install openjdk-6-jdk

Cheers
Xerxes



--
To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f195d18.6000...@zafena.se



Re: maven packaging

2012-01-20 Thread Boris Ribalkin
Hi,

One more question on mh_make.
I am trying to package google-http-client (
https://google-http-java-client.googlecode.com/hg/google-http-client/pom.xml)
which depends on com.google.code.gson (
http://google-gson.googlecode.com/svn/tags/gson-2.1/). So I packaged gson
first and it was fine, but when I run mh_make on google-http-client it says
the following:

This dependency cannot be found in the Debian Maven repository. Ignore this
> dependency?
>   com.google.code.gson:gson:jar:null
> y/[n] >
> > dpkg --search /usr/share/maven-repo/com/google/code/gson/gson
> *Found libgson-java*
> > dpkg --status libgson-java
> [error] Package libgson-java (2.1-1) is already installed and contains a
> possible match,
> but I cannot resolve library com.google.code.gson:gson:jar:*null* in it.
> [error] Please check manually that the library is up to date, otherwise it
> may be necessary to package version null in Debian.
> Try again to resolve the dependency?
> [y]/n >
> Rescanning /usr/share/maven-repo...
> Resolving com.google.code.gson:gson:jar:null of scope runtime...
> In pom.xml, cannot find the version for dependency
> com.google.code.gson:gson:jar:null from this POM or its parent POMs
> [warning] Option --no-parent has been set for POM file pom.xml, maybe it
> was not a good idea and you should first package the parent POM
> __super__:__pom__:pom:null
> [check dependency with bundle type]
> > dpkg --status libgson-java
> [error] Package libgson-java (2.1-1) is already installed and contains a
> possible match,
> but I cannot resolve library com.google.code.gson:gson:jar:null in it.
> [error] Please check manually that the library is up to date, otherwise it
> may be necessary to package version null in Debian.
> Try again to resolve the dependency?
> [y]/n >
>

Is this because dependency has no version, but how then junit dependency is
found if it has no version as well?
What is the proper way of fixing this?

Thanks.

On Thu, Dec 8, 2011 at 9:17 PM, Boris Ribalkin  wrote:

> Hi Ludovic,
>
> Actually I am the owner of the ucloud project on github :) so I can make
> any changes you suggested. Wil let you know if it will work.
>
> Thanks!
> On Dec 8, 2011 4:58 PM, "Ludovic Claude" 
> wrote:
>
>> Hello Boris,
>>
>> It looks like you are almost there. Your project is hosted on Github,
>> but I don't support yet Git, so the debian/watch used to find the latest
>> version and get the upstream code is not generated by mh_make.
>>
>> However there are lots of other packages which get their sources from
>> Github (basex, plexus-cipher, junit4, libjdom1-java), so you can study
>> their packaging using apt-get source .
>>
>> This watch file should in theory get the latest release of uCloud,
>> expect that it does not...
>>
>> cat < debian/watch
>> version=3
>> http://githubredir.debian.net/github/cyberb/uCloud/ (.*).tar.gz
>> EOF
>>
>> You should ask the project owner to tag in Git the latest release,
>> otherwise it's not possible to know what to download. Or better, he
>> should use maven-release-plugin to create a release of the project.
>>
>> After you get this detail sorted, then you should add those lines to
>> debian/rules:
>>
>> get-orig-source:
>>uscan --download-version $(DEB_UPSTREAM_VERSION)
>> --force-download --rename
>>
>> Finally, if you work on Ubuntu and use Launchpad, then you should store
>> your packaging in bzr:
>>
>> sudo apt-get install bzr-builddeb
>> bzr init
>> mkdir .bzr-builddeb/
>> echo -e '[BUILDDEB]\nmerge = True' > .bzr-builddeb/default.conf
>> bzr add .
>>
>> and you can build your package with
>>
>> bzr bd
>>
>> Well that's the usual procedure. In your case, since it's difficult to
>> get the upstream sources, you need to download  them yourself and put
>> them in a tar.gz file which you should call ucloud_1.0.0.orig.tar.gz and
>> copy it in the parent directory. Doing so will make bzr bd / debuild
>> happy since they don't have to download the sources.
>>
>> Consider also joining the Debian Java team, as it's full of active and
>> knowledgable developers (http://wiki.debian.org/Teams/JavaPackaging).
>> Once your package is ready, you can ask to include it in Debian and it
>> will land some time later into Ubuntu.
>>
>> Cheers,
>> Ludovic
>>
>> On 08/12/2011 07:31, Boris Ribalkin wrote:
>> > Hi,
>> >
>> > Thanks for the info, your new package is much better.
>> > After running mh_make in the root of my project, looks like everything
>> > went fine, just one exception at the end:
>> >
>> >> Cannot recognize the download url
>> > (scm:git:https://github.com/cyberb/uCloud.git).
>> > I've tried different scm urls, but it is always the same, is it OK?
>> >
>> > than I ran debuild and got the following error:
>> >
>> >> This package has a Debian revision number but there does not seem to be
>> > an appropriate original tar file or .orig directory in the parent
>> directory;
>> > (expected one of ucloud_1.0.0.orig.tar.gz, ucloud_1.0.0.orig.tar.bz2,
>> > ucloud_1.0.0.orig.tar.lzma,  uclou