{"diffoscope-json-version": 1, "source1": "/srv/reproducible-results/rbuild-debian/r-b-build.K1ZePJTJ/b1/asterisk_20.6.0~dfsg+~cs6.13.40431414-2_armhf.changes", "source2": "/srv/reproducible-results/rbuild-debian/r-b-build.K1ZePJTJ/b2/asterisk_20.6.0~dfsg+~cs6.13.40431414-2_armhf.changes", "unified_diff": null, "details": [{"source1": "Files", "source2": "Files", "unified_diff": "@@ -13,8 +13,8 @@\n 8661f6162dcd7918ec37dc7073bcc9f6 92016 comm optional asterisk-mp3_20.6.0~dfsg+~cs6.13.40431414-2_armhf.deb\n e7b559a51c063a1fc8e51bf789b4ffd8 66208 debug optional asterisk-mysql-dbgsym_20.6.0~dfsg+~cs6.13.40431414-2_armhf.deb\n 6d88d5807eace4e8f169d639eea92716 90656 comm optional asterisk-mysql_20.6.0~dfsg+~cs6.13.40431414-2_armhf.deb\n f82f73d7827eba7ec722a34403ccad4a 1122932 debug optional asterisk-ooh323-dbgsym_20.6.0~dfsg+~cs6.13.40431414-2_armhf.deb\n acee2215266405674c71064856e52392 364432 comm optional asterisk-ooh323_20.6.0~dfsg+~cs6.13.40431414-2_armhf.deb\n 559462ff8963f28a7774a6e40b5a4c46 1295092 debug optional asterisk-tests-dbgsym_20.6.0~dfsg+~cs6.13.40431414-2_armhf.deb\n 6fc2b99625146ac1edf265e24eb6fb6e 581148 comm optional asterisk-tests_20.6.0~dfsg+~cs6.13.40431414-2_armhf.deb\n- d2be6d71c875faafc8ca6d6a9b2e2538 2226340 comm optional asterisk_20.6.0~dfsg+~cs6.13.40431414-2_armhf.deb\n+ bd3592c2d550935106ea3078a22b1b72 2226344 comm optional asterisk_20.6.0~dfsg+~cs6.13.40431414-2_armhf.deb\n"}, {"source1": "asterisk_20.6.0~dfsg+~cs6.13.40431414-2_armhf.deb", "source2": "asterisk_20.6.0~dfsg+~cs6.13.40431414-2_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 2024-01-30 10:42:08.000000 debian-binary\n -rw-r--r-- 0 0 0 8444 2024-01-30 10:42:08.000000 control.tar.xz\n--rw-r--r-- 0 0 0 2217704 2024-01-30 10:42:08.000000 data.tar.xz\n+-rw-r--r-- 0 0 0 2217708 2024-01-30 10:42:08.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": "@@ -35410,337 +35410,14 @@\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@@ -39862,14 +39539,337 @@\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"}]}]}, {"source1": "xz --list", "source2": "xz --list", "unified_diff": "@@ -1,13 +1,13 @@\n Streams: 1\n Blocks: 1\n- Compressed size: 2165.7 KiB (2217704 B)\n+ Compressed size: 2165.7 KiB (2217708 B)\n Uncompressed size: 6560.0 KiB (6717440 B)\n Ratio: 0.330\n Check: CRC64\n Stream Padding: 0 B\n Streams:\n Stream Blocks CompOffset UncompOffset CompSize UncompSize Ratio Check Padding\n- 1 1 0 0 2217704 6717440 0.330 CRC64 0\n+ 1 1 0 0 2217708 6717440 0.330 CRC64 0\n Blocks:\n Stream Block CompOffset UncompOffset TotalSize UncompSize Ratio Check\n- 1 1 12 0 2217664 6717440 0.330 CRC64\n+ 1 1 12 0 2217668 6717440 0.330 CRC64\n"}]}]}]}