* [ISSUE] CI: Ensure package updates can be checked (and if any updates are available)
@ 2022-07-22 23:25 JamiKettunen
2024-06-14 6:08 ` [RFC] " classabbyamp
2024-06-14 6:08 ` [ISSUE] [CLOSED] " classabbyamp
0 siblings, 2 replies; 3+ messages in thread
From: JamiKettunen @ 2022-07-22 23:25 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1931 bytes --]
New issue by JamiKettunen on void-packages repository
https://github.com/void-linux/void-packages/issues/38193
Description:
Currently new packages can be submitted with broken `./xbps-src update-check`'s and I'd like to change that. I think it's important to have working update checking in packages, and as a bonus give some notice/warning when updates are available for packages on a PR when CI runs.
Chatlogs from `#xbps` IRC:
```
2022-07-23 00:45:43 deathmist would it make sense for xlint to check package updates? I think it would be nice to verify new updates can be checked for a new package submitted to void-packages (and I guess fail CI if there's updates before even building?)
2022-07-23 00:50:07 deathmist something like: [ -n "$(./xbps-src update-check $pkg 2>&1)" ] && (error etc. updates found or couldn't check them)
2022-07-23 00:50:55 abby would be better as a different ci lint, I think (like the commit lint)
2022-07-23 00:51:40 abby and not being the newest version isn't automatically bad, sometimes updates further can't/shouldn't be done
2022-07-23 00:51:42 deathmist sure, but it would be useful yes? not sure about the failing on available updates part, perhaps it could emit some warning?
2022-07-23 00:56:07 abby it might be good to check if the update-check works, but only error if the check is broken (no VERSION etc), not if further updates are available
2022-07-23 01:00:34 deathmist abby: hm, not even a notice/warning (I don't know if that is possible on GH actions / travis without failing CI) when there's updates?
2022-07-23 01:01:11 deathmist I guess a message could be printed if there's updates, but it'll get lost with the other CI logs if all is green
2022-07-23 01:01:51 deathmist (at leas that's my concern)
2022-07-23 01:09:49 abby maybe a notice or warning could work
2022-07-23 01:42:55 \\ abby, deathmist: github ci supports warnings/notices, so that'd work
```
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [ISSUE] [CLOSED] [RFC] CI: Ensure package updates can be checked (and if any updates are available)
2022-07-22 23:25 [ISSUE] CI: Ensure package updates can be checked (and if any updates are available) JamiKettunen
2024-06-14 6:08 ` [RFC] " classabbyamp
@ 2024-06-14 6:08 ` classabbyamp
1 sibling, 0 replies; 3+ messages in thread
From: classabbyamp @ 2024-06-14 6:08 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1934 bytes --]
Closed issue by JamiKettunen on void-packages repository
https://github.com/void-linux/void-packages/issues/38193
Description:
Currently new packages can be submitted with broken `./xbps-src update-check`'s and I'd like to change that. I think it's important to have working update checking in packages, and as a bonus give some notice/warning when updates are available for packages on a PR when CI runs.
Chatlogs from `#xbps` IRC:
```
2022-07-23 00:45:43 deathmist would it make sense for xlint to check package updates? I think it would be nice to verify new updates can be checked for a new package submitted to void-packages (and I guess fail CI if there's updates before even building?)
2022-07-23 00:50:07 deathmist something like: [ -n "$(./xbps-src update-check $pkg 2>&1)" ] && (error etc. updates found or couldn't check them)
2022-07-23 00:50:55 abby would be better as a different ci lint, I think (like the commit lint)
2022-07-23 00:51:40 abby and not being the newest version isn't automatically bad, sometimes updates further can't/shouldn't be done
2022-07-23 00:51:42 deathmist sure, but it would be useful yes? not sure about the failing on available updates part, perhaps it could emit some warning?
2022-07-23 00:56:07 abby it might be good to check if the update-check works, but only error if the check is broken (no VERSION etc), not if further updates are available
2022-07-23 01:00:34 deathmist abby: hm, not even a notice/warning (I don't know if that is possible on GH actions / travis without failing CI) when there's updates?
2022-07-23 01:01:11 deathmist I guess a message could be printed if there's updates, but it'll get lost with the other CI logs if all is green
2022-07-23 01:01:51 deathmist (at leas that's my concern)
2022-07-23 01:09:49 abby maybe a notice or warning could work
2022-07-23 01:42:55 \\ abby, deathmist: github ci supports warnings/notices, so that'd work
```
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [RFC] CI: Ensure package updates can be checked (and if any updates are available)
2022-07-22 23:25 [ISSUE] CI: Ensure package updates can be checked (and if any updates are available) JamiKettunen
@ 2024-06-14 6:08 ` classabbyamp
2024-06-14 6:08 ` [ISSUE] [CLOSED] " classabbyamp
1 sibling, 0 replies; 3+ messages in thread
From: classabbyamp @ 2024-06-14 6:08 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 240 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/38193#issuecomment-2167277386
Comment:
https://github.com/void-linux/void-packages/commit/019298192217acd3cc7e4134daffb1bd9703f290
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-06-14 6:08 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-07-22 23:25 [ISSUE] CI: Ensure package updates can be checked (and if any updates are available) JamiKettunen
2024-06-14 6:08 ` [RFC] " classabbyamp
2024-06-14 6:08 ` [ISSUE] [CLOSED] " classabbyamp
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).