Package version number

First of all hi to all of you!
I'm little confuesd from time to time, when upgrading my system. For example downloading firefox 2.0.0.12-x two times day by day. I assume that -x stands for build number of specific package, am I right ?
If so wouldn't be beter to place newest packages first to testing repo and after one or two days move to extra ? Somthing like that would prevent people (using only core and extra repos) from downloading same thing for 2 or more times. I think that testing, unstable and even community are the best place to test package not core and extra.
Arch is supposed to be a bleeding edge distro with newest software, I understand that. But I think it would be best to test builds for few days before they get to core or extra.
Last edited by lukslab (2008-02-15 17:00:12)

lukslab wrote:
brebs wrote:It contained security fixes - we want those ASAP.
I understand why it is crucial for some packages to be as fast as possible in extra, but sometimes few hours in testing would be enough to find out that there's something wrong with build.
There was nothing wrong with the build, it worked just fine, except for the occasional security flaw left wide open for an attacker. How exactly do you test that before putting into 'extra'?
You make it sound so easy, but have u tried to be a developer and release packages? Not everyone on the internet works at the same time, what is a normal day for you is an evening and morning for someone else.
I was gonna mention xdelta, but I see shining already did that, maybe u could offer some of your expertise to this project...

Similar Messages

Question nVidia Chipset Drive Package Version Number.

Question nVidia Chipset Drive Package Version Number.
Hope this question is in the right sub forum.
I have see this question asked on several Forums, but never see a answer.
How do you tell which Chipset Driver Package Version is installed on your system, other than going to the Device Manager calling up the properties for each device and record the version number and comparing it to what listed for the Drive Package version?
Roger

I agree with you Richard.
I wouldn't say super fast ram though, I buy Crucial. It is very nice ram and does not break the bank. (no heatsinks on it or any other expenses)
Maybe I offended you, Bcc, by accident. I'm just trying to help folks on these forums and I have been with the nforce since day one. I have never seen this issue happen (or anything like it) on this board.
Like my suggestion, (if that didn't work, I would have continued to work) if I couldn't disable the agp host I would have uninstalled it (the device itself) and let windows try again. It could have been an nforce package issue and not with the detonator. I wish when these problems occurred, that I had the opportunity to try and fix these very rare occurences and examine the issue at my own desk.
I see too many people jump to the conclusion that they have found the mystery bug and go tell nvidia to recall the boards and fix it. I would not try to tell you that you are clueless about computers, as I don't have any idea how well you know them. But as an experienced technical writer/helper, I'm inclined to speak to the people as if they are dumb. As you can guess, many aren't, and they think that I may be saying they are, but at least they understand the situation.
More than the majority of problems are caused by heat. Too much heat will cause funny things to start happening to your computer. Sometimes it's just the ram, or maybe the cpu that get overheated. With summer coming, it's prime time to see the 'heat' problem creep up. I'm sure this wasn't the case with your issue, but it is overlooked most of the time.
Anyway, I'm glad your happy and your problem is fixed.

Display Package version number in HTML?

Hi,
My customer wants to display the version number of the apps/xx package in the HTML.
I'm just wondering if this is a good idea, i.e. the actual package contents could be overwritten, but the package doesn't change.
Also - how could that be achieved? There is a services JSP in the CRX package manager - could that be used?
http://localhost:4502/crx/packmgr/service.jsp
Thanks!

The subject line & description looks contridactory. I am assuming you are looking for package version, For that You should be able to get using jcr package api [1]. Ex:- vJcrPackageDefinition.getId().getVersionString()
http://dev.day.com/docs/en/cq/current/javadoc/com/day/jcr/vault/packaging/JcrPackageDefini tion.html

Error - The version number in the package is not valid. The version number cannot be greater than current version number

whats does this error mean
i download 2008 r2 and try to open package but still getting error
Error 1
Error loading The version number in the package is not valid. The version number cannot be greater than current version number.
Error 2
Error loading Package migration from version 8 to version 3 failed with error 0xC001700A "The version number in the package is not valid. The version number cannot be greater than current version number.".

can you tell me which version it is >
i try to fix in dtexec
getting following error :
Started: 2:02:13 PM
Error: 2015-01-30 14:02:14.68
Code: 0xC000F427
Source: Member Eligibility
Description: To run a SSIS package outside of SQL Server Data Tools you must
install Member Eligibility of Integration Services or higher.
End Error
Warning: 2015-01-30 14:02:14.69
Code: 0x80019002
Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution
method succeeded, but the number of errors raised (2) reached the maximum allow
ed (1); resulting in failure. This occurs when the number of errors reaches the
number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the e
rrors.
End Warning
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 2:02:13 PM
Finished: 2:02:14 PM
i cannot upgrade original package

Package creation overwrites version number while submitting to WP store

I'm creating a package for submission the first time and I have set the version to 1.1.0.0, but when the package is uploaded to the associated app in Dev center, the package version is showing as "2015.203.1452.4045" instead of "1.1.0.0".
I really do not want the app to be published with a major version of 2015. I went and did a search on the entire solution for the version, but couldn't find any reference.
package.appxmanifest shows
<Identity Name="AppID" Publisher="PubID" Version="1.1.0.0" />
What am I doing wrong?

Bumping.
I still haven't figured anything out in this respect. Assistance would be greatly appreciated.

SCCM 2012 R2 CU3 installation successfull but the Full Version number still is 5.00.7958.1000

Hi Guys
I have a SCCM 2012R2 in Windows 2008R2 box with a Secondary Site also in Windows 2008R2. Before proceeding with the upgrade to CU3 I took a snapshot, installed Windows Management Framework 4.0 to get PowerShell 4.0 in order to run a health Check, all
fine until this point.
I installed CU3 and checked that the value in CULevel in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Setup is 3 and also check the
version that is displayed in the About System Center Configuration Manager dialog box is
5.00.7958.1401
I checked the log file C:\Windows\Temp\cm12-r2cu3-kb2994331-x64-enu.log and all good in there as well. So it's fair to say the installation was successful..??
the next step was to upgrade my secondary site from the Primary site console, so I went to Administration / Site Configuration / Sites and when I right clicked my Primary Server to check its properties I realised that the Version number was still
5.00.7958.1000 and the option to upgrade my secondary site is greyed out.
I haven't been able to find any information regarding this issue, in fact I am not sure if is a technical issue or human issue :)
the questions are, how do I upgrade my secondary site and why the difference in between version?
Regards
Jesus Gonzalez

Works as dessigned. The site version number will only show the version of the latest major build, which is R2 in your case. The same with upgrading your secondary site, that's only possible via the console, with a major build. For upgrading your secondary
site you can now use the created package R2 CU3 - server update.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Version number and updating extension

I wonder where to set my application version number, I have tried at the bundle manifest but if setting at extension it is not shown anywhere at the extension manager and I don't know how to get this value for an "About" window.
Therefore I have set the bundle version to match my application number, this way at least the number is visible in the manager.
Also if I try to install an updated version of my extension the extension manager asks me to delete previous version because it conflicts with this one, I expected that the extension manager would ask if updating; am I doing something the wrong way ?

Update: this post has the answer for this first part: http://forums.adobe.com/message/4687256#4687256
The version number that shows up in Adobe Extension Manager is controlled in the .mxi file.
<macromedia-extension name="com.zaalabs.MyExtension" requires-restart="true" version="1.2.3">
I haven't found a way yet to pull the version number directly from the MXI file at runtime to show in an about window. To work around this we actually populate the version number in two places using an ANT script.
One in MyExtensionVersion.as which gets compiled in and can be looked up at runtime, and then other in the MXI file.
package
public class MyExtensionVersion
// This will be populated from the MyExtensionVersion.as.template
public static const VERSION_NUMBER:String = "1.2.3";
Then in our application we can lookup MyExtensionVersion.VERSION_NUMBER
Message was edited by: Nate Beck

Frorefront Protection for Exchange 2010 Version Number

Afternoon Community
I am currently research and planning the upgrade of an MS Exchange 2010 Virtual Server. One of the steps requires the upgrade of Forefront Protection for Exchange to be updated to the latest Rollup (KB230203 - Rollup 5). Due to ongoing projects i am aware
that Forefront has never been upgraded by us.
A few weeks ago we noticed our license for the product was due to expire, so we extended the license until Dec 2015. I have noticed that the version number of Forefront is now showing as 11.0.727.0 (Forefront Protection 2010 w Rollup 4). We havent installed
any of the Rollup Hotfixes and i can find no trace of the install under control panel/programs and features.
1. Has anyone recently updated their license and seen that it has changed their version number?
2. How can i confirm that no Rollup Hotfix has been installed?
3. If i go ahead and try to install KB2619883 (Rollup 4), will it cleanly install or will it fail as Forefront thinks the package is already at the correct level?
Any help on this issue would be greatly appreciated.
Barry Fitzpatrick

Hi,
Maybe you can check the Installed Updates in Programs and Features under Control Panel. In addition, if you have Windows PowerShell, you can use Get-Hotfix cmdlet to get the hotfixes that have been applied to the local computer.
Best regards,
Susie

Best practice when upstream does not provide version number

I'm currently preparing a package for the game Dreamfall Chapters, unfortunately the Developer does not (yet) provide a Version number.
What is the best practice for this? Just count the releases and set epoch when they finally provide one themselves?
thanks in advance!

If you are missing a version number, you could use the date. Prefix it with "r" in case you want to avoid epoch when upstream decides to start versioning.
pkgver=r20140122
If you have another release on the same day, increment another subversion
pkgver=r20140122.1
Counting the releases by hand is poor practice (you could miss one). Do it only if upstream provides the count.
Edit: To tie the version stronger to the release, you can also add a part of the archive hash, e.g. +m###### with the first 6 characters of the md5sum.
pkgver=r20140122+m23df1e
Edit: r as prefix is better, thanks rumpelsepp.
Last edited by progandy (2014-10-22 09:32:56)

Which file in Omni.ja contains the version number in HELP | ABOUT

We are using Firefox in a corporate locked down environment.
we have made a number of changes to files in the OMNI.JA file to configure Firefox accordingly.
We now have a newer version of firefox to install/package however, when we replace the default omni.ja file in FF 10.0.10 and go into HELP | ABOUT it shows the version number of FF that the omni.ja file came from, ie 10.0.4.
Which file(s) need to be replaced in omni.ja so that when we select HELP | ABOUT it shows the correct version of 10.0.10 ?
regards
Bill

hello biffal, which changes to the omnia.ja file have you done originally? maybe there's a better way to do it, because this file will be overwritten by each & every firefox update...

The version number cannot be greater than current version number

i am deployingmy ssis package which is in 2012.(version 6)
and my ssis server also in 2012.
but i am getting error:
"the version number in package is not valid, the version number cannot be greater than current verison number"
and one more thing how to see ifmy package is in 2012,by looking it in notepad?

Hi coool_sweet,
Based on the error message that "The version number in the package is not valid. The version number cannot be greater than current version number.", we can infer that the underlying cause may be that the current SSIS package is created in SQL Server
2012, while you are trying to open or execute it in SQL Server 2008R2 or earlier versions.
As to your scenario, I guess you are using old version of the DTEXEC instead of the new one to run the package. That means, the exe shipped with 2008R2 or earlier versions is picked up when it is expected to use the one shipped with 2012. So, obviously this
happens when SQL Server 2012 is running along with SQL Serve r2008R2 or earlier versions on the same machine.
To fix this issue, there are three workarounds to correct this.
Hard code the path of SQL Server 2012's DTEXEC while calling the SSIS package as shown below.
C:\Program Files\Microsoft SQL Server\110\DTS\Binn\DTEXEC.exe /F "D:\MyFolder\MyPackage.dtsx"
Rename the old exe in the 2008R2 path to a different name (Example:- C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTEXEC_Old.exe)
Go to PATH environmental variable and edit it in such a way that "C:\Program Files\Microsoft SQL Server\110\DTS\Binn" path appears well before the "C:\Program Files\Microsoft SQL Server\100\DTS\Binn" path.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

AppManifest.xml is being generated with the wrong version number

I am having a interesting problem which is preventing me from submitting an update to my app to the Windows Phone Store. I have done this 100 times and something is wrong with visual studio building the .xap file. Steps I am taking:
Update all version references in project settings and appmanifestWM to 1.4.0.0
Build Release version
Copy .xap from /bin/release
Upload as an app update to windows phone dev site
What happens is that the current version of the app (1.3.1.0) is still listed as the version of the app that the submission page is parsing out of the version (1.4.0.0) .xap file. I unzipped the xap file and looked at the appmanifest files and found that
the AppManifest.xaml has the correct version number but the AppManifest.xml still has version 1.3.1.0. If anyone could help me resolve this issue it would be greatly appreciated.

Thanks for your reply. I believe it is a bug with my solution because I have now tried all of these steps on two computers and uploaded using two different browsers and I still get a AppManifest.xml file that has version 1.3.1.0. I will copy and paste the
unzipped code from the AppManifest.xml file.
<?xml version="1.0" encoding="utf-8"?>
<Package xmlns="http://schemas.microsoft.com/appx/2010/manifest" xmlns:m2="http://schemas.microsoft.com/appx/2013/manifest" xmlns:m3="http://schemas.microsoft.com/appx/2014/manifest" xmlns:mp="http://schemas.microsoft.com/appx/2014/phone/manifest" xmlns:build="http://schemas.microsoft.com/developer/appx/2012/build" IgnorableNamespaces="build">

<Identity Name="50523CameronStair.MyDebts" Publisher="CN=FA4BA529-B82F-4A0F-A35C-6700BC51B3E1" Version="1.3.1.0" ProcessorArchitecture="neutral" />
<mp:PhoneIdentity PhoneProductId="c805a27c-951f-4c0d-a831-1126f9a70563" PhonePublisherId="51beaec0-db37-4002-81de-5e138a756b34" />
<Properties>
<DisplayName>MyDebtsApp</DisplayName>
<PublisherDisplayName>Cameron Stair</PublisherDisplayName>
<Logo>Assets\StoreLogo.png</Logo>
</Properties>
<Prerequisites>
<OSMinVersion>6.3.1</OSMinVersion>
<OSMaxVersionTested>6.3.1</OSMaxVersionTested>
</Prerequisites>
<Resources>
<Resource Language="EN-US" />
</Resources>
<Applications>
<Application Id="App" Executable="AGHost.exe" EntryPoint="MainPage.xaml">
<m3:VisualElements DisplayName="My Debts" Square150x150Logo="Assets\SquareTile150x150.png" Square44x44Logo="Assets\Logo.png" Description="A debt tracker app." ForegroundText="light" BackgroundColor="#464646" ToastCapable="false">
<m3:DefaultTile Square71x71Logo="Assets\SquareTile71x71.png"></m3:DefaultTile>
<m3:SplashScreen Image="Assets\SplashScreen.png" />
</m3:VisualElements>
<Extensions>
<Extension Category="windows.backgroundTasks" EntryPoint="AgHost.BackgroundTask">
<BackgroundTasks>
<Task Type="systemEvent" />
</BackgroundTasks>
</Extension>
</Extensions>
</Application>
</Applications>
<Extensions>
<Extension Category="windows.activatableClass.inProcessServer">
<InProcessServer>
<Path>AgHostSvcs.dll</Path>
<ActivatableClass ActivatableClassId="AgHost.BackgroundTask" ThreadingModel="both" />
</InProcessServer>
</Extension>
</Extensions>
<Capabilities>
<m3:Capability Name="contacts" />
</Capabilities>
<build:Metadata>
<build:Item Name="TargetFrameworkMoniker" Value="WindowsPhone,Version=v8.1" />
<build:Item Name="VisualStudio" Version="12.0" />
<build:Item Name="VisualStudioEdition" Value="Microsoft Visual Studio Professional 2013" />
<build:Item Name="OperatingSystem" Version="6.3.9600.16384 (winblue_rtm.130821-1623)" />
<build:Item Name="Microsoft.Build.AppxPackage.dll" Version="12.0.31101.0" />
<build:Item Name="ProjectGUID" Value="{C805A27C-951F-4C0D-A831-1126F9A70563}" />
<build:Item Name="MSAdvertising" Version="6.1" />
<build:Item Name="MakePri.exe" Version="6.3.9600.17298 (winblue.141024-1500)" />
</build:Metadata>
</Package>
As you can see the package version being generated is wrong. Can you explain where exactly in the solution that value is taken from? I thought it was from WMAppManifest but I could be wrong.
Edit: In looking at the code above and then rereading what I wrote I realized my blaring error. I completely forgot that Silverlight 8.1 apps have an appxmanifest as well and that data is drawn from that as well as WMAppManifest. I never updated the version
in that appxmanifest. Thank you for the help and I apologize for my stupidity.

Java.lang.ClassFormatError: Bad major version number

Hi friends,
I am using JWS2.0(trial version). I have uploaded class files into servlet (and respective packages), every thing was working fine. one fine day i started getting the 404 - file not found error(JWS not yet expired). I uninstalled the jws, j2sdk1.4.0, jre1.4.0 but with no result.
I even formated the system and loaded all again. But still i am getting the same problem.
The servlet is the simple HelloWorld servlet.
Through the SunExample its working fine. But the uploaded servlet is not getting recognised.
Here is the ErrorLog
[Tue Feb 22 17:26:29 GMT+05:30 2005] ClassLoaderFactory Error: Can not find Class : Hello [ ClassNotFoundException ]
[Tue Feb 22 17:26:31 GMT+05:30 2005] ClassLoaderError: (com.sun.server.loader.JarClassLoader@17d67e:\servlets) ERROR: Unable to load class local class Hello
[Tue Feb 22 17:26:31 GMT+05:30 2005] java.lang.ClassFormatError: Bad major version number
at java.lang.ClassLoader.defineClass(ClassLoader.java:219)
at com.sun.server.loader.ServletClassLoader.callDefineClass(ServletClassLoader.jav a:726)
at com.sun.server.loader.ServletClassLoader.checkAndDefineClass(ServletClassLoader .java:620)
at com.sun.server.loader.DirectoryClassLoader.getClassFromLocalDir(Compiled Code)
at com.sun.

Try re-compiling the Servlet. Make sure that the JDK version used to recompile is <= the version used to run the server (if you are using a higher jdk to compile the servlet, maybe Java 5.x, then you are to run, maybe Java 1.4.x, then use the -target option of javac to target the lower release...)

[svn:bz-trunk] 17299: BLZ-555: Bad version number in . class when starting JBoss 5.x with latest BlazeDS app

Revision: 17299
Revision: 17299
Author:   [email protected]
Date:     2010-08-12 05:36:37 -0700 (Thu, 12 Aug 2010)
Log Message:
BLZ-555: Bad version number in .class when starting JBoss 5.x with latest BlazeDS app
The "testdata" package has been compiled using JDK 1.6. When you try to run on application server that uses JDK 1.5, it will give the above error. Removed this test related package from the aspectjweaver-1.6.5.jar.
Checkintests: PASS
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-555
    http://bugs.adobe.com/jira/browse/aspectjweaver-1
Modified Paths:
    blazeds/trunk/lib/spring/aspectjweaver-1.6.5.jar

andre.ramaciotti wrote:And I'm not sure if you should put that & after exec awesome. It works fine here without it.
No & after entries in .xinitrc . You've commented out the awesome entry.

[Solved] Package version format confusion: 1:0.16.17-1 = 1.0?

I'm having troubles understanding the versioning scheme used above. According to the libtorrent site, the latest version of libtorrent-rasterbar is 1.0, released on 2014-07-02. Our package has the "last updated" date of 2014-07-24, so I assumed we have the most up-to-date version. However, on the download page of libtorrent, there is both the 1.0 version and a 0.16.17 version. Is the arch package out of date or not? If yes, why is the "weird" 1:0.16-17-1 format is used?
Last edited by Soukyuu (2014-07-28 15:41:31)

Without knowing anything about libtorrent or its history in our repos, that version number hints that it may have been downgraded in the repos due to a problem with the 1.0 line.
The initial "1:" is an epoch number which is incrememented whenever the actual version number decreases yet the lower number should replace the higher in a normal upgrade.
So speculating, I suspect libtorrent 1.0 was added to the repos replacing 0.16, but a bug or problem or some conflict with other repo packages was found. So for the time being, it was downgraded back to 0.16.17 until those problems can be resolved, and thus the "1:" was appended. To figure out if this was the case, or why this would have happened, check the repo history, mailing lists, and bug tracker for information.
But to answer your core question, no 1:0.16.17-1 != 1.0
EDIT: oops - is this about libtorrent-rasterbar, or libtorrent? My answer (and the version number in your title) are just for the former.
Last edited by Trilby (2014-07-28 12:45:01)

Package version number

Similar Messages

Maybe you are looking for