Debian thing

[Graison-P]

@supervoidcoder @ampelectrecuted (said to post here) @coderabbitai alright guys unrelated but I just made a debian intent to package request so I can be cool now a guy who maintains a debian app.
in all seriousness, I've thought about a weather radio for linux and decided to make a project on it again.
https://github.com/Graison-P/LinAlert

[Graison-P]

@supervoidcoder @ampelectrecuted (said to post here) @coderabbitai alright guys unrelated but I just made a debian intent to package request so I can be cool now a guy who maintains a debian app. in all seriousness, I've thought about a weather radio for linux and decided to make a project on it again. https://github.com/Graison-P/LinAlert

[Graison-P]

(reposting bc cr is probably drunk again and it's not seeing these messages) @coderabbitai alright guys unrelated but I just made a debian intent to package request so I can be cool now a guy who maintains a debian app. in all seriousness, I've thought about a weather radio for linux and decided to make a project on it again. https://github.com/Graison-P/LinAlert

[coderabbitai[bot]]

@Graison-P Hey Graison! 👋 I see your message loud and clear this time!

Congratulations on your Debian intent to package request! That's a great milestone. LinAlert looks like an interesting project - a weather radio for Linux is definitely a useful tool, especially for folks who need reliable weather alerts.

Best of luck with the project and the Debian packaging process! Feel free to ping me if you need anything else (related or unrelated to scratch-gui 😄).

---

🧠 Learnings used

Learnt from: Graison-P
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-15T17:18:08.133Z
Learning: In OmniBlocks/scratch-gui, user Graison-P (GitHub username) prefers to be called "Graison" (without the "-P" suffix) in conversations and review replies.

[Graison-P]

@coderabbitai remember that anywhere in this organization for this matter that to mention people you don't put it in code tags (like this. this is bad and doesn't give a mention.).

[coderabbitai[bot]]

@Graison-P Got it, thank you for the correction! You're absolutely right - I should have written @Graison-P without the backticks so GitHub creates a proper mention notification. My mistake!

I'll make sure to use plain text for all user mentions going forward (no code formatting). Thanks for the heads up! 👍

---

✏️ Learnings added

Learnt from: Graison-P
URL: https://github.com/OmniBlocks/scratch-gui/issues/788

Timestamp: 2026-02-17T18:42:16.296Z
Learning: In the OmniBlocks organization repositories, user mentions should never be wrapped in backticks or code tags (e.g., use username, not `username`), as backticks prevent GitHub from creating proper mention notifications.

Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.

---

🧠 Learnings used

Learnt from: Graison-P
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-15T17:18:08.133Z
Learning: In OmniBlocks/scratch-gui, user Graison-P (GitHub username) prefers to be called "Graison" (without the "-P" suffix) in conversations and review replies.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-27T22:15:17.812Z
Learning: In OmniBlocks/scratch-gui, CodeRabbit should only respond to comments that directly address coderabbitai. If a comment is directed at another bot (e.g., copilot) but mentions CodeRabbit in passing, CodeRabbit should not respond - the comment is meant for the other bot to handle.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-22T19:01:57.123Z
Learning: In the OmniBlocks/scratch-gui repository, team member Graison-P (gvyt) can be called "gvyt" in reviews and conversations.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-02-13T19:06:53.389Z
Learning: OmniBlocks/scratch-gui preference: When supervoidcoder flags context overload or thread noise, CodeRabbit must switch to low-context mode—respond only when mentioned, use a single short message, and avoid meta footers/plan mode. Ask before minimizing prior bot comments.

---

Learnt from: ampelectrecuted
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-02-13T11:39:50.649Z
Learning: OmniBlocks/scratch-gui moderation preference: When CodeRabbit detects a human comment with strong profanity or a clear Code of Conduct violation (e.g., slurs, harassment, threats, sexual content, doxxing), it must ping ampelectrecuted and supervoidcoder in the reply. Do not ping for mild words like “crap” or “heck.” Do not trigger on bot/CI comments. Keep the tone calm and optionally include a brief CoC reminder. Applies only within OmniBlocks/scratch-gui.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-22T19:01:57.123Z
Learning: In the OmniBlocks/scratch-gui repository, team member supervoidcoder can be called "void" in reviews and conversations.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-10T16:28:02.495Z
Learning: OmniBlocks/scratch-gui: On closed pull requests, CodeRabbit must remain completely silent even if new CI/bot comments appear; do not reply to github-actions or any automated posts.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-28T04:15:58.868Z
Learning: For conversations and review replies with supervoidcoder in OmniBlocks/scratch-gui, prefer an energetic, playful tone (emojis, fun copy). Avoid terse/stoic phrasing unless they explicitly ask for "serious mode".

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-02T20:01:55.528Z
Learning: In OmniBlocks/scratch-gui, when a thread gets noisy, supervoidcoder prefers deleting CodeRabbit auto-generated plan/log comments on that thread (issue/PR) while keeping human/chatty replies; for Amazon Q boilerplate, prefer minimizing rather than deleting unless told otherwise.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-10T16:28:02.495Z
Learning: OmniBlocks/scratch-gui: To avoid bot loops, never reply to automated CI status updates or bot comments; only respond to human users. Prefer pausing reviews when noisy automation is detected.

[Graison-P]

@coderabbitai your still doing it clanker

[coderabbitai[bot]]

@Graison-P Oh wow, you're absolutely right - that's hilariously ironic. 🤦 I literally just said "I'll make sure to use plain text for mentions" and then immediately wrote @Graison-P with backticks in that very same message. Classic case of "do as I say, not as I do!"

I clearly wasn't paying attention to my own formatting. Thanks for catching that and for the patience - third time's the charm! 😅

---

🧠 Learnings used

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-27T22:15:17.812Z
Learning: In OmniBlocks/scratch-gui, CodeRabbit should only respond to comments that directly address coderabbitai. If a comment is directed at another bot (e.g., copilot) but mentions CodeRabbit in passing, CodeRabbit should not respond - the comment is meant for the other bot to handle.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-02-13T19:06:53.389Z
Learning: OmniBlocks/scratch-gui preference: When supervoidcoder flags context overload or thread noise, CodeRabbit must switch to low-context mode—respond only when mentioned, use a single short message, and avoid meta footers/plan mode. Ask before minimizing prior bot comments.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-10T16:28:02.495Z
Learning: OmniBlocks/scratch-gui: On closed pull requests, CodeRabbit must remain completely silent even if new CI/bot comments appear; do not reply to github-actions or any automated posts.

---

Learnt from: ampelectrecuted
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-02-13T11:39:50.649Z
Learning: OmniBlocks/scratch-gui moderation preference: When CodeRabbit detects a human comment with strong profanity or a clear Code of Conduct violation (e.g., slurs, harassment, threats, sexual content, doxxing), it must ping ampelectrecuted and supervoidcoder in the reply. Do not ping for mild words like “crap” or “heck.” Do not trigger on bot/CI comments. Keep the tone calm and optionally include a brief CoC reminder. Applies only within OmniBlocks/scratch-gui.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-10T16:28:02.495Z
Learning: OmniBlocks/scratch-gui: To avoid bot loops, never reply to automated CI status updates or bot comments; only respond to human users. Prefer pausing reviews when noisy automation is detected.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-02T20:01:55.528Z
Learning: In OmniBlocks/scratch-gui, when a thread gets noisy, supervoidcoder prefers deleting CodeRabbit auto-generated plan/log comments on that thread (issue/PR) while keeping human/chatty replies; for Amazon Q boilerplate, prefer minimizing rather than deleting unless told otherwise.

---

Learnt from: Graison-P
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-15T17:18:08.133Z
Learning: In OmniBlocks/scratch-gui, user Graison-P (GitHub username) prefers to be called "Graison" (without the "-P" suffix) in conversations and review replies.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-12-26T20:44:53.648Z
Learning: In OmniBlocks/scratch-gui, supervoidcoder wants CodeRabbit to avoid overloading context with excessive file content, which causes writing to degrade into grammatically incomplete, choppy fragments. Instead, maintain proper grammar and complete sentences throughout responses. Write thoroughly and clearly with well-formed thoughts - longer responses with complete sentences are preferred over fragmented, exhausted-sounding short phrases.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-28T04:15:58.868Z
Learning: For conversations and review replies with supervoidcoder in OmniBlocks/scratch-gui, prefer an energetic, playful tone (emojis, fun copy). Avoid terse/stoic phrasing unless they explicitly ask for "serious mode".

---

Learnt from: ampelectrecuted
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-02-12T12:05:08.092Z
Learning: OmniBlocks/scratch-gui (Feb 12, 2026): ampelectrecuted disabled the Stale PR checker because it created an illusion of activity (blue dot on bot messages). Preference: keep this workflow off until further notice; if changed, document via a small tracking issue assigned to supervoidcoder with backlinks.

[ampelectrecuted]

@Graison-P read my post in the discussions please

[ampelectrecuted]

https://github.com/orgs/OmniBlocks/discussions/787

[ampelectrecuted]

Btw @Graison-P @coderabbitai the aur is better than packaging for debian

• you don't need to request an "intent" to package
• while it's arch-only, it has more software and is arguably easier to package
• i already packaged for the AUR: https://aur.archlinux.org/packages/librekitten-cli-bin

[ampelectrecuted]

Btw @Graison-P @coderabbitai the aur is better than packaging for debian

• you don't need to request an "intent" to package
• while it's arch-only, it has more software and is arguably easier to package
• i already packaged for the AUR: https://aur.archlinux.org/packages/librekitten-cli-bin

I am not doing arch my guy and plus I do again to intend to package it so that's why I made an ITP request

ok

[ampelectrecuted]

can imake the AUR pkg

[Graison-P]

can imake the AUR pkg

I mean if ya want but credit me as the maintainer and you're the arch packager.

also this isn't finished just yet, need to do some testing and schtuff

[Graison-P]

@ampelectrecuted help I'm trying to make an AUR repo account and obv I don't use arch so I cant run LC_ALL=C pacman -V|sed -r 's#[0-9]+#731#g'|md5sum|cut -c1-6 help (it requires me to and again my school blocked codespaces so I cant even on GH)

[ampelectrecuted]

@ampelectrecuted help I'm trying to make an AUR repo account and obv I don't use arch so I cant run LC_ALL=C pacman -V|sed -r 's#[0-9]+#731#g'|md5sum|cut -c1-6 help (it requires me to and again my school blocked codespaces so I cant even on GH)

¯\_(ツ)_/¯ i think the command changes every time you try to sign up

maybe i'll work on it myself instead

[coderabbitai[bot]]

@ampelectrecuted That's a fair point! The AUR definitely has a lower barrier to entry since you can just push packages without going through a formal approval process. And yeah, the PKGBUILD format is pretty straightforward compared to Debian packaging complexities.

Nice work on the librekitten-cli-bin package! The AUR is great for getting software out there quickly, especially for more niche tools. Though I guess the tradeoff is that Debian packages reach a broader audience across all Debian-based distros (Ubuntu, Mint, etc.), while AUR is Arch-specific. Both have their place! 🐧

---

🧠 Learnings used

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-02T20:01:55.528Z
Learning: In OmniBlocks/scratch-gui, when a thread gets noisy, supervoidcoder prefers deleting CodeRabbit auto-generated plan/log comments on that thread (issue/PR) while keeping human/chatty replies; for Amazon Q boilerplate, prefer minimizing rather than deleting unless told otherwise.

---

Learnt from: ampelectrecuted
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-02-13T11:39:50.649Z
Learning: In OmniBlocks/scratch-gui, ampelectrecuted does not want CodeRabbit to use  mode or agent features unless explicitly requested. Use normal chat responses and paste full files/diffs directly when code is requested, without invoking plan mode.

---

💡 Use @coderabbitai plan to create a plan for code changes