On 15/12/2018 08:41, Chris Lamb wrote:
> [Adding ftpmas...@debian.org to CC]
>
> Hi Antoine et al.,
>
>> So anyways - irl will upload a new package now, presumably -2 or more,
>> so i think << 0.242+git20151019-2~ is fine.
>
> I just went to process this package in NEW but this new upload does
On 2018-12-15 22:25:58, Chris Lamb wrote:
> Antoine Beaupré wrote:
>
>> >From what I can tell, both were:
>>
>> https://tracker.debian.org/news/989684/accepted-python-duckduckgo2-0242git20151019-2-source-amd64-into-unstable/
>
> Neat, thanks. I've just processed python-internetarchive 1.8.1-1 in
Antoine Beaupré wrote:
> >From what I can tell, both were:
>
> https://tracker.debian.org/news/989684/accepted-python-duckduckgo2-0242git20151019-2-source-amd64-into-unstable/
Neat, thanks. I've just processed python-internetarchive 1.8.1-1 in
NEW.
Regards,
--
,''`.
: :' :
On 2018-12-15 09:41:50, Chris Lamb wrote:
> [Adding ftpmas...@debian.org to CC]
>
> Hi Antoine et al.,
>
>> So anyways - irl will upload a new package now, presumably -2 or more,
>> so i think << 0.242+git20151019-2~ is fine.
>
> I just went to process this package in NEW but this new upload does
[Adding ftpmas...@debian.org to CC]
Hi Antoine et al.,
> So anyways - irl will upload a new package now, presumably -2 or more,
> so i think << 0.242+git20151019-2~ is fine.
I just went to process this package in NEW but this new upload does
not appear to have happened yet. Is that correct?
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
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
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 <=
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: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?
>
>
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
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 (<<
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:
>
>
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)
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
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
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
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.
Hi,
TL;DR: new package from archive.org conflicts with existing `ia`
binary from python-duckduckgo2. Policy §10.1 consensus sought.
I'm in the process of packaging the Internet Archive (archive.org)
Python commandline client and that installs a client that is
conveniently called "ia" in
19 matches
Mail list logo
