[ptxdist] [ANNOUNCE] PTXdist 2014.05.0 released

[ptxdist] [ANNOUNCE] PTXdist 2014.05.0 released

[Michael Olbrich]

[-- Attachment #1.1: Type: text/plain, Size: 4356 bytes --]

Hi,

I'm happy to announce that I've just released ptxdist-2014.05.0.
Just the usual mix of new packages, new versions and bugfixes.
configure.ac got cleaned up a bit. Perl received some love, and adding new
Perl modules should be pretty simple now.
Also, rc-once changed a bit. All packages using this mechanism now have a
postinst script. This way installing such a packages after the first boot
works correctly now.
With image rules for UBI and Disk images the 'new' image rules should now
cover most basic use-cases.

Thanks to all contributors and - as always - the shortlog below.

Enjoy,
Michael Olbrich


Alexander Aring (4):
      libusb: rename libusbx to libusb
      configure.ac: add check for python 2.x version
      configure.ac: check for python2 binary as well
      configure.ac: use Python instead python everywhere

Andreas Bießmann (4):
      configure: search for GNU mktemp
      configure: search for GNU ln
      ptxdist: check vendor for ct-ng toolchain
      configure: consolidate compiler checks

Bernhard Walle (2):
      perl: Add missing dependencies
      perl: Enable thread support

Bruno Thomsen (1):
      php5: version bump 5.4.24 -> 5.4.27

Christoph Fritz (1):
      strongswan: version bump 5.0.4 -> 5.1.3

Jon Ringle (2):
      image_tgz: Make label optional
      nettle: disable parallel build

Juergen Beisert (1):
      patches/TODO: remove an orphaned file

Lucas Stach (2):
      libdrm: version bump 2.4.52 -> 2.4.53
      libdrm: version bump 2.4.53 -> 2.5.54

Markus Niebel (1):
      mbw: version bump 1.1 -> 1.4

Markus Pargmann (8):
      iproute2: version bump 3.9.0 -> 3.14.0
      iw: version bump 3.3 -> 3.14
      network: Add batctl
      crda: version bump 1.1.3 -> 3.13
      dnsmasq: version bump 2.47 -> 2.70
      iperf: version bump 2.0.4 -> 2.0.5
      wireshark: version bump 1.10.5 -> 1.10.6
      libjpeg: version bump 8a -> 9a, add binaries

Michael Olbrich (43):
      perl: version bump 5.14.2 -> 5.18.2
      ptxd_make_world_prepare: support <PKG>_CONF_TOOL := perl
      perl: add menu for modules
      net-server-perl: new package
      munin: new package
      digest-hmac-perl: new package
      net-ip-perl: new package
      socket6-perl: new package
      io-socket-inet6-perl: new package
      net-dns-perl: new package
      heirloom-mailx: new package
      ssmtp: install config file
      perl: name the wrapper 'cross-perl' to avoid name clashes with system perl
      perl: define the linker correctly again
      host-qemu: version bump 1.5.0 -> 2.0.0
      orc: version bump 0.4.18 -> 0.4.19
      e2fsprogs: add missing busybox dependency
      image_tgz: cleanup quoting and make the message nicer
      perl: cleanup thread handling
      gstreamer1: version bump 1.2.3 -> 1.2.4
      gst-plugins-base1: version bump 1.2.3 -> 1.2.4
      gst-plugins-good1: version bump 1.2.3 -> 1.2.4
      gst-plugins-bad1: version bump 1.2.3 -> 1.2.4
      gst-plugins-ugly1: version bump 1.2.3 -> 1.2.4
      qt4: version bump 4.8.2 -> 4.8.3
      evtest: version bump 1.25 -> 1.31
      pureftpd: version bump 1.0.32 -> 1.0.36
      evtest: use a stable tarball
      host-unfs3: add upstream patch for 64-bit Linux host systems
      rc-once: make it possible to run rc-once again if necessary
      machine-id: activate rc-once in postinst
      openssh: activate rc-once in postinst
      prelink: activate rc-once in postinst
      dropbear: activate rc-once in postinst
      xorg-fonts: add rc-once script to generate a fontconfig cache
      image-root-ubifs: add rules for generic UBIFS image
      image-root-ubi: add rules for generic UBI image
      image-hdimg: add generic HD image
      xorg-fonts: fix postinst
      connman: use the correct policykit package
      hal: move to staging
      policykit: move to staging
      poppler: jpeg support fails to build with jpeg-9a

Steffen Trumtrar (1):
      portmap: update portmap URL


-- 
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 |

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] [ANNOUNCE] PTXdist 2014.05.0 released

[Alexander Dahl]

Hei hei, 

Am 2014-05-12 12:56, schrieb Michael Olbrich:
> With image rules for UBI and Disk images the 'new' image rules should now
> cover most basic use-cases.

What's the difference between the old and the new image rules and why
should one use the one or the other?

Greets
Alex

-- 
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601  D1D5 8FBA 7744 CC87 10D0 ***

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] [ANNOUNCE] PTXdist 2014.05.0 released

[Michael Olbrich]

Hi,

On Wed, May 21, 2014 at 04:30:17PM +0200, Alexander Dahl wrote:
> Am 2014-05-12 12:56, schrieb Michael Olbrich:
> > With image rules for UBI and Disk images the 'new' image rules should now
> > cover most basic use-cases.
> 
> What's the difference between the old and the new image rules and why
> should one use the one or the other?

First of all, long-term I'd like to remove the old rules. So use the new
rules and yell here if you have a use-case that the new rules cannot
handle.
From a technical perspective, the new rules fix several problems the old
rules have:
- They are 'normal' packages, so they can be overwritten in the BSP.
- They handle dependencies correctly, so they are only rebuilt if needed.

I also tried to make them simpler to use (calculating sectors is a pain).

There is more stuff, and with the image templates you can handle some
really crazy scenarios. Unfortunately most of that is undocumented. So read
the source and ask questions here :-)

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

[ptxdist] new image rules (Was: PTXdist 2014.05.0 released)

[Alexander Dahl]

Hei hei, 

Am 2014-06-02 12:42, schrieb Michael Olbrich:
>> What's the difference between the old and the new image rules and why
>> should one use the one or the other?
> 
> First of all, long-term I'd like to remove the old rules. So use the new
> rules and yell here if you have a use-case that the new rules cannot
> handle.

We are using ubi and ubifs here and I tried it today after migration to
ptxdist 2014.06.0. It does not work yet, I get a kernel panic after a
factory reset with a new image. Digging deeper into this needs time I do
not have at the moment. I'll have a look later if you don't mind.

>>From a technical perspective, the new rules fix several problems the old
> rules have:
> - They are 'normal' packages, so they can be overwritten in the BSP.
> - They handle dependencies correctly, so they are only rebuilt if needed.
> 
> I also tried to make them simpler to use (calculating sectors is a pain).

I noticed some settings are not needed anymore. It's actually a little
easier, thanks for that.

Greets
Alex

-- 
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601  D1D5 8FBA 7744 CC87 10D0 ***

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] new image rules (Was: PTXdist 2014.05.0 released)

[Alexander Dahl]

Hei hei, 

>>> What's the difference between the old and the new image rules and why
>>> should one use the one or the other?
>>
>> First of all, long-term I'd like to remove the old rules. So use the new
>> rules and yell here if you have a use-case that the new rules cannot
>> handle.
> 
> We are using ubi and ubifs here and I tried it today after migration to
> ptxdist 2014.06.0. It does not work yet, I get a kernel panic after a
> factory reset with a new image. Digging deeper into this needs time I do
> not have at the moment. I'll have a look later if you don't mind.

I had time for this today and I found the reason for this: with the old
rules there was PTXCONF_IMAGE_UBI_ROOT_VOL_NAME which was set to
'rootfs0' here. With the new rules this parameter is gone and instead
there's a line 'name = "root"' hardcoded in config/images/ubifs.config
which lead to not mounting this and not finding that and so on. I could
fix this by adapting our uboot environment and startup scripts.

I suppose I could also have copied the config/images/ubifs.config to our
BSP and edit the name there?

Greets
Alex

-- 
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601  D1D5 8FBA 7744 CC87 10D0 ***

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] new image rules (Was: PTXdist 2014.05.0 released)

[Alexander Dahl]

Hei hei, 

Am 2014-11-25 14:49, schrieb Alexander Dahl:
> I suppose I could also have copied the config/images/ubifs.config to our
> BSP and edit the name there?

Nope, it was config/images/ubi.config and the change I had to made there
was:

@@ -11,7 +11,7 @@
         extraargs = "-v"
     }
     flashtype = "flash"
-    partition root {
+    partition rootfs0 {
         image = "root.ubifs"
         autoresize = true
     }

I think I'll stick with this solution for backwards compatibilty. :-)

Greets
Alex

-- 
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601  D1D5 8FBA 7744 CC87 10D0 ***

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] new image rules (Was: PTXdist 2014.05.0 released)

[Michael Olbrich]

Hi,

On Tue, Nov 25, 2014 at 02:49:06PM +0100, Alexander Dahl wrote:
> >>> What's the difference between the old and the new image rules and why
> >>> should one use the one or the other?
> >>
> >> First of all, long-term I'd like to remove the old rules. So use the new
> >> rules and yell here if you have a use-case that the new rules cannot
> >> handle.
> > 
> > We are using ubi and ubifs here and I tried it today after migration to
> > ptxdist 2014.06.0. It does not work yet, I get a kernel panic after a
> > factory reset with a new image. Digging deeper into this needs time I do
> > not have at the moment. I'll have a look later if you don't mind.
> 
> I had time for this today and I found the reason for this: with the old
> rules there was PTXCONF_IMAGE_UBI_ROOT_VOL_NAME which was set to
> 'rootfs0' here. With the new rules this parameter is gone and instead
> there's a line 'name = "root"' hardcoded in config/images/ubifs.config
> which lead to not mounting this and not finding that and so on. I could
> fix this by adapting our uboot environment and startup scripts.
> 
> I suppose I could also have copied the config/images/ubifs.config to our
> BSP and edit the name there?

Correct. That's the idea with the new image rules: Not to many options in
the menu, but you can always overwrite the config file in the BSP.

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