Debian Bug report logs - #782654
ITP: bazel -- Fast and correct automated build system by Google

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Kyle Moffett <kyle@moffetthome.net>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: ITP: bazel -- Fast and correct automated build system by Google

Date: Wed, 15 Apr 2015 10:33:11 -0700

X-Debbugs-Cc: debian-devel@lists.debian.org
Package: wnpp
Severity: wishlist
Owner: Kyle Moffett <kyle@moffetthome.net>

* Package name    : bazel
  Version         : 0~pre20150410-cc4463-1  (No upstream release yet)
  Upstream Author : Google
* URL             : http://bazel.io/
* License         : Apache License 2.0
  Programming Lang: Java and C++
  Description     : Fast and correct automated build system by Google

{Fast, Correct} - Choose two

Bazel is a build tool that builds code quickly and reliably. It is used to
build the majority of Google's software, and thus it has been designed to
handle build problems present in Google's development environment, including:

 * A massive, shared code repository, in which all software is built from
   source. Bazel has been built for speed, using both caching and parallelism
   to achieve this. Bazel is critical to Google's ability to continue to scale
   its software development practices as the company grows.

 * An emphasis on automated testing and releases. Bazel has been built for
   correctness and reproducibility, meaning that a build performed on a
   continuous build machine or in a release pipeline will generate
   bitwise-identical outputs to those generated on a developer's machine.

 * Language and platform diversity. Bazel's architecture is general enough to
   support many different programming languages within Google, and can be used
   to build both client and server software targeting multiple architectures
   from the same underlying codebase.

Message #10 received at 782654@bugs.debian.org (full text, mbox, reply):

From: Kyle Moffett <kyle@moffetthome.net>

To: 782654@bugs.debian.org

Subject: Re: ITP: bazel -- Fast and correct automated build system by Google

Date: Wed, 15 Apr 2015 10:54:30 -0700

On Wed, Apr 15, 2015 at 10:33 AM, Kyle Moffett <kyle@moffetthome.net> wrote:
> * Package name    : bazel
>   Version         : 0~pre20150410-cc4463-1  (No upstream release yet)
>   Upstream Author : Google
> * URL             : http://bazel.io/
> * License         : Apache License 2.0
>   Programming Lang: Java and C++
>   Description     : Fast and correct automated build system by Google

From discussions with upstream, some of Bazel's design may need to be
tweaked to interoperate well with distro requirements (like Debian).
They currently pack everything up into a single self-extracting
archive, with most libraries statically linked, which violates Debian
Policy, but they are definitely interested in making things compatible
with distro packaging:
  https://groups.google.com/forum/#!topic/bazel-dev/YIp70JgOksI

I have some patches and WIP packaging prepared here:
  https://github.com/kmoffett/bazel

Cheers,
Kyle Moffett

Message #17 received at 782654@bugs.debian.org (full text, mbox, reply):

From: lumin <cdluminate@gmail.com>

To: 782654@bugs.debian.org

Cc: kyle@moffetthome.net

Subject: [ITP:bazel] looking forward to this package

Date: Wed, 02 Dec 2015 14:49:04 +0000

Thank you for working on this software, I may need it in the future :-)

Message #24 received at 782654@bugs.debian.org (full text, mbox, reply):

From: Chris Lamb <lamby@debian.org>

To: 782654@bugs.debian.org, 838416@bugs.debian.org

Cc: Kyle Moffett <kyle@moffetthome.net>

Subject: Re: ITP: bazel -- Fast and correct automated build system by Google

Date: Fri, 23 Sep 2016 16:03:26 +0100

block 782654 by 838416
thanks

Hi,

> ITP: bazel -- Fast and correct automated build system by Google

Need this for #838416, "ITP: roughtime -- Secure time synchronisation" :)

Can you update on the latest status?


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org / chris-lamb.co.uk
       `-

Message #35 received at 782654@bugs.debian.org (full text, mbox, reply):

From: Nicolas Braud-Santoni <nicolas@braud-santoni.eu>

To: Chris Lamb <lamby@debian.org>

Cc: 782654@bugs.debian.org, 838416@bugs.debian.org, Kyle Moffett <kyle@moffetthome.net>

Subject: Re: ITP: bazel -- Fast and correct automated build system by Google

Date: Mon, 3 Oct 2016 15:40:37 +0200

[Message part 1 (text/plain, inline)]

unblock 782654 by 838416
block 838416 by 782654
thanks

Hi lamby,

I think you swapped the blocker and blockee there.

Also, I would be pretty keen on seeing roughtime packaged
in Debian, so don't hesitate to ping me in you need a
co-maintainer.  :)


Best,

  nicoo

On Fri, Sep 23, 2016 at 04:03:26PM +0100, Chris Lamb wrote:
> block 782654 by 838416
> thanks
> 
> Hi,
> 
> > ITP: bazel -- Fast and correct automated build system by Google
> 
> Need this for #838416, "ITP: roughtime -- Secure time synchronisation" :)
> 
> Can you update on the latest status?

[signature.asc (application/pgp-signature, inline)]

Message #40 received at 782654@bugs.debian.org (full text, mbox, reply):

From: Chris Lamb <lamby@debian.org>

To: "Nicolas Braud-Santoni" <nicolas@braud-santoni.eu>, 838416@bugs.debian.org

Cc: 782654@bugs.debian.org, Kyle Moffett <kyle@moffetthome.net>

Subject: Re: Bug#838416: ITP: bazel -- Fast and correct automated build system by Google

Date: Mon, 03 Oct 2016 17:29:38 +0100

Nicoo,

> I think you swapped the blocker and blockee there.

I think you forgot to cc or bcc control@bugs.debian.org … but I fixed
it in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838416;msg=21
so no worries.

> Also, I would be pretty keen on seeing roughtime packaged
> in Debian, so don't hesitate to ping me in you need a
> co-maintainer.

Well, if you could package Bazel… :)


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org / chris-lamb.co.uk
       `-

Message #45 received at 782654@bugs.debian.org (full text, mbox, reply):

From: Kyle Moffett <kyle@moffetthome.net>

To: Chris Lamb <lamby@debian.org>, 782654@bugs.debian.org

Cc: Nicolas Braud-Santoni <nicolas@braud-santoni.eu>, 838416@bugs.debian.org

Subject: Re: Bug#782654: Bug#838416: ITP: bazel -- Fast and correct automated build system by Google

Date: Tue, 4 Oct 2016 17:06:49 -0700

On Mon, Oct 3, 2016 at 9:29 AM, Chris Lamb <lamby@debian.org> wrote:
> > Also, I would be pretty keen on seeing roughtime packaged
> > in Debian, so don't hesitate to ping me in you need a
> > co-maintainer.
>
> Well, if you could package Bazel… :)

Unfortunately, there's more work than just "packaging" Bazel.  Just to
package Bazel, the open issues are:
  (1) Getting Bazel's dependencies packaged in Debian, with acceptable versions.
  (2) Fixing the Bazel build process to use Debian JAR files, rather
than pre-built versions shipped with Bazel.
  (3) Fixing the Bazel build process to comply with Debian policy
around static linking and self-extracting binaries.

But... even with that, Bazel cannot be used to _build_ a Debian
package, because it does not create Debian-policy-compliant binaries,
and it does not support all the Debian cross-compiler flags.  In order
to fix that, a bunch more integration work is needed, including
rewriting the Bazel "architecture specs" to use Debian architecture
names or tuples instead, and to fix the built-in rules to properly
support fully-dynamic linking and library installation paths.

So, yeah, it's a lot of work, and I haven't really had time to make
much progress.

Cheers,
Kyle Moffett

Message #50 received at 782654@bugs.debian.org (full text, mbox, reply):

From: Chris Lamb <lamby@debian.org>

To: Kyle Moffett <kyle@moffetthome.net>, 838416@bugs.debian.org, 782654@bugs.debian.org

Cc: "Nicolas Braud-Santoni" <nicolas@braud-santoni.eu>

Subject: Re: Bug#838416: Bug#782654: Bug#838416: ITP: bazel -- Fast and correct automated build system by Google

Date: Wed, 05 Oct 2016 19:38:04 +0100

Kyle Moffett wrote:

> > Well, if you could package Bazel… :)
> 
> Unfortunately, there's more work than just "packaging" Bazel.  Just to
> package Bazel, the open issues are:

[…]

Oh! My smiley was meant to represent how packaging Bazel is not a simple
task and thus imply you were delaying for no obvious reason! Apologies
that did not come across via email.

> But... even with that, Bazel cannot be used to _build_ a Debian
> package, because it does not create Debian-policy-compliant binaries

Oh, can you elaborate on this?

> [...]

Thanks so much for clarifying the other issues; very useful for myself
and for others coming across this bug report.

If your opinionn should, for example, Roughtime try and rewrite the build
system in the meantime/long-term?


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org / chris-lamb.co.uk
       `-

Message #55 received at 782654@bugs.debian.org (full text, mbox, reply):

From: "Ying-Chun Liu (PaulLiu)" <paulliu@debian.org>

To: 782654@bugs.debian.org, Kyle Moffett <kyle@moffetthome.net>

Subject: ITP: bazel -- Fast and correct automated build system by Google

Date: Sat, 17 Jun 2017 15:18:56 +0800

[Message part 1 (text/plain, inline)]

Hi Kyle,

I'm working on a project on Debian. And need tensorflow to be packaged
in Debian. I don't know if you still have time to work on this ITP. If
not, can I take it over? Or we can co-maintain this together?

I've read your comment (Message #45). Lots of things that needs to do.
I'll make a detailed list soon.

And after playing around the bazel from 0.1.0 to 0.4.1. It seems that
the early versions can be built directly in Debian. But later versions
need previous one.

Yours,
Paul

-- 
                                PaulLiu (劉穎駿)
E-mail: Ying-Chun Liu (PaulLiu) <paulliu@debian.org>

[signature.asc (application/pgp-signature, attachment)]

Message #60 received at 782654-quiet@bugs.debian.org (full text, mbox, reply):

From: "Ying-Chun Liu (PaulLiu)" <paulliu@debian.org>

To: debian-devel@lists.debian.org

Cc: 782654-quiet@bugs.debian.org

Subject: ITP: bazel, but it builds against its earlier version.

Date: Fri, 23 Jun 2017 16:19:14 +0800

[Message part 1 (text/plain, inline)]

Dear Debian devel,

I'm looking into how to package bazel these days. But found it is a bit
hard and I need some suggestions.

Bazel is a build system. Means it is something like cmake, autotools, ant.

First, bazel definitely needs some cleaning. It has some built-in libs
which should be package to Debian first. But that's fine because I'll do it.

The problem is, bazel 4.0.1 is the last version that can be built
directly inside Debian because it can be built from scratch by its own
shell script.
Later bazel version build depends on ealier version. That means, 4.0.2
depends on 4.0.1. And 4.0.3 depends on 4.0.2.

So my question is does that mean I need to package (and clean-up
built-in libs) for 4.0.1 first. And uploading 4.0.1 to Debian. And then
start to package 4.0.2 .. until to the latest? It is similar to gcc
compiles itself by earlier version. Just want to know how to solve this
and the best practice.

Yours,
Paul




-- 
                                PaulLiu (劉穎駿)
E-mail: Ying-Chun Liu (PaulLiu) <paulliu@debian.org>

[signature.asc (application/pgp-signature, attachment)]

Message #65 received at 782654-quiet@bugs.debian.org (full text, mbox, reply):

From: Damien Martin-Guillerez <dmarting@google.com>

To: "Ying-Chun Liu (PaulLiu)" <paulliu@debian.org>, 782654-quiet@bugs.debian.org, debian-devel@lists.debian.org

Subject: Re: Bug#782654: ITP: bazel, but it builds against its earlier version.

Date: Fri, 23 Jun 2017 08:26:19 +0000

[Message part 1 (text/plain, inline)]

Hi Ying-Chun,

AFAICT this is incorrect, we maintain distribution artifact that can be
built without bazel. See
https://github.com/bazelbuild/bazel/releases/download/0.5.1/bazel-0.5.1-dist.zip
for
0.5.1 distribution artifact. This is a source zip that does not need bazel
to be built.

On Fri, Jun 23, 2017 at 4:21 PM Ying-Chun Liu (PaulLiu) <paulliu@debian.org>
wrote:

> Dear Debian devel,
>
> I'm looking into how to package bazel these days. But found it is a bit
> hard and I need some suggestions.
>
> Bazel is a build system. Means it is something like cmake, autotools, ant.
>
> First, bazel definitely needs some cleaning. It has some built-in libs
> which should be package to Debian first. But that's fine because I'll do
> it.
>
> The problem is, bazel 4.0.1 is the last version that can be built
> directly inside Debian because it can be built from scratch by its own
> shell script.
> Later bazel version build depends on ealier version. That means, 4.0.2
> depends on 4.0.1. And 4.0.3 depends on 4.0.2.
>
> So my question is does that mean I need to package (and clean-up
> built-in libs) for 4.0.1 first. And uploading 4.0.1 to Debian. And then
> start to package 4.0.2 .. until to the latest? It is similar to gcc
> compiles itself by earlier version. Just want to know how to solve this
> and the best practice.
>
> Yours,
> Paul
>
>
>
>
> --
>                                 PaulLiu (劉穎駿)
> E-mail: Ying-Chun Liu (PaulLiu) <paulliu@debian.org>
>
>

[Message part 2 (text/html, inline)]

Message #70 received at 782654-quiet@bugs.debian.org (full text, mbox, reply):

From: PaulLiu <paulliu@debian.org>

To: Damien Martin-Guillerez <dmarting@google.com>

Cc: 782654-quiet@bugs.debian.org, debian-devel@lists.debian.org

Subject: Re: Bug#782654: ITP: bazel, but it builds against its earlier version.

Date: Fri, 23 Jun 2017 17:06:14 +0800

[Message part 1 (text/plain, inline)]

Hi Damien,

That's great. I didn't know that because I'm using git and just checkout
the version tags.
So the thing left is to clean-up the binary jar files inside that zip and
replaced by the Debian and modify the classpath.

I'll start working on this. :)

Thanks,
Paul



On Fri, Jun 23, 2017 at 4:26 PM, Damien Martin-Guillerez <
dmarting@google.com> wrote:

> Hi Ying-Chun,
>
> AFAICT this is incorrect, we maintain distribution artifact that can be
> built without bazel. See https://github.com/bazelbuild/bazel/releases/
> download/0.5.1/bazel-0.5.1-dist.zip for 0.5.1 distribution artifact. This
> is a source zip that does not need bazel to be built.
>
> On Fri, Jun 23, 2017 at 4:21 PM Ying-Chun Liu (PaulLiu) <
> paulliu@debian.org> wrote:
>
>> Dear Debian devel,
>>
>> I'm looking into how to package bazel these days. But found it is a bit
>> hard and I need some suggestions.
>>
>> Bazel is a build system. Means it is something like cmake, autotools, ant.
>>
>> First, bazel definitely needs some cleaning. It has some built-in libs
>> which should be package to Debian first. But that's fine because I'll do
>> it.
>>
>> The problem is, bazel 4.0.1 is the last version that can be built
>> directly inside Debian because it can be built from scratch by its own
>> shell script.
>> Later bazel version build depends on ealier version. That means, 4.0.2
>> depends on 4.0.1. And 4.0.3 depends on 4.0.2.
>>
>> So my question is does that mean I need to package (and clean-up
>> built-in libs) for 4.0.1 first. And uploading 4.0.1 to Debian. And then
>> start to package 4.0.2 .. until to the latest? It is similar to gcc
>> compiles itself by earlier version. Just want to know how to solve this
>> and the best practice.
>>
>> Yours,
>> Paul
>>
>>
>>
>>
>> --
>>                                 PaulLiu (劉穎駿)
>> E-mail: Ying-Chun Liu (PaulLiu) <paulliu@debian.org>
>>
>>

[Message part 2 (text/html, inline)]

Message #75 received at 782654-quiet@bugs.debian.org (full text, mbox, reply):

From: Damien Martin-Guillerez <dmarting@google.com>

To: PaulLiu <paulliu@debian.org>

Cc: 782654-quiet@bugs.debian.org, debian-devel@lists.debian.org

Subject: Re: Bug#782654: ITP: bazel, but it builds against its earlier version.

Date: Fri, 23 Jun 2017 09:18:31 +0000

[Message part 1 (text/plain, inline)]

Nice, I'll try to share with you the document we have internally about the
work we want to do to make that happens. Most of it is packaging
dependencies.

On Fri, Jun 23, 2017 at 5:06 PM PaulLiu <paulliu@debian.org> wrote:

> Hi Damien,
>
> That's great. I didn't know that because I'm using git and just checkout
> the version tags.
> So the thing left is to clean-up the binary jar files inside that zip and
> replaced by the Debian and modify the classpath.
>
> I'll start working on this. :)
>
> Thanks,
> Paul
>
>
>
> On Fri, Jun 23, 2017 at 4:26 PM, Damien Martin-Guillerez <
> dmarting@google.com> wrote:
>
>> Hi Ying-Chun,
>>
>> AFAICT this is incorrect, we maintain distribution artifact that can be
>> built without bazel. See
>> https://github.com/bazelbuild/bazel/releases/download/0.5.1/bazel-0.5.1-dist.zip for
>> 0.5.1 distribution artifact. This is a source zip that does not need bazel
>> to be built.
>>
>> On Fri, Jun 23, 2017 at 4:21 PM Ying-Chun Liu (PaulLiu) <
>> paulliu@debian.org> wrote:
>>
>>> Dear Debian devel,
>>>
>>> I'm looking into how to package bazel these days. But found it is a bit
>>> hard and I need some suggestions.
>>>
>>> Bazel is a build system. Means it is something like cmake, autotools,
>>> ant.
>>>
>>> First, bazel definitely needs some cleaning. It has some built-in libs
>>> which should be package to Debian first. But that's fine because I'll do
>>> it.
>>>
>>> The problem is, bazel 4.0.1 is the last version that can be built
>>> directly inside Debian because it can be built from scratch by its own
>>> shell script.
>>> Later bazel version build depends on ealier version. That means, 4.0.2
>>> depends on 4.0.1. And 4.0.3 depends on 4.0.2.
>>>
>>> So my question is does that mean I need to package (and clean-up
>>> built-in libs) for 4.0.1 first. And uploading 4.0.1 to Debian. And then
>>> start to package 4.0.2 .. until to the latest? It is similar to gcc
>>> compiles itself by earlier version. Just want to know how to solve this
>>> and the best practice.
>>>
>>> Yours,
>>> Paul
>>>
>>>
>>>
>>>
>>> --
>>>                                 PaulLiu (劉穎駿)
>>> E-mail: Ying-Chun Liu (PaulLiu) <paulliu@debian.org>
>>>
>>>
>

[Message part 2 (text/html, inline)]

Message #80 received at 782654-quiet@bugs.debian.org (full text, mbox, reply):

From: Philipp Kern <phil@philkern.de>

To: PaulLiu <paulliu@debian.org>, Damien Martin-Guillerez <dmarting@google.com>

Cc: 782654-quiet@bugs.debian.org, debian-devel@lists.debian.org

Subject: Re: Bug#782654: ITP: bazel, but it builds against its earlier version.

Date: Sun, 25 Jun 2017 13:05:55 +0200

[Message part 1 (text/plain, inline)]

On 6/23/2017 11:06 AM, PaulLiu wrote:
> That's great. I didn't know that because I'm using git and just checkout
> the version tags.
> So the thing left is to clean-up the binary jar files inside that zip
> and replaced by the Debian and modify the classpath.

I don't think it's quite that easy, but I wish you luck. :)

However in terms of how to get it in in the first place: For
bootstrapping the usual way is to do an upload per architecture that has
been built using a locally installed version of the package and then
binNMU it in the archive against itself.

Kind regards
Philipp Kern

[signature.asc (application/pgp-signature, attachment)]

Message #85 received at 782654-quiet@bugs.debian.org (full text, mbox, reply):

From: Damien Martin-Guillerez <dmarting@google.com>

To: Philipp Kern <phil@philkern.de>, PaulLiu <paulliu@debian.org>

Cc: 782654-quiet@bugs.debian.org, debian-devel@lists.debian.org

Subject: Re: Bug#782654: ITP: bazel, but it builds against its earlier version.

Date: Mon, 26 Jun 2017 05:41:47 +0000

[Message part 1 (text/plain, inline)]

Indeed as Philipp said it is not as simple as packaging dependencies.
However the Bazel team is going to do some of the refactoring needed and
will accept any help for that.

Here the current dicussion document:
https://docs.google.com/document/d/1VuYv41U_Esjrl0umu-uO3hUK4WNnCiG0pXZgjliHfTw

On Sun, Jun 25, 2017 at 5:06 PM Philipp Kern <phil@philkern.de> wrote:

> On 6/23/2017 11:06 AM, PaulLiu wrote:
> > That's great. I didn't know that because I'm using git and just checkout
> > the version tags.
> > So the thing left is to clean-up the binary jar files inside that zip
> > and replaced by the Debian and modify the classpath.
>
> I don't think it's quite that easy, but I wish you luck. :)
>
> However in terms of how to get it in in the first place: For
> bootstrapping the usual way is to do an upload per architecture that has
> been built using a locally installed version of the package and then
> binNMU it in the archive against itself.
>
> Kind regards
> Philipp Kern
>
>

[Message part 2 (text/html, inline)]

Message #92 received at 782654@bugs.debian.org (full text, mbox, reply):

From: Andrew Shadura <andrew.shadura@collabora.co.uk>

To: 782654@bugs.debian.org

Subject: Re: Bug#782654: ITP: bazel, but it builds against its earlier version.

Date: Fri, 6 Oct 2017 13:32:10 +0200

[Message part 1 (text/plain, inline)]

Hi,

Is there any update on bazel? It is needed to build recent Kubernetes.

-- 
Cheers,
  Andrew

[signature.asc (application/pgp-signature, attachment)]

Message #99 received at 782654@bugs.debian.org (full text, mbox, reply):

From: Damien Martin-Guillerez <dmarting@google.com>

To: Andrew Shadura <andrew.shadura@collabora.co.uk>, 782654@bugs.debian.org

Subject: Re: Bug#782654: ITP: bazel, but it builds against its earlier version.

Date: Fri, 06 Oct 2017 12:57:23 +0000

[Message part 1 (text/plain, inline)]

Hi Andrew,

I don't have any news on packaging the dependencies.
On the Bazel side we haven't address the refactoring on the build needed
for it yet. I'll see if we can prioritize the work.

On Fri, Oct 6, 2017, 4:42 AM Andrew Shadura <andrew.shadura@collabora.co.uk>
wrote:

> Hi,
>
> Is there any update on bazel? It is needed to build recent Kubernetes.
>
> --
> Cheers,
>   Andrew
>
>

[Message part 2 (text/html, inline)]

Message #104 received at 782654@bugs.debian.org (full text, mbox, reply):

From: Chris Lamb <lamby@debian.org>

To: Kyle Moffett <kyle@moffetthome.net>, 838416@bugs.debian.org, 782654@bugs.debian.org

Cc: "Nicolas Braud-Santoni" <nicolas@braud-santoni.eu>

Subject: Re: Bug#838416: Bug#782654: Bug#838416: ITP: bazel -- Fast and correct automated build system by Google

Date: Fri, 18 May 2018 11:56:01 +0100

Chris Lamb wrote:

> Kyle Moffett wrote:
> 
> > > Well, if you could package Bazel… :)
> > 
> > Unfortunately, there's more work than just "packaging" Bazel.  Just to
> > package Bazel, the open issues are:
> 
> […]
> 
> Oh! My smiley was meant to represent how packaging Bazel is not a simple
> task and thus imply you were delaying for no obvious reason! Apologies
> that did not come across via email.
> 
> > But... even with that, Bazel cannot be used to _build_ a Debian
> > package, because it does not create Debian-policy-compliant binaries
> 
> Oh, can you elaborate on this?
> 
> > [...]
> 
> Thanks so much for clarifying the other issues; very useful for myself
> and for others coming across this bug report.
> 
> If your opinionn should, for example, Roughtime try and rewrite the build
> system in the meantime/long-term?

Gentle ping on this?


Best wishes,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org / chris-lamb.co.uk
       `-

Message #109 received at 782654@bugs.debian.org (full text, mbox, reply):

From: Kyle Moffett <kyle@moffetthome.net>

To: Chris Lamb <lamby@debian.org>, 782654@bugs.debian.org

Cc: 838416@bugs.debian.org, Nicolas Braud-Santoni <nicolas@braud-santoni.eu>

Subject: Re: Bug#782654: Bug#838416: Bug#782654: Bug#838416: ITP: bazel -- Fast and correct automated build system by Google

Date: Tue, 22 May 2018 14:55:19 -0600

I spent a while working on it off and on, but there is a decent amount
of tweaking and other packaging work needed to get policy-compliant
bazel packages.  (E.G: There are quite a few binary JAR files shipped
in the upstream tarball that don't necessarily match the versions in
Debian).

I just didn't have the spare time, especially now that I have a kid,
to sink into one package.

(Also, FWIW, if you want to _create_ policy-compliant packages using
bazel, there is a lot more work than just getting a policy-compliant
bazel package, because bazel needs to understand debian multiarch
compilers, standard build flags, etc).

Cheers,
Kyle Moffett


On Fri, May 18, 2018 at 4:56 AM, Chris Lamb <lamby@debian.org> wrote:
> Chris Lamb wrote:
>
>> Kyle Moffett wrote:
>>
>> > > Well, if you could package Bazel… :)
>> >
>> > Unfortunately, there's more work than just "packaging" Bazel.  Just to
>> > package Bazel, the open issues are:
>>
>> […]
>>
>> Oh! My smiley was meant to represent how packaging Bazel is not a simple
>> task and thus imply you were delaying for no obvious reason! Apologies
>> that did not come across via email.
>>
>> > But... even with that, Bazel cannot be used to _build_ a Debian
>> > package, because it does not create Debian-policy-compliant binaries
>>
>> Oh, can you elaborate on this?
>>
>> > [...]
>>
>> Thanks so much for clarifying the other issues; very useful for myself
>> and for others coming across this bug report.
>>
>> If your opinionn should, for example, Roughtime try and rewrite the build
>> system in the meantime/long-term?
>
> Gentle ping on this?
>
>
> Best wishes,
>
> --
>       ,''`.
>      : :'  :     Chris Lamb
>      `. `'`      lamby@debian.org / chris-lamb.co.uk
>        `-

Message #114 received at 782654@bugs.debian.org (full text, mbox, reply):

From: Bastien ROUCARIES <roucaries.bastien@gmail.com>

To: Damien Martin-Guillerez <dmarting@google.com>, 782654@bugs.debian.org

Subject: News of bazel refactoring for compliance with debian policy

Date: Fri, 6 Sep 2019 16:38:04 +0200

Hi,

We recently drop tensorflow from debian due to the huge cost of
maintaining the build system byt converting from bazel to cmake.

Where is the roadmap to get bazel distrib friendly ?

Thanks

Bastien

Message #119 received at 782654@bugs.debian.org (full text, mbox, reply):

From: Olek Wojnar <olek@debian.org>

To: 782654@bugs.debian.org

Cc: 838416@bugs.debian.org, Kyle Moffett <kyle@moffetthome.net>, debian-med@lists.debian.org, Chris Lamb <lamby@debian.org>, Nicolas Braud-Santoni <nicolas@braud-santoni.eu>, Damien Martin-Guillerez <dmarting@google.com>, Bastien ROUCARIES <roucaries.bastien@gmail.com>, Philipp Kern <phil@philkern.de>, PaulLiu <paulliu@debian.org>, lumin <cdluminate@gmail.com>

Subject: Re: Bug#782654: Bug#838416: Bug#782654: Bug#838416: ITP: bazel -- Fast and correct automated build system by Google

Date: Wed, 8 Apr 2020 13:43:27 -0400

[Message part 1 (text/plain, inline)]

Hi Kyle, (or other interested/involved parties)

Bazel has suddenly become more important because it is preventing us from
getting packages working that would help with the COVID-19 pandemic. Due to
the significance, I am copying the Debian Med team as well as key people
from this bug's history in the hopes of getting something moving quickly.

On Tue, 22 May 2018 14:55:19 -0600 Kyle Moffett <kyle@moffetthome.net>
wrote:
> I spent a while working on it off and on, but there is a decent amount
> of tweaking and other packaging work needed to get policy-compliant
> bazel packages.  (E.G: There are quite a few binary JAR files shipped
> in the upstream tarball that don't necessarily match the versions in
> Debian).
>
> I just didn't have the spare time, especially now that I have a kid,
> to sink into one package.

I can relate to the kid/time issues! ;) Have you had any time to work on it
recently? Did you ever upload any of your work?

In the meantime, I see that Bazel has an unofficial Ubuntu build [1]. Do
you know anything about that? It seems like a good place for us to start if
you aren't close to a product yourself.

Oh, and to state this explicitly: I'm happy to work on this if it'll help
it get into Debian faster! I just don't want to step on anyone's toes if
someone has already made significant progress on this ITP.

-Olek

[1]
https://docs.bazel.build/versions/master/install-ubuntu.html#install-on-ubuntu

[Message part 2 (text/html, inline)]

Message #124 received at 782654@bugs.debian.org (full text, mbox, reply):

From: Philipp Kern <pkern@debian.org>

To: Olek Wojnar <olek@debian.org>

Cc: 782654@bugs.debian.org, 838416@bugs.debian.org, Kyle Moffett <kyle@moffetthome.net>, debian-med@lists.debian.org, Chris Lamb <lamby@debian.org>, Nicolas Braud-Santoni <nicolas@braud-santoni.eu>, Damien Martin-Guillerez <dmarting@google.com>, Bastien ROUCARIES <roucaries.bastien@gmail.com>, PaulLiu <paulliu@debian.org>, lumin <cdluminate@gmail.com>

Subject: Re: Bug#782654: Bug#838416: Bug#782654: Bug#838416: ITP: bazel -- Fast and correct automated build system by Google

Date: Wed, 08 Apr 2020 22:56:59 +0200

On 2020-04-08 19:43, Olek Wojnar wrote:
> Bazel has suddenly become more important because it is preventing us 
> from getting packages working that would help with the COVID-19 
> pandemic. Due to the significance, I am copying the Debian Med team as 
> well as key people from this bug's history in the hopes of getting 
> something moving quickly.
> 
> On Tue, 22 May 2018 14:55:19 -0600 Kyle Moffett <kyle@moffetthome.net> 
> wrote:
>> I spent a while working on it off and on, but there is a decent amount
>> of tweaking and other packaging work needed to get policy-compliant
>> bazel packages.  (E.G: There are quite a few binary JAR files shipped
>> in the upstream tarball that don't necessarily match the versions in
>> Debian).
>> 
>> I just didn't have the spare time, especially now that I have a kid,
>> to sink into one package.
> 
> I can relate to the kid/time issues! ;) Have you had any time to work 
> on it recently? Did you ever upload any of your work?
> 
> In the meantime, I see that Bazel has an unofficial Ubuntu build [1]. 
> Do you know anything about that? It seems like a good place for us to 
> start if you aren't close to a product yourself.

That's the build Google provides that is built with Bazel itself, using 
a ton of vendored libraries. (Because that's how Google operates 
internally.)

Generally the pkg_deb output[1] is not really policy-compliant and more 
built from the ground up without any Debian tooling. So the /mere 
existence/ of that package (which was there from the beginning) does not 
help the quest of getting Bazel packaged for Debian, unfortunately.

Kind regards
Philipp Kern, obviously not speaking for Google

[1] 
https://github.com/bazelbuild/bazel/blob/f828b4c77805ad0ea6afecef798aa69d68bec8d4/scripts/packages/debian/BUILD#L69

Message #129 received at 782654@bugs.debian.org (full text, mbox, reply):

From: Bastien ROUCARIES <roucaries.bastien@gmail.com>

To: Philipp Kern <pkern@debian.org>

Cc: Olek Wojnar <olek@debian.org>, 782654@bugs.debian.org, 838416@bugs.debian.org, Kyle Moffett <kyle@moffetthome.net>, Debian Med Project List <debian-med@lists.debian.org>, Chris Lamb <lamby@debian.org>, Nicolas Braud-Santoni <nicolas@braud-santoni.eu>, Damien Martin-Guillerez <dmarting@google.com>, PaulLiu <paulliu@debian.org>, lumin <cdluminate@gmail.com>

Subject: Re: Bug#782654: Bug#838416: Bug#782654: Bug#838416: ITP: bazel -- Fast and correct automated build system by Google

Date: Thu, 9 Apr 2020 22:22:55 +0200

Upstream seems to be friendly

Time to prod them:
https://github.com/bazelbuild/bazel/issues/9408

On Wed, Apr 8, 2020 at 10:57 PM Philipp Kern <pkern@debian.org> wrote:
>
> On 2020-04-08 19:43, Olek Wojnar wrote:
> > Bazel has suddenly become more important because it is preventing us
> > from getting packages working that would help with the COVID-19
> > pandemic. Due to the significance, I am copying the Debian Med team as
> > well as key people from this bug's history in the hopes of getting
> > something moving quickly.
> >
> > On Tue, 22 May 2018 14:55:19 -0600 Kyle Moffett <kyle@moffetthome.net>
> > wrote:
> >> I spent a while working on it off and on, but there is a decent amount
> >> of tweaking and other packaging work needed to get policy-compliant
> >> bazel packages.  (E.G: There are quite a few binary JAR files shipped
> >> in the upstream tarball that don't necessarily match the versions in
> >> Debian).
> >>
> >> I just didn't have the spare time, especially now that I have a kid,
> >> to sink into one package.
> >
> > I can relate to the kid/time issues! ;) Have you had any time to work
> > on it recently? Did you ever upload any of your work?
> >
> > In the meantime, I see that Bazel has an unofficial Ubuntu build [1].
> > Do you know anything about that? It seems like a good place for us to
> > start if you aren't close to a product yourself.
>
> That's the build Google provides that is built with Bazel itself, using
> a ton of vendored libraries. (Because that's how Google operates
> internally.)
>
> Generally the pkg_deb output[1] is not really policy-compliant and more
> built from the ground up without any Debian tooling. So the /mere
> existence/ of that package (which was there from the beginning) does not
> help the quest of getting Bazel packaged for Debian, unfortunately.
>
> Kind regards
> Philipp Kern, obviously not speaking for Google
>
> [1]
> https://github.com/bazelbuild/bazel/blob/f828b4c77805ad0ea6afecef798aa69d68bec8d4/scripts/packages/debian/BUILD#L69

Message #134 received at 782654@bugs.debian.org (full text, mbox, reply):

From: Olek Wojnar <olekw.dev@gmail.com>

To: Bastien ROUCARIES <roucaries.bastien@gmail.com>

Cc: Philipp Kern <pkern@debian.org>, 782654@bugs.debian.org, 838416@bugs.debian.org, Kyle Moffett <kyle@moffetthome.net>, Debian Med Project List <debian-med@lists.debian.org>, Chris Lamb <lamby@debian.org>, Nicolas Braud-Santoni <nicolas@braud-santoni.eu>, Damien Martin-Guillerez <dmarting@google.com>, PaulLiu <paulliu@debian.org>, lumin <cdluminate@gmail.com>

Subject: Re: Bug#782654: Bug#838416: Bug#782654: Bug#838416: ITP: bazel -- Fast and correct automated build system by Google

Date: Thu, 9 Apr 2020 18:19:15 -0400

[Message part 1 (text/plain, inline)]

Philipp and Bastien,

Thank you both for your responses!

On Thu, Apr 9, 2020 at 4:23 PM Bastien ROUCARIES <
roucaries.bastien@gmail.com> wrote:

> Upstream seems to be friendly
>
> Time to prod them:
> https://github.com/bazelbuild/bazel/issues/9408


Thanks for highlighting that. It indeed seems that they will likely realize
the importance of their software right now and help. Pinged. :) [1]


> On Wed, Apr 8, 2020 at 10:57 PM Philipp Kern <pkern@debian.org> wrote:
> >
> > On 2020-04-08 19:43, Olek Wojnar wrote:
> > >
> > > In the meantime, I see that Bazel has an unofficial Ubuntu build [1].
> > > Do you know anything about that? It seems like a good place for us to
> > > start if you aren't close to a product yourself.
> >
> > That's the build Google provides that is built with Bazel itself, using
> > a ton of vendored libraries. (Because that's how Google operates
> > internally.)
>

Ah, ok. Good to know. Thanks. Might be better to just start with a vanilla
source package then. I'm playing around with it just to see what I can get
working while we wait for a reply to my ping on Bastien's GitHub issue.


> > Generally the pkg_deb output[1] is not really policy-compliant and more
> > built from the ground up without any Debian tooling. So the /mere
> > existence/ of that package (which was there from the beginning) does not
> > help the quest of getting Bazel packaged for Debian, unfortunately.
> >
> > Kind regards
> > Philipp Kern, obviously not speaking for Google
> >
> > [1]
> >
> https://github.com/bazelbuild/bazel/blob/f828b4c77805ad0ea6afecef798aa69d68bec8d4/scripts/packages/debian/BUILD#L69


Well that's not as encouraging as I'd hoped but still good information to
have. Sounds like our best shot for getting something working in the
near-term is active cooperation and support from Google. Here's hoping they
support that!!

-Olek

[Message part 2 (text/html, inline)]

Message #139 received at 782654@bugs.debian.org (full text, mbox, reply):

From: Olek Wojnar <olek@debian.org>

To: 782654@bugs.debian.org

Cc: Philipp Kern <pkern@debian.org>, Bastien ROUCARIES <roucaries.bastien@gmail.com>, 838416@bugs.debian.org, Kyle Moffett <kyle@moffetthome.net>, Debian Med Project List <debian-med@lists.debian.org>, Chris Lamb <lamby@debian.org>, Nicolas Braud-Santoni <nicolas@braud-santoni.eu>, Damien Martin-Guillerez <dmarting@google.com>, PaulLiu <paulliu@debian.org>, lumin <cdluminate@gmail.com>, debian-science@lists.debian.org

Subject: ITP: bazel -- Fast and correct automated build system by Google

Date: Tue, 14 Apr 2020 11:27:45 -0400

[Message part 1 (text/plain, inline)]

To those interested in Bazel in Debian:

We just had a very positive discussion with upstream and I think that
finally getting Bazel into Debian is on the horizon. This endeavor is going
to be larger than one person, in the long run if not right at this moment.

Therefore, I would like to create a Bazel packaging team in Debian since a
team approach is what will ensure this build system remains viable and
well-supported even after the short-term goal of helping to get software
into Debian to address the COVID-19 pandemic.

If you are subscribed to this bug and are interested (or know someone who
is), please let me know if you would like to be part of that team in some
capacity. I am happy to continue coordinating this team and I am equally
happy to pass that responsibility on if anyone else has a strong desire to
do that. Since Kyle was previously working this project by himself, I
definitely defer to him if he has the time and desire to lead the new team.

Looking forward to getting a good group of people together who can
contribute to this, to whatever extent they are able!

-Olek

[Message part 2 (text/html, inline)]

Message #144 received at 782654@bugs.debian.org (full text, mbox, reply):

From: Andreas Tille <tille@debian.org>

To: Olek Wojnar <olek@debian.org>

Cc: 782654@bugs.debian.org, Philipp Kern <pkern@debian.org>, Bastien ROUCARIES <roucaries.bastien@gmail.com>, 838416@bugs.debian.org, Kyle Moffett <kyle@moffetthome.net>, Debian Med Project List <debian-med@lists.debian.org>, Chris Lamb <lamby@debian.org>, Nicolas Braud-Santoni <nicolas@braud-santoni.eu>, Damien Martin-Guillerez <dmarting@google.com>, PaulLiu <paulliu@debian.org>, lumin <cdluminate@gmail.com>, debian-science@lists.debian.org

Subject: Re: ITP: bazel -- Fast and correct automated build system by Google

Date: Tue, 14 Apr 2020 17:56:56 +0200

Hi Olek,

On Tue, Apr 14, 2020 at 11:27:45AM -0400, Olek Wojnar wrote:
> To those interested in Bazel in Debian:
> ...
> Looking forward to getting a good group of people together who can
> contribute to this, to whatever extent they are able!

while I doubt that I'll be of technical help to work on this package I'd
like to express that I'm extremely happy.  Your effort for bazel which
will finally a big step to get tensorflow in which is a precondition for
several COVID-19 releavant packages is really welcome.

Thanks a lot

      Andreas.

-- 
http://fam-tille.de

Message #151 received at 782654@bugs.debian.org (full text, mbox, reply):

From: Timo Röhling <timo@gaussglocke.de>

To: 782654@bugs.debian.org

Subject: Re: ITP: bazel -- Fast and correct automated build system by Google

Date: Sat, 25 Apr 2020 15:53:58 +0200

On Tue, 14 Apr 2020 11:27:45 -0400 Olek Wojnar <olek@debian.org> wrote:
> To those interested in Bazel in Debian:

I'm interested in helping out. I have decent C++ and Python experience,
both with coding and Debian packaging, and I would really like to see
Tensorflow in Debian.

Cheers
Timo

Message #156 received at 782654@bugs.debian.org (full text, mbox, reply):

From: Olek Wojnar <olek@debian.org>

To: Timo Röhling <timo@gaussglocke.de>, 782654@bugs.debian.org

Subject: Re: Bug#782654: ITP: bazel -- Fast and correct automated build system by Google

Date: Sat, 25 Apr 2020 12:58:47 -0400

[Message part 1 (text/plain, inline)]

Hi Timo,

On Sat, Apr 25, 2020, 10:06 Timo Röhling <timo@gaussglocke.de> wrote:

> On Tue, 14 Apr 2020 11:27:45 -0400 Olek Wojnar <olek@debian.org> wrote:
> > To those interested in Bazel in Debian:
>
> I'm interested in helping out. I have decent C++ and Python experience,
> both with coding and Debian packaging, and I would really like to see
> Tensorflow in Debian.
>

We'd love to have your help! I just added you to the temporary team on
Salsa [1]. I'll be setting up a proper team but, so far, my focus has been
on just getting something working in my personal namespace.

Expect an olek3 branch later today with the latest from what Yun (pcloudy)
and I have been working on.

Welcome to the team!

-Olek

[1] https://salsa.debian.org/olek/bazel

[Message part 2 (text/html, inline)]

Message #209 received at 782654-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 782654-close@bugs.debian.org

Subject: Bug#782654: fixed in bazel-bootstrap 3.4.0+ds-1

Date: Fri, 16 Oct 2020 23:00:09 +0000

Source: bazel-bootstrap
Source-Version: 3.4.0+ds-1
Done: Olek Wojnar <olek@debian.org>

We believe that the bug you reported is fixed in the latest version of
bazel-bootstrap, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 782654@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Olek Wojnar <olek@debian.org> (supplier of updated bazel-bootstrap package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 19 Jul 2020 00:25:48 -0400
Source: bazel-bootstrap
Binary: bazel-bootstrap bazel-bootstrap-data bazel-bootstrap-dbgsym
Architecture: source all amd64
Version: 3.4.0+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Bazel Team <team+bazel@tracker.debian.org>
Changed-By: Olek Wojnar <olek@debian.org>
Description:
 bazel-bootstrap - Tool to automate software builds and tests
 bazel-bootstrap-data - Tool to automate software builds and tests (data files)
Closes: 782654
Changes:
 bazel-bootstrap (3.4.0+ds-1) unstable; urgency=medium
 .
   * Initial release (Closes: #782654)
Checksums-Sha1:
 2280afda4950a5ca2e8c8b1957a49eb207f29c1a 3383 bazel-bootstrap_3.4.0+ds-1.dsc
 cdaabd5c09717f7c2e31746be27894b5a487012c 10410744 bazel-bootstrap_3.4.0+ds.orig.tar.xz
 e01c8b792d4466ea95617007aaf73d21b6c9e254 23140 bazel-bootstrap_3.4.0+ds-1.debian.tar.xz
 de0cfc351f75b2a6415134be5712d97ad40f2f6e 17379224 bazel-bootstrap-data_3.4.0+ds-1_all.deb
 2ebc9eff3c12dd57463602b82a55ab783d408a43 5827768 bazel-bootstrap-dbgsym_3.4.0+ds-1_amd64.deb
 b661b56abed648c51fe18525fbd7acd6df885092 15290 bazel-bootstrap_3.4.0+ds-1_amd64.buildinfo
 acae90a8250c60f430646547f22d69c3c2611916 484192 bazel-bootstrap_3.4.0+ds-1_amd64.deb
Checksums-Sha256:
 5557866bc0323680ecfef0ac2c9cde6e11cae7ab978300633b645a93615be37d 3383 bazel-bootstrap_3.4.0+ds-1.dsc
 de2c82c8e5cc06bb44c314521db39a361ae691e7c7b80311cc143bbf258d6f31 10410744 bazel-bootstrap_3.4.0+ds.orig.tar.xz
 eca9c53de2ce8ae2711d42856373c3562c2ea9bd2695a470567c1ecf6c6b5511 23140 bazel-bootstrap_3.4.0+ds-1.debian.tar.xz
 f7d2ce5da6c97a5d3c6134cd371b23f3248c2d461c1e05916288b4668cb86fa8 17379224 bazel-bootstrap-data_3.4.0+ds-1_all.deb
 6a37963a93442514ce2adc203f54d1fafffdf6df36ec5ce5ab1c8e8770262ced 5827768 bazel-bootstrap-dbgsym_3.4.0+ds-1_amd64.deb
 0c48252ccba3a0e14c4b0d4c597c984b94410bac8dd310f16b612b6c08ec56eb 15290 bazel-bootstrap_3.4.0+ds-1_amd64.buildinfo
 146a5dce00fc7b2e5fc01cc77369935399900513bd1d93d91ba740097ee48942 484192 bazel-bootstrap_3.4.0+ds-1_amd64.deb
Files:
 2f6a6680efff176fd5dde210c8cc9513 3383 devel optional bazel-bootstrap_3.4.0+ds-1.dsc
 eb5f849c72ca7c906ee1f0de55ad0a73 10410744 devel optional bazel-bootstrap_3.4.0+ds.orig.tar.xz
 cb1646d19fd2df5128c71e1a7af7a919 23140 devel optional bazel-bootstrap_3.4.0+ds-1.debian.tar.xz
 db256348e108ee8bd621ba4c16c3e558 17379224 devel optional bazel-bootstrap-data_3.4.0+ds-1_all.deb
 3a5b606dd533344734ecdc613401e3bb 5827768 debug optional bazel-bootstrap-dbgsym_3.4.0+ds-1_amd64.deb
 ff7cd9fe23391afcc8cbd882f6a92d58 15290 devel optional bazel-bootstrap_3.4.0+ds-1_amd64.buildinfo
 9cd7952d139efbf1eff92d47f2b4d95f 484192 devel optional bazel-bootstrap_3.4.0+ds-1_amd64.deb

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEELejiDiSiH9jtG0ynfYPUBqCdweQFAl84aCUACgkQfYPUBqCd
weSmwA//eNCu2ITeTeMg9dUQ3f22GY+Hv6z6hNrvX2TSdG2thTS9OsaN0rCRp9+x
pHk6ELhKLUHM/58oudh7UDAD34HfDS5wJVf+zs8tEhdVN91cmg8m9Dldm3FGWXVm
cAe3bAfx8EYYdXCOv+wncVWr1WxwjKK+3uiFfqel8SHrRq8ArP0TN/dNKb+RYjbL
MhWNJqBwfPs2r5ijNEMWaMqPS/t7YUGVJkvo8mxblP6Q31PYIc6px3VTvXSwnIyi
0Ae49qlfH4pePGFvI1Vg8dFZOvFr8qcv30cPDM41Bz0ZPUqCjjWDY3gEzJD3nRZu
ZeU2/1KkautKTqCwgHdFywJ8RjfOn4Pgn9LyU0ehGtOwh4uBkJ21pZw524dKYuSR
Zk5IPTibGU8/Z5yiZsYTCU7Xl18UQKNrL3hv4jkYWz5NKLK/850gHSgP23KB4Zs6
jAmkGUJ2QYjyKboFIrgLbmj5oUNX+xB7YX+wbWNRLINV7EgQPrvzO5A2nmLNDpTs
0RLe9M6pjzhzkvQ2Txv//xhf6AfrmOhcJq+mQW6L14ea4bTsjfnEuVkUTHQ+QhgI
hK07nR4k4NDIin/7pg4aN3tNdeNceFZh6oneY14RzwTGt5leECPv6XIKpGBKGppL
1URGs4GFssqNh0Ia1nGRakHzjqve2Q7s/+sDEApD7esv+pFUyq0=
=hqg3
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.