On Thursday, May 18 2017, Boyuan Yang wrote:
> 在 2017年5月18日星期四 +08 下午12:07:41，SJ Zhu 写道：
>> On Thu, May 18, 2017 at 11:59:36AM +0800, Boyuan Yang wrote:
>> > There are some problems: this packaging uses upstream source code directly
>> > from from Git repository, not the tarball upstream released
I checked the repo in collab-maint. I think it's not ideal to remove the
vendor js/css in source tree. We should remove it during building.
On ideal approach is to use dh-linktree to link these libraries, taking
wordpress for example,
在 2017年5月19日星期五 CST 下午3:06:30，Pirate Praveen 写道：
> On 2017, മേയ് 18 9:35:50 PM IST, Boyuan Yang <073p...@gmail.com> wrote:
> >I have several understandings on it:
> >
> >Option 1
> >
> >
> >* Will not use any bundled javascript libraries, no matter minified or
> >not
> >* Will depend
On 2017, മേയ് 18 9:35:50 PM IST, Boyuan Yang <073p...@gmail.com> wrote:
>I have several understandings on it:
>
>Option 1
>
>
>* Will not use any bundled javascript libraries, no matter minified or
>not
>* Will depend on corresponding libjs-* packages and make symlinks to
>provide
在 2017年5月18日星期四 +08 下午12:07:41，SJ Zhu 写道：
> On Thu, May 18, 2017 at 11:59:36AM +0800, Boyuan Yang wrote:
> > There are some problems: this packaging uses upstream source code directly
> > from from Git repository, not the tarball upstream released on https://
> > pagures.io.
>
> Hi,
> I import
On വ്യാഴം 18 മെയ് 2017 09:31 രാവിലെ, SJ Zhu wrote:
> I think we need to separate it, since I don't want this python package
> to depend on ruby(bring by ruby-cal-heatmap-rails)
yes, I will work on it. I already started working on at.js
(jquery.atwho.js)
> emoji/jquery.textcomplete-1.7.1.js
>
On Thu, May 18, 2017 at 11:59:36AM +0800, Boyuan Yang wrote:
> There are some problems: this packaging uses upstream source code directly
> from from Git repository, not the tarball upstream released on https://
> pagures.io.
>
Hi,
I import the source by `git archvie` and remove the minified
在 2017年5月18日星期四 +08 上午2:43:33，Shengjing Zhu 写道：
> Hi,
>
> I tried to build this package and fix the tests errors.
> My work is on:
> https://pagure.io/fork/zhsj/pagure/blob/debian/f/debian
>
> Now, it can build 2.15 successfully.
> There still needs three patches. one of them is applied
> in
On Thu, May 18, 2017 at 08:49:58AM +0530, Pirate Praveen wrote:
> > The remain work is to deal with the JS libraries,
> > some are still not in Debian:
> > * jdenticon.js
> > * cal-heatmap
>
> There is ruby-cal-heatmap, which I can split or package it separately.
I think we need to separate it,
On വ്യാഴം 18 മെയ് 2017 12:13 രാവിലെ, Shengjing Zhu wrote:
> Hi,
>
> I tried to build this package and fix the tests errors.
> My work is on:
> https://pagure.io/fork/zhsj/pagure/blob/debian/f/debian
>
> Now, it can build 2.15 successfully.
This is excellent!
> There still needs three patches.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I tried to build this package and fix the tests errors.
My work is on:
https://pagure.io/fork/zhsj/pagure/blob/debian/f/debian
Now, it can build 2.15 successfully.
There still needs three patches. one of them is applied
in trunk.
The remain
在 2017年5月17日星期三 +08 下午6:43:24，Boyuan Yang 写道：
> I made an (really) experimental packaging branch ("dev") based on previous
> v2.6 packaing on Alioth [1], on which developers can run debuild -b
> *outside* chroot and see the test results. There are 10 errors when using
> dh_auto_test and I believe
Okay, now with src tree based on 2.15 and various patches proposed upstream,
I am able to pass all tests with *manual* installing (setup.py build; setup.py
install) on my Debian Testing. That marks the elimination of compatibility
problem of pagure to Debian 9 (and similarly Debian Unstable).
I
在 2017年5月17日星期三 +08 上午9:18:42，Ben Finney 写道：
> On 16-May-2017, Boyuan Yang wrote:
> > * Every version needs py-bcrypt, which exists in fedora but long
> > superceded by python-bcrypt.
> >
> > Patches in pagure source code available.
>
> Do you mean that the Debian packaging could just take those
On 16-May-2017, Boyuan Yang wrote:
> I would like to summerize problems found when packaging pagure in
> May 2017.
This is a useful list of issues!
> * Every version needs py-bcrypt, which exists in fedora but long
> superceded by python-bcrypt.
>
> Patches in pagure source code available.
Do
15 matches
Mail list logo
