Bug 1068864 - vte3: please do not depend on initscripts.rpm
Summary: vte3: please do not depend on initscripts.rpm
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: vte3
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-22 15:36 UTC by Kay Sievers
Modified: 2016-07-19 11:03 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-19 11:03:03 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Kay Sievers 2014-02-22 15:36:17 UTC
vt3 depend on the initscripts package, but nothing commonly used should do
that today.

vt3.spec:
  # initscripts creates the utmp group
  Requires: initscripts

If it really needs the utmp group, it can just create it itself. This is what
initscripts does:
  %pre
  /usr/sbin/groupadd -g 22 -r -f utmp

Thanks!

Comment 1 Kay Sievers 2014-05-15 16:55:19 UTC
Ping! Please get rid of this outdated stuff.

Comment 2 Jaroslav Reznik 2015-03-03 15:31:02 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 3 Fedora End Of Life 2016-07-19 11:03:03 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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