At 09:50 07/08/2015 +0200, Piotr Strzyzewski wrote:
On Fri, Aug 07, 2015 at 09:52:20AM +0300, Hank Nussbacher wrote:
Hank,
I believe I have encountered a bug with email processing of updates via auto-dbm@ripe and have not been able to engage the people there via ticket NCC#2015080034. I reported it and the ticket was quickly closed without being solved. I therefore ask for help from the hive-mind.
The recently added "remarks:" line is causing parsing problems. The line looks like this:
remarks: For information on "status:" attribute read https://www.ripe.net/data-tools/db/faq/faq-status-values-legacy-resources
First I tried editing an object but the parser kept chopping the line as follows:
remarks: For information on "status:" attribute read https: //www.ripe.net/data-tools/db/faq/faq-status-values-legacy-resources ***Error: "https" is not a known RPSL attribute
So I just deleted the line and was able to update the object. But now I want to delete an intenum object with the "remarks" line. When I do that I get:
remarks: For information on "status:" attribute read https: //www.ripe.net/data-tools/db/faq/faq-status-values-legacy-resources ... created: 1970-01-01T00:00:00Z last-modified: 2014-05-27T13:18:49Z source: RIPE
***Error: Object [inetnum] 192.114.48.0 - 192.114.63.255 doesn't match version in database
The parser again chops the line at https and auto-starts a new line and therefore flags the entry as not macthing the version in the DB.
Is there a workaround for this? Some escape character that will cause it not to break the line?
Are you absolutely sure that this is not due to some other reasons? I have "reproduced" your object under my ip space just a minute ago and was able to delete it without any problems via email interface. The only important difference is that it doesn't have LEGACY status. I have created it one more time - take a look at 83.230.58.0/24. Just let me know if you see any meaningful differences to 192.114.48.0/20.
Indeed your object looks correct and has the proper remarks line. Someone else encountered the same issue with a legacy object so the bug might be specific to LEGACY objects only. -Hank
Piotr
-- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski@polsl.pl