July 2016 - Aur-general - lists.archlinux.org

[aur-general] ttf-google-webfonts{,-distilled,-git,-hg} mess
by Jason St. John 19 Jun '19

19 Jun '19

I am the current maintainer of the AUR package ttf-google-webfonts-hg[4], and I'm bothered by the mess of various packages there are for Google's Web Fonts project. It's not at all KISS in its current state. There are currently four different AUR packages[1][2][3][4] that essentially supply the same files, and all four packages conflict with each other. Around August of 2012, the package named ttf-google-webfonts[1] was orphaned, and user w0ng created a GitHub repository[5] that mirrors the Mercurial repository[6] on Google Code (why?). Then, the new maintainer changed the original ttf-google-webfonts package from a VCS-type package that simply lacked "-hg" in the name to a package that pulls tarballs from w0ng's GitHub repo[5]. As you can see in the comments for ttf-google-webfonts[1], this has caused all sorts of confusion and messages about the package being out-of-date or having invalid checksums. To get around these issues, user epinephrine created the package ttf-google-webfonts-git[3] that clones w0ng's GitHub repo[5] instead of pulling tarballs from it, which significantly reduces the maintenance required on the package. Then, user Gently created a package named ttf-google-webfonts-distilled[2] that pulls a tarball from w0ng's GitHub repo[5] and only installs a small subset of the fonts therein. Shortly after ttf-google-webfonts[1] was changed from being a Mercurial-based package and not liking the direction that the package was taking, I reuploaded the original ttf-google-webfonts package as ttf-google-webfonts-hg[4] for people that simply wanted the old package back that uses the actual Google Web Fonts repository to download the files. To clean up this mess, I propose that ttf-google-webfonts-distilled[2] and ttf-google-webfonts-git[3] be deleted outright, for what should be obvious reasons. I also propose that ttf-google-webfonts[1] be deleted because of how frequently the Web Fonts project is updated and because the project lacks version numbers. If people really feel strongly about keeping that maintenance nightmare, then let them have it, but I really don't see what advantage it provides over the original ttf-google-webfonts-hg[4] other than one less makedepends. I apologize for the huge email, but this situation really is a mess. [1] https://aur.archlinux.org/packages/ttf-google-webfonts/ [2] https://aur.archlinux.org/packages/ttf-google-webfonts-distilled/ [3] https://aur.archlinux.org/packages/ttf-google-webfonts-git/ [4] https://aur.archlinux.org/packages/ttf-google-webfonts-hg/ [5] https://github.com/w0ng/googlefontdirectory [6] https://code.google.com/p/googlefontdirectory/ Jason

14 23

[aur-general] PKGBUILD review request: libdime-hg
by Alessandro Menti 15 Aug '16

15 Aug '16

Hi everyone, I've just started writing some PKGBUILDs for some programs that are not present neither in the official package repository nor in the AUR. Specifically, I've packaged libdime [1] as a required dependency for the X-Plane developer tools [2]. I'm attaching the PKGBUILD below - if someone on this list could review it, that would be much appreciated. I've also got the following questions: 1) Is it correct to name the package "libdime-hg" only because its sources are checked out from a Mercurial repository (that's because no official tarballs exist any more - the Debian copyright file for the library [3] points to a now dismissed FTP site [4]), or should I just name it "libdime"? 2) On the same note, assuming that naming the package "libdime-hg" is correct, does it make sense to put provides=("${pkgname%-hg}") conflicts=("${pkgname%-hg}") in the PKGBUILD? I've thought to put these two lines as "safeguards" in case I need to distinguish between a libdime VCS and non-VCS package in the future. Cheers and thanks in advance, Alessandro Menti [1] https://bitbucket.org/Coin3D/dime [2] http://developer.x-plane.com/tools/ [3] http://metadata.ftp-master.debian.org/changelogs/main/d/dime/dime_0.2011120… [4] ftp://ftp.sim.no/pub/snapshots/ ----- The PKGBUILD follows: -------------------------------------------- # Maintainer: Alessandro Menti <alessandro dot menti at hotmail dot it> pkgname=libdime-hg pkgver=r187.7cd55bc6a6d0 pkgrel=1 pkgdesc="A DXF (Data eXchange Format) file format support library" arch=('i686' 'x86_64') url="https://bitbucket.org/Coin3D/dime" license=('BSD') depends=('gcc-libs') makedepends=('doxygen' 'mercurial') provides=("${pkgname%-hg}") conflicts=("${pkgname%-hg}") source=("${pkgname%-hg}::hg+https://bitbucket.org/Coin3D/dime") sha256sums=('SKIP') pkgver() { cd "$srcdir/${pkgname%-hg}" printf "r%s.%s" "$(hg identify -n)" "$(hg identify -i)" } build() { cd "$srcdir/${pkgname%-hg}" ./configure --prefix=/usr --enable-html make } package() { cd "$srcdir/${pkgname%-hg}" make DESTDIR="$pkgdir/" install install -D -m644 COPYING "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE" }

3 6

[aur-general] Trusted User application
by Nicola Squartini 12 Aug '16

12 Aug '16

Hi, My name is Nicola Squartini, long time Arch Linux user and enthusiast. I would like to become a Trusted User and György Balló offered to sponsor my application. I maintain the unofficial [atom] repository [1], and as a Trusted User my first mission will be to bring Atom and Electron to [community]. Atom is "A hackable text editor for the 21st Century"; contrary to what you learned in your physics class, at the core of Atom is Electron, a software that uses Chromium and Node to build desktop applications using JavaScript, HTML and CSS. When I first started using Atom, I didn't like the fact that the official installation procedure would push precompiled stuff into my system: as every old school Linux guy, I feel itchy using binaries not compiled by me or by the distribution of my choice. So I decided to create the [atom] repository and build Atom entirely from source; this wasn't easy, expecially with older versions, and it involved a lot of patching of the build system. I also decided to take a few steps further, like decoupling Atom from Electron (so that the latter can be used also for other applications), unbundling system libraries as much as possible, and enable GTK3 support (upstream binaries are built with GTK2). My method and patches for building Atom and Electron have been adopted also by Fedora. I contributed upstream with pull requests (some accepted, some not) and I will continue to do so. My other contributions to the Arch Linux community are the [haskell- happstack] repository [2], which contains web related packages for the Haskell programming language (my favourite language, btw), and a few packages on AUR [3], two of which I'm the author. I always build packages in chroot, and check them with namcap (in fact, back in May I posted a patch for namcap [4]). My main interests are functional programming and mathematics, although recently I do mostly web programming as I became involved in a startup. My strongest languages are Haskell, JavaScript and C. You can check my works on GitHub [5]. If accepted as a TU, I would like to maintain open source Electron based applications (Atom is the most popular, but there are others like Visual Studio Code [6], webtorrent-desktop [7], N1 [8] and Brave [9]). In the future I would also like to maintain Meteor [10], a popular web framework that I use for my job (I don't know if someone is already working on it), but only after they add support for the latest Node. Please don't hesitate to ask me questions, if you have any, and I hope to join the team! Best Regards Nicola Squartini [1] https://github.com/tensor5/arch-atom [2] https://github.com/tensor5/haskell-happstack [3] https://aur.archlinux.org/packages/?SeB=m&K=tensor5 [4] https://lists.archlinux.org/pipermail/arch-projects/2016-May/004346.html [5] https://github.com/tensor5 [6] https://github.com/Microsoft/vscode [7] https://github.com/feross/webtorrent-desktop [8] https://nylas.com/ [9] https://www.brave.com/ [10] https://www.meteor.com/

16 31

Re: [aur-general] Trusted User application
by Nicola Squartini 05 Aug '16

05 Aug '16

On Mon, 2016-07-25 at 18:06 +0200, Johannes Löthberg wrote: > What about the packages provided by ghc? Guess you could do > something > similar to get the provides list from pacman, hmm.. Thanks though! GHC only updates once every 4-5 months and provides few packages, so I don't mind handling those manually.

3 2

[aur-general] Deletion request for python-libtorrent-rasterbar
by Charles Pigott 01 Aug '16

01 Aug '16

After I noticed this package had gone missing from the AUR (git repo was still available, package page was 404ing), I resurrected it as it had broken the dependency for magnet2torrent-git Interestingly, the packaging and install somehow worked fine for me the first time, but then it was pointed out to me that there were file conflicts between it and one of its own dependencies, libtorrent-rasterbar. All of the files in the python package, for instance. Which happen to be all of the files in it. As such, python-libtorrent-rasterbar has been fully replaced by libtorrent-rasterbar and can be (re-)removed from AUR. I'll work on getting the dependency on magnet2torrent fixed instead. C

2 1

[aur-general] Questions before submitting my first package
by Henk te Sligte 31 Jul '16

31 Jul '16

Hi all, I noticed in the archlinux general mailing list that a package has been removed from community because the maintainer wasn't active anymore, but the package was not moved to AUR. I decided that this might be a nice first step in becoming a package maintainer in the AUR. But I have a few questions before I submit something that would be below the AUR standards. By the way, the package is called Dasher [1]. The last stable release (4.11) of Dasher is from six years ago. However, the package seems to be maintained, the last commit to the Gnome hosted repository [2] is two weeks ago. So I presume it would be the smartest to release it from git. But then the package would be called dasher-git, I presume? I can also go back a few commits before, to 5.0 beta, but that doesn't build. That has been fixed a commit later. What commit would you use to publish the package? I can also just copy and paste the PKGBUILD from svntogit [3] before it was removed from community, that uses the latest alpha build, but to me it makes more sense to go to either beta (which doesn't build) or the latest from master. I hope some experienced AUR maintainers can give me their thoughts about this to make my first AUR package a success. Greetings, Henk te Sligte [1] http://www.inference.phy.cam.ac.uk/dasher/ [2] https://git.gnome.org/browse/dasher/ [3] https://git.archlinux.org/svntogit/packages.git/tree/dasher/trunk?id=c819de…

2 1

[aur-general] Signoff report for [community-testing]
by Arch Website Notification 31 Jul '16

31 Jul '16

=== Signoff report for [community-testing] === https://www.archlinux.org/packages/signoffs/ There are currently: * 23 new packages in last 24 hours * 0 known bad packages * 0 packages not accepting signoffs * 0 fully signed off packages * 50 packages missing signoffs * 13 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.) == New packages in [community-testing] in last 24 hours (23 total) == * bluegriffon-2.1.1-2 (i686) * ffmpeg0.10-0.10.16-2 (i686) * mediastreamer-2.12.1-5 (i686) * mythplugins-1:0.28-2 (i686) * mythtv-1:0.28-6 (i686) * qxmpp-0.9.3-3 (i686) * seamonkey-2.40-4 (i686) * toxcore-3747-2 (i686) * toxic-0.7.0-5 (i686) * virtualbox-5.1.2-2 (i686) * xulrunner-41.0.2-8 (i686) * bluegriffon-2.1.1-2 (x86_64) * ffmpeg0.10-0.10.16-2 (x86_64) * hhvm-3.14.3-2 (x86_64) * mediastreamer-2.12.1-5 (x86_64) * mythplugins-1:0.28-2 (x86_64) * mythtv-1:0.28-6 (x86_64) * qxmpp-0.9.3-3 (x86_64) * seamonkey-2.40-4 (x86_64) * toxcore-3747-2 (x86_64) * toxic-0.7.0-5 (x86_64) * virtualbox-5.1.2-2 (x86_64) * xulrunner-41.0.2-8 (x86_64) == Incomplete signoffs for [community] (47 total) == * jupyter-4.1.0-5 (any) 0/2 signoffs * puppet-4.5.3-1 (any) 1/2 signoffs * bluegriffon-2.1.1-2 (i686) 0/1 signoffs * cutegram-2.9.5-2 (i686) 0/1 signoffs * facter-3.3.0-1 (i686) 0/1 signoffs * fcitx-libpinyin-0.3.91-1 (i686) 0/1 signoffs * ffmpeg0.10-0.10.16-2 (i686) 0/1 signoffs * ibus-libpinyin-1.7.91-1 (i686) 0/1 signoffs * iscan-2.30.2-1 (i686) 0/1 signoffs * libpinyin-1.5.91-1 (i686) 0/1 signoffs * libqtelegram-ae-3:10.0.0-1 (i686) 0/1 signoffs * luasec-2:0.6-1 (i686) 0/1 signoffs * mediastreamer-2.12.1-5 (i686) 0/1 signoffs * mythplugins-1:0.28-2 (i686) 0/1 signoffs * mythtv-1:0.28-6 (i686) 0/1 signoffs * qxmpp-0.9.3-3 (i686) 0/1 signoffs * seamonkey-2.40-4 (i686) 0/1 signoffs * telegramqml-2.0.0-1 (i686) 0/1 signoffs * toxcore-3747-2 (i686) 0/1 signoffs * toxic-0.7.0-5 (i686) 0/1 signoffs * virtualbox-5.1.2-2 (i686) 0/1 signoffs * vtk6-6.3.0-4 (i686) 0/1 signoffs * wt-3.3.6-1 (i686) 0/1 signoffs * xulrunner-41.0.2-8 (i686) 0/1 signoffs * bluegriffon-2.1.1-2 (x86_64) 0/2 signoffs * cutegram-2.9.5-2 (x86_64) 0/2 signoffs * facter-3.3.0-1 (x86_64) 1/2 signoffs * fcitx-libpinyin-0.3.91-1 (x86_64) 0/2 signoffs * ffmpeg0.10-0.10.16-2 (x86_64) 0/2 signoffs * hhvm-3.14.3-2 (x86_64) 0/2 signoffs * ibus-libpinyin-1.7.91-1 (x86_64) 0/2 signoffs * iscan-2.30.2-1 (x86_64) 0/2 signoffs * libpinyin-1.5.91-1 (x86_64) 0/2 signoffs * libqtelegram-ae-3:10.0.0-1 (x86_64) 0/2 signoffs * luasec-2:0.6-1 (x86_64) 0/2 signoffs * mediastreamer-2.12.1-5 (x86_64) 0/2 signoffs * mythplugins-1:0.28-2 (x86_64) 0/2 signoffs * mythtv-1:0.28-6 (x86_64) 0/2 signoffs * qxmpp-0.9.3-3 (x86_64) 0/2 signoffs * seamonkey-2.40-4 (x86_64) 0/2 signoffs * telegramqml-2.0.0-1 (x86_64) 0/2 signoffs * toxcore-3747-2 (x86_64) 0/2 signoffs * toxic-0.7.0-5 (x86_64) 0/2 signoffs * virtualbox-5.1.2-2 (x86_64) 0/2 signoffs * vtk6-6.3.0-4 (x86_64) 0/2 signoffs * wt-3.3.6-1 (x86_64) 0/2 signoffs * xulrunner-41.0.2-8 (x86_64) 0/2 signoffs == Incomplete signoffs for [unknown] (3 total) == * biber-2.5-1 (any) 0/2 signoffs * aseman-qt-tools-1.0.0-1 (i686) 0/1 signoffs * aseman-qt-tools-1.0.0-1 (x86_64) 0/2 signoffs == All packages in [community-testing] for more than 14 days (13 total) == * iscan-2.30.2-1 (x86_64), since 2016-07-10 * iscan-2.30.2-1 (i686), since 2016-07-10 * aseman-qt-tools-1.0.0-1 (i686), since 2016-07-13 * aseman-qt-tools-1.0.0-1 (x86_64), since 2016-07-13 * libqtelegram-ae-3:10.0.0-1 (i686), since 2016-07-13 * libqtelegram-ae-3:10.0.0-1 (x86_64), since 2016-07-13 * telegramqml-2.0.0-1 (i686), since 2016-07-13 * telegramqml-2.0.0-1 (x86_64), since 2016-07-13 * cutegram-2.9.5-2 (i686), since 2016-07-13 * cutegram-2.9.5-2 (x86_64), since 2016-07-13 * luasec-2:0.6-1 (i686), since 2016-07-14 * luasec-2:0.6-1 (x86_64), since 2016-07-14 * jupyter-4.1.0-5 (any), since 2016-07-16 == Top five in signoffs in last 24 hours == 1. lcarlier - 4 signoffs

1 0

[aur-general] Signoff report for [community-testing]
by Arch Website Notification 30 Jul '16

30 Jul '16

=== Signoff report for [community-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 * 0 fully signed off packages * 27 packages missing signoffs * 13 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 [community] (24 total) == * jupyter-4.1.0-5 (any) 0/2 signoffs * puppet-4.5.3-1 (any) 1/2 signoffs * cutegram-2.9.5-2 (i686) 0/1 signoffs * facter-3.3.0-1 (i686) 0/1 signoffs * fcitx-libpinyin-0.3.91-1 (i686) 0/1 signoffs * ibus-libpinyin-1.7.91-1 (i686) 0/1 signoffs * iscan-2.30.2-1 (i686) 0/1 signoffs * libpinyin-1.5.91-1 (i686) 0/1 signoffs * libqtelegram-ae-3:10.0.0-1 (i686) 0/1 signoffs * luasec-2:0.6-1 (i686) 0/1 signoffs * telegramqml-2.0.0-1 (i686) 0/1 signoffs * vtk6-6.3.0-4 (i686) 0/1 signoffs * wt-3.3.6-1 (i686) 0/1 signoffs * cutegram-2.9.5-2 (x86_64) 0/2 signoffs * facter-3.3.0-1 (x86_64) 1/2 signoffs * fcitx-libpinyin-0.3.91-1 (x86_64) 0/2 signoffs * ibus-libpinyin-1.7.91-1 (x86_64) 0/2 signoffs * iscan-2.30.2-1 (x86_64) 0/2 signoffs * libpinyin-1.5.91-1 (x86_64) 0/2 signoffs * libqtelegram-ae-3:10.0.0-1 (x86_64) 0/2 signoffs * luasec-2:0.6-1 (x86_64) 0/2 signoffs * telegramqml-2.0.0-1 (x86_64) 0/2 signoffs * vtk6-6.3.0-4 (x86_64) 0/2 signoffs * wt-3.3.6-1 (x86_64) 0/2 signoffs == Incomplete signoffs for [unknown] (3 total) == * biber-2.5-1 (any) 0/2 signoffs * aseman-qt-tools-1.0.0-1 (i686) 0/1 signoffs * aseman-qt-tools-1.0.0-1 (x86_64) 0/2 signoffs == All packages in [community-testing] for more than 14 days (13 total) == * iscan-2.30.2-1 (x86_64), since 2016-07-10 * iscan-2.30.2-1 (i686), since 2016-07-10 * aseman-qt-tools-1.0.0-1 (i686), since 2016-07-13 * aseman-qt-tools-1.0.0-1 (x86_64), since 2016-07-13 * libqtelegram-ae-3:10.0.0-1 (i686), since 2016-07-13 * libqtelegram-ae-3:10.0.0-1 (x86_64), since 2016-07-13 * telegramqml-2.0.0-1 (i686), since 2016-07-13 * telegramqml-2.0.0-1 (x86_64), since 2016-07-13 * cutegram-2.9.5-2 (i686), since 2016-07-13 * cutegram-2.9.5-2 (x86_64), since 2016-07-13 * luasec-2:0.6-1 (i686), since 2016-07-14 * luasec-2:0.6-1 (x86_64), since 2016-07-14 * jupyter-4.1.0-5 (any), since 2016-07-16 == Top five in signoffs in last 24 hours ==

1 0

[aur-general] Signoff report for [community-testing]
by Arch Website Notification 29 Jul '16

29 Jul '16

=== Signoff report for [community-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 * 0 fully signed off packages * 27 packages missing signoffs * 12 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 [community] (24 total) == * jupyter-4.1.0-5 (any) 0/2 signoffs * puppet-4.5.3-1 (any) 1/2 signoffs * cutegram-2.9.5-2 (i686) 0/1 signoffs * facter-3.3.0-1 (i686) 0/1 signoffs * fcitx-libpinyin-0.3.91-1 (i686) 0/1 signoffs * ibus-libpinyin-1.7.91-1 (i686) 0/1 signoffs * iscan-2.30.2-1 (i686) 0/1 signoffs * libpinyin-1.5.91-1 (i686) 0/1 signoffs * libqtelegram-ae-3:10.0.0-1 (i686) 0/1 signoffs * luasec-2:0.6-1 (i686) 0/1 signoffs * telegramqml-2.0.0-1 (i686) 0/1 signoffs * vtk6-6.3.0-4 (i686) 0/1 signoffs * wt-3.3.6-1 (i686) 0/1 signoffs * cutegram-2.9.5-2 (x86_64) 0/2 signoffs * facter-3.3.0-1 (x86_64) 1/2 signoffs * fcitx-libpinyin-0.3.91-1 (x86_64) 0/2 signoffs * ibus-libpinyin-1.7.91-1 (x86_64) 0/2 signoffs * iscan-2.30.2-1 (x86_64) 0/2 signoffs * libpinyin-1.5.91-1 (x86_64) 0/2 signoffs * libqtelegram-ae-3:10.0.0-1 (x86_64) 0/2 signoffs * luasec-2:0.6-1 (x86_64) 0/2 signoffs * telegramqml-2.0.0-1 (x86_64) 0/2 signoffs * vtk6-6.3.0-4 (x86_64) 0/2 signoffs * wt-3.3.6-1 (x86_64) 0/2 signoffs == Incomplete signoffs for [unknown] (3 total) == * biber-2.5-1 (any) 0/2 signoffs * aseman-qt-tools-1.0.0-1 (i686) 0/1 signoffs * aseman-qt-tools-1.0.0-1 (x86_64) 0/2 signoffs == All packages in [community-testing] for more than 14 days (12 total) == * iscan-2.30.2-1 (x86_64), since 2016-07-10 * iscan-2.30.2-1 (i686), since 2016-07-10 * aseman-qt-tools-1.0.0-1 (i686), since 2016-07-13 * aseman-qt-tools-1.0.0-1 (x86_64), since 2016-07-13 * libqtelegram-ae-3:10.0.0-1 (i686), since 2016-07-13 * libqtelegram-ae-3:10.0.0-1 (x86_64), since 2016-07-13 * telegramqml-2.0.0-1 (i686), since 2016-07-13 * telegramqml-2.0.0-1 (x86_64), since 2016-07-13 * cutegram-2.9.5-2 (i686), since 2016-07-13 * cutegram-2.9.5-2 (x86_64), since 2016-07-13 * luasec-2:0.6-1 (i686), since 2016-07-14 * luasec-2:0.6-1 (x86_64), since 2016-07-14 == Top five in signoffs in last 24 hours == 1. jasonwryan - 4 signoffs 2. eworm - 1 signoffs

1 0

[aur-general] Signoff report for [community-testing]
by Arch Website Notification 28 Jul '16

28 Jul '16

=== Signoff report for [community-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 * 0 fully signed off packages * 28 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 [community] (25 total) == * jupyter-4.1.0-5 (any) 0/2 signoffs * offlineimap-7.0.0-1 (any) 1/2 signoffs * puppet-4.5.3-1 (any) 1/2 signoffs * cutegram-2.9.5-2 (i686) 0/1 signoffs * facter-3.3.0-1 (i686) 0/1 signoffs * fcitx-libpinyin-0.3.91-1 (i686) 0/1 signoffs * ibus-libpinyin-1.7.91-1 (i686) 0/1 signoffs * iscan-2.30.2-1 (i686) 0/1 signoffs * libpinyin-1.5.91-1 (i686) 0/1 signoffs * libqtelegram-ae-3:10.0.0-1 (i686) 0/1 signoffs * luasec-2:0.6-1 (i686) 0/1 signoffs * telegramqml-2.0.0-1 (i686) 0/1 signoffs * vtk6-6.3.0-4 (i686) 0/1 signoffs * wt-3.3.6-1 (i686) 0/1 signoffs * cutegram-2.9.5-2 (x86_64) 0/2 signoffs * facter-3.3.0-1 (x86_64) 1/2 signoffs * fcitx-libpinyin-0.3.91-1 (x86_64) 0/2 signoffs * ibus-libpinyin-1.7.91-1 (x86_64) 0/2 signoffs * iscan-2.30.2-1 (x86_64) 0/2 signoffs * libpinyin-1.5.91-1 (x86_64) 0/2 signoffs * libqtelegram-ae-3:10.0.0-1 (x86_64) 0/2 signoffs * luasec-2:0.6-1 (x86_64) 0/2 signoffs * telegramqml-2.0.0-1 (x86_64) 0/2 signoffs * vtk6-6.3.0-4 (x86_64) 0/2 signoffs * wt-3.3.6-1 (x86_64) 0/2 signoffs == Incomplete signoffs for [unknown] (3 total) == * biber-2.5-1 (any) 0/2 signoffs * aseman-qt-tools-1.0.0-1 (i686) 0/1 signoffs * aseman-qt-tools-1.0.0-1 (x86_64) 0/2 signoffs == All packages in [community-testing] for more than 14 days (10 total) == * iscan-2.30.2-1 (x86_64), since 2016-07-10 * iscan-2.30.2-1 (i686), since 2016-07-10 * aseman-qt-tools-1.0.0-1 (i686), since 2016-07-13 * aseman-qt-tools-1.0.0-1 (x86_64), since 2016-07-13 * libqtelegram-ae-3:10.0.0-1 (i686), since 2016-07-13 * libqtelegram-ae-3:10.0.0-1 (x86_64), since 2016-07-13 * telegramqml-2.0.0-1 (i686), since 2016-07-13 * telegramqml-2.0.0-1 (x86_64), since 2016-07-13 * cutegram-2.9.5-2 (i686), since 2016-07-13 * cutegram-2.9.5-2 (x86_64), since 2016-07-13 == Top five in signoffs in last 24 hours == 1. pid1 - 3 signoffs 2. byte - 3 signoffs 3. jasonwryan - 1 signoffs

1 0