Announcement list for new TW snapshots?
Hi everyone, Perhaps my mailing list searching -fu is not up to snuff .. I'm searching for an announcement-only mailing list for new Tumbleweed snapshots. If no such list exists, can we create one? The list would only allow the following posts (from Dimstar .. :): * New Tumbleweed snapshot ... * Tumbleweed - Review of the week .. What do people think? --- Pablo
On Sun, 23 Jul 2023, 17:36:25 +0200, Pablo Sanchez wrote:
Hi everyone,
Perhaps my mailing list searching -fu is not up to snuff .. I'm searching for an announcement-only mailing list for new Tumbleweed snapshots.
If no such list exists, can we create one? The list would only allow the following posts (from Dimstar .. :):
* New Tumbleweed snapshot ... * Tumbleweed - Review of the week ..
What do people think?
+1
--- Pablo
Cheers. l8er manfred
Manfred Hollstein wrote:
On Sun, 23 Jul 2023, 17:36:25 +0200, Pablo Sanchez wrote:
Hi everyone, Perhaps my mailing list searching -fu is not up to snuff .. I'm searching for an announcement-only mailing list for new Tumbleweed snapshots. If no such list exists, can we create one? The list would only allow the following posts (from Dimstar .. :):
New Tumbleweed snapshot ... Tumbleweed - Review of the week ..
What do people think? +1
Pablo Cheers. l8er manfred
May I suggest using RSS instead/in addition? Dimstar posts to the forums.opensuse.org Discourse server for each new snapshot, and a feed that effectively represents a "Tumbleweed snapshots" feed can therefore be obtained by using this RSS link: https://forums.opensuse.org/u/dimstar/activity.rss Just thinking that is an existing mechanism that doesn't require any more infrastructure work to be done?
On 7/23/23 12:06, John Kizer via openSUSE Factory wrote:
[ trimmed to reduce clutter ] May I suggest using RSS instead/in addition? Dimstar posts to the forums.opensuse.org Discourse server for each new snapshot, and a feed that effectively represents a "Tumbleweed snapshots" feed can therefore be obtained by using this RSS link:
https://forums.opensuse.org/u/dimstar/activity.rss
Just thinking that is an existing mechanism that doesn't require any more infrastructure work to be done?
Hi John, The above is great information for those who are using RRS. Unfortunately (for me?), I no longer use RRS. Worst case: I suppose I could write a little shell script that periodically polls the above URI. If there's no appetite for the suggestion, I'll do that. Thank you for the link. Cheers, -pablo
Hi Pablo, On 23.07.23 at 18:13 Pablo Sanchez wrote:
The above is great information for those who are using RRS. Unfortunately (for me?), I no longer use RRS.
Your headers say you are using Thunderbird, hence RSS is only two clicks away... :-) Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
On 2023-07-24 01:04, Johannes Kastl wrote:
Hi Pablo,
On 23.07.23 at 18:13 Pablo Sanchez wrote:
The above is great information for those who are using RRS. Unfortunately (for me?), I no longer use RRS.
Your headers say you are using Thunderbird, hence RSS is only two clicks away... :-)
Hi Johannes, Thank you. It's not that I don't know how to use an RRS reader (I preferred akregator), I chose not to. :) Given only one other person liked the idea, I'll go with my scripting idea to get an email. Cheers! -pablo
On 7/23/23 12:13, Pablo Sanchez wrote:
On 7/23/23 12:06, John Kizer via openSUSE Factory wrote:
[ trimmed to reduce clutter ] May I suggest using RSS instead/in addition? Dimstar posts to the forums.opensuse.org Discourse server for each new snapshot, and a feed that effectively represents a "Tumbleweed snapshots" feed can therefore be obtained by using this RSS link:
https://forums.opensuse.org/u/dimstar/activity.rss
Just thinking that is an existing mechanism that doesn't require any more infrastructure work to be done?
Hi John,
The above is great information for those who are using RRS. Unfortunately (for me?), I no longer use RRS.
Worst case: I suppose I could write a little shell script that periodically polls the above URI. If there's no appetite for the suggestion, I'll do that. Thank you for the link.
Cheers,
-pablo
Hi Pablo, You can see the new builds here as well as what is currently being QA'd. https://openqa.opensuse.org/group_overview/1?limit_builds=25 If you use the tumbleweed-cli package, then tumbleweed status Shows you the latest build, the build you are currently targeted too, and your current build. tumbleweed list Shows you which builds are currently available ( the last 20 with the oldest rolling off when a new build is published ) I like using tumbleweed-cli because it leaves me in control of which build I am running and as long as I stay within the 20 builds available, if I need to install something later, I know that it is from the same build as I have installed. -- Regards, Joe
Op maandag 24 juli 2023 18:22:36 CEST schreef Pablo Sanchez:
On 2023-07-24 12:17, Joe Salmeri wrote:
Hi Pablo,
Hi Joe
[ trimmed ]
If you use the tumbleweed-cli package, then
Whoa! tumbleweed-cli .. that's the cat's meow! Thank you so much Joe! What a gem!
Cheers,
-pablo I firmly disagree, having seen the results on some machines, where the admin had used TW-cli to move back to a snapshot of ~2 months old. Meanwhile the move to /usr/etc happened, and they ended up with borked servers. If you want to move back and forward between snapshots, use btrfs, it's meant to do this
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board openSUSE Forums Team
On 2023-07-24 12:28, Knurpht-openSUSE wrote:
I firmly disagree, having seen the results on some machines, where the admin had used TW-cli to move back to a snapshot of ~2 months old. Meanwhile the move to /usr/etc happened, and they ended up with borked servers. If you want to move back and forward between snapshots, use btrfs, it's meant to do this
Hi Gertjan, I only use btrfs snapshots to unwind borked drops. My plan is to use the CLI to push me an email when there's a new drop. I'm too lazy to go and check an RRS feed. :] Cheers, -pablo
Op maandag 24 juli 2023 18:31:06 CEST schreef Pablo Sanchez:
On 2023-07-24 12:28, Knurpht-openSUSE wrote:
I firmly disagree, having seen the results on some machines, where the admin had used TW-cli to move back to a snapshot of ~2 months old. Meanwhile the move to /usr/etc happened, and they ended up with borked servers. If you want to move back and forward between snapshots, use btrfs, it's meant to do this
Hi Gertjan,
I only use btrfs snapshots to unwind borked drops. My plan is to use the CLI to push me an email when there's a new drop. I'm too lazy to go and check an RRS feed. :]
Cheers,
-pablo
Hola Pablo, Well, you're using a mail-client, I do too. i.e. kmail2 . And I use filters to have a folder for each ML I'm subscribed to. It would be a matter of minutes to filter the announcements in their own folder ( and/or delete the rest) . -- Gertjan Lettink a.k.a. Knurpht openSUSE Board openSUSE Forums Team
On 2023-07-24 12:36, Knurpht-openSUSE wrote:
Op maandag 24 juli 2023 18:31:06 CEST schreef Pablo Sanchez:
On 2023-07-24 12:28, Knurpht-openSUSE wrote:
I firmly disagree, having seen the results on some machines, where the admin had used TW-cli to move back to a snapshot of ~2 months old. Meanwhile the move to /usr/etc happened, and they ended up with borked servers. If you want to move back and forward between snapshots, use btrfs, it's meant to do this Hi Gertjan,
I only use btrfs snapshots to unwind borked drops. My plan is to use the CLI to push me an email when there's a new drop. I'm too lazy to go and check an RRS feed. :]
Cheers,
-pablo Hola Pablo,
Well, you're using a mail-client, I do too. i.e. kmail2 . And I use filters to have a folder for each ML I'm subscribed to. It would be a matter of minutes to filter the announcements in their own folder ( and/or delete the rest) .
Salut Gertjan ! You're absolutely right but there's my up bringing that comes into play ... I don't like to waste things. :) À bientôt ! -pablo
On 7/24/23 12:28, Knurpht-openSUSE wrote:
Op maandag 24 juli 2023 18:22:36 CEST schreef Pablo Sanchez:
On 2023-07-24 12:17, Joe Salmeri wrote:
Hi Pablo, Hi Joe
[ trimmed ]
If you use the tumbleweed-cli package, then Whoa! tumbleweed-cli .. that's the cat's meow! Thank you so much Joe! What a gem!
Cheers,
-pablo I firmly disagree, having seen the results on some machines, where the admin had used TW-cli to move back to a snapshot of ~2 months old. Meanwhile the move to /usr/etc happened, and they ended up with borked servers. If you want to move back and forward between snapshots, use btrfs, it's meant to do this
Hi Pablo and Knurpht, I AGREE with Knurpht that *if* I had to go backwards, I would ALWAYS use snapper/btrfs to rollback to prior snapshot. Going that route would be especially important if some major fs change occured like the /usr/etc mentioned or even the bigger /usr migration. Doing the snapper/btrfs rollback would also rollback your install to history repos that were being used when that snapshot was created, HOWEVER, if you rolled back far enough that the build was no longer 1 of the 20 history builds then you would not be able to install anything new until you switched to one of the history builds. Having said that, tw-cli will only let you switch to one of the 20 builds that history is maintained for so you would get an error if try to switch to a history build which is no longer available. Those builds are the exact snapshots of the day that build was published, you just don't have to worry about the build in the repo being updated out from under you. FWIW, the issue that Knurpht mentions is the same case if you were someone that updated using the downloaded ISO file and then tried to update back to an older ISO file. TW is very fast moving, therefore only real reason I would rollback is if the build I updated too introduced a problem with something that was important and that I needed to be working. I alawya monitor the QA site to see which builds are available, what the stats are for the build, and what issues the builds have and therefore when I update I don't expect to be rolling back becuase I don't update to a build that has issues with something I care about. I have never had to rollback to a previous snapshot and have only needed to switch back to a prior kernel 1 time. Feel free to reach out to me off list if you want more details or have other questions. -- Regards, Joe
On 7/24/23 12:22, Pablo Sanchez wrote:
[ trimmed ]
If you use the tumbleweed-cli package, then
Whoa! tumbleweed-cli .. that's the cat's meow! Thank you so much Joe! What a gem!
Hi Pablo, Glad you liked it! After installing the package ( it's just a shell script ), remember to do tumbleweed init # To initialze your setup to the 20 history repos Then going forward you decide when you want to switch to a new TW build by doing tumbleweed switch YYYYMMDD After doing that you can do the normal 'zypper dup' to update to that build. I've been using it for the last few years and it works great. -- Regards, Joe
On 2023-07-24 12:29, Joe Salmeri wrote:
Hi Pablo,
Glad you liked it!
After installing the package ( it's just a shell script ), remember to do
tumbleweed init # To initialze your setup to the 20 history repos
Hey Joe, Thank you. Yah, when I initially I ran it, it promptly told me to init.
Then going forward you decide when you want to switch to a new TW build by doing
tumbleweed switch YYYYMMDD
After doing that you can do the normal 'zypper dup' to update to that build.
I've been using it for the last few years and it works great.
My plan is to use the data to send me an email when there's a new drop. As I'm using my machines for 'production', I want to be careful. Thank you for the pointer though! Cheers, -pablo
On 24/07/2023 18.37, Pablo Sanchez wrote:
Yah, when I initially I ran it, it promptly told me to init.
It seems, init already makes you use a fixed snapshot https://github.com/boombatower/tumbleweed-cli/blob/master/tumbleweed#L74 If you don't want that, you need tumbleweed-cli uninit
On 7/24/23 22:35, Bernhard M. Wiedemann via openSUSE Factory wrote:
On 24/07/2023 18.37, Pablo Sanchez wrote:
Yah, when I initially I ran it, it promptly told me to init.
It seems, init already makes you use a fixed snapshot https://github.com/boombatower/tumbleweed-cli/blob/master/tumbleweed#L74
If you don't want that, you need tumbleweed-cli uninit
Yes, and that ensures that if you need to install something else that you are getting it from the same fixed snapshot as you would if you had originally installed from there. That is one of the big benefits, because if you are pointed to latest TW snapshots, now you could get into trouble with mixed or unresolved package versions, unless you first did the zypper dup before installing the new package. I tend to update every couple weeks ( to stay within the 20 history snapshots ) and pay attention status of the snapshot I am upgrading too. -- Regards, Joe
Pablo's suggestion aside, what I'm still missing is a low-frequency TW Newsfeed or Mailing lists, which announces breaking changes and manual interactions or heads-up. According to my knowledge the Factory mailinglist is the place to get news about what's going on in TW, but the mailing list is typically noisy for this purpose. Something like *cough* https://archlinux.org/news/ *cough* but for Tumbleweed would be super nice to have. Anyone has already a good setup/idea for a low-frequency, low-noise information channel on breaking/crucial changes for TW? If a RSS feed exists, we could further integrate this into the tumbleweed-cli as well, so users would get those information displayed before they update directly in their terminal. Best, phoenix
Felix Niederwanger wrote:
[...] Anyone has already a good setup/idea for a low-frequency, low-noise information channel on breaking/crucial changes for TW? If a RSS feed exists, we could further integrate this into the tumbleweed-cli as well, so users would get those information displayed before they update directly in their terminal.
https://review.tumbleweed.boombatower.com/ cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Software Solutions Germany GmbH, GF: Ivo Totev HRB 36809 (AG Nürnberg)
On Tue, Jul 25, 2023 at 1:58 PM Ludwig Nussel <ludwig.nussel@suse.de> wrote:
Felix Niederwanger wrote:
[...] Anyone has already a good setup/idea for a low-frequency, low-noise information channel on breaking/crucial changes for TW? If a RSS feed exists, we could further integrate this into the tumbleweed-cli as well, so users would get those information displayed before they update directly in their terminal.
The newest one is from 2021-07-12
07-24 just dropped Den tis 25 juli 2023 kl 13:02 skrev Andrei Borzenkov <arvidjaar@gmail.com>:
On Tue, Jul 25, 2023 at 1:58 PM Ludwig Nussel <ludwig.nussel@suse.de> wrote:
Felix Niederwanger wrote:
[...] Anyone has already a good setup/idea for a low-frequency, low-noise information channel on breaking/crucial changes for TW? If a RSS feed exists, we could further integrate this into the tumbleweed-cli as well, so users would get those information displayed before they update directly in their terminal.
The newest one is from 2021-07-12
On Tue, 2023-07-25 at 13:11 +0200, Luna Jernberg wrote:
07-24 just dropped
2021-07-12 - mind the year 2021. The project looks pretty much abandoned, at least judging from the latest snapshots.
Den tis 25 juli 2023 kl 13:02 skrev Andrei Borzenkov <arvidjaar@gmail.com>:
On Tue, Jul 25, 2023 at 1:58 PM Ludwig Nussel <ludwig.nussel@suse.de> wrote:
Felix Niederwanger wrote:
[...] Anyone has already a good setup/idea for a low-frequency, low- noise information channel on breaking/crucial changes for TW? If a RSS feed exists, we could further integrate this into the tumbleweed-cli as well, so users would get those information displayed before they update directly in their terminal.
The newest one is from 2021-07-12
Been a lot of snapshots since then: https://openqa.opensuse.org/group_overview/1 Den tis 25 juli 2023 kl 13:31 skrev Felix Niederwanger <felix.niederwanger@suse.de>:
On Tue, 2023-07-25 at 13:11 +0200, Luna Jernberg wrote:
07-24 just dropped
2021-07-12 - mind the year 2021.
The project looks pretty much abandoned, at least judging from the latest snapshots.
Den tis 25 juli 2023 kl 13:02 skrev Andrei Borzenkov <arvidjaar@gmail.com>:
On Tue, Jul 25, 2023 at 1:58 PM Ludwig Nussel <ludwig.nussel@suse.de> wrote:
Felix Niederwanger wrote:
[...] Anyone has already a good setup/idea for a low-frequency, low- noise information channel on breaking/crucial changes for TW? If a RSS feed exists, we could further integrate this into the tumbleweed-cli as well, so users would get those information displayed before they update directly in their terminal.
The newest one is from 2021-07-12
On 7/25/23 07:30, Felix Niederwanger wrote:
On Tue, 2023-07-25 at 13:11 +0200, Luna Jernberg wrote:
07-24 just dropped 2021-07-12 - mind the year 2021.
The project looks pretty much abandoned, at least judging from the latest snapshots.
Den tis 25 juli 2023 kl 13:02 skrev Andrei Borzenkov <arvidjaar@gmail.com>:
On Tue, Jul 25, 2023 at 1:58 PM Ludwig Nussel <ludwig.nussel@suse.de> wrote:
Felix Niederwanger wrote:
[...] Anyone has already a good setup/idea for a low-frequency, low- noise information channel on breaking/crucial changes for TW? If a RSS feed exists, we could further integrate this into the tumbleweed-cli as well, so users would get those information displayed before they update directly in their terminal. https://review.tumbleweed.boombatower.com/
The newest one is from 2021-07-12
I used to follow that but something broke with the message downloads that it got causing missed days and the issue was never fixed. It seems that the author didn't want to skip those missing days ( which seems like that was the right solution to me ) and therefore it has just sat there broken. I now use the QA website and look at the stats for each build focusing on the soft failed and failed items to determine if they are for items that are critical to my work setup and use that to determine which of the 20 history builds to move to next. So far that has worked well -- Regards, Joe
Am 25.07.23 um 18:34 schrieb Joe Salmeri: .....
exists, we could further integrate this into the tumbleweed-cli as well, so users would get those information displayed before they update directly in their terminal. https://review.tumbleweed.boombatower.com/
The newest one is from 2021-07-12
I used to follow that but something broke with the message downloads that it got causing missed days and the issue was never fixed.
It seems that the author didn't want to skip those missing days ( which seems like that was the right solution to me ) and therefore it has just sat there broken.
I now use the QA website and look at the stats for each build focusing on the soft failed and failed items to determine if they are for items that are critical to my work setup and use that to determine which of the 20 history builds to move to next.
So far that has worked well
well the
provided much more info's, because there where links to the bugs and to the mails, a wonderful place to get in a easy end-user way all info's for all tumbleweed snapshots. maybe jimmy ore somebody else who is able to do could start another try to fix the issue? would be great. i am (and as i read here other people also) are waiting since a long time for this fix. many thanks in advance, simoN -- www.becherer.de
On 7/25/23 13:35, Simon Becherer wrote:
Am 25.07.23 um 18:34 schrieb Joe Salmeri:
.....
> exists, we could further integrate this into the tumbleweed-cli > as > well, so users would get those information displayed before > they update > directly in their terminal. https://review.tumbleweed.boombatower.com/
The newest one is from 2021-07-12
I used to follow that but something broke with the message downloads that it got causing missed days and the issue was never fixed.
It seems that the author didn't want to skip those missing days ( which seems like that was the right solution to me ) and therefore it has just sat there broken.
I now use the QA website and look at the stats for each build focusing on the soft failed and failed items to determine if they are for items that are critical to my work setup and use that to determine which of the 20 history builds to move to next.
So far that has worked well
well the
provided much more info's, because there where links to the bugs and to the mails, a wonderful place to get in a easy end-user way all info's for all tumbleweed snapshots.
maybe jimmy ore somebody else who is able to do could start another try to fix the issue? would be great. i am (and as i read here other people also) are waiting since a long time for this fix. many thanks in advance,
simoN
I don't disagree with you, however, it has not been maintained for 2+ years now. I still believe the solution was to just ignore the missing data. I believe someone else found that if that missing data had been skipped it would have continued on. At one point there was an issue with the message download which I believe was related to the missing data. As fast as TW moves though, without information on current builds it is useless. FYI, if you go to the link above and click on Review broken by mailing list bug <https://github.com/boombatower/tumbleweed-review/issues/18> which points to https://github.com/boombatower/tumbleweed-review/issues/18 You can read some discussion about the long standing issue. I gave up waiting after a few months... Regards, Joe
On Tuesday, July 25, 2023 3:39:14 PM CDT Joe Salmeri wrote:
You can read some discussion about the long standing issue.
I gave up waiting after a few months...
Just tried it and looks like mailing list still provides an invalid archive. If someone want to fix the mailing list or implement a new way of getting the mail I'm happy to run it. Apparently, having a corrupt export method is a feature. -- Jimmy
On 28. 07. 23 6:13, Jimmy Berry wrote:
On Tuesday, July 25, 2023 3:39:14 PM CDT Joe Salmeri wrote:
You can read some discussion about the long standing issue.
I gave up waiting after a few months...
Just tried it and looks like mailing list still provides an invalid archive. If someone want to fix the mailing list or implement a new way of getting the mail I'm happy to run it.
Apparently, having a corrupt export method is a feature.
Having the bug fixed would be preferable. However, out of curiosity, why not do as suggested in the openSUSE Progress tracker issue [0] and export half a month instead of exporting the whole month? [0]: https://progress.opensuse.org/issues/95756#note-5
On Thu, 27 Jul 2023 23:13:22 -0500, Jimmy Berry <jimmy@boombatower.com> wrote:
On Tuesday, July 25, 2023 3:39:14 PM CDT Joe Salmeri wrote:
You can read some discussion about the long standing issue. I gave up waiting after a few months...
Just tried it and looks like mailing list still provides an invalid archive. If someone want to fix the mailing list or implement a new way of getting the mail I'm happy to run it.
Apparently, having a corrupt export method is a feature.
Here is some information about the archive. I hacked the URLs that were being tried in [1] and [2], removing the start and end parameters. === download: $ wget -P dl 'https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/export/f...' 'wget' did not report any errors. === file size: $ stat -c '%s' dl/factory@lists.opensuse.org-2021-07.mbox.gz 90009028 === uncompressed data available: $ zcat dl/factory@lists.opensuse.org-2021-07.mbox.gz |wc -c gzip: dl/factory@lists.opensuse.org-2021-07.mbox.gz: unexpected end of file 317069695 === file: $ file dl/factory@lists.opensuse.org-2021-07.mbox.gz dl/factory@lists.opensuse.org-2021-07.mbox.gz: gzip compressed data, from Unix, original size modulo 2^32 2147122926 gzip compressed data, unknown method, ASCII, has CRC, from FAT filesystem (MS-DOS, OS/2, NT), original size modulo 2^32 2147122926 'file' reports "from Unix" and "from FAT filesystem". What does that mean? === difference of the "original size" reported by 'file' from 2 GiB: $ expr 2147122926 - 256 \* 256 \* 256 \* 128 -360722 That is very close to 2 GiB. Is a size limit being reached, especially since a FAT filesystem may be involved? === gzip file test: $ gzip -t dl/factory@lists.opensuse.org-2021-07.mbox.gz gzip: dl/factory@lists.opensuse.org-2021-07.mbox.gz: unexpected end of file This shows that the downloaded gzip archive is corrupt/truncated, not just the contained mbox file. === first, last posts in the archive: From hvogel@suse.de Fri Nov 11 12:45:37 2005 From jmscdba+tw@gmail.com Mon Jul 12 17:05:43 2021 This leads me to wonder about the URL specification. What is the "2021-07" supposed to do? [1] Issue: recent releases are missing on the site https://github.com/boombatower/tumbleweed-review/issues/18 [2] Ticket #95756: factory mailing list archives incomplete https://progress.opensuse.org/issues/95756 -- Robert Webb
Am 07.08.23 um 09:39 schrieb Robert Webb via openSUSE Factory:
On Thu, 27 Jul 2023 23:13:22 -0500, Jimmy Berry <jimmy@boombatower.com> wrote:
On Tuesday, July 25, 2023 3:39:14 PM CDT Joe Salmeri wrote:
You can read some discussion about the long standing issue. I gave up waiting after a few months...
Just tried it and looks like mailing list still provides an invalid archive. If someone want to fix the mailing list or implement a new way of getting the mail I'm happy to run it.
Apparently, having a corrupt export method is a feature.
Here is some information about the archive. I hacked the URLs that were being tried in [1] and [2], removing the start and end parameters.
=== download: $ wget -P dl 'https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/export/f...'
.... snip ......
This leads me to wonder about the URL specification. What is the "2021-07" supposed to do?
[1] Issue: recent releases are missing on the site https://github.com/boombatower/tumbleweed-review/issues/18
[2] Ticket #95756: factory mailing list archives incomplete https://progress.opensuse.org/issues/95756
-- Robert Webb
I am not an programmer, so maybe i do not understand complete where the problem with the corrupted mbox/zipfile is comming from, and of course that should be fixed. but if nobody does (or is able/willing to), why not do a ugly work around: for me the homepage: https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/latest?c... looks quite ok, even with a bigger count. why not use the homepage instead of the mailing list archive file? something like: wget -P dl https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/latest?c... then cat ./dl/latest\?count=100 |grep /archives/list/factory@lists.opensuse.org/thread/ >latest1.txt and now wget each line of this file latest1.txt and work with this files for the mail analyse? OR ist the complete homepage also not correct? (what i would have missed by take short a look at it) THEN we could do another work around: to set up a small mail receiving program who gets all the mails like a "normal" email program (thunderbird) from the factory mailing list. and writes this in a mbox file and jimmy could use this file for his analyses. - after a month or so the files could be deleted, also this work around should not be to complex to realize. - only a emailprogramm must run and periodically receive the mails and write the gz-mbox file on a server. simoN -- www.becherer.de
Am 25.07.23 um 08:38 schrieb Felix Niederwanger:
Pablo's suggestion aside, what I'm still missing is a low-frequency TW Newsfeed or Mailing lists, which announces breaking changes and manual interactions or heads-up.
According to my knowledge the Factory mailinglist is the place to get news about what's going on in TW, but the mailing list is typically noisy for this purpose. Something like *cough* https://archlinux.org/news/ *cough* but for Tumbleweed would be super nice to have.
Anyone has already a good setup/idea for a low-frequency, low-noise information channel on breaking/crucial changes for TW? If a RSS feed exists, we could further integrate this into the tumbleweed-cli as well, so users would get those information displayed before they update directly in their terminal.
There is already a low-volume list for important announcements: <https://lists.opensuse.org/archives/list/announce@lists.opensuse.org/>. It's just not really being used for technical changes, perhaps because it's hard to decide what might be important enough to announce. (Hard to decide if you can't anticipate the breakage.) Aaron
On 23.07.23 17:36, Pablo Sanchez wrote:
Hi everyone, Hi Pablo,
If no such list exists, can we create one? The list would only allow the following posts (from Dimstar .. :):
* New Tumbleweed snapshot ... * Tumbleweed - Review of the week ..
What do people think? I really like the idea.
In the past I always had a look at the URL Ludwig mentioned (https://review.tumbleweed.boombatower.com), but this project [0] is sadly not maintained anymore. [0] https://github.com/boombatower/tumbleweed-review
--- Pablo
dom -- Dominik Gedon Software Engineer SUSE Manager QE SUSE Software Solutions Germany GmbH Frankenstr. 146, 90461 Nuernberg, Germany Geschäftsfuehrer: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nuernberg)
Am 28.07.23 um 11:35 schrieb Dominik Gedon:
On 23.07.23 17:36, Pablo Sanchez wrote:
Hi everyone, Hi Pablo,
If no such list exists, can we create one? The list would only allow the following posts (from Dimstar .. :):
* New Tumbleweed snapshot ... * Tumbleweed - Review of the week ..
What do people think? I really like the idea.
In the past I always had a look at the URL Ludwig mentioned (https://review.tumbleweed.boombatower.com), but this project [0] is sadly not maintained anymore.
not really true, there is a problem in the mailing list archive porvided, that was never fixed if you know who is responsible for mailing list archive and it will be fixed, the project wourld work fine. jimmy (the maintainer) has replyed to the post here on the list in this morning time 6:13 simoN
[0] https://github.com/boombatower/tumbleweed-review
--- Pablo
dom
-- www.becherer.de
participants (17)
-
Aaron Puchert -
Andrei Borzenkov -
Bernhard M. Wiedemann -
Dominik Gedon -
Felix Niederwanger -
Jimmy Berry -
Joe Salmeri -
Johannes Kastl -
John Kizer -
Knurpht-openSUSE -
Ludwig Nussel -
Lukas Kucharczyk -
Luna Jernberg -
Manfred Hollstein -
Pablo Sanchez -
Robert Webb -
Simon Becherer