Bug 848690 - Retiring Django south
Summary: Retiring Django south
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: Django-south
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Runge
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-16 08:38 UTC by Bohuslav "Slavek" Kabrda
Modified: 2012-11-04 01:13 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-11-03 20:58:50 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
The 'retire package' button does not shows in screen (81.47 KB, image/png)
2012-09-04 21:13 UTC, Domingo Becker
no flags Details
'retire package' button showns when I print from firefox to cups-pdf (361.24 KB, application/pdf)
2012-09-04 21:14 UTC, Domingo Becker
no flags Details

Description Bohuslav "Slavek" Kabrda 2012-08-16 08:38:39 UTC
Hi, since Django-south has been renamed to python-django-south, I'd like to ask you to retire the package in F19 (devel) and F18. Please follow the full procedure in [1].
Thanks.

[1] https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life

Comment 1 Domingo Becker 2012-08-29 05:16:11 UTC
Ooops, sorry!

I will take care of this as soon as possible.

Sorry for the inconvenience.  :-(

Comment 2 Domingo Becker 2012-09-02 12:57:54 UTC
There is no retired check box in 

https://admin.fedoraproject.org/pkgdb/acls/name/Django-south

'fedpkg retire' has been done.

It seems that the step 'git push' is missing from the instructions given in [1] in this bug report.

The ticket for retiring the renamed packages has been filed too:

https://fedorahosted.org/rel-eng/ticket/5315

Comment 3 Bohuslav "Slavek" Kabrda 2012-09-03 06:07:15 UTC
(In reply to comment #2)
> There is no retired check box in 
> 
> https://admin.fedoraproject.org/pkgdb/acls/name/Django-south
> 

It is in fact a button with "Retire package" written on it. You have to be logged in to see it. This is a necessary part of the retirement process, could you please do that? After that, I believe this bug can be closed.

> 'fedpkg retire' has been done.
> 
> It seems that the step 'git push' is missing from the instructions given in
> [1] in this bug report.
> 
> The ticket for retiring the renamed packages has been filed too:
> 
> https://fedorahosted.org/rel-eng/ticket/5315

Thanks.

Comment 4 Domingo Becker 2012-09-03 21:35:46 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > There is no retired check box in 
> > 
> > https://admin.fedoraproject.org/pkgdb/acls/name/Django-south
> > 
> 
> It is in fact a button with "Retire package" written on it. You have to be
> logged in to see it. This is a necessary part of the retirement process,
> could you please do that? After that, I believe this bug can be closed.
> 

Oops, I think I know why I don't see the 'Retire package' button: I'm using Fedora 14.

I will try later with a computer with Fedora 17.

cheers

Comment 5 Matthias Runge 2012-09-04 06:45:19 UTC
(In reply to comment #4)
> 
> Oops, I think I know why I don't see the 'Retire package' button: I'm using
> Fedora 14.
> 
> I will try later with a computer with Fedora 17.
> 
> cheers

Using fedora 14 shhouldn't be a problem. In fact, it's a web page, and it even should work on windows, but of course, you need to be logged in.

You're totally right, it's necessary to issue git push after running fedpkg retire.

Comment 6 Domingo Becker 2012-09-04 21:13:14 UTC
Created attachment 609778 [details]
The 'retire package' button does not shows in screen

Comment 7 Domingo Becker 2012-09-04 21:14:20 UTC
Created attachment 609779 [details]
'retire package' button showns when I print from firefox to cups-pdf

Comment 8 Domingo Becker 2012-09-04 21:20:13 UTC
It's strange because I don't see the button. Please, see comment #6.

When I print the screen to cups-pdf, the button shows up. Please see comment #7.

[me@mycomputer ~]$ uname -a
Linux mycomputer 3.5.3-1.fc17.x86_64 #1 SMP Wed Aug 29 18:46:34 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
[me@mycomputer ~]$ rpm -qa firefox
firefox-15.0-1.fc17.x86_64
[boris@boris64a ~]$ 

cheers

Comment 9 Bohuslav "Slavek" Kabrda 2012-09-05 05:18:20 UTC
(In reply to comment #8)
> It's strange because I don't see the button. Please, see comment #6.
> 
> When I print the screen to cups-pdf, the button shows up. Please see comment
> #7.
> 
> [me@mycomputer ~]$ uname -a
> Linux mycomputer 3.5.3-1.fc17.x86_64 #1 SMP Wed Aug 29 18:46:34 UTC 2012
> x86_64 x86_64 x86_64 GNU/Linux
> [me@mycomputer ~]$ rpm -qa firefox
> firefox-15.0-1.fc17.x86_64
> [boris@boris64a ~]$ 
> 
> cheers

Strange. Maybe it would be best if you reported this as a bug for pkgdb (And could you please put me to CC of that bug? I'm really curious about what's going on in there).

BTW is that button in html source of that page?

Comment 10 Matthias Runge 2012-11-01 19:29:06 UTC
ok, what's the status here? it looks like it isn't retired yet, and also Django-south is not blocked from f18. So basically we have TWO packages providing the same files.

Please fix asap.
Thank you.

Comment 11 Domingo Becker 2012-11-03 12:24:36 UTC
Sorry, but I still don't see the 'Retire Package' button. 

It is actually happening the same as in comment #8.

[user@mycomputer ~]$ uname -a 
Linux mycomputer 3.6.3-1.fc17.x86_64 #1 SMP Mon Oct 22 15:32:35 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

[user@mycomputer ~]$ rpm -qa firefox 
firefox-16.0.1-1.fc17.x86_64

A little newer but still the same problem.

kind regards

Domingo Becker

Comment 12 Matthias Runge 2012-11-03 20:11:47 UTC
OK, I can see that button, but nothing happens if I try it.

Filed a rel-eng ticket to block Django-south from f18, master branch.

https://fedorahosted.org/rel-eng/ticket/5386

Comment 13 Matthias Runge 2012-11-03 20:58:50 UTC
Ok, retired and blocked.

Comment 14 Domingo Becker 2012-11-04 01:13:42 UTC
I have some other packages in the same situation.

django-threadedcomments

django-contact-form

django-ajax-selects


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