Re: Preferred git branch structure when upstream moves from tarballs to git

On 5/2/2019 7:11 AM, Ben Finney wrote: > Conversely, I think it does a disservice to downstream users to mix in > Debian packaging changes with upstream changes. The separation is useful > and much easier to maintain when the repositories are separate. To be honest the greatest disservice is that

Re: Preferred git branch structure when upstream moves from tarballs to git

Sean Whitton writes: > Hello, > > On Tue 30 Apr 2019 at 08:05AM +02, Ansgar wrote: > > > As an example: to update to a new upstream release, I ideally just > > have to drop the new upstream tarball, update d/changelog and am > > done. > > As a package maintainer, if you don't keep the whole sourc

Re: Preferred git branch structure when upstream moves from tarballs to git

Hello, On Wed 01 May 2019 at 09:53PM +0200, Adam Borowski wrote: > On Wed, May 01, 2019 at 08:14:24AM +0200, Thomas Goirand wrote: >> It's basically useless, since upstream repository is just one command >> away, with the upstream URL documented in debian/rules. > > This assumes the upstream URL

Bug#928319: ITP: ngraph -- C++ library, compiler and runtime for Deep Learning frameworks

Package: wnpp Severity: wishlist Owner: Mo Zhou * Package name: ngraph Version : Upstream Author : Nervana / Intel * URL : https://github.com/NervanaSystems/ngraph * License : Apache-2.0 Programming Lang: C++ Description : C++ library, compiler and run

Bug#928318: ITP: onnxruntime -- scoring engine for Open Neural Network Exchange (ONNX) models

Package: wnpp Severity: wishlist Owner: Mo Zhou * Package name: onnxruntime Version : 0.4.0 Upstream Author : Microsoft, et al. * URL : https://github.com/Microsoft/onnxruntime * License : MIT Programming Lang: C++ Description : scoring engine for Open

Re: Preferred git branch structure when upstream moves from tarballs to git

On Wed, May 01, 2019 at 08:14:24AM +0200, Thomas Goirand wrote: > It's basically useless, since upstream repository is just one command > away, with the upstream URL documented in debian/rules. This assumes the upstream URL lives forever. But what if the upstream repo's hoster (let's call it "ali

Minimal X11 footprint will be 5 times bigger with buster

I discovered that even though Xorg explicitly only recommends hardware-backed OpenGL it effectively depends it in buster, bloating minimal disk size of an X11 Debian system from 49 MB to 284 MB. This is reported as bug#928297 but sharing here as well, hoping that someone more knowledgeable than

Re: Preferred git branch structure when upstream moves from tarballs to git

Oh, only now I noticed that this has become a long thread. Sorry for the out-of-context reply. :) On 01 May 2019, Gabriel F. T. Gomes wrote: >On 29 Apr 2019, Gard Spreemann wrote: > >>For one of my packages, I maintain two public git branches: one is >>upstream/latest, where I've been importing

Re: Preferred git branch structure when upstream moves from tarballs to git

On 29 Apr 2019, Gard Spreemann wrote: >For one of my packages, I maintain two public git branches: one is >upstream/latest, where I've been importing upstream's released tarballs, >and the other is debian/sid that contains the packaging. > >Recently, upstream has finally started using git. What is

Bug#928287: ITP: python-qutip -- python package for simulating the dynamics of open quantum systems

Package: wnpp Severity: wishlist Owner: Drew Parsons * Package name: python-qutip Version : 4.3.1 Upstream Author : Paul D. Nation and Robert J. Johansson * URL : http://qutip.org/ * License : BSD Programming Lang: Python Description : python package fo