[arch-dev-public] New dbscripts are now in /arch
Pierre's dbscripts changes are now in /arch. If you want to create xz or bzip2 packages, just change PKGEXT in /etc/makepkg.conf accordingly (although bzip2 is slower and has worse compression than xz, so we probably don't want to use it). However, namcap has not been fixed to my knowledge. The workaround we agreed on was to unxz the tar file and let namcap open the uncompressed version. I think Hugo was the namcap maintainer now, but he is inactive. Who has enough python knowledge to fix this? On another note, last time I checked the dbscripts on sigurd were quite out of date, can anyone take care of that?
Am Dienstag 23 Februar 2010 schrieb Thomas Bächler:
Pierre's dbscripts changes are now in /arch. If you want to create xz or bzip2 packages, just change PKGEXT in /etc/makepkg.conf accordingly (although bzip2 is slower and has worse compression than xz, so we probably don't want to use it).
However, namcap has not been fixed to my knowledge. The workaround we agreed on was to unxz the tar file and let namcap open the uncompressed version. I think Hugo was the namcap maintainer now, but he is inactive. Who has enough python knowledge to fix this?
On another note, last time I checked the dbscripts on sigurd were quite out of date, can anyone take care of that? When should we start to migrate to xz compression?
-- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
Am Dienstag, 23. Februar 2010 19:40:52 schrieb Tobias Powalowski:
When should we start to migrate to xz compression?
I don't see any reason to not use xz for all packages. But we didn't really decide this yet. -- Pierre Schmitz, https://users.archlinux.de/~pierre
On Tue, Feb 23, 2010 at 7:38 PM, Thomas Bächler <thomas@archlinux.org> wrote:
However, namcap has not been fixed to my knowledge. The workaround we agreed on was to unxz the tar file and let namcap open the uncompressed version. I think Hugo was the namcap maintainer now, but he is inactive. Who has enough python knowledge to fix this?
Pierre opened a bug report and attached a patch against namcap a few days ago to fix the xz issue. Suppose we can apply that and roll out a new release? Ronald
Am 23.02.2010 19:44, schrieb Ronald van Haren:
On Tue, Feb 23, 2010 at 7:38 PM, Thomas Bächler <thomas@archlinux.org> wrote:
However, namcap has not been fixed to my knowledge. The workaround we agreed on was to unxz the tar file and let namcap open the uncompressed version. I think Hugo was the namcap maintainer now, but he is inactive. Who has enough python knowledge to fix this?
Pierre opened a bug report and attached a patch against namcap a few days ago to fix the xz issue. Suppose we can apply that and roll out a new release?
Ronald
I just looked at the report, Dan said he'd look at it yesterday evening, so something might happen soon.
On Tue, Feb 23, 2010 at 12:50 PM, Thomas Bächler <thomas@archlinux.org> wrote:
Am 23.02.2010 19:44, schrieb Ronald van Haren:
On Tue, Feb 23, 2010 at 7:38 PM, Thomas Bächler <thomas@archlinux.org> wrote:
However, namcap has not been fixed to my knowledge. The workaround we agreed on was to unxz the tar file and let namcap open the uncompressed version. I think Hugo was the namcap maintainer now, but he is inactive. Who has enough python knowledge to fix this?
Pierre opened a bug report and attached a patch against namcap a few days ago to fix the xz issue. Suppose we can apply that and roll out a new release?
Ronald
I just looked at the report, Dan said he'd look at it yesterday evening, so something might happen soon.
I should have time tonight, I had things to do last night. There were some comments on the bug that were relevant that I was going to make anyway, like the ${1} usage that is wrong since namcap can work (and works more efficiently!) when given multiple args at a time, such as a whole directory full of packages. -Dan
Am Dienstag, 23. Februar 2010 19:59:40 schrieb Dan McGee:
like the ${1} usage that is wrong since namcap can work (and works more efficiently!) when given multiple args at a time, such as a whole directory full of packages.
Great, didn't know that this is possible. I always used namcap in a for loop...stupid me. (yes, now I see that this is even documented in the man page) -- Pierre Schmitz, https://users.archlinux.de/~pierre
Am Dienstag, 23. Februar 2010 19:38:19 schrieb Thomas Bächler:
However, namcap has not been fixed to my knowledge. The workaround we agreed on was to unxz the tar file and let namcap open the uncompressed version. I think Hugo was the namcap maintainer now, but he is inactive. Who has enough python knowledge to fix this?
I have applied a simple but working patch to this bug report: http://bugs.archlinux.org/task/18424 I could make an unofficial package for those who want to use ti right now. It's working fine. -- Pierre Schmitz, https://users.archlinux.de/~pierre
participants (5)
-
Dan McGee
-
Pierre Schmitz
-
Ronald van Haren
-
Thomas Bächler
-
Tobias Powalowski