{"diffoscope-json-version": 1, "source1": "/srv/reproducible-results/rbuild-debian/r-b-build.DxBZ1cl0/b1/asterisk_20.1.0~dfsg+~cs6.12.40431414-1_armhf.changes", "source2": "/srv/reproducible-results/rbuild-debian/r-b-build.DxBZ1cl0/b2/asterisk_20.1.0~dfsg+~cs6.12.40431414-1_armhf.changes", "unified_diff": null, "details": [{"source1": "Files", "source2": "Files", "unified_diff": "@@ -13,8 +13,8 @@\n fc4b41c5df79aa19d9072c011a3f6df6 165132 comm optional asterisk-mp3_20.1.0~dfsg+~cs6.12.40431414-1_armhf.deb\n 7dbfac6f794bb22da5a2237103351158 66420 debug optional asterisk-mysql-dbgsym_20.1.0~dfsg+~cs6.12.40431414-1_armhf.deb\n c029d1beccb4091c0bb65badf5b913e8 164000 comm optional asterisk-mysql_20.1.0~dfsg+~cs6.12.40431414-1_armhf.deb\n c277efa33866b46aa6a9fdc61243c2e1 1120004 debug optional asterisk-ooh323-dbgsym_20.1.0~dfsg+~cs6.12.40431414-1_armhf.deb\n 3baee870a809b1e596be67e6175dfd55 435656 comm optional asterisk-ooh323_20.1.0~dfsg+~cs6.12.40431414-1_armhf.deb\n 4ed9fbf8d896946397b60ac2bc6b8f12 1288484 debug optional asterisk-tests-dbgsym_20.1.0~dfsg+~cs6.12.40431414-1_armhf.deb\n dfe9948aa1f4bb513d43baf825cac842 652252 comm optional asterisk-tests_20.1.0~dfsg+~cs6.12.40431414-1_armhf.deb\n- d897023b74aefb5094ca6ac71f90c165 2308696 comm optional asterisk_20.1.0~dfsg+~cs6.12.40431414-1_armhf.deb\n+ 31c9aeffec08c2ac558e1ed2487e5ee5 2308684 comm optional asterisk_20.1.0~dfsg+~cs6.12.40431414-1_armhf.deb\n"}, {"source1": "asterisk_20.1.0~dfsg+~cs6.12.40431414-1_armhf.deb", "source2": "asterisk_20.1.0~dfsg+~cs6.12.40431414-1_armhf.deb", "unified_diff": null, "details": [{"source1": "file list", "source2": "file list", "unified_diff": "@@ -1,3 +1,3 @@\n -rw-r--r-- 0 0 0 4 2023-01-12 23:26:47.000000 debian-binary\n -rw-r--r-- 0 0 0 8400 2023-01-12 23:26:47.000000 control.tar.xz\n--rw-r--r-- 0 0 0 2300104 2023-01-12 23:26:47.000000 data.tar.xz\n+-rw-r--r-- 0 0 0 2300092 2023-01-12 23:26:47.000000 data.tar.xz\n"}, {"source1": "control.tar.xz", "source2": "control.tar.xz", "unified_diff": null, "details": [{"source1": "control.tar", "source2": "control.tar", "unified_diff": null, "details": [{"source1": "./md5sums", "source2": "./md5sums", "unified_diff": null, "details": [{"source1": "./md5sums", "source2": "./md5sums", "comments": ["Files differ"], "unified_diff": null}]}]}]}, {"source1": "data.tar.xz", "source2": "data.tar.xz", "unified_diff": null, "details": [{"source1": "data.tar", "source2": "data.tar", "unified_diff": null, "details": [{"source1": "./usr/share/asterisk/documentation/core-en_US.xml", "source2": "./usr/share/asterisk/documentation/core-en_US.xml", "unified_diff": null, "details": [{"source1": "./usr/share/asterisk/documentation/core-en_US.xml", "source2": "./usr/share/asterisk/documentation/core-en_US.xml", "comments": ["Ordering differences only"], "unified_diff": "@@ -34357,14 +34357,337 @@\n \n \n \n \n \n extended\n \n+ \n+ Core Geolocation Support\n+ \n+ \n+ Location\n+ \n+ Parameters for defining a Location object\n+ \n+ \n+ Must be of type 'location'.\n+ \n+ \n+ Location specification type\n+ \n+ \n+ \n+ \n+ The\n+ location_info\n+ parameter must contain a comma separated list of IANA codes\n+\t\t\t\t\t\t\t\t\tor synonyms describing the civicAddress of this location.\n+\t\t\t\t\t\t\t\t\tThe IANA codes and synonyms can be obtained by executing\n+\t\t\t\t\t\t\t\t\tthe CLI command\n+ geoloc show civicAddr_mapping\n+ .\n+ \n+ \n+ \n+ \n+ The\n+ location_info\n+ parameter must contain a comma\n+\t\t\t\t\t\t\t\t\tseparated list valid GML elements describing this location.\n+ \n+ \n+ \n+ \n+ The\n+ location_info\n+ parameter must contain a single\n+\t\t\t\t\t\t\t\t\tURI parameter which contains an external URI describing this location.\n+ \n+ \n+ \n+ \n+ \n+ \n+ Location information\n+ \n+ \n+ The contents of this parameter are specific to the\n+\t\t\t\t\t\t\tlocation\n+ format\n+ .\n+ \n+ \n+ \n+ location_info = country=US,A1="New York",city_district=Manhattan,\n+\t\t\t\t\t\tA3="New York", house_number=1633, street=46th, street_suffix = Street,\n+\t\t\t\t\t\tpostal_code=10222,floor=20,room=20A2\n+ \n+ \n+ location_info = Shape=Sphere, pos3d="39.12345 -105.98766 1920", radius=200\n+ \n+ \n+ location_info = URI=https:/something.com?exten=${EXTEN}\n+ \n+ \n+ \n+ \n+ \n+ Fully qualified host name\n+ \n+ \n+ This parameter isn't required but if provided, RFC8787 says it MUST be a fully\n+\t\t\t\t\t\tqualified host name. IP addresses are specifically NOT allowed. The value will be placed\n+\t\t\t\t\t\tin a\n+ loc-src\n+ parameter appended to the URI in the\n+ Geolocation\n+ header.\n+ \n+ \n+ \n+ \n+ Location determination method\n+ \n+ This is a rarely used field in the specification that would\n+\t\t\t\t\t\tindicate the method used to determine the location. Its usage and values should be\n+\t\t\t\t\t\tpre-negotiated with any recipients.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ Level of confidence\n+ \n+ This is a rarely used field in the specification that would\n+\t\t\t\t\t\tindicate the confidence in the location specified. See RFC7459\n+\t\t\t\t\t\tfor exact details.\n+ Sub-parameters:\n+ \n+ \n+ One of:\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ A percentage indicating the confidence.\n+ \n+ \n+ \n+ \n+ https://www.rfc-editor.org/rfc/rfc7459\n+ \n+ \n+ \n+ \n+ Profile\n+ \n+ Parameters for defining a Profile object\n+ \n+ \n+ Must be of type 'profile'.\n+ \n+ \n+ PIDF-LO element to place this profile in\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ Based on RFC5491 (see below) the recommended and default element\n+\t\t\t\t\t\t\tis\n+ device\n+ .\n+ \n+ \n+ \n+ https://www.rfc-editor.org/rfc/rfc5491.html#section-3.4\n+ \n+ \n+ \n+ Reference to a location object\n+ \n+ \n+ Reference to a location object\n+ \n+ \n+ Reference to a location object\n+ \n+ \n+ location specification type\n+ \n+ xxxx\n+ \n+ \n+ \n+ Notes to be added to the outgoing PIDF-LO document\n+ \n+ \n+ The specification of this parameter will cause a\n+ <note-well>\n+ element to be added to the\n+\t\t\t\t\t\toutgoing PIDF-LO document. Its usage should be pre-negotiated with\n+\t\t\t\t\t\tany recipients.\n+ \n+ \n+ \n+ \n+ Sets the value of the Geolocation-Routing header.\n+ \n+ \n+ Sets if empty Civic Address elements should be suppressed\n+\t\t\t\t\tfrom the PIDF-LO document.\n+ \n+ \n+ Determine which profile on a channel should be used\n+ \n+ \n+ \n+ Use the incoming profile if it exists and has location information, otherwise use the\n+\t\t\t\t\t\t\tconfigured profile if it exists and has location information. If neither profile has location\n+\t\t\t\t\t\t\tinformation, nothing is sent.\n+ \n+ \n+ Use the configured profile if it exists and has location information, otherwise use the\n+\t\t\t\t\t\t\tincoming profile if it exists and has location information. If neither profile has location\n+\t\t\t\t\t\t\tinformation, nothing is sent.\n+ \n+ \n+ Discard any incoming profile and use the configured profile if it exists and\n+\t\t\t\t\t\t\tit has location information. If the configured profile doesn't exist or has no\n+\t\t\t\t\t\t\tlocation information, nothing is sent.\n+ \n+ \n+ Discard any configured profile and use the incoming profile if it exists and\n+\t\t\t\t\t\t\tit has location information. If the incoming profile doesn't exist or has no\n+\t\t\t\t\t\t\tlocation information, nothing is sent.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ Get or Set a field in a geolocation profile\n+ \n+ \n+ The profile parameter to operate on. The following fields from the\n+\t\t\t\tLocation and Profile objects are supported.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ Additionally, the\n+ inheritable\n+ field may be\n+\t\t\t\tset to\n+ true\n+ or\n+ false\n+ to control\n+\t\t\t\twhether the profile will be passed to the outgoing channel.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ When used to set a parameter on a profile, if the profile doesn't already exist, a new\n+\t\tone will be created automatically.\n+ \n+ The\n+ ${GEOLOCPROFILESTATUS}\n+ channel variable will be set with\n+\t\ta return code indicating the result of the operation. Possible values are:\n+ \n+ \n+ \n+ Success\n+ \n+ \n+ No or not enough parameters were supplied\n+ \n+ \n+ There was an internal error finding or creating a profile\n+ \n+ \n+ There was an issue specific to the parameter specified\n+\t\t\t(value not valid or parameter name not found, etc.)\n+ \n+ \n+ \n+ \n \n SIP Resource using PJProject\n \n \n Endpoint\n \n \n@@ -38467,337 +38790,14 @@\n \n \n \n \n \n \n \n- \n- Core Geolocation Support\n- \n- \n- Location\n- \n- Parameters for defining a Location object\n- \n- \n- Must be of type 'location'.\n- \n- \n- Location specification type\n- \n- \n- \n- \n- The\n- location_info\n- parameter must contain a comma separated list of IANA codes\n-\t\t\t\t\t\t\t\t\tor synonyms describing the civicAddress of this location.\n-\t\t\t\t\t\t\t\t\tThe IANA codes and synonyms can be obtained by executing\n-\t\t\t\t\t\t\t\t\tthe CLI command\n- geoloc show civicAddr_mapping\n- .\n- \n- \n- \n- \n- The\n- location_info\n- parameter must contain a comma\n-\t\t\t\t\t\t\t\t\tseparated list valid GML elements describing this location.\n- \n- \n- \n- \n- The\n- location_info\n- parameter must contain a single\n-\t\t\t\t\t\t\t\t\tURI parameter which contains an external URI describing this location.\n- \n- \n- \n- \n- \n- \n- Location information\n- \n- \n- The contents of this parameter are specific to the\n-\t\t\t\t\t\t\tlocation\n- format\n- .\n- \n- \n- \n- location_info = country=US,A1="New York",city_district=Manhattan,\n-\t\t\t\t\t\tA3="New York", house_number=1633, street=46th, street_suffix = Street,\n-\t\t\t\t\t\tpostal_code=10222,floor=20,room=20A2\n- \n- \n- location_info = Shape=Sphere, pos3d="39.12345 -105.98766 1920", radius=200\n- \n- \n- location_info = URI=https:/something.com?exten=${EXTEN}\n- \n- \n- \n- \n- \n- Fully qualified host name\n- \n- \n- This parameter isn't required but if provided, RFC8787 says it MUST be a fully\n-\t\t\t\t\t\tqualified host name. IP addresses are specifically NOT allowed. The value will be placed\n-\t\t\t\t\t\tin a\n- loc-src\n- parameter appended to the URI in the\n- Geolocation\n- header.\n- \n- \n- \n- \n- Location determination method\n- \n- This is a rarely used field in the specification that would\n-\t\t\t\t\t\tindicate the method used to determine the location. Its usage and values should be\n-\t\t\t\t\t\tpre-negotiated with any recipients.\n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- Level of confidence\n- \n- This is a rarely used field in the specification that would\n-\t\t\t\t\t\tindicate the confidence in the location specified. See RFC7459\n-\t\t\t\t\t\tfor exact details.\n- Sub-parameters:\n- \n- \n- One of:\n- \n- \n- \n- \n- \n- \n- \n- A percentage indicating the confidence.\n- \n- \n- \n- \n- https://www.rfc-editor.org/rfc/rfc7459\n- \n- \n- \n- \n- Profile\n- \n- Parameters for defining a Profile object\n- \n- \n- Must be of type 'profile'.\n- \n- \n- PIDF-LO element to place this profile in\n- \n- \n- \n- \n- \n- \n- \n- Based on RFC5491 (see below) the recommended and default element\n-\t\t\t\t\t\t\tis\n- device\n- .\n- \n- \n- \n- https://www.rfc-editor.org/rfc/rfc5491.html#section-3.4\n- \n- \n- \n- Reference to a location object\n- \n- \n- Reference to a location object\n- \n- \n- Reference to a location object\n- \n- \n- location specification type\n- \n- xxxx\n- \n- \n- \n- Notes to be added to the outgoing PIDF-LO document\n- \n- \n- The specification of this parameter will cause a\n- <note-well>\n- element to be added to the\n-\t\t\t\t\t\toutgoing PIDF-LO document. Its usage should be pre-negotiated with\n-\t\t\t\t\t\tany recipients.\n- \n- \n- \n- \n- Sets the value of the Geolocation-Routing header.\n- \n- \n- Sets if empty Civic Address elements should be suppressed\n-\t\t\t\t\tfrom the PIDF-LO document.\n- \n- \n- Determine which profile on a channel should be used\n- \n- \n- \n- Use the incoming profile if it exists and has location information, otherwise use the\n-\t\t\t\t\t\t\tconfigured profile if it exists and has location information. If neither profile has location\n-\t\t\t\t\t\t\tinformation, nothing is sent.\n- \n- \n- Use the configured profile if it exists and has location information, otherwise use the\n-\t\t\t\t\t\t\tincoming profile if it exists and has location information. If neither profile has location\n-\t\t\t\t\t\t\tinformation, nothing is sent.\n- \n- \n- Discard any incoming profile and use the configured profile if it exists and\n-\t\t\t\t\t\t\tit has location information. If the configured profile doesn't exist or has no\n-\t\t\t\t\t\t\tlocation information, nothing is sent.\n- \n- \n- Discard any configured profile and use the incoming profile if it exists and\n-\t\t\t\t\t\t\tit has location information. If the incoming profile doesn't exist or has no\n-\t\t\t\t\t\t\tlocation information, nothing is sent.\n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- Get or Set a field in a geolocation profile\n- \n- \n- The profile parameter to operate on. The following fields from the\n-\t\t\t\tLocation and Profile objects are supported.\n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- Additionally, the\n- inheritable\n- field may be\n-\t\t\t\tset to\n- true\n- or\n- false\n- to control\n-\t\t\t\twhether the profile will be passed to the outgoing channel.\n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- When used to set a parameter on a profile, if the profile doesn't already exist, a new\n-\t\tone will be created automatically.\n- \n- The\n- ${GEOLOCPROFILESTATUS}\n- channel variable will be set with\n-\t\ta return code indicating the result of the operation. Possible values are:\n- \n- \n- \n- Success\n- \n- \n- No or not enough parameters were supplied\n- \n- \n- There was an internal error finding or creating a profile\n- \n- \n- There was an issue specific to the parameter specified\n-\t\t\t(value not valid or parameter name not found, etc.)\n- \n- \n- \n- \n \n bluetooth\n no\n extended\n \n \n no\n"}]}]}]}]}]}