| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
RepoMan-Options: --include-arches="ppc64"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
RepoMan-Options: --include-arches="ppc64"
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
RepoMan-Options: --include-arches="ppc"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
RepoMan-Options: --include-arches="ppc"
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
|
| |
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
Package-Manager: Portage-2.3.19, Repoman-2.3.6
RepoMan-Options: --include-arches="amd64"
|
|
|
|
|
|
|
| |
ernsteiswuerfel)
Package-Manager: Portage-2.3.24, Repoman-2.3.6
RepoMan-Options: --include-arches="ppc64"
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/648458
Closes: https://github.com/gentoo/gentoo/pull/7250
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/580022
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/588432
Closes: https://github.com/gentoo/gentoo/pull/7247
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/588432
Closes: https://github.com/gentoo/gentoo/pull/5317
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/645910
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
RepoMan-Options: --include-arches="ia64"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
RepoMan-Options: --include-arches="ia64"
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
Closes: https://github.com/gentoo/gentoo/pull/7199
|
|
|
|
|
|
|
|
|
| |
Remove useless/redundant maintainer <description/>. It does not benefit
bug wrangling, and only wastes developer's time on reading it. Few tips:
- assignee/CC is implied by ordering, there is no reason to repeat it,
- we know that maintainer is maintainer (la la la la la),
- most of adjectives for maintainer are of no value and/or are obvious.
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/647052
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.20, Repoman-2.3.6
|
| |
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
| |
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Gentoo-Bug: http://bugs.gentoo.org/608346
|
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.3
RepoMan-Options: --include-arches="hppa"
|
|
|
|
| |
Closes: https://bugs.gentoo.org/642912
|
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/show_bug.cgi?id=642918
Package-Manager: Portage-2.3.16, Repoman-2.3.6
Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.17, Repoman-2.3.6
|
|
|
|
|
|
|
|
|
| |
maksbotan (who is currently inactive as Gentoo developer, according to
git and IRC logs) was proxying maintenance by me. Since I am now Gentoo
developer myself, there's no need for proxying, as I am willing to
maintain sys-block/whdd as needed.
Package-Manager: Portage-2.3.17, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.17, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
TL;DR: if you run 3ware cards on a 3.8 or newer kernel, you need to
upgrade the utility to correctly write card variables, as the old
version will sometimes segfault.
Tested on hardware models: 9750-4i, 9650SE-8LPML, 9690SA.
Per email:
> I've noticed recently that sys-block/tw_cli will segfault on modern
> systems when setting variables on a card (at least on a 9750-4i).
> ...
> when you go to run a battery capacity test, it'll complete the capacity
> test command, but segfault before it can update the timestamp on the
> card to record the last capacity test date. That causes the date to
> become "01-Jan-1970", and then dmesg will get flooded with "Battery
> capacity test overdue" messages. That's what prompted me to open a case
> with Broadcom, and then try to find some kind of workaround.
Reported-by: Joshua Kinard <kumba@gentoo.org>
Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
Package-Manager: Portage-2.3.16, Repoman-2.3.6
RepoMan-Options: --force
|
|
|
|
| |
Package-Manager: Portage-2.3.14, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Ebuild changes:
===============
- Patch: Include sysmacros.h. [Bug 604442]
- Install systemd service. [Bug 640598]
- Remove deprecated iscsidev.sh udev rule in favor of udev native iSCSI
support which is available since udev-143. [Bug 633574]
- Drop "slp" USE flag. [Bug 558366]
Bug: https://bugs.gentoo.org/558366
Closes: https://bugs.gentoo.org/604442
Closes: https://bugs.gentoo.org/640598
Closes: https://bugs.gentoo.org/633574
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/642916
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
|
|
|
|
|
|
| |
Ebuild changes:
===============
- x86 dropped because no x86 package is currently available.
Closes: https://bugs.gentoo.org/641982
Package-Manager: Portage-2.3.19, Repoman-2.3.6
Signed-off-by: Thomas Deutschmann <whissi@gentoo.org>
|