Debian Bug report logs - #909550
ITP: internetarchive -- python interface to archive.org

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: ITP: internetarchive -- python interface to archive.org

Date: Mon, 24 Sep 2018 23:14:16 -0400

[Message part 1 (text/plain, inline)]

Package: wnpp
Severity: wishlist
Owner: Antoine Beaupré <anarcat@debian.org>
X-Debbugs-CC: debian-python@lists.debian.org

* Package name    : internetarchive
  Version         : 1.8.1
  Upstream Author : Jacob M. Johnson <jake@archive.org>
* URL             : https://github.com/jjjake/internetarchive
* License         : AGPL 3
  Programming Lang: Python
  Description     : python interface to archive.org

Command-line tool (`ia`) and Python library for searching, downloading
and uploading content to the Internet Archive.

--

Binary package names: python3-internetarchive python-internetarchive internetarchive

Unsure about those package names: I wonder if the libraries should be
separate from the main binary, although the latter is really just a
wrapper for the former.

Upstream documentation is available at:

https://archive.org/services/docs/api/internetarchive/

I've tested the package as installed by pip and it seems to work well.
py2dsp seems to work as well and was used to generate this email.

Can (should?) be maintained under the PAPT (or DPMT?) umbrella.

[signature.asc (application/pgp-signature, inline)]

Message #10 received at 909550@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: 909550@bugs.debian.org

Subject: Re: ITP: internetarchive -- python interface to archive.org)

Date: Tue, 25 Sep 2018 00:06:01 -0400

Control: tags -1 +pending +patch

Progress on this package:

 * the debianized source is here:

   https://salsa.debian.org/python-team/modules/python-internetarchive

 * tests are disabled because they fail as the `ia` binary is missing
   after build (but not, presumably, install)

 * similarly, the Py2 build is disabled because it requires
   backports.csv which is not in Debian at the time of writing

 * the upstream doc is also not built in a -doc package - that can be
   added later. this means no manpage is available for the `ia` command,
   but that should be okay as our package name is
   "python3-internetarchive", ie. we behave as a library and the `ia`
   command is auxiliary (even though the latter is what I use the most).

I'm still unsure about the binary package name: it would be pretty cool
to call this binary `ia` since it does provide this awesome commandline
tool. Unfortunately, that namespace is claimed by the python-duckduckgo2
package, which we conflict with.

I'll sit on this a little longer then upload as it seems pretty complete.

A.

-- 
Les plus beaux chants sont les chants de revendications
Le vers doit faire l'amour dans la tête des populations.
À l'école de la poésie, on n'apprend pas: on se bat!
                        - Léo Ferré, "Préface"

Message #19 received at 909550@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: debian-devel@lists.debian.org

Cc: irl@debian.org, 909550@bugs.debian.org

Subject: possible conflict over the /usr/bin/ia namespace

Date: Tue, 25 Sep 2018 00:35:45 -0400

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 /usr/bin. It's a simple wrapper around a
more elaborate Python library, but it allows a fairly complete set of
operations of the archive like searching, downloading, uploading and
deleting data.

Unfortunately, apt-file (is there a better way?) tells me that
python-duckduckgo2 already claimed that command namespace, along with
the ddg command, naturally.

I tried to figure out what the other package does: there's no
documentation in the Debian package, and neither command supports has
inline help or manpages. From what I can tell, the `ddg` command output
structured data from a DDG (DuckDuckGo.com) search and `ia` command does
a "feel lucky" type of request to output only one answer. This seems to
be somewhat related "Instant Answers" API (hence the `ia` acronym)
as defined here:

https://duckduckgo.com/api

So the situation falls directly under section 10.1 of the Policy:

https://www.debian.org/doc/debian-policy/ch-files.html#s-binaries

> Two different packages must not install programs with different
> functionality but with the same filenames.

The solution proposed by the policy is to rename one or both of the
packages, after a discussion here:

> [...] try to find a consensus about which program will have to be
> renamed. If a consensus cannot be reached, both programs must be
> renamed.

Obviously, DDG has the upper hand right now: it's already passed new and
is in the archive. My "internetarchive" package is only at the ITP stage
(in CC) but it's fairly complete and would be ready for upload. Right
now it Conflicts with the DDG package, but that's not the best solution
- I would need to rename the commandline binary to respect policy, if I
understand it correctly. But before doing that, I want to give the
Internet Archive a chance.

As an argument for the archive, I would say its acronym is more commonly
known and used than DDG's, which I found out for the first time here and
never heard about before. Wikipedia agrees; in this disambiguiation
page, DDG is not listed at the time of writing, while the Archive is:

https://en.wikipedia.org/wiki/IA

The "snap" package `ia` also points to the archive's software:

https://snapcraft.io/ia

Same for FreeBSD and, as far as I can tell, Arch Linux.

I would therefore propose for the python-duckduckgo2 ia binary to be
renamed to ddg-ia, as its "ia" use is only secondary in the package's
purpose.

The alternative course of action would be to rename the ia binary in the
internetarchive package to "internetarchive" but that's rather long and
unusual: all upstream documentation refers to the `ia` binary and this
could confuse our users needlessly, especially since other platforms
also use the `ia` acronym to refer to the archive as well.

The source of the package is available here:

https://salsa.debian.org/python-team/modules/python-internetarchive

Progress in the packaging can be followed in the CC'd bug report.

With good faith and spirit, sorry for the long email and thanks for any
feedback!

A,

PS: there is, incidentally, also the question of how to name this
(source and binary!) package: python3-internetarchive, internetarchive
and ia would all be interesting names for various reasons. I would
prefer the latter, but it would obviously require the DDG side to rename
first to make any sense. The Debian Python policy on this is, as far as
I know, rather undecided right now, especially for packages like
internetarchive that mix libraries and commandline tools.

-- 
I'm no longer accepting the things I cannot change.
I'm changing the things I cannot accept.
                        - Angela Davis

Message #24 received at 909550@bugs.debian.org (full text, mbox, reply):

From: Iain Learmonth <irl@debian.org>

To: Antoine Beaupré <anarcat@debian.org>, debian-devel@lists.debian.org

Cc: 909550@bugs.debian.org

Subject: Re: possible conflict over the /usr/bin/ia namespace

Date: Tue, 25 Sep 2018 10:45:07 +0100

[Message part 1 (text/plain, inline)]

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.

popcon reports 7 old and 0 recent.

The ia script was added in a patch and never actually present upstream:

https://sources.debian.org/src/python-duckduckgo2/0.242+git20151019-1/debian/patches/0001-add-ia-script.patch/

I was using this as part of an IRC bot but I now just call Python directly.

The easiest solution here is probably that I drop that script. It was
never accepted upstream anyway, nor have there been any updates upstream
since 2015.

Thanks,
Iain.

[signature.asc (application/pgp-signature, attachment)]

Message #29 received at 909550@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Iain Learmonth <irl@debian.org>, debian-devel@lists.debian.org

Cc: 909550@bugs.debian.org

Subject: Re: possible conflict over the /usr/bin/ia namespace

Date: Tue, 25 Sep 2018 08:29:27 -0400

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
> which is machine-readable but contains more information.
>
> popcon reports 7 old and 0 recent.
>
> The ia script was added in a patch and never actually present upstream:
>
> https://sources.debian.org/src/python-duckduckgo2/0.242+git20151019-1/debian/patches/0001-add-ia-script.patch/
>
> I was using this as part of an IRC bot but I now just call Python directly.
>
> The easiest solution here is probably that I drop that script. It was
> never accepted upstream anyway, nor have there been any updates upstream
> since 2015.

Great! I would be happy to help with that if you need any assistance.

In the meantime, should I just upload IA to NEW? :)

A.

-- 
To punish me for my contempt for authority, fate made me an authority myself.
                       - Albert Einstein

Message #34 received at 909550@bugs.debian.org (full text, mbox, reply):

From: Ian Jackson <ijackson@chiark.greenend.org.uk>

To: Antoine Beaupré <anarcat@debian.org>

Cc: Iain Learmonth <irl@debian.org>, debian-devel@lists.debian.org, 909550@bugs.debian.org

Subject: Re: possible conflict over the /usr/bin/ia namespace

Date: Tue, 25 Sep 2018 13:43:42 +0100

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 your new internet-archive package should probably
  Conflict: python-duckduckgo2 (<< version-without-ia~)

That can probably be uploaded before the new python-duckduckgo2 but
the relevant version number should be agreed.  And if you do upload
internet-archive before python-duckduckgo2 is changed there there
should probably be a bug against python-duckduckgo2.  I guess that bug
doesn't need to be rc ?

Ian.

-- 
Ian Jackson <ijackson@chiark.greenend.org.uk>   These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Message #39 received at 909550@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Ian Jackson <ijackson@chiark.greenend.org.uk>

Cc: Iain Learmonth <irl@debian.org>, debian-devel@lists.debian.org, 909550@bugs.debian.org

Subject: Re: possible conflict over the /usr/bin/ia namespace

Date: Tue, 25 Sep 2018 09:16:44 -0400

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 for the /usr/bin/ia filename.  I
> think that means your new internet-archive package should probably
>   Conflict: python-duckduckgo2 (<< version-without-ia~)
>
> That can probably be uploaded before the new python-duckduckgo2 but
> the relevant version number should be agreed.

Makes sense. How about:

Conflicts: python-duckduckgo2 (<= 0.242+git20151019-1)

This way we assume any newer upload of the package will remove ia?

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/collab-maint/python-duckduckgo2.git.tar.xz

... 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)?

> And if you do upload internet-archive before python-duckduckgo2 is
> changed there there should probably be a bug against
> python-duckduckgo2.

Sure, I'll file that anyways now.

> I guess that bug doesn't need to be rc ?

Yeah, that's not RC material, as long as the bug is not forgotten in the
next upload of course. :)

A.

-- 
Instead of worrying about what somebody else is going to do, which is
not under your control, the important thing is, what are you going to
decide about what is under your control?
                         - Richard Stallman

Message #44 received at 909550@bugs.debian.org (full text, mbox, reply):

From: Iain Learmonth <irl@debian.org>

To: Antoine Beaupré <anarcat@debian.org>, Ian Jackson <ijackson@chiark.greenend.org.uk>

Cc: debian-devel@lists.debian.org, 909550@bugs.debian.org

Subject: Re: possible conflict over the /usr/bin/ia namespace

Date: Tue, 25 Sep 2018 14:22:19 +0100

[Message part 1 (text/plain, inline)]

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/collab-maint/python-duckduckgo2.git.tar.xz
> 
> ... 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 thing is not something that I've been able to keep up
with. I have git repos locally and I've been moving things to salsa as
and when I do updates. You probably shouldn't trust what is on salsa
anyway unless we all start using signed commits and tags. The archive is
the only true record of packages.

I once looked at doing team maintenance on these packages but there was
enough extra policy regarding that team management that I did not have
the time to look at it. If you would like to adopt the package and move
it into the team then that's fine with me. I am also on the list of "low
nmu" maintainers. I am not interested in maintaining the package within
the team myself though.

>> And if you do upload internet-archive before python-duckduckgo2 is
>> changed there there should probably be a bug against
>> python-duckduckgo2.
> 
> Sure, I'll file that anyways now.

Ok, I will close that in approx 15 minutes. (:

Thanks,
Iain.

[signature.asc (application/pgp-signature, attachment)]

Message #49 received at 909550@bugs.debian.org (full text, mbox, reply):

From: Ian Jackson <ijackson@chiark.greenend.org.uk>

To: Antoine Beaupré <anarcat@debian.org>

Cc: Iain Learmonth <irl@debian.org>, debian-devel@lists.debian.org, 909550@bugs.debian.org

Subject: Re: possible conflict over the /usr/bin/ia namespace

Date: Tue, 25 Sep 2018 14:22:44 +0100

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) backports,
security updates, etc., which tend to add +something to versions.
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).

Ian.

Message #54 received at 909550@bugs.debian.org (full text, mbox, reply):

From: Adam Borowski <kilobyte@angband.pl>

To: debian-devel@lists.debian.org, 909550@bugs.debian.org

Subject: Re: possible conflict over the /usr/bin/ia namespace

Date: Tue, 25 Sep 2018 15:24:19 +0200

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 (<< version-without-ia~)
> >
> > That can probably be uploaded before the new python-duckduckgo2 but
> > the relevant version number should be agreed.
> 
> 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'd put a requirement on security updates -- and a program that talks to
untrusted remote servers is at risk of requiring such an update.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 10 people enter a bar:
⣾⠁⢰⠒⠀⣿⡁ • 1 who understands binary,
⢿⡄⠘⠷⠚⠋⠀ • 1 who doesn't,
⠈⠳⣄⠀⠀⠀⠀ • and E who prefer to write it as hex.

Message #59 received at 909550@bugs.debian.org (full text, mbox, reply):

From: Ian Jackson <ijackson@chiark.greenend.org.uk>

To: Iain Learmonth <irl@debian.org>

Cc: Antoine Beaupré <anarcat@debian.org>, debian-devel@lists.debian.org, 909550@bugs.debian.org

Subject: Re: possible conflict over the /usr/bin/ia namespace

Date: Tue, 25 Sep 2018 14:25:25 +0100

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 thing is not something that I've been able to keep up
> with. I have git repos locally and I've been moving things to salsa as
> and when I do updates. You probably shouldn't trust what is on salsa
> anyway unless we all start using signed commits and tags. The archive is
> the only true record of packages.

For packages maintained by very small (or unitary) teams with limited
collaboration, ad-hoc sharing via personal git repos works OK.  And of
course you can share your git branch more formally with everyone,
in step with the archive, and with reasonable security, by using `dgit
push'.

> Ok, I will close that in approx 15 minutes. (:

Yay :-).  Please use dgit push, so that you share your
actually-uploaded git branch as well as just the package.

Thanks,
Ian.
(back onto the dgit plug hobby-horse)

Message #64 received at 909550@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Ian Jackson <ijackson@chiark.greenend.org.uk>

Cc: Iain Learmonth <irl@debian.org>, debian-devel@lists.debian.org, 909550@bugs.debian.org

Subject: Re: possible conflict over the /usr/bin/ia namespace

Date: Tue, 25 Sep 2018 09:29:08 -0400

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?
>
> That's not a good choice because it excludes (local) backports,
> security updates, etc., which tend to add +something to versions.
> 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.242+git20151019-1~ be as effective? Why does it need
to be <<?

-- 
La publicité est la dictature invisible de notre société.
                        - Jacques Ellul

Message #69 received at 909550@bugs.debian.org (full text, mbox, reply):

From: Ian Jackson <ijackson@chiark.greenend.org.uk>

To: Antoine Beaupré <anarcat@debian.org>

Cc: Iain Learmonth <irl@debian.org>, debian-devel@lists.debian.org, 909550@bugs.debian.org

Subject: Re: possible conflict over the /usr/bin/ia namespace

Date: Tue, 25 Sep 2018 14:33:44 +0100

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.242+git20151019-1~ be as effective? Why does it need
> to be <<?

0.242+git20151019-1 is not <= 0.242+git20151019-1~ so that is
definitely wrong.  Maybe you meant <= 0.242+git20151019-1.1~ ?
But if I were preparing an NMU I would be intending to use
0.242+git20151019-1.1 as the nmu version; and my draft packages would
be called precisely 0.242+git20151019-1.1~ and don't want to be
conflicted against.  Hence  0.242+git20151019-1.1~

This seems like arcane lore really.  Surely this stuff ought to be
documented somewhere ?

Ian.

-- 
Ian Jackson <ijackson@chiark.greenend.org.uk>   These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Message #74 received at 909550@bugs.debian.org (full text, mbox, reply):

From: Ian Jackson <ijackson@chiark.greenend.org.uk>

To: Antoine Beaupré <anarcat@debian.org>, Iain Learmonth <irl@debian.org>, debian-devel@lists.debian.org, 909550@bugs.debian.org

Subject: Re: possible conflict over the /usr/bin/ia namespace

Date: Tue, 25 Sep 2018 14:34:08 +0100

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~
> > > which is all versions until the next draft(~)-of-an-nmu (.1).
> > 
> > But wouldn't <= 0.242+git20151019-1~ be as effective? Why does it need
> > to be <<?
> 
> 0.242+git20151019-1 is not <= 0.242+git20151019-1~ so that is
> definitely wrong.  Maybe you meant <= 0.242+git20151019-1.1~ ?
> But if I were preparing an NMU I would be intending to use
> 0.242+git20151019-1.1 as the nmu version; and my draft packages would
> be called precisely 0.242+git20151019-1.1~ and don't want to be
> conflicted against.  Hence  0.242+git20151019-1.1~

I mean, hence   << 0.242+git20151019-1.1~

Ian.

Message #79 received at 909550@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Ian Jackson <ijackson@chiark.greenend.org.uk>, Iain Learmonth <irl@debian.org>

Cc: debian-devel@lists.debian.org, 909550@bugs.debian.org

Subject: Re: possible conflict over the /usr/bin/ia namespace

Date: Tue, 25 Sep 2018 09:37:30 -0400

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 opposed to simply collab-maint)?
>> 
>> The whole salsa thing is not something that I've been able to keep up
>> with. I have git repos locally and I've been moving things to salsa as
>> and when I do updates. You probably shouldn't trust what is on salsa
>> anyway unless we all start using signed commits and tags. The archive is
>> the only true record of packages.

I agree with that, for the record. Like any upload I sponsor or work on,
I review the diff before signing anyways, regardless of the source.

> For packages maintained by very small (or unitary) teams with limited
> collaboration, ad-hoc sharing via personal git repos works OK.  And of
> course you can share your git branch more formally with everyone,
> in step with the archive, and with reasonable security, by using `dgit
> push'.

I really should give dgit a try again, but I guess it's a great use case
for people allergic to salsa (pun intended) and that just need a git
repo, right? :)

>> I once looked at doing team maintenance on these packages but there was
>> enough extra policy regarding that team management that I did not have
>> the time to look at it. If you would like to adopt the package and move
>> it into the team then that's fine with me. I am also on the list of "low
>> nmu" maintainers. I am not interested in maintaining the package within
>> the team myself though.

From what I understand, the Python folks are easy: it's just a way to
get the package some visibility and help, and the overhead is
minimal. You don't have to join the team to upload.

But "collab-maint" (also known as "debian" now on Salsa) also works
fine. I don't need a new package to maintain so I'd be happy to let you
proceed with the future of this one. :)

>> Ok, I will close that in approx 15 minutes. (:

Awesome! I'll proceed with the upload of "internetarchive" (binary and
source, after consulting with #debian-python people) shortly as well.

A.

-- 
Toute mère doit être mère par choix.
Tout enfant doit être un enfant désiré.
                         - Henry Morgentaler

Message #84 received at 909550@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Ian Jackson <ijackson@chiark.greenend.org.uk>

Cc: Iain Learmonth <irl@debian.org>, debian-devel@lists.debian.org, 909550@bugs.debian.org

Subject: Re: possible conflict over the /usr/bin/ia namespace

Date: Tue, 25 Sep 2018 09:46:17 -0400

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 next draft(~)-of-an-nmu (.1).
>> 
>> But wouldn't <= 0.242+git20151019-1~ be as effective? Why does it need
>> to be <<?
>
> 0.242+git20151019-1 is not <= 0.242+git20151019-1~ so that is
> definitely wrong.  Maybe you meant <= 0.242+git20151019-1.1~ ?
> But if I were preparing an NMU I would be intending to use
> 0.242+git20151019-1.1 as the nmu version; and my draft packages would
> be called precisely 0.242+git20151019-1.1~ and don't want to be
> conflicted against.  Hence  0.242+git20151019-1.1~
>
> This seems like arcane lore really.  Surely this stuff ought to be
> documented somewhere ?

It's super weird corner cases - those are hard to document... I looked
into those places in the policy, for example, and couldn't quite figure
it out:

https://www.debian.org/doc/debian-policy/ch-relationships.html#conflicting-binary-packages-conflicts
https://www.debian.org/doc/debian-policy/ch-relationships.html#syntax-of-relationship-fields

The former does not mention any way to specify the actual version; it
probably should. The latter mentions the comparison operators but it
doesn't go into details into how to use them.

The developer's reference also does not seem to have anything about this
that I could find quickly.

So anyways - irl will upload a new package now, presumably -2 or more,
so i think << 0.242+git20151019-2~ is fine.

A.

-- 
One of the things the Web teaches us is that everything is connected
(hyperlinks) and we all should work together (standards). Too often
school teaches us that everything is separate (many different
'subjects') and that we should all work alone.  - Aaron Swartz

Message #89 received at 909550@bugs.debian.org (full text, mbox, reply):

From: Chris Lamb <lamby@debian.org>

To: Antoine Beaupré <anarcat@debian.org>, Ian Jackson <ijackson@chiark.greenend.org.uk>

Cc: Iain Learmonth <irl@debian.org>, debian-devel@lists.debian.org, 909550@bugs.debian.org, ftpmaster@debian.org

Subject: Re: possible conflict over the /usr/bin/ia namespace

Date: Sat, 15 Dec 2018 09:41:50 +0100

[Adding ftpmaster@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?


Best wishes,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org / chris-lamb.co.uk
       `-

Message #94 received at 909550@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Chris Lamb <lamby@debian.org>, 909550@bugs.debian.org, Ian Jackson <ijackson@chiark.greenend.org.uk>

Cc: Iain Learmonth <irl@debian.org>, debian-devel@lists.debian.org, 909550@bugs.debian.org, ftpmaster@debian.org

Subject: Re: Bug#909550: possible conflict over the /usr/bin/ia namespace

Date: Sat, 15 Dec 2018 09:46:20 -0500

On 2018-12-15 09:41:50, Chris Lamb wrote:
> [Adding ftpmaster@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?

You mean the NEW upload or the duckduckgo one?

From what I can tell, both were:

https://tracker.debian.org/news/989684/accepted-python-duckduckgo2-0242git20151019-2-source-amd64-into-unstable/

https://ftp-master.debian.org/new/python-internetarchive_1.8.1-1.html

Did I miss something?

Thanks for looking into this!

A.

-- 
Gods don't like people not doing much work. People who aren't busy all
the time might start to think.
                        - Terry Pratchett, Small Gods

Message #99 received at 909550@bugs.debian.org (full text, mbox, reply):

From: Chris Lamb <lamby@debian.org>

To: Antoine Beaupré <anarcat@debian.org>, 909550@bugs.debian.org, Ian Jackson <ijackson@chiark.greenend.org.uk>

Cc: Iain Learmonth <irl@debian.org>, debian-devel@lists.debian.org, ftpmaster@debian.org

Subject: Re: Bug#909550: possible conflict over the /usr/bin/ia namespace

Date: Sat, 15 Dec 2018 22:25:58 +0100

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,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org / chris-lamb.co.uk
       `-

Message #104 received at 909550-close@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: 909550-close@bugs.debian.org

Subject: Bug#909550: fixed in python-internetarchive 1.8.1-1

Date: Sat, 15 Dec 2018 22:00:13 +0000

Source: python-internetarchive
Source-Version: 1.8.1-1

We believe that the bug you reported is fixed in the latest version of
python-internetarchive, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 909550@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Antoine Beaupré <anarcat@debian.org> (supplier of updated python-internetarchive package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 25 Sep 2018 03:08:05 +0000
Source: python-internetarchive
Binary: python3-internetarchive internetarchive
Architecture: source all
Version: 1.8.1-1
Distribution: unstable
Urgency: low
Maintainer: Antoine Beaupré <anarcat@debian.org>
Changed-By: Antoine Beaupré <anarcat@debian.org>
Description:
 internetarchive - commandline interface to archive.org
 python3-internetarchive - python interface to archive.org
Closes: 909550
Changes:
 python-internetarchive (1.8.1-1) unstable; urgency=low
 .
   * Package internetarchive library for Debian (Closes: #909550)
   * Partly generated by py2dsp v2.20180318
   * Patch in proper version number which was forgotten upstream
Checksums-Sha1:
 851867aed5950d3c3f881c64dc6744c5ef3c79f1 1990 python-internetarchive_1.8.1-1.dsc
 4eb4a5fa55f57db6761cbcf769ca806023658634 116878 python-internetarchive_1.8.1.orig.tar.gz
 df77ddce34ce87ca6607e29dfd1eb44e9c5c019e 13248 python-internetarchive_1.8.1-1.debian.tar.xz
 229ac56e208590e2b71b208e668cf217808fe7ee 19816 internetarchive_1.8.1-1_all.deb
 c6569506d26f8fd57dce9ca66f32bc0743388443 7044 python-internetarchive_1.8.1-1_amd64.buildinfo
 7c90c1d48908c8a38da96968c8f4bec186137b93 55840 python3-internetarchive_1.8.1-1_all.deb
Checksums-Sha256:
 10a21447512b8d94d40b7eba398b353da0a9df8ab33acf8f7f4ecc1119ad0ea4 1990 python-internetarchive_1.8.1-1.dsc
 fe66e7290480623e8206140a1eb2a258ba1a305400413427dbb7f36f49cf3ccb 116878 python-internetarchive_1.8.1.orig.tar.gz
 74e4ecf145fda06905de62c82b39a947424d750e354f2068ffd7c09ceb1bef7a 13248 python-internetarchive_1.8.1-1.debian.tar.xz
 f787bcb486bdca88e3cb80425fd502f80215d47542c4b343439af84ab4a6b178 19816 internetarchive_1.8.1-1_all.deb
 563541facd068eba9ac235fe7e89719ce5ee45e4dbc701cba6f2dd8926ddaf6c 7044 python-internetarchive_1.8.1-1_amd64.buildinfo
 22a30546682ffe51182d766871303cc3178d4157a433b0a17b5397aa345a6c66 55840 python3-internetarchive_1.8.1-1_all.deb
Files:
 e21ea1f707de82bedf851f877746959b 1990 python optional python-internetarchive_1.8.1-1.dsc
 648b142182f7a3438c92de25c78740d9 116878 python optional python-internetarchive_1.8.1.orig.tar.gz
 c64239c5e6c5febfd39b65454445bc81 13248 python optional python-internetarchive_1.8.1-1.debian.tar.xz
 0f5c19d9f99e8cc8207bd96ae6459daf 19816 utils optional internetarchive_1.8.1-1_all.deb
 b671070dfaafbd3bfd7b95c57d3737cb 7044 python optional python-internetarchive_1.8.1-1_amd64.buildinfo
 0d70e6353af2b3750f89f2c38b703c7f 55840 python optional python3-internetarchive_1.8.1-1_all.deb

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEexZCBNCWcjsBljWrPqHd3bJh2XsFAluqTOgACgkQPqHd3bJh
2XuB3wf/WEITBLq/r3P8UsloEC0x+nn1ssqor8DkXWdgvsX9x4EkQZj9cZg0WwMm
077ReAIMCTWOt4JNFWCUfW0avBJmC1W5vTgrjCZzAmABr7e0Kos9p0ju1T52RYPw
niK/yrMHOV9rsiGrW4Hr668t6MuNzah17FGhMAWzStgdKqv083s7WCVrNFjm6Jfe
QWYBGp5cJxtejrbnpsCYs9/ZIcKNsZKH+roIL5HqIkTC/A9Z4HMomMTVLRK0mSjL
PFdf3FR+byf4TH3KgntrLL1VEy8Pgvk2i+bEO4R+rK1i+7ECRCcxeoCDSrTLyV15
1iON5B1Ka9wj3c3NM23lviJfh/BTjA==
=PY94
-----END PGP SIGNATURE-----

Message #109 received at 909550@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Chris Lamb <lamby@debian.org>, 909550@bugs.debian.org, Ian Jackson <ijackson@chiark.greenend.org.uk>

Cc: Iain Learmonth <irl@debian.org>, debian-devel@lists.debian.org, ftpmaster@debian.org

Subject: Re: Bug#909550: possible conflict over the /usr/bin/ia namespace

Date: Sun, 16 Dec 2018 09:05:22 -0500

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

Thanks!!

-- 
Un éducateur dans l'âme ne prend rien au sérieux que par rapport
à ses disciples -- soi-même non excepté.
                        - Nietzsche, "Par delà le bien et le mal"

Message #114 received at 909550@bugs.debian.org (full text, mbox, reply):

From: Iain Learmonth <irl@debian.org>

To: Chris Lamb <lamby@debian.org>, Antoine Beaupré <anarcat@debian.org>, Ian Jackson <ijackson@chiark.greenend.org.uk>

Cc: debian-devel@lists.debian.org, 909550@bugs.debian.org, ftpmaster@debian.org

Subject: Re: possible conflict over the /usr/bin/ia namespace

Date: Tue, 18 Dec 2018 02:59:06 +0000

[Message part 1 (text/plain, inline)]

On 15/12/2018 08:41, Chris Lamb wrote:
> [Adding ftpmaster@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?
> 

https://packages.qa.debian.org/p/python-duckduckgo2/news/20180925T145048Z.html

Thanks,
Iain.

[signature.asc (application/pgp-signature, attachment)]

Send a report that this bug log contains spam.