Bug 1933434 - bitlbee-discord current release is broken, fixed upstream
Summary: bitlbee-discord current release is broken, fixed upstream
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: bitlbee-discord
Version: epel7
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-27 19:33 UTC by PDog
Modified: 2024-07-09 03:29 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-07-09 03:29:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description PDog 2021-02-27 19:33:48 UTC
Description of problem:
The current package is broken and does not properly establish a connection. This was fixed in upstream 0.4.3.

Version-Release number of selected component (if applicable):
0.4.2-1.el7

How reproducible:
Easily

Steps to Reproduce:
1. `yum install bitlbee-discord`
2. Set up a discord account via bitlbee
3. Once the account is enabled, the user will be disconnect from Discord immediately after connecting

Actual results:
User is repeatedly disconnect from Discord

Expected results:
User is not disconnected from Discord

Additional info:
Fixed in upstream version 0.4.3

Comment 1 Fedora Admin user for bugzilla script actions 2021-10-11 00:20:18 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 2 Ted McGee 2022-10-27 02:20:10 UTC
The _root sharedstatedir in this case is peculiar and unexpected. The sharedstatedir is unexpected if the pattern is that _root X maps to X outside of the SCL. We experienced some packaging issues as a result, thus we no longer use _root sharedstatedir.
http://file.rdu.redhat.com/pousley/snapshot-yaml-bug/virt/virtual machines/virtualdisks/virt-managing-vm-snapshots.html#virt-creating-vm-snapshot-cli virt-managing-vm-snapshots https://fivenights-atfreddys.com is a link to a preview of the documentation.

When you are able, would you kindly validate it?

Comment 3 Troy Dawson 2024-07-09 03:29:13 UTC
EPEL 7 entered end-of-life (EOL) status on 2024-06-30.\n\nEPEL 7 is no longer maintained, which means that it\nwill not receive any further security or bug fix updates.\n As a result we are closing this bug.


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