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: 1165 (new: 3)
Total number of packages offered up for adoption: 150 (new: 2)
Total number of packages reques
Package: wnpp
Severity: wishlist
Owner: Mike Gabriel
* Package name: vala-panel
Version : 0.3.71
Upstream Author : Konstantin P.
* URL : https://github.com/rilian-la-te/vala-panel
* License : GPL-2+, LGPL-2.1+
Programming Lang: Vala
Description : Deskt
On 18/01/18 21:50, Adrian Bunk wrote:
> On Thu, Jan 18, 2018 at 06:52:57PM +0100, Emilio Pozuelo Monfort wrote:
>> On 10/01/18 01:29, Sam Hartman wrote:
>>> A build profile seems like a great way to express the flag, and like
>>> many things in Debian, the work would fall on those who would benefit
On Thu, Jan 18, 2018 at 06:52:57PM +0100, Emilio Pozuelo Monfort wrote:
> On 10/01/18 01:29, Sam Hartman wrote:
> > A build profile seems like a great way to express the flag, and like
> > many things in Debian, the work would fall on those who would benefit
> > from it.
>
> I think it'd be better
On Wednesday 17 January 2018 18:07:59 Pali Rohár wrote:
> Ok, that you for opinion. I drop init script and include upstream udev
> rule which replace it. And because there is no feature request for
> splitting package into more, I let it as is to not complicate it.
Updated package is there: https:
On Thu, 18 Jan 2018, Emilio Pozuelo Monfort wrote:
> I think it'd be better to be able to mark a build-dependency as
> optional, and then implement a mechanism in dpkg to disable the
> undesired build-dependencies.
Someone who was interested could get part way to this by running builds
with an emp
On 10/01/18 01:29, Sam Hartman wrote:
> A build profile seems like a great way to express the flag, and like
> many things in Debian, the work would fall on those who would benefit
> from it.
I think it'd be better to be able to mark a build-dependency as optional, and
then implement a mechanism i
Matt Zagrabelny writes ("Re: Why do we list individual copyright holders?"):
> On Tue, Jan 16, 2018 at 10:53 AM, Ian Jackson
>
> wrote:
>
> But I'm a hardy soul who is quite prepared to see a warning and decide
> to ignore it :-).
>
> My view is that the purpose of a warning is to a
On Thu, 18 Jan 2018, Arturo Borrero Gonzalez wrote:
> On 18 January 2018 at 11:15, Alex Mestiashvili
> wrote:
> > Hi All,
> >
> > while browsing through salsa.debian.org packages I got a feeling that
> > displaying upstream's Readme by default is not exactly relevant to
> > Debian packages. I gu
Package: wnpp
Severity: wishlist
Owner: Joris Goosen
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: jasp
Version : 0.8.5
Upstream Author : JASP-team
* URL : http://www.jasp-stats.org/
* License : GPL
Programming Lang: C++, R
Description :
On 18 January 2018 at 11:15, Alex Mestiashvili wrote:
> Hi All,
>
> while browsing through salsa.debian.org packages I got a feeling that
> displaying upstream's Readme by default is not exactly relevant to
> Debian packages. I guess it would make more sense do display
> d/Readme.source if availab
Hi All,
while browsing through salsa.debian.org packages I got a feeling that
displaying upstream's Readme by default is not exactly relevant to
Debian packages. I guess it would make more sense do display
d/Readme.source if available or d/changelog instead.
Or even something more advanced like tr
12 matches
Mail list logo
