Re: "Could not retire package"

2016-10-11 Thread Bastien Nocera
- Original Message - > On Thursday, September 15, 2016 12:20:57 PM CDT Bastien Nocera wrote: > > - Original Message - > > > > > On Thursday, September 15, 2016 11:51:47 AM CDT Bastien Nocera wrote: > > > > Could not retire package: You a

Re: "Could not retire package"

2016-09-15 Thread Dennis Gilmore
On Thursday, September 15, 2016 12:20:57 PM CDT Bastien Nocera wrote: > - Original Message - > > > On Thursday, September 15, 2016 11:51:47 AM CDT Bastien Nocera wrote: > > > Could not retire package: You are not allowed to retire the package: > >

Re: "Could not retire package"

2016-09-15 Thread Bastien Nocera
- Original Message - > On Thursday, September 15, 2016 11:51:47 AM CDT Bastien Nocera wrote: > > Could not retire package: You are not allowed to retire the package: > > rpms/obexd on branch f24. > > > > obexd has been integrated in bluez since version 5.somet

Re: "Could not retire package"

2016-09-15 Thread Michael Catanzaro
On Thu, 2016-09-15 at 11:51 -0400, Bastien Nocera wrote: > Could not retire package: You are not allowed to retire the package: > rpms/obexd on branch f24. F24 has been released, nothing can be retired. You can only retire it for F25 and rawhide. Michael -- devel mailing list

Re: "Could not retire package"

2016-09-15 Thread Dennis Gilmore
On Thursday, September 15, 2016 11:51:47 AM CDT Bastien Nocera wrote: > Could not retire package: You are not allowed to retire the package: > rpms/obexd on branch f24. > > obexd has been integrated in bluez since version 5.something, which > happened at least 5 Fedora releases ago

"Could not retire package"

2016-09-15 Thread Bastien Nocera
Could not retire package: You are not allowed to retire the package: rpms/obexd on branch f24. obexd has been integrated in bluez since version 5.something, which happened at least 5 Fedora releases ago. My guess is that the "critpath" status of the package is stopping that. Cheer