[Bug 1605337] Re: [MIR] virtualbox
Here the updated reference link https://salsa.debian.org/pkg-virtualbox-team/virtualbox/tree/master/src/VBox/Devices/PC/BIOS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605337 Title: [MIR] virtualbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1605337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605337] Re: [MIR] virtualbox
the reference to the assembler file is not valid anymore. Would need an update. If we don't have the source, then we could promote it to restricted, not to main. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605337 Title: [MIR] virtualbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1605337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605337] Re: [MIR] virtualbox
** Changed in: virtualbox (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605337 Title: [MIR] virtualbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1605337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605337] Re: [MIR] virtualbox
** Bug watch added: Debian Bug tracker #709899 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709899 ** Also affects: virtualbox (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709899 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605337 Title: [MIR] virtualbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1605337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605337] Re: [MIR] virtualbox
Little update after a long conversation on irc with Oracle guys (with a big thanks to them). To be clear, I always had in mind that we were using prebuilt BIOS binaries, but this seems to be *not the case. Workflow. many *.c files Open Watcom some asm files yasm BIOS quoting upstream "we have no other choice. there simply is no (debian conforming) open source compiler which can deal with x86 segmentation, which is absolutely vital for implementing a working BIOS" irc conversation (at the begin I was looking to the wrong issue I admit) LocutusOfBorg: regarding the assembly BIOS, if you have an appropriate assembler on your system, to my limited knowledge the assembly BIOS should be build automatically, unless OpenWatcom is found. You said you failed to build the assembly BIOS. I believe that should happen automatically during the build if you have a suitable assembler installed. Looks like the configure file could do with fixing. And we should and don't check for yasm, but should use it if it is there. That is what needs fixing. so, if I understand correctly you check for watcom, and use the built one if no watcom is found but probably yasm is good too, even if the configure is not aware of that Right, but probably only used (that is the idea of Make after all) if no binary is found. and with rm src/VBox/Devices/PC/BIOS/VBoxBiosAlternative* I can see if it is correct your claim Wait... That is the assembly code you want to build. No idea where the binary is... "Auto Generated source file. Do not edit." There is probably some PcBiosBin file somewhere. it is written on that VBoxBiosAlternative files Sure, it is generated by OpenWatcom. But by us, not by you. this is the problem we can't generate that asm file I guess You can't generate the C files we feed to OpenWatcom. And you are free to ignore the message and use the assembly as your original source. A fork, so to speak. This package is not part of the Debian operating system. It is in the "contrib" area of the Debian archive because it requires a non-free compiler (Open Watcom) to build the BIOS. Upstream provides pre-built BIOS images which is used instead. this is what I get from debian/copyright, it has been done long time ago LocutusOfBorg: btw, there are no BIOS binaries in the vbox source tree. only the VBoxBiosAlternative.* files, which are used if you don't have OpenWatcom. The question is: are some autogenerated asm files "enough source files" to be considered part of Ubuntu main? this is an example https://anonscm.debian.org/cgit/pkg-virtualbox/virtualbox.git/tree/src/VBox/Devices/PC/BIOS/VBoxBiosAlternative.asm that would save us a lot of effort in the split. G. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605337 Title: [MIR] virtualbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1605337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605337] Re: [MIR] virtualbox
** Changed in: virtualbox (Ubuntu) Assignee: (unassigned) => Matthias Klose (doko) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605337 Title: [MIR] virtualbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1605337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1605337] Re: [MIR] virtualbox
Gianfranco, thanks for the feedback! On Thu, Jul 21, 2016 at 05:49:03PM -, LocutusOfBorg wrote: > Just to make you aware, I already did the split and it is even currently > waiting on trusty new queue > (the split was done because the guest packages needs to be rebuilt on top > of the lts stack, but this is OT). Ah, I hadn't noticed this - the SRU NEW queue often goes unnoticed, please feel free to ping me or another member of the SRU team directly on #ubuntu-release when you have packages there that need review I see that there is split packaging there, but I don't see anything to handle the splitting of the upstream orig.tar.gz for into free and non-free parts, which would be a requirement for putting the virtualbox-guest source in main. Have you looked into this at all? Perhaps if you even have an analysis of which parts of the source would need to be split, that would give us a head start on automating this split. > The question is: if you take over the maintenance, just please take it > over on Debian too! I really would like to avoid maintain a delta for > such a huge and problematic package. Seeing that you are an uploader of the virtualbox package in Debian, I was indeed quite eager to talk with you about how this might work. Would you be interested in having this split done in Debian, so that Debian could also have the virtualbox guest components in main instead of contrib - and so that this packaging could be kept in sync? Please note that when I spoke above of cloud or server teams being responsible for "maintenance", I meant it only in the sense of Ubuntu-specific maintenance - SRU requirements, security updates, the occasional temporal delta. They would not be committing to maintain the package in Debian, and I am 100% in agreement that we should avoid a delta here between Debian and Ubuntu. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605337 Title: [MIR] virtualbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1605337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605337] Re: [MIR] virtualbox
** Changed in: virtualbox (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605337 Title: [MIR] virtualbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1605337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605337] Re: [MIR] virtualbox
Just to make you aware, I already did the split and it is even currently waiting on trusty new queue (the split was done because the guest packages needs to be rebuilt on top of the lts stack, but this is OT). The question is: if you take over the maintenance, just please take it over on Debian too! I really would like to avoid maintain a delta for such a huge and problematic package. thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605337 Title: [MIR] virtualbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1605337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
