search

kiss-community / community

Officially unofficial KISS community repository, mirror of https://codeberg.org/kiss-community/community
https://kisscommunity.org
MIT License
49 stars 35 forks source link

[Tracker] Outdated Packages #197

Open dilyn-corner opened 3 years ago

dilyn-corner commented 3 years ago

Packages left outdated for "sufficiently long" will be mercilessly evicted. Packages with * will be dropped at the end of the month unless adopted. Packages which require dropped packages will also be dropped. Adopt your dependencies folx!

Packages out-of-date for a "good reason" are fine, but should be mentioned (in this tracker).

Abandoned

fluorescent-haze

Daniel M. Matongo

Xiaodong Xu

David Garland

Nihal Jere

Aaron G

AndreiSva

phoebos

Arthur Williams

Kyryl Melekhin

Cats that hovers

Mederim

Mederim

aabacchus

tslil clingman

Zola

Camille Scholtz

hovercats

Muhammad Herdiansyah

Vouivre

Azriel Akbar Ferry A

Dylan Araps

Jason Eslick

Daniel M. Matongo

Dilyn Corner

Michael Czigler

Owen Rafferty

Zola

Arthur Williams

Dilyn Corner

Ali Burak

Will Eccles

mmatongo commented 3 years ago

Good Lord that's a lot of slack on my part, so sorry.

I've been so held up with irl stuff but I'll try clear this out by tomorrow.

EDIT: Done

noocsharp commented 3 years ago

neofetch pash pfetch

😐

dilyn-corner commented 3 years ago

:eyes:

Very easy packages to maintain...

git-bruh commented 3 years ago

@konimex age was your package, do you still want to maintain it ?

dilyn-corner commented 3 years ago

Note that I'm not specifically saying it's outdated here and need to be updated to a release candidate.

ghost commented 3 years ago

I'll take:

shellcheck-bin sbase ubase sinit pfetch neofetch pash aria2

Vouivre commented 3 years ago

I take pandoc-bin. I don't use discount, but I could take it if you want to.

I have to think about luajit, perhaps I'll take it.

mmatongo commented 3 years ago

I'll take neovim, I wanna do something real quick.

mmatongo commented 3 years ago

croc is up to date, I'll be updating tor today.

acheam0 commented 3 years ago

I can take rclone (should @xuxiaodong not want it anymore), exa (should @kiedtl not want it anymore), and scdoc.

Vouivre commented 3 years ago

At the moment youtube-dl can't be updated. On my system I am unable to download some videos. See here.

EDIT: a fix has been pushed upstream. I won't update until a new version is released.

aaronNGi commented 3 years ago

I can take 9base.

jslick commented 3 years ago

fwiw, I'm well-aware there are updates to protobuf, but they are only for ruby, and protobuf is currently only depended on by mosh and android-tools, so I was ignoring it.

dilyn-corner commented 3 years ago

That's fine by me; thanks for letting me know!

dilyn-corner commented 3 years ago

libxml2 is also outdated; I'd rather not use the upstream http source and the GNOME gitlab source requires autoreconf. So either I'll be hosting one of the two, probably. Unless fossies updates soon...

Vouivre commented 3 years ago

I think we have to switch to the openprinting fork of cups. You can read here for some information:

https://www.phoronix.com/scan.php?page=news_item&px=Apple-No-More-CUPS

The last version of this fork is: 2.3.3op2. Is it ok for kiss if the version has some letters ? I saw Carbs Linux did the switch, so I assume it will work, but I want to make sure.

dilyn-corner commented 3 years ago

Yeah, cups was "forked" recently (this is I think the third time the cups dev has done this to his own project, and the second time Apple paying him to port his patches to their version... smh clever man).

Letters are fine. Whatever the actual version string reported by repology is is preferred, usually.

Vouivre commented 3 years ago

At the moment, the updated packages are not reported on repology. I don't know what must be done. I can help to solve this issue.

dilyn-corner commented 3 years ago

What do you mean, @Vouivre?

sdsddsd1 commented 3 years ago

Repology does not update the package database for some days. https://repology.org/projects/?inrepo=kiss_community&outdated=1 e.g chromium was updated 9 days ago but is still flaged out of date.

Vouivre commented 3 years ago

Exactly! Another example is gnutls.

dilyn-corner commented 3 years ago

Ah, I see what you're saying. I'm not so worried about that.

Vouivre commented 3 years ago

I use repology to know which packages are outdated. I can also switch to kiss-outdated, but it's slower. I could live with it, but I think it would be good that repology show the packages which are really outdated.

Should I have a look at it ?

dilyn-corner commented 3 years ago

A look at making kiss-outdated faster? I feel like someone (@aaronNGI ?) already looked at this with awk or something? Unless you mean changing what repology does. In that case, eh. I am not so worried.

I should make this clear: just because a package is on this list (or isn't) doesn't mean I'm badgering you to update it ASAP. It's just 1) a better way for people who might want to get involved to identify potential orphans they could take over, or 2) for people to figure out who took their package from them, or 3) a gentle reminder

For instance, I'm not checking my packages every day (in community, at least); I have too many to check this every day and update the list (though I could certainly automate this, or build off prior work). Just as long as packages are regularly updated (updated within a few releases, updated within two weeks of upstream releasing it, etc.), it's a-okay.

Mostly, this is just to telegraph (potential) orphans to the broader community. There's no 'good way' of knowing when a package has been abandoned outside of this sort of tracker.

Vouivre commented 3 years ago

Thank you for mentioning that somebody tried to write another version. awk ? I could be interested.

Thank you for clarifying this issue. I still had in mind this kind of issue with dylan: the idea was to open such an issue and to close it when almost every packages had been updated.

Time for me to think about the best way to get notified when a package has to be updated.

aaronNGi commented 3 years ago

I feel like someone (@aaronNGi ?) already looked at this with awk or something?

That was kiss-orphans. I can certainly try and optimize kiss-outdated as well.

aaronNGi commented 3 years ago

I forgot I actually improved kiss-outdated. It depends on jq though. The problem with the original script: It calls a curl (and some other utilities) per package of a repo.

Here it is:

#!/bin/sh
#
# This prints the first 200 outdated packages.

set -e

repo=kiss_community
api_url="https://repology.org/api/v1/projects/?inrepo=$repo&outdated=1"
jq_script='
    .[] | .[] | select(.repo == $repo) |
        .name +" "+ .version +" "+ .maintainers[0]
'

printf 'Downloading repository info from repology...\n' >&2

curl -Ss "$api_url" \
| jq \
    --exit-status \
    --unbuffered \
    --raw-output \
    --arg repo "$repo" \
    "$jq_script" \
| while read -r pkg version maintainer; do
    printf '%-40s %s\n' "$pkg $version" "$maintainer"
done
Vouivre commented 3 years ago

It's much faster, thank you. Unfortunately it doesn't work because I get the same information as on repology. gnutls for example is not outdated and with this script It's given as outdated. kiss-outdated gives the correct information.

I don't know jq, but I assume you can parse the information from repology. If I'm right, the information on repology are not correct, so it can't work.

aaronNGi commented 3 years ago

I don't know jq, but I assume you can parse the information from repology. If I'm right, the information on repology are not correct, so it can't work.

Yes, it uses the repology API, so it is the same as what you see on the website. The original script downloads an svg image for every package which contains the latest version number, which is then compared to the version in your local repo on disk. The question is why is repology wrong in the first place?

I could update the script to compare every outdated package, as received from the repology API, to the version on disk. The problem is name inconsistencies, and maintaining a translation database (like the original script does) kinda sucks.

[Edit] I don't know how repology works at all but a wild guess: It parses our GitHub's commits for text like "new version at ...". Because text like "bump to ...." is not recognized by it, it's not detecting bumps from certain people?!

Vouivre commented 3 years ago

The question is why is repology wrong in the first place?

I'll clarify it. In between I have written a small script to know which packages are outdated. Not perfect, but it does the job.

#!/bin/sh

kiss-outdated /var/db/kiss/repo-community/community 2> /dev/null | \
grep "2bwm \
\|azpainter \
\|cups \
\|zathura"

Just replace with your packages. Perhaps it can be useful to somebody.

EDIT: it seems a fix has been done. The reported outdated packages is right.

git-bruh commented 3 years ago

lld is outdated and cant be built with LLVM 12.

@Ominitay �

ominitay commented 3 years ago

lld is outdated and cant be built with LLVM 12.

@Ominitay �

Will take a look now. Was looking at updating it when LLVM 12 came out, but the LLVM package hadn't been yet updated.

ominitay commented 3 years ago

I have it working now. There's a bug in LLVM 12 which I had to address by bringing in a file from another source; will send a PR soon!

ominitay commented 3 years ago

Updating Zig as well now (will need to wait to compile Clang unfortunately)

ominitay commented 3 years ago

Unfortunately updates made to Zig mean that we can no longer use LLVM built without default targets. Should we drop Zig?

mmatongo commented 3 years ago

Unfortunately updates made to Zig mean that we can no longer use LLVM built without default targets. Should we drop Zig?

You can chuck over to mmatongo/kiss-lang if it ends up getting dropped.

ominitay commented 3 years ago

Unfortunately updates made to Zig mean that we can no longer use LLVM built without default targets. Should we drop Zig?

You can chuck over to mmatongo/kiss-lang if it ends up getting dropped.

I already have Ominitay/kiss-zig, but inclusion in kiss-lang may be a good idea! The issue is that we need an alternative LLVM build, and I'm not sure that that would be wanted at kiss-lang. Either way, I'll wait on kiss-community/repo#44, but I doubt it'll go anywhere...

ominitay commented 3 years ago

Since kiss-community/repo#44 has now been closed, I have submitted a PR to drop zig[-git].

artemkobets commented 3 years ago

Hey. I haven't used or had access to KISS machines for some time now, need to let you know that I won't be able to maintain packages assigned to me:

None of these have very regular updates, so shouldn't take much effort to maintain if they're any useful. Let me know if there's questions.

And thanks Dylan and the community team for a great distribution! Has been invaluable for learning Linux.

aaronNGi commented 3 years ago

I will adopt:

noocsharp commented 3 years ago

I think it's about time for me to prune some packages. I will be dropping:

ominitay commented 3 years ago

I can take htop.

xuxiaodong commented 3 years ago

I can take sdcv and cloc.

konimex commented 2 years ago

Due to my movement to Wayland, I'll drop both bspwm and sxhkd.

lowercasename commented 2 years ago

As KISS is moving to Wayland I will drop berrywm (berry), unless it makes sense to keep it updated?

sdsddsd1 commented 2 years ago

Somewhere, prob irc, I read that this repository shall stay in line with KISS. For me, that means any software which does not work in a wayland session is purgeable and prob banned, no? So every windowmanager, X support application. There is prob stuff which can utilize xorg-libs and libglvnd. Is xwayland in line? I think some guideline would be helpful. @dilyn-corner , since you control the merge button, I am very interested in your thoughts especially. https://github.com/sdsddsd1/kiss-games/blob/master/equipment/xorg-libs/sources

ominitay commented 2 years ago

I'll adopt lvm2. No need to make an adopt commit, I'll do that in my update PR.

dilyn-corner commented 2 years ago

@sdsddsd1 X should live in its repository, if someone has some interest in maintaining a Xorg stack + xorg applications, it's more then welcome to live in this org :)

TAAPArthur commented 2 years ago

@dilyn-corner Why are you asking for us to change dependencies from libressl -> openssl? I read your news post but it just mentioned that the change was being made didn't give a rationale. If there isn't a reason, I don't wish to comply and openconnect can be dropped/adopted.

This is also an example of how being able to change depends via a hook could save some mindless forks.

dilyn-corner commented 2 years ago

The rationale is that 

...community will continue to exist to serve its purpose as usual.
However, it is still governed by the guidestones behind KISS. Packages in it
should build against whatever exists in $/kisslinux/repo as this is the
standard.