Package: wnpp
Severity: wishlist
Owner: Andreas Tille
* Package name: r-other-x4r
Version : 1.0.1+git20150806.c6bd9bd
Upstream Author : George Chow; Norris Lee
* URL : https://github.com/overcoil/X4R
* License : GPL-2
Programming Lang: GNU R
Description
Package: wnpp
Severity: wishlist
Owner: Rafael Laboissière
* Package name: octave-lssa
Version : 0.1.2
Upstream Author : Ben Lewis
* URL : https://octave.sourceforge.io/lssa/
* License : GPL-v3+
Programming Lang: Octave, C++
Description : least square
On Thu, May 24, 2018 at 09:02:04PM +0200, Sebastiaan Couwenberg wrote:
> On 05/24/2018 08:53 PM, Raphael Hertzog wrote:
> > On Thu, 24 May 2018, Sebastiaan Couwenberg wrote:
> >> None of the other QA tools mail the maintainer without them asking for
> >> it, autopkgtest shouldn't either.
> >
> > W
Hello,
On Thu, May 24 2018, Ian Jackson wrote:
> I realise I am clearly some kind of antediluvian throwback, but: using
> the issue tracker means running a massive pile of javascript, and then
> creating an account. So people who have not already paid that price
> might prefer an email address.
On 25/05/18 12:09, Mattia Rizzolo wrote:
> autoremoval mails contains tons of false positive and cases where
> regular package maintainers can do nothing about but watch.
Can you give some examples of false positives in autoremoval mails?
Do you mean the case where you just fixed your package but
On Fri, May 25, 2018 at 12:16:20PM +0200, Emilio Pozuelo Monfort wrote:
> On 25/05/18 12:09, Mattia Rizzolo wrote:
> > autoremoval mails contains tons of false positive and cases where
> > regular package maintainers can do nothing about but watch.
>
> Can you give some examples of false positives
On 05/25/2018 12:09 PM, Mattia Rizzolo wrote:
> On Thu, May 24, 2018 at 09:02:04PM +0200, Sebastiaan Couwenberg wrote:
>> On 05/24/2018 08:53 PM, Raphael Hertzog wrote:
>>> On Thu, 24 May 2018, Sebastiaan Couwenberg wrote:
None of the other QA tools mail the maintainer without them asking for
On 25/05/18 12:24, Mattia Rizzolo wrote:
> On Fri, May 25, 2018 at 12:16:20PM +0200, Emilio Pozuelo Monfort wrote:
>> On 25/05/18 12:09, Mattia Rizzolo wrote:
>>> autoremoval mails contains tons of false positive and cases where
>>> regular package maintainers can do nothing about but watch.
>>
>>
Emilio Pozuelo Monfort writes ("Re: RFR: email about regressions [was: Dealing
with ci.d.n for package regressions]"):
> On 25/05/18 12:24, Mattia Rizzolo wrote:
> > But rather than false positive I should have said "things a maintainer
> > can usually do ~nothing about", like RC bugs on other pac
On Fri, May 25, 2018 at 03:13:43AM -0700, Sean Whitton wrote:
> Thank you for advocating on behalf of users who are not in a position to
> use the web form, Ian.
indeed, thanks, Ian.
--
cheers,
Holger
signature.asc
Description: PGP signature
Sean Whitton writes ("Re: Bug#864354: Bug #864354 in marked as
pending"):
> Thank you for advocating on behalf of users who are not in a position to
> use the web form, Ian.
Thanks for your support, Sean. I have submitted:
https://salsa.debian.org/salsa/webhook/merge_requests/7
Improve ema
Hi!
I heard a rumour some of us might need to read a package build log from time
to time. Those have grown enormously wordy during past decades: we include
all kinds of doodads about the build environment, and the compilation itself
has all verbosity options turned on. This makes searching for th
Ian Jackson writes ("Want to make salsa advertise contact and source code
details"):
> https://salsa.debian.org/salsa/support/issues/77
>Please provide web page footer on every page with service information
>
> In response to the latter, Alexander Wirt writes:
>
> Unless this is possible
On Fri, 25 May 2018, Ian Jackson wrote:
> Sean Whitton writes ("Re: Bug#864354: Bug #864354 in marked as
> pending"):
> > Thank you for advocating on behalf of users who are not in a position to
> > use the web form, Ian.
>
> Thanks for your support, Sean. I have submitted:
>
> https://salsa
Quoting my own other mail for more context:
Ian Jackson writes ("Re: Want to make salsa advertise contact and source code
details"):
> Alexander Wirt tells me that that feature is "EE only", ie AIUI
> that the Gitlab company have kept that feature proprietary.
>
> That means our choices are:
...
Package: wnpp
Severity: wishlist
Owner: Vanessa McHale
* Package name: polyglot-count
Version : 0.4.42
Upstream Author : Vanessa McHale
* URL : http://github.com/vmchale/polyglot
* License : BSD3
Programming Lang: ATS
Description : Polyglot is a comman
On Fri, 25 May 2018, Ian Jackson wrote:
> Quoting my own other mail for more context:
>
> Ian Jackson writes ("Re: Want to make salsa advertise contact and source code
> details"):
> > Alexander Wirt tells me that that feature is "EE only", ie AIUI
> > that the Gitlab company have kept that feat
On Fri, May 25, 2018 at 02:54:17PM +0200, Alexander Wirt wrote:
> On Fri, 25 May 2018, Ian Jackson wrote:
> >
> >
> > But, I find this response worrying. It makes me wonder whether Salsa
> > is in fact really Free Software, for Debian. I don't want to suck
> > energy out of the Salsa team, but:
On Fri, 2018-05-25 at 17:16 +0200, Geert Stappers wrote:
> Not knowing who is "we", but the thing I want to says is
>
> Do not ask for a lighter load,
> but ask for more shoulders to carry the load.
Asking for a lighter load has given us the wheel, washing machines,
dishwashers, computers, an
Alexander Wirt writes ("Re: Want to make salsa advertise contact and source
code details [and 1 more messages]"):
> > Can you point me to the source code for Salsa's gitlab instance,
> > please ?
> https://salsa.debian.org/salsa/gitlab-ce
I think I see where to make the change. How should I test
On Fri, 25 May 2018, Ian Jackson wrote:
> Alexander Wirt writes ("Re: Want to make salsa advertise contact and source
> code details [and 1 more messages]"):
> > > Can you point me to the source code for Salsa's gitlab instance,
> > > please ?
> > https://salsa.debian.org/salsa/gitlab-ce
>
> I t
On Fri, 25 May 2018, Geert Stappers wrote:
> On Fri, May 25, 2018 at 02:54:17PM +0200, Alexander Wirt wrote:
> > On Fri, 25 May 2018, Ian Jackson wrote:
> > >
> > >
> > > But, I find this response worrying. It makes me wonder whether Salsa
> > > is in fact really Free Software, for Debian. I d
Alexander Wirt writes ("Re: Want to make salsa advertise contact and source
code details [and 1 more messages]"):
> It was a decision by the team to disallow any patch that is not
> really really needed for function. Please submit your patch
> upstream.
I see. I'm afraid I strongly disagree with
*rings chimes*
On 25/05/2018 19:16, Ian Jackson wrote:
> Can you please tell me what you think the appropriate path or venue is
> for me to pursue this diagreement ?
I notice GitLab has a plugin system, would it be possible to affect that
change in a plugin? That way it's at least not a patch to
On Fri, 25 May 2018, Ian Jackson wrote:
> Alexander Wirt writes ("Re: Want to make salsa advertise contact and source
> code details [and 1 more messages]"):
> > It was a decision by the team to disallow any patch that is not
> > really really needed for function. Please submit your patch
> > ups
Hi
On 25-05-18 12:34, Sebastiaan Couwenberg wrote:
> DDPO, tracker.d.o, and the testing excuses already show the autopkgtest
> information I'm interested in.
>
> Unlike some maintainers I track the state of my packages daily and closely.
I said it before, and I am saying it again: not yet for th
Jonathan Carter writes ("Re: Want to make salsa advertise contact and source
code details [and 1 more messages]"):
> On 25/05/2018 19:16, Ian Jackson wrote:
> > Can you please tell me what you think the appropriate path or venue is
> > for me to pursue this diagreement ?
>
> I notice GitLab has a
Ian Jackson writes ("Re: Want to make salsa advertise contact and source code
details [and 1 more messages]"):
> Oh, quite possibly. I don't know anything about gitlab's plugin
> system.
... I don't think so, in fact. I found this documentation:
https://docs.gitlab.com/ce/administration/plugi
On Fri, 2018-05-25 at 18:57 +0100, Ian Jackson wrote:
> Another way to achieve the effect I want would be to do it post-hoc in
> a reverse proxy. I see that salsa is using Apache as a reverse proxy.
> So perhaps the right answer is to do this in Apache. It seems quite
> hacky, but if it's thought
On Fri, May 25, 2018 at 02:21:34PM +0200, Adam Borowski wrote:
> I heard a rumour some of us might need to read a package build log from time
> to time. Those have grown enormously wordy during past decades: we include
> all kinds of doodads about the build environment, and the compilation itself
Guus Sliepen writes:
> Even more helpful would be to NOT display anything irrelevant. When a
> package fails to build, I am generally only interested in the error
> message, not everything that led up to it, because up until the error
> message everything went fine, and the likelyhood that there
An upstream package I look after switched from sf.net to bintray. Do we have
a trick to parse layout via uscan?
Please CC me as I am no longer subscribed to debian-devel.
Dirk
--
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Guus Sliepen - 25.05.18, 21:46:
> On Fri, May 25, 2018 at 02:21:34PM +0200, Adam Borowski wrote:
> > I propose to add a new flag: DEB_BUILD_OPTIONS=color.
[…]
> That would be very helpful.
>
> Even more helpful would be to NOT display anything irrelevant. When a
> package fails to build, I am gene
On 26/05/18 12:28, Ben Caradoc-Davies wrote:
On 26/05/18 00:21, Adam Borowski wrote:
It might be good to pipe output through ansi2txt
Thank you so much for alerting me to ansi2txt. Given the miserable
failure of some command line tool authors to contemplate terminal
background colours other th
On 26/05/18 00:21, Adam Borowski wrote:
It might be good to pipe output through ansi2txt
Thank you so much for alerting me to ansi2txt. Given the miserable
failure of some command line tool authors to contemplate terminal
background colours other than black, I have had to endure all manner of
On Fri, 25 May 2018, 22:21 Adam Borowski, wrote:
> But, nice folks who make gcc have introduced an option which helps here:
> -fdiagnostics-color. It's very nice even for terse logs (such as the
> kernel), but for our use case it gives a ridiculously good improvement:
> instead of having to read
On Sat, May 26, 2018 at 5:23 AM, Dirk Eddelbuettel wrote:
> An upstream package I look after switched from sf.net to bintray.
Which upstream? Please link to bintray.
> Do we have a trick to parse layout via uscan?
Looks like only minor tricks are needed:
https://codesearch.debian.net/search?q=
On 26 May 2018 at 10:17, Paul Wise wrote:
| On Sat, May 26, 2018 at 5:23 AM, Dirk Eddelbuettel wrote:
|
| > An upstream package I look after switched from sf.net to bintray.
|
| Which upstream? Please link to bintray.
Quantlib.
upstream web https://www.quantlib.org/
upstream src https://g
On Sat, May 26, 2018 at 10:31 AM, Dirk Eddelbuettel wrote:
> Quantlib.
> upstream web https://www.quantlib.org/
> upstream src https://github.com/lballabio/QuantLib
> my srchttps://salsa.debian.org/edd/quantlib
Can't you use the github releases?
https://github.com/lballabio/Quant
On 26 May 2018 at 10:42, Paul Wise wrote:
| On Sat, May 26, 2018 at 10:31 AM, Dirk Eddelbuettel wrote:
|
| > Quantlib.
| > upstream web https://www.quantlib.org/
| > upstream src https://github.com/lballabio/QuantLib
| > my srchttps://salsa.debian.org/edd/quantlib
|
| Can't you u
On Sat, May 26, 2018 at 10:50 AM, Dirk Eddelbuettel wrote:
>https://www.quantlib.org/download.shtml
The bintray URL there eventually points here:
https://dl.bintray.com/quantlib/releases/
That has all the versions and if you remove the : character from the
download URLs, then you can get ta
Package: wnpp
Severity: wishlist
Owner: Xavier Guimard
* Package name: node-lemonldap-ng-handler
Version : 0.2.7
Upstream Author : Xavier Guimard
* URL : https://github.com/LemonLDAPNG/node-lemonldap-ng-handler
* License : GPL-2+
Programming Lang: JavaScript
42 matches
Mail list logo
