Re: [aur-general] Trusted User application
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. signature.asc Description: This is a digitally signed message part
Re: [aur-general] Trusted User application
Bah, and of course I get hit by the address rewriting done my the list now, and didn't think to look at the address! -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/ signature.asc Description: PGP signature
Re: [aur-general] Delete request for linux-yoga900{, -{headers, docs}}
On Mon, 2016-07-25 at 10:53 -0400, Eric Lehmann wrote: > I created this package to make some custom modifications to better > support the new laptop I got. I recently tested an installation on my > Yoga900 without any issues. As the system works fine now with the > latest kernel, I feel this package is nolonger needed and can be > deleted. Please submit a request on package's AUR page. Are you sure your patches are not useful for others? In my honest opinion you should find kernel updates substituting your modifications before removing the package. Marcin Wieczorek signature.asc Description: This is a digitally signed message part
[aur-general] Delete request for linux-yoga900{,-{headers,docs}}
I created this package to make some custom modifications to better support the new laptop I got. I recently tested an installation on my Yoga900 without any issues. As the system works fine now with the latest kernel, I feel this package is nolonger needed and can be deleted.
Re: [aur-general] Trusted User application
On Mon, 2016-07-25 at 15:17 +0200, Johannes Löthberg via aur-general wrote: > I've thought about using cblrepo to maintain a few things, but was > wondering how you add and make sure the ghc/distro packages are up > to > date in the cblrepo database? You use cblrepo to add new packages to your repo, or add dependencies already provided by other repos (for example my [haskell-happstack] depends on many packages in [haskell-core]). [1] cblrepo also tells you what packages in your repo have been updated in cabal, using `cblrepo update` and `cblrepo upgrades`. What it doesn't do is to track whether dependencies in [haskell-core] have been upgraded. For that I wrote a script [2]; check if it works for you. [1] https://github.com/magthe/cblrepo#using-it [2] https://github.com/tensor5/haskell-happstack/blob/master/updates.sh signature.asc Description: This is a digitally signed message part
Re: [aur-general] Trusted User application
Hey, Replying off-list since it's not really relevant to it. On 24/07, Nicola Squartini via aur-general wrote: haskell-happstack == To be honest I did not take too much time looking at the haskell repo thingie, however a small thing came into my mind while reading the build scripts: (I know you don't plan to move those, its just a small side note nothing more!): - everything that gets pulled into the repos must be able to build without special scripts/setup, f.e. by the wrapper extra-x86_64- build from the devtools package. The PKGBUILDs there are managed by Magnus Therning's excellent cblrepo tool [1]. My main job there is to write patches when something goes wrong with dependencies (Haskell is very strict also about dependencies). I've thought about using cblrepo to maintain a few things, but was wondering how you add and make sure the ghc/distro packages are up to date in the cblrepo database? -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/ signature.asc Description: PGP signature
Re: [aur-general] Trusted User application
On Sun, 2016-07-24 at 14:30 +0200, Levente Polyak wrote: > Any chance you feel like you need a new project and want to make > xmonad > work with wayland? :P :D Judging from the comment on GitHub issue [1] it seems that unfortunatly such thing is impossible. [1] https://github.com/xmonad/xmonad/issues/38 signature.asc Description: This is a digitally signed message part
Re: [aur-general] Trusted User application
On Mon, 2016-07-25 at 09:24 +0200, Massimiliano Torromeo wrote: > I packaged in the AUR a couple of years ago but to move it in > [community] it > required to much patching to decouple it's components and, again, > decided it > was not worth it. I then dropped it and moved along to use other > frameworks. The Meteor team is working on making it possible to decouple, and starting from version 1.4 Meteor will upgrade to Mongo 3.2 and Node 4. signature.asc Description: This is a digitally signed message part
[aur-general] Signoff report for [community-testing]
=== Signoff report for [community-testing] === https://www.archlinux.org/packages/signoffs/ There are currently: * 2 new packages in last 24 hours * 0 known bad packages * 0 packages not accepting signoffs * 0 fully signed off packages * 29 packages missing signoffs * 2 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 (2 total) == * vtk6-6.3.0-4 (i686) * vtk6-6.3.0-4 (x86_64) == Incomplete signoffs for [community] (25 total) == * jupyter-4.1.0-5 (any) 0/2 signoffs * offlineimap-7.0.0-1 (any) 0/2 signoffs * puppet-4.5.3-1 (any) 0/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) 0/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] (4 total) == * biber-2.5-1 (any) 0/2 signoffs * perl-xml-libxml-simple-0.97-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 (2 total) == * iscan-2.30.2-1 (x86_64), since 2016-07-10 * iscan-2.30.2-1 (i686), since 2016-07-10 == Top five in signoffs in last 24 hours ==
Re: [aur-general] Trusted User application
In data sabato 23 luglio 2016 13:39:45 CEST, Nicola Squartini via aur-general ha scritto: > 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). That's cool. I wanted to do something like this right after atom's first release, but once I took a look at the process I decided it was too much work and did not bother anymore. I'm glad someone else stuck to it. This should allow for other electron-based packages to use this shared runtime. > 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. I packaged in the AUR a couple of years ago but to move it in [community] it required to much patching to decouple it's components and, again, decided it was not worth it. I then dropped it and moved along to use other frameworks. Since you use it for work you should be more familiar to it than I was. -- Massimiliano Torromeo signature.asc Description: This is a digitally signed message part.