On 16/04/19 at 08:52 +0200, Andreas Tille wrote:
> On Mon, Apr 15, 2019 at 05:35:40PM +0200, Bastian Blank wrote:
> > On Mon, Apr 15, 2019 at 04:55:12PM +0200, Andreas Tille wrote:
> > > biococoa (U) does not use Debhelper (no compat level found)
> > > (source version: 2.2.2-4)
> > >
Lucas Nussbaum:
> On 16/04/19 at 08:52 +0200, Andreas Tille wrote:
>> On Mon, Apr 15, 2019 at 05:35:40PM +0200, Bastian Blank wrote:
>>> On Mon, Apr 15, 2019 at 04:55:12PM +0200, Andreas Tille wrote:
biococoa (U) does not use Debhelper (no compat level found)
(source version:
Hi people,
This message is neither a good news, nor asking for help. I'm writing
to share some of my points about Deep Learning Framework packaging,
after a re-evaluation of the status of TensorFlow's latest build
systems. My thoughts are concluded from failures instead of success.
That said, they
On 09.04.19 05:32, Mo Zhou wrote:
Hi,
> I drafted a 0.0 alpha release[1] for the toolkit, and created a logo for
> the DUPR project. From now on I'll try to add more packaging scripts
> (maybe I should call them recipes) to the default collection[2].
> Packaing plans are tracked here[3], and mayb
Dear Mo,
On Tue, Apr 16, 2019 at 11:12:44AM +, Mo Zhou wrote:
> ...
> This time I'm really giving up all related efforts [12], and shall never
> touch them again. I don't feel pity, even if these points seem to be
> tightly connected to some of my Debian activities. Apart from that, I'm
> stil
On 10.04.19 03:53, Russ Allbery wrote:
Hi,
> Possibly my least favorite> thing about RPMs is the spec files, because by
> smashing everything>
together into the same file, the syntax of that file is absurd. This
bit> is a shell script! This bit is a configuration file! This bit is>
human-read
Hi again,
speaking about false positives:
libhmsbeagle (U) should switch to dh. Current build system:
debhelper (source version: 3.1.2+dfsg-5)
I have no idea what might have triggered this on the current d/rules
file[1].
Kind regards
Andreas.
[1] https://salsa.debian.org/me
Andreas Tille:
> Hi again,
>
> speaking about false positives:
>
>libhmsbeagle (U) should switch to dh. Current build system:
> debhelper (source version: 3.1.2+dfsg-5)
>
> I have no idea what might have triggered this on the current d/rules
> file[1].
>
> Kind regards
>
>
On 10.04.19 16:56, Helmut Grohne wrote:
Hi,
> I looked into this. Your reasons are sound and you are scratching your> itch.
> This is great.
ACK. It's always good when people make their hands dirty and work on
solving actual problems. Even if the actual output (=code, etc) finally
doesn't get wi
Hi Niels,
On Tue, Apr 16, 2019 at 12:54:00PM +, Niels Thykier wrote:
> > speaking about false positives:
> >
> >libhmsbeagle (U) should switch to dh. Current build system:
> > debhelper (source version: 3.1.2+dfsg-5)
> >
> > I have no idea what might have triggered this on the c
On 11.04.19 09:44, Mo Zhou wrote:
> Different from that, duprkit's design don't hope to limit> the user with any
> pre-defined "sequence", but enable the users to>
selectively call the functions they need. In other words, the> user can
define how to deal with the prepared source+debian directorie
On 13.04.19 10:20, Lucas Nussbaum wrote:
> TL;DR: see https://trends.debian.net and
> https://trends.debian.net/#smells
>
> Hi,
>
> Following this blog post[1] I did some work on setting up a proper
> framework to graph historical trends about Debian packaging practices.
> The result is now avail
Andreas Tille:
> Hi Niels,
>
> On Tue, Apr 16, 2019 at 12:54:00PM +, Niels Thykier wrote:
>>> speaking about false positives:
>>>
>>>libhmsbeagle (U) should switch to dh. Current build system:
>>> debhelper (source version: 3.1.2+dfsg-5)
>>>
>>> I have no idea what might have trig
Hello,
Thanks for the feedback. In the accessibility team we had interest in
https://github.com/mozilla/DeepSpeech but I got quickly afraid but the
mention of "TensorFlow" in dependencies, it seems I was right in not
taking time to have a look, unfortunately.
Samuel
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: upass
Version : 0.3.0
Upstream Author : Chris Warrick
* URL : https://github.com/Kwpolska/upass
* License : BSD-3-clause
Programming Lang:
Hi Andreas,
On Tue, Apr 16, 2019 at 02:29:54PM +0200, Andreas Tille wrote:
> Thanks a lot for the summary and all your previous work you've spent
> into this. As far as I understand your summary it would be even
> "burning" a student if we would throw theses packaging task on a
> student in a GSo
On Tue, Apr 16, 2019 at 01:57:00PM +, Niels Thykier wrote:
>
> > Similarly
> >
> > prottest (U) should switch to dh. Current build system:
> > debhelper (source version: 3.4.2+dfsg-3)
> > python-pyfaidx (U) should switch to dh. Current build system:
> > debhelper (source v
Package: wnpp
Severity: wishlist
Owner: Mirek Kratochvil
* Package name: dte
Version : 1.7
Upstream Author : Craig Barnes
* URL : https://craigbarnes.gitlab.io/dte/
* License : GPL
Programming Lang: C
Description : Small and easy to use console text ed
On Mon, 15 Apr 2019, Thomas Goirand wrote:
> On 4/15/19 9:24 AM, Hideki Yamane wrote:
> > On Sun, 14 Apr 2019 21:11:09 +0200
> > "Dr. Tobias Quathamer" wrote:
> >> I think it's the right decision of the release team to stick with golang
> >> 1.11 for buster. The previous migration from golang 1.10
On 4/13/19 10:20 AM, Lucas Nussbaum wrote:
> TL;DR: see https://trends.debian.net and
> https://trends.debian.net/#smells
>
> Hi,
>
> Following this blog post[1] I did some work on setting up a proper
> framework to graph historical trends about Debian packaging practices.
> The result is now ava
On 2019/04/16 21:51, Thomas Goirand wrote:
> I'm not sure if I should say thanks, or just hide myself behind the
> wall, considering how much work there would be to fix all of these
> packages that I need to fix... :/
Heh, that's exactly why these graphs are so great! Rome wasn't built in
a day ei
On Tue, Apr 16, 2019 at 02:29:54PM +0200, Andreas Tille wrote:
>...
> As far as I understand your summary it would be even
> "burning" a student if we would throw theses packaging task on a
> student in a GSoC / outreachy project (I'm aware that we are usually
> not supporting packaging tasks in th
On 16/04/19 at 15:55 +0200, Enrico Weigelt, metux IT consult wrote:
> On 13.04.19 10:20, Lucas Nussbaum wrote:
> > TL;DR: see https://trends.debian.net and
> > https://trends.debian.net/#smells
> >
> > Hi,
> >
> > Following this blog post[1] I did some work on setting up a proper
> > framework to
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
* Package name: redfishtool
Version : 1.0.8
Upstream Author : DMTF, https://www.dmtf.org/standards/feedback
* URL : https://github.com/DMTF/Redfishtool
* License : BSD-3-clause
Programming Lang: Python
Dear Mo,
Thanks for your work!
On Tue, Apr 16, 2019 at 11:53 PM Mo Zhou wrote:
>
> The student may also need access to a strong build machine. My Xeon
> E5-2687v4 x1 [1] takes about 20 minutes to finish a build, while my
> laptop (I5-7440HQ) takes ~90 minutes.
Have you tried ccache? Interested
Hi Jonathan,
On Mon, 15 Apr 2019 at 7:38 am, Jonathan Wiltshire wrote:
> At the time of writing 150 release-critical bugs affect buster. This is the
> number which needs to reach zero before the release can take place.
What’s the easiest way to get a list of these RC bugs?
Hugh
在 2019-04-17三的 08:44 +1000，Hugh McMaster写道：
> Hi Jonathan,
>
> On Mon, 15 Apr 2019 at 7:38 am, Jonathan Wiltshire wrote:
> > At the time of writing 150 release-critical bugs affect buster.
> > This is the
> > number which needs to reach zero before the release can take place.
>
> What’s the easie
Hi Adrian,
On Tue, Apr 16, 2019 at 11:07:34PM +0300, Adrian Bunk wrote:
>
> How many percent of the paid GSoC and Outreachy student workers
> continue unpaid afterwards and become a DM or DD?
It's not realistic to expect a student to continue any unpaid effort
after the GSoC / Outreachy particip
On 13.04.19 17:01, Joerg Jaspert wrote:
> On 15371 March 1977, Aurelien Jarno wrote:
>
>>> How is the move to debian-ports supposed to happen? I won't have the
>>> time to do anything about it within the 2 weeks.
>
>> The process to inject all packages to debian-ports is to get all the
>> deb, ud
Adrian Bunk:
> Outreachy is a complete failure.[1]
> […]
> [1] If anyone has data to prove that I am wrong, please let me to know.
I only have one single data point: the only person I've been an
Outreachy mentor for is now an active, uploading DD.
Cheers,
--
intrigeri
On Wed, Apr 17, 2019 at 08:44:20AM +1000, Hugh McMaster wrote:
> > At the time of writing 150 release-critical bugs affect buster. This is the
> > number which needs to reach zero before the release can take place.
>
>
> What’s the easiest way to get a list of these RC bugs?
https://udd.debian.or
31 matches
Mail list logo
