From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id AEF9015800D for ; Sun, 2 Jul 2023 22:01:33 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D5ED4E088A; Sun, 2 Jul 2023 22:01:32 +0000 (UTC) Received: from mail-yb1-xb2d.google.com (mail-yb1-xb2d.google.com [IPv6:2607:f8b0:4864:20::b2d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id CF8A9E088A for ; Sun, 2 Jul 2023 22:01:32 +0000 (UTC) Received: by mail-yb1-xb2d.google.com with SMTP id 3f1490d57ef6-c50c797c31bso955724276.0 for ; Sun, 02 Jul 2023 15:01:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1688335292; x=1690927292; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=7U5f+wcIABjdvJ2O0gWpLDsJHLdYz7lf5YCTeeT30YU=; b=JnJ9KipTvtmS9OicDKuNfjm0tDcOHXwz/5G2Re9MZNgTRrxYqRcrOKPP+3FZxMcHz8 PgMMWk57G/fd5xbPrwkWIUsbn08EjHRVvHSJCRsow6ndknNHfEGJ8GrxRq3Nf320QCkC b9fUYolj5qmoB2fAtAzBo+tecZhdCqim+dwVHbGSl6Ru4SudeOeXSRgOXCD9O9SVvyLE iCsHvYAQuSFKrfdsKfJ9eH9/17pEHHiA9KK7V2fx9A6zgs2m2A0wmitikev1hfBFkFjl wOOsedax4mPzrBVEhAvrZSRfbh8Fq1LQR2KGN9iOrrm+vHg9RDRCg82Cp0GH0YhmHxP1 J/oA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688335292; x=1690927292; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=7U5f+wcIABjdvJ2O0gWpLDsJHLdYz7lf5YCTeeT30YU=; b=BAnHq22b8WxaXRITW4uyICZYRBHtQQKy2lVJ62vhHc434VaHf2/3wOqxwW+37QuTxA qxxv8IABoB9Lw2LGddMejiWk2ORDrklS26qzDoZtpKQPdPXCVhxvlbXbRIy1fSC27y2w hrYG4iwRAAowgictAHyqp89OHxls8V5YhLqUzaxjw2V4kJ90PnxfjbjlfpZeQbaPneFq Tvks+6StwXQMF1qA2F1s65Z2PMuF7JTU3sYbEjw1/qLRsZBBch6UC8nOD/MTYtq48E5E NT3mD14be+zpt5FZFiyVhGePiJeJLyE66oDugG7eMRfHf0gAv1+6epMFtrmamHR5Tkas sk4A== X-Gm-Message-State: ABy/qLZ+JqM4MNdVxh/z9pcsrRK7i+YKXaCprxg5bNeImACHaPg4EeHB EzLy6rJw9c5jT2w9H0kZgcox170jcGx8/VlKR5Mc3AODxlQrcSAupl0= X-Google-Smtp-Source: APBJJlHy+TniF6y2bpUpYk/83Cti9ctKmXdI6JHR4RtuKnTud95fD5YJS2y8ncDh/rCa1Ms7M7ebIunEmAV2A8yKL5c= X-Received: by 2002:a25:f208:0:b0:c2d:8a7f:8dd1 with SMTP id i8-20020a25f208000000b00c2d8a7f8dd1mr8072583ybe.24.1688335292063; Sun, 02 Jul 2023 15:01:32 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-soc@lists.gentoo.org Reply-to: gentoo-soc@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 From: Kulikov Stepan Date: Mon, 3 Jul 2023 01:01:21 +0300 Message-ID: Subject: [gentoo-soc] Week 5 report, Automated Gentoo system updater To: gentoo-soc@lists.gentoo.org Content-Type: multipart/alternative; boundary="00000000000058655e05ff883136" X-Archives-Salt: 33983f71-5aea-4b60-95b6-18aff432b7bb X-Archives-Hash: a59a42e7feab231cb8ff3d7e4bc82a0d --00000000000058655e05ff883136 Content-Type: text/plain; charset="UTF-8" Here is my report for the 5th week. I will be brief because all details are in the Gentoo blog . *Week 5 Wrap-Up*: Got some community feedback, overall it was a good experience because I've got some new ideas and insights about the project. Forum discussion is still ongoing. Had a small breakthrough in coding the parser. To make it work I had to rewrite some parts of the program, but it's good because it improved the overall stability. I also updated and re-tested some Docker containers. Due to the dynamic nature of Gentoo Linux, some container just become unusable after a couple weeks. *Week 6 Plan*: For the next week I want to add some error handling to the parser. This means I will have to find some different ways to cause Portage to break, and then try to make parser understand the errors that have occurred. After that is done, I can focus on using this information to create nice-looking update reports. That's all, have a good week everyone! --- Best regards, Kulikov Stepan (Lab-Brat) --00000000000058655e05ff883136 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Here is my report for the 5th week.
I will = be brief because all details are in the Gentoo=C2=A0blog.=C2=A0

= Week 5=C2=A0Wrap-Up:
Got some community feedback, over= all it was a good experience=C2=A0
because I've got some new = ideas and insights about the project.=C2=A0
Forum discussion is s= till ongoing.

Had a small breakthrough in coding t= he parser. To make it work I=C2=A0
had to rewrite some parts of t= he program, but it's good because it=C2=A0
improved the overa= ll stability.

I also updated and re-tested some Do= cker containers. Due to the=C2=A0
dynamic nature of Gentoo Linux,= some container just become unusable=C2=A0
after a couple weeks.= =C2=A0


Week 6=C2=A0Plan:
For the next week I want = to add some error handling to the parser.=C2=A0
This means I will= have to find some different ways to cause Portage to break,=C2=A0
and then try to make parser understand the errors that have occurred.
=
After that is done, I can focus on using this information to create nic= e-looking update reports.

That= 's all, have a good week everyone!

<= div>---
Best regards,
Kulikov Stepan (Lab-Brat)
--00000000000058655e05ff883136--