| Summary: | app-emulation/qemu-1.5 version bump | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | luis <li0ngm> |
| Component: | Current packages | Assignee: | Doug Goldstein (RETIRED) <cardoe> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | andcycle-gentoo, qemu+disabled, schinkelm |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
luis
2013-05-20 22:53:33 UTC
Into the 0-day bin. Hello, just to give the button send, I felt that should have expected more (nerves), an error today hehe sorry. Thank you,byee (In reply to comment #1) > Into the 0-day bin. Hello How much time have to wait to report new version of programs? For future bugs reports knows when i can or no. I dont know , and i dont see nothing in the faq as i remember. Thanks.. Luis, Don't waste my time messing with this bug. The more I have to mess with it, the less time there is to work on qemu. If its so important to you, become a Gentoo developer and do the bump yourself. Or pay a Gentoo developer to do it for you. I like most Gentoo developers work on Gentoo on a volunteer basis in my free time. I happen to volunteer my time to a number of other open source projects, such as QEMU, so I was more than aware of the release before hand. If this was a trivial version bump it would have happened without your prodding. If you must have the absolute latest qemu, I provide an ebuild within the tree that can do that for you. qemu-9999. Look at the docs and you can install 1.5 yourself on your machine and test various configurations and potentially report back useful information regarding other changes. (In reply to comment #4) > Luis, > > Don't waste my time messing with this bug. The more I have to mess with it, > the less time there is to work on qemu. > > If its so important to you, become a Gentoo developer and do the bump > yourself. Or pay a Gentoo developer to do it for you. I like most Gentoo > developers work on Gentoo on a volunteer basis in my free time. I happen to > volunteer my time to a number of other open source projects, such as QEMU, > so I was more than aware of the release before hand. If this was a trivial > version bump it would have happened without your prodding. > > If you must have the absolute latest qemu, I provide an ebuild within the > tree that can do that for you. qemu-9999. Look at the docs and you can > install 1.5 yourself on your machine and test various configurations and > potentially report back useful information regarding other changes. Man, u kidding me? So why u do here ? The version bumps not possible with you?. Well i put all this nice understand anwsers by you to see if im wrong or you. Because im goind crazy. (I understand u dotn have time or something similar ,but your awnsers and more.. are O_O Luís, doing a 0-day bump is usually considered "rude". As Doug already told you, and is usually the case with package maintainers, he tracks upstream releases, so he's aware of the 1.5 release. "Fighting" with a maintainer is never the correct way to get a package bump, so please step back and wait until the package is bumped - unless you want to test it yourself and provide an ebuild + patches. (In reply to comment #6) > Luís, > > doing a 0-day bump is usually considered "rude". > As Doug already told you, and is usually the case with package maintainers, > he tracks upstream releases, so he's aware of the 1.5 release. "Fighting" > with a maintainer is never the correct way to get a package bump, so please > step back and wait until the package is bumped - unless you want to test it > yourself and provide an ebuild + patches. I understand all that I have never said that not.If we do not understand what the for that standing up to people who live in the same "House" without think about whether that person, or in this case, read if you could offend someone and then get an idea and 'normal' opinion.What to my and just like many more, (I'm sure) that tell me to pay a programmer of gentoo that makes it me or etc etc.No I know that tells me that, since until then not you had said nothing.I sometimes "help" people like you that you use your time free to take this project forward.And I love it. But as I'm not programmed, sometimes attempt to help by donating something via paypal to gentoo developers.And to answer me so, as if I were a shit or I did not do anything and to pay you for doing something that I asked in good faith, was enough that I had said that the was aware and now I could not but that he was attentive.And it would have been more simple to understand and this had not come up here. (In reply to comment #7) > (In reply to comment #6) > > Luís, > > > > doing a 0-day bump is usually considered "rude". > > As Doug already told you, and is usually the case with package maintainers, > > he tracks upstream releases, so he's aware of the 1.5 release. "Fighting" > > with a maintainer is never the correct way to get a package bump, so please > > step back and wait until the package is bumped - unless you want to test it > > yourself and provide an ebuild + patches. > > I understand all that I have never said that not.If we do not understand > what the for that standing up to people who live in the same "House" without > think about whether that person, or in this case, read if you could offend > someone and then get an idea and 'normal' opinion.What to my and just like > many more, (I'm sure) that tell me to pay a programmer of gentoo that makes > it me or etc etc.No I know that tells me that, since until then not you had > said nothing.I sometimes "help" people like you that you use your time free > to take this project forward.And I love it. But as I'm not programmed, > sometimes attempt to help by donating something via paypal to gentoo > developers.And to answer me so, as if I were a shit or I did not do anything > and to pay you for doing something that I asked in good faith, was enough > that I had said that the was aware and now I could not but that he was > attentive.And it would have been more simple to understand and this had not > come up here. Well *** Bug 471482 has been marked as a duplicate of this bug. *** *** Bug 473664 has been marked as a duplicate of this bug. *** |
