Bug#682736: unblock: vmware-manager/0.2.0-2
On Mon, 2012-08-13 at 15:38 +1000, Alexander Zangerl wrote: sorry for the late response: after digging through this a few more times i've got an explanation for the debdiff output. [...] the problem is that the debian diff doesn't represent file deletions, and that i rather should have left the vmm filename intact and just installed it with its new name via debian/rules (hindsight and all that). net effect: a newly unpacked 0.2.0-2 includes the correct vwm file, but also a superfluous and unused vmm file from the orig tarball, which of course reflects only the state before the -1 changes were made. Okay. Assuming an upload could be made fairly quickly, I think I'd prefer a -3 which made the POD changes to the original binary and installed it under the new name. Thanks for working on this. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1345288868.31960.59.ca...@jacala.jungle.funky-badger.org
Bug#682736: unblock: vmware-manager/0.2.0-2
On Sat, 18 Aug 2012 12:21:08 +0100, Adam D. Barratt writes: Okay. Assuming an upload could be made fairly quickly, I think I'd prefer a -3 which made the POD changes to the original binary and installed it under the new name. Thanks for working on this. done; i've uploaded vmware-manager 0.2.0-3 an hour ago (and this time debdiff shows only the expected POD changes for vmm/vwm). regards az -- Alexander Zangerl + GnuPG Keys 0x42BD645D or 0x5B586291 + http://snafu.priv.at/ Outside of a dog, a book is a man's best friend. Inside of a dog, it's too dark to read. -- Groucho Marx signature.asc Description: Digital Signature
Processed: Re: Bug#682736: unblock: vmware-manager/0.2.0-2
Processing control commands: tags -1 + moreinfo Bug #682736 [release.debian.org] unblock: vmware-manager/0.2.0-2 Added tag(s) moreinfo. -- 682736: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682736 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.b682736.13448087486329.transcr...@bugs.debian.org
Bug#682736: unblock: vmware-manager/0.2.0-2
Control: tags -1 + moreinfo
On Wed, 2012-08-01 at 06:37 +0100, Adam D. Barratt wrote:
On 01.08.2012 06:22, Adam D. Barratt wrote:
adsb@franck:~$ dpkg-source -x
ftp/pool/contrib/v/vmware-manager/vmware-manager_0.2.0-1.dsc v-m1
[...]
adsb@franck:~$ dpkg-source -x
ftp/pool/contrib/v/vmware-manager/vmware-manager_0.2.0-2.dsc v-m2
[...]
adsb@franck:~$ diff -adNru v-m1 v-m2 | diffstat
[...]
vmm | 19
vwm | 1382
++
8 files changed, 1414 insertions(+), 16 deletions(-)
If you think debdiff is buggy, please file appropriate bug reports.
The
above agrees with what is shows, however.
Similarly, as an example:
adsb@franck:~$ diff -adNru v-m2/v{m,w}m | grep =
-file = ($cfgfile ? $cfgfile : \*DATA), # Read defaults from
__DATA__ section if we cant find a default file.
-default = 'global',
- -fallback = 'global',
-nocase = 1,
-allowempty = 1,
- -handle_trailing_comment = 1,
Ping?
Regards,
Adam
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/1344808661.2978.100.ca...@jacala.jungle.funky-badger.org
Bug#682736: unblock: vmware-manager/0.2.0-2
On Sun, 12 Aug 2012 22:57:41 +0100, Adam D. Barratt writes: Ping? sorry for the late response: after digging through this a few more times i've got an explanation for the debdiff output. in 0.2.0-1 there were some local changes to vmm, precisely the ones that debdiff reports now (in reverse): ie. the change from Number::Bytes::Format to Number::Format and the VMware::VIRuntime loading in eval. for 0.2.0-2 i renamed vmm to vwm, and adjusted the inline pod sections to reflect that name change. nothing else was modified. the problem is that the debian diff doesn't represent file deletions, and that i rather should have left the vmm filename intact and just installed it with its new name via debian/rules (hindsight and all that). net effect: a newly unpacked 0.2.0-2 includes the correct vwm file, but also a superfluous and unused vmm file from the orig tarball, which of course reflects only the state before the -1 changes were made. what's the verdict? upload a new version -3 that avoids the filename changes and concomitant spurious difference reports, or accept the current status with vmm(from -1) identical modulo doc changes to vwm(from -2) and ignore the unnecessary vmm(from orig tarball)? regards az -- Alexander Zangerl + GnuPG Keys 0x42BD645D or 0x5B586291 + http://snafu.priv.at/ When you understand UNIX, you will understand the world. When you understand NTyou will understand NT -- R. Thieme signature.asc Description: Digital Signature
Bug#682736: unblock: vmware-manager/0.2.0-2
On Sat, 28 Jul 2012 15:15:49 +0100, Adam D. Barratt writes:
On Wed, 2012-07-25 at 18:27 +1000, Alexander Zangerl wrote:
Please unblock package vmware-manager
the version in unstable fixes rc bug #680481,
which is a file name conflict between the
packages vmm and vmware-manager: both
provide a program named vmm, and the man page is
causing the clash. the fix consists of vmware-manager
switching to use /usr/bin/vwm (note: w).
Are vwm and vmm supposed to be identical, other than the name
change? The version of vmm shipped in -2 appears to include new
changes which are then not carried over in to vmw:
no, that's not the case but seems a problem invented by debdiff:
the package is git-hosted and -built and for some weird reason
debdiff hands out all kinds of weird deltas here...
attached you'll find a diff -ub between files from the binary packages:
vmm from the 0.2.0-1 and the renamed 0.2.0-2 vwm, which shows that
apart from renaming vmm into vwm in the POD sections nothing
has been changed.
regards
az
--- alt/usr/bin/vmm 2012-05-14 13:00:05.0 +1000
+++ neu/usr/bin/vwm 2012-07-08 19:42:57.0 +1000
@@ -2,32 +2,32 @@
# POD {{{
=head1 NAME
-vmm - Manage VMware virtual machines
+vwm - Manage VMware virtual machines
=head1 SYNOPSIS
- vmm command [options]
+ vwm command [options]
=over
=item BGlobal syntax:
- vmm command [-f] [-v+] [-w seconds] [@profile]
+ vwm command [-f] [-v+] [-w seconds] [@profile]
=item BCommand specific syntax:
- vmm clone [-o pool] [-c count] [-a datastore...] [-l folder] source vm new vm name
- vmm deploy [synonym of 'clone']
- vmm df [-h] [datastore...]
- vmm host [maintenance|restore|restart|shutdown|disconnect|reconnect] hosts...
- vmm list [-d col1,col2... | perl string] [-t title] [vm|datastore|host|pool|template][s] [patterns...]
- vmm migrate [-p low|normal|high] [-o pool] vms... host
- vmm move [-o pool] vms... datastore
- vmm setpool low|normal|high cpu|mem|all pools...
- vmm show [vm|datastore|host|pool] [items...]
- vmm snapshot [-t title] vms...
- vmm state on|off|suspend|reboot|shutdown|restart|standby vms...
- vmm version
+ vwm clone [-o pool] [-c count] [-a datastore...] [-l folder] source vm new vm name
+ vwm deploy [synonym of 'clone']
+ vwm df [-h] [datastore...]
+ vwm host [maintenance|restore|restart|shutdown|disconnect|reconnect] hosts...
+ vwm list [-d col1,col2... | perl string] [-t title] [vm|datastore|host|pool|template][s] [patterns...]
+ vwm migrate [-p low|normal|high] [-o pool] vms... host
+ vwm move [-o pool] vms... datastore
+ vwm setpool low|normal|high cpu|mem|all pools...
+ vwm show [vm|datastore|host|pool] [items...]
+ vwm snapshot [-t title] vms...
+ vwm state on|off|suspend|reboot|shutdown|restart|standby vms...
+ vwm version
=back
@@ -108,7 +108,7 @@
=item Bversion
Display various version informaiton about the connected vServer and local API.
-This command is the default if no actual command is specified (i.e. just running 'vmm' with nothing else specified).
+This command is the default if no actual command is specified (i.e. just running 'vwm' with nothing else specified).
=back
@@ -134,16 +134,16 @@
Specifies which profile to use when addressing the vServer.
This can be an entry within the config file or the URL (with optional login details) e.g.
- vmm version @cluster1
- vmm version @cluster2
- vmm version @https://cluster1.acme.edu
- vmm version @https://usern...@cluster1.acme.edu
- vmm version @https://username:passw...@cluster1.acme.edu
+ vwm version @cluster1
+ vwm version @cluster2
+ vwm version @https://cluster1.acme.edu
+ vwm version @https://usern...@cluster1.acme.edu
+ vwm version @https://username:passw...@cluster1.acme.edu
Examples 1 and two assume 'custer1' and 'customer2' have been defined in the examples file (see EXAMPLES). The further examples specify the connection information on the command line.
Specifying the password from the command line is exceptionally silly and should be avoided.
-If username and/or password is omitted (such as in examples 3 and 4 above) they will be prompted for when vmm is run.
+If username and/or password is omitted (such as in examples 3 and 4 above) they will be prompted for when vwm is run.
=item B-c
@@ -228,8 +228,8 @@
=back
Force continue if an error occurs.
-Normaly if an error occurs vmm will stop processing any operations specified on the command line.
-If this flag is enabled vmm will continue operation as if no error occured.
+Normaly if an error occurs vwm will stop processing any operations specified on the command line.
+If this flag is enabled vwm will continue operation as if no error occured.
=item B--human
@@ -268,7 +268,7 @@
=back
Dry run mode.
-When enabled vmm will continue as normal but no actual call to the VMware VServer is made.
+When enabled vwm will continue as normal but no actual call to the VMware VServer is made.
=item B--folder
@@ -414,69 +414,69 @@
=over
-=item Bvmm
Bug#682736: unblock: vmware-manager/0.2.0-2
On Wed, 2012-08-01 at 09:55 +1000, Alexander Zangerl wrote: On Sat, 28 Jul 2012 15:15:49 +0100, Adam D. Barratt writes: Are vwm and vmm supposed to be identical, other than the name change? The version of vmm shipped in -2 appears to include new changes which are then not carried over in to vmw: no, that's not the case but seems a problem invented by debdiff: the package is git-hosted and -built and for some weird reason debdiff hands out all kinds of weird deltas here... debdiff is displaying it because it's what's in the source package: adsb@franck:~$ dpkg-source -x ftp/pool/contrib/v/vmware-manager/vmware-manager_0.2.0-1.dsc v-m1 [...] adsb@franck:~$ dpkg-source -x ftp/pool/contrib/v/vmware-manager/vmware-manager_0.2.0-2.dsc v-m2 [...] adsb@franck:~$ diff -adNru v-m1 v-m2 | diffstat [...] vmm | 19 vwm | 1382 ++ 8 files changed, 1414 insertions(+), 16 deletions(-) If you think debdiff is buggy, please file appropriate bug reports. The above agrees with what is shows, however. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1343798528.1551.18.ca...@jacala.jungle.funky-badger.org
Bug#682736: unblock: vmware-manager/0.2.0-2
On 01.08.2012 06:22, Adam D. Barratt wrote:
adsb@franck:~$ dpkg-source -x
ftp/pool/contrib/v/vmware-manager/vmware-manager_0.2.0-1.dsc v-m1
[...]
adsb@franck:~$ dpkg-source -x
ftp/pool/contrib/v/vmware-manager/vmware-manager_0.2.0-2.dsc v-m2
[...]
adsb@franck:~$ diff -adNru v-m1 v-m2 | diffstat
[...]
vmm | 19
vwm | 1382
++
8 files changed, 1414 insertions(+), 16 deletions(-)
If you think debdiff is buggy, please file appropriate bug reports.
The
above agrees with what is shows, however.
Similarly, as an example:
adsb@franck:~$ diff -adNru v-m2/v{m,w}m | grep =
-file = ($cfgfile ? $cfgfile : \*DATA), # Read defaults from
__DATA__ section if we cant find a default file.
-default = 'global',
- -fallback = 'global',
-nocase = 1,
-allowempty = 1,
- -handle_trailing_comment = 1,
Regards,
Adam
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/27cce14229ef24aeeae4b9e7fae030fe@localhost
Bug#682736: unblock: vmware-manager/0.2.0-2
On Wed, 2012-07-25 at 18:27 +1000, Alexander Zangerl wrote: Please unblock package vmware-manager the version in unstable fixes rc bug #680481, which is a file name conflict between the packages vmm and vmware-manager: both provide a program named vmm, and the man page is causing the clash. the fix consists of vmware-manager switching to use /usr/bin/vwm (note: w). Are vwm and vmm supposed to be identical, other than the name change? The version of vmm shipped in -2 appears to include new changes which are then not carried over in to vmw: +* Install all the required CPAN modules + + cpan Config::IniFiles Getopt::Long Number::Bytes::Human Term::ReadKey Text::Glob - This requires the packages libclass-methodmaker-perl libcrypt-ssleay-perl - libsoap-lite-perl libuuid-perl libxml-libxml-perl. +* Setup the config file. See either the CONFIG section above or use the sample file from /usr/share/doc/vmm -* Setup the config file. See either the CONFIG section above or use the sample file from /usr/share/doc/vmware-manager. [...] +use Number::Bytes::Human qw/format_bytes/; -use Number::Format qw/format_bytes/; use Term::ReadKey; use Text::Glob qw/match_glob glob_to_regex/; +use VMware::VIRuntime; - -my $mod=VMware::VIRuntime; -die Couldn't load the VMware SDK: maybe you haven't installed it yet?\nPlease check the README file in /usr/share/doc/vmware-manager/ for details.\n -if (!eval require $mod); -$mod-import(); [...] my $cfg = Config::IniFiles-new( -file = ($cfgfile ? $cfgfile : \*DATA), # Read defaults from __DATA__ section if we cant find a default file. -default = 'global', + -fallback = 'global', -nocase = 1, -allowempty = 1, + -handle_trailing_comment = 1, What's going on with those? Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1343484949.18013.59.ca...@jacala.jungle.funky-badger.org
Bug#682736: unblock: vmware-manager/0.2.0-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package vmware-manager the version in unstable fixes rc bug #680481, which is a file name conflict between the packages vmm and vmware-manager: both provide a program named vmm, and the man page is causing the clash. the fix consists of vmware-manager switching to use /usr/bin/vwm (note: w). regards az unblock vmware-manager/0.2.0-2 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120725082745.31689.24039.report...@cft.snafu.priv.at
