Re: planning (a) hsqldb transition(s)

2013-05-07 Thread Rene Engelhard
Hi,

On Thu, Apr 25, 2013 at 11:22:05PM +0200, Rene Engelhard wrote:
 openjpa failed to build (see #706176)
[...]
 Will upload the new version after wheezy release[1] as announced in
 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670902#17

Done.

Regards,
 
Rene

__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. 
Please use
debian-j...@lists.debian.org for discussions and questions.


Re: planning (a) hsqldb transition(s)

2013-04-25 Thread Rene Engelhard
block 670902 by 706176
thanks

Hi,

since the release is next week I did a testbuild of the r-deps -
except hsqldb itself of course :-) - now (in a clean sid chroot +
libhsqldb-java from experimental pre-installed):

$ grep-available -FDepends libhsqldb-java -sPackagePackage: hsqldb-server
Package: eucalyptus-java-common
Package: libbiojava1.7-java
Package: libbiojava3.0-java
Package: entagged
Package: libreoffice-base
Package: libopenjpa-java
Package: hsqldb-utils
Package: pixelmed-java
Package: biomaj
Package: paros

openjpa failed to build (see #706176)

The rest did build - so it actually isn't as as bad as I
feared (that of course doesn't say whether it needs other steps to work
like upgrade/re-create whatever db file, but... - at least the biojavas
ran tests which worked, too)

Will upload the new version after wheezy release[1] as announced in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670902#17

Regards,

Rene

[1] together with LO to make that one not uninstallable

__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. 
Please use
debian-j...@lists.debian.org for discussions and questions.


Processed: Re: planning (a) hsqldb transition(s)

2013-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 block 670902 by 706176
Bug #670902 [release.debian.org] transition: hsqldb
670902 was not blocked by any bugs.
670902 was not blocking any bugs.
Added blocking bug(s) of 670902: 706176
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
670902: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670902
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. 
Please use
debian-j...@lists.debian.org for discussions and questions.


Re: planning (a) hsqldb transition(s)

2013-02-11 Thread Rene Engelhard
Hi,

On Mon, Jan 07, 2013 at 11:09:41AM +0100, Rene Engelhard wrote:
  Or is this silent agreement? 
  (If so then please do not complain if a upgrade of libhsqldb-java from 
  1.8.0.10 to
  libhsqldb-java 2.2.8 breaks anything - you had advance warning.
 
 This is the LAST ping. When there will be no reply (well, -med and
 Sebastien[1] answered, this targets -java..) I *will* take this as a
 silent agreement and do it immediately when the freeze ends
 (and libreoffice will directly switch to libhsqldb1.8.0-java).

Quoting IRC with Niels (2013-01-07):

11:01 _rene_ ping?
11:06 nthykier yes
11:06 _rene_ http://lists.debian.org/debian-openoffice/2012/04/msg00227.html 
   etc
11:07 _rene_ no pkg-java answer since February 2011
11:07 _rene_ I will send a last ping and if there's no reply just do it(tm) 
   once we unfreeze
11:07 _rene_ see also 
http://packages.qa.debian.org/h/hsqldb/news/20130107T011735Z.html and 
   http://ftp-master.debian.org/new/hsqldb1.8.0_1.8.0.10-15.html
11:08 _rene_ will also send a mail ping
11:09 _rene_ but here jfyi ;)
11:09 nthykier perhaps not the day we unfreeze, but yeah - I think silence 
 is acceptance is a good approach for the Java team atm, which 
 is generally not very active anymore
11:10 _rene_ mail sent

Nothing happened by now, so I *will* take this as silent consensus and
not ask any further. Will upload the new hsqldb after the freeze[1] and 
make LO use either the internal hsqldb 1.8.0 or libhsqldb1.8.0-java[2]..

Regards,
 
Rene

[1] Now that 698943 is fixed the new libhsqldb-java now is visible in
experimentals Packages files
[2] right now in NEW 
(http://ftp-master.debian.org/new/hsqldb1.8.0_1.8.0.10-15.html))

__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. 
Please use
debian-j...@lists.debian.org for discussions and questions.


Re: planning (a) hsqldb transition(s)

2013-01-07 Thread Rene Engelhard
Hi,

 Two weeks later, and rougly one month before the freeze? PING? Can you
 (= pkg-java and Sebastien!) please answer?

Now - *8* months later (yes, I let it slip but it was not very likely
to fit the freeze anyway with the non-reaction of the r-dep maintainers) -
we are long inside the freeze - so another Debian release with a completely
obosolete default libhsqldb-java :/
(And http://bugs.debian.org/670902 got wheezy-ignore.)

But we should fix it asap in jeesie.

 Or is this silent agreement? 
 (If so then please do not complain if a upgrade of libhsqldb-java from 
 1.8.0.10 to
 libhsqldb-java 2.2.8 breaks anything - you had advance warning.

This is the LAST ping. When there will be no reply (well, -med and
Sebastien[1] answered, this targets -java..) I *will* take this as a
silent agreement and do it immediately when the freeze ends
(and libreoffice will directly switch to libhsqldb1.8.0-java).

(See http://lists.debian.org/debian-openoffice/2012/04/msg00408.html and it's
References for the context, I _am not_ going to cut'n'paste it here again.)

 I *will* do this change - and ake LO use libhsqldb1.8-java *for sure* in the
 next weeks and libsqldb-java will become 2.2.8.

I seem to be too nice (or lazy) and actually didn't do it.

First part of this is now done, though:
- http://packages.qa.debian.org/h/hsqldb/news/20130107T011735Z.html
- hsqldb1.8.0 is in NEW:
  http://ftp-master.debian.org/new/hsqldb1.8.0_1.8.0.10-15.html

If hsqldb1.8.0 won't get accepted I still can use internal hsqldb
in LibreOffice, so...
If one of you still need it, too fine. Just change your packages :)
That way is not ideal, but better than carrying oround this
hsqldb mess longer without a reply from the r-dep maintainers.)

 And that upload will directly orphan the package.

This isn't yet done, but it will be done when this is in unstable.

Regards,

Rene

[1] http://lists.debian.org/debian-openoffice/2012/04/msg00410.html

__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. 
Please use
debian-j...@lists.debian.org for discussions and questions.


Re: planning (a) hsqldb transition(s)

2012-04-30 Thread Sébastien Delafond
On Apr/30, Rene Engelhard wrote:
 Hi,
 
 On Fri, Apr 13, 2012 at 04:31:31PM +0200, Rene Engelhard wrote:
   so I'd like to upload that to unstable (and adapt libreoffice) if it 
   happens.
   
   But this problem makes me ask
   
   Q1) does anyone of your programs using libhsqldb-java have the same 
   problem? Do we need to wait for them to be patches
   to upload 1.8.1.x?
   
   As you probably noticed, libhsqldb-java is 1.8.x while we have a
   libhsqldb2.0-java in experimental (and there's a 2.2.8 released, which I
   packaged some days ago and is ready to upload here now that I long 
   neglected
   because I didn't care as OOo and LibO *do* need 1.8.x.)
   
   Q2) Would you agree that renaming libhsqldb-java to libhsqldb1.8-java 
   would be
   worthwile? We then can upload 2.2.8 as libhsqldb-java. This needs 
   source
   uploads of all the above packages, though.
   
   Q3) Does anyone want to overtake libhsqldb-java (2.x) then? I am only
   interested in 1.8.x for OOo/LO.
   
   Q4) does anyone need 2.0 *and* 2.2 be different? Anything working with 2.0
   and not 2.2? (Doubt that, but better safe than sorry) - in that case 
   we
   need to have libhsqldb1.8-java, libhsqldb2.0-java and the new
   libhsqldb-java)
  
  And noone except tillea (for debian-med)[1] answered here. pkg-java,
  Sebastien?
 
 Two weeks later, and rougly one month before the freeze? PING? Can you
 (= pkg-java and Sebastien!) please answer?

Sorry for the lag, real life has been a bit hectic lately. I'm fine
with your upload plan, and will make my paros package depend on
libhsqldb1.8-java once you upload it. paros is not maintained upstream
anymore, but I will be able to take care of its patching to ensure
1.8.1.x compatibility, if need be.

Cheers,

--Seb

__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. 
Please use
debian-j...@lists.debian.org for discussions and questions.


Re: planning (a) hsqldb transition(s)

2012-04-29 Thread Rene Engelhard
Hi,

On Fri, Apr 13, 2012 at 04:31:31PM +0200, Rene Engelhard wrote:
  so I'd like to upload that to unstable (and adapt libreoffice) if it 
  happens.
  
  But this problem makes me ask
  
  Q1) does anyone of your programs using libhsqldb-java have the same 
  problem? Do we need to wait for them to be patches
  to upload 1.8.1.x?
  
  As you probably noticed, libhsqldb-java is 1.8.x while we have a
  libhsqldb2.0-java in experimental (and there's a 2.2.8 released, which I
  packaged some days ago and is ready to upload here now that I long neglected
  because I didn't care as OOo and LibO *do* need 1.8.x.)
  
  Q2) Would you agree that renaming libhsqldb-java to libhsqldb1.8-java would 
  be
  worthwile? We then can upload 2.2.8 as libhsqldb-java. This needs source
  uploads of all the above packages, though.
  
  Q3) Does anyone want to overtake libhsqldb-java (2.x) then? I am only
  interested in 1.8.x for OOo/LO.
  
  Q4) does anyone need 2.0 *and* 2.2 be different? Anything working with 2.0
  and not 2.2? (Doubt that, but better safe than sorry) - in that case we
  need to have libhsqldb1.8-java, libhsqldb2.0-java and the new
  libhsqldb-java)
 
 And noone except tillea (for debian-med)[1] answered here. pkg-java,
 Sebastien?

Two weeks later, and rougly one month before the freeze? PING? Can you
(= pkg-java and Sebastien!) please answer?

Or is this silent agreement? 
(If so then please do not complain if a upgrade of libhsqldb-java from 1.8.0.10 
to
libhsqldb-java 2.2.8 breaks anything - you had advance warning.
I *will* do this change - and ake LO use libhsqldb1.8-java *for sure* in the 
next weeks
and libsqldb-java will become 2.2.8. And that upload will directly orphan the 
package.
UNLESS you object)

Regards,

Rene

__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. 
Please use
debian-j...@lists.debian.org for discussions and questions.