[Q] updating other people's packages on npackd.appspot.com?

[GoogleCodeExporter]

Hi, this is actually a question and likely not a bug.

What should I do when I detect a buggy/obsolete version  of a package on 
npackd.appspot.com?

An example is the Virtualbox package, v4.3.17 has a a serious bug that prevents 
VMs from starting, it has been fixed in 4.3.20 but the package is still not 
updated. Another one is the bleachbit package which is currently stuck at v1.2 
on npackd.appspot.com, but v1.7 (!) is available on the official website.

I don't have the required permissions to edit those packages/provide/detect a 
new version. I've tried emailing the package maintainers, but got no reply so 
far. Some may even use a dummy mail address for this.

How can I help fixing this?
Isn't this effectively a bug as someone can add a new package to the list, 
never check it again, locking up the package to the version he added?

Thanks

Original issue reported on code.google.com by nodiscc on 15 Dec 2014 at 4:35

[GoogleCodeExporter]

Normally all packages are updated once every 3 months. I do it regardless of 
the initial package creator. If there is something very important, you could 
file an issue and I will update the package out of order. If you would like to 
contribute, I could give you the permissions for the packages.

Original comment by tim.lebe...@gmail.com on 15 Dec 2014 at 8:46

[GoogleCodeExporter]

Thanks for your reply, yes if you could check updates for the mentioned 
packages (http://npackd.appspot.com/p/org.virtualbox.virtualbox and 
http://npackd.appspot.com/p/bleachbit) it would be nice.

Otherwise I could do it myself. But what would definitely be an improvement is 
to allow anyone to use the "Detect new version" button. Is this doable (or what 
could go wrong)?

Original comment by nodiscc on 22 Dec 2014 at 12:05

[GoogleCodeExporter]

It would be possible to allow everybody to detect new versions. It would be 
even possible to do it automatically by a regularly running program.

The important thing is that every package version should be tested. I test 
every package version by installing it and removing it.

I added you to the list of editors for VirtualBox and BlechBit. Please add the 
new versions.

Original comment by tim.lebe...@gmail.com on 3 Jan 2015 at 10:45

[GoogleCodeExporter]

You are right that adding new versions needs some manual checks (I added 
BleachBit 1.6 and Virtualbox 4.3.20 and had to do a bit of tweaking for both, 
"Detect new version" correctly detected the new version number, but was wrong 
on the download URL).

I don't know if something can be done; of course there are other implications 
to an automatic version detection (does the new installer contain toolbar/crap 
installers? This has to be checked manually). Adding people to the editors list 
may be good enough.

Anyway I have updated Bleachbit (confirmed working) and I'm currently trying to 
get the VBox 4.3.20 installer to work. I get this error message:

MSI (s) (D4:F8) [14:23:05:906]: Product: Oracle VM VirtualBox 4.3.20 -- This 
application only runs on 32-bit Windows systems. Please install the 64-bit 
version of Oracle VM VirtualBox 4.3.20!

The previous versions worked properly, so the architecture-specific installer 
may have changed name, or the architecture detection in npackd fails. Npackd 
tries to run 'set setup=VirtualBox-4.3.20-r96997-MultiArch_x86.msi ' which 
seems wrong.

Any help is welcome

Original comment by nodiscc on 3 Jan 2015 at 1:27

[GoogleCodeExporter]

I marked Bleachbit 1.7 as reviewed. 

There are 2 VirtualBox packages: 32 bit and 64 bit. By choosing the right 
package you decide which version should be installed. If your platform does not 
match, you get an error.

Original comment by tim.lebe...@gmail.com on 3 Jan 2015 at 9:16

[GoogleCodeExporter]

Thanks for reviewing bleachbit.

> There are 2 VirtualBox packages: 32 bit and 64 bit. 

That was not my understanding. From the virtualbox 64 package details 
(org.virtualbox.virtualbox64):

> WARNING: this package will not be updated anymore. The package "VirtualBox" 
contains 32 bit and 64 bit software. virtual machine (VM). WARNING: 4 
confirmations about unsigned drivers on windows XP

added to this, http://download.virtualbox.org/virtualbox/4.3.20/ only has ONE 
installer for both x86 and x86-64 platforms. I think npackd/the installer does 
some architecture detection magic, but in this case it fails. Installing the 
Virtualbox package (not the 64-bit one) used to work on my 64-bit machine, but 
now fails.

What am I doing wrong?

Original comment by nodiscc on 4 Jan 2015 at 9:13

[GoogleCodeExporter]

You were right, but I decided now to re-establish the distinction between the 
32 and 64 bit packages and un-deprecate the 64 bit one. Now both packages 
should work.

Original comment by tim.lebe...@gmail.com on 8 Jan 2015 at 9:39

[GoogleCodeExporter]

Original comment by tim.lebe...@gmail.com on 8 Jan 2015 at 9:39

• Changed state: FixedPleaseTest

[GoogleCodeExporter]

Original comment by tim.lebe...@gmail.com on 16 Jan 2015 at 7:20

• Changed state: Fixed