Closed proletarius101 closed 3 years ago
Started test build 39669
Build 39669 failed
Started test build 39672
Build 39672 failed
I disagree with random bumps of random modules, and this is essentially what adding x-data-checker accomplishes here. This is fine if an upstream maintainer decides to do so, but not so much if it's done via drive-through contribution.
Yes. I agree with @barthalion.
Although we are proposing automatic updates for our osinfo-db https://github.com/flathub/org.gnome.Boxes.Extension.OsinfoDb/pull/2 where I think this makes sense, since this is just a database, and the project has strong CI. For libraries/modules, I don't think that brings us any practical benefits now.
libvirt-check-for-disk-type-correctly.patch
removed: it's already applied by the upstreamDoes it use the git version and not the released one?
Not true. I select the tagged versions. Some reason as https://github.com/flathub/org.gnome.Evince/pull/37#issuecomment-781910919 They are simply hosted on GitLab, but they have the same version (as their tags) as the ones hosted on the website. I don't use the ones on download.gnome.org because the urls don't compatible with the x-checker-data. e.g.
There is a
1.8
in the middle. But what if the version bumps to1.9.x
? We don't have a procedure to provide the substring1.9
.