I agree on -1 for now. I'd be willing to reconsider if it gets back in
Debian and we could sync it from there.
--
[FFe][karmic] Please update verlihub to 0.9.8e-r2 version
https://bugs.launchpad.net/bugs/391279
You received this bug notification because you are a member of Ubuntu
Bugs, which is
problems is there all multiple builds flags / options that could be used
and you know, we cannot build a package with different build options in
it. So, it's up to you, but my suggestion is to not re-introduce it into
the archive.
--
[FFe][karmic] Please update verlihub to 0.9.8e-r2 version
https
Hmmm, maybe should packaged with options/flags which are usually using
by users? And include package verlihub-plugins.
--
[FFe][karmic] Please update verlihub to 0.9.8e-r2 version
https://bugs.launchpad.net/bugs/391279
You received this bug notification because you are a member of Ubuntu
Bugs, wh
@Stefan,
this package shouldnt be re-uploaded into Debian again, it would make no
sense. Looks like users prefers to build / install it manually to enable
any eventual feature. The popcon reported 30 installations in Debian, so
I would suggest to not re-introduce this package again into the archiv
Hi,
sorry, but -1 from me here at this time in the cycle, as it was removed
from Ubuntu as well, and hence would need to be treated as new package.
I'd suggest to start maintaining this package in Debian, that way we
could sync it for karmic+1.
(marking as invalid, please upload to revu, as this
** Summary changed:
- [karmic] Please update verlihub to 0.9.8e-r2 version
+ [FFe][karmic] Please update verlihub to 0.9.8e-r2 version
** Changed in: verlihub (Ubuntu)
Assignee: Artur Rona (ari-tczew) => (unassigned)
** Changed in: verlihub (Ubuntu)
Status: Incomplete => New
--
[FF