Package: wnpp
Severity: wishlist
Owner: Abhishek Lolage
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-plur
Version : 2.1.2
Upstream Author : Sindre Sorhus (sindresorhus.com)
* URL : https://github.com/sindresorhus/plur
* License : Expat
P
Matthias Klose wrote...
> fyi, I NMUed logrotate yesterday to fix #849743, currently in delayed. Please
> add this fix to your upload.
Thanks for the heads-up, included in ~exp2 I had to do for other
reasons as well.
Christoph
signature.asc
Description: Digital signature
Package: wnpp
Severity: wishlist
Owner: Nupur Malpani
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-get-port
Version : 2.1.0
Upstream Author : Sindre Sorhus (sindresorhus.com
)
* URL : https://github.com/sindresorhus/get-port
* License : Exp
Package: wnpp
Severity: wishlist
Owner: Roshan Nalawade
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-pinkie
Version : 2.0.4
Upstream Author : Vsevolod Strukchinsky (
github.com/floatdrop)
* URL : https://github.com/floatdrop/pinkie
* License
> jenkins.d.n would be the place to put full-system cross-grading tests.
> piuparts would be the place to put per-package cross-grading tests.
FWIW, I just went through a cross-grade of a Lil'Debi chroot from armel
to armhf. I wouldn't recommend it to someone who's not used to command
line use of
Nikolaus Rath writes:
>> I have had to sort out the mess when the Debian package upload
>> did not match my git tree because another maintainer didn't correctly
>> merge in my changes.
>
> I don't understand... how does a Debian package upload affect any of the
> work on your git-dpm tree?
I can
On Jan 05 2017, Brian May wrote:
> Vincent Bernat writes:
>
>> There have been a lot of complaints about it. For me, it is a pain to
>> use. Its integration with gbp is poor, it produces a messy history when
>> you are working on your patches and I often run into problems with
>> .debian/.git-dpm
Brian May writes:
> No, my understanding that is git pq is something quite different, and
> does not maintain the history of changes in git - except by commiting
> the debian/patches/* files. It is a while since I looked at this in
> depth however.
That's correct. gbp pq is equivalent to mainta
http://houstonknanayacatholics.com/xuowwnd.php
...A happy life consists in tranquillity of
mind.Kelsi Guillemette
Vincent Bernat writes:
> There have been a lot of complaints about it. For me, it is a pain to
> use. Its integration with gbp is poor, it produces a messy history when
> you are working on your patches and I often run into problems with
> .debian/.git-dpm file it maintains (import a new upstream
Package: wnpp
Severity: wishlist
* Package name: Extinction
Version : 0.3.0
Upstream Author : Kyle Barbary
* URL : https://github.com/kbarbary/extinction
* License : MIT
Programming Lang: Python/Cython
Description : Fast interstellar dust extinction law
Simon McVittie writes:
> I think the bottom line here is that what you are doing *is* rebasing:
> you are treating the new upstream (or new security-patched downstream)
> as the new baseline for your local work, discarding any of your changes
> that are no longer necessary, and adjusting the rest
On Jan 04 2017, Vincent Bernat wrote:
> ❦ 4 janvier 2017 09:47 -0800, Nikolaus Rath :
>
>> It's surprisingly awkward, and, at least for me, it turns out that
>> externalizing my rebased branch as a patch series solves many of
>> problems surprisingly well. All the other solutions I
On 2017-01-03 16:58:21 [+], Ian Jackson wrote:
> Looked at another way, it is trying to be a version control system,
> layered on top of the Debian archive. But it is only about a quarter
> of a VCS. There are no formal interfaces to do proper VCS operations.
> If there is a formal interface,
On Wed, 2017-01-04 at 20:33 +0100, Michael Biebl wrote:
> Am 04.01.2017 um 19:53 schrieb Margarita Manterola:
>
> > Can we accelerate the removal of non key packages, please?
> >
> > One example: https://tracker.debian.org/pkg/libsigc++-1.2 migrated to
> > testing on Dec 29th even though it has a
Am 04.01.2017 um 19:53 schrieb Margarita Manterola:
> Can we accelerate the removal of non key packages, please?
>
> One example: https://tracker.debian.org/pkg/libsigc++-1.2 migrated to
> testing on Dec 29th even though it has an RC bug that was intended to
> keep it out of it.
>
> For whatever
Michael Biebl writes ("Re: "not authorised" doing various desktoppy things [and
1 more messages]"):
> Am 04.01.2017 um 12:07 schrieb Ian Jackson:
> > I think #844785 needs a fix though.
>
> Agreed. Does anyone who uses sysvinit want to look into this?
Um, me ? Well, I don't particularly want t
On 2017-01-04 19:51, Samuel Thibault wrote:
Hello,
Gilles Filippini, on Wed 04 Jan 2017 19:31:28 +0100, wrote:
On Wed, 28 Dec 2016 02:23:24 +0200 Adrian Bunk wrote:
> This looks like a threading bug in Scilab exposed by TSX.
I've just noticed this RC bug [1] against scilab.
FYI, glibc is ab
Control: severity 844134 normal
Samuel Thibault writes ("Re: Request for help - scilab segfaults with TSX"):
> Gilles Filippini, on Wed 04 Jan 2017 19:31:28 +0100, wrote:
> > On Wed, 28 Dec 2016 02:23:24 +0200 Adrian Bunk wrote:
> > > This looks like a threading bug in Scilab exposed by TSX.
> >
Package: eglibc
Gilles Filippini writes ("Request for help - scilab segfaults with TSX"):
> I've just noticed this RC bug [1] against scilab. [...]
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844134
> [2] https://lists.debian.org/debian-devel/2016/11/threads.html#00210
...
> I don't ha
❦ 4 janvier 2017 09:47 -0800, Nikolaus Rath :
> It's surprisingly awkward, and, at least for me, it turns out that
> externalizing my rebased branch as a patch series solves many of
> problems surprisingly well. All the other solutions I can think of
> require one or more thing
Hi,
On Fri, Dec 30, 2016 at 5:25 AM, Emilio Pozuelo Monfort
wrote:
> We thought about rolling back to the previous state, but that means testing
> users who have already upgraded would need to manually downgrade... which
> is not
> good.
>
> So we may just wait for the auto-removal hinter to do
Gilles Filippini writes ("Request for help - scilab segfaults with TSX"):
> Control: tag -1 + help
...
> I've just noticed this RC bug [1] against scilab. After reading through
> the recent thread on this subject [2] I must admit I have no clue what
> to do.
>
> [1] https://bugs.debian.org/cgi-bin
Hello,
Gilles Filippini, on Wed 04 Jan 2017 19:31:28 +0100, wrote:
> On Wed, 28 Dec 2016 02:23:24 +0200 Adrian Bunk wrote:
> > This looks like a threading bug in Scilab exposed by TSX.
>
> I've just noticed this RC bug [1] against scilab.
FYI, glibc is about to just disable TSX entirely in vers
Control: tag -1 + help
Hi,
On Wed, 28 Dec 2016 02:23:24 +0200 Adrian Bunk wrote:
> This looks like a threading bug in Scilab exposed by TSX.
I've just noticed this RC bug [1] against scilab. After reading through
the recent thread on this subject [2] I must admit I have no clue what
to do.
[1]
Am 04.01.2017 um 12:07 schrieb Ian Jackson:
> I think #844785 needs a fix though.
Agreed. Does anyone who uses sysvinit want to look into this?
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP d
On Tue, Jan 03, 2017 at 09:14:59PM -0500, Harlan Lieberman-Berg wrote:
> Toni Mueller writes:
> > I found them only on PyPI. Did you find them elsewhere?
>
> We get them from releases.ansible.com. Are the docs in the tarballs in
> PyPi?
Nope, there are only man pages.
Cheers,
--Toni++
On Jan 04 2017, Vincent Bernat wrote:
> ❦ 4 janvier 2017 04:52 GMT, Scott Kitterman :
>
It's surprisingly awkward, and, at least for me, it turns out that
externalizing my rebased branch as a patch series solves many of
problems surprisingly well. All the other solutions I can t
On Jan 04 2017, Sean Whitton wrote:
>> > I also read Russ's e-mail, but I'm not yet convinced that powerful tools
>> > like `git diff` and `git log` won't be able to give you the information
>> > you need pretty quickly.
>>
>> Can you give an example? Eg if I have to Debian patched that both
>> p
On Wed, Jan 04, 2017 at 12:53:12PM +, Simon McVittie wrote:
> Joking aside, the attempts I've seen at managing SRPMs in a version
> control system have either not tracked upstream source at all (Fedora), or
> invented a layout that is actually a lot like Debian's but with packaging/
> instead
On Wed, 04 Jan 2017 at 02:10:56 +, Ian Jackson wrote:
> Michael Biebl writes ("Re: "not authorised" doing various desktoppy things"):
> > Check if your session is marked as active and local
> > $ loginctl show-session $XDG_SESSION_ID
>
> I see (amongst other things):
>
> Remote=no
> Activ
On Wed, 04 Jan 2017 at 13:59:26 +0800, Paul Wise wrote:
> On Wed, Jan 4, 2017 at 1:30 PM, Nikolaus Rath wrote:
> > But I am not sure if a package structure like
> >
> > mypkg/upstream/*
> > mypkg/debian/*
> > mypkg/patches/* (?)
> >
> > would have any *practical* benefits over the current situation
Niels Thykier writes ("Re: Migration despite an RC bug?"):
> An exception in my experience: In process is cheaper when the
> (de)compressor is available in the PerlIO Layer as native C code.
> Notable example being libperlio-gzip-perl where you use "open(my $fd,
> '<:gzip', $file)".
> At least th
On Tue, 03 Jan 2017 at 22:17:33 -0800, Russ Allbery wrote:
> Usually what I have to do (and I think this is a pretty common use case
> for anyone who customizes Debian packages) is that I need to start from a
> package from unstable (or at least newer than stable, or oldstable, or
> ancient Ubuntu,
On January 4, 2017 6:23:23 AM EST, Jonas Smedegaard wrote:
>Quoting Vincent Bernat (2017-01-04 08:12:08)
>> ❦ 4 janvier 2017 04:52 GMT, Scott Kitterman
> :
>>
>> >>> It's surprisingly awkward, and, at least for me, it turns out
>that
>> >>> externalizing my rebased branch as a patch series so
Package: tweetnacl
Severity: wishlist
Owner: Yashashree Kolhe
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-tweetnacl
Version : 0.14.5
Upstream Author : TweetNaCl-js contributors
* URL : https://tweetnacl.js.org
* License : Unlicense
Progra
Nikolaus Rath writes ("Re: Converting to dgit"):
> I still haven't really made up my mind if I want to use git-maint-merge
> or git-dpm. Russ recently raised a valid point with the Debian
> modifications over-time becoming all tangled up and impossible to
> separate. I thought I could solve this wi
Russ Allbery writes ("Re: Feedback on 3.0 source format problems"):
> Even if we never used tarballs, and instead our unit of operation was the
> upstream Git repository plus Debian branches, I would maintain a rebased
> branch of Debian changes to upstream
I think this is definitely the right thi
Hello,
On Tue, Jan 03, 2017 at 04:33:39PM -0800, Russ Allbery wrote:
> Curating a patch series is only 5% slower than commiting directly to the
> Git repository to me. I just have to remember to gbp pq import before
> making new changes, gbp pq export when I'm done, and once in a great while
> I
Package: wnpp
Severity: wishlist
Owner: Nupur Malpani
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-delegates
Version : 1.0.0
Upstream Author : TJ Holowaychuk
* URL : https://github.com/visionmedia/node-delegates#readme
* License : Expat
P
Quoting Vincent Bernat (2017-01-04 08:12:08)
> ❦ 4 janvier 2017 04:52 GMT, Scott Kitterman :
>
> >>> It's surprisingly awkward, and, at least for me, it turns out that
> >>> externalizing my rebased branch as a patch series solves many of
> >>> problems surprisingly well. All the other solutio
Package: wnpp
Severity: wishlist
Owner: Saurabh Agrawal
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-assert-plus
Version : 1.0.0
Upstream Author : Mark Cavage
* URL : https://github.com/mcavage/node-assert-plus#readme
* License : Expat
Pr
Package: wnpp
Severity: wishlist
Owner: Rushikesh Bhadane
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-stringstream
Version : 0.0.5
Upstream Author : Michael Hart (
http://github.com/mhart)
* URL : https://github.com/mhart/StringStream#readme
* Lic
Package: wnpp
Severity: wishlist
Owner: akshay kemekar
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-asn1
Version : 0.2.3
Upstream Author : Mark Cavage
* URL : https://github.com/mcavage/node-asn1
* License : Expat
Programming Lang: JavaSc
Package: wnpp
Severity: wishlist
Owner: Aditya Neralkar
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-asynckit
Version : 0.4.0
Upstream Author : Alex Indigo
* URL : https://github.com/alexindigo/asynckit#readme
* License : Expat
Programmi
Package: wnpp
Severity: wishlist
Owner: Shirish Togarla
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-fn-name
Version : 2.0.1
Upstream Author : Sindre Sorhus (
http://sindresorhus.com)
* URL : https://github.com/sindresorhus/fn-name
* License
Package: wnpp
Severity: wishlist
Owner: Gaurav Juvekar
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-is-obj
Version : 1.0.1
Upstream Author : Sindre Sorhus
(sindresorhus.com)
* URL : https://github.com/sindresorhus/is-obj#readme
* License
Package: wnpp
Severity: wishlist
Owner: Srushti Chaudhari
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-aws-sign2
Version: 0.6.0
Upstream Author: Mikeal Rogers (
http://www.futurealoof.com)
* URL: http://github.com/mikeal/aws-sign#readme
* L
Ansgar Burchardt writes ("Re: "not authorised" doing various desktoppy things
[and 1 more messages]"):
> Ian Jackson writes:
> > In fact I didn't have libpam-systemd installed for some strange
> > reason, but installing it hasn't helped. (All the symptoms I report
> > above are with it installed.
Hey,
On Wed, Jan 04, 2017 at 01:04:12AM +0100, Toni Mueller wrote:
> On Sat, Dec 31, 2016 at 01:07:44PM -0500, Harlan Lieberman-Berg wrote:
> > Unfortunately, we don't build ansible off of the git repository, but
> > rather from the released tarballs.
>
> I found them only on PyPI. Did you find t
Package: wnpp
Severity: wishlist
Owner: Tejas Nayak
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-onetime
Version : 2.0.0
Upstream Author : Sindre Sorhus (sindresorhus.com
)
* URL : https://github.com/sindresorhus/onetime#readme
* License :
Package: wnpp
Severity: wishlist
Owner: Aarti Kashyap
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-is-generator-fn
Version : 1.0.0
Upstream Author : Sindre Sorhus (sindresorhus.com
)
* URL : https://github.com/sindresorhus/is-generator-fn
* License
Package: wnpp
Severity: wishlist
Owner: Tushar Agey
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-aproba
Version : 1.0.4
Upstream Author : Rebecca Turner
* URL : https://github.com/iarna/aproba
* License : ISC
Programming Lang: JavaScript
Package: wnpp
Severity: wishlist
Owner: Siddhesh Rane
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-ci-info
Version : 1.0.0
Upstream Author : Thomas Watson Steen (
https://twitter.com/wa7son)
* URL : https://github.com/watson/ci-info
* License
Package: node-buf-compare
Severity: wishlist
Owner: Nikhil Gawande
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-buf-compare
Version : 1.0.1
Upstream Author : Sindre Sorhus (sindresorhus.com
)
* URL : https://github.com/sindresorhus/buf-compare#read
Package: wnpp
Severity: wishlist
Owner: Vinay Desai
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-aws4
Version : 1.5.0
Upstream Author : Michael Hart (
http://github.com/mhart)
* URL : https://github.com/mhart/aws4#readme
* License : Expat
Package: wnpp
Severity: wishlist
Owner: Yogiraj Kulkarni
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-has-unicode
Version : 2.0.1
Upstream Author : Rebecca Turner
* URL : https://github.com/iarna/has-unicode
* License : ISC
Programming La
Package: wnpp
Severity: wishlist
Owner: Pratham
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-clean-yaml-object
Version : 0.1.0
Upstream Author : James Talmage (
github.com/jamestalmage)
* URL : https://github.com/tapjs/clean-yaml-object#readme
* Li
Package: wnpp
Severity: wishlist
Owner: Vivek
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-binary-extensions
Version : 1.8.0
Upstream Author : Sindre Sorhus (sindresorhus.com)
* URL : https://github.com/sindresorhus/binary-extensions#readme
* Licen
Package: wnpp
Severity: wishlist
Owner: Sumedh Pendurkar
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-slice-ansi
Version : 0.0.4
Upstream Author : David Caccavella
* URL : https://github.com/chalk/slice-ansi#readme
* License : Expat
Prog
Package: wnpp
Severity: wishlist
Owner: Roshan Nalawade
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-tough-cookie
Version : 2.3.2
Upstream Author : Jeremy Stashewsky
* URL : https://github.com/salesforce/tough-cookie
* License : BSD-3-Claus
Package: wnpp
Severity: wishlist
Owner: Ameya Apte
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-common-path-prefix
Version : 1.0.0
Upstream Author : Mark Wubben (https://novemberborn.net/)
* URL :
https://github.com/novemberborn/common-path-prefix#r
Quoting Jérémy Lal (2017-01-04 10:12:44)
> 2017-01-04 10:04 GMT+01:00 Andrey Rahmatullin :
>> On Wed, Jan 04, 2017 at 09:54:34AM +0100, Jérémy Lal wrote:
>>> i really think it would be best to have nodejs 6.9 in next debian release.
>>> That version is currently in experimental and i was about to u
On Tue, Jan 03, 2017 at 07:01:22PM -0800, Nikolaus Rath wrote:
> When talking about percentages, I think it's worth keeping in mind the
> 1000% longer that it takes to comprehend a diff of two patches-unapplied
> trees (as gbp produces them) over a diff of two patches-applied trees
> (as git-dpm a
On 04.01.2017 00:23, Christoph Biedl wrote:
> Hi there,
>
> as the stretch freeze approaches, I'm getting concerned about the
> status of logrotate, most notably #734688. The maintainer (CC'ed)
> hasn't shown any sign of activity for a while, also no response to a
> private message (I admit, it's
2017-01-04 10:04 GMT+01:00 Andrey Rahmatullin :
> On Wed, Jan 04, 2017 at 09:54:34AM +0100, Jérémy Lal wrote:
>> i really think it would be best to have nodejs 6.9 in next debian release.
>> That version is currently in experimental and i was about to upload it
>> to unstable, but i tried to do thi
On Wed, Jan 04, 2017 at 09:54:34AM +0100, Jérémy Lal wrote:
> i really think it would be best to have nodejs 6.9 in next debian release.
> That version is currently in experimental and i was about to upload it
> to unstable, but i tried to do things right and prepared the addons
> that need to be r
Hi,
i really think it would be best to have nodejs 6.9 in next debian release.
That version is currently in experimental and i was about to upload it
to unstable, but i tried to do things right and prepared the addons
that need to be rebuilt and binNMUed, then opened a transition bug
#849505.
No a
Ian Jackson writes:
> Michael Biebl writes ("Re: "not authorised" doing various desktoppy things"):
> I'm not sure I need "logind integration" in my X server but perhaps I
> do ?
Only if you want to start X as non-root.
> Simon McVittie writes ("Re: "not authorised" doing various desktoppy things
69 matches
Mail list logo
