Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.java > #10473 > unrolled thread

Help to upgrade icedtea-web

Started byVincent Privat <vincent@josm.openstreetmap.de>
First post2018-05-03 23:50 +0200
Last post2018-05-08 00:20 +0200
Articles 12 — 3 participants

Back to article view | Back to linux.debian.maint.java

Contents

  Help to upgrade icedtea-web Vincent Privat <vincent@josm.openstreetmap.de> - 2018-05-03 23:50 +0200
    Re: Help to upgrade icedtea-web Emmanuel Bourg <ebourg@apache.org> - 2018-05-04 00:00 +0200
      Re: Help to upgrade icedtea-web Vincent Privat <vincent@josm.openstreetmap.de> - 2018-05-04 00:10 +0200
        Re: Help to upgrade icedtea-web Emmanuel Bourg <ebourg@apache.org> - 2018-05-04 00:30 +0200
    Re: Help to upgrade icedtea-web Emmanuel Bourg <ebourg@apache.org> - 2018-05-04 18:20 +0200
      Re: Help to upgrade icedtea-web Vincent Privat <vincent@josm.openstreetmap.de> - 2018-05-04 23:40 +0200
        Re: Help to upgrade icedtea-web Emmanuel Bourg <ebourg@apache.org> - 2018-05-08 00:20 +0200
          Re: Help to upgrade icedtea-web Vincent Privat <vincent.privat@gmail.com> - 2018-05-08 00:40 +0200
            Re: Help to upgrade icedtea-web Vincent Privat <vincent.privat@gmail.com> - 2018-05-08 01:00 +0200
              Re: Help to upgrade icedtea-web Vincent Privat <vincent.privat@gmail.com> - 2018-05-08 13:40 +0200
                Re: Help to upgrade icedtea-web Vincent Privat <vincent.privat@gmail.com> - 2018-05-21 19:00 +0200
        Re: Help to upgrade icedtea-web Vincent Privat <vincent@josm.openstreetmap.de> - 2018-05-08 00:20 +0200

#10473 — Help to upgrade icedtea-web

FromVincent Privat <vincent@josm.openstreetmap.de>
Date2018-05-03 23:50 +0200
SubjectHelp to upgrade icedtea-web
Message-ID<vLugV-6Hv-3@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Hello,
Following Emmanuel's request for more manpower in the Java 10/11 migration
I volunteer to help.
I have very little Debian packaging experience so I may ask beginner/rookie
questions; I hope this is OK.
I am interested in upgrading icedtea-web to fix #886109 and #894360.
My first question: Is the VCS up-to-date? There's a vcswatch warning about
that. The changelog I find in Bazaar stops at 1.6.2-1 while the current
package version is 1.6.2-3.1:
https://qa.debian.org/cgi-bin/vcswatch?package=icedtea-web

Cheers,
Vincent

[toc] | [next] | [standalone]

#10474

FromEmmanuel Bourg <ebourg@apache.org>
Date2018-05-04 00:00 +0200
Message-ID<vLuqB-6Lh-3@gated-at.bofh.it>
In reply to#10473
Hi Vincent,

Le 03/05/2018 à 23:43, Vincent Privat a écrit :

> Following Emmanuel's request for more manpower in the Java 10/11
> migration I volunteer to help.

Thank you for stepping in!

> I have very little Debian packaging experience so I may ask
> beginner/rookie questions; I hope this is OK.
> I am interested in upgrading icedtea-web to fix #886109 and #894360.

icedtea-web covers browser applets and Java Web Start applications. The
applet part can be scrapped or disabled since it's no longer supported
by current browsers. Oracle is removing JWS from Java 11, but this
technology is still working and worth keeping I think.

> My first question: Is the VCS up-to-date? There's a vcswatch warning
> about that. The changelog I find in Bazaar stops at 1.6.2-1 while the
> current package version is 1.6.2-3.1:
> https://qa.debian.org/cgi-bin/vcswatch?package=icedtea-web

I guess Matthias didn't update the VCS unfortunately. Not sure he still
can, the update is two years old :(

Emmanuel Bourg

[toc] | [prev] | [next] | [standalone]

#10475

FromVincent Privat <vincent@josm.openstreetmap.de>
Date2018-05-04 00:10 +0200
Message-ID<vLuAi-745-1@gated-at.bofh.it>
In reply to#10474

[Multipart message — attachments visible in raw view] — view raw

2018-05-03 23:58 GMT+02:00 Emmanuel Bourg <ebourg@apache.org>:

> icedtea-web covers browser applets and Java Web Start applications. The
> applet part can be scrapped or disabled since it's no longer supported
> by current browsers. Oracle is removing JWS from Java 11, but this
> technology is still working and worth keeping I think.
>

I know :) We (JOSM) are deeply impacted by this sudden removal.
I'm in touch with Jiri Vanek from Red Hat to see how to improve Windows
support as well.
I hope we will succeed to replace JWS by ITW for most of our users.

I guess Matthias didn't update the VCS unfortunately. Not sure he still
> can, the update is two years old :(
>

Then I have another rookie question: aren't the binaries built from source?

[toc] | [prev] | [next] | [standalone]

#10476

FromEmmanuel Bourg <ebourg@apache.org>
Date2018-05-04 00:30 +0200
Message-ID<vLuTE-7b9-13@gated-at.bofh.it>
In reply to#10475
Le 04/05/2018 à 00:09, Vincent Privat a écrit :

> I know :) We (JOSM) are deeply impacted by this sudden removal.
> I'm in touch with Jiri Vanek from Red Hat to see how to improve Windows
> support as well.
> I hope we will succeed to replace JWS by ITW for most of our users.

I also heavily rely on JWS at work. I hope an alternative to JWS
supporting application and Java runtime upgrades will emerge.


> Then I have another rookie question: aren't the binaries built from source?

Yes they are. First you checkout the package (either with "debcheckout"
if the VCS is up to date, or "apt-get source" otherwise) and then run
"debuild" from the source directory fetched.

Regarding the VCS, I'll import the repository to salsa.debian.org.

Emmanuel Bourg

[toc] | [prev] | [next] | [standalone]

#10482

FromEmmanuel Bourg <ebourg@apache.org>
Date2018-05-04 18:20 +0200
Message-ID<vLLB7-1xQ-3@gated-at.bofh.it>
In reply to#10473
Le 03/05/2018 à 23:43, Vincent Privat a écrit :

> I am interested in upgrading icedtea-web to fix #886109 and #894360.
> My first question: Is the VCS up-to-date? There's a vcswatch warning
> about that. The changelog I find in Bazaar stops at 1.6.2-1 while the
> current package version is 1.6.2-3.1:
> https://qa.debian.org/cgi-bin/vcswatch?package=icedtea-web

I've migrated the Bazaar repository to Git and imported the missing
updates, you are ready to go:

  https://salsa.debian.org/java-team/icedtea-web

Emmanuel Bourg

[toc] | [prev] | [next] | [standalone]

#10485

FromVincent Privat <vincent@josm.openstreetmap.de>
Date2018-05-04 23:40 +0200
Message-ID<vLQAN-4MG-3@gated-at.bofh.it>
In reply to#10482

[Multipart message — attachments visible in raw view] — view raw

Thanks a lot!
After reading some documentation I forked the repo and did the following:

git clone git@salsa.debian.org:don-vip-guest/icedtea-web.git
cd icedtea-web
git checkout origin/upstream -b upstream
git checkout origin/pristine-tar -b pristine-tar
git checkout master
gbp import-orig --uscan --pristine-tar
git push --all

then created three Merge Requests (one per branch) in this order: upstream,
pristine-tar, master:
https://salsa.debian.org/java-team/icedtea-web/merge_requests

The first two seem to be correct, but the third (master) has merge
conflicts, I don't understand why? I probably did something wrong.

Vincent

2018-05-04 18:16 GMT+02:00 Emmanuel Bourg <ebourg@apache.org>:

> Le 03/05/2018 à 23:43, Vincent Privat a écrit :
>
> > I am interested in upgrading icedtea-web to fix #886109 and #894360.
> > My first question: Is the VCS up-to-date? There's a vcswatch warning
> > about that. The changelog I find in Bazaar stops at 1.6.2-1 while the
> > current package version is 1.6.2-3.1:
> > https://qa.debian.org/cgi-bin/vcswatch?package=icedtea-web
>
> I've migrated the Bazaar repository to Git and imported the missing
> updates, you are ready to go:
>
>   https://salsa.debian.org/java-team/icedtea-web
>
> Emmanuel Bourg
>

[toc] | [prev] | [next] | [standalone]

#10488

FromEmmanuel Bourg <ebourg@apache.org>
Date2018-05-08 00:20 +0200
Message-ID<vMWE9-7jI-9@gated-at.bofh.it>
In reply to#10485
Le 08/05/2018 à 00:10, Vincent Privat a écrit :
> Updates: the original repository now contains 1.7.1.
> I reworked the debian scripts in my fork:
> https://salsa.debian.org/don-vip-guest/icedtea-web/commit/ef0ea531f1ff83b12d7b6d7733a7fbfff100c3a7
> It seems I now manage to build icedtea-web using "debuild -b -uc -us" in
> debian directory but I don't know how to install it? The packaging
> tutorial tells to install the package with dpkg -i but I don't see any
> .deb file as a result ?

Did you check the parent directory? This is were the .deb files land
usually.

[toc] | [prev] | [next] | [standalone]

#10490

FromVincent Privat <vincent.privat@gmail.com>
Date2018-05-08 00:40 +0200
Message-ID<vMWXw-7qD-3@gated-at.bofh.it>
In reply to#10488

[Multipart message — attachments visible in raw view] — view raw

Ah, yes they're here! I did not expect them to be built outside of source
directory. Thanks! :)

2018-05-08 0:18 GMT+02:00 Emmanuel Bourg <ebourg@apache.org>:

> Le 08/05/2018 à 00:10, Vincent Privat a écrit :
> > Updates: the original repository now contains 1.7.1.
> > I reworked the debian scripts in my fork:
> > https://salsa.debian.org/don-vip-guest/icedtea-web/commit/
> ef0ea531f1ff83b12d7b6d7733a7fbfff100c3a7
> > It seems I now manage to build icedtea-web using "debuild -b -uc -us" in
> > debian directory but I don't know how to install it? The packaging
> > tutorial tells to install the package with dpkg -i but I don't see any
> > .deb file as a result ?
>
> Did you check the parent directory? This is were the .deb files land
> usually.
>
>

[toc] | [prev] | [next] | [standalone]

#10491

FromVincent Privat <vincent.privat@gmail.com>
Date2018-05-08 01:00 +0200
Message-ID<vMXgR-7xM-5@gated-at.bofh.it>
In reply to#10490

[Multipart message — attachments visible in raw view] — view raw

I'm able to install the packages and launch javaws \o/
But when launching JOSM I face a JAXP configuration error:

javax.xml.validation.SchemaFactoryConfigurationError: Provider for class
javax.xml.validation.SchemaFactory cannot be created
    at
java.xml/javax.xml.validation.SchemaFactoryFinder.findServiceProvider(SchemaFactoryFinder.java:361)
    at
java.xml/javax.xml.validation.SchemaFactoryFinder._newFactory(SchemaFactoryFinder.java:218)
    at
java.xml/javax.xml.validation.SchemaFactoryFinder.newFactory(SchemaFactoryFinder.java:145)
    at
java.xml/javax.xml.validation.SchemaFactory.newInstance(SchemaFactory.java:246)
    at
org.openstreetmap.josm.data.preferences.PreferencesReader.validateXML(PreferencesReader.java:99)
    at
org.openstreetmap.josm.data.preferences.PreferencesReader.validateXML(PreferencesReader.java:87)
    at org.openstreetmap.josm.data.Preferences.load(Preferences.java:498)
    at org.openstreetmap.josm.data.Preferences.init(Preferences.java:603)
    at
org.openstreetmap.josm.gui.MainApplication.mainJOSM(MainApplication.java:937)
    at
org.openstreetmap.josm.gui.MainApplication$2.processArguments(MainApplication.java:280)
    at
org.openstreetmap.josm.gui.MainApplication.main(MainApplication.java:860)
    ... 6 more
Caused by: java.util.ServiceConfigurationError:
javax.xml.validation.SchemaFactory: Provider
org.apache.xerces.jaxp.validation.XMLSchemaFactory not found
    at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:588)
    at java.base/java.util.ServiceLoader.access$200(ServiceLoader.java:390)
    at
java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.nextProviderClass(ServiceLoader.java:1206)
    at
java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNextService(ServiceLoader.java:1215)
    at
java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.access$1200(ServiceLoader.java:1103)
    at
java.base/java.util.ServiceLoader$LazyClassPathLookupIterator$1.run(ServiceLoader.java:1262)
    at
java.base/java.util.ServiceLoader$LazyClassPathLookupIterator$1.run(ServiceLoader.java:1261)
    at java.base/java.security.AccessController.doPrivileged(Native Method)
    at
java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNext(ServiceLoader.java:1264)
    at java.base/java.util.ServiceLoader$2.hasNext(ServiceLoader.java:1294)
    at java.base/java.util.ServiceLoader$3.hasNext(ServiceLoader.java:1379)
    at
java.xml/javax.xml.validation.SchemaFactoryFinder$2.run(SchemaFactoryFinder.java:350)
    at
java.xml/javax.xml.validation.SchemaFactoryFinder$2.run(SchemaFactoryFinder.java:346)
    at java.base/java.security.AccessController.doPrivileged(Native Method)
    at
java.xml/javax.xml.validation.SchemaFactoryFinder.findServiceProvider(SchemaFactoryFinder.java:346)
    ... 16 more

Does it speak to anyone? I'm not sure if I must install something else or
if it comes from a packaging problem.
Vincent

2018-05-08 0:33 GMT+02:00 Vincent Privat <vincent.privat@gmail.com>:

> Ah, yes they're here! I did not expect them to be built outside of source
> directory. Thanks! :)
>
> 2018-05-08 0:18 GMT+02:00 Emmanuel Bourg <ebourg@apache.org>:
>
>> Le 08/05/2018 à 00:10, Vincent Privat a écrit :
>> > Updates: the original repository now contains 1.7.1.
>> > I reworked the debian scripts in my fork:
>> > https://salsa.debian.org/don-vip-guest/icedtea-web/commit/ef
>> 0ea531f1ff83b12d7b6d7733a7fbfff100c3a7
>> > It seems I now manage to build icedtea-web using "debuild -b -uc -us" in
>> > debian directory but I don't know how to install it? The packaging
>> > tutorial tells to install the package with dpkg -i but I don't see any
>> > .deb file as a result ?
>>
>> Did you check the parent directory? This is were the .deb files land
>> usually.
>>
>>
>

[toc] | [prev] | [next] | [standalone]

#10492

FromVincent Privat <vincent.privat@gmail.com>
Date2018-05-08 13:40 +0200
Message-ID<vN98m-6zi-11@gated-at.bofh.it>
In reply to#10491

[Multipart message — attachments visible in raw view] — view raw

I found the issue to be caused by my installation of the Java debian helper
packages which rely on JAXP 1.3.
Removing libjaxp1.3-java and all packages needing it (gradle-debian-helper,
maven-debian-helper, etc.) fixed the issue.
As I am now able to run JOSM with IcedTea-Web 1.7.1 built with default-jdk
I have open the following Merge Request:
https://salsa.debian.org/java-team/icedtea-web/merge_requests/4/diffs

Can you please review it? As it is the first time I update a Debian package
I surely have missed/broken something.

Cheers,
Vincent

2018-05-08 0:51 GMT+02:00 Vincent Privat <vincent.privat@gmail.com>:

> I'm able to install the packages and launch javaws \o/
> But when launching JOSM I face a JAXP configuration error:
>
> javax.xml.validation.SchemaFactoryConfigurationError: Provider for class
> javax.xml.validation.SchemaFactory cannot be created
>     at java.xml/javax.xml.validation.SchemaFactoryFinder.
> findServiceProvider(SchemaFactoryFinder.java:361)
>     at java.xml/javax.xml.validation.SchemaFactoryFinder._newFactory(
> SchemaFactoryFinder.java:218)
>     at java.xml/javax.xml.validation.SchemaFactoryFinder.newFactory(
> SchemaFactoryFinder.java:145)
>     at java.xml/javax.xml.validation.SchemaFactory.newInstance(
> SchemaFactory.java:246)
>     at org.openstreetmap.josm.data.preferences.PreferencesReader.
> validateXML(PreferencesReader.java:99)
>     at org.openstreetmap.josm.data.preferences.PreferencesReader.
> validateXML(PreferencesReader.java:87)
>     at org.openstreetmap.josm.data.Preferences.load(Preferences.java:498)
>     at org.openstreetmap.josm.data.Preferences.init(Preferences.java:603)
>     at org.openstreetmap.josm.gui.MainApplication.mainJOSM(
> MainApplication.java:937)
>     at org.openstreetmap.josm.gui.MainApplication$2.processArguments(
> MainApplication.java:280)
>     at org.openstreetmap.josm.gui.MainApplication.main(
> MainApplication.java:860)
>     ... 6 more
> Caused by: java.util.ServiceConfigurationError: javax.xml.validation.SchemaFactory:
> Provider org.apache.xerces.jaxp.validation.XMLSchemaFactory not found
>     at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:588)
>     at java.base/java.util.ServiceLoader.access$200(
> ServiceLoader.java:390)
>     at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.
> nextProviderClass(ServiceLoader.java:1206)
>     at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.
> hasNextService(ServiceLoader.java:1215)
>     at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.
> access$1200(ServiceLoader.java:1103)
>     at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator$1.
> run(ServiceLoader.java:1262)
>     at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator$1.
> run(ServiceLoader.java:1261)
>     at java.base/java.security.AccessController.doPrivileged(Native
> Method)
>     at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.
> hasNext(ServiceLoader.java:1264)
>     at java.base/java.util.ServiceLoader$2.hasNext(
> ServiceLoader.java:1294)
>     at java.base/java.util.ServiceLoader$3.hasNext(
> ServiceLoader.java:1379)
>     at java.xml/javax.xml.validation.SchemaFactoryFinder$2.run(
> SchemaFactoryFinder.java:350)
>     at java.xml/javax.xml.validation.SchemaFactoryFinder$2.run(
> SchemaFactoryFinder.java:346)
>     at java.base/java.security.AccessController.doPrivileged(Native
> Method)
>     at java.xml/javax.xml.validation.SchemaFactoryFinder.
> findServiceProvider(SchemaFactoryFinder.java:346)
>     ... 16 more
>
> Does it speak to anyone? I'm not sure if I must install something else or
> if it comes from a packaging problem.
> Vincent
>
> 2018-05-08 0:33 GMT+02:00 Vincent Privat <vincent.privat@gmail.com>:
>
>> Ah, yes they're here! I did not expect them to be built outside of source
>> directory. Thanks! :)
>>
>> 2018-05-08 0:18 GMT+02:00 Emmanuel Bourg <ebourg@apache.org>:
>>
>>> Le 08/05/2018 à 00:10, Vincent Privat a écrit :
>>> > Updates: the original repository now contains 1.7.1.
>>> > I reworked the debian scripts in my fork:
>>> > https://salsa.debian.org/don-vip-guest/icedtea-web/commit/ef
>>> 0ea531f1ff83b12d7b6d7733a7fbfff100c3a7
>>> > It seems I now manage to build icedtea-web using "debuild -b -uc -us"
>>> in
>>> > debian directory but I don't know how to install it? The packaging
>>> > tutorial tells to install the package with dpkg -i but I don't see any
>>> > .deb file as a result ?
>>>
>>> Did you check the parent directory? This is were the .deb files land
>>> usually.
>>>
>>>
>>
>

[toc] | [prev] | [next] | [standalone]

#10518

FromVincent Privat <vincent.privat@gmail.com>
Date2018-05-21 19:00 +0200
Message-ID<vRWka-3A5-5@gated-at.bofh.it>
In reply to#10492

[Multipart message — attachments visible in raw view] — view raw

Hi,
I've taken into account the feedback. Should I hit the "Merge" button?
Cheers,
Vincent

2018-05-08 13:37 GMT+02:00 Vincent Privat <vincent.privat@gmail.com>:

> I found the issue to be caused by my installation of the Java debian
> helper packages which rely on JAXP 1.3.
> Removing libjaxp1.3-java and all packages needing it
> (gradle-debian-helper, maven-debian-helper, etc.) fixed the issue.
> As I am now able to run JOSM with IcedTea-Web 1.7.1 built with default-jdk
> I have open the following Merge Request:
> https://salsa.debian.org/java-team/icedtea-web/merge_requests/4/diffs
>
> Can you please review it? As it is the first time I update a Debian
> package I surely have missed/broken something.
>
> Cheers,
> Vincent
>
> 2018-05-08 0:51 GMT+02:00 Vincent Privat <vincent.privat@gmail.com>:
>
>> I'm able to install the packages and launch javaws \o/
>> But when launching JOSM I face a JAXP configuration error:
>>
>> javax.xml.validation.SchemaFactoryConfigurationError: Provider for class
>> javax.xml.validation.SchemaFactory cannot be created
>>     at java.xml/javax.xml.validation.SchemaFactoryFinder.findServic
>> eProvider(SchemaFactoryFinder.java:361)
>>     at java.xml/javax.xml.validation.SchemaFactoryFinder._newFactor
>> y(SchemaFactoryFinder.java:218)
>>     at java.xml/javax.xml.validation.SchemaFactoryFinder.newFactory
>> (SchemaFactoryFinder.java:145)
>>     at java.xml/javax.xml.validation.SchemaFactory.newInstance(Sche
>> maFactory.java:246)
>>     at org.openstreetmap.josm.data.preferences.PreferencesReader.va
>> lidateXML(PreferencesReader.java:99)
>>     at org.openstreetmap.josm.data.preferences.PreferencesReader.va
>> lidateXML(PreferencesReader.java:87)
>>     at org.openstreetmap.josm.data.Preferences.load(Preferences.java:498)
>>     at org.openstreetmap.josm.data.Preferences.init(Preferences.java:603)
>>     at org.openstreetmap.josm.gui.MainApplication.mainJOSM(MainAppl
>> ication.java:937)
>>     at org.openstreetmap.josm.gui.MainApplication$2.processArgument
>> s(MainApplication.java:280)
>>     at org.openstreetmap.josm.gui.MainApplication.main(MainApplicat
>> ion.java:860)
>>     ... 6 more
>> Caused by: java.util.ServiceConfigurationError:
>> javax.xml.validation.SchemaFactory: Provider
>> org.apache.xerces.jaxp.validation.XMLSchemaFactory not found
>>     at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:588)
>>     at java.base/java.util.ServiceLoader.access$200(ServiceLoader.
>> java:390)
>>     at java.base/java.util.ServiceLoader$LazyClassPathLookupIterato
>> r.nextProviderClass(ServiceLoader.java:1206)
>>     at java.base/java.util.ServiceLoader$LazyClassPathLookupIterato
>> r.hasNextService(ServiceLoader.java:1215)
>>     at java.base/java.util.ServiceLoader$LazyClassPathLookupIterato
>> r.access$1200(ServiceLoader.java:1103)
>>     at java.base/java.util.ServiceLoader$LazyClassPathLookupIterato
>> r$1.run(ServiceLoader.java:1262)
>>     at java.base/java.util.ServiceLoader$LazyClassPathLookupIterato
>> r$1.run(ServiceLoader.java:1261)
>>     at java.base/java.security.AccessController.doPrivileged(Native
>> Method)
>>     at java.base/java.util.ServiceLoader$LazyClassPathLookupIterato
>> r.hasNext(ServiceLoader.java:1264)
>>     at java.base/java.util.ServiceLoader$2.hasNext(ServiceLoader.
>> java:1294)
>>     at java.base/java.util.ServiceLoader$3.hasNext(ServiceLoader.
>> java:1379)
>>     at java.xml/javax.xml.validation.SchemaFactoryFinder$2.run(Sche
>> maFactoryFinder.java:350)
>>     at java.xml/javax.xml.validation.SchemaFactoryFinder$2.run(Sche
>> maFactoryFinder.java:346)
>>     at java.base/java.security.AccessController.doPrivileged(Native
>> Method)
>>     at java.xml/javax.xml.validation.SchemaFactoryFinder.findServic
>> eProvider(SchemaFactoryFinder.java:346)
>>     ... 16 more
>>
>> Does it speak to anyone? I'm not sure if I must install something else or
>> if it comes from a packaging problem.
>> Vincent
>>
>> 2018-05-08 0:33 GMT+02:00 Vincent Privat <vincent.privat@gmail.com>:
>>
>>> Ah, yes they're here! I did not expect them to be built outside of
>>> source directory. Thanks! :)
>>>
>>> 2018-05-08 0:18 GMT+02:00 Emmanuel Bourg <ebourg@apache.org>:
>>>
>>>> Le 08/05/2018 à 00:10, Vincent Privat a écrit :
>>>> > Updates: the original repository now contains 1.7.1.
>>>> > I reworked the debian scripts in my fork:
>>>> > https://salsa.debian.org/don-vip-guest/icedtea-web/commit/ef
>>>> 0ea531f1ff83b12d7b6d7733a7fbfff100c3a7
>>>> > It seems I now manage to build icedtea-web using "debuild -b -uc -us"
>>>> in
>>>> > debian directory but I don't know how to install it? The packaging
>>>> > tutorial tells to install the package with dpkg -i but I don't see any
>>>> > .deb file as a result ?
>>>>
>>>> Did you check the parent directory? This is were the .deb files land
>>>> usually.
>>>>
>>>>
>>>
>>
>

[toc] | [prev] | [next] | [standalone]

#10489

FromVincent Privat <vincent@josm.openstreetmap.de>
Date2018-05-08 00:20 +0200
Message-ID<vMWE9-7jI-11@gated-at.bofh.it>
In reply to#10485

[Multipart message — attachments visible in raw view] — view raw

Updates: the original repository now contains 1.7.1.
I reworked the debian scripts in my fork:
https://salsa.debian.org/don-vip-guest/icedtea-web/commit/ef0ea531f1ff83b12d7b6d7733a7fbfff100c3a7
It seems I now manage to build icedtea-web using "debuild -b -uc -us" in
debian directory but I don't know how to install it? The packaging tutorial
tells to install the package with dpkg -i but I don't see any .deb file as
a result ?
Vincent

2018-05-04 23:36 GMT+02:00 Vincent Privat <vincent@josm.openstreetmap.de>:

> Thanks a lot!
> After reading some documentation I forked the repo and did the following:
>
> git clone git@salsa.debian.org:don-vip-guest/icedtea-web.git
> cd icedtea-web
> git checkout origin/upstream -b upstream
> git checkout origin/pristine-tar -b pristine-tar
> git checkout master
> gbp import-orig --uscan --pristine-tar
> git push --all
>
> then created three Merge Requests (one per branch) in this order:
> upstream, pristine-tar, master:
> https://salsa.debian.org/java-team/icedtea-web/merge_requests
>
> The first two seem to be correct, but the third (master) has merge
> conflicts, I don't understand why? I probably did something wrong.
>
> Vincent
>
> 2018-05-04 18:16 GMT+02:00 Emmanuel Bourg <ebourg@apache.org>:
>
>> Le 03/05/2018 à 23:43, Vincent Privat a écrit :
>>
>> > I am interested in upgrading icedtea-web to fix #886109 and #894360.
>> > My first question: Is the VCS up-to-date? There's a vcswatch warning
>> > about that. The changelog I find in Bazaar stops at 1.6.2-1 while the
>> > current package version is 1.6.2-3.1:
>> > https://qa.debian.org/cgi-bin/vcswatch?package=icedtea-web
>>
>> I've migrated the Bazaar repository to Git and imported the missing
>> updates, you are ready to go:
>>
>>   https://salsa.debian.org/java-team/icedtea-web
>>
>> Emmanuel Bourg
>>
>
>

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.java

csiph-web