Fedora-Cloud-33-20201227.0 compose check report
No missing expected images. Soft failed openQA tests: 1/7 (x86_64), 1/7 (aarch64) (Tests completed, but using a workaround for a known bug) ID: 747200 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/747200 ID: 747207 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/747207 Passed openQA tests: 6/7 (x86_64), 6/7 (aarch64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Self Introduction -- Derek Pressnall
Hello fellow developers. I've joined this list quite a while ago, mostly to keep a pulse on the Fedora development community, but also to look to become a package contributor. But before getting to that, a few words about myself. I've been "into computers" since mid-80's, started off with a 4.77 Mhz 8088 (IBM PCjr). I learned Unix in the early 90's on an IBM AIX system, where I picked up C programming and sysadmin experience. Which eventually took me into the world of Linux (I think it was kernel version 0.12, came on a boot disk and root disk pair I grabbed off a BBS, long before there was easy general public Internet access). Anyway I've been focused on Red Hat based distros for the past 15 years, and at my current employer I oversee about 700 systems installed at customer locations (where I was the resource responsible for packaging our applications and creating system build images). Any way, what I'd like to give back to the community is a really nice backup system called Snebu (Simple Network Encrypting Backup Utility). I initially developed this more than 8 years ago since there wasn't anything else that fit my needs -- I used it to back up my personal systems, and also in some lab environments. I've read plenty of rants that have been posted about how backups are either too difficult to set up, or don't support multiple clients, or require a repository encryption password to be placed in plain text on clients, and other issues people have. With that in mind, I believe that Snebu can be just what people want. Before going through and submitting the package for formal review, I'd appreciate some feedback on what I have packaged up so far. The current release is at https://github.com/derekp7/snebu/releases/download/v1.1.0/snebu-1.1.0-1.fc33.src.rpm, and the project web site is at https://www.snebu.com. The main features that it has that are interesting: It maintains a centralized package database on the server (using SQLite3) tracking backup sets and metadata; actual files are stored in the filesystem as lzop compressed files using a file hash for the file name which leads to full cross-system file level de-duplication (so no proprietary file formats); uses a snapshot style backup strategy; it uses GNU tar as a serialization format to shuffle backups to the server which leads to how the public key encryption support was added by developing "tarcrypt"; and it works in single-system installs, client-push or server-pull backups, with no agent required on the client. Another interesting project that I may spin off is the above mentioned "tarcrypt" command. This acts as a filter for tar files, which adds RSA key data to the header (passphrase protected private key, public key, HMAC signatures, etc), compresses and encrypts the file contents while keeping standard tar headers in place (with the additional encryption metadata added via extended PAX headers). The details on this project is at https://www.snebu.com/tarcrypt.html. So far tarcrypt is part of the Snebu repository, but if there is interest then it may eventually be spun out as an independent project. BTW, the current .src.rpm file for Snebu mentioned above has passed through a valid build using the Fedora "mock" utility, and passed rpmlint. The only error rpmlint shows is: snebu.src: W: spelling-error %description -l en_US de -> DE, ed, d Not sure what that error is saying, as the text at the end of the message doesn't appear anywhere in the .spec file. Thanks, and I look forward to your feedback. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora Screnshots
Hi, I was taking a look at /etc/appstream.conf and I see there is a screenshot website for Debian and Ubuntu: ``` [debian] ScreenshotUrl=http://screenshots.debian.net [opensuse] ScreenshotUrl=http://software.opensuse.org/package ``` (There is one of Ubuntu but really does not exist) Is there something alike for Fedora? And just out of curiosity, the screenshots that we can see Plasma Discover are from upstream? Thanks in advance! -- -- Sergio Belkin LPIC-2 Certified - http://www.lpi.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Popularity contest for Fedora
Hey all, While installing Debian for setting up an appliance, I discovered they have something called a “popularity contest” that, according to my understanding, allows for package statistics to be gathered and used by the developers/packagers. Has anything like this been considered for Fedora? It would actually be kind of nice to see installation statistics of my packages, if only to determine if I’m the only one using them. :) Ron ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Stale proven packagers
Gary Buhrmaster wrote: > Arguably those with elevated access (provenpackagers(*)) > should be required to use a hardware token such > as a FIDO2 authenticators with biometrics and/or > PIN required I'm in favor of complementing the FAS passphrase with a second factor. I'm against any attempt to require biometrics. These are my reasons: · Biometric identifiers aren't cleanly separated from identity. They are more akin to your username than to your passphrase. A random key or a passphrase can be revoked and replaced if it gets out. Fingers and faces are very difficult to replace. And yes they can get out. Once your fingerprint has been scanned and turned into data, those data can be copied like any other secret. You also leave your fingerprints on everything you touch. · Such a requirement is unenforceable. A client can never prove to a server that it has a certain piece of hardware. It can only prove that it knows a certain secret – or two secrets since we're talking about two-factor authentication. Whether the secrets are stored on a hard disk, in a Yubikey, in somebody's brain or in somebody's retina, is unknown to the server. Before authentication it must be assumed that the client may be an attacker who is lying about everything they can lie about. Some protocol might allow the client to claim that it used a fingerprint reader, but as far as the server knows the attacker might just be using a stored scan of the real user's fingerprint. · Biometrics is low-grade security for use where convenience takes precedence. If somebody can't remember a good PIN, then it's better for them to unlock their phone with their fingerprint than to choose "" for their PIN. Strong crypto keys and hardware tokens are better where security requirements are higher, like in two-factor authentication. Requiring biometrics is effectively the same as prohibiting stronger authentication methods, which is a stupid thing to do. Björn Persson pgpUh0Z_Vy5p9.pgp Description: OpenPGP digital signatur ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
openvdb-8.0.0 so version change
Hello team, openvdb-8.0.0 is released upstream meaning the soversion is now 8.0 resulting a break on dependent packages like OpenImageIO and Blender as tested on COPR blender[1]. The commit is already complete https://src.fedoraproject.org/rpms/openvdb and it is a matter of building for proven packagers. Thanks in advance Reference: [1] https://copr.fedorainfracloud.org/coprs/luya/blender-egl/build/1848958/ -- Luya Tshimbalanga Fedora Design Team Fedora Design Suite maintainer ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: eclipse-photran builds failed/not included since F32
Am Samstag, dem 26.12.2020 um 22:10 +0100 schrieb Dominik 'Rathann' Mierzejewski: > On Wednesday, 23 December 2020 at 02:13, Mark E. Fuller wrote: > > I'm not quite sure where else to direct this - I intermittently do > > some > > Fortran work and the Eclipse plugin (eclipse-photran) appears to > > have > > disappeared from the repos since F32. Looking at Koji, releng was > > previously doing the builds for it . Does anyone know anymore about > > this including whether eclipse-photran is being (intentionally) > > dropped > > and alternatives? > > It was retired 7 months ago after being orphaned[1]. To bring it > back, > you'd have to become the new maintainer, submit a new review request > and > ask for unretirement. Thank you very much. For the next question, since I have never built or maintained packages before, can someone point me to a "dummies" guide if such a thing exists? I would be happy to try to take over the package and learn something along the way. > > Regards, > Dominik > > [1] https://src.fedoraproject.org/rpms/eclipse-photran > > -- > Fedora https://getfedora.org | RPM Fusion http://rpmfusion.org > There should be a science of discontent. People need hard times and > oppression to develop psychic muscles. > -- from "Collected Sayings of Muad'Dib" by the Princess > Irulan > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org -- Mark E. Fuller, Ph.D. Robensstraße 57 52070 Aachen +49 (0)1577-1848188 +1 401-366-2771 mark.e.ful...@gmail.com mark.e.ful...@gmx.de @mefuller:matrix.org https://mefuller.github.io/ signature.asc Description: This is a digitally signed message part ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: eclipse-photran builds failed/not included since F32
On Wednesday, 23 December 2020 at 02:13, Mark E. Fuller wrote: > I'm not quite sure where else to direct this - I intermittently do some > Fortran work and the Eclipse plugin (eclipse-photran) appears to have > disappeared from the repos since F32. Looking at Koji, releng was > previously doing the builds for it . Does anyone know anymore about > this including whether eclipse-photran is being (intentionally) dropped > and alternatives? It was retired 7 months ago after being orphaned[1]. To bring it back, you'd have to become the new maintainer, submit a new review request and ask for unretirement. Regards, Dominik [1] https://src.fedoraproject.org/rpms/eclipse-photran -- Fedora https://getfedora.org | RPM Fusion http://rpmfusion.org There should be a science of discontent. People need hard times and oppression to develop psychic muscles. -- from "Collected Sayings of Muad'Dib" by the Princess Irulan ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Updating cryptopp to 8.3.0
On Friday, 25 December 2020 at 22:26, Vascom wrote: > Hi all. > > I want to update cryptopp package to 8.3.0. > It has the same soname version but changes in ABI. If there are ABI changes without SONAME bump, then it's at least worth opening a ticket with upstream. It might be unintentional and the author(s) need to be made aware of the impact. > I found only two dependent packages: > clementine > tegrarcm > > So I will rebuild them too. > > If you have any suggestions or I missed some dependent packages please tell > me. > I am plan to make builds at 28.12.2020 in rawhide. I'd hold off with updating until I got a reply from upstream. Regards, Dominik -- Fedora https://getfedora.org | RPM Fusion http://rpmfusion.org There should be a science of discontent. People need hard times and oppression to develop psychic muscles. -- from "Collected Sayings of Muad'Dib" by the Princess Irulan ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: What is the most time consuming task for you as packager?
Hi, For me the most time consuming is monkey updates packages like kde apps , which every month or two we have a new release ( kde app 20.04.1 20.04.2 20.08.0 , 20.12.00 etc ) I did some scripts to automate my builds , we got some software like https://github.com/fedora-infra/the-new-hotness/ but the more I do, I always some variables that are different from project to project , we need to know the version number, we may need to download more than one source, we may need drop patches that we know that are already upstreamed, not all the package are build in same branches so we need to know what branches we want update , we may have to add buildroot-overrides, we need add build to bodhi and fill some information , we need close bugs create made by hotness or other users etc Examples of my scripts are usually in packages sources like https://src.fedoraproject.org/rpms/virtualbox-guest-additions/blob/master/f/update_vbox.sh or (in attachment) scripts in very quick-and-dirty style So, combine tools like rpmdevtools , the-new-hotness , bodhi-client etc we improve building automation . Thank you. -- Sérgio M. B. update_from_bugzilla.sh Description: application/shellscript update_package.sh Description: application/shellscript ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora-IoT-33-20201226.0 compose check report
No missing expected images. Failed openQA tests: 2/16 (x86_64), 3/15 (aarch64) ID: 747174 Test: x86_64 IoT-dvd_ostree-iso iot_zezere_server URL: https://openqa.fedoraproject.org/tests/747174 ID: 747178 Test: x86_64 IoT-dvd_ostree-iso iot_zezere_ignition URL: https://openqa.fedoraproject.org/tests/747178 ID: 747179 Test: aarch64 IoT-dvd_ostree-iso iot_clevis@uefi URL: https://openqa.fedoraproject.org/tests/747179 ID: 747190 Test: aarch64 IoT-dvd_ostree-iso iot_zezere_server@uefi URL: https://openqa.fedoraproject.org/tests/747190 ID: 747193 Test: aarch64 IoT-dvd_ostree-iso iot_zezere_ignition@uefi URL: https://openqa.fedoraproject.org/tests/747193 Soft failed openQA tests: 1/16 (x86_64) (Tests completed, but using a workaround for a known bug) ID: 747163 Test: x86_64 IoT-dvd_ostree-iso iot_clevis URL: https://openqa.fedoraproject.org/tests/747163 Passed openQA tests: 13/16 (x86_64), 12/15 (aarch64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Stale proven packagers
On Thu, Dec 24, 2020 at 07:32:04AM +, Dridi Boukelmoune wrote: > > The weakest point in the current system is really the FAS password. If > > you have a packager's FAS password you can change the ssh key > > associated with the account to another that you control, and the FAS > > password is also all you need to run a build and submit it to Bodhi. Well, really the weakest point is email. If you have control over a fas accounts email address you can reset the password, etc. > Or you add an SSH key without removing the maintainer's keys on the > off chance that it would go unnoticed... fas sends email on every such change. kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Stale proven packagers
On Wed, Dec 23, 2020 at 12:49:10AM +, Peter Robinson wrote: > > Just to expand on this a little. Removing access from people that have > left the project either because they've decided they're able to > continue to contribute (option 1) or because something has triggered > an admin process (option 2) isn't a slight on the person involved in > any of this process and removing a well earned ACL doesn't remove any > of the contributions or the value they provided in the past. Completely agreed! > But we have to realise than inactive accounts may mean associated > inactive email addresses or other things associated with a person > which may be open to compromise as well and we need to protect the > project as a whole as after-all if a fellow contributor has moved on > to better things account is used to comprise everything where does > that leave us? > > Group membership is easily re-instated, trust after a security > compromise not so much! Well, we might need to think about that too though. Say we have a contributor that is very active, in tons of groups. They go inactive. We remove their group membership after a while. Then, years later they appear and send an email from their old gmail account 'Hi, I'm back, please re-add me to all my old groups". How do we know thats really the old contributor vs just someone who reclaimed a old gmail account? but anyhow, lots to consider here... we probibly need to come up with a straw man proposal for everyone to poke holes in after the new year. kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: What is the most time consuming task for you as packager?
On Sat, Dec 26, 2020 at 01:04:50AM +0100, Miro Hrončok wrote: > On 23. 12. 20 0:11, Kevin Fenzi wrote: > > Cool. The help didn't get me this at all.;) > > > >--from-git FROM_GIT regexes for packages to build from git > > > > Perhaps that should be "copr-name packager-name:packagename:branchname" > > ? > > As a side note, the --from-git option is not what the "copr-name > packager-name:packagename:branchname" is. The --from-git option is an extra > option you specify to change the way dependent packages are built. The > "copr-name packager-name:packagename:branchname" are the positional > arguments of the script: > > positional arguments: > copr copr repo to use (and create) > project projects to build (in order); format: USER:REPO:BRANCH Ah ha. I completely misread it then. Thanks. kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora-Rawhide-20201226.n.0 compose check report
Missing expected images: Xfce raw-xz armhfp Compose FAILS proposed Rawhide gating check! 2 of 43 required tests failed openQA tests matching unsatisfied gating requirements shown with **GATING** below Failed openQA tests: 9/180 (x86_64), 12/122 (aarch64) New failures (same test not failed in Fedora-Rawhide-20201225.n.0): ID: 746818 Test: x86_64 Server-dvd-iso server_cockpit_updates URL: https://openqa.fedoraproject.org/tests/746818 ID: 746838 Test: x86_64 Workstation-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/746838 ID: 746921 Test: aarch64 Server-dvd-iso server_freeipa_replication_master@uefi URL: https://openqa.fedoraproject.org/tests/746921 ID: 746927 Test: aarch64 Server-dvd-iso server_freeipa_replication_replica@uefi URL: https://openqa.fedoraproject.org/tests/746927 ID: 746928 Test: aarch64 Server-dvd-iso server_freeipa_replication_client@uefi URL: https://openqa.fedoraproject.org/tests/746928 ID: 746948 Test: aarch64 Workstation-raw_xz-raw.xz desktop_browser@uefi URL: https://openqa.fedoraproject.org/tests/746948 ID: 746950 Test: aarch64 Workstation-raw_xz-raw.xz desktop_update_graphical@uefi URL: https://openqa.fedoraproject.org/tests/746950 ID: 747046 Test: aarch64 universal install_shrink_ntfs@uefi URL: https://openqa.fedoraproject.org/tests/747046 ID: 747069 Test: aarch64 universal install_mirrorlist_graphical@uefi URL: https://openqa.fedoraproject.org/tests/747069 Old failures (same test failed in Fedora-Rawhide-20201225.n.0): ID: 746833 Test: x86_64 Workstation-live-iso desktop_browser **GATING** URL: https://openqa.fedoraproject.org/tests/746833 ID: 746840 Test: x86_64 Workstation-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/746840 ID: 746850 Test: x86_64 KDE-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/746850 ID: 746859 Test: x86_64 KDE-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/746859 ID: 746861 Test: x86_64 KDE-live-iso desktop_browser **GATING** URL: https://openqa.fedoraproject.org/tests/746861 ID: 746873 Test: x86_64 Silverblue-dvd_ostree-iso desktop_browser URL: https://openqa.fedoraproject.org/tests/746873 ID: 747013 Test: x86_64 universal install_cyrillic_language URL: https://openqa.fedoraproject.org/tests/747013 ID: 747040 Test: aarch64 universal upgrade_2_server_domain_controller@uefi URL: https://openqa.fedoraproject.org/tests/747040 ID: 747051 Test: aarch64 universal install_blivet_resize_lvm@uefi URL: https://openqa.fedoraproject.org/tests/747051 ID: 747067 Test: aarch64 universal install_cyrillic_language@uefi URL: https://openqa.fedoraproject.org/tests/747067 ID: 747072 Test: aarch64 universal install_with_swap@uefi URL: https://openqa.fedoraproject.org/tests/747072 ID: 747076 Test: aarch64 universal upgrade_2_realmd_client@uefi URL: https://openqa.fedoraproject.org/tests/747076 Soft failed openQA tests: 18/180 (x86_64), 15/122 (aarch64) (Tests completed, but using a workaround for a known bug) New soft failures (same test not soft failed in Fedora-Rawhide-20201225.n.0): ID: 746779 Test: x86_64 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/746779 ID: 746891 Test: aarch64 Server-dvd-iso install_vncconnect_client@uefi URL: https://openqa.fedoraproject.org/tests/746891 Old soft failures (same test soft failed in Fedora-Rawhide-20201225.n.0): ID: 746780 Test: x86_64 Server-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/746780 ID: 746787 Test: x86_64 Server-dvd-iso install_vncconnect_client URL: https://openqa.fedoraproject.org/tests/746787 ID: 746791 Test: x86_64 Server-dvd-iso install_vnc_client URL: https://openqa.fedoraproject.org/tests/746791 ID: 746795 Test: x86_64 Server-dvd-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/746795 ID: 746796 Test: x86_64 Server-dvd-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/746796 ID: 746809 Test: x86_64 Server-dvd-iso server_realmd_join_kickstart URL: https://openqa.fedoraproject.org/tests/746809 ID: 746881 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/746881 ID: 746890 Test: aarch64 Server-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/746890 ID: 746899 Test: aarch64 Server-dvd-iso install_default_upload@uefi URL: https://openqa.fedoraproject.org/tests/746899 ID: 746910 Test: aarch64 Server-dvd-iso server_realmd_join_kickstart@uefi URL: https://openqa.fedoraproject.org/tests/746910 ID: 746916 Test: aarch64 Server-dvd-iso install_vnc_client@uefi URL: https://openqa.fedoraproject.org/tests/746916 ID: 746930 Test: aarch64 Server-raw_xz-raw.xz install_arm_image_deployment_upload@uefi URL: https://openqa.fedoraproject.org/tests/746930 ID: 746934 Tes
Fedora-IoT-34-20201226.0 compose check report
Missing expected images: Iot dvd aarch64 Iot dvd x86_64 Failed openQA tests: 1/16 (x86_64), 7/15 (aarch64) ID: 747139 Test: x86_64 IoT-dvd_ostree-iso base_services_start URL: https://openqa.fedoraproject.org/tests/747139 ID: 747148 Test: aarch64 IoT-dvd_ostree-iso iot_clevis@uefi URL: https://openqa.fedoraproject.org/tests/747148 ID: 747150 Test: aarch64 IoT-dvd_ostree-iso podman@uefi URL: https://openqa.fedoraproject.org/tests/747150 ID: 747151 Test: aarch64 IoT-dvd_ostree-iso podman_client@uefi URL: https://openqa.fedoraproject.org/tests/747151 ID: 747153 Test: aarch64 IoT-dvd_ostree-iso base_services_start@uefi URL: https://openqa.fedoraproject.org/tests/747153 ID: 747157 Test: aarch64 IoT-dvd_ostree-iso iot_rpmostree_overlay@uefi URL: https://openqa.fedoraproject.org/tests/747157 ID: 747159 Test: aarch64 IoT-dvd_ostree-iso iot_zezere_server@uefi URL: https://openqa.fedoraproject.org/tests/747159 ID: 747162 Test: aarch64 IoT-dvd_ostree-iso iot_zezere_ignition@uefi URL: https://openqa.fedoraproject.org/tests/747162 Soft failed openQA tests: 1/16 (x86_64) (Tests completed, but using a workaround for a known bug) ID: 747132 Test: x86_64 IoT-dvd_ostree-iso iot_clevis URL: https://openqa.fedoraproject.org/tests/747132 Passed openQA tests: 14/16 (x86_64), 8/15 (aarch64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora rawhide compose report: 20201226.n.0 changes
OLD: Fedora-Rawhide-20201225.n.0 NEW: Fedora-Rawhide-20201226.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 15 Dropped packages:0 Upgraded packages: 36 Downgraded packages: 0 Size of added packages: 14.40 MiB Size of dropped packages:0 B Size of upgraded packages: 236.16 MiB Size of downgraded packages: 0 B Size change of upgraded packages: -2.91 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = = ADDED PACKAGES = Package: golang-github-antlr-antlr4-4.9-1.fc34 Summary: Powerful parser generator for reading, processing, executing, or translating structured text or binary files RPMs:golang-github-antlr-antlr4-devel Size:2.24 MiB Package: golang-github-fonts-dejavu-0.1.0-1.fc34 Summary: DejaVu fonts for Go RPMs:golang-github-fonts-dejavu-devel Size:5.03 MiB Package: golang-github-google-cel-0.6.0-1.20201225git4c3317a.fc34 Summary: Fast, portable, non-Turing complete expression evaluation RPMs:golang-github-google-cel-devel Size:231.85 KiB Package: golang-github-google-cel-spec-0.5.0-1.fc34 Summary: Common Expression Language, specification and binary representation RPMs:golang-github-google-cel-spec-devel Size:63.67 KiB Package: golang-github-latex-0-0.1.20201224git94de131.fc34 Summary: Go package for LaTeX RPMs:golang-github-latex golang-github-latex-devel Size:5.52 MiB Package: python-textdistance-4.2.0-2.fc34 Summary: Compute distance between the two texts RPMs:python3-textdistance Size:58.68 KiB Package: rust-clap2-2.33.3-1.fc34 Summary: Simple to use, efficient, and full-featured Command Line Argument Parser RPMs:rust-clap2+ansi_term-devel rust-clap2+atty-devel rust-clap2+color-devel rust-clap2+debug-devel rust-clap2+default-devel rust-clap2+doc-devel rust-clap2+no_cargo-devel rust-clap2+strsim-devel rust-clap2+suggestions-devel rust-clap2+term_size-devel rust-clap2+unstable-devel rust-clap2+vec_map-devel rust-clap2+wrap_help-devel rust-clap2+yaml-devel rust-clap2+yaml-rust-devel rust-clap2-devel Size:274.30 KiB Package: rust-clap_derive-3.0.0~beta.2-1.fc34 Summary: Parse command line argument by defining a struct, derive crate RPMs:rust-clap_derive+debug-devel rust-clap_derive+default-devel rust-clap_derive+doc-devel rust-clap_derive+unstable-devel rust-clap_derive-devel Size:57.49 KiB Package: rust-crosstermion-0.5.0-1.fc34 Summary: Unification of crossterm and termion behind a common facade for use with feature flags RPMs:rust-crosstermion+ansi_term-devel rust-crosstermion+async-channel-devel rust-crosstermion+color-devel rust-crosstermion+crossterm-devel rust-crosstermion+default-devel rust-crosstermion+futures-channel-devel rust-crosstermion+futures-core-devel rust-crosstermion+futures-lite-devel rust-crosstermion+input-async-crossterm-devel rust-crosstermion+input-async-devel rust-crosstermion+termion-devel rust-crosstermion+tui-crossterm-backend-devel rust-crosstermion+tui-crossterm-devel rust-crosstermion+tui-devel rust-crosstermion+tui-react-crossterm-devel rust-crosstermion+tui-react-devel rust-crosstermion+tui-react-termion-devel rust-crosstermion+tui-termion-backend-devel rust-crosstermion+tui-termion-devel rust-crosstermion-devel Size:155.51 KiB Package: rust-minify-html-0.3.10-1.fc34 Summary: Fast and smart HTML + JS minifier RPMs:rust-minify-html+crossbeam-devel rust-minify-html+default-devel rust-minify-html+esbuild-rs-devel rust-minify-html+js-esbuild-devel rust-minify-html-devel Size:133.04 KiB Package: rust-os_str_bytes-2.4.0-1.fc34 Summary: Traits for converting between byte sequences and platform-native strings RPMs:rust-os_str_bytes+default-devel rust-os_str_bytes+raw-devel rust-os_str_bytes-devel Size:38.69 KiB Package: rust-relative-path-1.3.2-1.fc34 Summary: Portable, relative paths for Rust RPMs:rust-relative-path+ci-devel rust-relative-path+default-devel rust-relative-path+serde-devel rust-relative-path-devel Size:48.72 KiB Package: rust-roxmltree-0.13.1-1.fc34 Summary: Represent an XML as a read-only tree RPMs:rust-roxmltree+default-devel rust-roxmltree-devel Size:73.47 KiB Package: rust-svg_metadata-0.4.1-1.fc34 Summary: Extracts metadata (like the viewBox, width, and height) from SVG graphics RPMs:rust-svg_metadata+default-devel rust-svg_metadata-devel Size:459.05 KiB Package: rust-xmlparser-0.13.3-1.fc34 Summary: Pull-based, zero-allocation XML parser RPMs:rust-xmlparser+default-devel rust-xmlparser+std-devel rust-xmlparser-devel Size:48.12 KiB = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: borgbackup-1.1.15-1.fc34 Old package: borgbackup-1.1.14-1.fc34 Summary: A deduplicating backup program with compression and authenticated encryption RPMs: borgbackup Size: 5.05 MiB Size change: -1.15 KiB Changelog: * Fri Dec 25 2020 Felix Schwarz
Re: Stale proven packagers
On 22. 12. 20 21:39, Adam Williamson wrote: Perhaps we need a process for cleaning up membership of this extremely powerful group? If the FAS password of*any one* of those user accounts were somehow compromised (or if just one of them decided they had a grudge against Fedora now and were going to have some fun), the results could be...unfortunate. I've read the thread an I agree. At very least, we should remove the provenpackager membership when we deem somebody nonresponsive (we currently don't). -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora-Cloud-32-20201226.0 compose check report
No missing expected images. Soft failed openQA tests: 1/7 (x86_64), 1/7 (aarch64) (Tests completed, but using a workaround for a known bug) ID: 746771 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/746771 ID: 746778 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/746778 Passed openQA tests: 6/7 (x86_64), 6/7 (aarch64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
