Bug 1183227 - ibus-sunpinyin-2.0.99-1.1.riscv64.rpm appears to be corrupted
Summary: ibus-sunpinyin-2.0.99-1.1.riscv64.rpm appears to be corrupted
Status: REOPENED
Alias: None
Product: openSUSE.org
Classification: openSUSE
Component: BuildService (show other bugs)
Version: unspecified
Hardware: Other Linux
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Hillwood Yang
QA Contact: Adrian Schröter
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-09 12:05 UTC by Florian Weimer
Modified: 2021-11-08 13:29 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Weimer 2021-03-09 12:05:23 UTC 
primary.xml for https://download.opensuse.org/ports/riscv/tumbleweed/repo/oss/ contains this:

<package type="rpm">
  <name>ibus-sunpinyin</name>
  <arch>riscv64</arch>
  <version epoch="0" ver="2.0.99" rel="1.1"/>
  <checksum type="sha256" pkgid="YES">4cb8703b289f371c6ea39ff351100b24a54177a968e4269914ede443daccf30f</checksum>
  <summary>Sunpinyin module for ibus</summary>
  <description>ibus-sunpinyin is a wrapper around SunPinyin which enables user to use
SunPinyin with IBus framework.</description>
  <packager>http://bugs.opensuse.org</packager>
  <url>https://github.com/sunpinyin/sunpinyin</url>
  <time file="1614688606" build="1614688435"/>
  <size package="238730" installed="495184" archive="499052"/>
  <location href="riscv64/ibus-sunpinyin-2.0.99-1.1.riscv64.rpm"/>

Indicating an RPM size of 238730. But the downloads for https://download.opensuse.org/ports/riscv/tumbleweed/repo/oss/riscv64/ibus-sunpinyin-2.0.99-1.1.riscv64.rpm are all 233508 bytes in size (apparently independently of the mirror).
Comment 1 Hillwood Yang 2021-03-11 08:53:54 UTC 
This is a bug of ibus-sunpinyin, please check you network.
Comment 2 Florian Weimer 2021-03-11 11:11:06 UTC 
Thanks. My network is fine, as far as I can tell.

It seems this bug was mistriaged. This looks like a problem with the repository master or perhaps the compose generation tools. Inconsistent data was pushed to the mirror network. It is probably not a package-specific bug.