[arch-dev-public] Signoff report for [testing]
=== Signoff report for [testing] === https://www.archlinux.org/packages/signoffs/ There are currently: * 0 new packages in last 24 hours * 0 known bad packages * 0 packages not accepting signoffs * 9 fully signed off packages * 19 packages missing signoffs * 10 packages older than 14 days (Note: the word 'package' as used here refers to packages as grouped by pkgbase, architecture, and repository; e.g., one PKGBUILD produces one package per architecture, even if it is a split package.) == Incomplete signoffs for [core] (7 total) == * kbd-1.15.5-3 (i686) 1/2 signoffs * linux-3.7.3-1 (i686) 1/2 signoffs * linux-lts-3.0.59-1 (i686) 0/2 signoffs * reiserfsprogs-3.6.22-1 (i686) 1/2 signoffs * rfkill-0.4-7 (i686) 1/2 signoffs * reiserfsprogs-3.6.22-1 (x86_64) 1/2 signoffs * rfkill-0.4-7 (x86_64) 1/2 signoffs == Incomplete signoffs for [extra] (12 total) == * cairo-1.12.10-1 (i686) 0/2 signoffs * lirc-1:0.9.0-35 (i686) 0/2 signoffs * nvidia-310.19-3 (i686) 0/2 signoffs * nvidia-304xx-304.64-2 (i686) 0/2 signoffs * qemu-1.3.0-1 (i686) 0/2 signoffs * ruby-1.9.3_p374-1 (i686) 0/2 signoffs * slim-1.3.5-1 (i686) 0/2 signoffs * cairo-1.12.10-1 (x86_64) 1/2 signoffs * lirc-1:0.9.0-35 (x86_64) 0/2 signoffs * nvidia-304xx-304.64-2 (x86_64) 0/2 signoffs * ruby-1.9.3_p374-1 (x86_64) 0/2 signoffs * slim-1.3.5-1 (x86_64) 0/2 signoffs == Completed signoffs (9 total) == * dash-0.5.7-3 (i686) * lvm2-2.02.98-3 (i686) * dash-0.5.7-3 (x86_64) * kbd-1.15.5-3 (x86_64) * linux-3.7.3-1 (x86_64) * linux-lts-3.0.59-1 (x86_64) * lvm2-2.02.98-3 (x86_64) * nvidia-310.19-3 (x86_64) * qemu-1.3.0-1 (x86_64) == All packages in [testing] for more than 14 days (10 total) == * lvm2-2.02.98-3 (i686), since 2012-11-03 * lvm2-2.02.98-3 (x86_64), since 2012-11-03 * nvidia-310.19-3 (i686), since 2012-12-11 * lirc-1:0.9.0-35 (i686), since 2012-12-11 * nvidia-304xx-304.64-2 (i686), since 2012-12-11 * nvidia-310.19-3 (x86_64), since 2012-12-11 * lirc-1:0.9.0-35 (x86_64), since 2012-12-11 * nvidia-304xx-304.64-2 (x86_64), since 2012-12-11 * qemu-1.3.0-1 (i686), since 2012-12-20 * qemu-1.3.0-1 (x86_64), since 2012-12-20 == Top five in signoffs in last 24 hours == 1. thestinger - 2 signoffs
[arch-dev-public] Nymeria Migration Guide for extra
Hi,
We finally migrated extra to nymeria, here's a quick check list how to
get things working again:
Host name: nymeria.archlinux.org
User name: same as archweb login name
RSA fingerprint: cd:26:69:1a:7c:7f:bd:bd:42:4f:d7:ee:27:37:27:b4
DSA fingerprint: 11:a3:e7:27:9c:6d:8f:42:be:7c:31:93:05:1e:ad:36
ECDSA fingerprint: 6e:8b:ce:e4:74:92:3d:c2:67:9a:2f:8f:66:8b:96:e1
Migration:
- dbscripts is in /srv/repos/svn-pacakges/dbscripts and there is a
symlink /packages for easier access. community also got /community now.
- authorized ssh keys have been migrated, user names have been changed
to match archweb login names.
- fix your ~/.ssh/config so the user name is correct (only needed for
running dbscripts)
- your old home from gerolde is available in
/mnt/old_homes/gerolde/$user. Please only copy what you need and leave
or remove the rest. /mnt/old_homes will be erased in a few weeks/months.
- update devtools to 20130120 or newer
- run the following for all checkouts:
svn relocate svn+ssh://gerolde.archlinux.org/srv/svn-packages
svn+ssh://svn-packa...@nymeria.archlinux.org/srv/repos/svn-packages/svn
- do the same on pkgbuild.com if you use svn there
- You might have to recreate some dirs in ~/staging. core, extra and
testing are already there.
- If you add a new ssh key to ~/.ssh/authorized_keys it can take up to
15 minutes before the key is added to the list of authorized keys for
the svn-{packages,community} user.
You will only have an account on nymeria if you were marked active in
archweb and in the dev group.
If something is broken please tell Pierre or me via mail or IRC.
signature.asc
Description: OpenPGP digital signature
Re: [arch-dev-public] Nymeria Migration Guide for extra
On 20 January 2013 18:31, Florian Pritz bluew...@xinu.at wrote:
Hi,
We finally migrated extra to nymeria, here's a quick check list how to
get things working again:
Host name: nymeria.archlinux.org
User name: same as archweb login name
RSA fingerprint: cd:26:69:1a:7c:7f:bd:bd:42:4f:d7:ee:27:37:27:b4
DSA fingerprint: 11:a3:e7:27:9c:6d:8f:42:be:7c:31:93:05:1e:ad:36
ECDSA fingerprint: 6e:8b:ce:e4:74:92:3d:c2:67:9a:2f:8f:66:8b:96:e1
Migration:
- dbscripts is in /srv/repos/svn-pacakges/dbscripts and there is a
symlink /packages for easier access. community also got /community now.
- authorized ssh keys have been migrated, user names have been changed
to match archweb login names.
- fix your ~/.ssh/config so the user name is correct (only needed for
running dbscripts)
- your old home from gerolde is available in
/mnt/old_homes/gerolde/$user. Please only copy what you need and leave
or remove the rest. /mnt/old_homes will be erased in a few weeks/months.
- update devtools to 20130120 or newer
- run the following for all checkouts:
svn relocate svn+ssh://gerolde.archlinux.org/srv/svn-packages
svn+ssh://svn-packa...@nymeria.archlinux.org/srv/repos/svn-packages/svn
- do the same on pkgbuild.com if you use svn there
- You might have to recreate some dirs in ~/staging. core, extra and
testing are already there.
- If you add a new ssh key to ~/.ssh/authorized_keys it can take up to
15 minutes before the key is added to the list of authorized keys for
the svn-{packages,community} user.
You will only have an account on nymeria if you were marked active in
archweb and in the dev group.
If something is broken please tell Pierre or me via mail or IRC.
Hi,
Thanks for this.
Just for you to know we do not have read rights on /mnt/old_home/gerolde
--
Guillaume
Re: [arch-dev-public] Nymeria Migration Guide for extra
Just for you to know we do not have read rights on /mnt/old_home/gerolde Fixed signature.asc Description: OpenPGP digital signature
Re: [arch-dev-public] [arch-general] Winter Cleanup of [community]
[2013-01-19 17:54:51 +0100] Alexander Rødseth: It's time again for the yearly cleanup of the [community] repository. Please send such messages to arch-dev-public in the future: adopting packages are dev's and TU's decision, and not all read arch-general. Somehow, time passed, and it's now too late for a Christmas Cleanup like last year. Instead I'm announcing a Winter Cleanup, which I think is a better name as well. 45.8 degrees beg to differ. -- Gaetan
Re: [arch-dev-public] [arch-general] SeaMonkey outdated. Critical security holes in the current version!
Hrm... this got dropped to [community] so that there would be a better response time to updates. Obviously it has not happened, so it should be dropped. I'll wait 24 hours... Allan
Re: [arch-dev-public] [arch-general] Winter Cleanup of [community]
Hi, @Fons Adriaensen Didn't think of that, here's the current list: dcron espeakup gmerlin-avdecoder i2c-tools iksemel isomaster libmatio libtlen libtxc_dxtn libxml-perl lua-sql-mysql lua-sql-postgres lua-sql-sqlite mget multipath-tools ndisc6 nvclock pam-krb5 perl-text-wrapi18n pidgin-musictracker python2-gasp python2-pypdf ttf-envy-code-r udunits vim-nerdcommenter vim-timestamp winefish I also checked that none of these packages are makedepends of any of the [community] packages. @Gaetan Bisson: Please send such messages to arch-dev-public in the future: adopting packages are dev's and TU's decision, and not all read arch-general. I also think non-devs and non-TUs may have valuable insights for why for instance a package should be considered to be too important to not be moved to unsupported. The ibus and lxdm packages were considered to be too important to move to unsupported during the last cleanup. Perhaps someone (the upstream developers?) may have a reason or opinion for why one of the listed packages should not be moved. The decision would still be in the hands of devs and TUs, but there could still be potentially useful information coming from the outside. 45.8 degrees beg to differ. Point taken, and suggestions for a better name are welcome. How about New Year Cleanup? -- Sincerely, Alexander Rødseth xyproto / TU
Re: [arch-dev-public] [arch-general] Winter Cleanup of [community]
On Mon, Jan 21, 2013 at 12:05 AM, Alexander Rødseth rods...@gmail.com wrote: ndisc6 I took this one. I use it. Cheers, -- Sébastien Seblu Luttringer https://www.seblu.net GPG: 0x2072D77A
[arch-dev-public] Winter Cleanup of [community]
Hi, Posting this here as well, after a suggestion from Gaetan Bisson: It's time again for the yearly cleanup of the [community] repository. Somehow, time passed, and it's now too late for a Christmas Cleanup like last year. Instead I'm announcing a Winter Cleanup, which I think is a better name as well. (Or perhaps New Year Cleanup is better, as there isn't winter everywhere at the same time. Suggestions for a better name is welcome). The wonderful developers of Arch Web have added a report of Uneeded Orphans since last time, which should make this cleanup considerably easier. (Thanks Dan McGee: https://projects.archlinux.org/archweb.git/commit/?id=5379348c9337a4abe27e807fef7956e11eebed30) Another positive development is that all the ibus-packages that nobody seemed to want to adopt, are no longer orphans. Thanks goes out to Felix Yan, one of our latest TUs, for that. The list of unneeded orphans can be viewed at this page: https://www.archlinux.org/devel/reports/unneeded-orphans/ Here is the current list: dcron espeakup gmerlin-avdecoder i2c-tools iksemel isomaster libmatio libtlen libtxc_dxtn libxml-perl lua-sql-mysql lua-sql-postgres lua-sql-sqlite mget multipath-tools ndisc6 nvclock pam-krb5 perl-text-wrapi18n pidgin-musictracker python2-gasp python2-pypdf ttf-envy-code-r udunits vim-nerdcommenter vim-timestamp winefish I also checked that none of these packages are makedepends of any of the other [community] packages. If you know of other packages that deserves to be cleaned up somehow, in [community], AUR or any of the other repositories, please reply to this e-mail and let us know. (If there should be too many requests, we'll start a wiki page this year as well). If there aren't any protests, I'll wait a couple of days and then move all the unneeded orphans in [community] to AUR. Developers and maintainers of [core], [extra] and [multilib] should feel free to join in on the cleanup, of course. I'll round off this invitation with a somewhat pretentious and slightly akward slogan: :] Happy Winter Cleanup. Let our repositories shine! Sincerely, Alexander Rødseth xyproto / TU
Re: [arch-dev-public] [arch-general] Winter Cleanup of [community]
[2013-01-21 00:05:32 +0100] Alexander Rødseth: I also think non-devs and non-TUs may have valuable insights for why for instance a package should be considered to be too important to not be moved to unsupported. Sure. Users sometimes make insightful points on what is being discussed on arch-dev-public by replying to arch-general. Most users interested in Arch's development should read arch-dev-public anyway. If you are really looking for community feedback, cross-posting to arch-general is fine, but you should post to arch-dev-public in any case. -- Gaetan
