from:"shirish"

at bottom :-

On 28/08/2017, Guillem Jover <guil...@debian.org> wrote:
> Hi!
>
> On Mon, 2017-08-28 at 12:50:48 +0100, Colin Watson wrote:
>> It did take a little while for the current format to evolve.  For
>> example, very early source packages had changes recorded in a
>> "debian.README" file in somewhat ad-hoc formats.
>>
>> I think the current changelog format arrived with dpkg 1.3.x in August
>> 1996 (https://lists.debian.org/debian-devel/1996/08/msg00369.html etc.),
>> but true old-timers might remember more.
>
> I think it's older than that. But it might not have been "formalized"
> until that point because there was no tool to parse it automatically
> before then.
>
> Check the tail of the dpkg changelog, which is one of the oldest ones
> I know is still currently present in unstable, and you'll see that
> evolution taking place:
>
>
> <http://metadata.ftp-master.debian.org/changelogs/main/d/dpkg/unstable_changelog>
>
> Thanks,
> Guillem
>


Dear Guillem,

Thank you for pointing in the right direction.

The first thing I wanted to find out, the separation of changelogs
happened in 1998 according to dpkg changelogs.

dpkg (1.4.0.22) frozen unstable; urgency=medium

  * Non-maintainer bug-fix release
  * Install main changelog file as `changelog.gz' instead of
`changelog.dpkg.gz' (Debian Policy, section 5.8) (Bug#6052,15157)
...

...

 Juan Cespedes <cespe...@debian.org>  Sun,  5 Apr 1998 17:37:01 +0200


And the earliest mention as correctly pointed out by you started In
August 1994 itself.


Thu Aug 25 11:46:27 1994  Ian Murdock  (imurd...@debra.debian.org)

..

..

ChangeLog begins Thu Aug 25 11:46:27 1994 for dpkg 0.93.5.

which means it was there from starting itself.

Thank you again for sharing that.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

PackageConfigUpgrade: Was X facts about Debian - some fact checking and looking for ideas.

Dear Audrey,

Please CC me. I read
https://lists.debian.org/debian-devel/2017/08/msg00600.html

My mistake, I assumed the package was named lcdproc and not
pkg-config-model which the package is all about. Sorry for being a bit
incoherent, just not in the best of the health.

I had seen the page https://wiki.debian.org/PackageConfigUpgrade and
had to read it twice before understanding that the package it talks
about is pkg-config.model.

I do agree with your assessment and I imagine it might take quite a
bit of work. That is why I am against blindly taking maintainer
changes and usually cancel updates which have a diff. or need me to
take a decision on a later/next day morning where I'll be more fresh
and have time to see what is best for my setup.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Re: X facts about Debian - some fact checking and looking for ideas.

at bottom :-

On 27/08/2017, Dominique Dumont <d...@debian.org> wrote:
> On Thursday, 24 August 2017 08:01:54 CEST shirish शिरीष wrote:
>> Are there any such unsung technical/non-technical or social
>> innovations that Debian has done that is now known/or lesser known
>> which Debianities should know about and be proud about. Having more
>> Debian fanboys should also increase both participation and
>> contribution to Debian.
>
> lcdproc package now feature automatic configuration merge when upgrading a
> package: system admin modifications and package manager modifications are
> merged
> automatically in a way that preserve both changes.
>
> See [1] for more details.
>
> All the best.
>
> [1] https://wiki.debian.org/PackageConfigUpgrade
>

Dominique, thank you, that was a nice find. I'm looking both new and
old innovations which might be credited to Debian, both in technical
terms or in social terms. I would discuss about lcdproc in another
e-mail altogether which I just did. I do have loads of questions about
Debian history which perhaps might or might not be interesting to
people, I just fired the first one just a short while ago -

https://lists.debian.org/debian-devel/2017/08/msg00597.html

While some of the queries might seem to be trivial there is lack of
authoritative answers to them.

@Andrey Rahmatullin  I read your answer at
https://lists.debian.org/debian-devel/2017/08/msg00598.html but it
doesn't tell me whether this obvious idea was born in Debian or some
other GNU/Linux distribution. I do not the early history of Debian so
it is possible that at one point it was a single changelog.gz file and
then separation of the two changelogs happened along the road or
something like that.

If somebody knows something it would be nice to know. I had tried to
look if early packages could be found but sadly snapshot.debian.org
has records from 2k5 only, a simple
http://snapshot.debian.org/archive/debian/?year=2000 reveals from when
the packages are available. The first Debian stable release was in
1996. https://www.debian.org/doc/manuals/project-history/ch-releases.en.html

It would be helpful if somebody has one of the 1996 packages snapshots
and can share how the changelogs were at that point of time. That
might give a bit of reference as to how things were and if there were
any changes between them and now.

Also the crucial question if whether this idea came in Debian first
and then flowed to other distributions or was it was first used in
Redhat and then came to Debian would be interesting in itself.

Hope I gave a bit more context from where I'm coming from.

> --
>  https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
> http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org
>

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

lcdproc was Re: X facts about Debian - some fact checking and looking for ideas.

Dear Dominique,

Thank you for sharing about lcdproc as response to my mail. For my 2
cents, I disliked the idea (of lcdproc) immediately as simply applying
maintainer changes defeats the very purpose the tool declares or
claims to help. For e.g. I know of quite a few people where the modem
login page is at a different rather than the universal 192.168.0.1
address.https://en.wikipedia.org/wiki/Private_network and at times
have to write manual /etc/network/interfaces rules in order for
internet to work. In India, in practise this happens quite a bit
within ethernet based modem/routers, leave alone cable modems.

Couple of URL's to tell what I mean (only for the modem router page mind you) .

http://www.in.techspot.com/features/tips-tricks/a-list-of-common-default-router-ip-addresses/articleshow/47795297.cms

https://www.digitaltrends.com/computing/how-to-find-your-routers-ip-and-admin/

Add to that an ISP's settings that an elderly person might have to set up.

https://bpedia.co.in/bsnl-modem-configuration/ - just one ISP's settings.

And there are 244 ISP's in India alone according to December 2016 latest list

http://www.dot.gov.in/sites/default/files/2016_08_24%20ISP-DS_0.pdf?download=1

In such a scenario a grandma's internet may simply stop working after
an upgrade if she blindly accepts a maintainer's changes. It has
happened with me in the past even though I know a bit about how things
work, let alone a non-technical grandma.

What is actually required is a tool which asks questions in a manner
in which the grandma or anybody not knowing technology can answer.
This I accept is really hard to fix :(

Apart from cryptic info. what is also needed to fix is also cryptic
errors which is not easy for non-technical people to diagnose what is
wrong but that's a different question altogether.

history questions about how changelog.gz and changelog.Debian.gz came about.

Dear all,   

Please CC me if anybody has an answer to below as I'm not subscribed
to either of the mailing lists due to the volume both ML generate.

I like the way Debian gives various changelogs . For instance for most
packages it has -

changelog.gz - This is the upstream changelog giving details of the
differences between any two versions or at times even point versions.
Nowadays usually distilled from $ git shortlog or whatever equivalent
command in whatever vcs is being used.

changelog.Debian.gz - This talks about changes/improvements done to
the packaging.  Some of the common changes include changes in the
packaging team/uploader, changes to the standards versions, Updating
build-depends, any patches which fixes some issue in Debian which has
not been accepted by upstream, any changes to either debian/rules or
debian/control which might be notable and the uploader feels that they
need to be mentioned in the changelog (notable).

While I'm pretty happy with the way Debian organizes this thing, was
this idea of having separate changelogs to lessen confusion born at
Debian or some other GNU/Linux distribution. If so, where and when
this idea was born, implemented before Debian ?

In short, was Debian the first distribution to use the concept to
apply for third-party software.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

X facts about Debian - some fact checking and looking for ideas.

2017-08-23 Thread shirish शिरीष

Dear all,

I have been writing some beginner articles in my spare-time to
talk/share about Debian and make it more popular.

In that direction I have and had been penning few articles at
https://itsfoss.com/author/shirish/

As shared before, these are beginner articles and are meant only to
bring awareness about Debian to the masses.

Just a few days back, Debian turned 24
https://bits.debian.org/2017/08/debian-turns-24.html

While I have been thinking about sharing the number of packages, the
number of developers, the diversity, the debconf's and where debconfs
have been held over the years for starters but all of these I have
already shared before.

I saw hartmann's article on p.d.o. the other day
http://hartmans.livejournal.com/96841.html and I started pondering
about some of the lesser unknown innovative ideas of debian which
people don't know about.

For e.g. the reproducible builds project
https://reproducible-builds.org/ seems to have a lot of weight and
faith of DD's but is not known at all (or maybe some slightly bit)
outside the technical circles.

Are there any such unsung technical/non-technical or social
innovations that Debian has done that is now known/or lesser known
which Debianities should know about and be proud about. Having more
Debian fanboys should also increase both participation and
contribution to Debian.

As far as fact-checking goes, can anybody share about Debian and Kali
Linux relationship in bit more detail. AFAIK Raphaël Hertzog is one of
the main developers and there has been lot of symbiotic relationship
between the two projects but how much both projects have benefited
from this partnership has not been codified or told/shared anywhere
AFAIK.

The only thing I could get is
https://docs.kali.org/policy/kali-linux-relationship-with-debian which
seems to be pretty dry and short as far as documentation goes.

Looking forward to knowing more.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

what's the latest on the update of moving from alioth to pagure.

2017-07-16 Thread shirish शिरीष

Dear all,

While I love and loved alioth, I know for probably newish people the
interface is somewhat ugly.

>From what I did see in https://lwn.net/Articles/724986/ it seems there
were lots of pros and cons which were discussed. I was also able to
converse with Alexander Wirt and download the survey which wasn't
available anymore for public consumption.

Can somebody tell/share which forge are the developers looking forward
to replace alioth with, pagure or something else .

The choices seem to be to do lot of coding if some project/product is
taken which is not mature enough or has features that we want and in
some cases there is restrictive licensing or/and have two products,
one which has foss licensing and the other which has commercial
aspects but more features.

While there doesn't seem to be any hurry to replace alioth today, the
clock is ticking.

There is/was some discussion about it in May 2017
https://lists.debian.org/debian-devel/2017/05/msg00095.html, the
thread I'm reading right now. Would be nice though if somebody can
share what is/are the possible scenarios.

-- 
  Regards,
      Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Re: IMPORTANT: Do live Debian images have a future?

2017-07-12 Thread shirish शिरीष

at bottom :-

On 12/07/2017, Fernando Toledo <ftol...@docksud.com.ar> wrote:
> El 26/06/17 a las 11:08, Steve McIntyre escribió:
>> [ Note the cross-posting... ]
>>
>> Hey folks,
>>
>
> Our Use-case:
>
> We develop a derivated distro from Debian called Huayra GNU/Linux, this
> is for educational program of government in Argentina. This big program
> ship around 5 millons of netbooks to highschool students.

>
> --
> Fernando Toledo
> Dock Sud BBS
> http://bbs.docksud.com.ar
> telnet://bbs.docksud.com.ar
>

In short, this alone use-case answers Steve's original question which
was primarily are there any users who use or would use this tool or
his time would be better spent somewhere else. I think just the above
use-case and number of users answers the need for a tool like
live-wrapper. As has been pointed out by me and others, it just needs
more testing (documentation and love by devs.) to drive more usage
forwards.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Re: IMPORTANT: Do live Debian images have a future?

2017-06-27 Thread shirish शिरीष

at bottom :-

On 26/06/2017, Steve McIntyre <st...@einval.com> wrote:
> [ Note the cross-posting... ]
>
> Hey folks,
>
> Background: we released live images for Stretch using new tooling,
> namely live-wrapper. It is better than what we had before (live-build)
> in a number of ways, particularly in terms of build reliability and
> some important new features (e.g. UEFI support). But it's also less
> mature and has seen less testing. There have been bugs because of
> that. I have fixes for most of the ones I know about [1], and I'm
> still working on more bugfixes yet.
>
> While the bugs are annoying, what worries me more is that they were
> only spotted in release builds. There had been testing versions of
> live images available for multiple weeks beforehand, presumably with
> the same bugs included. (Almost) none of them reported. This shows
> that we don't have enough people using these live images and/or caring
> about filing bugs.
>
> We have a similar lack of involvement in terms of the content of the
> live images. As I said above, I'm happy that we now have a reliable
> tool for building our live images - that makes my life much
> easier. But I honestly have no idea if the multiple desktop-specific
> live images are actually reasonable representations of each of the
> desktops. For example, I *seriously* hope that normal KDE
> installations are not effected by #865382 like our live KDE
> images. Validation by the various desktop teams would be useful here.
>
> The current situation is *not* good enough. I ended up getting
> involved in live image production because the images needed making,
> and I was already the main person organising production of Debian's
> official images. To be frank, I had (and still have) no direct use for
> the live images myself and I don't *particularly* care about them all
> that much. Despite that, I've ended up spending a lot of time working
> on them. A few other people have also spent a lot of time working in
> this area - thanks are due to those people too. But it's still not
> enough.
>
> If our live images are going to be good enough to meet the standards
> that Debian users deserve and expect, we need *consistent*,
> *sustained* involvement from a lot more people. Please tell me if
> you're going to help. If we don't see a radical improvement soon, I'll
> simply disable building live images altogether to remove the false
> promises they're making.
>
> [1]
> https://get.debian.org/images/release/current-live/amd64/iso-hybrid/#issues
>
> --
> Steve McIntyre, Cambridge, UK.
> st...@einval.com
> "...In the UNIX world, people tend to interpret `non-technical user'
>  as meaning someone who's only ever written one device driver." -- Daniel
> Pead
>

One of the things at least to my mind is we (the users) do not know
which is most closest testing release  near to the final release. For
e.g.  take the last/latest announcement done by Cyril Brulebois on
13th June talking about the Stretch RC5 release. In the whole
announcement, there is not even a hint to potential testers that this
might be the closest to the final released (gold) image. I am
presuming/assuming that Cyril was also talking about the live image
and not the just the installer improvements.

What would be nicer/better perhaps if debian-live does announcements
on d-d-a  and more importantly hint as when it's going to be nearer to
release (final image).

We are going to have a release party this week-end in Pune (haven't
posted the details yet at https://wiki.debian.org/ReleasePartyStretch
, hoping the organizers will do the needful otherwise will do it in a
day or two.

I/we could also have testing parties before the release as well with a
two-week window to the final image . This also gives times to students
to see how things work in the real world as well.

I can't volunteer for any activities atm (due to health issues) except
for taking part in organising testing party in Pune before release and
getting more people to file bugs in case they hit problems.

I am hopeful we can find a better way/solution to the above.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Re: Fwd: debian stretch being released without fixing wpagui and wpasupplicant ?

2017-06-18 Thread shirish शिरीष

at bottom :-

On 17/06/2017, gregor herrmann <gre...@debian.org> wrote:

>
> Yeah, maybe apt-listbugs is a bit confused here:
>
> # apt-listbugs list wpasupplicant
> Retrieving bug reports... Done
> Parsing Found/Fixed information... Done
> grave bugs of wpasupplicant (-> ) 
>  b1 - #849122 - With 2.6-2 i dont have the wifi adapter in the
> (network-manager) list available.
> serious bugs of wpasupplicant (-> ) 
>  b2 - #849077 - wpasupplicant: [Regression] Updating wpasupplicant makes not
> possible to connect to encrypted WiFi
>  b3 - #849875 - broadcom-sta-dkms: Wifi association took too long, failing
> activation
> Summary:
>  wpasupplicant(3 bugs)
>

Gregor,

Sorry for the late reply. Were you able to file a bug in apt-listbugs
or should I ? I'm still seeing the same  issue/bug still.

[$]  apt-listbugs list wpasupplicant
 [5:32:13]
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
grave bugs of wpasupplicant (→ ) 
 b1 - #849122 - With 2.6-2 i dont have the wifi adapter in the
(network-manager) list available.
serious bugs of wpasupplicant (→ ) 
 b2 - #849077 - wpasupplicant: [Regression] Updating wpasupplicant
makes not possible to connect to encrypted WiFi
 b3 - #849875 - broadcom-sta-dkms: Wifi association took too long,
failing activation
Summary:
 wpasupplicant(3 bugs)

I don't know much about 'epoch' but I could make reference to the
discussion on debian-devel. That might be enough for the apt-listbugs
maintainers to take some call.

Btw pkg-wpa-de...@lists.alioth.debian.org seems to be a moderated list
and haven't heard anything from them till yet as well.

Looking forward to your advice/answer.

Till later.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Re: Fwd: debian stretch being released without fixing wpagui and wpasupplicant ?

2017-06-17 Thread shirish शिरीष

at bottom :-

On 17/06/2017, gregor herrmann <gre...@debian.org> wrote:
> On Sat, 17 Jun 2017 07:44:17 +0530, shirish शिरीष wrote:
>
>> On 17/06/2017, gregor herrmann <gre...@debian.org> wrote:
>> > On Sat, 17 Jun 2017 02:48:25 +0530, shirish शिरीष wrote:
>> >> b1 - #849122 - With 2.6-2 i dont have the wifi adapter in the
>> >> (network-manager) list available
>> >> b2 - #849077 - wpasupplicant: [Regression] Updating wpasupplicant
>> >> makes not possible to connect to encrypted WiFi
>> >>  b3 - #849875 - broadcom-sta-dkms: Wifi association took too long,
>> >> failing activation
>> > All these bugs only affect versions in experimental, if the
>> > information in the BTS is correct.
>>
>> If you what you say is true then I shouldn't have got notices while I
>> was upgrading wpagui and wpasupplicant. I have apt-listbugs installed
>> and as can be seen the ones which are installed on my system are
>> stretch ones only .
>
> Yeah, maybe apt-listbugs is a bit confused here:
>
> # apt-listbugs list wpasupplicant
> Retrieving bug reports... Done
> Parsing Found/Fixed information... Done
> grave bugs of wpasupplicant (-> ) 
>  b1 - #849122 - With 2.6-2 i dont have the wifi adapter in the
> (network-manager) list available.
> serious bugs of wpasupplicant (-> ) 
>  b2 - #849077 - wpasupplicant: [Regression] Updating wpasupplicant makes not
> possible to connect to encrypted WiFi
>  b3 - #849875 - broadcom-sta-dkms: Wifi association took too long, failing
> activation
> Summary:
>  wpasupplicant(3 bugs)
>
>
> And with versions:
>
> # apt-listbugs list wpasupplicant/2.4-1
> Retrieving bug reports... Done
> Parsing Found/Fixed information... Done
>
> # apt-listbugs list wpasupplicant/2.6-4
> Retrieving bug reports... Done
> Parsing Found/Fixed information... Done
> grave bugs of wpasupplicant (-> 2.6-4) 
>  b1 - #849122 - With 2.6-2 i dont have the wifi adapter in the
> (network-manager) list available.
> serious bugs of wpasupplicant (-> 2.6-4) 
>  b2 - #849077 - wpasupplicant: [Regression] Updating wpasupplicant makes not
> possible to connect to encrypted WiFi
>  b3 - #849875 - broadcom-sta-dkms: Wifi association took too long, failing
> activation
> Summary:
>  wpasupplicant(3 bugs)
>
> Vs.:
>
> # apt-listbugs list wpasupplicant/2:2.4-1
> Retrieving bug reports... Done
> Parsing Found/Fixed information... Done
> grave bugs of wpasupplicant (-> 2:2.4-1) 
>  b1 - #849122 - With 2.6-2 i dont have the wifi adapter in the
> (network-manager) list available.
> serious bugs of wpasupplicant (-> 2:2.4-1) 
>  b2 - #849077 - wpasupplicant: [Regression] Updating wpasupplicant makes not
> possible to connect to encrypted WiFi
>  b3 - #849875 - broadcom-sta-dkms: Wifi association took too long, failing
> activation
> Summary:
>  wpasupplicant(3 bugs)
>
> # apt-listbugs list wpasupplicant/2:2.6-4
> Retrieving bug reports... Done
> Parsing Found/Fixed information... Done
> grave bugs of wpasupplicant (-> 2:2.6-4) 
>  b1 - #849122 - With 2.6-2 i dont have the wifi adapter in the
> (network-manager) list available.
> serious bugs of wpasupplicant (-> 2:2.6-4) 
>  b2 - #849077 - wpasupplicant: [Regression] Updating wpasupplicant makes not
> possible to connect to encrypted WiFi
>  b3 - #849875 - broadcom-sta-dkms: Wifi association took too long, failing
> activation
> Summary:
>  wpasupplicant(3 bugs)
>
>
> Looks like the epoch ("2:") is causing confusion here. Not sure if
> apt-listbugs should strip it, or if the version information for the
> bugs in the BTS should add it. -- Or not, after looking at [0], this
> looks all correct anyway ... Maybe it's that found:2.6-2 is lower
> than 2:2.4-1 but in a different branch (would a "notfound 
> 2:2.4-1" help here?)
> Cc'ingg the wpa maintainers.
>
> But anyway, the bugs affect version (2:)2.6-* in experimental only.
>
>
> Cheers,
> gregor
>
> [0]
> https://bugs.debian.org/cgi-bin/version.cgi?absolute=0;collapse=0;format=png;found=wpa%2F2.6-2;height=;info=1;package=wpasupplicant;width=;ignore_boring=0
> https://bugs.debian.org/cgi-bin/version.cgi?absolute=0;collapse=0;format=png;found=wpa%2F2.6-2;height=;info=1;package=wpasupplicant;width=;ignore_boring=0
> https://bugs.debian.org/cgi-bin/version.cgi?absolute=0;collapse=0;format=png;found=wpa%2F2.6-2;height=;info=1;package=wpasupplicant;width=;ignore_boring=0
>
>
> --
>  .''`.  https://info.comodo.priv.at/ - Debian Developer
> https://www.debian.org
>  : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649
> AA06
>  `. `'  Member of VIBE!AT

Re: Fwd: debian stretch being released without fixing wpagui and wpasupplicant ?

2017-06-16 Thread shirish शिरीष

at bottom :-

On 17/06/2017, gregor herrmann <gre...@debian.org> wrote:
> On Sat, 17 Jun 2017 02:48:25 +0530, shirish शिरीष wrote:
>
>> b1 - #849122 - With 2.6-2 i dont have the wifi adapter in the
>> (network-manager) list available
>> b2 - #849077 - wpasupplicant: [Regression] Updating wpasupplicant
>> makes not possible to connect to encrypted WiFi
>>  b3 - #849875 - broadcom-sta-dkms: Wifi association took too long,
>> failing activation
>
> All these bugs only affect versions in experimental, if the
> information in the BTS is correct.
>
>
> Cheers,
> gregor
>
> --
>  .''`.  https://info.comodo.priv.at/ - Debian Developer
> https://www.debian.org
>  : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649
> AA06
>  `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation
> Europe
>`-   NP: Dawn Landes: Picture Show
>

Dear Gregor,

If you what you say is true then I shouldn't have got notices while I
was upgrading wpagui and wpasupplicant. I have apt-listbugs installed
and as can be seen the ones which are installed on my system are
stretch ones only .

─[$] apt-cache policy wpagui wpasupplicant

[7:36:37]
wpagui:
  Installed: 2:2.4-1
  Candidate: 2:2.4-1
  Version table:
 2:2.6-4 1
  1 http://httpredir.debian.org/debian experimental/main amd64 Packages
 *** 2:2.4-1 600
600 http://httpredir.debian.org/debian stretch/main amd64 Packages
  1 http://httpredir.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
wpasupplicant:
  Installed: 2:2.4-1
  Candidate: 2:2.4-1
  Version table:
 2:2.6-4 1
  1 http://httpredir.debian.org/debian experimental/main amd64 Packages
 *** 2:2.4-1 600
600 http://httpredir.debian.org/debian stretch/main amd64 Packages
  1 http://httpredir.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status

If what you are saying is correct, then either the BTS has tagged them
incorrectly affecting stretch versions as well Or a bug in
apt-listbugs. I am not in a position to experiment and find out more
as I'm ill. Please see if you can find out more if possible.

Till later.
-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Fwd: debian stretch being released without fixing wpagui and wpasupplicant ?

2017-06-16 Thread shirish शिरीष

Please excuse for the delay as I'm not well.

incidentally Paul Wise shared on debian-release that anyone can post
on debian-devel hence posting so it falls on relevant people to fix or
at least warn users of situation with broadcom chips along other bugs
in wpagui & wpasupplicant. Details below :-

-- Forwarded message --
From: shirish शिरीष <shirisha...@gmail.com>
Date: Thu, 15 Jun 2017 22:23:50 +0530
Subject: debian stretch being released without fixing wpagui and wpasupplicant ?
To: debian-release <debian-rele...@lists.debian.org>

Dear all,

I had shared the below at debian-publicity in response to the stretch
announcement in which I was given this answer -

https://lists.debian.org/debian-publicity/2017/06/msg00012.html

Now as I'm not a DD (nor hopeful of becoming a non-uploading DD at
least for sometime) hence debian-devel list is closed to me and the
only way to get my plea heard is the debian-release team. So without
further ado, here it is -

I have a query, how is stretch being released without multiple bugs
fixed for wpagui and wpasupplicant, I had a look at the stretch
announcement notes as well as the serious and grave bugs filed against
wpagui and wpasupplicant i.e.

b1 - #849122 - With 2.6-2 i dont have the wifi adapter in the
(network-manager) list available
b2 - #849077 - wpasupplicant: [Regression] Updating wpasupplicant
makes not possible to connect to encrypted WiFi
 b3 - #849875 - broadcom-sta-dkms: Wifi association took too long,
failing activation

While some of the bugs is related to broadcom only chipsets, other bug
could be hit by anyone. So unless there are packages which can take
place of wpagui and wpasupplicant and these packages can be removed
then please inform users.

Or at the very least warn them through stretch announcement as to what
they should do otherwise users having broadcom chips would be in for a
very nasty surprise when upgrading.

Maybe some of the experts could weigh in and make a proper message
about the above bugs situation.

Till later.
-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Accepted node-date-now 1.0.1-1 (source all) into unstable, unstable

2017-04-12 Thread Shirish Togarla

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 07 Feb 2017 19:49:26 +
Source: node-date-now
Binary: node-date-now
Architecture: source all
Version: 1.0.1-1
Distribution: unstable
Urgency: low
Maintainer: Debian Javascript Maintainers 
<pkg-javascript-de...@lists.alioth.debian.org>
Changed-By: Shirish Togarla <shirishtogarla...@gmail.com>
Description:
 node-date-now - requirable version of Date.now()
Closes: 854509
Changes:
 node-date-now (1.0.1-1) unstable; urgency=low
 .
   * Initial release (Closes: #854509)
Checksums-Sha1:
 28c11cc136d0de2107280c6e413d53023127277c 2049 node-date-now_1.0.1-1.dsc
 d3c204b8e035031b17f3ec9542868a0469a7b1af 2820 node-date-now_1.0.1.orig.tar.gz
 e057daad9676fd0e30b7907ecdaa97f9ce5068e7 2184 
node-date-now_1.0.1-1.debian.tar.xz
 6cc46bfdd0d73cac2a8968c6302c19449d9d0861 3282 node-date-now_1.0.1-1_all.deb
 f07a5fa5cf7022e490984704c7fb2d7fc7ee7ebb 5262 
node-date-now_1.0.1-1_amd64.buildinfo
Checksums-Sha256:
 02ba5b937f35c47af70f89e0e4872c86e3a01250021b42cc82a2cb7d4eead7d0 2049 
node-date-now_1.0.1-1.dsc
 d07fcd816bb6237d8a8693f599e3d827f2693d998b2405beaf80f076018268f0 2820 
node-date-now_1.0.1.orig.tar.gz
 dde35e10003ba7b1f7d6eec97a3b8fb25a01062944eaf6b58ba453d986ced819 2184 
node-date-now_1.0.1-1.debian.tar.xz
 d3aa0ecd6a3f48d3b1b42e24b6bc9a6147dfd5613f46f9052a4995fb21baff08 3282 
node-date-now_1.0.1-1_all.deb
 a7263abf62ce0ec1dccfb7a67add97c89551536ad408605bfc7b244ef3189b8f 5262 
node-date-now_1.0.1-1_amd64.buildinfo
Files:
 9371f78e7d1b5a614055c2541b16f2bb 2049 web optional node-date-now_1.0.1-1.dsc
 b24fd133e5b3bf6845bdd4406b9b1e9a 2820 web optional 
node-date-now_1.0.1.orig.tar.gz
 8b9a599aa6807150fdf31fdb976c6aa4 2184 web optional 
node-date-now_1.0.1-1.debian.tar.xz
 6a5fc8c7b0a7e462a52146285c918039 3282 web optional 
node-date-now_1.0.1-1_all.deb
 1c168d07502610d3c4cf43966c94b808 5262 web optional 
node-date-now_1.0.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJY7hAnAAoJEM4fnGdFEsIqsmwP/3NwHStRAdtS50bt5L7wvRVf
p5so//zkHSnTwtUhQcFk7/lkyZtHcwiG5/LdP/yBEj3H47Vf3N7HejKxOmAhLccD
EoMBWmKhPMdvcQdoPaiLMGAOVlc7j8+vSWmsWgrDaeX2QzNwTd1QE4qt2PjmfJFm
VojXUKMPswNwS0CC8gAA8ofE5485c7yiscCBipZkeWE2IKnlsTxbsFxBeYnE2HSm
AmrCqr5Sy3WkzHYnAbiKhlrpb6eYCdEFBIoVuHdE5Umw6YaHVxL3GdndEh+BqP9X
+YnVMge6676+Ndr+8+6nNzv1J2zwGy2rZ8pI6qArO1VXtyBNSM3ZaaDmpMxk4fU+
9Of3z8xTXl05lCV8XRfGpmVJ9hoNsWCTCfeWs5mmhNchcFdItbFqsqdjx8KN4dGL
WkeZPz+ZKhj7Ojppkv5hNfD3H2hUyHbur0SjMIIzOLKxGAI/y7dv1aD3wt+h5KDJ
+R1f9kb+47SFNOV1ForZJkdMijwL/YkbJdHq55Gfo31oZHSRx2QBLU2L2QOlGpMW
UPO9f7NiQZUQ0qE98Kucdo822vdxoRXhWcN6ADAJBJ7Q7Pf1d5s/fMI2cHwYDy9x
iFUi45mdyD2SrAV85vDb2aD28tD+Sl32s7DkzMcYPnjV4PUODkshT/nfENkW9CIA
a+8fH/GQy/BsGGVHSvqX
=+7Yj
-END PGP SIGNATURE-

Accepted node-is-redirect 1.0.0-1 (source all) into experimental, experimental

2017-02-15 Thread Shirish Togarla

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 07 Jan 2017 08:36:44 +
Source: node-is-redirect
Binary: node-is-redirect
Architecture: source all
Version: 1.0.0-1
Distribution: experimental
Urgency: low
Maintainer: Debian Javascript Maintainers 
<pkg-javascript-de...@lists.alioth.debian.org>
Changed-By: Shirish Togarla <shirishtogarla...@gmail.com>
Description:
 node-is-redirect - Check if a number is a redirect HTTP status code
Closes: 850498
Changes:
 node-is-redirect (1.0.0-1) experimental; urgency=low
 .
   * Initial release (Closes: #850498)
Checksums-Sha1:
 7d4b9326384696871900c53fbf78475106872ece 2082 node-is-redirect_1.0.0-1.dsc
 067cee7fa68f67e597f492c719efebb462dac3b7 2103 
node-is-redirect_1.0.0.orig.tar.gz
 efbe296c0789d01adca885e6369b8999b774565b 2212 
node-is-redirect_1.0.0-1.debian.tar.xz
 f85a197bc5ca7ae65072b84d8597071e6f72a7ee 3066 node-is-redirect_1.0.0-1_all.deb
 8be82d471e9dab55f38a292fdf88be40a020c5cd 4597 
node-is-redirect_1.0.0-1_amd64.buildinfo
Checksums-Sha256:
 32e94dda92c66e7370a35a82bd3d767139c1c04f2666e763568ea9ec3c66daff 2082 
node-is-redirect_1.0.0-1.dsc
 4710dcc654d19f3b10f78ce2b59f75ed798643a224c0a894015ad48a7199b6e7 2103 
node-is-redirect_1.0.0.orig.tar.gz
 620e4a06d514b5de6a3da27df788b1fb5016cdf61a125e8d1d2f42b48f9bb915 2212 
node-is-redirect_1.0.0-1.debian.tar.xz
 4927e41106392780a2cb669a0ead1ee53dc0fc54fa7a44c4d91293beed65adc0 3066 
node-is-redirect_1.0.0-1_all.deb
 df7c9c05a99111f5f9a893771e007740d78d450f26923ec1a357287fec5f1a4d 4597 
node-is-redirect_1.0.0-1_amd64.buildinfo
Files:
 b2b1ea527f2905fec38d494e3a5b00f7 2082 web optional node-is-redirect_1.0.0-1.dsc
 46166dc45911b1e0b34559600e869459 2103 web optional 
node-is-redirect_1.0.0.orig.tar.gz
 f7c29efc1f3080e69609ba9801e5608b 2212 web optional 
node-is-redirect_1.0.0-1.debian.tar.xz
 64903c7c32db80cf7ceb8766e03eb064 3066 web optional 
node-is-redirect_1.0.0-1_all.deb
 f31b585ed2a0b0c5238fd3a72777ae71 4597 web optional 
node-is-redirect_1.0.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAliijZwACgkQzh+cZ0US
wirObhAAt57/H/02cT1q5gvQhbdvkgRjWH0eS55nQURNZ2QQyeG2QHA2PmyIIxTI
Ko5YpajxErRgJIBbNgWe5cI12dabAIoOayFhDIHoKEwwLIV17TTnOCdnO9+h7qfX
PO2aRzYv4NAUtDEHg4ZwnAN9N53BoujiVNqk7IlSEuGc4IUOi3UjAY/bPrnhq2BF
brzgFimeNJDd1skYr8ISC/TIMr52+twQ5tJUYQ2KE3JJDxuqDu0SUCcbsqFkgmLv
UIjQpjNuuWuEK5d6ONbO5e8Cm+lCB52kI/p9EgpELhVVolEvKkDCjq7+kJsidwu+
g7JWiwuh1ODgSv9I6gDU7VmIQQwXhCxSHkhyKj5V2+7R75yeBoez+pJ2Z2R3wte7
jCNIJipq23m9DXTRyKFKGgVXt7HaniTbRqEjFNnPrE7+9zabP3otIVDvqKP7zMrm
kJfFz/rEa2+DWxs29R0bkKOqPcNHfZRV01sZkTKKVCf+3+Uj4JgE1YNlY+69BN3d
b+I1Vci+wvveCrrYARLbA5YZfRKt9ZZryZu47+hc1lgfyF6YTrP9e7MT7OmHHnUp
NAhHeJFb4k0J+gYnuYkTzFYH9fgMV0vUk5CrYq+e3cyJsY0r0/IQmpg0S2Y79V9O
479HVEILmw2nLGP5Rv7qbPFHCCUlxGQA9aFaFUFvrDF1Ef6+nos=
=ubR8
-END PGP SIGNATURE-

Accepted node-p-finally 1.0.0-1 (source all) into experimental, experimental

2017-02-12 Thread Shirish Togarla

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 04 Feb 2017 19:13:01 +
Source: node-p-finally
Binary: node-p-finally
Architecture: source all
Version: 1.0.0-1
Distribution: experimental
Urgency: low
Maintainer: Debian Javascript Maintainers 
<pkg-javascript-de...@lists.alioth.debian.org>
Changed-By: Shirish Togarla <shirishtogarla...@gmail.com>
Description:
 node-p-finally - Invoked when the promise is settled regardless of outcome
Closes: 854187
Changes:
 node-p-finally (1.0.0-1) experimental; urgency=low
 .
   * Initial release (Closes: #854187)
Checksums-Sha1:
 82a965c077abc85dc4ccac83dbb250ff05c350e0 2065 node-p-finally_1.0.0-1.dsc
 59fbb647903574e02bc9513c5fa9ec6cdf84ca13 2497 node-p-finally_1.0.0.orig.tar.gz
 2cbe6ac83a4ce3d21d8b00c1cfc7c29f779b1ce8 2064 
node-p-finally_1.0.0-1.debian.tar.xz
 671523b0c52995a496785301bd6c095852a4ed7f 3142 node-p-finally_1.0.0-1_all.deb
 551da1d08c731625a8594ec4334d1b9b9414143c 4577 
node-p-finally_1.0.0-1_amd64.buildinfo
Checksums-Sha256:
 c5d1533d2f4c7800eb9b956ae3e3de9ad6da6c7e1b2f5371544f34279fa15b33 2065 
node-p-finally_1.0.0-1.dsc
 1becb02c072bc3fe20a097ba4094b57a85dbdbf7a16f16c07c1291914a4faee6 2497 
node-p-finally_1.0.0.orig.tar.gz
 c0d2de284ad9f8aea54fbae0a56ba0dc1fa0f15b7ded71a95d720c0ffd522b63 2064 
node-p-finally_1.0.0-1.debian.tar.xz
 62ea3c8616e22ac94eabf19c8374434aa4705917a4c72ccafca4e0518c6f414e 3142 
node-p-finally_1.0.0-1_all.deb
 da82caca8a001f3c49a06b127942152ef9b12451e5a5dc512d273f4bcd8579c2 4577 
node-p-finally_1.0.0-1_amd64.buildinfo
Files:
 829e6ddfdecd015e2f70b77a14d849a2 2065 web optional node-p-finally_1.0.0-1.dsc
 9e7d604e1a292abc991178f86e323966 2497 web optional 
node-p-finally_1.0.0.orig.tar.gz
 5e545a9128c57d2eafc937dfe0229606 2064 web optional 
node-p-finally_1.0.0-1.debian.tar.xz
 47b3039663799060bb861407f000c8cf 3142 web optional 
node-p-finally_1.0.0-1_all.deb
 dc517fd4860f734e80329ee42122d49c 4577 web optional 
node-p-finally_1.0.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAligUpoACgkQzh+cZ0US
wiq6Pw/+LBWQusVHh4ml7kfB8I8THjMLwhlnLQAGAomV7JpOCXvX0Y0/562+yhqq
EmFuG2v2ruzLXpgVuNvtjosSU3BFXMPN+6voV4MEbyj+wXVom38KH4irMW1Zi+4V
9FM6+zRXQ8CZB/Op9j/lXDskBuH63SMlzm55Kw+3+qcogfsUdXgxEwcUdXswx9AN
Ed6y0M2gEDuOBCu7gDwg6SJIvwoMyn12ZUYmkIwdtbZQ1FnEN9UXsYJigKM99n3y
PLVNLTVlh0LEGds9ru5sIeDPTxOxLjHBA1gaPLm6W07JGrM3d8zDoBhwL90V9z1F
DuuAIswzCPBRQhIRlVjtHrGy/w8r1a2EhN4u13XkCYc4A7FkV2w7/lzR+eBpp98a
AM2xAYZkflXDH1RCuAzuvPzuL4Q8TYgafiDxv2c0nsN8gNH7AxG50SXe6oGrVv88
dmF4WiX1HLrJHAeHch4OBh32sm3SJUawYFFxfh3M6eJZJYKZ73nljMT+rj6IfzGy
dLX+x4VaDu4+PTRHPzBT7Mvn79h7svzBdT0MNl29IUiLlCs9NDrKktuMOhb6mxt2
/4yUs3n15EQf+hP15cyMIl9TrfAgQGAotXoVC+XC7ITUAAEK2zEOV9eDRm/+tIFk
b0krklPaIRaGPFS/EQgXbfd8nBke2dUTLlL5QLCHZFuyqCtzckQ=
=hEGw
-END PGP SIGNATURE-

Accepted node-time-zone 1.0.0-1 (source all) into experimental, experimental

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 04 Feb 2017 13:33:59 +
Source: node-time-zone
Binary: node-time-zone
Architecture: source all
Version: 1.0.0-1
Distribution: experimental
Urgency: low
Maintainer: Debian Javascript Maintainers 
<pkg-javascript-de...@lists.alioth.debian.org>
Changed-By: Shirish Togarla <shirishtogarla...@gmail.com>
Description:
 node-time-zone - Pretty time zone: `+2` or `-9:30`
Closes: 854156
Changes:
 node-time-zone (1.0.0-1) experimental; urgency=low
 .
   * Initial release (Closes: #854156)
Checksums-Sha1:
 e4e6e264f622373bf2fb57c13bd33c5116406916 2065 node-time-zone_1.0.0-1.dsc
 563ac53be4a4363e6eb2a97c0176b9d50247b88c 2175 node-time-zone_1.0.0.orig.tar.gz
 3e8d3eb3bba11c7f897dc142e781dba9b590dc2a 2084 
node-time-zone_1.0.0-1.debian.tar.xz
 30d7aa7b137994b68d813a69f60c09983c38982c 3084 node-time-zone_1.0.0-1_all.deb
 2bf01942313ea78f8d7cfb12b950e761a2d69279 4575 
node-time-zone_1.0.0-1_amd64.buildinfo
Checksums-Sha256:
 24f541efdce5b33815eb7463907f54fce4a2a5cd347cfe80da749a478f0fd42a 2065 
node-time-zone_1.0.0-1.dsc
 c551d40ab85c552e55a2fccb69e74bbafcdb39660aa262eb87cf4dcc243f3d7b 2175 
node-time-zone_1.0.0.orig.tar.gz
 f28b2527c8fa9978aec0d9349e1926727089b3b76668ebc1b932a14389721807 2084 
node-time-zone_1.0.0-1.debian.tar.xz
 94d161f02270d6a2c4f6c685b6b1944d109a3a256ce7dfe2b2b32069d4579c99 3084 
node-time-zone_1.0.0-1_all.deb
 9086548abfb156b0498a339fc225fca40f8968363b2af7a3bcc0fb016661f75a 4575 
node-time-zone_1.0.0-1_amd64.buildinfo
Files:
 520f497af7ffbf3e6357217347fe2541 2065 web optional node-time-zone_1.0.0-1.dsc
 f9493f2726d78472e2857c067822c031 2175 web optional 
node-time-zone_1.0.0.orig.tar.gz
 278643808810fc2ceddf535557c7022c 2084 web optional 
node-time-zone_1.0.0-1.debian.tar.xz
 69c48205f9a50ba5311f763bb09614f3 3084 web optional 
node-time-zone_1.0.0-1_all.deb
 1ea85ea85813a7b338012ee0aee32bf5 4575 web optional 
node-time-zone_1.0.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAliWtQoACgkQzh+cZ0US
wiogfg//R9vhTWtAVhH2PPYM9fYpSN6/d7SQLgdem/BR6HzUXtI7++R8Ncrj04CY
onTKE1OyaA8O17H/K4uDB13ITWAtJtG1Y0LIjjdedsH9n04VqR73GX5eQssvtYdo
wOJY/244mz/IedpobkTYmPUFEfOwkVWwtNYu4RQZPQU3EhRNkvnZq1BMo4M25HhW
0uYN4zfFz2pm9Woh7IZx/BZTxIGN8mzo9fnpBG4OySPRAjGYqAZ9BUqjYLCuK6Cx
LUtQ0++A0F1E6k9b7Xi8A/RBRXIG43w9cle/2cougYRj2N2+h5hPvCT4Njnaq79Y
ZHNrhrR3LcSi9gDSN6SExkgMh/LN6Furd3ZXNPpMFnCGIt4lZrvcNAukV5cjptUq
+Wujw26ARAemh5LDHSPrfSFsvuN4LEKmX35KaFcbqtiA5I1prGZHZxEgSb11EQcP
V1Zsnj0HWBpbfIOTxXvtfspH96wmZ/nTb1CozeBQhIjsh3+gqBMz/kw51ptxrCNX
fi4mlGsR+ZIiVLzgq1nQyfy1k9knR8SCe57rkJVp4yvuwNqpASDsY+GeJIJba7cR
XmQoNvgSd3z3BPU6UXyf06spUmEbR4Stg5GUzbm25YP9KQdpw9u4zvwChf5Ptiu/
dYYphxLUC7aVCNVw6niUz5L9Z2g6rpsPmvF6/jnTIiWZeYktIPE=
=MDJ+
-END PGP SIGNATURE-

Accepted node-prepend-http 1.0.4-1 (source all) into experimental, experimental

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 03 Feb 2017 16:02:17 +
Source: node-prepend-http
Binary: node-prepend-http
Architecture: source all
Version: 1.0.4-1
Distribution: experimental
Urgency: low
Maintainer: Debian Javascript Maintainers 
<pkg-javascript-de...@lists.alioth.debian.org>
Changed-By: Shirish Togarla <shirishtogarla...@gmail.com>
Description:
 node-prepend-http - Prepend `http://` to humanized URLs like todomvc.com and 
localhos
Closes: 854067
Changes:
 node-prepend-http (1.0.4-1) experimental; urgency=low
 .
   * Initial release (Closes: #854067)
Checksums-Sha1:
 f3323c0c535039132006fcdc9bb9e85158b3c211 2069 node-prepend-http_1.0.4-1.dsc
 4071677c01e80e0f422e174b9dc4869f2ca5a468 2151 
node-prepend-http_1.0.4.orig.tar.gz
 b3af043a5522a6356b9db518e14411e26f3452e5 2016 
node-prepend-http_1.0.4-1.debian.tar.xz
 31061298ad1ce45aab73ac3852afe0588d6bd144 2900 node-prepend-http_1.0.4-1_all.deb
 a78f6fb4153a24cf2104aa0e00f78a90fcbc52a2 4601 
node-prepend-http_1.0.4-1_amd64.buildinfo
Checksums-Sha256:
 de65b5c944155a403f0d66c1fc6b6917cd8c54154e9cc64c83842e9cbb859646 2069 
node-prepend-http_1.0.4-1.dsc
 1c0596338c1e59edfd19cd1e0342dcc9fe732abcbf411b5e9831254ed7ae248c 2151 
node-prepend-http_1.0.4.orig.tar.gz
 9a52153cdecc1edb2f8a21697c694f97ec78b3e2eb8771d0dc623246a17fadb1 2016 
node-prepend-http_1.0.4-1.debian.tar.xz
 35171ab5d7cf2e72b294b9ce655acf89203f700531cc0690ad5092b5f374df59 2900 
node-prepend-http_1.0.4-1_all.deb
 efa300ca254aa65971134a159759b6519fd337382010e89cc7d9eaa597357f84 4601 
node-prepend-http_1.0.4-1_amd64.buildinfo
Files:
 893b4deded53f7ffe6e293104acc7778 2069 web optional 
node-prepend-http_1.0.4-1.dsc
 95c6ac8f3db0fd17ed6d7272306b6d99 2151 web optional 
node-prepend-http_1.0.4.orig.tar.gz
 e715aeeed866b3696f3ecc4fa5a1e638 2016 web optional 
node-prepend-http_1.0.4-1.debian.tar.xz
 71ddab82f0ecaac63eaf1a4238397ad7 2900 web optional 
node-prepend-http_1.0.4-1_all.deb
 79ffda7d5e09a6cafeb6d1a8c2bdac68 4601 web optional 
node-prepend-http_1.0.4-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYnFe0AAoJEM4fnGdFEsIq/4AP/0vuyTictjpxr6lZWx16Qk+X
Pc7St9S2eMmGX3exhNS0oceNWtED8/DcaUMq0IGRkwCxI95p9exP7qhT+cU8gkdf
8J/8labm2o4foCzwka2vFUuXgVcSgnYsQTcJbL5vU3NCDTrD111Ic/ITnz9bdPKo
jGiTF8zwOLRAQanHjTY2k54s29j1sPgMAmDdXQPhGxcyKaWUzGZ+Uel9CNp61oLH
Tr77u+oNKUQvdW00gIAxd9yagJh1jPEEqlKBq/0Wx8Wynv1KLmQKvpO+OV+Porz5
GLXpSrNytzWaZ4CE69NUH65EW9laaAjSluV8mjTyjt/jvVN5syd8JUTHVVnILRQK
qZ5wEIzxbqDIkJdjcVL0U1ajza6c+FKTYugTKrlp6EvC+4kwT1SsFCRJI4DitSdX
d0khziScbk+EQTt5GAqh9ZA8mAYHn8Po7r4GIp42xDTAOz4wXOx1UIKtRURWRAgD
Mw6J4UT02/G994IxFUWqY3w3HfrXiVEH/6Iec9ADY0HKzvqV6BfMcfauzJjs5YSs
lmeCHWcqWNMHJcLh2H7UY8XGY20JoyWUCMZ7ScJEFg8vg5ZzwnVqyioc21ZkIdFM
253/KeCkU7BtOYxRSvXJAGtMlonwv6r9/G89mVPjpOGejjL5PQddBizW4WgCOXph
n4hq+Uq47yxYrTlgNAaj
=Q5dD
-END PGP SIGNATURE-

Accepted node-lowercase-keys 1.0.0-1 (source all) into experimental, experimental

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 04 Feb 2017 15:01:06 +
Source: node-lowercase-keys
Binary: node-lowercase-keys
Architecture: source all
Version: 1.0.0-1
Distribution: experimental
Urgency: low
Maintainer: Debian Javascript Maintainers 
<pkg-javascript-de...@lists.alioth.debian.org>
Changed-By: Shirish Togarla <shirishtogarla...@gmail.com>
Description:
 node-lowercase-keys - Lowercase the keys of an object
Closes: 854169
Changes:
 node-lowercase-keys (1.0.0-1) experimental; urgency=low
 .
   * Initial release (Closes: #854169)
Checksums-Sha1:
 3fd052b0c0fe89077a77e32699212fa499889ca3 2086 node-lowercase-keys_1.0.0-1.dsc
 d00e394e62dc5ff617cbd197a2dce9e339f2737d 2114 
node-lowercase-keys_1.0.0.orig.tar.gz
 196f2cbce94812f00266da9274949d4ae0bc2a6c 2064 
node-lowercase-keys_1.0.0-1.debian.tar.xz
 a205d5217c1c0102260affb36a3b160b2c5a071b 2916 
node-lowercase-keys_1.0.0-1_all.deb
 09cf5fdebb74f0dbe20f7178bdb33a418971e55a 4607 
node-lowercase-keys_1.0.0-1_amd64.buildinfo
Checksums-Sha256:
 8b78547793dc44bd9fc3b042d3a637920e6ae2988f7057214b9cca915df402e8 2086 
node-lowercase-keys_1.0.0-1.dsc
 e74374e060b408710232c4d45f37a857142219dd1a953dd5e1df7f2009dfb08f 2114 
node-lowercase-keys_1.0.0.orig.tar.gz
 4d77ca294d6ed806a0ac5c0ac76c2b86cb01525d79ad549ee586433566741c82 2064 
node-lowercase-keys_1.0.0-1.debian.tar.xz
 c5a3e8999700127ddec319ed46fb76bdfc7a4dd997c46513b2feef40c26a8033 2916 
node-lowercase-keys_1.0.0-1_all.deb
 d55ef9e4c4b84ba787203fe6ea8d26943cf69e7b6828494fbaca7a444f0ccdf2 4607 
node-lowercase-keys_1.0.0-1_amd64.buildinfo
Files:
 4f97542c55ff46a21fefaafa26cccf6d 2086 web optional 
node-lowercase-keys_1.0.0-1.dsc
 c651e0fda3f82be9dfce56dad21c4bfb 2114 web optional 
node-lowercase-keys_1.0.0.orig.tar.gz
 8f02b87aea4736294666c3c3d98ca1f5 2064 web optional 
node-lowercase-keys_1.0.0-1.debian.tar.xz
 35214dbd79dc0b449377051c758a8265 2916 web optional 
node-lowercase-keys_1.0.0-1_all.deb
 7a862bcad10a8277b8f2322368738cd3 4607 web optional 
node-lowercase-keys_1.0.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYmtw6AAoJEM4fnGdFEsIqUhIQAJF50IMP+6Cyye04gnVKaJ3A
Mw/swNQ1hgVLqtAyYltKgBa6XhAInZkj+ckBy9Bv2qWJvdI6ZZ61sg+dsHXKgrxd
7xNi+EXh5X+IsSG3xf6ngxJfRzuiqmZygLWsuT0SkkdBVHXeJ2CfZvBqx9Ukc70D
ngV8Cd5WlfpES3+EctDy2z1cLRH/2WLH2XM0/4XTREHW77eLfavB81G2vVzKqGRa
uLumOujuF3IT63pMMu6/C/pQT5iui8zpAs8W14R6xi/VG+i2FeK5UPaAoksvXs+B
l3SwVab9UCvnFLcwi7zhSg+9P4VkiRXWfto3wIJteNZ8yE3n2s6SKRuJfamrjo15
M+F5c9mcbraSkzsmUpRBNnlrQLJ32OBtVUFrFYyibwiD0BZBDaiWr0JF27YQqeno
ddFIRuY8M5cRRBqW7USSzGLkppVhIXsROo6/0NGitVtEO3R7KllNhDDKnkTzc9XO
+hofaIYlRvcYHS9cxDkN+K0VFsylfkzKGlJmQjX+XVK+vWnMuow5+R95EooCf74t
wXF49cU0B612Lo1CoR6OsWQAC20dqKYmSGtZxEpBLITO+73OQstVd/5NdOhxcUhQ
JaTtXxjIrY+LlrUzOQXWX5YpACCF162sByhOGCvuu/UcoIlybX9F9W41V2jM8B0z
v0Om2TFdnKyhtYZ/AFyc
=VyEX
-END PGP SIGNATURE-

Accepted node-safe-buffer 5.0.1-1 (source all) into experimental, experimental

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 04 Feb 2017 18:52:59 +
Source: node-safe-buffer
Binary: node-safe-buffer
Architecture: source all
Version: 5.0.1-1
Distribution: experimental
Urgency: low
Maintainer: Debian Javascript Maintainers 
<pkg-javascript-de...@lists.alioth.debian.org>
Changed-By: Shirish Togarla <shirishtogarla...@gmail.com>
Description:
 node-safe-buffer - Safer Node.js Buffer API
Closes: 854185
Changes:
 node-safe-buffer (5.0.1-1) experimental; urgency=low
 .
   * Initial release (Closes: #854185)
Checksums-Sha1:
 1b56aeb5ec95d6d1414b06de566a3d82996eb665 2044 node-safe-buffer_5.0.1-1.dsc
 84ef04847a7cf78ece0ef382f04632b21732b1ee 8890 
node-safe-buffer_5.0.1.orig.tar.gz
 4add36fc68d9b1686f017e1c65bd7dc7cc40244c 2120 
node-safe-buffer_5.0.1-1.debian.tar.xz
 8f9ffd3f066ed4e84086502e3a07db12fc295ccd 9922 node-safe-buffer_5.0.1-1_all.deb
 8a72ce7a12736bb406a4f4097c9ed2608862ec5f 4575 
node-safe-buffer_5.0.1-1_amd64.buildinfo
Checksums-Sha256:
 9c7a0d418c22176db654a4480d21237eac6e670766bc4583270bd741ba07dd4e 2044 
node-safe-buffer_5.0.1-1.dsc
 35baea811f63bc59bdaf85ad48e4ddce28b22ef0a5a2d1665a55053c6230b2ce 8890 
node-safe-buffer_5.0.1.orig.tar.gz
 7970d42f8fb4063975b98de5cc312837ed9cd262a1dbea8b2e8f8439959f695b 2120 
node-safe-buffer_5.0.1-1.debian.tar.xz
 105da8fa7b2894e3d9d463e9e40ffc4c701fbfabe88829879852f240d491786e 9922 
node-safe-buffer_5.0.1-1_all.deb
 2381b5f94b328df661cdf15591753f29b470d826d254640581e9685124d78393 4575 
node-safe-buffer_5.0.1-1_amd64.buildinfo
Files:
 b4a73f9238db4c94cedab3e53363b5d8 2044 web optional node-safe-buffer_5.0.1-1.dsc
 7deb3e72fec9d103de187d60a47975a9 8890 web optional 
node-safe-buffer_5.0.1.orig.tar.gz
 cc082dd1fd2ad2c7fc6fe287272d720f 2120 web optional 
node-safe-buffer_5.0.1-1.debian.tar.xz
 8782c2566658d5f4f3d01a17f46135d8 9922 web optional 
node-safe-buffer_5.0.1-1_all.deb
 e9277364b49865e43425640714618531 4575 web optional 
node-safe-buffer_5.0.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYmdAcAAoJEM4fnGdFEsIqcJ8P/RomYWJ5Ju1y0wxL1ZEhF9Ee
J0jzCziv4vwb03HLMdjuIF/oqm+LBlt0R9TrkvLsD2saPJHmgitUhktFtN6qmqUF
fd8hjFW5iBdWILp1I6mPjYS1q+YqSjTbd6xFbWiR/luaGjUtCJrlS/vYRusopo0l
GVVhDziBX9Q7vd9JuzCCKmtHj9Czj/f+5t1/PkQs5MAtDMhCa4DbutYVlQiBA8S2
teVN0dR4ytCeHQgNJDkq20UwTA3/9RHH8QmDTF/OAqYKgVPtb5nZYAWGOwkgjpCn
TZvCpAQey9LoTSBp7MU2hSCsmsGh6FflIJushLuqObadXTeZv58ZTg7n6Q/7hIsQ
67DmcnN44dnELREdqi6++kLjRgBc7Cc0efpE4C9cYVUnXTbnihj+1RNn8cJd2rmb
NNRXMsYEvgpdQHAkR07YTY84l7PeuRtS/Ht44OBN1TXk2jwxRvGTHJYVW7CrHyY8
qthYyISczs0UmTs7iArkXQd7FvrDlrGoZaFbn1VNmpgl3MsPCLfYjUL4LBzBQFG3
/jEDrEPufnjE0kFLceU9+lC6HqWF3kdIdpMwRC0TrdoD7eE5nD9gADL+6n/v5OZ9
leue+N3Hqxr2Zr5Qiqs1EHo21Q42naUM9gmn2XaqQpEnxe1ZOUQeMHMYf60NP2Ik
wb0ev7tYfV4p5KPmgYa7
=cIlg
-END PGP SIGNATURE-

Bug#854510: ITP: node-astw -- walk the ast with references to parent nodes

Package: wnpp
Severity: wishlist
Owner: Shirish Togarla <shirishtogarla...@gmail.com>
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-astw
  Version : 2.0.0
  Upstream Author : James Halliday <m...@substack.net> (http://substack.net)
* URL : https://github.com/substack/astw
* License : Expat
  Programming Lang: JavaScript
  Description : walk the ast with references to parent nodes

 This module is a faster version of
 [falafel](https://github.com/substack/node-falafel)
 that only does ast walking and `.parent` tracking, not source transforms.
 # example
 var astw = require('astw');
 var deparse = require('escodegen').generate;
 var walk = astw('4 + beep(5 * 2)');
 walk(function (node) {
var src = deparse(node);
console.log(node.type + ' :: ' + JSON.stringify(src));
 });

Bug#854509: ITP: node-date-now -- A requirable version of Date.now()

Package: wnpp
Severity: wishlist
Owner: Shirish Togarla <shirishtogarla...@gmail.com>
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-date-now
  Version : 1.0.1
  Upstream Author : Raynos <rayn...@gmail.com>
* URL : https://github.com/Raynos/date-now
* License : Expat
  Programming Lang: JavaScript
  Description : A requirable version of Date.now()

 Use-case is to be able to mock out Date.now() using require interception.
 For example
 var now = require("date-now")
 var ts = now()
 var ts2 = Date.now()
 assert.equal(ts, ts2)
 Example of seed:
 var now = require("date-now/seed")(timeStampFromServer)
 // ts is in "sync" with the seed value from the server
 // useful if your users have their local time being a few minutes
 // out of your server time.
 var ts = now()

Bug#854508: ITP: node-hash-base -- abstract base class for hash-streams

Package: wnpp
Severity: wishlist
Owner: Shirish Togarla <shirishtogarla...@gmail.com>
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-hash-base
  Version : 3.0.3
  Upstream Author : Kirill Fomichev <fana...@ya.ru> (
https://github.com/fanatid)
* URL : https://github.com/crypto-browserify/hash-base
* License : Expat
  Programming Lang: JavaScript
  Description : abstract base class for hash-streams

 Abstract base class to inherit from if you want to create streams
 implementing the same API as node crypto Hash 1. For example
 function MyHash () {
  HashBase.call(64) // in bytes
 }
 inherits(MyHash, HashBase)
 MyHash.prototype._update = function () {
  // hashing one block with buffer this._block
 }
 MyHash.prototype._digest = function () {
  // create padding and produce result
 }

Bug#854503: ITP: node-strict-uri-encode -- A stricter URI encode adhering to RFC 3986

Package: wnpp
Severity: wishlist
Owner: Shirish Togarla <shirishtogarla...@gmail.com>
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-strict-uri-encode
  Version : 2.0.0
  Upstream Author : Kevin Mårtensson <kevinmartens...@gmail.com> (
github.com/kevva)
* URL : https://github.com/kevva/strict-uri-encode#readme
* License : Expat
  Programming Lang: JavaScript
  Description : A stricter URI encode adhering to RFC 3986

 A stricter URI encode adhering to [RFC 3986].For example
 const strictUriEncode = require('strict-uri-encode');
 strictUriEncode('unicorn!foobar');
 //=> 'unicorn%21foobar'
 strictUriEncode('unicorn*foobar');
 //=> 'unicorn%2Afoobar'

Bug#854501: ITP: node-array-reduce -- `[].reduce()` for old browsers

Package: wnpp
Severity: wishlist
Owner: Shirish Togarla <shirishtogarla...@gmail.com>
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-array-reduce
  Version : 0.0.0
  Upstream Author : James Halliday <m...@substack.net> (http://substack.net)
* URL : https://github.com/substack/array-reduce
* License : Expat
  Programming Lang: JavaScript
  Description : `[].reduce()` for old browsers

 Create a result `res` by folding `acc = f(acc, xs[i], i)` over each
element in
 the array `xs` at element `i`. If `init` is given, the first `acc` value is
 `init`, otherwise `xs[0]` is used. For example
 var reduce = require('array-reduce');
 var xs = [ 1, 2, 3, 4 ];
 var sum = reduce(xs, function (acc, x) { return acc + x }, 0);
 console.log(sum);
 Output:
 10

Bug#854360: ITP: node-array-map

2017-02-06 Thread Shirish Togarla

Package: wnpp
Severity: wishlist
Owner: Shirish Togarla <shirishtogarla...@gmail.com>
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-array-map
  Version : 0.0.0
  Upstream Author : James Halliday <m...@substack.net> (http://substack.net)
* URL : https://github.com/substack/array-map
* License : Expat
  Programming Lang: JavaScript
  Description : `[].map(f)` for older browsers

 It maps an array(i.e. every value in the array) onto a function and returns
 the result.For example
 var map = require('array-map');
 var letters = map([97,98,99], function (c) {
return String.fromCharCode(c);
 });
 console.log(letters.join(''));
 The output is
 abc

Re: Bug#854183: ITP: node-time-out

2017-02-06 Thread Shirish Togarla

The link is https://git.fosscommunity.in/shirish/node-time-out.git

On 6 February 2017 at 13:59, Dominique Dumont <d...@debian.org> wrote:

> On Sunday, 5 February 2017 00:09:07 CET Shirish Togarla wrote:
> > * URL : https://github.com/mfunkie/time-out#readme
>
> This URLs returns a 404.
>
> I could not find time-out repo in https://github.com/mfunkie/
>
> Please provide the correct upstream URL and author
>
> All the best
> --
>  https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
> http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org
>

Bug#854187: ITP: node-p-finally

Package: wnpp
Severity: wishlist
Owner: Shirish Togarla <shirishtogarla...@gmail.com>
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-p-finally
  Version : 1.0.0
  Upstream Author : Sindre Sorhus <sindresor...@gmail.com> (sindresorhus.com
)
* URL : https://github.com/sindresorhus/p-finally#readme
* License : Expat
  Programming Lang: JavaScript
  Description : `Promise#finally()` ponyfill - Invoked when the promise
is settled regardless of outcome

 `Promise#finally()` ponyfill - Invoked when the promise is settled
 regardless of outcome. It can be used for cleanup purpose.

Bug#854185: ITP : node-safe-buffer

Package: wnpp
Severity: wishlist
Owner: Shirish Togarla <shirishtogarla...@gmail.com>
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-safe-buffer
  Version : 5.0.1
  Upstream Author : Feross Aboukhadijeh <fer...@feross.org> (
http://feross.org)
* URL : https://github.com/feross/safe-buffer
* License : Expat
  Programming Lang: JavaScript
  Description : Safer Node.js Buffer API

The goal of this package is to provide a safe replacement for the node.js
 `Buffer`. It's a drop-in replacement for `Buffer`. You can use it by adding
 one `require` line to the top of your node.js modules; for example
 var Buffer = require('safe-buffer').Buffer
 Existing buffer code will continue to work without issues.

Bug#854183: ITP: node-time-out

Package: wnpp
Severity: wishlist
Owner: Shirish Togarla <shirishtogarla...@gmail.com>
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-time-out
  Version : 0.0.3
  Upstream Author : Mark Funk
* URL : https://github.com/mfunkie/time-out#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Simple setTimeout cancellation

 Timeout is a library that wraps setTimeout to provide an easy way to clear
 timeouts.

Bug#854169: ITP : node-lowercase-keys

Package: wnpp
Severity: wishlist
Owner: Shirish Togarla <shirishtogarla...@gmail.com>
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-lowercase-keys
  Version : 1.0.0
  Upstream Author : Sindre Sorhus <sindresor...@gmail.com> (sindresorhus.com
)
* URL : https://github.com/sindresorhus/lowercase-keys
* License : Expat
  Programming Lang: JavaScript
  Description : Lowercase the keys of an object

 It lowercases the keys and returns a new object.
 If you pass the keys of an object which are not in lowercase or if you
 want to ensure that all the keys are in lowercase then you can pass the
 object as an argument and it returns a new object with all the keys in
 lowercase.

Bug#854161: ITP: node-is-utf8

Package: wnpp
Severity: wishlist
Owner: Shirish Togarla <shirishtogarla...@gmail.com>
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-is-utf8
  Version : 0.2.1
  Upstream Author : wayfind
* URL : https://github.com/wayfind/is-utf8#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Detect if a buffer is utf8 encoded

 It detects if a buffer is utf8 encoded. If it is utf8 encoded then it says
 true or otherwise false. It need the minimum amount of bytes is 4.

Bug#854156: ITP: node-time-zone

Package: wnpp
Severity: wishlist
Owner: Shirish Togarla <shirishtogarla...@gmail.com>
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-time-zone
  Version : 1.0.0
  Upstream Author : Sindre Sorhus <sindresor...@gmail.com> (sindresorhus.com
)
* URL : https://github.com/sindresorhus/time-zone#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Pretty time zone: `+2` or `-9:30`

  This package displays the Coordinated Universal Time of the current time
  zone. For example if current time zone is Norway then it will show the
  UTC time. You can also put an arbitrary date in the arguments.

Bug#854108: ITP: node-has-yarn -- Check if a project is using Yarn