« first day (3757 days earlier)      last day (46 days later) » 

6:48 AM
@AndrasDeak Ah, I missed that link. I guess I didn't look carefully. So another Debian derivative?
@AndrasDeak ?
 
 
2 hours later…
8:38 AM
@FaheemMitha amazingly enough, someone whose name seems familiar asked about it last August on bugs.debian.org/cgi-bin/bugreport.cgi?bug=954407
 
8:53 AM
@StephenKitt Yes, I see. I forgot I did that.
I don't think I got a reply, either.
@StephenKitt Question: if a package never appears in a stable release, would it still have a record on packages.qa.debian.org?
 
@StephenKitt Yes, I see. Though isn't firefox an old package?
So perhaps Daniel didn't upload litecli to unstable, because otherwise there would be a record of it.
 
@FaheemMitha yes, and it has been in stable before, but here’s one that hasn’t: packages.qa.debian.org/g/gcc-9.html
@FaheemMitha the ITP bug would have been closed for a start
 
@StephenKitt Right.
@StephenKitt Yes, so why doesn't that previous history show up?
 
@FaheemMitha because packages.qa is obsolete; you can see the history on tracker.debian.org/pkg/firefox
 
9:00 AM
@StephenKitt Oh. I knew there was an alternative now, but I didn't realise that it had been obsoleted. Thank you for the clarification.
 
9:13 AM
That site should probably be explicitly marked as obsolete.
Weird. pip3 lists installed Debian packages too. Is that normal/expected behavior?
For example,
reportbug           7.5.3-deb10u1
which is definitely an installed Debian package.
There's no mention of this in the man page.
 
9:27 AM
@FaheemMitha yes, Debian Python modules appear in such a way that pip sees them too
 
@StephenKitt That's not ideal. At a minimum, it should be possible to distinguish them.
 
@FaheemMitha why? The point is that Python modules from packages can satisfy pip dependencies too.
 
@StephenKitt Sure. But it can be important to distinguish between locally installed packages, and those that are not locally installed.
 
@FaheemMitha that’s what dpkg is for, not pip. pip3 list -v will tell you where modules are installed, and the installer (if known); you can use that to identify packaged modules v. locally-installed modules.
 
@StephenKitt Ok.
 
10:15 AM
Still, it wouldn't hurt for this to be stated explicitly. The documentation doesn't say this. At least what I read.
 
10:28 AM
Does anyone know what this lintian line is for?
> I: dh_python3 pydist:228: Cannot find package that provides cli_helpers. Please add package that provides it to Build-Depends or add "cli_helpers python3-cli-helpers" line to debian/py3dist-overrides or add proper dependency to Depends by hand and ignore this info.
 
10:48 AM
@FaheemMitha lintian -i will give you more info
but I don’t think that’s a lintian message
 
@StephenKitt Yes, maybe debhelper.
 
11:35 AM
@FaheemMitha assuming Daniel Baumann is indeed a debian guy, he's probably wearing multiple hats, and another one is with progress linux
@FaheemMitha for what it's worth apt and pip often/usually use different trees stackoverflow.com/questions/9387928/… . Furthermore, it's considered a good practice to use virtualenvs for your own (non-system) stuff so that you don't step on the toes of the system python. In that case everything is in the virtualenv's local tree. Or at least you can use pip install --user which would put it in ~/.local/lib/python*/site-packages
I haven't used system python packages in a long time. Pip installed isolated versions are a lot more recent too.
 

« first day (3757 days earlier)      last day (46 days later) »