Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister
 
PerlMonks  

rt://46333 links to rt.perl.org not rt.cpan.org

by Anonymous Monk
on Feb 24, 2017 at 01:57 UTC ( [id://1182683]=monkdiscuss: print w/replies, xml ) Need Help??

Replies are listed 'Best First'.
Re: rt://46333 links to rt.perl.org not rt.cpan.org
by kcott (Archbishop) on Feb 24, 2017 at 03:18 UTC

    I've checked, and can confirm, this.

    In the short term, I imagine fixing this is just a matter of s/perl/cpan/ in the code that generates the link.

    In the longer term, can I suggest something similar to what's currently used for [man://]:

    • [rt://nnnnn;cpan] generates a link to https://rt.cpan.org/Public/Bug/Display.html?id=nnnnn
    • [rt://nnnnn;perl] generates a link to https://rt.perl.org/Public/Bug/Display.html?id=nnnnn
    • [rt://nnnnn] continues as currently documented, i.e. generates a link to https://rt.cpan.org/Public/Bug/Display.html?id=nnnnn

    — Ken

      In the short term, I imagine fixing this is just a matter of s/perl/cpan/ in the code that generates the link.

      I'm not sure how nodes are stored internally, but I suspect that might break the links in nodes that have come to rely on the current behavior. Maybe it's the documentation that should be fixed first.

        G'day haukex,

        That seemed like a reasonable comment when I read it; however, I then read jdporter's response: the "current behavior" is actually only very recent behaviour.

        Anyway, as per his subsequent response, the current behaviour is back to the original behaviour. The link I put in my private scratchpad ([rt://46333]), to initially check the reported problem, now resolves to http://rt.cpan.org/Public/Bug/Display.html?id=46333, so this is again working as documented.

        Having said that, there are two documentation issues. When the change to [rt://] was made ("on 2016-12-21"):

        — Ken

      Hi,

      How about, instead

      rt:// keeps going to cpan .... and rtp:// goes to perl?

      But I haven't done any search to see how people have been using or misusing rt:// ...

      But perlrt, perlbug, cpanrt sound better to me

      perldeltas use  [perl #113054] and [cpan #86613] which also sounds good to me :)

        I was only making a suggestion (based on existing usage with [man://]). Your suggestions also have merit. Let's see what others think.

        I don't use [rt://] myself. When I have posted links to either of those, it's typically after viewing the ticket, and a copy/paste of the RT's URI is less work than typing rt://....

        — Ken

Re: rt://46333 links to rt.perl.org not rt.cpan.org
by jdporter (Paladin) on Feb 24, 2017 at 21:59 UTC

    I made that change on 2016-12-21 because linking to rt.cpan.org by ID seemed to be broken. In fact, it seems rt.cpan.org fails for some IDs, rt.perl.org fails for other IDs. Examples:

      86969:  at cpan (OK)  - at perl (ERR) 
      130361: at cpan (ERR) - at perl (OK) 
    

    Can someone elucidate what's going on? Maybe we can "code around it". :-)

    I reckon we are the only monastery ever to have a dungeon stuffed with 16,000 zombies.

      I think not every bug ID is a visible ticket on each of the bug trackers. Think of spam tickets which might use up an ID.

      The perl.org RT instance is for bugs in Perl while the CPAN RT instance is for bugs in CPAN modules. So the two URLs will lead to different tickets for the same ticket ID, and should stay that way.

        Ah! Interesting. Thank you. I will revert that change.

        Update: Done.

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: monkdiscuss [id://1182683]
Approved by kcott
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others pondering the Monastery: (5)
As of 2024-03-28 23:16 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found