Re: [Evergreen] openSUSE 13.1 after 2016-11-01
Hi, Am 24.10.2016 um 09:11 schrieb Moser Helmut: > Can anybody here please answer the original question (besides tips about > distro change)? > It's very important for me too to know what to do after November 1st as I > have several 13.1 machines sitting there. Seeing how we were struggling up to now with 13.1 I see no way to officially extend the support further. Nevertheless I'm volunteering to accept patches if submitted through the maintenance mechanism but I would not call it official support until someone steps up to take the responsibility tracking security issues. Therefore the following facts: - currently there is noone after November who officially tracks updates - 13.1 has to be considered insecure officially - patches will be accepted if submitted from contributors - if people step up, support can be extended Wolfgang > -Ursprüngliche Nachricht- > Von: Evergreen [mailto:evergreen-boun...@lists.rosenauer.org] Im Auftrag von > Sebastian Niemeyer > Gesendet: Sonntag, 23. Oktober 2016 15:59 > An: oS Evergreen > Betreff: [Evergreen] openSUSE 13.1 after 2016-11-01 > > Hallo together, > > how are the plans for openSUSE 13.1 after 2016-11-01. Is there a change for a > longer support of the current evergreen release? > > Greetings > > Sebastian ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] latest samba update broken for Opensuse 13.1
Am 13.05.2016 um 17:23 schrieb Noel Power: > On 13/05/16 16:03, Manfred Schwarb wrote: >> Am 12.05.2016 um 22:56 schrieb Manfred Schwarb: > [...] >> There is now a repository for 13.1: >> http://download.opensuse.org/repositories/home:/npower:/update-os13.1-samba/standard/x86_64/ >> I tested it, and it works for me, FWIW. > so... this is in no way a supported repo, I don't even know how long it > will exist (probably until I get a mail from obs to clean stuff up) I > only built it because of the comment > >> I tried to build it myself, but somehow OBS seems to be broken: >> OBS installs outdated versions of libtdb, libtevent et al., >> although there are official updates available. > I didn't have any problem building it for 13.1, I don't know what plans > there are wrt evergreen community and provision of an update, don't > depend on the repo above, it may not exist for much longer We accept update requests or would pull in patches ourselves if we know what to pull. The repository above contains many changes compared to current 13.1 version and I cannot easily assess what the risk is to pull the full set. Wolfgang ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Missing securityfixes for ntpd
Hi, Am 04.05.2016 um 06:41 schrieb Ronny Peine: > Hello Evergreen-Team, > > as I can see in https://bugzilla.suse.com/show_bug.cgi?id=952611 most > likely all of the lately securityfixes for ntpd are missing in openSUSE > 13.1 (since Mai 2015). Would it be possible to maybe have the ntpd > version from openSUSE Leap 42.1? We try to avoid updates if not really required from a security perspective or because of critical issues. I'm wondering which security fixes you are referring to? From what I can see is that the 13.1 version is on par with the 13.2 version security wise. Are you saying the 13.2 version has open and known security problems because in that case I'm sure the openSUSE security team is also interested in them. Wolfgang ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
[Evergreen] testmail - ignore
___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] samba security update - badlock and friends
Am 16.04.2016 um 13:11 schrieb Christian Boltz: > Hello, > > Am Samstag, 16. April 2016, 12:40:47 CEST schrieb Michal Kubecek: >> On Sat, Apr 16, 2016 at 12:24:03AM +0200, Christian Boltz wrote: > > FYI: a quick test of the updated packages on one of my 13.1 machines > looks good. > >> But I'm not realy expert on this. So maybe >> >>> That said - I don't think having a separate update is a real problem >>> if both are released at the same time (or AppArmor first). >> >> might be the safest option after all. > > Indeed ;-) > > I just submitted the update: > https://build.opensuse.org/request/show/390298 For whatever reason it ended up in the openSUSE:Maintenance target instead of openSUSE:Evergreen:Maintenance. I've just did an SR https://build.opensuse.org/request/show/390300 You can revoke the other one. Thanks, Wolfgang ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] samba security update - badlock and friends
Am 16.04.2016 um 12:40 schrieb Michal Kubecek: > On Sat, Apr 16, 2016 at 12:24:03AM +0200, Christian Boltz wrote: >>> The samba update is submitted now to >>> openSUSE:Evergreen:Maintenance:4627 If you are going to submit the >>> AppArmor profile update, using this incident would be IMHO the best >>> option as that way both samba and profile update would be released at >>> once, preventing regressions. >> >> What is the best way to do this? >> I'd guess something like >> >> osc sr security:apparmor apparmor_2_8 \ >> openSUSE:Evergreen:Maintenance:4627 WHATEVER >> >> but I'm not sure what I should use for WHATEVER ;-) > > I assume apparmor.openSUSE_13.1_Update > > Or maybe rather > > osc mr -a Evergreen:MaintenanceProject \ > --incident-project openSUSE:Evergreen:Maintenance:4627 \ > security:apparmor apparmor_2_8 openSUSE:13.1:Update Just submit it via SR or MR without anything special (with the a Evergreen:MaintenanceProject for MR though. I can merge incoming requests afterwards. Thanks, Wolfgang ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] 13.1 systemd update breaks build - and also *runtime* :(
Am 07.02.2016 um 18:41 schrieb Manfred Hollstein: > Hi there, > > On Wed, 03 Feb 2016, 17:27:06 +0100, Olaf Hering wrote: >> On Wed, Feb 03, Marcus Meissner wrote: >> >>> Please check if this helps. >> >> Thanks. At least the i586 part of 13.1 is in "blocked/scheduled" state >> again. I think the x86_64 part will catch up soon. > > this is not related with any _build_ problems, but rather _using_ the > systemd-210 update. Before (using systemd-208) my systems started > without any issue, but since systemd-210 named doesn't start anymore. > Here is a message from /var/log/messages indicating that there is a > dependency cycle: > > systemd[1]: Job remote-fs.target/stop deleted to break ordering cycle > starting with named.service/stop > > Normally I would expect that named will start up as a result of this > decision, but it does not - which is horrible because all my local names > do not get resolved anymore. Yeah, I could add all those names to > /etc/hosts, but there are way too many systems and using named for it > used to work since years. FWIW, I have now downgraded to 208 again and > locked all relevant packages, and everything is smooth again... > > How and where shall I report this bug? Still openSUSE bugzilla? I think openSUSE bugzilla makes sense in any case. For systemd I'm not sure who can pick it up for 13.1 though. The update itself was not released yet from the Evergreen maintenance project so I'm not exactly sure what changed etc. Wolfgang signature.asc Description: OpenPGP digital signature ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] 13.1 systemd update breaks build
Am 03.02.2016 um 16:46 schrieb Olaf Hering: > Not sure if this is already an Evergreen or still regular update thing. > > openSUSE_13.1x86_64 unresolvable: nothing provides > this-is-only-for-build-envs needed by libudev-mini1 > nothing provides this-is-only-for-build-envs needed by udev-mini > > Seen in various projects, including PMBS:Essentials/ffmpeg systemd was released still from the official maintenance queue. That does not mean necessarily that we do not have to do something about it from our side though. Any help is appreciated. Wolfgang ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] phpMyAdmin needs update
Am 31.01.2016 um 22:10 schrieb Marcus Meissner: > No > > OSC branch -M openSUSE:13.1:Update phpMyAdmin > > Then OSC SR to send it back. > > Branxhing from maintennance projects ist almost always incorrect. hmm, so it seems it did work fine though. Yes, it's not the usual case but the above would create the branch not based on the running maintenance process I guess? I have to admit that I often changed these projects in place but that is only possible because I have the needed rights there. Wolfgang ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
