aports-turbo issueshttps://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues2017-03-17T11:51:11Zhttps://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues/2API for all packages2017-03-17T11:51:11ZCarlo LandmeterAPI for all packages*Created by: saulshanabrook*
Is there an HTTP API available to get a list of all packages?
*Created by: saulshanabrook*
Is there an HTTP API available to get a list of all packages?
https://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues/7Search should be case-insensitive2020-03-27T10:43:10ZCarlo LandmeterSearch should be case-insensitive*Created by: stwa*
The search is case-sensitive, it would be more intuitive if the search would be case-insensitive.
As package names are always lower-case there should not be any problems.
*Created by: stwa*
The search is case-sensitive, it would be more intuitive if the search would be case-insensitive.
As package names are always lower-case there should not be any problems.
https://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues/9Autolink URLs in message popups on /flagged page2016-04-19T08:47:41ZPrzemysław PawełczykAutolink URLs in message popups on /flagged pageIt would be nice to have autolinking URLs in message popups, so we could simply click such link. Bells and whistles kind of thing, I guess, but would be useful for people browsing /flagged that are not maintainers (as maintainers get me...It would be nice to have autolinking URLs in message popups, so we could simply click such link. Bells and whistles kind of thing, I guess, but would be useful for people browsing /flagged that are not maintainers (as maintainers get messages in their mailboxes).
Remember to use rel="nofollow" in a tag if ever implementing that.
https://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues/22Aggregate flag emails to daily(?) digests2017-01-14T15:25:15ZJakub JirutkaAggregate flag emails to daily(?) digestshttps://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues/38Maintainer lookup by email, not name2018-01-29T17:32:49ZAriadne Conillariadne@ariadne.spaceMaintainer lookup by email, not nameIt is possible that two maintainers might have the same name if it is a common one. So we should use email addresses instead.
It is possible that two maintainers might have the same name if it is a common one. So we should use email addresses instead.
https://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues/39Improving package search - searching in pkgdesc2020-03-28T15:18:18ZBernhard J. M. GrünImproving package search - searching in pkgdescIt would be a nice improvement to also have a switch to enable searching
in package descriptions (pkgdesc) too on the website
https://pkgs.alpinelinux.org/packages .
*(from redmine: issue id 8489, created on 2018-02-15)*It would be a nice improvement to also have a switch to enable searching
in package descriptions (pkgdesc) too on the website
https://pkgs.alpinelinux.org/packages .
*(from redmine: issue id 8489, created on 2018-02-15)*Carlo LandmeterCarlo Landmeterhttps://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues/42Allow filtering out -doc, -lang, -dbg, -dev and -static subpackages2020-08-25T10:26:55ZBart RibbersAllow filtering out -doc, -lang, -dbg, -dev and -static subpackagesIt would be nice to filter out such packages as they're often not relevant to my search and fill up the search results.It would be nice to filter out such packages as they're often not relevant to my search and fill up the search results.https://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues/44Consider making the default package search fuzzy (not exact)2024-03-12T06:56:05ZValentinConsider making the default package search fuzzy (not exact)On most websites search is by default fuzzy, including other distro's package search pages like https://archlinux.org/packages/ and https://www.debian.org/distrib/packages . This is different from https://pkgs.alpinelinux.org/packages w...On most websites search is by default fuzzy, including other distro's package search pages like https://archlinux.org/packages/ and https://www.debian.org/distrib/packages . This is different from https://pkgs.alpinelinux.org/packages where the default is exact.
The website does tell you this when you hover over the field with the mouse but it is easy to miss and not everyone uses the mouse to navigate. If you do miss it then you might end up thinking the package you are looking or does not exist or you miss interesting related packages.
For example if I search for `gdb` on alpine I only see the `gdb` package but not `gdb-doc`. In the other linked searches it shows similar names by default.
To me it would feel better if the search was by default something like `*gdb*` with the results ordered by some kind of similarity metric so that the exact match `gdb` still shows up first.
I understand that this is a subjective preference. I still want to give this feedback as it might confuse other new users.https://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues/47requires/required-by displays first virtual match only2023-02-11T23:28:12ZGhost Userrequires/required-by displays first virtual match onlyif a package depends on, e.g., `so:libsomething.so.1`, then in the webui the `Requires` will display a concrete package that provides that virtual.
however, if actually multiple packages provide= that virtual, then all of them will disp...if a package depends on, e.g., `so:libsomething.so.1`, then in the webui the `Requires` will display a concrete package that provides that virtual.
however, if actually multiple packages provide= that virtual, then all of them will display the original package in `Required by`. this looks confusing at first glance because one sees required-by on a package, clicks it, then doesn't see it in `Requires`
not really very meaningful, but just to keep trackhttps://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues/48Add functionality to remove misflagged packages2024-02-28T10:38:30ZKrassy Boykinovkboykinov@teamcentrixx.comAdd functionality to remove misflagged packagesSometimes the flagged page of aports-turbo (https://pkgs.alpinelinux.org/flagged) can contain bogus information, it seems useful for me to introduce some kind of removal process to aid in general validity of the said service.
There are ...Sometimes the flagged page of aports-turbo (https://pkgs.alpinelinux.org/flagged) can contain bogus information, it seems useful for me to introduce some kind of removal process to aid in general validity of the said service.
There are multiple types of wrong flags:
1. Non version number content:
![spam](/uploads/b08f250aaf96278fd15fefab7b2873dc/spam.png)
2. Wrong version number content:
![wrong](/uploads/cf9574072f24a72adf7329dbc7cbf2d3/wrong.png)
3. Dev version marked as release by Anitya (mapping error on their platform):
![anitya](/uploads/29004ab4512778f0c9ac8447f68d0850/anitya.png)
<br>
<br>
What have i thought of?
As there are multiple causes of the mismatched flag data, multiple sulutions are proposed:
* Non Solution: The admin has to remove the entries by hand from the SQL database (does not happen atm)
* Solution 1: Removing the userbased flag functionality and instead referencing to Anitya for flagging (after the Flag button click)
| pros | cons |
| ------ | ------ |
| light implementation demand | some enterprise users have time windows and possibly would not flag the package at all |
| bar for spam flaggers rises, because an account has to be created at Anitya | does not directly aid in removing existing bad entries |
* Solution 2: Adding a "report false positive" button, that notifies the maintainer of the package to confirm the false positive
| pros | cons |
| ------ | ------ |
| safegurad against bot-based deletes | if maintainer is inactive, the confirmation link will (probably) never be clicked on |
| | does not handle unmaintained packages well |
* Sulution 3: Solution_2() + notifying active maintainers, that have write permission to `/aports` repo after a timeout or directly if without maintainer
| pros | cons |
| ------ | ------ |
| safegurad against bot-based deletes | maybe harder to implement |
| confirmation links of inactive maintainers are forwardable to active ones | |
| handles unmaintained packages | |
Comments welcome!
P.S. Whether one of these solutions is approached, displaying a tooltip with a link and one to two lines of explanation towards Anitya would help imo.https://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues/49Using aports-turbo for OpenWrt2024-01-04T14:50:37ZPaul SpoorenUsing aports-turbo for OpenWrtHi I'm an OpenWrt developer and Alpine user. For the longest of time we've tracked packages inside our wiki which comes with many drawbacks. Since I like the simple and clean approach of Alpine pkgs, I created a custom importer which add...Hi I'm an OpenWrt developer and Alpine user. For the longest of time we've tracked packages inside our wiki which comes with many drawbacks. Since I like the simple and clean approach of Alpine pkgs, I created a custom importer which adds OpenWrt packages.
I'm running a demo instance over and wanted to ask if Alpine people mind if we run a similar instance? I'm happy to mention that it originates from the Alpine project or whatever credits you desire.
* http://evernet.duckdns.org:21001/packagesCarlo LandmeterCarlo Landmeter