Alternatively if one wanted to get more sophisticated than just
importing every version from snapshot in version number order, one
might write something to look inside the package at the changelogs to
try to discern the branch structure.
https://github.com/plugwash/autoforwardportergit/blob/maste
Package: wnpp
Severity: wishlist
Owner: Ron
* Package name: libopusenc
Version : 0.2.1
Upstream Author : Xiph.Org
* URL : http://opus-codec.org/development/
* License : BSD
Programming Lang: C
Description : High-level API for encoding Ogg Opus audio str
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-mtrmac-gpgme
Version : 0.0~git20170102.b243242-1
Upstream Author : Miloslav Trmač
* URL : https://github.com/mtrmac/gpgme
* License : BSD-3-clause
Programming Lang: Go
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
Package name: python-pydrive
Version: 1.3.1
Upstream Author: Robin Nabel
URL: https://pypi.org/project/PyDrive/
License: Apache-2.0
Description: Python API for Google Drive
PyDrive is a
On Monday, 11 February 2019 09:51:11 CET Jérémy Lal wrote:
> that's what i tried to do in the first place.
> However, the lack of v8 soname and abi stability across versions gave me so
> much additional work that i ended up not doing it at all, leading to v8
> being unmaintained. The solution here
Jonathan Dowland writes ("Re: Recreating history of a package"):
> On Wed, Feb 06, 2019 at 06:32:02PM +0100, Carsten Schoenert wrote:
> >I know of at least git-buildpackage will do this with the option
> >'--import-dscs' by importing all available versions from the Debian
> >archives.
> >
> >I assu
Le lun. 11 févr. 2019 à 09:11, Dominique Dumont a écrit :
> Hi
>
> On Friday, 8 February 2019 12:10:01 CET Jérémy Lal wrote:
> > > I suppose i need to ask a removal of libv8 from unstable (it's removed
> > > from testing) to
> > > be able to "take" libv8-dev. Or maybe declare a libv8-in-nodejs-de
Hi
On Friday, 8 February 2019 12:10:01 CET Jérémy Lal wrote:
> > I suppose i need to ask a removal of libv8 from unstable (it's removed
> > from testing) to
> > be able to "take" libv8-dev. Or maybe declare a libv8-in-nodejs-dev
> > package ?
> > In any case i don't know if i should make a libv8-x
8 matches
Mail list logo