Bug 22093 - java-1.8.0-openjdk-headless = 1:1.8.0.141-1.b16.1.mga6 won't install
Summary: java-1.8.0-openjdk-headless = 1:1.8.0.141-1.b16.1.mga6 won't install
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-29 06:32 CET by Oliver Burger
Modified: 2017-12-11 14:08 CET (History)
2 users (show)

See Also:
Source RPM: java-1.8.0-openjdk-1.8.0.141-1.b16.1.mga6.src.rpm
CVE:
Status comment:


Attachments

Description Oliver Burger 2017-11-29 06:32:26 CET
Description of problem:
The package java-1.8.0-openjdk-headless = 1:1.8.0.141-1.b16.1.mga6 can't be installed.

Because of this, most other updates fail.

How reproducible:
Type "urpmi --auto-update", urpmi trys to download this package and fails.
Because of that, the update fails.

This happens in a newly installed 64bit VM in VirtualBox.
Comment 1 Marja Van Waes 2017-11-29 08:17:43 CET
Hi Oliver, nice to see you again :-)

I don't have a Mageia 6 at hand, atm.

This is a fresh install, it is possible that you have more updates than can be handled in one default-size transaction, and that things that belong together don't end up in the same transaction :-/

Please retry, after first starting, as root 

   journalctl -af 2>&1 | tee log.txt

To rule out that problem is with packages needing one another not being in the same transaction, please increase the transaction size with the 
"--split-length" urpmi switch. You could try to set it to "0" for an unlimited transaction size.

If the problem persists, then attach log.txt to this report.

Cheers,
Marja

Keywords: (none) => NEEDINFO
CC: (none) => mageia, marja11

Comment 2 Oliver Burger 2017-12-11 14:08:19 CET
I'm sorry,

the problem was the company firewall.
For some unknown reason it blocks sevarl rpm packages.

In some cases I got a http 403 access forbidden, in some cases it just ran endlessly with no result.

After our IT whitelisted my prefferred mirror, everything is working again.

Status: NEW => RESOLVED
Keywords: NEEDINFO => (none)
Resolution: (none) => INVALID


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