Bug 1266662 - Drop sqljet-browser subpackage
Summary: Drop sqljet-browser subpackage
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: sqljet
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ismael Olea
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-26 09:31 UTC by Kalev Lember
Modified: 2015-10-03 17:36 UTC (History)
2 users (show)

Fixed In Version: sqljet-1.1.10-5.fc23
Clone Of:
Environment:
Last Closed: 2015-10-03 17:36:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
[PATCH] Drop sqljet-browser subpackage (5.35 KB, text/plain)
2015-09-26 10:08 UTC, Kalev Lember
no flags Details

Description Kalev Lember 2015-09-26 09:31:40 UTC
sqljet-browser needs netbeans-platform that is broken in F23. Unless someone steps up to fix netbeans-platform, sqljet-browser needs to go as well to keep sqljet building without netbeans-platform.

https://lists.fedoraproject.org/pipermail/devel/2015-September/215011.html

Comment 1 Kalev Lember 2015-09-26 10:08:59 UTC
Created attachment 1077378 [details]
[PATCH] Drop sqljet-browser subpackage

Comment 2 Fedora Update System 2015-09-26 15:22:34 UTC
sqljet-1.1.10-5.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-43810c646f

Comment 3 Fedora Update System 2015-09-27 00:54:14 UTC
sqljet-1.1.10-5.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
$ su -c 'dnf --enablerepo=updates-testing update sqljet'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-43810c646f

Comment 4 Fedora Update System 2015-10-03 17:36:09 UTC
sqljet-1.1.10-5.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.