Very exciting! Thanks for your status updates on this. Do you want more
visibility for them? I think more people would see these if they were posted to
a blog or Mastodon. It is easy to set up a simple Markdown/Jekyll blog on
Salsa. Or you could post to this one:
https://android-tools-
Great news! Congrats on hitting that major milestone!
Julien Plissonneau Duquène:
Good evening,
Some great news for this week, as I got my "stage 0" gradle (the one that is
locally built by a pre-built binary distribution of Gradle from upstream) to
rebuild itself successfully.
Le 2025-0
sre4e...@free.fr:
Le 2024-12-09 14:32, Emmanuel Bourg a écrit :
I don't think we should try too hard to keep the bootstrapping logic in the
package, that'll most certainly be tedious to maintain over time.
Well that's indeed something to think about, and I am a bit worried about that
as
Emmanuel Bourg:
Hi Julien,
Le 04/11/2024 à 14:43, Julien Plissonneau Duquène a écrit :
This is to let you know that I am currently working on overhauling and
upgrading the gradle package to the upcoming 8.11 release. This is indeed
quite challenging and I am not yet to the point where I cou
If the test passes regularly, and just sometimes fails under the same
conditions, I would consider disabling it in autopkgtest rather than have it not
make it into bookworm. The perfect is the enemy of the good.
.hc
Olek Wojnar:
Fellow Bazel contributors (and Java Team members),
I've dis
Emmanuel Bourg:
Le 2023-02-13 16:38, Hans-Christoph Steiner a écrit :
android-framework-23 is in bullseye. So I doublechecked, it is
actually just a conflict with JDK17, due to the removal of
com.sun.javadoc, which was deprecated in JDK11. JDK8 would cover that
though.
I have no idea how
Hans-Christoph Steiner:
Thorsten Glaser:
On Mon, 13 Feb 2023, Hans-Christoph Steiner wrote:
Great work there! I would still love to see openjdk-8 in bookworm.
That ship has sailed yesterday. No new entries into testing are now
possible any more.
Damn, that might mean a lot of Android
Thorsten Glaser:
On Mon, 13 Feb 2023, Hans-Christoph Steiner wrote:
Great work there! I would still love to see openjdk-8 in bookworm.
That ship has sailed yesterday. No new entries into testing are now
possible any more.
Damn, that might mean a lot of Android packages are not going to
Markus Koschany:
Am Mittwoch, dem 01.02.2023 um 12:24 +0100 schrieb Emmanuel Bourg:
Le 2023-01-26 17:17, Emmanuel Bourg a écrit :
I've been working on Kotlin lately, trying to make it build with
OpenJDK 17
only, and hopefully have it included in Bookworm.
Long story short, after days bangi
Markus Koschany:
Am Samstag, dem 20.08.2022 um 18:27 +0200 schrieb Thorsten Glaser:
On Sat, 20 Aug 2022, Phil Morrell wrote:
Hi all, documenting my observations as of today because it's not looking
promising for bookworm.
* kotlin FTBFS because of changes to support openjdk 17 #1012214
I
Hey Sunday,
I think you still want to try to patch out as much as possible with this
package. Gradle builds include lots of things that will never be used by the
Debian packaging, like plugins for pushing files to maven repos and generating
test coverage reports. There are many java-team p
I can make it!
Raman Sarda:
Count me in too.
On 23 March 2021 1:09:18 am IST, Manas Kashyap
wrote:
I am in for monthly meeting.
On Tue, Mar 23, 2021, 1:08 AM Samyak Jain wrote:
Hello, Teams!
I hope everyone is doing well.
The last Thursday of this month is about to knock on the doors
Hear hear! Thanks for working on Bazel, looks like Android/AOSP is
switching to Bazel, so we'll need it to build the Android Tools packages
in the future.
.hc
Olek Wojnar:
Fellow Java Maintainers,
Due to the tight interdependencies between a number of the Google ecosystem
Java packages t
Emmanuel Bourg:
Le 07/12/2020 à 11:38, Antonin Delpeuch (lists) a écrit :
Keep the suggestions coming, this is super useful!
Another point to keep in mind, if you build and distribute your own .deb
or Flatpak package you keep the control on the release schedule. Using
jdeb you could publish
Antonin Delpeuch (lists):
Hi Emmanuel,
On 06/12/2020 22:18, Emmanuel Bourg wrote:
Did you consider building a .deb package with jdeb [1] ? It's an
alternative that involves much less work than uploading to the Debian
repository. For a complex and very specialized software like OpenRefine
th
Hey Nico,
I would be interested to see Briar be in Debian. I think its only
worthwhile to get it in as a real Debian package. You can start by
working with the upstream kotlin/gradle binaries with versions that
match what is aimed for Debian/bullseye. I think that's gradle 6.4.1.
If you ge
Samyak Jain:
> Hi again :D
>
>
> The issue for the modified binaries was fixed last week and the package
> built successfully, without any failures. The updated package can be found
> here[1]
>
> On Wed, May 27, 2020 at 4:18 AM Emmanuel Bourg wrote:
>
>> Thank you very much for working on K
Hey Raman,
Here's the error in question:
sed \
-e 's/\(.*\):: *$/\n=item \1\n/' \
-e 's/`\([^`]*\)`/B<\1>/g' \
-e 's/^+$//g' \
-e 's/\(https:[^[]*\)[[][^]]*\]/L<\1>/g' \
-e '/<]*>>/y/_/ /' \
-e 's/<]*\)>>/the documentation section B<\U\1\E>/g' \
hey Jim,
On Debian/buster, `apt-get install gradle` works for me, and its running
Java11. bullseye has the same version, as far as I know.
gradle started using kotlin, so the blocker for updates is getting
kotlin into Debian. Unfortunately the Kotlin devs made that much harder
than it should
As far as I can tell, the errors are with maven. GitLab CI will
automatically run again when you push new commits. If you are logged
into salsa.debian.org, then you can also click the Retry button.
.hc
Mechtilde Stehmann:
> Hello,
>
> I did my first own prepared build for libjavax-annotatio
guava are used by lots of things, so its probably not a simply "update
and move on". That said, I have nothing to do with the guava package.
.hc
Steffen Möller:
> Hello,
>
> I need an update for the guava libraries from
>
> https://salsa.debian.org/java-team/guava-libraries/blob/master/debia
Markus Koschany:
> Hello,
>
> Am 18.08.19 um 14:46 schrieb Hideki Yamane:
>> Hi,
>>
>> On Mon, 12 Aug 2019 13:22:45 +0900
>> Hideki Yamane wrote:
>>> I cannot find CI setting on salsa for jcodings and jruby-joni package
>>> https://salsa.debian.org/java-team/jruby-joni
>>> https://salsa.deb
Just about any free software is eligable. The next step is find someone
to sponsor your package upload. Once you have it packaged and tested,
upload it to https://mentors.debian.net or ask here again.
.hc
olit...@yahoo.fr:
> Hello,
>
> I would like to submit this java based open source softwa
A version of this was reviewed and went out on the Java team blog a
while ago, before FOSDEM.
Emmanuel Bourg wrote:
> Hans-Christoph Steiner wrote:
>
> Some comments on the post:
>
>> Include a build target in your build system that builds using only
>> libraries in D
Hey Guido,
I think you are missing the key point here: "We don't have the resources
to maintain more than one version". So if you think it is important,
you should find the resources to make it happen. That's how Debian works.
.hc
Guido Medina:
> So, let me get this, you have removed OpenJDK 8
Andreas Schildbach:
> On 24/04/2019 10.56, Emmanuel Bourg wrote:
>
>> Yes, we've worked hard on the transition to Java 11, fixing more than
>> 500 issues over a year. Incompatible packages have been either upgraded,
>> fixed or removed. The notable exception right now is netbeans (#925509).
>
Hey Armando,
Thanks for your interest and welcome! There are many ways to jump into
Java packaging. One way is to go through the bug reports and try
confirming them and fixing them. Right now Debian/buster is in the
release freeze, so it is a great time to fix bugs for the upcoming release.
Ot
Emmanuel Bourg:
> Le 30/01/2019 à 22:59, Hans-Christoph Steiner a écrit :
>
>> I thought it was worth a blog post too, as a follow up to your talk:
>> https://salsa.debian.org/publicity-team/bits/merge_requests/16
>
> Nice, remember the Java Team also has its own
Markus Koschany:
>
>
> Am 30.01.19 um 11:10 schrieb Hans-Christoph Steiner:
>>
>> Great that you are giving that talk! I think the Java Team's work is
>> generally under-appreciated, so getting the word out should help with
>> that. Here's w
Great that you are giving that talk! I think the Java Team's work is
generally under-appreciated, so getting the word out should help with
that. Here's what I would add:
I think one thing to mention is how the Debian Java Team has to
consistently fight the Java standard practice of bundling al
Emmanuel Bourg:
> Le 27/01/2019 à 22:52, Hans-Christoph Steiner a écrit :
>
>> The call that is crashing out with all those errors is the doclava call.
>> I think there needs to be a --patch-module option to java when running
>> doclava, but I'm not sure what th
Hans-Christoph Steiner:
>
>
> Emmanuel Bourg:
>> Le 27/01/2019 à 21:12, Hans-Christoph Steiner a écrit :
>>
>>> I have been building with these options in gradle:
>>>
>>> sourceCompatibility = 1.8
>>> targetCompatibility = 1.8
>
Emmanuel Bourg:
> Le 27/01/2019 à 21:12, Hans-Christoph Steiner a écrit :
>
>> I have been building with these options in gradle:
>>
>> sourceCompatibility = 1.8
>> targetCompatibility = 1.8
>>
>> And that doesn't solve the problem of the ne
Thorsten Glaser:
> On Sun, 27 Jan 2019, Hans-Christoph Steiner wrote:
>
>> android-framework-23 doesn't work with Java 9+, but will build with Java
>> 8. But that would make it the only package in buster that needs java8.
>> So no go. Building with default-jdk ru
Hey Java Team!
We're trying to get some version of the android-framework-2x into
buster, and it is a struggle. Since y'all have helped with this package
before, and know lots about packaging Java, I'm asking for some advice.
seamlik, cdesai, and I are stumped. I did apply some upstream patches
Markus Koschany:
> On Wed, 15 Nov 2017 18:01:07 +0200 Adrian Bunk wrote:
> [...]
>> I tried to sort out what I could find as required for getting the
>> ancient eclipse out of testing in [1]:
>>
>> 1. src:bnd
>> You fixed that already.
>>
>> 2. batik -> maven -> guice -> libspring-java -> aspect
Markus Koschany:
> On 20.02.2017 09:03, 殷啟聰 wrote:
>> Hi Markus,
>>
>> That makes sense, I'll rename it to libsmali-1-java and move it to
>> android-tools. Although I think it would also make sense if you had
>> put libsmali-java in pkg-java in the first place, since it's just a
>> Java library.
compile 'com.google.guava:guava:debian'
> }
> }
> ```
>
> And see what happens :)
>
> 2016-12-23 7:31 GMT+08:00 Hans-Christoph Steiner :
>>
>> I'm trying to update the Android gradle plugin (java/groovy/gradle) to
>> the latest release in time for stretch.
I'm trying to update the Android gradle plugin (java/groovy/gradle) to
the latest release in time for stretch. I already updated the dependent
lib android-platform-frameworks-data-binding to 2.2.2 and uploaded that.
Seamlik uploaded
android-platform-tools-analytics-library and this is already us
Hey all,
Its time for 2016's GSoC application process. Last year Markus and I
were the mentors for this project, and we got a lot of solid
contributions included, both for pkg-java and android-tools teams
packages (groovy, gradle, android SDK bits written in C, etc). We also
had lots of student a
We welcome more contributors! I'd love to see Android Studio in Debian. I
agree with Markus and Kai-Chung that the best approach is to start by packaging
dependencies. The first step is getting the Android SDK in Debian so that apps
can be built only from packages in Debian. We're getting c
I remember getting odd errors like this while working with lombok-ast,
my solution in the end was to try disabling chunks of lombok*, which
obviously didn't work.
Have you tried emailing upstream? I did manage to get one or two
responses from them. This is a very specialized beast.
.hc
Markus
Markus Koschany:
> Am 15.02.2016 um 17:07 schrieb Hans-Christoph Steiner:
>>
>> lamby is working on this project also, and is a NEW reviewer, so it
>> should be quick. Is there anything else that needs fixing here?
>> Anything that I should upload?
>
> lombok
lamby is working on this project also, and is a NEW reviewer, so it
should be quick. Is there anything else that needs fixing here?
Anything that I should upload?
.hc
Markus Koschany:
> Hi,
>
> I have fixed lombok by patching the failing Javac class. Upstream tries
> to be backwards compatible
Markus Koschany:
> Am 07.02.2016 um 15:52 schrieb Ioan Eugen Stan:
>> Hello,
>>
>> I'm trying to fix lombok packge so it builds but there are some issues
>> that I don't know how to handle best.
>
> Hi,
>
> I need lombok to build lombok-ast but the current lombok package has
> some issues and d
Hey Ioan,
Glad to have another person joining in the lombok struggles! apo and I
have been working on the lombok suite, but it is not quite complete yet.
I think apo is still struggling with ivyplusplus, which is the upstream
build system for lombok.
.hc
Ioan Eugen Stan:
> Hello,
>
> I'm try
I'm packaging lombok and related things since the Android SDK Tools
depend on it. They all build with a custom additions to ivy called
ivyplusplus, which I've packaged. The build/compile process runs fine,
but it does not actually compile some of the .java files into .class
files. Looking at th
Hey all,
I've been working to package the 'project lombok' suite of libraries and
tools, and its been pretty brutal. They are all interdependant on each
other, so I've ended up writing my own build ant system for lombok and
ivyplusplus to get around that. Also, the native build system makes
bun
Hey Jakub and all,
A stroke of madness has driven me to try to get the lombok libraries
into Debian. They are a mess of circular dependencies and custom build
tools. The Android-SDK relies on lombok.ast, which requires all sorts
of other things, and that's what got me there.
I found Jakub Adam
Emmanuel Bourg:
> Le 3/12/2015 13:11, Hans-Christoph Steiner a écrit :
>
>> They've made quite a bit of progress, but there are a couple things that
>> we need to run by the team here. The first one I remember is that
>> Apache commons-pool needs to be updated f
Hey all,
I'm here at the Reproducible Builds summit in Athens, and I've been
helping Lukacs and Janak from Google get Bazel into Debian. Also, they
mentioned that there are some upcoming efforts to get more of their Java
stuff into Debian, but I'll let them elaborate on that.
They've made quite
Markus Koschany:
> Am 13.11.2015 um 19:05 schrieb Markus Koschany:
>> Hi all,
>>
>> I intend to start the transition for BND at the beginning of next week.
>> I will start with switching problematic packages to the bnd1.50 package,
>> so everything continues to work. For all other packages I expe
I would love to see gradle backported to Debian/jessie. I want to push hard
the idea of getting gradle from Debian directly and get Android and other devs
used to that idea as soon as possible.
Right now, the distribution of gradle and plugins is seriously crappy
security-wise. Having gradle an
殷啟聰:
> On Tue, 28 Jul 2015 22:38:40 +0200 Moritz Muehlenhoff wrote:
>> Package: groovy
>> Severity: serious
>>
>> A separate source package groovy2 was uploaded, so reverse dependencies
>> need to be migrated to that one and groovy removed.
>>
>> Cheers,
>> Moritz
>>
>>
>
> Hi Moritz an
I know that Komal has been working on updating it. She's currently working on
dependencies needed by the latest release. We recently uploaded cmdreader and
javawriter as part of that effort.
.hc
olivier sallou:
> Hi,
> has anyone already build package using Ivy (manage ant dependencies etc...)
ation of ivy.jar to ant with
> 'lib' flag. I think there won't be any
> problem now.
>
> As you suggested, I have added my name in uploaders field.
>
>
> On Wed, Aug 19, 2015 at 4:31 PM, Hans-Christoph Steiner
> wrote:
>
>>
>> Komal Sukhani:
&
Komal Sukhani:
> Hi Hans,
>
> On Tue, Aug 4, 2015 at 6:00 PM, Hans-Christoph Steiner
> wrote:
>
>>
>> Hey Komal,
>>
>> Looks good overall. You seem to be getting much quicker at packaging :) I
>> pushed some commits to fix some minor things.
Emmanuel Bourg:
> Le 17/08/2015 21:23, Markus Koschany a écrit :
>
>> I have just uploaded groovy2 2.4.3-2 and gradle 2.5-3 to unstable. I
>> would like to take the opportunity to thank our Google Summer of Code
>> students Kai-Chung Yan and Komal Sukhani for their magnificent work on
>> both no
If anyone wants to give feedback on the student proposals for the "Android
Tools in Debian" Summer of Code project, here are the full applications:
https://wiki.debian.org/SummerOfCode2015/StudentApplications#Android_tools_in_Debian
We have 4 or maybe 5 complete applications for 2 slots. We def
Sounds good to me. I think it would be good to mention gradle even though its
old, just to start getting the word out that its in Debian.
You could also mention the packages the derive from androidsdk-tools:
https://packages.debian.org/source/jessie/androidsdk-tools
Looks like we'll have two Go
Markus Koschany:
> On 26.03.2015 15:44, Hans-Christoph Steiner wrote:
> [...]
>> Yes, this definitely helps. The GSoC admins just need to see people
>> officially listed as mentors, then we can have more students
>>
>> I'm happy to do all the evaluations and
Miguel Landaeta:
> On Wed, Mar 25, 2015 at 02:31:02PM -0400, Hans-Christoph Steiner wrote:
>>
>> [...]
>>
>> I can say that an up-to-date gradle is one of my top priorities for this
>> work.
>
> I'm pretty sure help in this regard is more than welc
Markus Koschany:
> On 25.03.2015 15:22, Hans-Christoph Steiner wrote:
>>
>> Hey all,
>>
>> So there is a number of qualified students who are putting together
>> applications to work on Android Tools in Debian. Debian needs more people to
>> be a
Hey all,
So there is a number of qualified students who are putting together
applications to work on Android Tools in Debian. Debian needs more people to
be a Google Summer of Code (GSoC) co-mentor! This may be a little bit off
topic, but I think its relevant because the work includes updating
64 matches
Mail list logo
