new pkgtreediff tool
Hi, I made a little tool called pkgtreediff to compare package trees (directories of rpm files). See https://github.com/juhp/pkgtreediff#readme for more details. I hope some people here may find it useful. Fedora and Epel7 builds are available in < https://copr.fedorainfracloud.org/coprs/petersen/pkgtreediff/>. Feedback and suggestions are welcome (particularly other than "why did you write in Haskell again?";-) Thanks, Jens ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Procedure to get keytable included in official console and X and wayland keytables.
I use a custom keymapping that I developed to save my hands, and because it is very efficient. It's strength is that the most used keys are under the strongest fingers, and that for my typing about 80% of what I type is on the home row. The problem is that whenever I have issues with my system, it reverts to qwerty, and I have to hunt and peck to do things. If it was official, this wouldn't be a problem, because I could just select it, the same as one can select dvorak or colemak. Unlike those, I really rearranged the keys for efficiency, and there are only 2 or 3 keys the same as qwerty. I used to use qwerty as a touch typist, and I suppose I could learn to switch back and forth, but qwerty is just so clumsy, and my hands don't like it. Does anyone know how I would go about getting my keytable, which I call uneaf after the left home row, included? Is there an official procedure, or is it just a submission with a request to a programmer somewhere. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: How to consume fedora-messaging?
On Mon, Jun 10, 2019 at 01:24 Igor Gnatenko wrote: > Hello, > > I have been trying to write some script which would listen on > generation of new repository / successful build is tagged in Koji and > do some actions locally. Or basically whenever someone pushes commits, > I want to fetch repo locally. > > I was reading > https://fedora-messaging.readthedocs.io/en/latest/consuming.html, > but it is not very clear to me where I can find list of topics and > what data messages will contain... > Hi Igor, you can find the list of topics and their associated schema here: https://fedora-fedmsg.readthedocs.io/en/latest/topics.html And you can also find samples on this website: https://apps.fedoraproject.org/datagrepper/raw > Bonus point who can tell me how does it know which messages should be > re-queued and how to manipulate that. > It doesn't seems like you have to worry about re-queue when consuming the bus. Regards, -Tristan 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
How to consume fedora-messaging?
Hello, I have been trying to write some script which would listen on generation of new repository / successful build is tagged in Koji and do some actions locally. Or basically whenever someone pushes commits, I want to fetch repo locally. I was reading https://fedora-messaging.readthedocs.io/en/latest/consuming.html, but it is not very clear to me where I can find list of topics and what data messages will contain... Bonus point who can tell me how does it know which messages should be re-queued and how to manipulate that. Thanks! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Do people not care about broken dependencies?
On Sun, Jun 9, 2019, 19:59 Igor Gnatenko wrote: > On Sun, Jun 9, 2019 at 7:03 PM Fabio Valentini > wrote: > > > > On Sun, Jun 9, 2019, 18:06 Igor Gnatenko < > ignatenkobr...@fedoraproject.org> wrote: > >> > >> Hello, > >> > >> I've noticed that people keep pushing updates which have broken > dependencies. > >> > >> For example, python-kombu was updated from 4.6.0 to 4.6.1. Both of > >> those versions have broken dependency "python3.7dist(amqp) >= 2.5.0 ". > >> However, it was built both for F30 and F31 and even submitted to > >> bodhi. > >> > >> I have more examples… > > > > > > Hi Igor, > > > > I have some additional examples of this as well. I think this is most > often caused by automatically generated unsatisfied dependencies of binary > packages - which don't break the build, but make the package uninstallable. > > If you mean Rust ones, those are intentional because we do not indent > to ship them to the users... However, we need to build them somewhere. > No, I didn't attempt to be passive-aggressive here ;) My issues were caused by python package updates, as well. > But yeah, people just don't notice this. > > > Fabio > > > >> ___ > >> devel mailing list -- devel@lists.fedoraproject.org > >> To unsubscribe send an email to devel-le...@lists.fedoraproject.org > >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > >> List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > > > > ___ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Do people not care about broken dependencies?
On Sun, Jun 9, 2019 at 7:03 PM Fabio Valentini wrote: > > On Sun, Jun 9, 2019, 18:06 Igor Gnatenko > wrote: >> >> Hello, >> >> I've noticed that people keep pushing updates which have broken dependencies. >> >> For example, python-kombu was updated from 4.6.0 to 4.6.1. Both of >> those versions have broken dependency "python3.7dist(amqp) >= 2.5.0 ". >> However, it was built both for F30 and F31 and even submitted to >> bodhi. >> >> I have more examples… > > > Hi Igor, > > I have some additional examples of this as well. I think this is most often > caused by automatically generated unsatisfied dependencies of binary packages > - which don't break the build, but make the package uninstallable. If you mean Rust ones, those are intentional because we do not indent to ship them to the users... However, we need to build them somewhere. But yeah, people just don't notice this. > Fabio > >> ___ >> devel mailing list -- devel@lists.fedoraproject.org >> To unsubscribe send an email to devel-le...@lists.fedoraproject.org >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[Test-Announce] Proposal to CANCEL: 2019-06-10 Fedora QA Meeting
Hi folks! I'm proposing we cancel the QA meeting tomorrow. I don't have anything urgent for the agenda. If you're aware of anything important we have to discuss this week, please do reply to this mail and we can go ahead and run the meeting. Thanks, everyone! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Do people not care about broken dependencies?
On Sun, Jun 9, 2019, 18:06 Igor Gnatenko wrote: > Hello, > > I've noticed that people keep pushing updates which have broken > dependencies. > > For example, python-kombu was updated from 4.6.0 to 4.6.1. Both of > those versions have broken dependency "python3.7dist(amqp) >= 2.5.0 ". > However, it was built both for F30 and F31 and even submitted to > bodhi. > > I have more examples… > Hi Igor, I have some additional examples of this as well. I think this is most often caused by automatically generated unsatisfied dependencies of binary packages - which don't break the build, but make the package uninstallable. Fabio ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Do people not care about broken dependencies?
On Sun, Jun 9, 2019 at 5:18 PM Igor Gnatenko wrote: > > Hello, > > I've noticed that people keep pushing updates which have broken dependencies. > > For example, python-kombu was updated from 4.6.0 to 4.6.1. Both of > those versions have broken dependency "python3.7dist(amqp) >= 2.5.0 ". > However, it was built both for F30 and F31 and even submitted to > bodhi. This looks like a low-hanging fruit job for CI Gating - if the package can't be installed, gate it, barring override. regards, bex > > I have more examples… > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org -- Brian "bex" Exelbierd (he/him/his) Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org bexel...@redhat.com | b...@pobox.com ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do people not care about broken dependencies?
Hello, I've noticed that people keep pushing updates which have broken dependencies. For example, python-kombu was updated from 4.6.0 to 4.6.1. Both of those versions have broken dependency "python3.7dist(amqp) >= 2.5.0 ". However, it was built both for F30 and F31 and even submitted to bodhi. I have more examples… ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Tagging commit hashes of Koji builds in dist-git
On Thu, Jun 06, 2019 at 02:07:18PM -0500, Dennis Gilmore wrote: > On Thu, Jun 6, 2019 at 7:11 AM Neal Gompa wrote: > > > > On Thu, Jun 6, 2019 at 7:53 AM Florian Weimer wrote: > > > > > > Is there a reason why we do not tag dist-git commits, using a name which > > > is derived from the NEVR from a Koji build? > > > > > > How well does Git scale with thousands of tags? > > > > > > > We used to back in the CVS days, because we needed it for plague. Koji > > blocks duplicate submissions anyway, so it stopped being needed when > > we transitioned to Git. > > it was not plague that needed it, using tags was the only way to > cjeckout the intended output, they had the problem that they were not > immutable, if you made a typo you forced in a new tag so you did not > need to bump the nvr > > > We're going to probably introduce it for some automation in the near > > future, though. > > > > Git is not great with thousands of any kind of refs, be it branches or > > tags. It still works, it's just things like 'git log' get kind of > > expensive. > > koji stores the git hash for all builds, writing a script to get the > hash for a given nvr would be trivial. it just means you have to be > online to retrieve the data than being able to get the date while > disconnected, if it was stored in git. I'd also point out that the link is also made in pagure, for example: https://src.fedoraproject.org/rpms/kernel/c/ead55fdbc7606e96fb1436249e4d121c5119218b?branch=master Basically, we listen for koji build results and "flag" the commit which was used for the build with the outcome (success/failure) of the build. Here is another example who both succeeded and failed to build in koji: https://src.fedoraproject.org/rpms/0ad/c/d43ffc4721e7c5d6af33e9bc26b739ec6802cb76?branch=master If this needs to be made more easily discoverable via the API, we can adjust pagure for this. Pierre ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
