[gentoo-dev] tcl/tk-8.6 incompatibilities
Hi, some packages do not build against version 8.6 and show errors like this: error: 'Tcl_Interp' has no member named 'result' and error: 'Tcl_Interp' has no member named 'errorline' This is due to a removal of an old and deprecated (at least since 2004) feature. Here some simple fixes: Version A (will stop working with tcl/tk-9.0): append -DUSE_INTERP_RESULT and/or -DUSE_INTERP_ERRORLINE to the *FLAGS. Version B (long lasting and better): patch code (and send upstream) to use Tcl_GetResult(), Tcl_GetStringResult(), Tcl_SetResult(), Tcl_SetStringResult(), Tcl_GetErrorLine() Examples: @@ -1980,10 +1980,10 @@ void tcl_run( trace = (char *)Tcl_GetVar(interp, errorInfo, 0); if (trace == NULL) - trace = interp-result; + trace = Tcl_GetStringResult(interp); fprintf(stderr, %s: TCL error @ line %d: %s\n, -script, interp-errorLine, trace); +script, Tcl_GetErrorLine(interp), trace); } Tcl_DeleteInterp(interp); Some more little facts: * Please link against libtcl.so and libtk.so instead of libtcl8.6.so and libtk8.6. * Version 8.6 supports pkg-config * Version 8.6 is subslotted. * Reference bug https://bugs.gentoo.org/show_bug.cgi?id=451368 Thanks justin signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Proposal to end-of-life tree-clean old profiles/updates/ files
On Wed, 2013-01-02 at 17:05 -0800, Zac Medico wrote: This command seems to do the trick: $ ls -1 /usr/portage/profiles/updates/ | grep -Ev '(08|09|10|11|12|13)$' 1Q-2004 1Q-2005 1Q-2006 1Q-2007 2Q-2004 2Q-2005 2Q-2006 2Q-2007 3Q-2004 3Q-2005 3Q-2006 3Q-2007 4Q-2004 4Q-2005 4Q-2006 4Q-2007 OK, these old updates have now been cleaned from the tree. They have been tar'd and can be downloaded at: http://dev.gentoo.org/~dolsen/cleaned-updates-20130111.tbz2 If we are going to archive them to be available. It can be moved to there, otherwise I can remove it once we know it is not needed. Now, where to document this procedure for future reference? -- Brian Dolbec dol...@gentoo.org signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] Proposal to end-of-life tree-clean old profiles/updates/ files
On 01/11/2013 01:10 AM, Brian Dolbec wrote: On Wed, 2013-01-02 at 17:05 -0800, Zac Medico wrote: This command seems to do the trick: $ ls -1 /usr/portage/profiles/updates/ | grep -Ev '(08|09|10|11|12|13)$' 1Q-2004 1Q-2005 1Q-2006 1Q-2007 2Q-2004 2Q-2005 2Q-2006 2Q-2007 3Q-2004 3Q-2005 3Q-2006 3Q-2007 4Q-2004 4Q-2005 4Q-2006 4Q-2007 OK, these old updates have now been cleaned from the tree. They have been tar'd and can be downloaded at: http://dev.gentoo.org/~dolsen/cleaned-updates-20130111.tbz2 If we are going to archive them to be available. It can be moved to there, otherwise I can remove it once we know it is not needed. Now, where to document this procedure for future reference? Maybe here: http://www.gentoo.org/proj/en/qa/treecleaners/policy.xml -- Thanks, Zac
Re: [gentoo-dev] tcl/tk-8.6 incompatibilities
One additional note: application-specific initialization failed: package not known invalid command name auto_mkindex_parser::command This comes from a broken dev-lang/tcl-8.6.0. Revision 1 is fixed. Justin signature.asc Description: OpenPGP digital signature
[gentoo-dev] Re: call for testers: udev predictable network interface names
Christopher Head wrote: William Hubbs willi...@gentoo.org wrote: There is a way for users to opt out if we default this to on, but I think the new naming scheme has advantages over the traditional eth* wlan* etc names. I think it should be taken with a grain of salt. The page mentions how it lets you replace a failed NIC without losing its name. But given a simple computer with just one NIC, if the NIC fails and is replaced (perhaps by a different type of NIC in a different slot, or perhaps an onboard NIC disabled in the BIOS and replaced by an add-in), the name could change, while the kernel’s automatically assigned name will not: eth0 (this also applies to a computer with one Ethernet NIC and one wifi NIC: eth0 and wlan0). That fact was never mentioned on the wiki page, even though it applies to a heck of a lot of systems. Perhaps something to include when the Gentoo docs are put together, as part of the balance of reasons to choose one way or the other? That's a very good point. For the vast majority of users all these desktop changes are supposed to help, it's not at all relevant. Obviously it's good to have the functionality should you need it, but again it appears that simple cases are being made complex, just to allow for someone else's complex cases. Which is faulty logic. While many packages have default configurations, changing the default setup for base system packages in the absence of any configuration is not generally a good idea, unless you know for a fact it's not going to mess anything up (which is a big ask given that you're distributing source.) Especially given the arguments presented as a motivation, that all this has serious security implications, for example in firewall rules which are coded for certain naming schemes, and which are hence very sensitive to unpredictable changing names. If you're certain that every user with a current simple setup, who uses the kernel default names, and has such a firewall setup isn't going to suddenly find their interface name changed when they reboot, fair play to you. If not, allow the admin to opt-in, rather than force them to opt-out when something breaks. That's the usual manner to introduce something new or changed, and for good reason. After all, those who are aware of it and interested, already know to configure it, or are looking for help to do so. Most other users don't care, and don't want the maintenance headache. -- #friendly-coders -- We're friendly, but we're not /that/ friendly ;-)
[gentoo-dev] app-emulation/qemu-user mask
Just wanted to give everyone a heads up. app-emulation/qemu provides all the functionality of app-emulation/qemu-user without all the outstanding security bugs and issues the package has. For users using a cross chroot, I encourage you to look at QEMU_USER_TARGETS. I presently use an arm chroot with app-emulation/qemu. Should there truly be a missing feature, open a bug and I'll fix it. The only item I'm aware of that app-emulation/qemu does not have is the binfmt initscript. But I plan on adding that to the unstable version shortly. If there are no objections for 30 days, I'll send a treecleaner notice in 30 days and remove it 30 days after that (60 days from now). -- Doug Goldstein
[gentoo-dev] Handy pybugz wrappers
Anyone have handy pybugz wrappers for bumping ebuilds and fixing bugs? I'm so used to the environment at work where a post-commit hook parses specifically formatted commit messages to take several actions on commits. I figure before I hack on any I'd ask if someone has some that could be shared with the community. Really just looking to combine steps like echangelog and repoman commit with pybugz. -- Doug Goldstein
