Package: wnpp
Severity: wishlist
Owner: Neil Williams
* Package name: black
Version : 18.6b4
Upstream Author : Łukasz Langa
* URL : https://github.com/ambv/black
* License : BSD-3-Clause
Programming Lang: Python
Description : uncompromising Python code
Hi,
On 25/09/18 05:35, Antoine Beaupré wrote:
> I tried to figure out what the other package does:
It uses the DuckDuckGo instant answers API to give an instant answer on
the command line as a more human friendly version of the ddg command
which is machine-readable but contains more information.
On Mon, 24 Sep 2018 14:57:52 +0100, Jonathan Dowland
wrote:
>+1 from me. Epochs are not only painful for maintainers, they are
>confusing for users too.
Why do we have them then, and why do we keep tightening up Policy in a
way that we'd better write "don't use epochs, they're evil"?
Greetings
M
Package: wnpp
Severity: wishlist
Owner: la...@debian.org
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: opensnitch
Version : 0~git20180913+e9c10b9-1
Upstream Author : Simone "evilsocket" Margaritelli
* URL : https://opensnitch.io/
* License : GPL-3
On 2018-09-25 10:45:07, Iain Learmonth wrote:
> Hi,
>
> On 25/09/18 05:35, Antoine Beaupré wrote:
>> I tried to figure out what the other package does:
>
> It uses the DuckDuckGo instant answers API to give an instant answer on
> the command line as a more human friendly version of the ddg command
Antoine Beaupré writes ("Re: possible conflict over the /usr/bin/ia namespace"):
> Great! I would be happy to help with that if you need any assistance.
> In the meantime, should I just upload IA to NEW? :)
You need to coordinate the transition for the /usr/bin/ia filename. I
think that means you
On 2018-09-25 13:43:42, Ian Jackson wrote:
> Antoine Beaupré writes ("Re: possible conflict over the /usr/bin/ia
> namespace"):
>> Great! I would be happy to help with that if you need any assistance.
>> In the meantime, should I just upload IA to NEW? :)
>
> You need to coordinate the transition
Hi,
On 25/09/18 14:16, Antoine Beaupré wrote:
> Conflicts: python-duckduckgo2 (<= 0.242+git20151019-1)
The upload I am currently preparing is 0.242+git20151019-2
> I'd be happy to do that upload, actually. I see the git repo used to be
> on Alioth:
>
> https://alioth-archive.debian.org/git/coll
Antoine Beaupré writes ("Re: possible conflict over the /usr/bin/ia namespace"):
> Makes sense. How about:
>
> Conflicts: python-duckduckgo2 (<= 0.242+git20151019-1)
>
> This way we assume any newer upload of the package will remove ia?
That's not a good choice because it excludes (local) backpo
On Tue, Sep 25, 2018 at 09:16:44AM -0400, Antoine Beaupré wrote:
> On 2018-09-25 13:43:42, Ian Jackson wrote:
> > You need to coordinate the transition for the /usr/bin/ia filename. I
> > think that means your new internet-archive package should probably
> > Conflict: python-duckduckgo2 (<< vers
Iain Learmonth writes ("Re: possible conflict over the /usr/bin/ia namespace"):
> On 25/09/18 14:16, Antoine Beaupré wrote:
> > ... but it hasn't been migrated to Salsa. Would you be okay to move this
> > in the Python module's team umbrella (as opposed to simply collab-maint)?
>
> The whole salsa
On 2018-09-25 14:22:44, Ian Jackson wrote:
> Antoine Beaupré writes ("Re: possible conflict over the /usr/bin/ia
> namespace"):
>> Makes sense. How about:
>>
>> Conflicts: python-duckduckgo2 (<= 0.242+git20151019-1)
>>
>> This way we assume any newer upload of the package will remove ia?
>
> Tha
Antoine Beaupré writes ("Re: possible conflict over the /usr/bin/ia namespace"):
> On 2018-09-25 14:22:44, Ian Jackson wrote:
> > If you can't get a better idea I would suggest
> > << 0.242+git20151019-1.1~
> > which is all versions until the next draft(~)-of-an-nmu (.1).
>
> But wouldn't <= 0.2
Ian Jackson writes ("Re: possible conflict over the /usr/bin/ia namespace"):
> Antoine Beaupré writes ("Re: possible conflict over the /usr/bin/ia
> namespace"):
> > On 2018-09-25 14:22:44, Ian Jackson wrote:
> > > If you can't get a better idea I would suggest
> > > << 0.242+git20151019-1.1~
>
On 2018-09-25 14:25:25, Ian Jackson wrote:
> Iain Learmonth writes ("Re: possible conflict over the /usr/bin/ia
> namespace"):
>> On 25/09/18 14:16, Antoine Beaupré wrote:
>> > ... but it hasn't been migrated to Salsa. Would you be okay to move this
>> > in the Python module's team umbrella (as op
(dropping the bug)
Antoine Beaupré writes ("Re: possible conflict over the /usr/bin/ia namespace"):
> On 2018-09-25 14:25:25, Ian Jackson wrote:
> > For packages maintained by very small (or unitary) teams with limited
> > collaboration, ad-hoc sharing via personal git repos works OK. And of
> >
On 2018-09-25 14:33:44, Ian Jackson wrote:
> Antoine Beaupré writes ("Re: possible conflict over the /usr/bin/ia
> namespace"):
>> On 2018-09-25 14:22:44, Ian Jackson wrote:
>> > If you can't get a better idea I would suggest
>> > << 0.242+git20151019-1.1~
>> > which is all versions until the ne
Hello,
On Mon 24 Sep 2018 at 07:19PM +0200, Christoph Biedl wrote:
> For me this concern is about asking upstream for a change that is caused
> by something more or less Debian-internal - although other distributions
> might have that issue as well. So it should rather be handled inside
> Debian.
hi ftp-master,
Sorry for the noise, but I really care about the package src:julia. And
I started to suspect that ftp-master failed to recieve my last feedback
on the rejection. So I'm re-sending the feedback again, and CCing
-devel to make sure the mail won't get lost.
As of 1.0.0-3 (NEW), this p
Hi Lumin,
On Tue, Sep 25, 2018 at 02:40:43PM +, Lumin wrote:
> > What I'm emphasizing here is, the debug info in those shared objects
> > are intensionally kept to preserve a good user experience and
> > avoid increasing maintainance burden.
> >
> > This is the expected backtrace from the cod
Package: wnpp
Severity: wishlist
Owner: Emmanuel Bourg
* Package name: eclipse-platform-debug
Version : 4.7.3
Upstream Author : Eclipse Foundation, Inc.
* URL : https://www.eclipse.org/eclipse/debug/
* License : EPL-1.0
Programming Lang: Java
Description
Hi Lumin
On Tue, Sep 25, 2018 at 02:40:43PM +, Lumin wrote:
> 1. Isn't "incomplete backtrace" a sensible reason to keep debug symbols?
>Policy said "should" but not "must". Please tell me what I can do in
>order to help improve the src:julia package to satisfy the requirements?
The ju
t system cannot interpret (such as ``ALPHA`` or ``pre-``), or
with silly orderings.
I think the canonical example is a package that was using version numbers
like 20180925 and then switches to semver 1.0 versions. (Policy
recommends always using 0.0.20180925 as the version for packages ver
There are few reasons why I believe upgrade does not bring in entirely new
packages by default when dependencies are changed.
1. The man page of apt-get says the following
upgrade
upgrade is used to install the newest versions of all packages
currently installed on the syst
"Devarajulu, Mohanasundaram" writes:
> There are few reasons why I believe upgrade does not bring in entirely
> new packages by default when dependencies are changed.
IIRC there's a difference here between "apt-get upgrade" and "apt
upgrade". The latter is equivalent to "apt-get --with-new-pkgs
Hallo everyone,
The yesteday uploaded Developer's Reference has now got a chapter
about "Package Salvaging". [1]
So, package salvaging is now implemented and ready to be used,
and whenever you find some package in need, you can now consider to
salvage it for the benefit of Debian and our users.
26 matches
Mail list logo
