Package: wnpp
Severity: wishlist
Owner: Olek Wojnar
X-Debbugs-Cc: debian-de...@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
Control: retitle -1 Please upgrade Bazel to version 5.0.0
Hi Daniel and thank you for your interest in the Debian Bazel package!
On 2/5/23 04:05, Daniel Baumann wrote:
retitle 1021950 update to current LTS version (6.0)
thanks
Sorry for not noticing this sooner but this bug is for tracking
Update: Upstream has agreed to release a new version which should
address the issues of the aging codebase. Therefore, my current
inclination is to continue to provide this package.
I'll keep this bug open for now in case anyone else would like to weigh
in with opinions.
-Olek
Control: tag -1 unreproducible
Control: severity -1 important
Hello Lucas and thanks for the bug report. Unfortunately, I am unable to
reproduce this behavior. I just uploaded a new version of this package
to fix an unrelated bug and it built normally on the buildds.
I'm leaving this as
Control: tag -1 pending
Hi Lucas and thanks for the bug report!
On 7/26/23 16:23, Lucas Nussbaum wrote:
During a rebuild of all packages in sid, your package failed to build
on amd64.
Fixed and will be uploading shortly.
-Olek
OpenPGP_signature
Description: OpenPGP digital signature
Control: tag -1 + moreinfo
On 6/18/23 11:55, Simon McVittie wrote:
While opening bugs for packages that depend on libsdl1.2, I noticed
that cegui-mk2 seems to be a library that is not depended on by anything
in Debian. Is it still useful to have in the distribution?
That's a very fair
Package: wnpp
Severity: wishlist
Owner: Olek Wojnar
X-Debbugs-Cc: debian-de...@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
Control: tag -1 - moreinfo
Hi Paul,
On Thu, Jun 8, 2023 at 6:56 AM Paul Gevers wrote:
I reworded a tiny bit and added markup. Please review the merge request
I just reviewed it and it looks good. In the future, and now that I see
how your process works, I'll do the MR myself to save
21:28, Olek Wojnar wrote:
If possible, please include the following in section 2.2 (What's new
in the
distribution?) of the release notes for the following architectures:
amd64, arm64, ppc64el, s390x, ppc64, riscv64
2.2.x Initial availability of the Bazel build system
The [Bazel](https
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: rm
Severity: normal
As explained by upstream [1], the entire WorldForge project is
constantly changing and does not anticipate a stable software release in
the foreseeable future. The end-user binaries, the server
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: rm
Severity: normal
As explained by upstream [1], the entire WorldForge project is
constantly changing and does not anticipate a stable software release in
the foreseeable future. The end-user binaries, the server
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: rm
Severity: normal
As explained by upstream [1], the entire WorldForge project is
constantly changing and does not anticipate a stable software release in
the foreseeable future. The end-user binaries, the server
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: rm
Severity: normal
As explained by upstream [1], the entire WorldForge project is
constantly changing and does not anticipate a stable software release in
the foreseeable future. The end-user binaries, the server
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: rm
Severity: normal
As explained by upstream [1], the entire WorldForge project is
constantly changing and does not anticipate a stable software release in
the foreseeable future. The end-user binaries, the server
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: rm
Severity: normal
As explained by upstream [1], the entire WorldForge project is
constantly changing and does not anticipate a stable software release in
the foreseeable future. The end-user binaries, the server
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: rm
Severity: normal
As explained by upstream [1], the entire WorldForge project is
constantly changing and does not anticipate a stable software release in
the foreseeable future. The end-user binaries, the server
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: rm
Severity: normal
As explained by upstream [1], the entire WorldForge project is
constantly changing and does not anticipate a stable software release in
the foreseeable future. The end-user binaries, the server
Control: tag -1 pending
Thanks for letting me know about the impending removal and the suggested
fix!
On 5/14/23 10:04, Markus Koschany wrote:
Control: tags -1 patch
Hi,
bazel-bootstrap already build-depends on libgeronimo-annotation-1.3-spec-java.
The fix is trivial. Patch is attached.
Package: wnpp
Severity: wishlist
Owner: Olek Wojnar
X-Debbugs-Cc: debian-de...@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
Package: wnpp
Severity: wishlist
Owner: Olek Wojnar
X-Debbugs-Cc: debian-de...@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
Hi Adrian,
On March 3, 2023 11:02:53 AM UTC, Adrian Bunk wrote:
>On Thu, Mar 02, 2023 at 12:44:42AM -0500, Olek Wojnar wrote:
>>...
>> I disabled mips64el leading up to the soft freeze since -4 was not building
>> correctly at that time on that architecture. Lacking the ti
Hi and thanks for the bug report.
I disabled mips64el leading up to the soft freeze since -4 was not
building correctly at that time on that architecture. Lacking the time
to troubleshoot, I made the decision to sacrifice the one problem
architecture in favor of all the others that were
Hi Adam,
On 2/4/23 13:11, Adam D. Barratt wrote:
Control: tags -1 + confirmed
On Sun, 2023-01-29 at 20:28 -0500, Olek Wojnar wrote:
The phyx package incorrectly declares a Build Dependency on the
libatlas-cpp-0.6-dev package. The src:atlas-cpp package is obsolete
since the
only packages
upload
+ * Remove erroneous Build Dependency on libatlas-cpp
+- libatlas-cpp is completely unrelated to phyx and phyx does not use it
+- The BD was added accidentally and needs to be removed for proper
+ dependency resolution
+
+ -- Olek Wojnar Sun, 29 Jan 2023 18:27:53 -0500
+
phyx
Control: tag -1 confirmed help
Hi and thanks for the bug report.
On 1/28/23 12:01, Adrian Bunk wrote:
Source: bazel-bootstrap
Version: 4.2.3+ds-2
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/amd64/b/bazel-bootstrap/30777521/log.gz
OpenJDK 64-Bit Server VM warning:
Hi there,
On 1/4/23 09:51, Gianfranco Costamagna wrote:
Hello, FWIW I think I crafted a patch that might fix the issue (in a
ugly and hard-coded way)
Thanks! It's always good to have options.
---
bazel-bootstrap-4.2.3+ds.orig/tools/distributions/debian/debian_cc.BUILD
+++
Control: reopen -1
Control: found -1 1.51.1-3
Control: block 1027112 by -1
Control: affects -1 bazel-bootstrap
Hi László,
I noticed that you added some linker flags in a recent commit to grpc
[1]. However, it appears that this one is still missing:
-labsl_synchronization
Having spent some
Control: tag -1 moreinfo
Hi Sebastian and thanks for the bug report.
On 12/27/22 18:15, Sebastian Ramacher wrote:
Source: bazel-bootstrap
Version: 4.2.3+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc:
Control: tag -1 pending
Hi Andreas and thanks for the report!
On 12/22/22 11:29, Andreas Beckmann wrote:
libgoogle-auto-common-java ships two dubious files that should probably
not be in the package at all:
/usr/share/maven-repo/build-only/build-only/NO_VERSION/build-only-NO_VERSION.pom
Hi there,
I just had a quick look at the source code. The problem are the vendored
headers in the dependencies/ folder. Per debian policy they need to be
packaged themselves.
I was just looking at this package as well and I was a bit confused by
your comment. What exactly are you seeing in
Package: ftp.debian.org
Severity: normal
Hello,
This is a follow-up to [1], apologies for not mentioning experimental in that
report.
Thanks!
-Olek
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024116
Hi Salvatore,
On Sat, Nov 19, 2022, 15:26 Salvatore Bonaccorso wrote:
>
> It was removed from unstable, but should it be removed as well from
> experimental?
>
Yes! And I thought it would be... Then again, this is the first time I've
gone through the removal process. Perhaps I should have
Control: tags -1 - moreinfo
On Mon, Nov 14, 2022, 21:22 Olek Wojnar wrote:
>
> I'll remove the tag once the upload is complete.
>
Upload complete
>
Hi Scott,
On 11/14/22 20:19, Scott Kitterman wrote:
Checking reverse dependencies...
# Broken Build-Depends:
phyx: libatlas-cpp-0.6-dev
Phyx build-dependency will have to be addressed first. Please remove the
moreinfo tag once that's complete.
Thanks for pointing this out! This is a
Package: ftp.debian.org
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Upstream agrees with removal: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=950926#49
-BEGIN PGP SIGNATURE-
iQJEBAEBCgAuFiEELejiDiSiH9jtG0ynfYPUBqCdweQFAmNy1zcQHG9sZWtAZGVi
Package: ftp.debian.org
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Upstream agrees with removal: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=950926#49
-BEGIN PGP SIGNATURE-
iQJEBAEBCgAuFiEELejiDiSiH9jtG0ynfYPUBqCdweQFAmNy1xwQHG9sZWtAZGVi
Package: ftp.debian.org
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Upstream agrees with removal: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=950926#49
-BEGIN PGP SIGNATURE-
iQJEBAEBCgAuFiEELejiDiSiH9jtG0ynfYPUBqCdweQFAmNy1wgQHG9sZWtAZGVi
Package: ftp.debian.org
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Upstream agrees with removal: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=950926#49
-BEGIN PGP SIGNATURE-
iQJEBAEBCgAuFiEELejiDiSiH9jtG0ynfYPUBqCdweQFAmNy1vAQHG9sZWtAZGVi
Package: ftp.debian.org
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Upstream agrees with removal: \https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=950926#49
-BEGIN PGP SIGNATURE-
iQJEBAEBCgAuFiEELejiDiSiH9jtG0ynfYPUBqCdweQFAmNy1swQHG9sZWtAZGVi
Package: ftp.debian.org
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Upstream agrees with removal: \https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=950926#49
-BEGIN PGP SIGNATURE-
iQJEBAEBCgAuFiEELejiDiSiH9jtG0ynfYPUBqCdweQFAmNy1ocQHG9sZWtAZGVi
Package: ftp.debian.org
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Upstream agrees with removal: \https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=950926#49
-BEGIN PGP SIGNATURE-
iQJEBAEBCgAuFiEELejiDiSiH9jtG0ynfYPUBqCdweQFAmNy1i8QHG9sZWtAZGVi
Package: ftp.debian.org
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Upstream agrees with removal: \https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=950926#49
-BEGIN PGP SIGNATURE-
iQJEBAEBCgAuFiEELejiDiSiH9jtG0ynfYPUBqCdweQFAmNy1hkQHG9sZWtAZGVi
Package: ftp.debian.org
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Upstream agrees with removal: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=950926#49
-BEGIN PGP SIGNATURE-
iQJEBAEBCgAuFiEELejiDiSiH9jtG0ynfYPUBqCdweQFAmNy1dQQHG9sZWtAZGVi
Package: ftp.debian.org
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Upstream agrees with removal: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=950926#49
-BEGIN PGP SIGNATURE-
iQJEBAEBCgAuFiEELejiDiSiH9jtG0ynfYPUBqCdweQFAmNy1EgQHG9sZWtAZGVi
Hello everyone,
On Fri, Nov 11, 2022 at 11:27 AM Zitchas Z wrote:
Good day Michael, Job, Damyan, and the Debian games team,
I think we may have a person or two familiar with Debian. I will
bring this up with the community and see if we're can find someone
interested in doing this.
Source: bazel-bootstrap
Version: 4.2.2+ds-1
Severity: serious
Tags: ftbfs upstream
Forwarded: https://github.com/bazelbuild/bazel/issues/15831
The default use of OpenJDK 17 causes bazel-bootstrap to FTBFS. This is an
upstream issue and upstream's fix[1] should be cherry-picked as soon as
Control: tags -1 confirmed
Hi László,
On 11/5/22 08:50, László Böszörményi (GCS) wrote:
I would like to start the Protobuf transition. Your package fails to
build since it tries to include a header which is moved to a new name.
Simple patch is attached to update this.
Please be prepared to
Package: lintian
Version: 2.115.3
Severity: normal
Dear Maintainer,
While performing an initial build for libzstd-jni-java I discovered that
lintian was giving a false positive for the package. I verified manually
that the jar file is named correctly. My package uses an upstream
versioning
Source: bazel-bootstrap
Version: 4.2.2+ds-1
Severity: wishlist
Bazel Team,
The 4.x series of Bazel is rather old at this point and there have been
significant improvements in the 5.x series. Some of those improvements will
have a direct and positive impact on ease of packaging, ease of use, and
Package: wnpp
Severity: wishlist
Owner: Olek Wojnar
X-Debbugs-Cc: debian-de...@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
Source: rx-java
Version: 3.0.7+ds-2
Severity: wishlist
Tags: newcomer
Dear Prospective Debian Bazel contributor,
This package needs to be updated for the Bazel 5.x release. This *should* be
a fairly straightforward process. If you are interested, please send an email
to our mailing list [1]
Source: grpc-java
Version: 1.26.0+ds-1
Severity: wishlist
Tags: help
Dear Prospective Debian Bazel contributor,
This package needs to be updated for the Bazel 5.x release. This will likely
*NOT* be a straightforward process. If you are interested, please send an email
to our mailing list [1]
Source: checker-framework-java
Version: 3.0.1+ds2-3
Severity: wishlist
Tags: newcomer
Dear Prospective Debian Bazel contributor,
This package needs to be updated for the Bazel 5.x release. This *should* be
a fairly straightforward process. If you are interested, please send an email
to our
Source: google-auto-value-java
Version: 1.7.2-2
Severity: wishlist
Tags: newcomer
Dear Prospective Debian Bazel contributor,
This package needs to be updated for the Bazel 5.x release. This *should* be
a fairly straightforward process. If you are interested, please send an email
to our mailing
Source: google-auto-common-java
Version: 0.10-2
Severity: wishlist
Tags: newcomer
Dear Prospective Debian Bazel contributor,
This package needs to be updated for the Bazel 5.x release. This *should* be
a fairly straightforward process. If you are interested, please send an email
to our mailing
Thanks again for the VERY quick response!
On 10/9/22 15:50, Paul Gevers wrote:
Pardon my ignorance of the finer points of autopkgtest but is there a
way to get more-verbose logging?
I started it with --shell-fail. That gave me a shell on the first test
that failed and I could then easily
Hi Paul,
Thanks for the quick reply and the troubleshooting!
On 10/6/22 16:14, Paul Gevers wrote:
Hi Olek,
On 06-10-2022 22:05, Paul Gevers wrote:
On 06-10-2022 21:38, Olek Wojnar wrote:
It's entirely possible that this is also a problem in may package,
which is
why I have the test suite
Package: autopkgtest
Version: 5.25
Severity: normal
Dear Maintainer,
I noticed some autopkgtest failures [1][2][3] in a recent package upload. I
also noticed that the amd64 build [4] was consistently successful. In
addition, the autopkgtest that I run automatically during my build process
(also
If it helps, the empty directory tag from lintian is:
https://lintian.debian.org/tags/package-contains-empty-directory
I'm not sure how many, if any, of the packages currently triggering the
tag are related to this bug in mk-origtargz.
OpenPGP_signature
Description: OpenPGP digital signature
Package: devscripts
Version: 2.22.2
Severity: normal
Dear Maintainer,
While using the Files-Included functionality for the first time, I noticed
that linitian was giving me errors about empty directories in my package.
Upon investigation, I realized that the Files-Included process was only
Control: tag -1 = confirmed
Thanks for reminding me about this bug, tobi! I guess a lot has been
happening since February of 2020
On 8/27/22 08:11, Tobias Frost wrote:
> User: tobi-rm-proposals@d.o
> Usertags: rm-proposal
>
> (FTR, I also don't think that snap/flatpak/appimage should be
Hi Petter,
On Wed, Nov 3, 2021 at 7:13 PM Petter Reinholdtsen wrote:
> Hi,
>
> Any news on getting Teensorflow through the NEW queue?
>
I'm afraid not. The NEW queue is quite huge at the moment. We've had a
pretty trivial (but progress-blocking) update to bazel-bootstrap sitting
there for over
Markus,
Sorry for the slow reply, it has been an extraordinarily crazy time over
here recently. I'm barely keeping up on emails but I'm hoping that things
quiet down a little in the coming weeks and allow me to catch up. This is
near the top of my list!
-Olek
On Fri, Oct 22, 2021 at 6:41 AM
Hi
On Wed, Sep 15, 2021, 22:36 Sandro Tosi wrote:
> > I've moved the package under the games-team [1]. I was going to give you
> > access to it but I can't find a Salsa account for you. If you don't have
> an
> > account yet, you can easily create one [2] and let me know your username.
> > I'll
Package: release-notes
Severity: normal
Dear Release Team,
If possible, please include the following in section 2.2 (What's new in the
distribution?) of the release notes for the following architectures:
amd64, arm64, ppc64el, s390x, ppc64, riscv64
2.2.x Initial availability of the Bazel
Control: tag -1 confirmed
Thanks for the fix! Looks good and I appreciate you committing to VCS as
well. I will definitely include this on my next upload (after freeze).
Hi smcv,
On Sun, Jun 13, 2021 at 6:43 PM Simon McVittie wrote:
>
> On Sun, 13 Jun 2021 at 22:18:42 +0200, Jochen Sprickerhof wrote:
> > * Olek Wojnar [2021-06-13 15:15]:
>
> some API designs make it
> really hard to keep backwards compatibility, because a lot of int
Hi Jochen,
First of all, thank you very much for taking the time to fix those issues!
And an extra thank you for speaking with the release team already! I always
get very nervous with significant package changes this close to a release.
Are you also planning to file an unblock bug or would you
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Dear Release Team,
Please unblock package google-oauth-client-java
[ Reason ]
Backport of fix for RC security issue (CVE-2020-7692)
Control: tag -1 + confirmed
Thanks for the bug report, Moritz!
Sorry for the delay, apparently I was not receiving emails about the
google-oauth-client-java package. I will work to get this fixed today.
-Olek
OpenPGP_signature
Description: OpenPGP digital signature
Hi Matthias,
On Thu, Mar 4, 2021 at 5:02 AM Matthias Klose wrote:
>
> Debian has porter boxes ... please build with the proposed patch and
> check if
> your bootstrap works. You can run the just built jdk from the build
> location.
>
Thanks for the suggestion! Ideally, I would love to
So this bug is definitely not RC but would it be possible to get a fix for
it into bullseye? This seems like something that would be good to fix
before that release is stable.
Thanks in advance!
-Olek
Package: openjdk-11-jre-headless
Version: 11.0.11+4-1
Severity: important
Tags: patch
Control: affects -1 bazel-bootstrap
Dear OpenJDK Maintainers,
This bug report is a follow-up to the email discussion [1] about how OpenJDK
does not correctly delete directories on mips64el. The Bazel team
Hello Simon and other interested parties,
On Sat, 28 Nov 2020 12:28:16 +0100 Simon Ruderich
wrote:
>
> is the problem because blhc requires a space after each flag. I
> know this handling is not perfect but parsing arbitrary shell
> commands is difficult.
I have run into this exact issue with
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
Package: reportbug
Version: 7.9.0
Severity: normal
Dear reportbug Maintainers,
I've noticed that when filing WNPP bugs for new packages, reportbug does not
clearly identify if there is a previous WNPP bug for that (new) package.
Instead, it seems to just return all WNPP bugs.
Expected behavior:
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
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
Package: wnpp
Severity: wishlist
* Package name: bazel-rules-proto
Version : Pending
Upstream Author : Google Inc.
* URL : https://github.com/bazelbuild/rules_proto
* License : Apache-2
Programming Lang: Starlark
Description : Protobuf Rules for Bazel
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: wnpp
Severity: wishlist
* Package name: bazel-rules-java
Version : 0.1.1
Upstream Author : Google Inc.
* URL : https://github.com/bazelbuild/rules_java
* License : Apache-2
Programming Lang: Starlark
Description : Java Rules for Bazel
*
Package: wnpp
Severity: wishlist
* Package name: bazel-rules-cc
Version : pending
Upstream Author : Google Inc.
* URL : https://github.com/bazelbuild/rules_cc
* License : Apache-2
Programming Lang: Starlark
Description : C++ rules for Bazel
Starlark
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
Package: wnpp
Severity: wishlist
* Package name: bazel-java-tools
Version : 10.5
Upstream Author : Google Inc.
* URL : https://github.com/bazelbuild/java_tools
* License : Apache-2
Programming Lang: Java
Description : Bazel Tools for Java
Tools used by
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
Hi reprotest maintainers,
I'd like to point out that an additional impact of this bug is that it
results in failures for packages that are designed to build on amd64 but
not on i386. For example, bazel-bootstrap supports 64-bit processors but
(currently) does not support 32-bit processors. This
The initial bazel-bootstrap package is now in Debian and we could really
use a public forum to discuss issues with both further Bazel packaging and
with packaging of software that uses Bazel to build.
Please consider creating this mailing list so that we can have these
technical discussions in a
Package: wnpp
Severity: wishlist
* Package name: bazel-platforms
Version : Latest
Upstream Author : Google
* URL : https://github.com/bazelbuild/platforms
* License : Apache
Programming Lang: Configuration data
Description : Bazel platforms values
All
Package: wnpp
Severity: wishlist
* Package name: bazel-java-tools
Version : javac14_v1.0
Upstream Author : Google
* URL : https://github.com/bazelbuild/java_tools
* License : Apache
Programming Lang: C++ and Java
Description : Bazel Tools for Java
The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I don't have the time to package this but I am interested in it and I would
be happy to mentor/sponsor someone who wanted to work on it.
- -Olek
On 2020-08-16 at 03:08, deb...@emorrp1.name wrote:
> Package: wnpp
> Severity: wishlist
>
> * Package
I'd like to add that this issue often comes up in Java packages as well,
for similar directory structure reasons. For example,
O: libgoogle-flogger-java: [90mrepeated-path-segment [0m flogger
usr/share/maven-repo/com/google/flogger/flogger/0.5.1/
O: libgoogle-flogger-java:
Hi Felix,
First of all, apologies for accidentally replying to the wrong email
before. Sending to the bug email now.
On Wed, Aug 12, 2020 at 2:26 AM Olek Wojnar wrote:
> Hi Felix,
>
> On Tue, Aug 11, 2020 at 7:35 AM Felix Lechner
> wrote:
>
>> Hi Olek,
>>
>&g
Package: lintian
Version: 2.62.0
Severity: normal
Dear Maintainer,
Lintian currently emits an arch-dependent-file-in-usr-share error when it sees
an "ar" file within usr/share. Based on the description, it seems that lintian
assumes that this is a static library. However, it gives the same error
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
Hi Matthias,
Thanks for the bug report!
On Thu, Jun 18, 2020, 08:21 Matthias Klose wrote:
>
> Mark one more symbol as optional when building with -march=z13 on s390x
>
Per a discussion regarding CEGUI, I'm actually eliminating symbols files
from my C++ libraries, at least in the near term. I
Hi Sudip,
On Wed, Jun 17, 2020, 13:38 Sudip Mukherjee
wrote:
>
> That was easy. I have pushed my changes to "sudip" which now builds
> only those two.
>
Great, thanks!
And, just noticed (after pushing) that the Vcs in d/control is wrong.
> It should be
On Wed, Jun 17, 2020 at 12:19 PM Andreas Tille wrote:
> I have the feeling we are coming closer to a solution iteratively now
> but there are some remaining errors unfortunately:
>
If any of you have a moment, I recommend patching the main pom.xml to only
build the two modules that we need
Hi tony,
On Wed, Jun 17, 2020 at 12:39 AM tony mancill wrote:
>
> I've pushed a "tmancill" branch to the Salsa repo that gets us further
>
Thanks!
> along. At this point, the build is failing with this error:
>
>package com.google.api.client.util does not exist
>
> This Java package
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
Hi Andreas,
On Tue, Jun 16, 2020 at 4:15 AM Andreas Tille wrote:
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [ERROR] Non-resolvable import POM: Cannot access central (
> https://repo.maven.apache.org/maven2) in offline mode and the artifact
>
1 - 100 of 212 matches
Mail list logo
