Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1842107 - F33FailsToInstall: python3-osmium
Summary: F33FailsToInstall: python3-osmium
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: pyosmium
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tom Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1841335
Blocks: F33FTBFS F33FailsToInstall PYTHON39
TreeView+ depends on / blocked
 
Reported: 2020-05-30 17:33 UTC by Igor Raits
Modified: 2020-06-17 10:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-17 10:00:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Igor Raits 2020-05-30 17:33:11 UTC
Hello,

Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (ignatenkobrain).

Your package (pyosmium) Fails To Install in Fedora 33:

can't install python3-osmium:
  - nothing provides python(abi) = 3.8 needed by python3-osmium-3.0.0-1.fc33.x86_64
  
If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks.

P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors.

P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/rawhide-gating/multi-builds/

Thanks!

Comment 1 Tom Hughes 2020-05-30 23:10:40 UTC
Yes I know. It will be rebuilt just as soon as all the dependencies are available.

Comment 2 Igor Raits 2020-06-08 07:00:47 UTC
Hello,

This is the first reminder (step 3 from https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs).

If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.

Comment 3 Tom Hughes 2020-06-08 07:22:01 UTC
The only information you need is that which I have already provided, namely that this is waiting on a fix for BZ#1785415 so please do stop wasting my time with ridiculous needinfo requests.

Comment 4 Tom Hughes 2020-06-08 07:23:55 UTC
Sorry I mean to say BZ#1841335 but the point is that it's clearly listed as a blocking this bug.

Comment 5 Miro Hrončok 2020-06-08 09:02:48 UTC
The automated comment said: "If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED."

And that is indeed the way to stop the reminders.

The "ridiculous needinfo requests" is a pre-requisite for following the policy.

Comment 6 Tom Hughes 2020-06-08 09:31:15 UTC
It doesn't say that in the original message when the bug is opened though, so there's no way to avoid at least one needinfo unless you're psychic.

It's an abuse of "needinfo" though - there was no information being requested here, it was just using "needinfo" as a way to get bugzilla to annoy people with daily emails demanding an update.

The problem with the policy is that it's geared to an assumption that people aren't paying attention and need to be constantly prodded to look at bugs which means that those of us that are paying attention and are aware of our bugs are forced into having to know the right magic changes to make to bugs (whether changing status to ASSIGNED or acknowledging needinfo requests) to stop the onslaught of automated bug spam from filling our mailboxes.

All the extra noise actually makes it more likely that I will miss things, not less :-(

Comment 7 Miro Hrončok 2020-06-08 09:52:32 UTC
> It doesn't say that in the original message when the bug is opened though...

I believe this is fixed now, right Igor?

> The problem with the policy is that it's geared to an assumption that people aren't paying attention...

Unfortunately, this is the majority case :(


> All the extra noise actually makes it more likely that I will miss things, not less :-(

Yes, I believe that during "things are slightly broken" periods, this is annoying for packagers who are aware. I don't know how to fix this wile keeping it working for the majority case.

I suppose that we should make it more clear that "set this to ASSIGNED to acknowledge you are aware and will eventually fix this" is the appropriate "stop" mechanism (instead of, for example, simply saying so).


Note You need to log in before you can comment on or make changes to this bug.