Well, according to the changelog, https://pakfire.ipfire.org/package/pakfire/changelog version 0.9.23 should support the new package format.

Could you please check which release is installed by running: pakfire info pakfire

Thanks.

Michael

On Wed, 2013-02-27 at 16:22 +0100, Thomas Ebert wrote:

Hi Michael,

[root@ipfire ~]# pakfire --version pakfire 0.9.23

is this the information you needed or do you need some more files or outputs.

regards Thomas

Am 27.02.2013 16:14, schrieb Michael Tremer:

...

Hi,

this not really a bug, but we should possible print a more understable error message: Basically this says that the version of pakfire does not support the latest package format.

Could you please provide me the version of pakfire you have currently installed on your system? I will push an older version so you can update to that first and then move to the latest one.

@Stevee: We should update the image, because I do not want to have such old versions of some packages lying around in the stable repositories!

Michael

On Tue, 2013-02-26 at 23:53 +0100, Thomas Ebert wrote:

...

I've tried to use this image: http://people.ipfire.org/~stevee/IPFire_3.x/VM-Images/20121006/i686/ipfire-3...

But i get the following error while trying these commands: pakfire install pakfire-builder pakfire update

Loading installed packages Time: 00:00:17

Traceback (most recent call last): File "/bin/pakfire", line 61, in <module> cli.run() File "/usr/lib/python2.7/site-packages/pakfire/cli.py", line 286, in run return func() File "/usr/lib/python2.7/site-packages/pakfire/cli.py", line 306, in handle_update **args) File "/usr/lib/python2.7/site-packages/pakfire/api.py", line 53, in update allow_vendorchange=allow_vendorchange, allow_archchange=allow_archchange) File "/usr/lib/python2.7/site-packages/pakfire/base.py", line 501, in update t = solver.transaction File "/usr/lib/python2.7/site-packages/pakfire/satsolver.py", line 184, in transaction transaction.Transaction.from_solver(self.pakfire, self) File "/usr/lib/python2.7/site-packages/pakfire/transaction.py", line 235, in from_solver transaction.add(action_name, pkg) File "/usr/lib/python2.7/site-packages/pakfire/transaction.py", line 256, in add action = cls(self.pakfire, pkg) File "/usr/lib/python2.7/site-packages/pakfire/actions.py", line 42, in __init__ binary_package = self.pkg.get_from_cache() File "/usr/lib/python2.7/site-packages/pakfire/packages/solv.py", line 240, in get_from_cache return file.BinaryPackage(self.pakfire, self.repo, path) File "/usr/lib/python2.7/site-packages/pakfire/packages/file.py", line 143, in __init__ self.check() File "/usr/lib/python2.7/site-packages/pakfire/packages/file.py", line 169, in check assert self.format in PACKAGE_FORMATS_SUPPORTED, self.format AssertionError: 5

If needed, i can put logfiles here _______________________________________________ Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development

---

Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development

---

Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development

Please try to install pakfire-0.9.24-1.ip3 first and then go ahead.

# pakfire install "pakfire=0.9.24-1.ip3" # pakfire update pakfire # pakfire update

It may take a while until the package appears in the repository.

Michael

On Wed, 2013-02-27 at 16:37 +0100, Thomas Ebert wrote:

Here is the complete output:

stable: package database | 2.0 MB 00:00 ... Loading installed packages Time: 00:00:18 Name : pakfire Arch : i686 Version : 0.9.23 Release : 4.ip3 Size : 20 Repo : @system Summary : Package installer/updater. Groups : Base System/Packaging URL : None License : GPLv3+ Description : Pakfire optains package lists from the mirrors and can install : and update packages.

Name : pakfire Arch : i686 Version : 0.9.24 Release : 2.ip3 Size : 20 Repo : stable Summary : Package installer/updater. Groups : Base System/Packaging URL : http://www.ipfire.org/ License : GPLv3+ Description : Pakfire optains package lists from the mirrors and can install : and update packages.

Name : pakfire Arch : i686 Version : 0.9.24 Release : 3.ip3 Size : 20 Repo : stable Summary : Package installer/updater. Groups : Base System/Packaging URL : http://www.ipfire.org/ License : GPLv3+ Description : Pakfire optains package lists from the mirrors and can install : and update packages.

---

Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development

You'll have to disable signature checking in /etc/pakfire/general.conf.

On Wed, 2013-02-27 at 17:04 +0100, Thomas Ebert wrote:

Must i wait a little bit more? Because i got a signature error

[root@ipfire ~]# pakfire install "pakfire=0.9.24-1.ip3" stable: package database | 2.0 MB 00:00 ... Loading installed packages Time: 00:00:17

================================================================================ Package Arch Version Repository Size ================================================================================ Updating: pakfire i686 0.9.24-1.ip3 stable 20 pakfire-common i686 0.9.24-1.ip3 stable 310

Transaction Summary

Updating: 2 packages Total download size: 330 Installed size: 2k

Is this okay? [y/N] y

Downloading packages: (1/2): pakfire-0.9.24-1.ip3.i686.pfm | 40 kB 00:00 ... (2/2): pakfire-common-0.9.24-1.ip3.i686.pfm | 620 kB 00:00 ...

---

850 B/s | 330 B 00:00

Verifying signatures... Time: 00:00:00

An error has occured when running Pakfire.

Error message: SignatureError: An unhandled error occured.

Further description: pakfire-common-0.9.23-4.ip3.i686 has got no signatures pakfire-0.9.23-4.ip3.i686 has got no signatures

---

Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development

I've the following problem. Everytime i want to make a package the script is entirely downloading all needed software for pakfire-builder again.

Example: pakfire-builder shell ... Installing: 105 packages Installed size: 391M ...

Then i'm leaving the shell and enter the command again. Then he is again downloading and installing all files with dependencies.

Is it normal? That's cost much of bandwith and installation time in my virtual machine.

Regards

Am 27.02.2013 17:13, schrieb Thomas Ebert:

FYI.

All is working now.

Thanks

Am 27.02.2013 17:05, schrieb Michael Tremer:

...

You'll have to disable signature checking in /etc/pakfire/general.conf.

On Wed, 2013-02-27 at 17:04 +0100, Thomas Ebert wrote:

...

Must i wait a little bit more? Because i got a signature error

[root@ipfire ~]# pakfire install "pakfire=0.9.24-1.ip3" stable: package database | 2.0 MB 00:00 ... Loading installed packages Time: 00:00:17

================================================================================

Package Arch Version Repository Size

Updating: pakfire i686 0.9.24-1.ip3 stable 20 pakfire-common i686 0.9.24-1.ip3 stable 310

Transaction Summary

Updating: 2 packages Total download size: 330 Installed size: 2k

Is this okay? [y/N] y

Downloading packages: (1/2): pakfire-0.9.24-1.ip3.i686.pfm | 40 kB 00:00 ... (2/2): pakfire-common-0.9.24-1.ip3.i686.pfm | 620 kB 00:00 ...

---

850 B/s | 330 B 00:00

Verifying signatures... Time: 00:00:00

An error has occured when running Pakfire.

Error message: SignatureError: An unhandled error occured.

Further description: pakfire-common-0.9.23-4.ip3.i686 has got no signatures pakfire-0.9.23-4.ip3.i686 has got no signatures

---

Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development

---

Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development

---

Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development

Then is something wrong with my installation:

[root@ipfire cache]# find . -name .gz [root@ipfire cache]# find . -name *.gz ./man/cat8/network-zone.8.gz ./pakfire/sources/lldpd-0.5.4.tar.gz ./pakfire/sources/lldpd-0.7.1.tar.gz [root@ipfire cache]# find . -name *.bz2 [root@ipfire cache]#

You see the only packages which are in there is the lldpd package which first is from the packfire server and the second i manually downloaded?

What files or command output can i provide to trigger the problem?

Am 28.02.2013 23:24, schrieb Michael Tremer:

Hi,

On Thu, 2013-02-28 at 22:47 +0100, Thomas Ebert wrote:

...

I've the following problem. Everytime i want to make a package the script is entirely downloading all needed software for pakfire-builder again.

Example: pakfire-builder shell ... Installing: 105 packages Installed size: 391M ...

Then i'm leaving the shell and enter the command again. Then he is again downloading and installing all files with dependencies.

Is it normal? That's cost much of bandwith and installation time in my virtual machine.

This is not normal. Repository metadata get updated when they are older than 10 minutes and the package database will be downloaded when ever it has changed.

Packages will be stored in /var/cache/pakfire and of course they will be reused. Maybe you have a look into that directory and check your time (signatures)?

Michael

---

Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development

Sorry. I missunderstood the output. Packfire is using local packages as you described. But what about the build chroot environment. Is it normal that the build environment is cleaned everytime if you exit from it and start the command "pakfire-builder shell".

Here is the paste from my shell: http://pastebin.com/fKn3UECQ

This is my configuration /etc/pakfire/builder.conf

[logger]

# Use a different log file for the builder stuff. file = /var/log/pakfire-builder.log

[builder] # Select the distribution to build for. distro = ipfire3

# Use ccache in order to build rebuilds in less time. use_ccache = true

# Use icecream in order to speed up builds. use_icecream = false

# Create build environments in a tmpfs. # This requires a lot of RAM. # Only enable if you know what your are doing. #use_tmpfs = false

# Create loop devices in build environment. #use_loop_devices = true

Regards

Yes, the build environment is cleaned up after every build. This is intentional, so you start every build in a clean environment and don't get caught up in any errors.

However, the downloaded package files are never deleted.

Are you sure you see a re-download or just the extraction?

-Michael

On Thu, 2013-03-07 at 18:38 +0100, Thomas Ebert wrote:

Hello out there.

I know most of you are very busy at the moment, but could anybody of you provide an answer of my question? ... Is it normal that the build environment is cleaned everytime if you exit from it and start the command "pakfire-builder shell"?

Regards Thomas

Am 01.03.2013 13:43, schrieb Thomas Ebert:

...

Sorry. I missunderstood the output. Packfire is using local packages as you described. But what about the build chroot environment. Is it normal that the build environment is cleaned everytime if you exit from it and start the command "pakfire-builder shell".

Here is the paste from my shell: http://pastebin.com/fKn3UECQ

This is my configuration /etc/pakfire/builder.conf

[logger]

# Use a different log file for the builder stuff. file = /var/log/pakfire-builder.log

[builder] # Select the distribution to build for. distro = ipfire3

# Use ccache in order to build rebuilds in less time. use_ccache = true

# Use icecream in order to speed up builds. use_icecream = false

# Create build environments in a tmpfs. # This requires a lot of RAM. # Only enable if you know what your are doing. #use_tmpfs = false

# Create loop devices in build environment. #use_loop_devices = true

Regards

---

Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development

Hello Thomas,

thanks for your post on this list. Your described problem is a result of a miss-configured network.

It is only possible to create a lan0 or a upl0 network zone.

A lanX network zone is a local Ethernet, which doesn't have an a default route.

An uplX zone describes a network zone which has access to the next "bigger" network - In most cases this will be the Internet.

Best regards,

Stefan

I'm trying to configure my network with the network script, but it gives me errors.

[root@ipfire3build ~]# uname -a Linux ipfire3build 3.7.7-2.ip3.i686 #1 SMP Fri Feb 15 17:32:00 UTC 2013 i686 GNU/Linux

network zone create lan0/upl0 bridge network zone lan0/upl0 port add p0 network zone lan0/upl0 config create ipv4-static --address=192.168.11.43 --prefix=24 --gateway=192.168.11.5 network dns add 192.168.11.5 network start lan0/upl0 Job for network@lan0-upl0.service failed. See 'systemctl status network@lan0-upl0.service' and 'journalctl -xn' for details. Started service 'network@lan0/upl0.service', code=1. network status lan0/upl0

[root@ipfire3build ~]# network status lan0/upl0 Zone lan0/upl0 (bridge) Status DOWN

network@lan0-upl0.service - Network Connectivity for zone lan0/upl0 Loaded: loaded (/usr/lib/systemd/system/network@.service; static) Active: failed (Result: exit-code) since Fri, 2013-03-08 22:23:34 CET; 21s ago Process: 597 ExecStart=/usr/sbin/network zone %I up (code=exited, status=128) CGroup: name=systemd:/system/network@.service/lan0-upl0

Mar 08 22:23:34 ipfire3build network[597]: [81B blob data] Mar 08 22:23:34 ipfire3build network[678]: bridge: error_log: 'hook_exec' called from /usr/lib/network/functions.hook:127 Mar 08 22:23:34 ipfire3build network[597]: [81B blob data] Mar 08 22:23:34 ipfire3build network[680]: bridge: error_log: 'hook_zone_exec' called from /usr/lib/network/functions.zone:221 Mar 08 22:23:34 ipfire3build network[597]: [67B blob data] Mar 08 22:23:34 ipfire3build network[597]: [68B blob data] Mar 08 22:23:34 ipfire3build network[597]: [47B blob data] Mar 08 22:23:34 ipfire3build systemd[1]: network@lan0-upl0.service: main process exited, code=exited, status=128/n/a Mar 08 22:23:34 ipfire3build systemd[1]: Failed to start Network Connectivity for zone lan0/upl0. Mar 08 22:23:34 ipfire3build systemd[1]: Unit network@lan0-upl0.service entered failed state

---

Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development

A little problem here. Network settings are working and the network is autmatically configured static after a reboot. The default-route which i've set isn't working:

[root@ipfire3build ~]# network status upl0 Zone upl0 (bridge) Status UP MTU 1500

Statistics Received 4218 packets 196k (0 errors) Sent 220 packets 30k (0 errors)

Spanning Tree Protocol information Version Spanning Tree Protocol ID 0200.000c29057a38 Priority 512 This bridge is root.

Topology changing no Topology change time 0s Topology change count 0

Ports p0 FORWARDING - DSR: 00:0c:29:05:7a:38 - Cost: 100

Configurations ipv4-static UP IPv4 address 192.168.11.43/24 Gateway 192.168.11.5

[root@ipfire3build ~]# ping www.google.de connect: Network is unreachable [root@ipfire3build ~]# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.11.0 0.0.0.0 255.255.255.0 U 0 0 0 upl0 [root@ipfire3build ~]# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master upl0 state UNKNOWN qlen 1000 link/ether 00:0c:29:05:7a:38 brd ff:ff:ff:ff:ff:ff inet6 fe80::20c:29ff:fe05:7a38/64 scope link valid_lft forever preferred_lft forever 3: upl0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP link/ether 00:0c:29:05:7a:38 brd ff:ff:ff:ff:ff:ff inet 192.168.11.43/24 scope global upl0 inet6 fe80::20c:29ff:fe05:7a38/64 scope link valid_lft forever preferred_lft forever

Regards

Am 09.03.2013 11:51, schrieb Thomas Ebert:

Finally, i wanna say thank you for the great support.

As you described, your method works now.

Best Regards Thomas

Am 09.03.2013 10:04, schrieb Stefan Schantl:

...

Hello Thomas,

thanks for your post on this list. Your described problem is a result of a miss-configured network.

It is only possible to create a lan0 or a upl0 network zone.

A lanX network zone is a local Ethernet, which doesn't have an a default route.

An uplX zone describes a network zone which has access to the next "bigger" network - In most cases this will be the Internet.

Best regards,

Stefan

...

I'm trying to configure my network with the network script, but it gives me errors.

[root@ipfire3build ~]# uname -a Linux ipfire3build 3.7.7-2.ip3.i686 #1 SMP Fri Feb 15 17:32:00 UTC 2013 i686 GNU/Linux

network zone create lan0/upl0 bridge network zone lan0/upl0 port add p0 network zone lan0/upl0 config create ipv4-static --address=192.168.11.43 --prefix=24 --gateway=192.168.11.5 network dns add 192.168.11.5 network start lan0/upl0 Job for network@lan0-upl0.service failed. See 'systemctl status network@lan0-upl0.service' and 'journalctl -xn' for details. Started service 'network@lan0/upl0.service', code=1. network status lan0/upl0

[root@ipfire3build ~]# network status lan0/upl0 Zone lan0/upl0 (bridge) Status DOWN

network@lan0-upl0.service - Network Connectivity for zone lan0/upl0 Loaded: loaded (/usr/lib/systemd/system/network@.service; static) Active: failed (Result: exit-code) since Fri, 2013-03-08 22:23:34 CET; 21s ago Process: 597 ExecStart=/usr/sbin/network zone %I up (code=exited, status=128) CGroup: name=systemd:/system/network@.service/lan0-upl0

Mar 08 22:23:34 ipfire3build network[597]: [81B blob data] Mar 08 22:23:34 ipfire3build network[678]: bridge: error_log: 'hook_exec' called from /usr/lib/network/functions.hook:127 Mar 08 22:23:34 ipfire3build network[597]: [81B blob data] Mar 08 22:23:34 ipfire3build network[680]: bridge: error_log: 'hook_zone_exec' called from /usr/lib/network/functions.zone:221 Mar 08 22:23:34 ipfire3build network[597]: [67B blob data] Mar 08 22:23:34 ipfire3build network[597]: [68B blob data] Mar 08 22:23:34 ipfire3build network[597]: [47B blob data] Mar 08 22:23:34 ipfire3build systemd[1]: network@lan0-upl0.service: main process exited, code=exited, status=128/n/a Mar 08 22:23:34 ipfire3build systemd[1]: Failed to start Network Connectivity for zone lan0/upl0. Mar 08 22:23:34 ipfire3build systemd[1]: Unit network@lan0-upl0.service entered failed state

---

Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development

---

Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development

---

Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development

Hi Michael,

i've tested the fix. It works. After that I've to delete the old configuration and create a new one.

Thank you. Thomas

Am 10.03.2013 14:09, schrieb Michael Tremer:

Hi Thomas,

I just fixed the default route problem in this commit: http://git.ipfire.org/?p=network.git;a=commitdiff;h=2741ce5581c3dc5d34942d0b...

Just check out the git repository on your box and run make install to get the fix. Maybe you will have to reconfigure some ports.

-Michael

On Sat, 2013-03-09 at 12:04 +0100, Thomas Ebert wrote:

...

A little problem here. Network settings are working and the network is autmatically configured static after a reboot. The default-route which i've set isn't working:

[root@ipfire3build ~]# network status upl0 Zone upl0 (bridge) Status UP MTU 1500

Statistics
  Received        4218 packets   196k (0 errors)
  Sent             220 packets    30k (0 errors)

Spanning Tree Protocol information
  Version                    Spanning Tree Protocol
  ID                         0200.000c29057a38
  Priority                   512
  This bridge is root.

  Topology changing          no
  Topology change time       0s
  Topology change count      0

Ports
  p0            FORWARDING  - DSR: 00:0c:29:05:7a:38 - Cost: 100

Configurations
  ipv4-static       UP
    IPv4 address             192.168.11.43/24
    Gateway                  192.168.11.5

[root@ipfire3build ~]# ping www.google.de connect: Network is unreachable [root@ipfire3build ~]# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.11.0 0.0.0.0 255.255.255.0 U 0 0 0 upl0 [root@ipfire3build ~]# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master upl0 state UNKNOWN qlen 1000 link/ether 00:0c:29:05:7a:38 brd ff:ff:ff:ff:ff:ff inet6 fe80::20c:29ff:fe05:7a38/64 scope link valid_lft forever preferred_lft forever 3: upl0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP link/ether 00:0c:29:05:7a:38 brd ff:ff:ff:ff:ff:ff inet 192.168.11.43/24 scope global upl0 inet6 fe80::20c:29ff:fe05:7a38/64 scope link valid_lft forever preferred_lft forever

Regards

Am 09.03.2013 11:51, schrieb Thomas Ebert:

...

Finally, i wanna say thank you for the great support.

As you described, your method works now.

Best Regards Thomas

Am 09.03.2013 10:04, schrieb Stefan Schantl:

...

Hello Thomas,

thanks for your post on this list. Your described problem is a result of a miss-configured network.

It is only possible to create a lan0 or a upl0 network zone.

A lanX network zone is a local Ethernet, which doesn't have an a default route.

An uplX zone describes a network zone which has access to the next "bigger" network - In most cases this will be the Internet.

Best regards,

Stefan

...

I'm trying to configure my network with the network script, but it gives me errors.

[root@ipfire3build ~]# uname -a Linux ipfire3build 3.7.7-2.ip3.i686 #1 SMP Fri Feb 15 17:32:00 UTC 2013 i686 GNU/Linux

network zone create lan0/upl0 bridge network zone lan0/upl0 port add p0 network zone lan0/upl0 config create ipv4-static --address=192.168.11.43 --prefix=24 --gateway=192.168.11.5 network dns add 192.168.11.5 network start lan0/upl0 Job for network@lan0-upl0.service failed. See 'systemctl status network@lan0-upl0.service' and 'journalctl -xn' for details. Started service 'network@lan0/upl0.service', code=1. network status lan0/upl0

[root@ipfire3build ~]# network status lan0/upl0 Zone lan0/upl0 (bridge) Status DOWN

network@lan0-upl0.service - Network Connectivity for zone lan0/upl0 Loaded: loaded (/usr/lib/systemd/system/network@.service; static) Active: failed (Result: exit-code) since Fri, 2013-03-08 22:23:34 CET; 21s ago Process: 597 ExecStart=/usr/sbin/network zone %I up (code=exited, status=128) CGroup: name=systemd:/system/network@.service/lan0-upl0

Mar 08 22:23:34 ipfire3build network[597]: [81B blob data] Mar 08 22:23:34 ipfire3build network[678]: bridge: error_log: 'hook_exec' called from /usr/lib/network/functions.hook:127 Mar 08 22:23:34 ipfire3build network[597]: [81B blob data] Mar 08 22:23:34 ipfire3build network[680]: bridge: error_log: 'hook_zone_exec' called from /usr/lib/network/functions.zone:221 Mar 08 22:23:34 ipfire3build network[597]: [67B blob data] Mar 08 22:23:34 ipfire3build network[597]: [68B blob data] Mar 08 22:23:34 ipfire3build network[597]: [47B blob data] Mar 08 22:23:34 ipfire3build systemd[1]: network@lan0-upl0.service: main process exited, code=exited, status=128/n/a Mar 08 22:23:34 ipfire3build systemd[1]: Failed to start Network Connectivity for zone lan0/upl0. Mar 08 22:23:34 ipfire3build systemd[1]: Unit network@lan0-upl0.service entered failed state

---

Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development

---

Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development

---

Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development

---

Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development

---

Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development