aports-turbo issueshttps://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues2024-01-04T14:50:37Zhttps://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 Landmeterhttps://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/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/46Package name not properly escaped in "Contents of package" link2023-06-07T12:41:57ZSamantaz FoxPackage name not properly escaped in "Contents of package" linkThe package's name inside the `Contents of package` link is not properly URL encoded
Steps to reproduce:
1. Go to a package page like https://pkgs.alpinelinux.org/package/edge/main/x86_64/libstdc++
1. Click the `Contents of package` l...The package's name inside the `Contents of package` link is not properly URL encoded
Steps to reproduce:
1. Go to a package page like https://pkgs.alpinelinux.org/package/edge/main/x86_64/libstdc++
1. Click the `Contents of package` link
1. URL contains `&name=libstdc++`, `Package` filter contains `libstdc` and there are no results
1. Manually search for `libstdc++` on the same page
1. URL now contains `&name=libstdc%2B%2B` and the expected results appearhttps://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues/45Anitya watcher does not distinguish pre-release versions2022-07-28T04:31:39ZPatrycja Rosaalpine@ptrcnull.meAnitya watcher does not distinguish pre-release versionsCan be seen on `community/librsvg`:
![image](/uploads/f25a3acb3b68481e315c75e01a6b5bae/image.png)
Even though 2.53.2 is marked as pre-release, it's still flagged:
![image](/uploads/31c2f636764c59b8278073986d6a997c/image.png)Can be seen on `community/librsvg`:
![image](/uploads/f25a3acb3b68481e315c75e01a6b5bae/image.png)
Even though 2.53.2 is marked as pre-release, it's still flagged:
![image](/uploads/31c2f636764c59b8278073986d6a997c/image.png)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/43Use code fragments for OpenWrt2020-11-11T05:56:22ZPaul SpoorenUse code fragments for OpenWrtHi, I'm doing some stuff around the OpenWrt project and there are some ambitions to "beautify" the current package overview. The Alpine project solved the matter in a elegant way and even if the reporting/flagging features are a bit out ...Hi, I'm doing some stuff around the OpenWrt project and there are some ambitions to "beautify" the current package overview. The Alpine project solved the matter in a elegant way and even if the reporting/flagging features are a bit out of the current scope, I'd like to use parts of the current website - if that's okay.
I'd obviously apply a different style/logo, but keep the structure (because it's great). Would that work for the Alpine devs? What kind of *mentioning* would you require or do you very much dislike the idea? In that case I'd have to reinvent the wheel.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/41aports-turbo fails to start on Alpine v3.122023-06-07T13:02:52ZGreyaports-turbo fails to start on Alpine v3.12It appears there is an issue with using aports-turbo on a fresh Alpine v3.12 install. When started I get the following error:
```
[W 2020/06/13 00:46:16] _G.__TURBO_USE_LUASOCKET__ set, using LuaSocket (degraded performance).
luajit: at...It appears there is an issue with using aports-turbo on a fresh Alpine v3.12 install. When started I get the following error:
```
[W 2020/06/13 00:46:16] _G.__TURBO_USE_LUASOCKET__ set, using LuaSocket (degraded performance).
luajit: attempt to index a number value
stack traceback:
[C]: in function 'poll'
/usr/share/luajit-2.1.0-beta3/turbo/ioloop.lua:464: in function '_event_poll'
/usr/share/luajit-2.1.0-beta3/turbo/ioloop.lua:443: in function 'start'
./aports.lua:154: in main chunk
[C]: at 0x5631f48fd0b2
```
I can't quite pin down what is going on exactly, but it works fine on a fresh v3.8 install. I put this down to some sort of change in lua-turbo between the package in v3.8 (lua-turbo 2.1.2-r1) and the package in v3.12 (lua-turbo 2.1.3-r4). I haven't confirmed this, but the behaviour points that way.https://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues/40Discourage incorrect use of pkgs.a.o's flag feature2022-07-25T10:55:12ZTBKDiscourage incorrect use of pkgs.a.o's flag featureI have seen quite a few bug reports and other messages from flagged packages.
Here is one example:
![flagged-incorrect-use](/uploads/86d0800d7b2cf023c0f844782e527a50/flagged-incorrect-use.png)
Google Translate says it is Japanese and m...I have seen quite a few bug reports and other messages from flagged packages.
Here is one example:
![flagged-incorrect-use](/uploads/86d0800d7b2cf023c0f844782e527a50/flagged-incorrect-use.png)
Google Translate says it is Japanese and means "thank you" https://translate.google.com/#view=home&op=translate&sl=auto&tl=en&text=%E3%82%88%E3%82%8D%E3%81%97%E3%81%8F%E3%81%8A%E9%A1%98%E3%81%84%E3%81%84%E3%81%9F%E3%81%97%E3%81%BE%E3%81%99%E3%80%82
A simple warning/notice might alleviate the problem.
I made a quick markup:
![warning](/uploads/36651b747f8cd86fcf937ed70f079eac/warning.png)
Related code:
```html
<div class="pure-u-1 pure-u-lg-10-24">
.......
<div class="grid-head">Be aware!</div>
<div class="grid-body" style="">
<notice style="color: #fff;background-color: #dd320b;padding: 1em;border-radius: 4px;line-height: 2em;width: 541.167px;height: 57px;display: inherit;" color="d9edf7">This form is intented to report outdated packages.<br>Please report all other issues related to tini via the <a href="https://bugs.alpinelinux.org/projects/alpine/issues">Bug Tracker</a></notice>
</div>
</div>
```
```css
element {
color: #fff;
background-color: #dd320b;
padding: 1em;
border-radius: 4px;
line-height: 2em;
width: 541.167px;
height: 57px;
display: inherit;
}
```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/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/8Message popups on /flagged page vanish too easily2016-04-18T22:47:16ZPrzemysław PawełczykMessage popups on /flagged page vanish too easilyThey are hidden even when I want to select the text from the message popup itself.
(Tested in Chrome 49 on Windows 7 x64)
They are hidden even when I want to select the text from the message popup itself.
(Tested in Chrome 49 on Windows 7 x64)
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/6Adding a OpenSearch description file2016-04-18T15:31:39ZCarlo LandmeterAdding a OpenSearch description file*Created by: leo-unglaub*
Hey,
it would be very awesome if you could add an OpenSearch description file. That way the user cann add the package search to the browser and simply use the browser to search dircetly thru the package databas...*Created by: leo-unglaub*
Hey,
it would be very awesome if you could add an OpenSearch description file. That way the user cann add the package search to the browser and simply use the browser to search dircetly thru the package database.
I addded you an untested version of the correct xml and header tag.
`<link rel="search" type="application/opensearchdescription+xml" href="opensearch.xml" title="Alpine Linux Package Database"/>`
```
<?xml version="1.0" encoding="UTF-8"?>
<OpenSearchDescription xmlns="http://a9.com/-/spec/opensearch/1.1/" xmlns:moz="http://mozilla.org/2006/browser/search">
<ShortName>Alpine Linux Package Database</ShortName>
<Description>Search for Alpine Linux packages (apk)</Description>
<Tags>linux alpine packages apk</Tags>
<Contact>webmaster@alpinelinux.org</Contact>
<Url type="text/html" method="GET" template="https://pkgs.alpinelinux.org/packages">
<Param name="name" value="{searchTerms}"/>
<Param name="repo" value="all"/>
<Param name="arch" value="x86_64"/>
<Param name="maintainer" value="all"/>
</Url>
<LongName>Alpine: Search packages</LongName>
<Image height="16" width="16" type="image/png">https://alpinelinux.org/favicon.ico</Image>
<InputEncoding>UTF-8</InputEncoding>
</OpenSearchDescription>
```
Thanks and greetings
Leo
https://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/3Py-Cffi not found2016-03-30T06:56:55ZCarlo LandmeterPy-Cffi not found*Created by: kilpatty*
Currently with any version of Alpine-Linux from the Dockerhub repositories attempting to install any package with py-cffi as a dependency will return not found as it is looking for py-cffi-1.3.0 whereas it appears...*Created by: kilpatty*
Currently with any version of Alpine-Linux from the Dockerhub repositories attempting to install any package with py-cffi as a dependency will return not found as it is looking for py-cffi-1.3.0 whereas it appears that on alpine-linux apk package repo it is currently version 1.4.2
https://pkgs.alpinelinux.org/package/community/x86_64/py-cffi
https://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues/37css tooltip does not like overflow on parent div2020-03-28T15:23:02ZCarlo Landmetercss tooltip does not like overflow on parent divIn the flagged section when there are [limited results](https://pkgs.alpinelinux.org/flagged?origin=&maintainer=7heo) the tooltip applied to the message icon will be hidden behind the parent div which has overflow-x:auto set. We need ove...In the flagged section when there are [limited results](https://pkgs.alpinelinux.org/flagged?origin=&maintainer=7heo) the tooltip applied to the message icon will be hidden behind the parent div which has overflow-x:auto set. We need overflow-x to make the table kind of usable on smaller screens.
One solution would be to make the parent div min-height set to 100% to allow the tooltip to use the extra space below the table, but this does not work.
A solution without the use of JavaScript would be preferred.https://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues/28add makedepens to db2018-01-31T08:34:30ZCarlo Landmeteradd makedepens to dbAs apk-tools will probably never have this feature, maybe it would be a nice addition to add them to its own table in our db.
As apk-tools will probably never have this feature, maybe it would be a nice addition to add them to its own table in our db.
https://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues/22Aggregate flag emails to daily(?) digests2017-01-14T15:25:15ZJakub JirutkaAggregate flag emails to daily(?) digests