mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] ipkg-push failure for several packages
Date: Fri, 28 Oct 2011 11:39:24 +0200	[thread overview]
Message-ID: <20111028093924.GD12223@pengutronix.de> (raw)
In-Reply-To: <3944866A166FC34A948C72DD5EDDCA2A1DA5958A@HQ0SBS01.airtag.local>

On Wed, Oct 12, 2011 at 01:19:58PM +0000, Benoît BURNICHON wrote:
> There are undocumented restrictions on the package names and version needed in order to have ipkg-push working.
> 
> These are:
> Packages names should not contains any '_'.
> Packages versions should not contain any '-' or '_'.
> 
> This is because the ipkg-push process need to add an ipkg version number. It does this by assuming the ipk package name is as follows:
> 
> ${PackageName}_${PackageVersion}-${PackageIpkVersion}_${arch}.ipk
> 
> A simple sed is performed on this format and including a '-' in the package version leads to incorrect parsing of package name.
> 
> There are currently several packages having this issue:
> 
> $ (cd ~/Pengutronix/ptxdist && grep -ne 'VERSION.*:=[ \t]*.*-.*' rules/*)                                                           
> rules/binutils.make:23:BINUTILS_VERSION := $(shell $(CROSS_LD) -v | sed -e 's/.* \(.*\)$$/\1/g')
> rules/calibrator.make:19:CALIBRATOR_VERSION     := 20070821-1
> rules/canfestival.make:20:CANFESTIVAL_VERSION   := 3-20081204-1
> rules/chrony.make:20:CHRONY_VERSION     := 1.24-pre1
> rules/cross-insight.make:20:CROSS_INSIGHT_VERSION       := 6.8-1
> rules/dialog.make:19:DIALOG_VERSION     := 1.1-20100428
> rules/elektra.make:19:ELEKTRA_VERSION   := 0.7.0-r1618
> rules/fbtest.make:20:FBTEST_VERSION     := 20041102-1
> rules/fbutils.make:19:FBUTILS_VERSION   := 20041102-1
> rules/fbv.make:19:FBV_VERSION   := 1.0b-ptx3
> rules/gcclibs.make:22:GCCLIBS_VERSION   := $(shell $(CROSS_CC) -dumpversion)
> rules/hackbench.make:20:HACKBENCH_VERSION       := 20070821-1
> rules/host-localedef.make:20:HOST_LOCALEDEF_VERSION     := eglibc-2.11.90-ptx1
> rules/hping.make:19:HPING_VERSION       := 3-20051105
> rules/jed.make:20:JED_VERSION   := 0.99-19
> rules/libedit.make:19:LIBEDIT_VERSION   := 20100424-3.0
> rules/libezv24.make:20:LIBEZV24_VERSION := 0.1.1-ptx2
> rules/lmbench.make:19:LMBENCH_VERSION   := 3.0-a9
> rules/ltt-control.make:20:LTT_CONTROL_VERSION   := 0.87-09062010
> rules/mbw.make:20:MBW_VERSION   := 1.1-1
> rules/media-ctl.make:19:MEDIA_CTL_VERSION       := 2011.05.24-ga183835
> rules/mysql.make:20:MYSQL_VERSION       := 5.1.14-beta
> rules/ptrtd.make:27:PTRTD_VERSION_SUFFIX    := -1~14
> rules/rxtx.make:27:RXTX_VERSION := 2.1-7r2
> rules/umkimage.make:19:UMKIMAGE_VERSION := 2010.03-1
> 
> To avoid conflicts, packages names and versions should follow the debian conventions 
> Name: http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Source
> Versions: http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version
> 
> http://www.debian.org/doc/manuals/maint-guide/first.en.html#namever
> 
> Actually, there already is a solution for these issues. I have made the needed changes for the above packages in several patches.
> I do not want to send them all  to the mailing list.

I don't think changing each package is the correct solution. For package
names we already replace '_' with '-'. Something similar should be done for
the version, when creating the ipks.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2011-10-28  9:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-12 13:19 Benoît BURNICHON
2011-10-28  9:39 ` Michael Olbrich [this message]
2011-10-28 10:26   ` 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=20111028093924.GD12223@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --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