After upgrade from 4.3.1 rev 40062 to 4.4.1 rev 40089 I have noticed my Debian repositories are no longer updating their index files. After looking at the logs it appears that the 4.4.x vintage has switched to a new mechanism for parsing the control files within the packages.
We have a variety of 'bad' packages that dpkg cannot extract due to the control.tar.gz coming after the data.tar.gz and the control file containing empty fields, i.e. "Depends: ". In versions of Artifactory prior to 4.4.x the indexer was able to parse these bad packages and update the index without any issue. In the new versions these package cause the indexer to fail. We use this repository as an Opkg target and it has always been fine with the 'bad' packages. Since 4.4.x has added native support for Opkg repositories I may look at migrating, but from initial testing it appears that the Opkg package indexer is just running dpkg and has the same failures. Is there any way of getting the old behavior back or am I going to be forced to try and fix all the package artifacts we have in there? Thanks for any help. -- View this message in context: http://forums.jfrog.org/Debian-Opkg-Package-Extractor-in-4-4-x-tp7580734.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
