Bug#1050889: ITP: turbine-java -- A header compiler for Java

2023-08-30 Thread Olek Wojnar
Package: wnpp
Severity: wishlist
Owner: Olek Wojnar 
X-Debbugs-Cc: debian-devel@lists.debian.org

* Package name: turbine-java
  Upstream Author : Google Inc. 
* URL : https://github.com/google/turbine
* License : Apache-2.0
  Programming Lang: Java
  Description : A header compiler for Java

 Used internally in the Bazel Build System.

This is required to package Bazel Java Tools which in turn is required to
package Bazel version 5.



Bug#1037260: ITP: plume-hashmap-util-java -- Plume-lib utility libraries for Java HashMaps

2023-06-09 Thread Olek Wojnar
Package: wnpp
Severity: wishlist
Owner: Olek Wojnar 
X-Debbugs-Cc: debian-devel@lists.debian.org

* Package name: plume-hashmap-util-java
  Version : 0.0.1
  Upstream Author : Michael Ernst 
* URL : https://github.com/plume-lib/hashmap-util
* License : GPL 2 with Classpath Exception
  Programming Lang: Java
  Description : Plume-lib utility libraries for Java HashMaps

 Hashmap Java utility libraries from the plume-lib project. These libraries are:
 Hasher, WeakHashMap, and WeakIdentityHashMap.

This package is needed to build the full Checker Framework package which is
in turn needed for Bazel version 5.



Bug#1035706: ITP: plume-util-java -- Plume-lib utility libraries for Java

2023-05-07 Thread Olek Wojnar
Package: wnpp
Severity: wishlist
Owner: Olek Wojnar 
X-Debbugs-Cc: debian-devel@lists.debian.org

* Package name: plume-util-java
  Version : 1.1.0
  Upstream Author : Michael Ernst 
* URL : https://github.com/plume-lib/plume-util
* License : MIT
  Programming Lang: Java
  Description : Plume-lib utility libraries for Java

 Various Java utility libraries from the plume-lib project. These include:
 collections and iterators, text processing, math, random selection,
 determinism and immutability, utility interfaces, and the JVM runtime system.

This package is needed to build the full Checker Framework package which is
in turn needed for Bazel version 5.



Bug#1035705: ITP: plume-reflection-util-java -- Utility libraries related to Java reflection

2023-05-07 Thread Olek Wojnar
Package: wnpp
Severity: wishlist
Owner: Olek Wojnar 
X-Debbugs-Cc: debian-devel@lists.debian.org

* Package name: plume-reflection-util-java
  Version : 0.2.2
  Upstream Author : Michael Ernst 
* URL : https://github.com/plume-lib/reflection-util
* License : MIT
  Programming Lang: Java
  Description : Utility libraries related to Java reflection

 Various utility libraries related to Java reflection from the plume-lib
 project.

This package is needed to build the full Checker Framework package which is
in turn needed for Bazel version 5.



Bug#1021949: ITP: zstd-jni-java -- JNI bindings for Zstd

2022-10-17 Thread Olek Wojnar
Package: wnpp
Severity: wishlist
Owner: Olek Wojnar 
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-j...@lists.debian.org

* Package name: zstd-jni-java
  Version : 1.5.0
  Upstream Author : Luben Karavelov 
* URL : https://github.com/luben/zstd-jni
* License : BSD
  Programming Lang: C, Java, Scale, C++
  Description : JNI bindings for Zstd
 Native library that provides a fast and high-compression lossless algorithm
 for Android, Java, and all JVM languages. It features static
 compress/decompress methods, implementation of InputStream and OutputStream
 for transparent compression of data streams fully compatible with the "zstd"
 program, and minimal performance overhead.

This package is required for Bazel version 5.0.0, it is not currently in
Debian, and therefore I am packaging it. :)



Re: Changed Github download URLs are affecting lots of existing watch files

2021-03-29 Thread Olek Wojnar
On Sun, Mar 28, 2021 at 2:42 AM Paul Wise  wrote:

>
> doing things. One option for doing this more optimally would be to add
> some code to vcswatch to extract debian/watch files from the Vcs-*
> repos and pass those to UDD, which could then run uscan with the VCS
> debian/watch files where they are newer than the package.
>

Nice, that sounds fairly non-intrusive!


> It might be interesting to look at how Fedora monitors new upstream
> releases.
>
> https://release-monitoring.org/
> https://fedoramagazine.org/how-fedora-monitors-upstream-releases/


Thanks for sharing that, the automated test build is a great feature! It
would be useful if maintainers could opt-in to using something like that
for specific packages.

-Olek


Bug#979846: ITP: bazel -- Tool to automate software builds and tests

2021-01-11 Thread Olek Wojnar
Package: wnpp
Severity: wishlist
Owner: Olek Wojnar 

* Package name: bazel
  Version : 3.5.1
  Upstream Author : Google Inc. 
* URL : https://github.com/bazelbuild/bazel
* License : Apache-2
  Programming Lang: Java and C++
  Description : Tool to automate software builds and tests
 Supported build tasks include running compilers and linkers to produce
 executable programs and libraries, and assembling deployable packages
 for Android, iOS and other target environments. Bazel is similar to
 other tools like Make, Ant, Gradle, Buck, Pants and Maven.



This package will effectively replace the bazel-bootstrap package which was
created to avoid circular build dependencies with Bazel. The bazel-bootstrap
package will likely remain in the archives as a means of adding Bazel support
to additional architectures in the future.



Bug#978669: ITP: bazel-skylib -- Skylib

2020-12-29 Thread Olek Wojnar
Package: wnpp
Severity: wishlist
Owner: Olek Wojnar 

* Package name: bazel-skylib
  Version : 1.0.3
  Upstream Author : Google Inc.
* URL : https://github.com/bazelbuild/bazel-skylib
* License : Apache-2
  Programming Lang: Starlark
  Description : Skylib
 Library of Starlark functions for manipulating collections, file paths, and
 various other data types in the domain of Bazel build rules.
 .
 Each of the .bzl files in the lib directory defines a "module" — a struct
 that contains a set of related functions and/or other symbols that can be
 loaded as a single unit, for convenience.
 .
 Skylib also provides build rules under the rules directory.


Bug#978668: ITP: bazel-stardoc -- Starlark Documentation Generator

2020-12-29 Thread Olek Wojnar
Package: wnpp
Severity: wishlist
Owner: Olek Wojnar 

* Package name: bazel-stardoc
  Version : 0.4.0
  Upstream Author : Google Inc.
* URL : https://github.com/bazelbuild/stardoc
* License : Apache-2
  Programming Lang: Starlark
  Description : Starlark Documentation Generator
 Documentation generator for Bazel build rules written in Starlark. Stardoc
 provides a Starlark rule that can be used to build documentation for Starlark
 rules in Markdown. Stardoc generates one documentation page per .bzl file.


*

This package is part of the Bazel Build System. If you would like to package
it, please joint the team at https://salsa.debian.org/bazel-team and upload
to the pre-made project for this package. Please contact us at
bazel-t...@lists.launchpad.net if you have any questions!

*



Bug#978665: ITP: bazel-rules-pkg -- Bazel package building & fetching rules

2020-12-29 Thread Olek Wojnar
Package: wnpp
Severity: wishlist
Owner: Olek Wojnar 

* Package name: bazel-rules-pkg
  Version : 0.3.0
  Upstream Author : Google Inc.
* URL : https://github.com/bazelbuild/rules_pkg
* License : Apache-2
  Programming Lang: Starlark
  Description : Bazel package building & fetching rules
 Bazel rules for packaging and fetching (for Debian and other distribution
 channels).


*

This package is part of the Bazel Build System. If you would like to package
it, please joint the team at https://salsa.debian.org/bazel-team and upload
to the pre-made project for this package. Please contact us at
bazel-t...@lists.launchpad.net if you have any questions!

*



Bug#978653: ITP: bazel-platforms -- Bazel Platforms

2020-12-29 Thread Olek Wojnar
Package: wnpp
Severity: wishlist
Owner: Olek Wojnar 

* Package name: bazel-platforms
  Version : 0.0.2
  Upstream Author : Google Inc.
* URL : https://github.com/bazelbuild/platforms
* License : Apache-2
  Programming Lang: Settings
  Description : Bazel Platforms
 All canonical constraint_setting()s, constraint_value()s and platform()s that
 are universally useful across languages and Bazel projects.


*

This package is part of the Bazel Build System. If you would like to package
it, please joint the team at https://salsa.debian.org/bazel-team and upload
to the pre-made project for this package. Please contact us at
bazel-t...@lists.launchpad.net if you have any questions!

*



Bug#978482: ITP: rx-java -- Reactive Extensions for the JVM

2020-12-27 Thread Olek Wojnar
Package: wnpp
Severity: wishlist
Owner: Olek Wojnar 

* Package name: rx-java
  Version : 3.0.7
  Upstream Author : David Karnok 
* URL : https://github.com/ReactiveX/RxJava
* License : Apache 2
  Programming Lang: Java
  Description : Reactive Extensions for the JVM
 Java VM implementation of Reactive Extensions: a library for composing
 asynchronous and event-based programs by using observable sequences.
 .
 It extends the observer pattern to support sequences of data/events and adds
 operators that allow you to compose sequences together declaratively while
 abstracting away concerns about things like low-level threading,
 synchronization, thread-safety and concurrent data structures.

This is a dependency of newer versions of Bazel.



Bug#963579: ITP: perfmark-java -- High Performance Tracing Library for Java

2020-06-23 Thread Olek Wojnar
Package: wnpp
Severity: wishlist
Owner: Olek Wojnar 

* Package name: perfmark-java
  Version : 0.19.0
  Upstream Author : Google LLC
* URL : https://github.com/perfmark/perfmark
* License : Apache
  Programming Lang: Java
  Description : High Performance Tracing Library for Java

 Low-overhead, manually-instrumented, tracing library for Java. Users can add
 the tracing function calls to their code to see how long each part takes.
 .
 Features
 .
 * Very Low Overhead: When enabled, tracing a function call adds about 70ns.
   Tracing is done in a lock-free, wait-free, thread local buffer, which
   avoids interfering with your latency-sensitive code.
 .
 * Dynamically Enabled: PerfMark can be enabled or disabled at runtime. When
   disabled, PerfMark has zero overhead, taking advantage of the JIT compiler
   to remove the tracing.
 .
 * Inter-thread Communication: Existing profilers have difficulty expressing
   which thread wakes up and executes work on another thread. PerfMark allows
   users to express this relationship explicitly, making for a clear picture
   of how code flows.
 .
 * Small Library Size: The PerfMark tracing API is only 5 KB in size, and has
   minimal dependencies making it easy to include in other projects. If no
   backend for recording the trace is present, the library safely disables
   itself.
 .
 * Multiple Java Versions: The PerfMark API supports Java 6, making it easy to
   include on older or constrained environments. Additionally, PerfMark
   includes optimized backends for Java 6, Java 7, and Java 9. Each of these
   backends is automatically loaded at runtime (if possible) and uses advanced
   JVM features for maximum speed.
 .
 * Chrome Trace Viewer Integration: PerfMark can export to the Chrome Trace
   Event Format, making it easy to view in your Web Browser.



Bug#962967: ITP: google-oauth-client-java -- Google OAuth Client Library for Java

2020-06-16 Thread Olek Wojnar
Package: wnpp
Severity: wishlist
Owner: Olek Wojnar 

* Package name: google-oauth-client-java
  Version : 1.27.0
  Upstream Author : Jeff Ching 
* URL : https://github.com/googleapis/google-oauth-java-client
* License : Apache-2.0
  Programming Lang: Java
  Description : Google OAuth Client Library for Java

Powerful and easy-to-use Java library for the OAuth 1.0a and OAuth 2.0
authorization standards. The Google OAuth Client Library for Java is designed
to work with any OAuth service on the web, not just with Google APIs. It is
built on the Google HTTP Client Library for Java.



Bug#962899: ITP: google-common-protos-java -- Google common protos for Java

2020-06-15 Thread Olek Wojnar
Package: wnpp
Severity: wishlist
Owner: Olek Wojnar 

* Package name: google-common-protos-java
  Version : 1.16.0
  Upstream Author : Google Inc.
* URL : https://github.com/googleapis/common-protos-java
* License : Apache-2.0
  Programming Lang: Java
  Description : Google common protos for Java

Protocol buffer types which are common dependencies throughout the Google API
ecosystem, generated for Java. The protobuf definitions for these generated
Java classes are provided in the googleapis repository.



Bug#962308: ITP: ceed-cpp -- CEED (CEGUI unified editor) port to C++ and Qt 5

2020-06-05 Thread Olek Wojnar
Package: wnpp
Severity: wishlist
Owner: Olek Wojnar 

* Package name: ceed-cpp
  Version : 1.0.0
  Upstream Author : Vladimir Orlov 
* URL : https://github.com/cegui/ceed-cpp
* License : GPL-3
  Programming Lang: C++
  Description : CEED (CEGUI unified editor) port to C++ and Qt 5

CEED C++ is a GPL3-licensed, cross-platform, C++ port of the (now unmaintained)
python CEED. It provides a multi-tab CEGUI layout designer and imageset editor.


**

The CEGUI package has been in Debian for years but it has limited usefulness
without a means of creating/modifying GUIs. This package does that. The
original version of CEED was written in Python, was messy, and was
unmaintained. This package addresses those shortcomings.



Bug#962082: ITP: escapevelocity-java -- A subset reimplementation of Apache Velocity with a much simpler API.

2020-06-02 Thread Olek Wojnar
Package: wnpp
Severity: wishlist
Owner: Olek Wojnar 

* Package name: escapevelocity-java
  Version : 0.9.1
  Upstream Author : Google, Inc.
* URL : https://github.com/google/escapevelocity
* License : Apache
  Programming Lang: Java
  Description : A subset reimplementation of Apache Velocity with a much 
simpler API.

EscapeVelocity is a templating engine that can be used from Java. It is a
reimplementation of a subset of functionality from Apache Velocity.
.
If EscapeVelocity successfully produces a result from a template evaluation,
that result should be the exact same string that Velocity produces. If not,
that is a bug.
.
EscapeVelocity has no facilities for HTML escaping and it is not appropriate
for producing HTML output that might include portions of untrusted input.



Re: Progress in preparing the Bazel Build System for Debian (COVID-19 Biohackathon follow-up)

2020-05-06 Thread Olek Wojnar
On Wed, May 6, 2020 at 11:23 AM Thorsten Glaser  wrote:

> Or perhaps we need a webpage or wiki page generated by parsing the
> Contents file and listing the matching Debian package for each class
> or, at least, Java package (unless split across multiple packages)…
>
> …
>
> …
>
> … I just volunteerd, didn’t I?
>

Sure sounds like it! Ha, ha! :)


Re: Progress in preparing the Bazel Build System for Debian (COVID-19 Biohackathon follow-up)

2020-05-06 Thread Olek Wojnar
Hi Emmanuel,

On Wed, May 6, 2020 at 10:03 AM Emmanuel Bourg  wrote:

>
> You can remove javax-annotation from the list, it's already packaged as
> libgeronimo-annotation-1.3-spec-java. Also error-prone and
> checker-framework provide annotations that are not required at runtime,
> patching them out is an option.
>

Excellent, thanks for the info! That's great news. Yes, I was considering
that if we couldn't get those packaged quickly. Those two are my lowest
priority for that reason. I already did something similar in a patch for
libprotobuf-java and it was reasonably painless.

Regarding the other generic dependencies, it would be nice to package
> them under the Java Team umbrella.
>

I absolutely agree but I didn't want to speak for the Java Team. :) I'll
pass that request on to any contributors I interact with.

-Olek


Progress in preparing the Bazel Build System for Debian (COVID-19 Biohackathon follow-up)

2020-05-05 Thread Olek Wojnar
Fellow Developers, Maintainers, and Contributors,

This is a quick update on recent progress with packaging the Bazel Build
System [1] for Debian. My involvement grew out of an urgent need for
TensorFlow that was identified during the recent COVID-19 Biohackathon
[2]. Upstream has been very supportive of our efforts and we have had
many positive interactions with them.

However, we've now reached a point where we need more help in order to
get these important tools packaged in a timely manner. There are
currently 10 Java package dependencies that are not available in Debian.
These are:
google-api-client
google-auth
google-auto
checker-framework
diffutils
error-prone
google-flogger
grpc-java
opencensus
javax-annotation

We have more information available, including links to RFP bugs, on our
Workplan wiki [3]. If you have Java experience and are willing to assist
in this effort, even packaging one of these would be a great help. If
you also want to help with the main Bazel-packaging effort, please feel
free to join the team!

Stay safe out there!


-Olek

PS I am not subscribed to -science or -java

[1] https://bazel.build/
[2] https://salsa.debian.org/med-team/community/2020-covid19-hackathon
[3] https://salsa.debian.org/bazel-team/meta/-/wikis/Workplan-Part-1



signature.asc
Description: OpenPGP digital signature


Re: Bug#799748: ITP: ember -- 3D client framework for the WorldForge project

2015-09-22 Thread Olek Wojnar

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Simon,

You bring up some very good points and those are very fair questions.

On 09/22/2015 12:45 PM, Tobias Frost wrote:
| Am Dienstag, den 22.09.2015, 08:19 +0100 schrieb Simon McVittie:
|> After those problems have been corrected, will you continue to
|> maintain
|> ember and the rest of the WorldForge-related packages in the longer
|> term, and ensure that they do not become a burden to other
|> developers? I

Yes, that is my intention.

|> ask because in the 16 years that ember was in the archive, it had a
|> total of 7 uploads, of which 2 NMUs and at least 3 maintainer uploads
|> were to fix release-critical bugs. That isn't a particularly good
|> ratio
|> of maintainer's time used : other people's time used.

That is very true, and I completely agree with you that Debian would be
unsustainable if all (or even a significant fraction of) packages had
this kind of track record.

|> This is not intended as a veto - hopefully you'll have more time for
|> it
|> than its previous maintainers - but I felt that before it is
|> reintroduced, I should specifically point out that every time a
|> package
|> fails to build from source or is otherwise RC-buggy, and every time
|> it
|> blocks a transition, it is creating work for people other than its
|> maintainer.

Yes, very true. I always try to do a quality job on anything I set my
mind to. I can't promise that all my uploads will be perfect, but I am
aware of the work that falls on others when a package is sub-standard
and I do not like others to have to do my work for me.

|> While team maintenance is of course A Good Thing, I'm not sure that
|> having "the games team" as a co-maintainer mitigates this very much;
|> the
|> wide range of game technologies and styles maintained by that team
|> mean
|> that it is relatively unlikely that a random games-team member knows
|> how
|> to fix and test a random games-team package (or indeed has any
|> interest
|> in that random package).

True, and the WorldForge packages are not exactly simple. I believe that
I can only safely count on Games Team support if an urgent fix is
required, the fix is simple, and I'm temporarily unavailable for
whatever reason. Obviously, anything more is a bonus. :) That's not
meant to be disparaging to my fellow Games Team members but I know that
they are all busy maintaining their own packages as well. I don't want
these packages to be a burden on the Games Team just like I don't want
them to be a burden on Debian resources at large.

|> Based on the history of ember and its dependencies, it seems fairly
|> likely that developers with an interest in the archive as a whole (QA
|> team, release team, ftpmasters) will respond to any RC bugs that
|> aren't
|> fixed promptly by just removing it again.

Well, I aim to maintain them in such a way that this does not become
necessary. :) It's not exactly a secret that I've had a strong interest
in Debian's success since I started using it in...oh, late 90s sometime.
Recently I have been trying to give back and I hope to apply to be a DM
soon... maybe a DD eventually, if my contributions are deemed
worthwhile. ;) I mention this to clarify that my involvement with the
WorldForge packages is not just a passing whim but part of my commitment
to help Debian overall.

I hope that assuages your concerns!

| Hi Simon,
|
| Maybe I chime in..
| I'm in contact with Olek since a while regarding the ecosystem around
| ember and the wf libraries. I also volunteered to sponsor his work and
| the first uploads are currently being prepared.
|
| Yes, the former maintainer was, lets say, problematic, a kind of 51th
| shade of MIA. (Responding to pings, promising actions soon, but in the
| end nothing happened) This was the main blocker here and Olek didn't
| want to offend the maintainer, despite that the packages were de-facto
| unmaintained.
| So this is the right point of time to get those packages a good
| restart, with Olek as maintainer, even if I see another 51th-shade of
| MIA in the way -- down the road. (Therefore I would be interested in
| general guidance how to handle such pseudo-MIA or selective-MIA: Cases
| where the maintainer is active, but still nothing happens at least on
| certain packages, even after prodding.)
|
| I'm confident that Olek will maintain the packages adequately.
| If not, removal bugs can still be filed, but I prefer to give him the
| opportunity to show.
|
| --
| tobi

Thanks for the support, Tobi! :)

- -Olek

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJWAkUeAAoJEH2D1AagncHkoVkP/RzZFY5mQykl9Actw4LrTr/B
F2/XneXSIAd0vMz7SkKhYme6C5d9ozqAjU5vJkmjytLAWdw38JKCC+5tzI3CMkRd
B+GxgRDJ3zr8Lz7WjyA2FzIngh8EhP+9HW/8EJR2ftq93K+KXjtNpFwxuxiaNsvk
I5ONsY6e3JI3t0A6lBWyms5BcEkSmW99EoYbmnBL+n8mYt+TQGjdK4LZufZyJY7X
+xS0kcbeH2toq60rAFKIYpDNQawCj4eXGxWdAqph6OipXNaCZPrfzR4zkVwGZ0Jy
V614f7W4od5Tr8x504ETR9O3Xh55M9ywYLyR4hl/6nuDEAsoKxL7vHszZkaAAJL1
WDlNes2D5ZlUiSoLR1jjQQfpIY/X4YnEeIFQkX

Bug#799749: ITP: eris -- WorldForge Client Entity Library

2015-09-21 Thread Olek Wojnar
Package: wnpp
Severity: wishlist
Owner: Olek Wojnar 

* Package name: eris
  Version : 1.3.23
  Upstream Author : WorldForge Project 
* URL : http://www.worldforge.org/
* License : GPL
  Programming Lang: C++
  Description : WorldForge Client Entity Library

This package is being reintroduced into Debian. It was previously maintained
by the Games Team and will continue to be maintained that way. It was removed 
by Bug #777842 due to the GCC 5 transition. The problems that caused it to be
removed will be corrected before it is uploaded again.



Bug#799748: ITP: ember -- 3D client framework for the WorldForge project

2015-09-21 Thread Olek Wojnar
Package: wnpp
Severity: wishlist
Owner: Olek Wojnar 

* Package name: ember
  Version : 0.7.2.1
  Upstream Author : WorldForge Project 
* URL : http://www.worldforge.org/
* License : GPL
  Programming Lang: C++   
  Description : 3D client framework for the WorldForge project

This package is being reintroduced into Debian. It was previously maintained
by the Games Team and will continue to be maintained that way. It was removed 
by Bugs #797418, #563768, #682332, #760058 due to the GCC 5 transition. The
problems that caused it to be removed will be corrected before it is uploaded
again.



Bug#799746: ITP: libwfut -- WorldForge Update Tool

2015-09-21 Thread Olek Wojnar
Package: wnpp
Severity: wishlist
Owner: Olek Wojnar 

* Package name: libwfut
  Version : 0.2.3
  Upstream Author : WorldForge Project 
* URL : http://www.worldforge.org/
* License : GPL
  Programming Lang: C++
  Description : WorldForge Update Tool

This package is being reintroduced into Debian. It was previously maintained
by the Games Team and will continue to be maintained that way. It was removed
by Bug #777977 due to the GCC 5 transition. The problems that caused it to be
removed will be corrected before it is uploaded again.