[gentoo-dev] Last rites: x11-themes/pekwm-themes-hewphoria
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 # Markos Chandras hwoar...@gentoo.org (19 May 2013) # Unclear license. Bug #452418 # Removal in 30 days x11-themes/pekwm-themes-hewphoria - -- Regards, Markos Chandras - Gentoo Linux Developer http://dev.gentoo.org/~hwoarang -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) iQJ7BAEBCgBmBQJRmJwkXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzNTVDNDczOUYzRjJEMTRGNDRGMzU2RkMw OUJGNEY1NEMyQkE3RjNDAAoJEAm/T1TCun882X0P9RfY8wFcjWEaMRapNG/MoUGG /b9a8CXdHCYpIl+qXZz5Uwq15st1y4Z43+OaH0urt7L6V1Tccm3mlzfxGOuzlxtE WygBC8oBPRBNfSJz+Ky0rnRAWLojUfNaWU1Tb9UTIqU6gfBdWy4zpt5Egd7m15h0 Fu12w3VSVthzlxk3fT+eOzA+ZFPGlDYPR3XIaGM1dR+Ka/u5DMPcu8uJW+vIQxiN SMErxcBkXTngLwG1g6w66pfyJP9bpZA1L2ctziV4d1c4JrHF3y3xgMfHXRYxAbvn lvqkm7sJ7p2Zm2YnmJi0bTxtmDNP8c26HYSwZEJ5TXDaDoI02Ey9NdIJ/SM+aR05 sYEsVoVvJvGETI+xqo6rPMW+H1GiPLNAb2FIxFRdTup2W2P2xLFO0W6oDw/UOES+ 7fpfJSSeOZL92Yp6eRGHyIaTy9Ehc/6uz8KqKmR39NUDui0JJdC0DhFcyWO21AZ4 dXdfyiMY0QMTLvHrnPaOSXddBS+w5JtWCoGlVyI3qUjMJPnumzUadRLOBhqFjKYk 4pYZy9qujHCuqsUp/hL11KyfsiL+9bZtBae/gIPYj+wu0j+SRri8wMc9NesmCGpj /wGUu/rQCt1YKKbRjltdjv+7rY7+OhqbJDYokFf673gUeH9aHDoYoA6blCDu+lYZ MIj+CCe0sXi1T9L3VRg= =yLcp -END PGP SIGNATURE-
Re: [gentoo-dev] mono-env.eclass: new eclass to be used by most of dotnet packages
El dom, 14-04-2013 a las 11:40 +0200, Pacho Ramos escribió:
Due reasons explained here:
https://bugs.gentoo.org/show_bug.cgi?id=462052#c1
We would like to start a process of simplifying dotnet maintained
eclasses a lot because they are currently really hard to maintain. As a
start point, we will need a simple eclass simply to export some
variables needed to build most of dotnet packages. That variables are
currently being exported by mono.eclass, the idea would be to split the
environment exporting part out of it (and deprecate current
mono.eclass in the future)
Updated eclass taking care of previous suggestions
# Copyright 1999-2013 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $
# @ECLASS: mono-env.eclass
# @MAINTAINER:
# dot...@gentoo.org
# @BLURB: Set environment variables commonly used by dotnet packages.
# @DESCRIPTION:
# Set environment variables commonly used by dotnet packages.
inherit multilib
EXPORT_FUNCTIONS pkg_setup
if [[ ! ${_MONO_ENV} ]]; then
mono-env_pkg_setup() {
# =mono-0.92 versions using mcs -pkg:foo-sharp require shared memory,
so we set the
# shared dir to ${T} so that ${T}/.wapi can be used during the install
process.
export MONO_SHARED_DIR=${T}
# export more variables as needed by other dotnet packages
export MONO_REGISTRY_PATH=${T}/registry
export XDG_DATA_HOME=${T}/data
# Building mono, nant and many other dotnet packages is known to fail
if LC_ALL
# variable is not set to C. To prevent this all mono related packages
will be
# build with LC_ALL=C (see bugs #146424, #149817)
export LC_ALL=C
# Monodevelop-using applications need this to be set or they will try
to create config
# files in the user's ~ dir.
export XDG_CONFIG_HOME=${T}
# Fix bug 83020:
# Access Violations Arise When Emerging Mono-Related Packages with
MONO_AOT_CACHE
unset MONO_AOT_CACHE
# mono libs can live on /usr/lib as they are not arch specific
QA_MULTILIB_PATHS=usr/lib/
}
_MONO_ENV=1
fi
Re: [gentoo-dev] Re: Making systemd more accessible to normal users
On 05/18/2013 03:23 PM, Carlos Silva wrote: Is the real problem just the god damn unit/init files?! Damn, who cares about 2KiB files in the age of GiBs?! You can install 1000 of them that it will only take 2MiB of storage, so please, quit complaining about this. Practically speaking, I think the problem is likely more about the inode usage than the physical size of the files. With today's huge disks, the problem does seem to be becoming the cost of metadata over the cost of the data itself. (Why else would we need sectors larger than 512 bytes?) One thing dev's should take care is (not that affects me, 'cause I really don't care) is mentions to rc-update on einfo's. Again, I really don't care, but, for the sake of making them (openrc, systemd, etc) equal, that really shouldn't be mentioned. [snip] signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Re: Making systemd more accessible to normal users
Am Sonntag, 19. Mai 2013, 14:59:21 schrieb Michael Mol: On 05/18/2013 03:23 PM, Carlos Silva wrote: Is the real problem just the god damn unit/init files?! Damn, who cares about 2KiB files in the age of GiBs?! You can install 1000 of them that it will only take 2MiB of storage, so please, quit complaining about this. Practically speaking, I think the problem is likely more about the inode usage than the physical size of the files. With today's huge disks, the problem does seem to be becoming the cost of metadata over the cost of the data itself. (Why else would we need sectors larger than 512 bytes?) Then use a decent file system. http://kernelnewbies.org/Linux_3.8#head-372b38979138cf2006bd0114ae97f889f67ef46a EOT -- Andreas K. Huettel Gentoo Linux developer dilfri...@gentoo.org http://www.akhuettel.de/ signature.asc Description: This is a digitally signed message part.
[gentoo-dev] robo-stable bugs
Private messages and public comments through bugzilla are so far ignored, it seems, so let's try a venue where it's sure to cause a flamewar instead. My apologies for the inconvenience. On Sat, 18 May 2013 21:08:53 + bugzilla-dae...@gentoo.org wrote: DO NOT REPLY TO THIS EMAIL. Also, do not reply via email to the person whose email is mentioned below. To comment on this bug, please visit: https://bugs.gentoo.org/show_bug.cgi?id=470392 Bug ID: 470392 Summary: Please stabilize =dev-libs/libconfig-1.4.9-r1 We agreed a little while ago that bug Summaries should start with an atom, if possible, and explain the action later. Also, robotically filing thousands of bugs and making them say please every time isn't going to endear anyone to your cause. So do something like this: cat/pkg-version stabilisation request URL: http://packages.gentoo.org/package/dev-libs/libconfig? arches=linux Is this URL useful to include, or did you just want to abuse every last feature found in pybugz? Wouldn't maintainers already know where to find this kind of information? Who do you think is your audience? OS: Linux Status: CONFIRMED Severity: enhancement Is a stabilisation an enhancement per se? If all stabilisations are enhancements, then why isn't Severity set to Normal instead? (What is an enhanced severity to begin with, Mozilla?) Priority: Normal This is where you probably wanted to set something similar to Enhancement above, but again you probably shouldn't. Normal stabilisation bugs are normal, not less than normal. Is it OK to stabilize =dev-libs/libconfig-1.4.9-r1 ? If so, please CC all arches which have stable keywords for older versions of this package and add STABLEREQ keyword to the bug. My e-mail editor is messing up the line endings here, but your messages already include double newlines - on bugzilla web pages as well as in the e-mail it sends, so this is your broken pybugz script again, I reckon? Also, your script does not set the STABLEREQ keyword. People are having to hunt down your robo-stabilisation requests and add it themselves. You should just do it yourself or turn your script off. jer
Re: [gentoo-dev] Re: Making systemd more accessible to normal users
Andreas K. Huettel dilfri...@gentoo.org wrote: Am Sonntag, 19. Mai 2013, 14:59:21 schrieb Michael Mol: On 05/18/2013 03:23 PM, Carlos Silva wrote: Is the real problem just the god damn unit/init files?! Damn, who cares about 2KiB files in the age of GiBs?! You can install 1000 of them that it will only take 2MiB of storage, so please, quit complaining about this. Practically speaking, I think the problem is likely more about the inode usage than the physical size of the files. With today's huge disks, the problem does seem to be becoming the cost of metadata over the cost of the data itself. (Why else would we need sectors larger than 512 bytes?) Then use a decent file system. http://kernelnewbies.org/Linux_3.8#head-372b38979138cf2006bd0114ae97f889f67ef46a EOT -- Andreas K. Huettel Gentoo Linux developer dilfri...@gentoo.org http://www.akhuettel.de/ Andreas. I don't see how this will avoid the issue of a limited amount of inodes. That is what I usually run out of before the disk is full when storing lots of smaller files. -- Joost -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Re: [gentoo-dev] Re: Making systemd more accessible to normal users
J. Roeleveld wrote: I don't see how this will avoid the issue of a limited amount of inodes. That is what I usually run out of before the disk is full when storing lots of smaller files. I guess the number of unit files is on the order of hundreds, as long as you haven't configured an INSTALL_MASK to avoid installing them. (Why haven't you?) Are you saying that a few hundred inodes more will break many systems? It doesn't seem very likely to me. //Peter
[gentoo-dev] Re: robo-stable bugs
On 19/05/2013 23:40, Jeroen Roovers wrote: OS: Linux Status: CONFIRMED Severity: enhancement Is a stabilisation an enhancement per se? Usually I think so yes. If it is an urgent stabilisation there is priority field. If all stabilisations are enhancements, then why isn't Severity set to Normal instead? (What is an enhanced severity to begin with, Mozilla?) According to the Bugzilla docs: Severity - How severe the bug is, or whether it's an enhancement. so there is no such thing as an enhanced severity. Priority: Normal This is where you probably wanted to set something similar to Enhancement above, but again you probably shouldn't. Normal stabilisation bugs are normal, not less than normal. Why should enhancement go in the priority field, when it does not presently exist there but does exist in the severity field? Also, your script does not set the STABLEREQ keyword. People are having to hunt down your robo-stabilisation requests and add it themselves. You should just do it yourself or turn your script off. According to the bug wrangler docs STABLEREQ should be handled by the maintainer. Why should there be a difference whether a user or a dev is requesting stabilisation?
Re: [gentoo-dev] Re: CPU use flag detection
On Sat, 18 May 2013 22:31:11 -0400 Walter Dnes waltd...@waltdnes.org wrote: [...] ...shouldn't mmxext be moved out of use.local.desc into use.desc? all the cpu flags should be global IMHO, regardless of how many packages use them: we already mask/unmask them globally on arches where they are irrelevant. Alexis.
Re: [gentoo-dev] robo-stable bugs
On Sun, May 19, 2013 at 3:40 PM, Jeroen Roovers j...@gentoo.org wrote: On Sat, 18 May 2013 21:08:53 + bugzilla-dae...@gentoo.org wrote: DO NOT REPLY TO THIS EMAIL. Also, do not reply via email to the person whose email is mentioned below. To comment on this bug, please visit: https://bugs.gentoo.org/show_bug.cgi?id=470392 Bug ID: 470392 Summary: Please stabilize =dev-libs/libconfig-1.4.9-r1 We agreed a little while ago that bug Summaries should start with an atom, if possible, and explain the action later. Also, robotically filing thousands of bugs and making them say please every time isn't going to endear anyone to your cause. So do something like this: cat/pkg-version stabilisation request When/where did that happen? Is a stabilisation an enhancement per se? If all stabilisations are enhancements, then why isn't Severity set to Normal instead? (What is an enhanced severity to begin with, Mozilla?) Huh, good point. It makes sense to me that this bug is strictly an enhancement (e.g. more like a feature than like a bug), but that's more a bug type than a severity. Priority: Normal This is where you probably wanted to set something similar to Enhancement above, but again you probably shouldn't. Normal stabilisation bugs are normal, not less than normal. Also, your script does not set the STABLEREQ keyword. People are having to hunt down your robo-stabilisation requests and add it themselves. You should just do it yourself or turn your script off. According to the bug wrangler docs STABLEREQ should be handled by the maintainer. Why should there be a difference whether a user or a dev is requesting stabilisation? Sure, but in the case of mass-filing stabilization bugs, optimizing for maintainers makes more sense to me. Cheers, Dirkjan
Re: [gentoo-dev] robo-stable bugs
On 05/19/2013 02:40 PM, Jeroen Roovers wrote: Private messages and public comments through bugzilla are so far ignored, it seems, so let's try a venue where it's sure to cause a flamewar instead. My apologies for the inconvenience. fwiw the current situation works for me quite well. -- Regards, Markos Chandras - Gentoo Linux Developer http://dev.gentoo.org/~hwoarang
Re: [gentoo-dev] Re: CPU use flag detection
On 05/19/13 17:47, Alexis Ballier wrote: On Sat, 18 May 2013 22:31:11 -0400 Walter Dnes waltd...@waltdnes.org wrote: [...] ...shouldn't mmxext be moved out of use.local.desc into use.desc? all the cpu flags should be global IMHO, regardless of how many packages use them: we already mask/unmask them globally on arches where they are irrelevant. Alexis. +1 also +1 they should be easily recognizable as cpu features USE flags, as already mentioned recently by someone (sorry could not search)
Re: [gentoo-dev] Re: CPU use flag detection
On Sun, May 19, 2013 at 8:47 AM, Alexis Ballier aball...@gentoo.org wrote: On Sat, 18 May 2013 22:31:11 -0400 Walter Dnes waltd...@waltdnes.org wrote: [...] ...shouldn't mmxext be moved out of use.local.desc into use.desc? all the cpu flags should be global IMHO, regardless of how many packages use them: we already mask/unmask them globally on arches where they are irrelevant. Alexis. Yes, they should. And while we're at it, we should stop naming them differently. (sse4_1 vs sse41) Also, since SSE4 isn't a thing (there's SSE4.1, SSE4.2, and SSE4a) we shouldn't have /any/ USE=sse4 in the tree. And we should never set up the masks like this: https://bugs.gentoo.org/show_bug.cgi?id=470220
Re: [gentoo-dev] Re: CPU use flag detection
Am 19.05.2013 18:03, schrieb viv...@gmail.com: On 05/19/13 17:47, Alexis Ballier wrote: On Sat, 18 May 2013 22:31:11 -0400 Walter Dnes waltd...@waltdnes.org wrote: [...] ...shouldn't mmxext be moved out of use.local.desc into use.desc? all the cpu flags should be global IMHO, regardless of how many packages use them: we already mask/unmask them globally on arches where they are irrelevant. Alexis. +1 also +1 they should be easily recognizable as cpu features USE flags, as already mentioned recently by someone (sorry could not search) So this sounds like one of the places, where a USE_EXPAND could really be correct and worthwhile :). - René
Re: [gentoo-dev] Re: Making systemd more accessible to normal users
On Sun, May 19, 2013 at 9:34 AM, Peter Stuge pe...@stuge.se wrote: J. Roeleveld wrote: I don't see how this will avoid the issue of a limited amount of inodes. That is what I usually run out of before the disk is full when storing lots of smaller files. I guess the number of unit files is on the order of hundreds, Full GNOME as long as you haven't configured an INSTALL_MASK to avoid installing them. (Why haven't you?) Are you saying that a few hundred inodes more will break many systems? It doesn't seem very likely to me. //Peter -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-dev] Re: Making systemd more accessible to normal users
On Sun, May 19, 2013 at 9:34 AM, Peter Stuge pe...@stuge.se wrote: J. Roeleveld wrote: I don't see how this will avoid the issue of a limited amount of inodes. That is what I usually run out of before the disk is full when storing lots of smaller files. I guess the number of unit files is on the order of hundreds (Sorry, sent email before it was ready). Laptop running full GNOME: # find /usr/lib/systemd/system -type f | wc 154 1547012 Server running Apache+MySQL+Mailman+Squid+Other services: # find /usr/lib/systemd/system -type f | wc 121 1215560 And as you said, you can always use INSTALL_MASK. If 154 files are going to deplete your inodes, I think your problem lies somewhere else. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-dev] robo-stable bugs
TL;DR: I like the stabilization bugs as they are. Summary: Please stabilize =dev-libs/libconfig-1.4.9-r1 We agreed a little while ago that bug Summaries should start with an atom, if possible, and explain the action later. Also, robotically filing thousands of bugs and making them say please every time isn't going to endear anyone to your cause. So do something like this: cat/pkg-version stabilisation request No opinion about the order of things, that's imho nitpicking. The Please does not hurt anyone. URL: http://packages.gentoo.org/package/dev-libs/libconfig? arches=linux Is this URL useful to include, or did you just want to abuse every last feature found in pybugz? Wouldn't maintainers already know where to find this kind of information? Who do you think is your audience? It's convenient, although redundant. Why is it a problem to have the URL there? Maybe someone finds it useful. Severity: enhancement Is a stabilisation an enhancement per se? If all stabilisations are enhancements, then why isn't Severity set to Normal instead? (What is an enhanced severity to begin with, Mozilla?) That's how it has been done for a while now with stablerequests. You're clearly an oldtimer. :) Also, your script does not set the STABLEREQ keyword. People are having to hunt down your robo-stabilisation requests and add it themselves. You should just do it yourself or turn your script off. Well, that was as far as I can remember a deliberate decision- maintainer action should be set STABLEREQ keyword and CC arches. Probably the keyword could already be preset, though. -- Andreas K. Huettel Gentoo Linux developer dilfri...@gentoo.org http://www.akhuettel.de/ signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] robo-stable bugs
On 5/19/13 6:40 AM, Jeroen Roovers wrote: Private messages and public comments through bugzilla are so far ignored, it seems, so let's try a venue where it's sure to cause a flamewar instead. My apologies for the inconvenience. Hey Jeroen, apologies if I have ignored any of your feedback. I'm indeed behind on bugmail (5000 unread emails, how about that?). I do read mailing list traffic and direct e-mail though. We agreed a little while ago that bug Summaries should start with an atom, if possible, and explain the action later. Could you refer me to the part where we agreed and why? I'm actually happy to make changes that are useful for people, but without a good rationale and an _actual_ consensus someone else will inevitably come and says he likes the old way better. URL: http://packages.gentoo.org/package/dev-libs/libconfig? arches=linux Is this URL useful to include, or did you just want to abuse every last feature found in pybugz? Wouldn't maintainers already know where to find this kind of information? Who do you think is your audience? My audience is a developer who doesn't have lots of time. It's not so much about not knowing at all where to look for it, but being able to do so really quickly. For me (maybe not so for other people - fine), it's much quicker to click a link than to copy-paste package name to either a URL or eshowkw or anything else, especially with more tricky package names like: app-emulation/open-vm-tools-2012.03.13.651368 (long version number) dev-perl/LWP-Protocol-https-6.30.0 (case variations) dev-php/PEAR-Crypt_RC4-1.0.3 (underscore vs dash variations) Please let me know if there is any _downside_ of having the URL, especially now that you know the upside. :) OS: Linux Status: CONFIRMED Severity: enhancement Is a stabilisation an enhancement per se? If all stabilisations are enhancements, then why isn't Severity set to Normal instead? (What is an enhanced severity to begin with, Mozilla?) What is your constructive alternative to this? Priority: Normal This is where you probably wanted to set something similar to Enhancement above, but again you probably shouldn't. Normal stabilisation bugs are normal, not less than normal. AFAIK this is the default setting. What is your constructive alternative? I'm actually serious - if you have specific changes in mind, I'd be happy to make them if I see the rationale. My e-mail editor is messing up the line endings here, but your messages already include double newlines - on bugzilla web pages as well as in the e-mail it sends, so this is your broken pybugz script again, I reckon? Fixed: http://git.overlays.gentoo.org/gitweb/?p=proj/arch-tools.git;a=commitdiff;h=3d2d92a6537bec6be9c39ac113eb88f85faca315 Thank you for reporting this. Also, your script does not set the STABLEREQ keyword. People are having to hunt down your robo-stabilisation requests and add it themselves. You should just do it yourself or turn your script off. This is more tricky. If there is a consensus about STABLEREQ keyword, I'd be happy to add it. I vaguely remember some past controversies about it (or maybe it was actually same as what you're suggesting here). Remember this is supposed to _help_ Gentoo. You can opt out of the bugs (there is a package name and maintainer name regex in the script). You don't need to hunt them down - if you do nothing another script will just CC arches after 30 days. Paweł signature.asc Description: OpenPGP digital signature
[gentoo-dev] Automated Package Removal and Addition Tracker, for the week ending 2013-05-19 23h59 UTC
The attached list notes all of the packages that were added or removed from the tree, for the week ending 2013-05-19 23h59 UTC. Removals: dev-php/phpcpd 2013-05-13 03:27:30 patrick dev-php/phploc 2013-05-13 03:27:30 patrick app-text/wpd2odt2013-05-13 12:18:14 scarabeus dev-util/dialogblocks 2013-05-14 03:47:02 dirtyepic dev-util/helpblocks 2013-05-14 03:47:02 dirtyepic Additions: app-misc/ddate 2013-05-13 10:08:28 ssuominen app-text/writerperfect 2013-05-13 12:16:06 scarabeus dev-python/pychef 2013-05-14 19:28:15 prometheanfire www-misc/nx_util2013-05-14 21:39:22 dev-zero dev-python/pygeocoder 2013-05-16 03:40:16 patrick dev-lang/jwasm 2013-05-16 06:40:56 slyfox dev-python/netlib 2013-05-16 08:10:31 radhermit www-servers/pathod 2013-05-16 08:15:47 radhermit sci-chemistry/pymol-plugins-dynamics2013-05-16 09:53:54 jlec app-misc/solaar 2013-05-16 10:18:35 radhermit profiles/hardened 2013-05-16 19:29:27 zorry dev-python/pgmagick 2013-05-17 08:41:00 dev-zero media-fonts/termsyn 2013-05-18 10:16:30 xmw sci-electronics/qucs2013-05-18 16:38:02 mgorny -- Robin Hugh Johnson Gentoo Linux Developer E-Mail : robb...@gentoo.org GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 Removed Packages: dev-php/phpcpd,removed,patrick,2013-05-13 03:27:30 dev-php/phploc,removed,patrick,2013-05-13 03:27:30 app-text/wpd2odt,removed,scarabeus,2013-05-13 12:18:14 dev-util/dialogblocks,removed,dirtyepic,2013-05-14 03:47:02 dev-util/helpblocks,removed,dirtyepic,2013-05-14 03:47:02 Added Packages: app-misc/ddate,added,ssuominen,2013-05-13 10:08:28 app-text/writerperfect,added,scarabeus,2013-05-13 12:16:06 dev-python/pychef,added,prometheanfire,2013-05-14 19:28:15 www-misc/nx_util,added,dev-zero,2013-05-14 21:39:22 dev-python/pygeocoder,added,patrick,2013-05-16 03:40:16 dev-lang/jwasm,added,slyfox,2013-05-16 06:40:56 dev-python/netlib,added,radhermit,2013-05-16 08:10:31 www-servers/pathod,added,radhermit,2013-05-16 08:15:47 sci-chemistry/pymol-plugins-dynamics,added,jlec,2013-05-16 09:53:54 app-misc/solaar,added,radhermit,2013-05-16 10:18:35 profiles/hardened,added,zorry,2013-05-16 19:29:27 dev-python/pgmagick,added,dev-zero,2013-05-17 08:41:00 media-fonts/termsyn,added,xmw,2013-05-18 10:16:30 sci-electronics/qucs,added,mgorny,2013-05-18 16:38:02 Done.
