[needs-packaging] Add Java DB packages for Hardy

Bug #188962 reported by Lars Heill
10
Affects Status Importance Assigned to Milestone
Ubuntu
Fix Released
Wishlist
Lars Heill

Bug Description

Requesting the addition of Java DB packages for Hardy:

  * Package names (6): sun-javadb-*
  * License: Apache 2.0
  * Source: http://revu.tauware.de/details.py?package=sun-javadb

See also: https://bugs.launchpad.net/bugs/192887

Revision history for this message
Daniel Holbach (dholbach) wrote :

- debian/changelog:
 - 10.3.2.1-1 -> 10.3.2.1-0ubuntu1
 - "Closes: #188962" -> (LP: #188962)
- debian/control
 - Should sun-javadb-client be in section: libs and sun-javadb-common in docs?
 - You can use the new Homepage: field in the source stanza instead of "For more information see http://developers.sun.com/javadb/"
- debian/{postinst,prerm is nearly empty, could be dropped

Build fails in a chroot:
unzip javadb-10_3_2_1.zip -d build-tree
make: unzip: Command not found
make: *** [debian/stamp-javadb-10_3_2_1.zip] Error 127
dpkg-buildpackage: failure: debian/rules build gave error exit status 2

Seems that unzip is needed as a Build-Depends

Revision history for this message
Lars Heill (heill) wrote : Re: [Bug 188962] Re: [needs-packaging] Add Java DB packages for Hardy

Daniel Holbach wrote, On 02/05/08 08:33:
> - debian/changelog:
> - 10.3.2.1-1 -> 10.3.2.1-0ubuntu1
> - "Closes: #188962" -> (LP: #188962)
> - debian/control
> - Should sun-javadb-client be in section: libs and sun-javadb-common in docs?
> - You can use the new Homepage: field in the source stanza instead of "For more information see http://developers.sun.com/javadb/"
> - debian/{postinst,prerm is nearly empty, could be dropped
>
> Build fails in a chroot:
> unzip javadb-10_3_2_1.zip -d build-tree
> make: unzip: Command not found
> make: *** [debian/stamp-javadb-10_3_2_1.zip] Error 127
> dpkg-buildpackage: failure: debian/rules build gave error exit status 2
>
> Seems that unzip is needed as a Build-Depends

Hi Daniel,

Thanks so much for doing an initial review before REVU.

I have made adjustments as suggested.

Tried building with pbuilder under --distribution=hardy, but ran into
noise with "debian-changelog-file-is-a-symlink". Found a discussion
on this here: http://irclogs.ubuntu.com/2007/11/21/%23ubuntu-motu.txt.
Not sure I agree with the new behaviour when changelog etc are symlinked
into dependant packages... Anyway, it seems working on gutsy and
pbuilding on hardy is not trivial...

I have tried to upload my last attempt to REVU, but some strange local
network issue will not let dput through to revu.tauware.de from my
gutsy host. Will ask my friendly lab eng to fix the network issue and
upload to REVU as soon as possible.

If you should have the cycles to have a look at my last attempt still on
http://dbtg.thresher.com/derby/bits/ubuntu/, I'd very much appreciate it.

Thanks!

Revision history for this message
Daniel Holbach (dholbach) wrote :

debian-changelog-file-is-a-symlink is a CDBS bug I believe and only a warning, so nothing to worry about. Pbuilder shouldn't fail building it because of that.

If all fails, try to upload to PPA: http://help.launchpad.net/PPAQuickStart - your page is fine too.

Review:
 - try to make it non-native (have a sun-javadb_10.3.2.1.orig.tar.gz + .diff.gz (with all the debian/ bits) and .dsc)
 - "The deprecated frameworks software is not included" (in debian/README.Debian) could be a bit more verbose. Also adding that information to debian/copyright would not hurt.
 - Make it Standards-Version 3.7.3 to comply with the newest policy version.
 - usr/share/javadb/demo/programs/localcal/lib/ seems to be an empty directory
 - please adhere to http://wiki.ubuntu.com/DebianMaintainerField

Revision history for this message
Lars Heill (heill) wrote :

Daniel Holbach wrote, On 02/06/08 11:14:
> debian-changelog-file-is-a-symlink is a CDBS bug I believe and only a
> warning, so nothing to worry about. Pbuilder shouldn't fail building it
> because of that.
>
> If all fails, try to upload to PPA:
> http://help.launchpad.net/PPAQuickStart - your page is fine too.
>
> Review:
> - try to make it non-native (have a sun-javadb_10.3.2.1.orig.tar.gz + .diff.gz (with all the debian/ bits) and .dsc)
> - "The deprecated frameworks software is not included" (in debian/README.Debian) could be a bit more verbose. Also adding that information to debian/copyright would not hurt.
> - Make it Standards-Version 3.7.3 to comply with the newest policy version.
> - usr/share/javadb/demo/programs/localcal/lib/ seems to be an empty directory
> - please adhere to http://wiki.ubuntu.com/DebianMaintainerField

Stepping into a mess getting confused when trying to make it non-native:

1. CDBS tarball would like a tarball in sun-javadb-10.3.2.1, without it
    I am not suprised to get stuff like

 dh_install -psun-javadb-client build-tree/javadb/lib/derbyclient.jar usr/share/javadb/lib
 cp: cannot stat `./build-tree/javadb/lib/derbyclient.jar': No such file or directory

2. With a copy of sun-javadb_10.3.2.1.orig.tar.gz in sun-javadb-10.3.2.1,
    I get

 dpkg-source: warning: unknown information field 'Homepage' in input data in general section of control info file
 dpkg-source: warning: Version number suggests Ubuntu changes, but there is no XSBC-Original-Maintainer field
 dpkg-source: building sun-javadb using existing sun-javadb_10.3.2.1.orig.tar.gz
 dpkg-source: building sun-javadb in sun-javadb_10.3.2.1-0ubuntu1.diff.gz
 dpkg-source: warning: newly created empty file 'sun-javadb_10.3.2.1.orig.tar.gz.cdbs-config_list' will not be represented in diff

    and then:

 dpkg-source: cannot represent change to sun-javadb_10.3.2.1.orig.tar.gz: binary file contents changed
 dpkg-source: warning: ignoring deletion of file CHANGES.html
 dpkg-source: warning: ignoring deletion of file RELEASE-NOTES.html
 ...
 dpkg-source: warning: ignoring deletion of file docs/pdf/ref/refderby.pdf
 dpkg-source: building sun-javadb in sun-javadb_10.3.2.1-0ubuntu1.dsc
 dpkg-source: unrepresentable changes to source

    booom!

With pbuilder I run into this one, regardless:

 dh_install -psun-javadb-client build-tree/javadb/lib/derbyclient.jar usr/share/javadb/lib
 cp: cannot stat `./build-tree/javadb/lib/derbyclient.jar': No such file or directory

with orig.tar.gz, dsc and diff.gz in place.

There must be some fundamental I have missed, - tried googling, and all FAQs and guides I know of...

Any pointers?

Thanks,
Lars

Revision history for this message
Lars Heill (heill) wrote :
Download full text (4.0 KiB)

Lars Heill wrote, On 02/06/08 18:20:
> Daniel Holbach wrote, On 02/06/08 11:14:
>> debian-changelog-file-is-a-symlink is a CDBS bug I believe and only a
>> warning, so nothing to worry about. Pbuilder shouldn't fail building it
>> because of that.
>>
>> If all fails, try to upload to PPA:
>> http://help.launchpad.net/PPAQuickStart - your page is fine too.
>>
>> Review: - try to make it non-native (have a
>> sun-javadb_10.3.2.1.orig.tar.gz + .diff.gz (with all the debian/ bits)
>> and .dsc)
>> - "The deprecated frameworks software is not included" (in
>> debian/README.Debian) could be a bit more verbose. Also adding that
>> information to debian/copyright would not hurt.
>> - Make it Standards-Version 3.7.3 to comply with the newest policy
>> version.
>> - usr/share/javadb/demo/programs/localcal/lib/ seems to be an empty
>> directory
>> - please adhere to http://wiki.ubuntu.com/DebianMaintainerField
>
> Stepping into a mess getting confused when trying to make it non-native:
>
> 1. CDBS tarball would like a tarball in sun-javadb-10.3.2.1, without it
> I am not suprised to get stuff like
>
> dh_install -psun-javadb-client
> build-tree/javadb/lib/derbyclient.jar usr/share/javadb/lib
> cp: cannot stat `./build-tree/javadb/lib/derbyclient.jar': No such
> file or directory
>
> 2. With a copy of sun-javadb_10.3.2.1.orig.tar.gz in sun-javadb-10.3.2.1,
> I get
>
> dpkg-source: warning: unknown information field 'Homepage' in input
> data in general section of control info file
> dpkg-source: warning: Version number suggests Ubuntu changes, but
> there is no XSBC-Original-Maintainer field
> dpkg-source: building sun-javadb using existing
> sun-javadb_10.3.2.1.orig.tar.gz
> dpkg-source: building sun-javadb in
> sun-javadb_10.3.2.1-0ubuntu1.diff.gz
> dpkg-source: warning: newly created empty file
> 'sun-javadb_10.3.2.1.orig.tar.gz.cdbs-config_list' will not be
> represented in diff
>
> and then:
>
> dpkg-source: cannot represent change to
> sun-javadb_10.3.2.1.orig.tar.gz: binary file contents changed
> dpkg-source: warning: ignoring deletion of file CHANGES.html
> dpkg-source: warning: ignoring deletion of file RELEASE-NOTES.html
> ...
> dpkg-source: warning: ignoring deletion of file
> docs/pdf/ref/refderby.pdf
> dpkg-source: building sun-javadb in sun-javadb_10.3.2.1-0ubuntu1.dsc
> dpkg-source: unrepresentable changes to source
>
> booom!
>
> With pbuilder I run into this one, regardless:
>
> dh_install -psun-javadb-client
> build-tree/javadb/lib/derbyclient.jar usr/share/javadb/lib
> cp: cannot stat `./build-tree/javadb/lib/derbyclient.jar': No such
> file or directory
>
> with orig.tar.gz, dsc and diff.gz in place.
>
> There must be some fundamental I have missed, - tried googling, and all
> FAQs and guides I know of...

Silly me forgot a 'cd'...

Have updated Source link with new packages. Changes:

   * non-native
   * no longer unzip build dependency
   * put "frameworks" back in for consistency across platforms for Java DB
     ==> get "W: sun-javadb-core: executable-not-elf-or-script" for .ksh
         files under frameworks. Yes,...

Read more...

Revision history for this message
Lars Heill (heill) wrote :
Download full text (4.2 KiB)

Lars Heill wrote, On 02/07/08 15:18:
> Lars Heill wrote, On 02/06/08 18:20:
>> Daniel Holbach wrote, On 02/06/08 11:14:
>>> debian-changelog-file-is-a-symlink is a CDBS bug I believe and only a
>>> warning, so nothing to worry about. Pbuilder shouldn't fail building it
>>> because of that.
>>>
>>> If all fails, try to upload to PPA:
>>> http://help.launchpad.net/PPAQuickStart - your page is fine too.
>>>
>>> Review: - try to make it non-native (have a
>>> sun-javadb_10.3.2.1.orig.tar.gz + .diff.gz (with all the debian/
>>> bits) and .dsc)
>>> - "The deprecated frameworks software is not included" (in
>>> debian/README.Debian) could be a bit more verbose. Also adding that
>>> information to debian/copyright would not hurt.
>>> - Make it Standards-Version 3.7.3 to comply with the newest policy
>>> version.
>>> - usr/share/javadb/demo/programs/localcal/lib/ seems to be an empty
>>> directory
>>> - please adhere to http://wiki.ubuntu.com/DebianMaintainerField
>>
>> Stepping into a mess getting confused when trying to make it non-native:
>>
>> 1. CDBS tarball would like a tarball in sun-javadb-10.3.2.1, without it
>> I am not suprised to get stuff like
>>
>> dh_install -psun-javadb-client
>> build-tree/javadb/lib/derbyclient.jar usr/share/javadb/lib
>> cp: cannot stat `./build-tree/javadb/lib/derbyclient.jar': No such
>> file or directory
>>
>> 2. With a copy of sun-javadb_10.3.2.1.orig.tar.gz in sun-javadb-10.3.2.1,
>> I get
>>
>> dpkg-source: warning: unknown information field 'Homepage' in
>> input data in general section of control info file
>> dpkg-source: warning: Version number suggests Ubuntu changes, but
>> there is no XSBC-Original-Maintainer field
>> dpkg-source: building sun-javadb using existing
>> sun-javadb_10.3.2.1.orig.tar.gz
>> dpkg-source: building sun-javadb in
>> sun-javadb_10.3.2.1-0ubuntu1.diff.gz
>> dpkg-source: warning: newly created empty file
>> 'sun-javadb_10.3.2.1.orig.tar.gz.cdbs-config_list' will not be
>> represented in diff
>>
>> and then:
>>
>> dpkg-source: cannot represent change to
>> sun-javadb_10.3.2.1.orig.tar.gz: binary file contents changed
>> dpkg-source: warning: ignoring deletion of file CHANGES.html
>> dpkg-source: warning: ignoring deletion of file RELEASE-NOTES.html
>> ...
>> dpkg-source: warning: ignoring deletion of file
>> docs/pdf/ref/refderby.pdf
>> dpkg-source: building sun-javadb in sun-javadb_10.3.2.1-0ubuntu1.dsc
>> dpkg-source: unrepresentable changes to source
>>
>> booom!
>>
>> With pbuilder I run into this one, regardless:
>>
>> dh_install -psun-javadb-client
>> build-tree/javadb/lib/derbyclient.jar usr/share/javadb/lib
>> cp: cannot stat `./build-tree/javadb/lib/derbyclient.jar': No such
>> file or directory
>>
>> with orig.tar.gz, dsc and diff.gz in place.
>>
>> There must be some fundamental I have missed, - tried googling, and
>> all FAQs and guides I know of...
>
> Silly me forgot a 'cd'...
>
> Have updated Source link with new packages. Changes:
>
> * non-native
> * no longer unzip build dependency
> * put "frameworks" back in for consistency across platforms for Java DB
>...

Read more...

Revision history for this message
Daniel Holbach (dholbach) wrote :

Sorry for the confusion. Forget what I wrote about the native package.

Revision history for this message
Lars Heill (heill) wrote :
Download full text (4.4 KiB)

Lars Heill wrote, On 02/07/08 15:27:
> Lars Heill wrote, On 02/07/08 15:18:
>> Lars Heill wrote, On 02/06/08 18:20:
>>> Daniel Holbach wrote, On 02/06/08 11:14:
>>>> debian-changelog-file-is-a-symlink is a CDBS bug I believe and only a
>>>> warning, so nothing to worry about. Pbuilder shouldn't fail building it
>>>> because of that.
>>>>
>>>> If all fails, try to upload to PPA:
>>>> http://help.launchpad.net/PPAQuickStart - your page is fine too.
>>>>
>>>> Review: - try to make it non-native (have a
>>>> sun-javadb_10.3.2.1.orig.tar.gz + .diff.gz (with all the debian/
>>>> bits) and .dsc)
>>>> - "The deprecated frameworks software is not included" (in
>>>> debian/README.Debian) could be a bit more verbose. Also adding that
>>>> information to debian/copyright would not hurt.
>>>> - Make it Standards-Version 3.7.3 to comply with the newest policy
>>>> version.
>>>> - usr/share/javadb/demo/programs/localcal/lib/ seems to be an empty
>>>> directory
>>>> - please adhere to http://wiki.ubuntu.com/DebianMaintainerField
>>>
>>> Stepping into a mess getting confused when trying to make it non-native:
>>>
>>> 1. CDBS tarball would like a tarball in sun-javadb-10.3.2.1, without it
>>> I am not suprised to get stuff like
>>>
>>> dh_install -psun-javadb-client
>>> build-tree/javadb/lib/derbyclient.jar usr/share/javadb/lib
>>> cp: cannot stat `./build-tree/javadb/lib/derbyclient.jar': No
>>> such file or directory
>>>
>>> 2. With a copy of sun-javadb_10.3.2.1.orig.tar.gz in
>>> sun-javadb-10.3.2.1,
>>> I get
>>>
>>> dpkg-source: warning: unknown information field 'Homepage' in
>>> input data in general section of control info file
>>> dpkg-source: warning: Version number suggests Ubuntu changes, but
>>> there is no XSBC-Original-Maintainer field
>>> dpkg-source: building sun-javadb using existing
>>> sun-javadb_10.3.2.1.orig.tar.gz
>>> dpkg-source: building sun-javadb in
>>> sun-javadb_10.3.2.1-0ubuntu1.diff.gz
>>> dpkg-source: warning: newly created empty file
>>> 'sun-javadb_10.3.2.1.orig.tar.gz.cdbs-config_list' will not be
>>> represented in diff
>>>
>>> and then:
>>>
>>> dpkg-source: cannot represent change to
>>> sun-javadb_10.3.2.1.orig.tar.gz: binary file contents changed
>>> dpkg-source: warning: ignoring deletion of file CHANGES.html
>>> dpkg-source: warning: ignoring deletion of file RELEASE-NOTES.html
>>> ...
>>> dpkg-source: warning: ignoring deletion of file
>>> docs/pdf/ref/refderby.pdf
>>> dpkg-source: building sun-javadb in sun-javadb_10.3.2.1-0ubuntu1.dsc
>>> dpkg-source: unrepresentable changes to source
>>>
>>> booom!
>>>
>>> With pbuilder I run into this one, regardless:
>>>
>>> dh_install -psun-javadb-client
>>> build-tree/javadb/lib/derbyclient.jar usr/share/javadb/lib
>>> cp: cannot stat `./build-tree/javadb/lib/derbyclient.jar': No
>>> such file or directory
>>>
>>> with orig.tar.gz, dsc and diff.gz in place.
>>>
>>> There must be some fundamental I have missed, - tried googling, and
>>> all FAQs and guides I know of...
>>
>> Silly me forgot a 'cd'...
>>
>> Have updated Source link with new packages. Changes:
>>
>> * non-nativ...

Read more...

Revision history for this message
Lars Heill (heill) wrote :

Daniel Holbach wrote, On 02/07/08 16:11:
> Sorry for the confusion. Forget what I wrote about the native package.

Thanks for all your kind help, Daniel!

I have just completed a new set of packages that lintian (hardy) sanctions.
The are still at http://dbtg.thresher.com/derby/bits/ubuntu/, if you could
have a look.

Cheers,
Lars

Revision history for this message
Lars Heill (heill) wrote : Package on REVU
Lars Heill (heill)
description: updated
Revision history for this message
Lars Heill (heill) wrote :
Revision history for this message
Gerardo Curiel (gcuriel-deactivatedaccount) wrote :

I can see that another package, sun-java6-javadb is already in hardy, it's bundled with the sun-java6 package, please see http://packages.ubuntu.com/hardy/devel/sun-java6-javadb for more information.

I can't see any difference between sun-javadb and sun-java6-javadb. Is it meant to be a javadb backport to java5 or something?

Thanks for your work.

Revision history for this message
Lars Heill (heill) wrote :

sun-java6-javadb has version 10.2.2 of Java DB. sun-java6 is based on the DLJ tarball bundle of Sun's JDK 6 which contained Java DB in a db/ subdirectory. Packaged versions of Java 6 include the original Java DB product packages, which for debian/ubuntu would be the proposed sun-javadb packages which contains the latest release of Java DB: 10.3. The sun-java6-javadb package does not appear to have been updated in pace with Sun's JDK 6 which currently co-package Java DB 10.3.

Ideally, sun-javadb should replace/obsolete sun-java6-javadb.

Java DB currently supports Java SE 1.4.x, 5 and 6 (and has been tested on iced tea <~ 7).

Please see https://bugs.launchpad.net/bugs/192887 for more details/background.

description: updated
Revision history for this message
Lars Heill (heill) wrote :

Updated package on REVU.

Revision history for this message
Lars Heill (heill) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

sun-javadb accepted from source NEW into hardy.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.