[releng] Issue #7814: Fedora Scientific 29 Beta 1.3 vagrant box - virtualbox
issue
by Dusty Mabe
dustymabe added a new comment to an issue you are following:
``
i guess it's possible something in the package set is causing things to get locked down? Can you build images locally? If so I would try to build a cloud base image and verify it works then build the scientific image and make sure it doesn't, then try to add in packages and see if there is any one (or group) that causes the problem to crop up.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7814
5 years, 8 months
[releng] Issue #7814: Fedora Scientific 29 1Beta 1.3 vagrant box issue
by Dusty Mabe
dustymabe added a new comment to an issue you are following:
``
`bootloader --append="no_timer_check console=tty1 console=ttyS0,115200n8 net.ifnames=0 biosdevname=0" --location=mbr --timeout=1 --boot-drive=vdaautopart --type=plain --nohome --noboot --noswap` is all on one line in one of the files. that looks wrong
can you confirm that is the case?
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7814
5 years, 8 months
[releng] Issue #7825: Please fix the python-blivet-3.1.0-2.fc29 update
by Mohan Boddu
mohanboddu reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
As part of the [RC compose]((https://pagure.io/releng/issue/7803#comment-531392)), we have included python-blivet-3.1.0-2.fc29 build in the compose but the [update](https://bodhi.fedoraproject.org/updates/FEDORA-2018-85853d46b5) got unpushed. We have included a newer version of anaconda which is not in the update mentioned, but we need the python-blivet. So, the update needs to fixed so that we can push python-blivet to stable when we are a go with the beta release.
* When do you need this? (YYYY/MM/DD)
ASAP, before F29 Beta unfreeze
* When is this no longer needed or useful? (YYYY/MM/DD)
* If we cannot complete your request, what is the impact?
World will break.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7825
5 years, 8 months
[releng] Issue #7814: Fedora Scientific 29 1Beta 1.3 vagrant box issue
by Amit Saha
amitksaha added a new comment to an issue you are following:
``
Thanks for the tip! I did a diff, and besides the `packages`, the diff is:
```
diff cloud-base.cfg fedora-scientific.cfg
4c4,5
< bootloader --append="no_timer_check console=tty1 console=ttyS0,115200n8 net.ifnames=0 biosdevname=0" --location=mbr --timeout=1 --boot-drive=vdaautopart --type=plain --nohome --noboot --noswap
---
> bootloader --append="no_timer_check console=tty1 console=ttyS0,115200n8 net.ifnames=0 biosdevname=0" --location=mbr --timeout=1 --boot-drive=vda
> autopart --type=plain --nohome --noboot --noswap
13c14
< repo --name="koji-override-0" --baseurl=http://kojipkgs.fedoraproject.org/compose/29/Fedora-29-20180912.0/compose/Everything/x86_64/os
---
> repo --name="koji-override-0" --baseurl=http://kojipkgs.fedoraproject.org/compose/29/Fedora-29-20180916.0/compose/Everything/x86_64/os
15c16
< url --url="https://kojipkgs.fedoraproject.org/compose/29/Fedora-29-20180912.0/compos..."
---
> url --url="https://kojipkgs.fedoraproject.org/compose/29/Fedora-29-20180916.0/compos..."
```
I then compared the `classroom` vagrant image configuration with scientific, but cannot see any
other difference other than the packages.
Would you have any other suggestions?
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7814
5 years, 8 months
