Re: Automatic trimming of changelogs in binary packages
19 septembre 2022 23:19 "Bill Allombert" a écrit: > Le Tue, Sep 06, 2022 at 07:13:30AM +0200, Gioele Barabucci a écrit : > >> On 18/08/22 21:18, Gioele Barabucci wrote: >> Does anybody have objective objections against activating automatic >> changelog trimming in binary packages? >> >> Hi, >> >> a couple of weeks since the initial email (thanks everybody for the input), >> my reading is that there is now consensus in going ahead with the proposed >> automatic trimming of changelogs. > > Count me out. changelog embbed Debian history. The very first entries > are often very important. They can be important _in the source package_. I have yet to see binary packages for which having access to early debian/changelog entries matters at all. ( debian/NEWS is another story of course, and these are not affected).
Q: uscan with GitHub
On Tue 20 Sept 2022, 01:39 Paul Wise, wrote: On Mon, 2022-09-19 at 18:54 +0200, Andrea Pappacoda wrote: > Hi, what I usually do with GitHub is to use its API, since it has the > advantage of not breaking uscan when they do changes to the web UI. Since the API uses pagination, this has the minor downside of making it harder to use the uscan --download-version option with older versions. The GitHub pages are also paginated, so you get the same issue whether using the API or not. I have been hit by this on cases where upstream does enough beta|rc|snapshots releases such that the latest GA release gets in the second page and uscan fails due to not finding it.
Bug#1020332: ITP: python-mrcfile -- Python implementation of the MRC2014 file format
Package: wnpp Severity: wishlist Owner: Roland Mas X-Debbugs-Cc: debian-devel@lists.debian.org, debian-pan-maintain...@alioth-lists.debian.net * Package name: python-mrcfile Version : 1.4.2 Upstream Author : Colin Palmer * URL : https://github.com/ccpem/mrcfile * License : BSD Programming Lang: Python Description : Python implementation of the MRC2014 file format mrcfile is a Python implementation of the MRC2014 file format, which is used in structural biology to store image and volume data. It allows MRC files to be created and opened easily using a very simple API, which exposes the file's header and data as numpy arrays. The code runs in Python 2 and 3 and is fully unit-tested. This library aims to allow users and developers to read and write standard-compliant MRC files in Python as easily as possible, and with no dependencies on any compiled libraries except numpy. You can use it interactively to inspect files, correct headers and so on, or in scripts and larger software packages to provide basic MRC file I/O functions. Key Features * Clean, simple API for access to MRC files * Easy to install and use * Validation of files according to the MRC2014 format * Seamless support for gzip and bzip2 files * Memory-mapped file option for fast random access to very large files * Asynchronous opening option for background loading of multiple files * Runs in Python 2 & 3, on Linux, Mac OS X and Windows This package will be maintained within the Python team on Salsa.
Re: Q: uscan with GitHub
On Tue, Sep 20, 2022 at 10:36 AM Samuel Henrique wrote: > On Tue 20 Sept 2022, 01:39 Paul Wise, wrote: > > On Mon, 2022-09-19 at 18:54 +0200, Andrea Pappacoda wrote: > > > Hi, what I usually do with GitHub is to use its API, since it has the > > advantage of not breaking uscan when they do changes to the web UI. > > Since the API uses pagination, this has the minor downside of making it > harder to use the uscan --download-version option with older versions. > > > The GitHub pages are also paginated, so you get the same issue whether > using the API or not. > There is a per_page parameter: https://docs.github.com/en/rest/releases/releases#list-releases E.g. https://api.github.com/repos/torvalds/linux/tags?per_page=100 The maximum is 100 though. Cheers, Stephan
Re: Q: uscan with GitHub
On Tue, Sep 20, 2022 at 08:36:48AM +0800, Paul Wise wrote: > On Mon, 2022-09-19 at 18:54 +0200, Andrea Pappacoda wrote: > > Hi, what I usually do with GitHub is to use its API, since it has the > > advantage of not breaking uscan when they do changes to the web UI. > Since the API uses pagination, this has the minor downside of making it > harder to use the uscan --download-version option with older versions. Well, uscan can properly implement pagination. It is just not a simple scraper anymore. Bastian -- It is more rational to sacrifice one life than six. -- Spock, "The Galileo Seven", stardate 2822.3
Bug#1020398: ITP: jqp -- A TUI playground to experiment with jq
Package: wnpp Severity: wishlist Owner: Stephen Gelman * Package name: jqp Version : 0.1.0-1 Upstream Author : Noah Gorstein * URL : https://github.com/noahgorstein/jqp * License : Expat Programming Lang: Go Description : A TUI playground to experiment with jq A TUI tool that allows for experimentation with jq with fast iteration. This application utilizes itchny's (https://github.com/itchyny) implementation of jq written in Go, gojq (https://github.com/itchyny/gojq). This package will be team maintained by the go team.
