palemoon
No description set
-
3
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout network/palemoon && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
Python-2.7.18.tar.xz | 0012854736 12.3 MB | |
README.update.source | 0000000694 694 Bytes | |
_constraints | 0000000444 444 Bytes | |
default-prefs.js | 0000000334 334 Bytes | |
distribution.ini.in | 0000001047 1.02 KB | |
palemoon-33.7.0_Release.tar.gz | 0271741302 259 MB | |
palemoon-localizations-33.7.0.tar.gz | 0012242108 11.7 MB | |
palemoon-mimeinfo.xml | 0000000292 292 Bytes | |
palemoon-nongnome-proxies.patch | 0000001409 1.38 KB | |
palemoon-profile.patch | 0000000522 522 Bytes | |
palemoon-vendor.patch | 0000000627 627 Bytes | |
palemoon.changes | 0000037462 36.6 KB | |
palemoon.desktop | 0000010261 10 KB | |
palemoon.in | 0000000198 198 Bytes | |
palemoon.spec | 0000013491 13.2 KB | |
spellcheck.js | 0000000060 60 Bytes |
Comments 5
When uninstalling, I faced the next error:
warning: directory /: remove failed: Device or resource busy
Probably, there is some configuration error, that can went bad
This package after revision 66 breaks builds for anything that depends on nss/nspr in the network repo (see obs://network/nextcloud-desktop) and needs to be reverted to pre-rev66 status or somehow worked around so that it does not fake provide nss/nspr.
This package (which is not in Factory) is now an impediment to packages like nextcloud-desktop for which network is actually the devel project and this needs to be dealt with urgently, in my opinion. Appreciate any efforts towards that. Thanks in advance.
@dirkmueller @seife @msmeissn @joachimwerner Urgently requesting project owners to unset the UseForBuild flag for this package so that the broken "Provides" from it does not continue to be a hindrance to development of other packages in the project. Package manager seems to be unresponsive.
I disabled usedforbuild for this package. Sorry, due to the huge Leap 16 OBS mail spam I did miss your message, your ping on factory@ was successfull :-)
Oh, so that's happened for everyone then? I thought it was some kind of bug. I have only been mass deleting notifications for the last couple of days or so.
Thanks a lot for the help.