Package: wnpp
Severity: wishlist
Owner: Dmitry Smirnov
X-Debbugs-CC: debian-devel@lists.debian.org,
pkg-go-maintain...@lists.alioth.debian.org
Package name: mockery
Version: 0.0~git20181123
Upstream Author: Opinionated Architecture
License: BSD-3-clause
URL: https:
On 2019, സെപ്റ്റംബർ 13 1:06:13 AM IST, Marc Haber
wrote:
>alioth.debian.org, anyone? That one went away pretty fast.
I wonder why people keep repeating this. This was migrated to salsa and also
archived, so nothing was lost. This was a planned move to a better solution
(gforge was unmaintai
On Thu, 2019-09-12 at 15:37:49 +0100, Ian Jackson wrote:
> Ansgar writes ("Re: Git Packaging Round 2: When to Salsa"):
> > (Using dgit to upload packages is sadly incompatible with best
> > practices around packaging.)
>
> Using dgit to upload packages is best practice.
I'm sorry, but "best pract
// send from my mobile device
Jeremy Stanley 于 2019年9月13日周五 06:51写道：
> On 2019-09-12 22:27:39 +0200 (+0200), Simon Richter wrote:
> [...]
> > The idea for resilience is "too big to block".
> >
> > When Domain Fronting still worked with Google, people used this to
> > circumvent censorship becaus
The following is a listing of packages for which help has been requested
through the WNPP (Work-Needing and Prospective Packages) system in the
last week.
Total number of orphaned packages: 1307 (new: 2)
Total number of packages offered up for adoption: 153 (new: 0)
Total number of packages reques
On 2019-09-12 22:27:39 +0200 (+0200), Simon Richter wrote:
[...]
> The idea for resilience is "too big to block".
>
> When Domain Fronting still worked with Google, people used this to
> circumvent censorship because blocking it would have required
> blocking Google, so cooperation from Google was
On Thu, Sep 12, 2019 at 11:43:33PM +0200, Marco d'Itri wrote:
> On Sep 12, Wouter Verhelst wrote:
>
> > Except all they need to do is return NXDOMAIN on the
> > "use-application-dns.net" domain, and Presto! they can spy on their
> > users again.
> They need to have a government to compel then to
Package: wnpp
Severity: wishlist
Owner: Bastien Roucariès
Package name: node-es-to-primitive
Version : 1.2.0
Upstream Author : Jodan Harband
URL : https://github.com/ljharb/es-to-primitive/
License : expat
Programming Lang: javascript
Description
On Sep 12, Wouter Verhelst wrote:
> Except all they need to do is return NXDOMAIN on the
> "use-application-dns.net" domain, and Presto! they can spy on their
> users again.
They need to have a government to compel then to do it, which is not
obvious. And then Mozilla will disable that (you can
On Thu, Sep 12, 2019 at 07:02:15PM +0200, Jeff wrote:
> The package I uploaded yesterday failed to build[1]. In the buildd, 2 of
> 1000+ tests failed. Of course, I built in a clean sbuild for sid before
> I uploaded it, and the same package built fine on the newer Ubuntu
> distros on launchpad. So
On Tue, Sep 10, 2019 at 07:56:48PM +0200, Julien Cristau wrote:
> On Tue, Sep 10, 2019 at 08:24:03 +0200, Ondřej Surý wrote:
>
> > > On 9 Sep 2019, at 15:31, Bjørn Mork wrote:
> > >
> > > I for one, do trust my ISPs a lot more than I trust Cloudflare or
> > > Google, simply based on the jurisdic
On Sun, Sep 08, 2019 at 11:17:13PM +0200, Marco d'Itri wrote:
> On Sep 08, Ondřej Surý wrote:
>
> > I would rather see an explicit statement. I would be very surprised
> > with Debian’s usual stance regarding the users’ privacy that we would
> > not consider this as a privacy violation, but aga
Hi,
On Thu, Sep 12, 2019 at 06:52:47PM +0200, Adam Borowski wrote:
> > I still believe that generic users are better served by deploying more
> > censorship-resistant protocols than by worrying that Cloudflare (or
> > whoever else) would violate the privacy requirements mandated by
> > Mozilla
Le September 12, 2019 4:52:47 PM UTC, Adam Borowski a
écrit :
>On Tue, Sep 10, 2019 at 07:46:57PM +0200, Marco d'Itri wrote:
>> On Sep 09, Adam Borowski wrote:
>>
>> > With DoH:
>> > * the target server knows about you (duh!)
>> > * the ISP can read the destination of every connection
>> > [r
On 12/09/2019 19:08, Adam D. Barratt wrote:
> If you're a DD, then you can use the service described in
> https://debblog.philkern.de/2019/08/alpha-self-service-buildd-givebacks.html
Thanks to those who replied so quickly. The instructions worked a treat.
Regards
Jeff
signature.asc
Descripti
On Sun, 08 Sep 2019 22:05:17 -0700, Russ Allbery
wrote:
>Sean Whitton writes:
>> On Sun 08 Sep 2019 at 05:35PM -04, Sam Hartman wrote:
>
>>> You are encouraged to mirror your repository to Salsa so that people can
>>> find more of the Debian packaging in one place.
>
>> Hmm, if the Vcs-* are set
On Sun, 08 Sep 2019 17:35:10 -0400, Sam Hartman
wrote:
>* Use a public repository where in-progress and ongoing work are
> available to the public. Do not just push when you release.
I would liket to have a recommendation about git push --force in that
case. I frequently do rebase --interactive
On Thu, Sep 12, 2019 at 09:30:09AM -0700, Mo Zhou wrote:
> How should Debian react if someone submitted an ITP for python2
> forks, such as the tauthon above?
"Go ahead but don't interfere with other packages, including the Python 3
interpreter and the Python 3 modules, and we won't maintain tautho
What? How did you manage to go from me suggesting disabling DoH by default to
CloudFlare in Firefox without explicit user consent to an attack on ICANN?
But I guess that this alternative DNS root nonsense will just never die, so I
should not be really surprised.
--
Ondřej Surý
> On 12 Sep 201
Then you should ask why we have ICANN in the first place!
PS: https://en.wikipedia.org/wiki/OpenNIC
On Sun, Sep 8, 2019 at 11:01 PM Ondřej Surý wrote:
>
> Hi,
>
> I haven’t found any discussion on the topic (although I haven’t searched very
> hard and only looked for DoH and DNS keywords in the
On Thu, Sep 12, 2019 at 06:26:34PM +0200, Marc Haber wrote:
> Will DOH break corporate web apps that are accessed over a VPN (and
> thus only resolvable via the local resolver)? Or has Mozilla catered
> for that?
Please see https://wiki.mozilla.org/Trusted_Recursive_Resolver.
network.trr.mode=2 se
On 2019-09-12 Jeff wrote:
> The package I uploaded yesterday failed to build[1]. In the buildd, 2 of
> 1000+ tests failed. Of course, I built in a clean sbuild for sid before
> I uploaded it, and the same package built fine on the newer Ubuntu
> distros on launchpad. So I'm hoping it was just a gl
Hello,
Jeff, le jeu. 12 sept. 2019 19:02:15 +0200, a ecrit:
> How can I give back the build?
Please read the Misc Developer News on d-d-a :)
https://lists.debian.org/debian-devel-announce/2019/08/msg3.html
Samuel
On Thu, 2019-09-12 at 19:02 +0200, Jeff wrote:
> The package I uploaded yesterday failed to build[1]. In the buildd, 2
> of 1000+ tests failed. Of course, I built in a clean sbuild for sid
> before I uploaded it, and the same package built fine on the newer
> Ubuntu distros on launchpad. So I'm hop
Adam Borowski writes:
> On Tue, Sep 10, 2019 at 07:46:57PM +0200, Marco d'Itri wrote:
>> Well, no. They cannot without significantly more expensive hardware to
>> do DPI and a *totally different* legislative framework.
>> (Source: I have been dealing with government-mandated censorship in
>> Ital
The package I uploaded yesterday failed to build[1]. In the buildd, 2 of
1000+ tests failed. Of course, I built in a clean sbuild for sid before
I uploaded it, and the same package built fine on the newer Ubuntu
distros on launchpad. So I'm hoping it was just a glitch, and I'd like
to retry the bui
On Tue, Sep 10, 2019 at 07:46:57PM +0200, Marco d'Itri wrote:
> On Sep 09, Adam Borowski wrote:
>
> > With DoH:
> > * the target server knows about you (duh!)
> > * the ISP can read the destination of every connection
> > [reading the IP header, reading SNI header]
> > * the ISP can block such
Sam Hartman writes ("Re: Git Packaging Round 2: SHOULD Not or MUSt NOT Github"):
> Ian Jackson writes:
>
> > Sam Hartman writes ("Re: Git Packaging Round 2: SHOULD Not or
> > MUSt NOT Github"):
> >> Unfortunately, I believe you are in the [wrong] when judging
>
> Ian placed the word "wrong" in m
> "Ian" == Ian Jackson writes:
Ian> Sam Hartman writes ("Re: Git Packaging Round 2: SHOULD Not or
Ian> MUSt NOT Github"):
>> Unfortunately, I believe you are in the [wrong] when judging
Ian placed the word "wrong" in my mouth replacing the word "rough" from
my original mail. I d
On Thu, 12 Sep 2019 08:47:49 -0400
Sam Hartman wrote:
> That said, I'm really confused that your message didn't get any
> response before now. Considering how sharp some of the responses
> were on -project, I don't know how to take this. Were people not
> responding because the -project discussi
On 2019-09-12 16:22, Marco d'Itri wrote:
> On Sep 12, Alf Gaida wrote:
>
>> It doesn't really matter. In fact python2 is dead for years, if we
>> start now to make a plan we are years to late. The timeframe is _now:.
> Dead for who? As long as somebody will be interested in maintaining
> python2
On Mon, 9 Sep 2019 00:38:03 +0200, Adam Borowski
wrote:
>With local DNS:
>* the target server knows about you (duh!)
>* the ISP can read the destination of every connection
> [reading the DNS packets, reading the IP header, reading SNI header]
>* the ISP can block such connections
> [blocking DN
On Sep 12, Alf Gaida wrote:
> It doesn't really matter. In fact python2 is dead for years, if we
> start now to make a plan we are years to late. The timeframe is _now:.
Dead for who? As long as somebody will be interested in maintaining
python2 it will not be dead.
I maintain some packages whic
Hi,
On 12-09-2019 17:01, Ian Jackson wrote:
> But we need to be clear what's going on and communicate early.
Yes, not on the front page, but there is (first bullet):
https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#deprecated-components
Paul
signature.asc
Des
On Thu, 12 Sep 2019 16:01:54 +0100
Ian Jackson wrote:
> That statement is a *pledge* to drop support for python2 by the end of
> 2020. Have we in fact made such a pledge ? I think I may have missed
> the memo that python2 would be removed from bullseye.
>
""He's dead, Jim" (Doctor Leonard McCo
On 12.09.19 17:01, Ian Jackson wrote:
Drew Parsons writes ("should Debian add itself to https://python3statement.org
?"):
https://python3statement.org/ is a site documenting the projects which
are supporting the policy of dropping Python2 to keep Python3 only.
That statement is a *pledge* to
Hi Drew,
https://release.debian.org/transitions/html/python2-rm.html
Given the current progress it looks not easy to make a promise.
If some upstream happen to lag behind the schedule of python3
migration, we'll just stuck there for a while.
On 2019-09-12 14:46, Drew Parsons wrote:
> https://pyt
Package: wnpp
Owner: Gianfranco Costamagna
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: sphinxcontrib-svg2pdfconverter
Version : 0.1.0
Upstream Author : 2018-2019 by Missing Link Electronics, 2018-2019 by Stefan
Wiehler
* URL : https
On Thu, 2019-09-12 at 16:14 +0100, Ian Jackson wrote:
> Jim Popovitch writes ("Re: should Debian add itself to
> https://python3statement.org ?"):
> > On Thu, 2019-09-12 at 16:01 +0100, Ian Jackson wrote:
> > > Drew Parsons writes ("should Debian add itself to
> > > https://python3statement.org
Jim Popovitch writes ("Re: should Debian add itself to
https://python3statement.org ?"):
> On Thu, 2019-09-12 at 16:01 +0100, Ian Jackson wrote:
> > Drew Parsons writes ("should Debian add itself to
> > https://python3statement.org ?"):
> > > https://python3statement.org/ is a site documenting
On Thu, 2019-09-12 at 16:01 +0100, Ian Jackson wrote:
> Drew Parsons writes ("should Debian add itself to
> https://python3statement.org ?"):
> > https://python3statement.org/ is a site documenting the projects which
> > are supporting the policy of dropping Python2 to keep Python3 only.
>
> Th
Drew Parsons writes ("should Debian add itself to https://python3statement.org
?"):
> https://python3statement.org/ is a site documenting the projects which
> are supporting the policy of dropping Python2 to keep Python3 only.
That statement is a *pledge* to drop support for python2 by the end
Enrico Zini writes ("Re: Git Packaging Round 2: SHOULD Not or MUSt NOT Github"):
> On Thu, Sep 12, 2019 at 02:07:52PM +0100, Ian Jackson wrote:
> > I think this does not demonstrate that I am wrong about project's
> > overall opinion about this. I am confident that a GR to forbid this
> > would su
https://python3statement.org/ is a site documenting the projects which
are supporting the policy of dropping Python2 to keep Python3 only.
The site is designed for python packages specifically, to have only
Python3 supported by end of 2020.
But it seems to me it would be in the spirit of the
Ansgar writes ("Re: Git Packaging Round 2: When to Salsa"):
> If dgit provides a program to figure this out, people interested in
> obtaining the information automatically can just extract and use that.
It is not possible to figure out the branch format automatically
given just the maintainer bra
On Thu, Sep 12, 2019 at 02:07:52PM +0100, Ian Jackson wrote:
> I think this does not demonstrate that I am wrong about project's
> overall opinion about this. I am confident that a GR to forbid this
> would succeed.
For what is worth, I would vote against such a GR.
I'm extremely uncomfortable
Sam Hartman writes:
>> "Ansgar" == Ansgar writes:
>
> Ansgar> On Thu, 2019-09-12 at 08:14 -0400, Sam Hartman wrote:
> Ian> 1. The maintainer's git repository branch format must be
> Ian> documented. Otherwise another contributor has to guess. This
> Ian> could be done eith
> "Ansgar" == Ansgar writes:
Ansgar> On Thu, 2019-09-12 at 08:14 -0400, Sam Hartman wrote:
Ian> 1. The maintainer's git repository branch format must be
Ian> documented. Otherwise another contributor has to guess. This
Ian> could be done either by doing maintainer uploads w
Sam Hartman writes ("Re: Git Packaging Round 2: SHOULD Not or MUSt NOT Github"):
> Unfortunately, I believe you are in the [wrong] when judging rough
> consensus on this issue.
>
> This was discussed fairly recently on debian-project; my take is that
> Thomas Goirand represented a position roughly
On Thu, 2019-09-12 at 08:14 -0400, Sam Hartman wrote:
> Ian> 1. The maintainer's git repository branch format must be
> Ian> documented. Otherwise another contributor has to guess. This
> Ian> could be done either by doing maintainer uploads with dgit
> Ian> (since recent versions
> "Ian" == Ian Jackson writes:
Ian> No-one should be asked to interact with a non-free service, as
Ian> part of contributing to Debian.
Ian> Note I say "no-one should be asked". It is not enough, for me,
Ian> for there to be a "plan (b)" route. Ie, it is not OK for a
I
Sam Hartman writes:
>
> I did do a bit of looking at data.
> In my unstable sources.list, there are 17863 source packages that
> include salsa.debian.org in the vcs-git. Of those, 2192 are in the
> debian group.
> That's the largestsingle group; perl-team (next) comes in at 1417.
>
> The debian g
> "Ian" == Ian Jackson writes:
Ian> Sam Hartman writes ("Git Packaging Round 2: When to Salsa"):
>> Discussion Comments ---
Ian> ...
>> I realize that not everyone wants all developers to have push
>> access to their packages. If you have a firm idea about
53 matches
Mail list logo
