- Arch-dev-public - lists.archlinux.org

[arch-dev-public] [signoff] grep-2.6-1
by Allan McRae 25 Mar '10

25 Mar '10

Upstream big update. Local changelog: - Removed the multibyte locale speed-up patch (and all the patches to fix the issues it created...) as it is now included upstream. - Removed the other patches as it appears they are not being considered upstream. Upstream NEWS: * Noteworthy changes in release 2.6 (2010-03-23) [stable] ** Speed improvements grep is much faster on multibyte character sets, especially (but not limited to) UTF-8 character sets. The speed improvement is also very pronounced with case-insensitive matches. ** Bug fixes Character classes would malfunction in multi-byte locales when using grep -i. Examples which would print nothing for LC_ALL=en_US.UTF-8 include: - for ranges, echo Z | grep -i '[a-z]' - for single characters, echo Y | grep -i '[y]' - for character types, echo Y | grep -i '[[:lower:]]' grep -i -o would fail to report some matches; grep -i --color, while not missing any line containing a match, would fail to color some matches. grep would fail to report a match in a multibyte character set other than UTF-8, if another match occurred earlier in the line but started in the middle of a multibyte character. Various bugs in grep -P, caused by expressions such as [^b] or \S matching newlines, were fixed. grep -P also supports the special sequences \Z and \z, and can be combined with the command-line option -z to perform searches on NUL-separated records. grep would mistakenly exit with status 1 upon error, rather than 2, as it is documented to do. Using options like -1 -2 or -1 -v -2 results in two lines of context (the last value that appears on the command line) instead twelve (the concatenation of all the values). This is consistent with the behavior of options -A/-B/-C. Two new command-line options, --group-separator=ARGUMENT and --no-group-separator, enable further customization of the output when -A, -B or -C is being used. ** Other changes egrep accepts the -E option and fgrep accepts the -F option. If egrep and fgrep are given another of the -E/-F/-G options, they print a more meaningful error message. Signoff both, Allan

2 1

[arch-dev-public] [signoff] pcre-8.02-1
by Eric Bélanger 25 Mar '10

25 Mar '10

Hi, pcre-8.02-1 is in testing. The x86_64 pkg will be there later (wonder will build it). Please test and signoff. -minor upstream update Version 8.02 19-Mar-2010 ------------------------ 1. The Unicode data tables have been updated to Unicode 5.2.0. 2. Added the option --libs-cpp to pcre-config, but only when C++ support is configured. 3. Updated the licensing terms in the pcregexp.pas file, as agreed with the original author of that file, following a query about its status. 4. On systems that do not have stdint.h (e.g. Solaris), check for and include inttypes.h instead. This fixes a bug that was introduced by change 8.01/8. 5. A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive quantifier applied to a forward-referencing subroutine call, could compile incorrect code or give the error "internal error: previously-checked referenced subpattern not found". 6. Both MS Visual Studio and Symbian OS have problems with initializing variables to point to external functions. For these systems, therefore, pcre_malloc etc. are now initialized to local functions that call the relevant global functions. 7. There were two entries missing in the vectors called coptable and poptable in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors. I've fixed the data, and added a kludgy way of testing at compile time that the lengths are correct (equal to the number of opcodes). 8. Following on from 7, I added a similar kludge to check the length of the eint vector in pcreposix.c. 9. Error texts for pcre_compile() are held as one long string to avoid too much relocation at load time. To find a text, the string is searched, counting zeros. There was no check for running off the end of the string, which could happen if a new error number was added without updating the string. 10. \K gave a compile-time error if it appeared in a lookbehind assersion. 11. \K was not working if it appeared in an atomic group or in a group that was called as a "subroutine", or in an assertion. Perl 5.11 documents that \K is "not well defined" if used in an assertion. PCRE now accepts it if the assertion is positive, but not if it is negative. 12. Change 11 fortuitously reduced the size of the stack frame used in the "match()" function of pcre_exec.c by one pointer. Forthcoming implementation of support for (*MARK) will need an extra pointer on the stack; I have reserved it now, so that the stack frame size does not decrease. 13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other item in branch that calls a recursion is a subroutine call - as in the second branch in the above example - was incorrectly given the compile- time error "recursive call could loop indefinitely" because pcre_compile() was not correctly checking the subroutine for matching a non-empty string. 14. The checks for overrunning compiling workspace could trigger after an overrun had occurred. This is a "should never occur" error, but it can be triggered by pathological patterns such as hundreds of nested parentheses. The checks now trigger 100 bytes before the end of the workspace. 15. Fix typo in configure.ac: "srtoq" should be "strtoq".

2 1

[arch-dev-public] Removing *.db.tar.gz.old files?
by Pierre Schmitz 24 Mar '10

24 Mar '10

Hi, I am just wondering if we really need those *.old backup files that the dbscripts create. Even if something really went wrong. the old file most likely wont match the package set anyway and we could easily recreate it using repo-add. So, any objection to remove those files and their creation from dbscripts? -- Pierre Schmitz, https://users.archlinux.de/~pierre

3 5

[arch-dev-public] [signoff] dbus-core 1.2.24
by Jan de Groot 24 Mar '10

24 Mar '10

Following the crasher release of 1.2.22, this should fix FS#18796. Please test and signoff.

2 1

[arch-dev-public] gmp-5 rebuilds
by Allan McRae 24 Mar '10

24 Mar '10

Hi, I have the updated gmp and a toolchain rebuilt sitting in my staging directory to be moved into [testing] once the boost downgrade is finished. I have done all the rebuilds in [core] and nothing in the rebuild list looks critical, so updating should not be too risky. xmonad users may want to hold off until haskell is updated. Allan

3 5

[arch-dev-public] [signoff] kernel26 2.6.33.1-1
by Thomas Bächler 24 Mar '10

24 Mar '10

No idea if it is time for signoff yet, I have to check that with tpowa. However, I put 2.6.31.1 in testing with these changes: - Added a trivial patch to support my touchpad (selfish, I know, but it is already accepted upstream for 2.6.34) - Removed EXT4_USE_FOR_EXT23 due to some problems that upstream isn't quite finished discussing yet - we can keep using the ext2 and ext3 drivers for now.

11 12

[arch-dev-public] Moving to pkg.tar.xz officially?
by Pierre Schmitz 23 Mar '10

23 Mar '10

Hi all, some of us already commit xz compressed packages, others don't. We didn't really decide on this yet. So, is there a reason not to recommond every TU and Dev to change PKGEXT to .pkg.tar.xz? We might also want to write a little announcement to inform users about this change. While most of them wont be affected, some would have to adjust their custom scripts. And for those who use netinstall on a 2009.02 or older iso would have to run pacman -Syu once to get a version of libarchive which is able to deal with xz. If wanted I also could add a check to devtools which issues a warning if xz is not used. Greetings, Pierre -- Pierre Schmitz, https://users.archlinux.de/~pierre

8 19

[arch-dev-public] [draft] Switching to xz compression for new packages
by Pierre Schmitz 23 Mar '10

23 Mar '10

Hi all, as people keep asking me about this it a news item seems still to be a good idea. -- About a month ago we updated our tools to support packages that are compressed with the xz format, also known as LZMA2. Compared to gzip this will decrease package size significantly; about 30% smaller or even more depending on the data. If you want to compress your packages with the new format change the "PKGEXT" variable in the makepkg.conf of your build environment to '.pkg.tar.xz'. Our tools like dbscripts, devtools, namcap and of course pacman are able to process these packages. If you use any custom scripts which match "*.pkg.tar.gz" files, make sure to change the pattern to "*.pkg.tar.*". To allow a smooth update for older installations pacman, pacman-mirrorlist, libarchive, libfetch and xz-utils are kept in gz format. (This is achieved by adding "PKGEXT='.pkg.tat.gz'" to their PKGBUILDs) -- Pierre Schmitz, https://users.archlinux.de/~pierre

3 2

[arch-dev-public] [signoff] openssh 5.4p1-3
by Pierre Schmitz 23 Mar '10

23 Mar '10

So, there was some back and forth with openssh's init script. I rolled back to the previous one that we had used for a long time. We should put that one in core for now to make sure a running ssh session doesn't get killed on a restart: http://bugs.archlinux.org/task/18611 Once this is done I'll leave it to the maintainer to work on a method which also fixes http://bugs.archlinux.org/task/17138 Please sign off, Pierre -- Pierre Schmitz, https://users.archlinux.de/~pierre

5 9

[arch-dev-public] [signoff] gdbm 1.8.3-7
by Allan McRae 23 Mar '10

23 Mar '10

Changes: - Fix linking: run "ldd -r /usr/lib/libgdbm_compat.so.3.0.0" on old package to notice lots of undefined symbols - Put headers in more correct locations (removes need to patch e.g. python to find headers). Allan

3 4