tk missing?
-
- Offline
- 1 month 1 week ago
- 2015-09-30
In the Package browser on the Alpine site (a great thing, by the way; it's very useful to be able to query the package database, especially being able to ask "what packages contain a file whose name is LIKE x) shows a tk (v8.6) package in the main repository. I am using dl-2.alpinelinux.org. My /etc/apk/repositories:
#/media/cdrom/apks
http://dl-2.alpinelinux.org/alpine/v3.2/main
#http://dl-2.alpinelinux.org/alpine/edge/main
http://dl-2.alpinelinux.org/alpine/edge/testing
'apk search tk' doesn't find it. tcl is there, but tk is not.
Yes, I've done apk update. And I checked the repository with a web browser and tk is missing. This raises two questions:
1. Why is tk missing?
2. Why does the package browser say one thing and the repository another?
I checked dl-[3,4,5] and they are all the same -- no tk.
/Don
You are using two release repositoies here. "v3.2/main" and "edge/testing"
tk is currently in the "edge/main" repository, which is the future "v3.3/main" repository.
apk doesn't find it because tk is neither in "3.2/main" nor "edge/testing", the only ones in your /etc/apk/repositories
I think the web package search tool looks up packages in edge, which is why you got a positive result there.
In addition, and for other reasons, I would avoid mixing repository versions. Stick to 3.2, and wait for tk to appear in 3.3 (which should be shortly, #famouslastwords)
On 11/13/15, Alpine Linux forums wrote:
> Hi DonAllen,
>
> You have received a comment on: "tk missing?"
>
> ----
> You are using two release repositoies here. "v3.2/main" and "edge/testing"
>
> tk is currently in the "edge/main" repository, which is the future
> "v3.3/main" repository.
>
> apk doesn't find it because tk is neither in "3.2/main" nor "edge/testing",
> the only ones in your /etc/apk/repositories
Actually, edge/main *is* in /etc/apk/repositories, just commented out.
>
> I think the web package search tool looks up packages in edge, which is why
> you got a positive result there.
Except that it says 'main' in the Repository column. If the package
search tool is searching multiple repositories named 'main', it ought
to give the fully qualified name in its response. Or perhaps it's a
bad idea to have multiple repositories named main. The point is that
the package tool's response is ambiguous and that should be fixed, one
way or the other.
>
> In addition, and for other reasons, I would avoid mixing repository
> versions. Stick to 3.2, and wait for tk to appear in 3.3 (which should be
> shortly, #famouslastwords)
Yes. I am not attempting to mix repository versions. I only have
3.2/main enabled in my /etc/apk/repositories. Though, as I mentioned
above, the /etc/apk/repositories file includes a line for edge/main,
commented out. If it's a bad idea to use both main repositories, then
perhaps that line should not be there. Or a comment that one should
enable one or the other, not both.
Thanks for your response. You cleared up the mystery of the missing tk.
/Don