from:"shirish"

Package: wnpp
Severity: wishlist
Owner: Shirish Togarla 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-has-yarn
  Version : 1.0.0
  Upstream Author : Sindre Sorhus  (sindresorhus.com
)
* URL : https://github.com/sindresorhus/has-yarn#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Check if a project is using Yarn

 Useful for tools that needs to know whether to use `yarn` or `npm` to
install
 dependencies. You can check if a project is using Yarn.

Bug#854156: ITP: node-time-zone

Package: wnpp
Severity: wishlist
Owner: Shirish Togarla 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-time-zone
  Version : 1.0.0
  Upstream Author : Sindre Sorhus  (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#854161: ITP: node-is-utf8

Package: wnpp
Severity: wishlist
Owner: Shirish Togarla 
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#854169: ITP : node-lowercase-keys

Package: wnpp
Severity: wishlist
Owner: Shirish Togarla 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-lowercase-keys
  Version : 1.0.0
  Upstream Author : Sindre Sorhus  (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#854183: ITP: node-time-out

Package: wnpp
Severity: wishlist
Owner: Shirish Togarla 
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#854185: ITP : node-safe-buffer

Package: wnpp
Severity: wishlist
Owner: Shirish Togarla 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-safe-buffer
  Version : 5.0.1
  Upstream Author : Feross Aboukhadijeh  (
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#854187: ITP: node-p-finally

Package: wnpp
Severity: wishlist
Owner: Shirish Togarla 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-p-finally
  Version : 1.0.0
  Upstream Author : Sindre Sorhus  (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.

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  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#854360: ITP: node-array-map

2017-02-06 Thread Shirish Togarla

Package: wnpp
Severity: wishlist
Owner: Shirish Togarla 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-array-map
  Version : 0.0.0
  Upstream Author : James Halliday  (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

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

Package: wnpp
Severity: wishlist
Owner: Shirish Togarla 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-array-reduce
  Version : 0.0.0
  Upstream Author : James Halliday  (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#854503: ITP: node-strict-uri-encode -- A stricter URI encode adhering to RFC 3986

Package: wnpp
Severity: wishlist
Owner: Shirish Togarla 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-strict-uri-encode
  Version : 2.0.0
  Upstream Author : Kevin Mårtensson  (
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#854508: ITP: node-hash-base -- abstract base class for hash-streams

Package: wnpp
Severity: wishlist
Owner: Shirish Togarla 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-hash-base
  Version : 3.0.3
  Upstream Author : Kirill Fomichev  (
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#854509: ITP: node-date-now -- A requirable version of Date.now()

Package: wnpp
Severity: wishlist
Owner: Shirish Togarla 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-date-now
  Version : 1.0.1
  Upstream Author : Raynos 
* 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#854510: ITP: node-astw -- walk the ast with references to parent nodes

Package: wnpp
Severity: wishlist
Owner: Shirish Togarla 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-astw
  Version : 2.0.0
  Upstream Author : James Halliday  (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));
 });

PTS, salsa and knowing if a Debian Maintainer has uploaded a point release.

2018-03-18 Thread shirish शिरीष

Dear all,

While I read some bits of [1] I haven't read through the whole thread,
only some. While the gentleman concerned has shared about getting
through the 'new' process, I feel even for users some parts could use
more love.

Now as I understand it and please share if I'm in the wrong,  alioth
is going away and salsa is taking over repository creation, branching
and maybe at some point also the BTS although then reportbug would
have to be retooled to query salsa/gitlab so similar functionality can
be provided as it does for bug creation .

Now I know that debian has a watch file by which the maintainers of
packages come to know of new upstream binary releases as and when they
do and at times there maybe a time lag between upstream and getting
the binary in unstable.

Now if the package maintainer is just a DM, even (s)f he prepares a
package, (s)he still needs the ok of a DD to upload/sponsor the
package so it fit for distribution i.e. new, experimental or unstable
and  ftp-mirror and that whole process.

Now a user of the package is usually in the dark about this and there
is a possibility of upsetting the maintainer even though the person is
active on their own team.

I looked at the tracker.debian.org BTS page and saw [2] 317711 which
exactly talks of this kind of situation and more and this was filed in
2005 so it isn't something which isn't known, just hasn't been
acknowledged.

This unknowing became apparent to me when the debian-mate were doing
packaging for the 1.20.0 release [3] and more recently when I am
asking for a point release of qbittorrent [4] . In this case I know
that the maintainer is usually pretty active and perhaps uses the
package as well.

I'm no programmer but just a mere user. I'm not subscribed to the list
so please CC me if somebody responds.

1. https://lists.debian.org/debian-devel/2018/03/msg00128.html
2. bugs. debian.org/317711
3. https://lists.debian.org/debian-mate/2018/02/msg00152.html
4. bugs.debian.org/893331

Look 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

Re: PTS, salsa and knowing if a Debian Maintainer has uploaded a point release.

2018-03-18 Thread shirish शिरीष

Reply in-line :-

On 18/03/2018, Andrey Rahmatullin  wrote:
> On Sun, Mar 18, 2018 at 01:54:20PM +0530, shirish शिरीष wrote:

Dear Andrey,

First of all thank you for responding.

>> and maybe at some point also the BTS although then reportbug would
>> have to be retooled to query salsa/gitlab so similar functionality can
>> be provided as it does for bug creation .
> I think the current consensus is that it won't.
>

That is a relief to know as I rely on reportbug and the BTS quite a bit

>> Now if the package maintainer is just a DM, even (s)f he prepares a
>> package, (s)he still needs the ok of a DD to upload/sponsor the
>> package so it fit for distribution i.e. new, experimental or unstable
>> and  ftp-mirror and that whole process.
> This is not true. Please read https://wiki.debian.org/DebianMaintainer
> I think you mean regular non-DM non-DD maintainers.
>

Hmm.. I was under the impression that DM or Debian Maintainers do not
have upload rights and only DD's have.

I am confused when I see packages such as
https://tracker.debian.org/news/896579/accepted-qbittorrent-403-1-source-amd64-into-unstable/
just to take as an example.
There have been few packages where I have been confused as well.

Now here it says -

Maintainer: Cristian Greco 
Changed-By: Andrew Starr-Bochicchio 

now what role does or did Andrew play in the above. Is he the uploader
or just a reviewer of the work that Cristian Greco did ? Or is it some sort
of team-maintenance thing, not sure.

I do and did see that Cristian did upload some of the older package
releases but
now Andrew seems to be handling that part.

>> Now a user of the package is usually in the dark about this and there
>> is a possibility of upsetting the maintainer even though the person is
>> active on their own team.

> The maintainer can also be preparing the package for uploading and you
> cannot do anything to know that except asking them. And if they committed
> the work in progress into the VCS the tracker will show that.

where would it show ?  Please share an example so I know what to look for.

> tracker could show RFSes though, like how-can-i-help does, actually I
> thought it already shows them.
>

I see two packages which have RFS against them in how-can-i-help

New packages waiting for sponsorship (reviews/tests are also useful):
 - logrotate - https://bugs.debian.org/884697 - RFS: logrotate/3.13.0-1 ITA
 - xml-core - https://bugs.debian.org/885641 - RFS: xml-core/0.18-1 [ITA]

but neither one of them shows up in tracker.debian.org .  I do see
that some people
have decided to adopt those packages which is good though.

>> I looked at the tracker.debian.org BTS page and saw [2] 317711 which
>> exactly talks of this kind of situation and more and this was filed in
>> 2005 so it isn't something which isn't known, just hasn't been
>> acknowledged.

> It only talks about NEW. tracker shows binary NEW, though only in the
> version sidebar, not in the news.
> Do you know any other states which it should track? It's not clear from
> your email.
>

Maybe I was not clear enough,  my concerns are not with the 'NEW' queue
i.e. $ aptitude search '~n' but for existing package updates also to have
the info. of package updates done but not yet in the archive in the
sidebar as well.

Maybe I should file a new bug ?

>> This unknowing became apparent to me when the debian-mate were doing
>> packaging for the 1.20.0 release [3] and more recently when I am
>> asking for a point release of qbittorrent [4] . In this case I know
>> that the maintainer is usually pretty active and perhaps uses the
>> package as well.

> It's not clear what problems do you have with these packages and what are
> you proposing to solve them.
>

Simply, have a more effective feedback loop for know-how as to what's coming
while at the same time create less bit of noise in the BTS asking for
new point releases.

The only other recourse I know  is to traverse
https://incoming.debian.org/debian-buildd/pool/ and that isn't
user/human friendly as it's machine-friendly.

I hope I was able to clarify what I meant above.

> --
> WBR, wRAR
>

-- 
  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: PTS, salsa and knowing if a Debian Maintainer has uploaded a point release.

2018-03-19 Thread shirish शिरीष

On 18/03/2018, Andrey Rahmatullin  wrote:



Dear Audrey,

Thank you again by responding.
> https://tracker.debian.org/pkg/ipdb
>

My query is actually solved by the link you shared. I'm sorry if I was a mess :)

>
> --
> WBR, wRAR
>

-- 
  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

why hasn't the debian transition freeze been announced or shared in debin testing info. or bits.debian.org ?

2018-04-25 Thread shirish शिरीष

Dear all,

I had read https://lists.debian.org/debian-devel-announce/2018/04/msg6.html
so knew when the transition freeze is going to happen. For a blog
post/technical article I wanted to share about the transition freeze
and went to https://www.debian.org/releases/testing/ as well as
https://bits.debian.org/ but neither seems to have that info.

Shouldn't be the milestone including perhaps info. on tentative alpha
releases be put somewhere or are the dates subject to change ?

If the dates are locked down, it would be nicer to be able to
share/link to an official page on debian website rather than just an
e-mail.

Looking for info.
-- 
  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: why hasn't the debian transition freeze been announced or shared in debin testing info. or bits.debian.org ?

2018-04-27 Thread shirish शिरीष

at bottom :-

On 26/04/2018, Emilio Pozuelo Monfort  wrote:



>
> Yes. In any case, those dates (as well as links to the announcement) are
> also
> available from https://release.debian.org/
>
> Emilio
>

Thank you Emilio/Pochu,

Just the link I was looking for to link to :)

-- 
  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 do people feel think of changing the configuration file path from ~/.aptitude/config to ~/.config/aptitude

2018-04-29 Thread shirish शिरीष

Dear all,

First of all thank you all the fine people who have contributed to
packaging and maintaining the whole suit of apt, aptitude, apt-get,
dpkg low and high-level variety of tools in Debian for system
administration and making good choices.

Please CC me if you any thoughts as although I'm subscribed to
debian-devel I have opted out of receiving mails due to the
high-volume nature of the mailing list.

Now about a year back, I had proposed changing paths of the
configuration file ~/.aptitude/config to ~/.config/aptitude . The
reason is for a change in
https://specifications.freedesktop.org/basedir-spec/basedir-spec-0.6.html

As shared by somebody in
https://www.reddit.com/r/debian/comments/8fpr6i/thoughts_on_changing_configuration_files_of/
I don't think I'm alone in this .

The obvious breakage would be in any scripts that use aptitude and one
way or the other depend or use the configuration path currently using
would be broken.

There may also be some subtle bugs which may or may not be uncovered
or not known which may be exposed by the change perhaps.

The other part which perhaps not correctly worded is that aptitude
would lose some of its special coolness as it would be in the space
where all other packages which use ~/.config are there and it would be
easier to find for common folks.

The upside if people think would be a good idea is that any perceived
or un-perceived fallout of the change, we would have at least a year
and a bit more to fix at least in Debian repos.

I do know that the Debian aptitude maintainers are conservative when
it comes to changes and understandably so.

I'm looking for people's thoughts on the above of what people think .
I am no coder hence I dunno how much work it would involve and would
the changes be self-sustained (till aptitude only) or the changes
would also lead to changes in libapt* packages although even then if a
transition were to be done it seems both seem to have smaller cycles
than some of the transition cycles we have got going through.

I did -

$ apt-rdepends -r aptitude
$ apt-rdepends -r libapt-pkg-dev

to have an idea in case if the change I ask meant they need to built
from source and transitioned.

I am sure there may be lacunae in my theory, but if not asked how would I know ?

Look forward to know.

--
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: what do people feel think of changing the configuration file path from ~/.aptitude/config to ~/.config/aptitude

2018-04-29 Thread shirish शिरीष

at bottom :-

On 29/04/2018, Chris Lamb  wrote:
> Hi shirish,
>
>> Re: what do people feel think of changing the configuration file
>> path from ~/.aptitude/config to ~/.config/aptitude
>
> Unless you are requesting a distribution-wide move from ~/.foo
> to XDG ~/.config/foo, filing a wishlist bug against the aptitude
> package would seem a more appropriate venue for this discussion..
>
>
> Regards,
>
> --
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-
>

Dear Chris,

Had already done it, see #894332 ,  But don't think it's not going to
go anywhere from the last two times :( as it seems the effort to do it
is not the worth the effort as shared by the maintainer.

At least I tried, well guess just will have to learn to live with it.

-- 
  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: what do people feel think of changing the configuration file path from ~/.aptitude/config to ~/.config/aptitude

2018-04-29 Thread shirish शिरीष

Reply in-line :-

On 29/04/2018, Chris Lamb  wrote:
> Shirish,
>

Chris,

>> Had already done it, see #894332 ,  But don't think it's not going to
>> go anywhere from the last two times :( as it seems the effort to do it
>> is not the worth the effort as shared by the maintainer.
>>
>> At least I tried, well guess just will have to learn to live with it.
>
> Thank you for linking the bug.
>
> Not speaking to this case specifically, but in general I would try
> to convince maintainers with some combination of irrefutable
> argument and well-tested patches (combined with a friendly demeanour
> and a rhethorical flourish) rather than try and summon the "mob" from
> debian-devel if I didn't immediately get my way.  ;)
>
>

The irrefutable argument is that most packages seem to think it's a
good and convenient way to do things and it does simplify things quite
a lot.

I didn't hear from the maintainers anything untoward except that it
would have breakage and probably needs fixing at various places.

I am at a loss as I'm not a coder but am open to testing any patches
and report any breakages if somebody can step up to do the same. I
have done that in the past

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877717

where I was able to connect with the maintainer and we did couple of
rounds of testing before he got it right and was able to put it up on
experimental.

As far as 'not getting immediately my way'  the immediacy would have
been if I had filed a bug yesterday and bugged today, then your
statement would have been valid.

But couple of years is not immediate as Axel shared in the bug, if
memory serves me right, this was around October/November 2016
thereish.

> Best wishes,
>
> --
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-
>

-- 
  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 शिरीष 
Date: Thu, 15 Jun 2017 22:23:50 +0530
Subject: debian stretch being released without fixing wpagui and wpasupplicant ?
To: debian-release 

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

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

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

at bottom :-

On 17/06/2017, gregor herrmann  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

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

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

at bottom :-

On 17/06/2017, gregor herrmann  wrote:
> On Sat, 17 Jun 2017 07:44:17 +0530, shirish शिरीष wrote:
>
>> On 17/06/2017, gregor herrmann  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 & SPI, fellow o

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

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

at bottom :-

On 17/06/2017, gregor herrmann  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: IMPORTANT: Do live Debian images have a future?

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

at bottom :-

On 26/06/2017, Steve McIntyre  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: IMPORTANT: Do live Debian images have a future?

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

at bottom :-

On 12/07/2017, Fernando Toledo  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

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

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

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

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.

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

at bottom :-

On 27/08/2017, Dominique Dumont  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

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.