From: Mike Looijmans <mike.looijmans@topic.nl>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Is There a Package Limit to use of Smart / RPM?
Date: Mon, 30 May 2016 09:17:46 +0200 [thread overview]
Message-ID: <574BE91A.7030901@topic.nl> (raw)
In-Reply-To: <8F90F944E50427428C60E12A34A309D24B6D12CAA4@carmd-exchmb01.sierrawireless.local>
We've seen similar effects with IPK packages and opkg, but the problem then
isn't so much the package manager, but it's just that some packages don't
upgrade properly when bunched together with some others. For example, two
packages A and B which individually upgrade just fine, but if you try to
upgrade them both, something in their pre/post-install/remove actions messes
things up and causes one or both of them to fail.
Also, things like upgrading network components while using ssh to start the
upgrade, or upgrading parts of the package manager can also cause strange
upgrade problems.
I doubt there's some magic "maximum number of packages" in any package manager.
On 28-05-16 21:16, Darcy Watkins wrote:
> Hi,
>
> In my project, we have exceeded 700 packages and have run into numerous issues
> using smart with rpm handling large transactions on the target (e.g. update
> from a non-PR service build to a PR-service build resulting in all RPMs being
> updated, though most are just version/release 'bumped' by the PR service).
>
> Before I dig too deep, I figured I would see if anyone recognizes this
> signature as a known issue.
>
> 1. Are there any hard coded limits to number of packages that can be handled
> in a smart/rpm transaction? (Particularly around 700)?
>
> 2. Are there known issues related to when 'smart' updates itself and/or 'rpm'?
>
> Daisy branch
>
> Layerscape (ARM) architecture
>
> Kernel 3.19 (yocto-linux + BSP patches)
>
> Installing on ext3 rootfs
>
> Building on CentOS7
>
> All appeared to work fine until recently when a bunch of added kernel modules
> and other firmware packages were added, which makes me wonder about a magic
> limit of 700.
>
> Thanks in advance for your insights.
>
>
>
> Regards,
>
> Darcy
>
> Darcy Watkins :: Staff Engineer, Firmware
>
> SIERRA WIRELESS
> Direct +1 604 233 7989 :: Fax +1 604 231 1109 :: Main +1 604 231 1100
> 13811 Wireless Way :: Richmond, BC Canada V6V 3A4
> [M1]
> dwatkins@sierrawireless.com :: www.sierrawireless.com ::
> www.inmotiontechnology.com
>
>
>
Kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
next prev parent reply other threads:[~2016-05-31 0:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-28 19:16 Is There a Package Limit to use of Smart / RPM? Darcy Watkins
2016-05-30 7:17 ` Mike Looijmans [this message]
2016-05-30 15:15 ` Darcy Watkins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=574BE91A.7030901@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.