From: "Benoît BURNICHON" <Benoit.BURNICHON@airtag.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: [ptxdist] ptxdist-2011.01.0 bug in make ipkg-push
Date: Tue, 29 Nov 2011 11:36:26 +0000 [thread overview]
Message-ID: <3944866A166FC34A948C72DD5EDDCA2A1DC6992C@HQ0SBS01.airtag.local> (raw)
Hello All,
I know that this is an old release of ptxdist but for now, I cannot upgrade to the latest version.
I have my BSP set-up, I modified something in the ncurses config which changed libncurses.so.5.6.
But, when running ipkg-push, I end up with something like:
----8<--------8<--------8<--------8<--------8<--------8<--------8<--------8<--------8<----
...
checking pool for..: ncurses_5.6_armel.ipk
candidate........: ncurses_5.6-1_armel.ipk
candidate........: ncurses_5.6-2_armel.ipk
latest version...: ncurses_5.6-1_armel.ipk
comparing........: ncurses_5.6_armel.ipk with ncurses_5.6-1_armel.ipk
--- /tmp/ptxdist.Fs8Oia/first/data.md5 2011-11-29 11:30:21.863077130 +0100
+++ /tmp/ptxdist.Fs8Oia/second/data.md5 2011-11-29 11:30:21.875077118 +0100
@@ -1,6 +1,6 @@
data/lib/libform.so.5.6 ba902d5b074f2d3164977cccbfc40ff3
data/lib/libmenu.so.5.6 bca61f8054248a20ef3da9b9d8c1d74b
-data/lib/libncurses.so.5.6 8d1609660d6fa3883b474ed50e68afb5
+data/lib/libncurses.so.5.6 2c6704284feaae239717bd371b9b3c51
data/lib/libpanel.so.5.6 55828ecbe6c40ba3b328e2679f7ef963
data/usr/share/terminfo/a/ansi 6b3a86ff2f1b95acfdd820fbf8750b01
data/usr/share/terminfo/l/linux 645999d4afb490d40ff6b55239ad8173
ipkg-revision error: /var/www/ipkg-repository/myproject/pool/ncurses_5.6-2_armel.ipk already exists
RSC2: newpackage=/var/www/ipkg-repository/myproject/pool/ncurses_5.6-2_armel.ipk
linking.source...: ../../pool//var/www/ipkg-repository/myproject/pool/ncurses_5.6-2_armel.ipk
linking.to.......: /var/www/ipkg-repository/airpad/dists/myprojectv1.4//var/www/ipkg-repository/myproject/pool/ncurses_5.6-2_armel.ipk
ln: creating symbolic link `/var/www/ipkg-repository/myproject/dists/myprojectv1.4//var/www/ipkg-repository/myproject/pool/ncurses_5.6-2_armel.ipk': No such file or directory
...
----8<--------8<--------8<--------8<--------8<--------8<--------8<--------8<--------8<----
As you can see, the latest version is not correctly guessed. This happens each time a version is composed of 2 digits only.
I have also seen that there is an issue if the version is not matching the '\d+\.\d+\.\d+' regulator expression.
Jon Ringle already proposed to replace the incriminated ptxd_ipkg_rev_smaller by dpkg --compare-versions, but as ptxdist tries to be distribution independent, patch was not accepted.
There was no answer to the solution of the script given in the following thread: http://lists.us.dell.com/pipermail/dkms-devel/2004-July/000142.html
Of course, I can apply this script in lieu of ptxd_ipkg_rev_smaller but I prefer to stick to ptxdist releases.
Cheers,
Ben
________________________________
Ce courriel et toutes les pièces jointes sont confidentiels et peuvent être couverts par un privilège ou une protection légale. Il est établi à l’attention exclusive de ses destinataires. Toute utilisation de ce courriel non conforme à sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse préalable.
This email and any attachment are confidential and may be legally privileged or otherwise protected from disclosure. It is intended only for the stated addressee(s) and access to it by any other person(s) is unauthorized. Any use, dissemination or disclosure not in accordance with its purpose, either in whole or in part, is prohibited without our prior formal approval.
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2011-11-29 11:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 11:36 Benoît BURNICHON [this message]
2011-11-29 17:07 ` Alexander Dahl
2011-11-29 17:31 ` Benoît BURNICHON
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=3944866A166FC34A948C72DD5EDDCA2A1DC6992C@HQ0SBS01.airtag.local \
--to=benoit.burnichon@airtag.com \
--cc=ptxdist@pengutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox