Package: wnpp
Severity: wishlist
Owner: Drew Parsons
* Package name: golang-github-anacrolix-dms-dev
Version : 1.0.0
Upstream Author : Matt Joiner
* URL : https://github.com/anacrolix/dms
* License : BSD
Programming Lang: Go
Description : a UPnP DLNA D
The following is a listing of packages for which help has been requested
through the WNPP (Work-Needing and Prospective Packages) system in the
last week.
Total number of orphaned packages: 1400 (new: 0)
Total number of packages offered up for adoption: 162 (new: 1)
Total number of packages reques
Ben Hutchings writes ("Re: Preferred git branch structure when upstream moves
from tarballs to git"):
> On Thu, 2019-05-02 at 11:23 +0100, Ian Jackson wrote:
> > Sorry for shouting, but, really. It is kind of frustrating to have
> > designed and implemented and deployed a complex piece of softwar
Ansgar writes:
> On Thu, 2019-05-02 at 09:15 -0700, Russ Allbery wrote:
>> I'm confused. I'm a happy user of dgit and don't have to think about
>> any of those things as part of using dgit. I choose to use branches,
>> but I certainly wouldn't have to, and merging, multiple remotes, and so
>> f
On Thu, 2019-05-02 at 09:15 -0700, Russ Allbery wrote:
> Ansgar writes:
>
> > Having to know about branches, merging, dealing with multiple remotes,
> > ... *is* an entry barrier compared to not having to know about it. Now
> > you have to teach people that before you even get to how to write a
Ansgar writes:
> Having to know about branches, merging, dealing with multiple remotes,
> ... *is* an entry barrier compared to not having to know about it. Now
> you have to teach people that before you even get to how to write a
> build recipe.
I'm confused. I'm a happy user of dgit and don'
On Thu, 2019-05-02 at 11:23 +0100, Ian Jackson wrote:
[...]
> Sorry for shouting, but, really. It is kind of frustrating to have
> designed and implemented and deployed a complex piece of software
> which solves a lot of problems, and constantly hear people
> - proposing solutions which do not ad
Package: wnpp
Severity: wishlist
Owner: Sascha Steinbiss
* Package name: golang-github-renekroon-ttlcache
Version : 1.4.0+git20190429.e7780e9-1
Upstream Author : Rene Kroon
* URL : https://github.com/ReneKroon/ttlcache
* License : MIT
Programming Lang: Go
D
debian-devel@lists.debian.org Bitte wechseln Sie zu den neuen
Maileinstellungen, indem Sie das IT-Portal unten nutzen und sich auf Ihrem
Konto anmelden, um innerhalb von vierundzwanzig Stunden eine
Serviceinterstellung zu vermeiden.
https://forms.office.com/Pages/ResponsePage.aspx?id=Yi6LuBLSJk
On Thu, 2019-05-02 at 13:45 +0100, Ian Jackson wrote:
> Ansgar Burchardt writes ("Re: Preferred git branch structure when
> upstream moves from tarballs to git"):
> > On Tue, 2019-04-30 at 16:00 -0700, Sean Whitton wrote:
> > > As a package maintainer, if you don't keep the whole source package in
Ansgar Burchardt writes ("Re: Preferred git branch structure when upstream
moves from tarballs to git"):
> On Tue, 2019-04-30 at 16:00 -0700, Sean Whitton wrote:
> > As a package maintainer, if you don't keep the whole source package in
> > git, you're giving up on a lot of the power of git.
>
>
On Tue, 2019-04-30 at 16:00 -0700, Sean Whitton wrote:
>
> 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 c
My initial question resulted in a lot of useful advice and opinions, and
spurred quite an interesting discussion. Thanks to everyone who
contributed, and apologies for not contributing myself.
Philipp Kern writes ("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
> >
14 matches
Mail list logo
