From dh at dotlan.net Mon Jul 4 00:11:52 2022 From: dh at dotlan.net (Daniel Hoffend) Date: Mon, 4 Jul 2022 00:11:52 +0200 Subject: Repository changes around the OBS In-Reply-To: <2592230.X9hSmTKtgW@delle> References: <17af7d7d3b7b4358be3acdc05eef7dcc@kube> <2592230.X9hSmTKtgW@delle> Message-ID: <4f52096a-835a-fcbb-5d95-9ddfa3323d7b@dotlan.net> Same here I know i'm not that active any more compared to couple years ago. Not sure If I find the time to actively maintain the Debian packages, but at least I'm maintaining 3 debian installations. It's a bit sad, that the old irc times are over where we could chat of the future roadmap. I still try to fix some bugs if I find them ... Would be nice if someone could have hat look at them on git from time to time. -- Regards Daniel Am 13.06.2022 um 23:21 schrieb Christoph Erhardt: > Hi Christian, > > On Monday, 13 June 2022 10:29:09 CEST Christian Mollekopf wrote: >> This means, going forward: >> * The Kolab:16 project represents the current stable version of Kolab. >> * The Kolab:16:Testing project are the updates for the next stable version >> of Kolab. >> * The Kolab:16:Testing:Candidate repository is a staging >> repository for Kolab:16:Testing. > I welcome this change as it should make things more stable and reduce the > potential for breakage. > >> Please also note that you should no longer directly push updates to Kolab:16 >> (for those with permissions), because the changes will directly be >> reflected on the mirror. If you have access and would like to participate >> in the release process then please contact me, if not we will revoke write >> access to that specific project. > I have write access and would like to remain an active contributor to the > project. > > Best, > Christoph > > > _______________________________________________ > users mailing list > users at lists.kolab.org > https://lists.kolab.org/mailman/listinfo/users From dh at dotlan.net Mon Jul 4 00:21:09 2022 From: dh at dotlan.net (Daniel Hoffend) Date: Mon, 4 Jul 2022 00:21:09 +0200 Subject: New selfcontained packaging for roundcube and guam In-Reply-To: References: Message-ID: <95394cff-4a92-eb00-150d-40355d4592e5@dotlan.net> Hi I can understand your decisions when it comes to dependency hell of php, python, erlang, javascript and other projects that heavyly rely on external additional packages. But the "skins" is something I would like to see kept seperate. For my installations I usually take the debian source skin package, change the colors (in _variables.less), add a logo, rename the package and rebuild and I'm done (1 short bash script). The new structure would likely work as well, but would be a bit more work The next time I've to update, I'll take a closer look on what things break. I'll have to take a closer look at my ansible role later. Regards Daniel Am 13.06.2022 um 10:40 schrieb Christian Mollekopf: > Hi, > > To reduce packaging effort on new platforms roundcubemail and guam have been turned into selfcontained packages that we'll use going forward. > You may already have noticed this if you are using the Kolab:16 repository directly from the OBS. > > For roundcube that means that roundcubemail-1.5.2 replaces: > * roundcubemail-plugins-* > * roundcubemail-skins-* > > The buildroundcubemailtarball.sh script now assembles a tarball that includes the plugins and skins and is checked into the OBS. > > > For guam-0.9.12 the erlang dependencies are vendorized, and on debian we currently replace: > * erlang-eimap > * erlang-goldrush > * erlang-lager > * erlang-syslog > > We wouldn't strictly have to replace those packages, but we currently conflict with files (could be improved in the packaging). > > > I understand if this is not everyones preferred method, but with recent distributions lacking a lot of the dependencies that we traditionally require, > and a vast reduction in complexity of the packaging itself, I hope you can understand why this is happening. > > To opt-out a separate branch project on the OBS would have to be maintained where the *-selfcontained packages could be disabled. > Please note that the traditional packages will no longer receive updates from our side. > > I tried making sure that all package managers automatically upgrade to the new packages, but it's of course possible that I missed some upgrade scenarios that could be solved better, help is welcome. > > Cheers, > Christian > _______________________________________________ > users mailing list > users at lists.kolab.org > https://lists.kolab.org/mailman/listinfo/users From mollekopf at apheleia-it.ch Tue Jul 5 17:25:40 2022 From: mollekopf at apheleia-it.ch (Christian Mollekopf) Date: Tue, 05 Jul 2022 17:25:40 +0200 Subject: Repository changes around the OBS In-Reply-To: <4f52096a-835a-fcbb-5d95-9ddfa3323d7b@dotlan.net> References: <17af7d7d3b7b4358be3acdc05eef7dcc@kube> <2592230.X9hSmTKtgW@delle> <4f52096a-835a-fcbb-5d95-9ddfa3323d7b@dotlan.net> Message-ID: <89ed4e1a5b8f405eaa8e36ea6495d79b@kube> On Monday, 4 July 2022 00:11:52 CEST you wrote: > Same here > Hi Daniel, > I know i'm not that active any more compared to couple years ago. Not > sure If I find the time to actively maintain the Debian packages, but at > least I'm maintaining 3 debian installations. It's a bit sad, that the > old irc times are over where we could chat of the future roadmap. > True, we don't currently have a suitable replacement for that. > I still try to fix some bugs if I find them ... Would be nice if someone > could have hat look at them on git from time to time. Feel free to raise some topics here if you feel they deserve some attention. Cheers, Christian > > > -- > Regards > Daniel > > > Am 13.06.2022 um 23:21 schrieb Christoph Erhardt: > > Hi Christian, > > > > On Monday, 13 June 2022 10:29:09 CEST Christian Mollekopf wrote: > >> This means, going forward: > >> * The Kolab:16 project represents the current stable version of Kolab. > >> * The Kolab:16:Testing project are the updates for the next stable version > >> of Kolab. > >> * The Kolab:16:Testing:Candidate repository is a staging > >> repository for Kolab:16:Testing. > > I welcome this change as it should make things more stable and reduce the > > potential for breakage. > > > >> Please also note that you should no longer directly push updates to Kolab:16 > >> (for those with permissions), because the changes will directly be > >> reflected on the mirror. If you have access and would like to participate > >> in the release process then please contact me, if not we will revoke write > >> access to that specific project. > > I have write access and would like to remain an active contributor to the > > project. > > > > Best, > > Christoph > > > > > > _______________________________________________ > > users mailing list > > users at lists.kolab.org > > https://lists.kolab.org/mailman/listinfo/users > _______________________________________________ > users mailing list > users at lists.kolab.org > https://lists.kolab.org/mailman/listinfo/users >