Re: Switch a package from noarch to arch - current guidelines?

[Vít Ondruch <vondruch@xxxxxxxxxx>]

Dne 27.7.2017 v 16:56 Martin Langhoff napsal(a):

Turns out that Elixir should not be noarch, as some of its code is endianness specific. What's best practice to switch away from noarch for packages in current Fedora? How about EPEL?

I see this outdated and unresolved Packaging Comittee issue... https://pagure.io/packaging-committee/issue/117 

and I see a bunch of bugs referring to specs (and rpms) that fail during upgrades. Some have obsoletes on their own name, others don't. 

https://bugzilla.redhat.com/show_bug.cgi?id=753149

https://bugzilla.redhat.com/show_bug.cgi?id=1230183

This was related to rubygem-bson and I switched the rubygem-bson from noarch to arch in this commit:

http://pkgs.fedoraproject.org/cgit/rpms/rubygem-bson.git/commit/?id=f507fa3ee0e8b29e60ef6164c28733691332dea4

I don't think there should be any additional concern ATM.


Vít

https://bugzilla.redhat.com/show_bug.cgi?id=1301306

Is there clarity / consensus on this? Any packages that have made the transition successfully recently?

cheers,

martin

--

 martin.langhoff@xxxxxxxxx

 - ask interesting questions  ~  http://linkedin.com/in/martinlanghoff

 - don't be distracted        ~  http://github.com/martin-langhoff

   by shiny stuff

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx