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

On 4/30/19 9:55 AM, Adam Borowski wrote: > On Tue, Apr 30, 2019 at 09:04:09AM +0200, Thomas Goirand wrote: >> What I found the most easy way is to just use whatever branching names >> upstream is using, and *never* store them in Salsa. If you need upstream >> repository, you can simply run a ./debi

Bug#928273: dgit: want separate manpage on conversion between workflows

Package: dgit Version: 8.4 Severity: wishlist X-debbugs-cc: Ian Jackson , debian-devel@lists.debian.org, Ian Campbell There should be a manpage on converting between workflows. On Mon 29 Apr 2019 at 01:50PM -07, Sean Whitton wrote: > dgit-maint-merge -> dgit-maint-debrebase would indeed be the

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

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. > Compare with [1] which is much more complicated, even ignoring the extra > complexity using dgit

CheckPoint Customers List 2019

Hi, I understand that you are a “Checkpoint Customers 2019” and have presence in many parts of the world. However, if you think of expanding your business further worldwide, we would be able to provide you client lists with accurate phone numbers, verified e-mails, contact names, job titles

Bug#928260: ITP: golang-github-jefferai-jsonx -- Object or JSON -> JSONx. Because sometimes your luck runs out.

Package: wnpp Severity: wishlist Owner: Dawid Dziurla * Package name: golang-github-jefferai-jsonx Version : 1.0.0-1 Upstream Author : Jeff Mitchell * URL : https://github.com/jefferai/jsonx * License : MPL-2.0 Programming Lang: Go Description : Object

Bug#928259: ITP: golang-github-jeffail-gabs -- For parsing, creating and editing unknown or dynamic JSON in Go

Package: wnpp Severity: wishlist Owner: Dawid Dziurla * Package name: golang-github-jeffail-gabs Version : 1.2.0-1 Upstream Author : Ashley Jeffs * URL : https://github.com/Jeffail/gabs * License : Expat Programming Lang: Go Description : For parsing, c

Re: Bits from the DPL (April 2019)

Thanks very much for the reply! Have you been discussing this with the gitlab people? They seem very open to discuss with projects, e.g. see https://gitlab.com/gitlab-org/gitlab-ce/issues/53206 I understand your points (especially agree on moving bugs between different projects) and that there is n

Bug#928258: ITP: golang-github-sap-go-hdb -- SAP HANA Database Client for Go

Package: wnpp Severity: wishlist Owner: Dawid Dziurla * Package name: golang-github-sap-go-hdb Version : 0.14.1-1 Upstream Author : SAP * URL : https://github.com/SAP/go-hdb * License : Apache-2.0 Programming Lang: Go Description : SAP HANA Database Cli

Bug#928255: ITP: golang-github-schollz-closestmatch -- Golang library for fuzzy matching within a set of strings

Package: wnpp Severity: wishlist Owner: Dawid Dziurla * Package name: golang-github-schollz-closestmatch Version : 2.1.0-1 Upstream Author : Zack * URL : https://github.com/schollz/closestmatch * License : TODO Programming Lang: Go Description : Golang

Re: Handling Japanese new era "令和 (Reiwa)"

On 30/04/2019 15:09, Hideki Yamane wrote: On Tue, 30 Apr 2019 14:52:37 +0100 Alastair McKinstry wrote: Time to go file RC bugs. Are those FTBFS for unicode-data 12.0.0, too? Yes. Ack, will file those to BTS later (wait for a while...) And maybe non-FTBFS packages are also necessar

Bug#928239: ITP: r-cran-openimager -- read, analyse, modify, write images with R

Package: wnpp Severity: wishlist Owner: Steffen Moeller * Package name: r-cran-openimager * URL : https://cran.r-project.org/web/packages/OpenImageR * License : Misc. non-free Programming Lang: R Description : read, analyse, modify, write images with R Team mainta

Bug#928238: ITP: r-cran-tiff -- read and write TIFF images with R

Package: wnpp Severity: wishlist Owner: Steffen Moeller * Package name: r-cran-tiff * URL : https://cran.r-project.org/web/packages/tiff/ * License : GPL Programming Lang: R Description : read and write TIFF images with R Team maintained on https://salsa.debian.or

Bug#928237: ITP: r-cran-jpeg -- read and write JPEG images with R

Package: wnpp Severity: wishlist Owner: Steffen Moeller * Package name: r-cran-jpeg * URL : https://cran.r-project.org/package=jpeg * License : GPL Programming Lang: R Description : read and write JPEG images with R Team-maintained on https://salsa.debian.org/r-pk

Bug#928236: ITP: e-antic -- Real Embedded Algebraic Number Theory In C

Package: wnpp Severity: wishlist Owner: Jerome Benoit * Package name: e-antic Version : 0.1.2 Upstream Author : Vincent Delecroix * URL : https://github.com/videlec/e-antic * License : LGPL-3 Programming Lang: C/C++ Des

Re: Handling Japanese new era "令和 (Reiwa)"

On Tue, 30 Apr 2019 14:52:37 +0100 Alastair McKinstry wrote: > >> Time to go file RC bugs. > > Are those FTBFS for unicode-data 12.0.0, too? > > > Yes. Ack, will file those to BTS later (wait for a while...) And maybe non-FTBFS packages are also necessary to be built against newer unicode-d

Re: Handling Japanese new era "令和 (Reiwa)"

On 30/04/2019 14:48, Hideki Yamane wrote: gucharmap can be built with small patch (will push MR for it). Time to go file RC bugs. Are those FTBFS for unicode-data 12.0.0, too? Yes. -- Alastair McKinstry, email: alast...@sceal.ie, matrix: @alastair:sceal.ie Commander Vimes didn’t lik

Re: Handling Japanese new era "令和 (Reiwa)"

Hi, Thanks, Alastair. On Thu, 25 Apr 2019 08:55:01 +0100 Alastair McKinstry wrote: > > I've uploaded 12.0.0 to unstable; 12.1 is not officially released yet. > > unicode-data itself is small and easy to validate, but the following > > packages will need to be rebuilt as they build-depend on u

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

On Tue, 2019-04-30 at 12:05 +0100, Ian Jackson wrote: > Sean Whitton writes ("Re: Preferred git branch structure when upstream moves > from tarballs to git"): > > On Mon 29 Apr 2019 at 02:12PM +01, Ian Campbell wrote: > > > > > > I think (but don't know) that the answer is that if your queue drop

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

Sean Whitton writes ("Re: Preferred git branch structure when upstream moves from tarballs to git"): > On Mon 29 Apr 2019 at 02:12PM +01, Ian Campbell wrote: > > Are there any docs/advice on switching back and forth between these (or > > at least switching between dgit-maint-merge and one of the p

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

On Mon, 2019-04-29 at 13:50 -0700, Sean Whitton wrote: > > dgit-maint-merge -> dgit-maint-debrebase would indeed be the > convert-from-dgit-view subcommand. If I were dealing with this, for > simplicity, I would start from the point of just having made an upload. > That way you know your HEAD is

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

On Tue, Apr 30, 2019 at 09:04:09AM +0200, Thomas Goirand wrote: > What I found the most easy way is to just use whatever branching names > upstream is using, and *never* store them in Salsa. If you need upstream > repository, you can simply run a ./debian/rules fetch-upstream-remote, > and most of

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

On 4/29/19 11:18 AM, Gard Spreemann wrote: > Hi, > > 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