Debian Bug report logs - #829046
ITP: pagure -- A git centered forge

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Sergio Durigan Junior <sergiodj@sergiodj.net>

To: submit@bugs.debian.org

Subject: ITP: pagure -- A git centered forge

Date: Wed, 29 Jun 2016 21:10:21 -0400

[Message part 1 (text/plain, inline)]

Package: wnpp
Severity: wishlist
Owner: Sergio Durigan Junior <sergiodj@sergiodj.net>

* Package name    : pagure
  Version         : 2.2.1
  Upstream Author : Pierre-Yves Chibon <pingou@pingoured.fr>
* URL             : https://pagure.io/pagure
* License         : GPL-2
  Programming Lang: Python
  Description     : A git centered forge

  Pagure is a git-centered forge, python based using pygit2.

  With pagure you can host your project with its documentation, let your
  users report issues or request enhancements using the ticketing system
  and build your community of contributors by allowing them to fork your
  projects and contribute to it via the now-popular pull-request
  mechanism.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

[signature.asc (application/pgp-signature, inline)]

Message #12 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Alexandre Viau <aviau@debian.org>

To: sergiodj@sergiodj.net

Cc: 829046@bugs.debian.org

Subject: Status of pagure

Date: Fri, 29 Jul 2016 11:36:19 -0400

[Message part 1 (text/plain, inline)]

Hello,

What is the status of Pagure packaging, and how can I help?

Do you have a repository where you have started to work on the packaging?

Did you compile a list of dependencies, especially unavailable
dependencies? If yes, can you post it here so that we can start filing ITPs?

I intend to contribute to this.

Cheers,

-- 
Alexandre Viau
aviau@debian.org

[signature.asc (application/pgp-signature, attachment)]

Message #17 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Sergio Durigan Junior <sergiodj@sergiodj.net>

To: Alexandre Viau <aviau@debian.org>

Cc: 829046@bugs.debian.org

Subject: Re: Status of pagure

Date: Fri, 29 Jul 2016 11:42:05 -0400

[Message part 1 (text/plain, inline)]

On Friday, July 29 2016, Alexandre Viau wrote:

> Hello,

Hi there,

> What is the status of Pagure packaging, and how can I help?

I'm packaging it.  I'll be unavailable during this weekend, but I intend
to get back to work on Tuesday.

> Do you have a repository where you have started to work on the packaging?

Not yet; everything is on my machine.  But I will create a temporary
repository for packaging; then I can let you know.

> Did you compile a list of dependencies, especially unavailable
> dependencies? If yes, can you post it here so that we can start filing ITPs?

I already filed ITPs and took care of all dependencies listed on the
requirements.txt file, so we should be good on that.

> I intend to contribute to this.

Thanks for the help!  I'll send you an e-mail as soon as I set up a
repository.

Cheers,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

[signature.asc (application/pgp-signature, inline)]

Message #22 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Rahulkrishnan R A <rahulkrishnanfs@gmail.com>

To: 829046@bugs.debian.org

Subject: Interested in Pagure packaging

Date: Wed, 3 Aug 2016 10:20:02 +0530

[Message part 1 (text/plain, inline)]

Hi Sergio,

I would like to contribute to Pagure packaging.
Could you please let me know the status?

Regards,

Rahulkrishnan R A

[Message part 2 (text/html, inline)]

Message #27 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Ben Finney <ben+debian@benfinney.id.au>

To: Sergio Durigan Junior <sergiodj@sergiodj.net>, 829046@bugs.debian.org

Subject: Re: Bug#829046: Status of pagure

Date: Sun, 7 Aug 2016 20:53:17 +1000

[Message part 1 (text/plain, inline)]

On 29-Jul-2016, Sergio Durigan Junior wrote:

> Thanks for the help! I'll send you an e-mail as soon as I set up a
> repository.

I would also like to be able to contribute to maintenance of Pagure in
Debian.

Can you post an update to this bug report for how volunteers can help:
repository (at Alioth?), discussion mailing list, etc.

-- 
 \       “First things first, but not necessarily in that order.” —The |
  `\                                              Doctor, _Doctor Who_ |
_o__)                                                                  |
Ben Finney <ben@benfinney.id.au>

[signature.asc (application/pgp-signature, inline)]

Message #32 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Sergio Durigan Junior <sergiodj@sergiodj.net>

To: Ben Finney <ben+debian@benfinney.id.au>

Cc: 829046@bugs.debian.org

Subject: Re: Bug#829046: Status of pagure

Date: Sun, 07 Aug 2016 11:31:20 -0400

[Message part 1 (text/plain, inline)]

On Sunday, August 07 2016, Ben Finney wrote:

> On 29-Jul-2016, Sergio Durigan Junior wrote:
>
>> Thanks for the help! I'll send you an e-mail as soon as I set up a
>> repository.
>
> I would also like to be able to contribute to maintenance of Pagure in
> Debian.
>
> Can you post an update to this bug report for how volunteers can help:
> repository (at Alioth?), discussion mailing list, etc.

Thanks for wanting to contribute.

Yesterday I've created a repository at alioth (collab-maint/pagure), but
it's still empty.  I should push my changes later today.

As for a mailing list, I haven't created anything.  So far, we're using
this bug to coordinate the collaboration.  But I can request the
creation of a group on alioth when the package is accepted.

I'll let you know when I push the code today.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

[signature.asc (application/pgp-signature, inline)]

Message #37 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Sergio Durigan Junior <sergiodj@sergiodj.net>

To: Ben Finney <ben+debian@benfinney.id.au>, Alexandre Viau <aviau@debian.org>

Cc: 829046@bugs.debian.org

Subject: Re: Bug#829046: Status of pagure

Date: Mon, 08 Aug 2016 19:46:33 -0400

[Message part 1 (text/plain, inline)]

On Sunday, August 07 2016, Ben Finney wrote:

> On 29-Jul-2016, Sergio Durigan Junior wrote:
>
>> Thanks for the help! I'll send you an e-mail as soon as I set up a
>> repository.
>
> I would also like to be able to contribute to maintenance of Pagure in
> Debian.
>
> Can you post an update to this bug report for how volunteers can help:
> repository (at Alioth?), discussion mailing list, etc.

OK, so here's a more detailed update.

I've advanced quite a bit in the packaging, but there are still some
things to do.

I'm using a temporary repository to push what I've done so far; it's
good because I can overwrite history if needed.  The URL is:

  <http://git.sergiodj.net/?p=debian/pagure.git;a=summary>

Eventually I'll move everything to collab-maint/pagure, which should be
the official repository anyway.

All the Python dependencies have finally been packaged, which is good
because I can fully build the package now.  However, there are still
some JavaScript libraries that are (a) not being shipped on Debian, and
(b) bundled in their minified version inside pagure.  This is bad, so my
next task is to package those libraries for Debian.  You can take a look
at them by going to the pagure/static directory on the source tree.

I decided to follow what Fedora does and split the package into several
subpackages.  The first one, pagure, should contain the core
functionality and work out-of-the-box.  Then, the user will also have
the possibility to install:

 - pagure-milters, which takes care of allowing users to comment on
   tickets/pull-requests by e-mail (instead of going to the web
   interface).  This package in specific also has a "problem": it
   depends on postfix to work properly, which is not good because Debian
   ships exim4 as the default MTA.  I've also been investigating how to
   use milters with exim4, and I *may* have a solution.

 - pagure-ev-server, which allows live refreshing of a page when someone
   is viewing it.

 - pagure-webhook-server, which sends notifications to third-party
   services (like fedmsg) using POST http reqs.

There's also the pagure-doc package.

I ran the full testsuite and found a few errors on Debian.  I'm in
constant communication with upstream, so they are aware and I should
send some patches in the next days.

I still have this TODO list:

 - Package missing JS libraries

 - Send patch upstream to use python-bcrypt instead of py-bcrypt to hash
   passwords

 - Take care of d/copyright

 - Correctly fill d/pagure-doc.doc-base

 - Review the *.init scripts and make sure they work

 - Review the *.postinst scripts and make sure they work

 - Write *.postrm scripts

 - Decide whether to run pagure-milters as user/group postfix.  Maybe
   decide that based on what the user is using as MTA, and change it
   accordingly on pagure-milters.postinst.  Same applies for
   pagure-milters.tmpfile.

 - Maybe include more systemd security features on *.service files.

 - Fix some lintian warnings/errors that I've seen

Well, that's it.  I think I should be able to finish everything by the
end of the week, and then move to the sponsorship phase :-).

Cheers,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

[signature.asc (application/pgp-signature, inline)]

Message #42 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Alexander Wirt <formorer@debian.org>

To: Sergio Durigan Junior <sergiodj@sergiodj.net>, 829046@bugs.debian.org

Subject: Re: Bug#829046: Status of pagure

Date: Thu, 1 Sep 2016 22:39:27 +0200

[Message part 1 (text/plain, inline)]

On Mon, 08 Aug 2016, Sergio Durigan Junior wrote:

Hi,
*snip*
> Well, that's it.  I think I should be able to finish everything by the
> end of the week, and then move to the sponsorship phase :-).
Any updates on that package? 

Alex 

[signature.asc (application/pgp-signature, inline)]

Message #47 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Sergio Durigan Junior <sergiodj@sergiodj.net>

To: Alexander Wirt <formorer@debian.org>

Cc: 829046@bugs.debian.org

Subject: Re: Bug#829046: Status of pagure

Date: Thu, 01 Sep 2016 17:02:48 -0400

[Message part 1 (text/plain, inline)]

On Thursday, September 01 2016, Alexander Wirt wrote:

> On Mon, 08 Aug 2016, Sergio Durigan Junior wrote:
>
> Hi,
> *snip*
>> Well, that's it.  I think I should be able to finish everything by the
>> end of the week, and then move to the sponsorship phase :-).
> Any updates on that package? 

Yes.

I spent a lot of time packaging some JavaScript dependencies, but
unfortunately I won't be able to package them all.  They are *really* a
hassle...

Anyway, I talked to Alexandre Viau (aviau) about this and he assured me
that I could bundle the non-minified versions of JS libraries needed by
the package without problems, because ftp-master is OK with this.

Having said that, I am now working on make pagure use the non-minified
JS libs (I've already proposed a patch upstream for this, which is being
discussed), and on finishing the other bits of the packaging.

I learned a valuable lesson: I will not say "I should be able to finish
everything by XYZ date" anymore :-).  I can say, however, that the
package is in a good shape and I consider it very close to being
finished.

As always, you can check the status of my work here:

  http://git.sergiodj.net/?p=debian/pagure.git;a=summary

I try to keep this repo relatively up-to-date.

So yeah, in a nutshell, here's what's missing:

  - Bundle the non-minified versions of the necessary JS libs (note that
    most of the libs *are* on Debian)

  - Create the necessary symlinks for the libs that are already on
    Debian

  - Install the conffiles, helper scripts and other stuff (see Fedora
    package), probably on /usr/share/pagure

  - Write documentation about configuring pagure on Apache (at least)

  - Write documentation about configuring pagure with postfix (see
    upstream docs; maybe just refer to them)

  - Test installation

Alexandre Viau told me he'd be glad to sponsor this package for me, so
that's it.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

[signature.asc (application/pgp-signature, inline)]

Message #52 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Ben Finney <bignose@debian.org>

To: Sergio Durigan Junior <sergiodj@sergiodj.net>, 829046@bugs.debian.org

Subject: Re: Bug#829046: Status of pagure

Date: Fri, 2 Sep 2016 07:15:23 +1000

[Message part 1 (text/plain, inline)]

On 01-Sep-2016, Sergio Durigan Junior wrote:

> I spent a lot of time packaging some JavaScript dependencies, but
> unfortunately I won't be able to package them all. They are *really*
> a hassle...

Can you please:

* Open a RFP bug report for each of the JavaScript libraries that are
  not in Debian, that are needed for Pagure.

* Set this bug report as blocked by all of those RFP bug reports.

I would like that Pagure not start in a bad way, with bundled
third-party code, if we can avoid it. I can respond to the RFP reports
you open.

Thank you for the update!

-- 
 \        “The restriction of knowledge to an elite group destroys the |
  `\                   spirit of society and leads to its intellectual |
_o__)                                impoverishment.” —Albert Einstein |
Ben Finney <bignose@debian.org>

[signature.asc (application/pgp-signature, inline)]

Message #57 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Sergio Durigan Junior <sergiodj@sergiodj.net>

To: Ben Finney <bignose@debian.org>

Cc: 829046@bugs.debian.org

Subject: Re: Bug#829046: Status of pagure

Date: Thu, 01 Sep 2016 17:28:51 -0400

[Message part 1 (text/plain, inline)]

On Thursday, September 01 2016, Ben Finney wrote:

> On 01-Sep-2016, Sergio Durigan Junior wrote:
>
>> I spent a lot of time packaging some JavaScript dependencies, but
>> unfortunately I won't be able to package them all. They are *really*
>> a hassle...
>
> Can you please:
>
> * Open a RFP bug report for each of the JavaScript libraries that are
>   not in Debian, that are needed for Pagure.
>
> * Set this bug report as blocked by all of those RFP bug reports.
>
> I would like that Pagure not start in a bad way, with bundled
> third-party code, if we can avoid it. I can respond to the RFP reports
> you open.

I can, but then my best estimate is that pagure will not be ready until
the freeze.  Actually, it may not be ready until next year, because, hm,
JS libraries are *really* nasty.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

[signature.asc (application/pgp-signature, inline)]

Message #62 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Alexander Wirt <formorer@debian.org>

To: Sergio Durigan Junior <sergiodj@sergiodj.net>

Cc: 829046@bugs.debian.org

Subject: Re: Bug#829046: Status of pagure

Date: Fri, 2 Sep 2016 09:27:52 +0200

[Message part 1 (text/plain, inline)]

On Thu, 01 Sep 2016, Sergio Durigan Junior wrote:

> On Thursday, September 01 2016, Alexander Wirt wrote:
> 
> > On Mon, 08 Aug 2016, Sergio Durigan Junior wrote:
> >
> > Hi,
> > *snip*
> >> Well, that's it.  I think I should be able to finish everything by the
> >> end of the week, and then move to the sponsorship phase :-).
> > Any updates on that package? 
> 
> Yes.
> 
> I spent a lot of time packaging some JavaScript dependencies, but
> unfortunately I won't be able to package them all.  They are *really* a
> hassle...
> 
> Anyway, I talked to Alexandre Viau (aviau) about this and he assured me
> that I could bundle the non-minified versions of JS libraries needed by
> the package without problems, because ftp-master is OK with this.
Yeah, thats no problem as long as the source (non-monified) is available. 
> 
> Having said that, I am now working on make pagure use the non-minified
> JS libs (I've already proposed a patch upstream for this, which is being
> discussed), and on finishing the other bits of the packaging.
you don't have to, include the non-minified versions and minify them in the
buildprocess and use them afterwards. 
> 
> I learned a valuable lesson: I will not say "I should be able to finish
> everything by XYZ date" anymore :-).  I can say, however, that the
> package is in a good shape and I consider it very close to being
> finished.
:)
> 
> As always, you can check the status of my work here:
> 
>   http://git.sergiodj.net/?p=debian/pagure.git;a=summary
> 
> I try to keep this repo relatively up-to-date.
> 
> So yeah, in a nutshell, here's what's missing:
> 
>   - Bundle the non-minified versions of the necessary JS libs (note that
>     most of the libs *are* on Debian)
> 
>   - Create the necessary symlinks for the libs that are already on
>     Debian
> 
>   - Install the conffiles, helper scripts and other stuff (see Fedora
>     package), probably on /usr/share/pagure
> 
>   - Write documentation about configuring pagure on Apache (at least)
> 
>   - Write documentation about configuring pagure with postfix (see
>     upstream docs; maybe just refer to them)
> 
>   - Test installation
> 
> Alexandre Viau told me he'd be glad to sponsor this package for me, so
> that's it.
Thanks for your work! I am really looking forward in testing it for alioth. 


Alex

[signature.asc (application/pgp-signature, inline)]

Message #67 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Ben Finney <bignose@debian.org>

To: Sergio Durigan Junior <sergiodj@sergiodj.net>, 829046@bugs.debian.org

Subject: Re: Bug#829046: Status of pagure

Date: Fri, 2 Sep 2016 19:50:21 +1000

[Message part 1 (text/plain, inline)]

On 01-Sep-2016, Sergio Durigan Junior wrote:
> On Thursday, September 01 2016, Ben Finney wrote:
> 
> > Can you please:
> >
> > * Open a RFP bug report for each of the JavaScript libraries that
> >   are not in Debian, that are needed for Pagure.
> >
> > * Set this bug report as blocked by all of those RFP bug reports.
> 
> I can, but then my best estimate is that pagure will not be ready
> until the freeze. Actually, it may not be ready until next year,
> because, hm, JS libraries are *really* nasty.

I hear you :-)

None the less, that's the right way to do it for third-party bundled
code: we don't bundle into the dependent source package, but rather
package them separately in Debian.

I promise to respond quickly enough to decide which ones are actually
too difficult for the Stretch freeze; but let's start by assuming each
of them can be done.

-- 
 \      “He who allows oppression, shares the crime.” —Erasmus Darwin, |
  `\                                     grandfather of Charles Darwin |
_o__)                                                                  |
Ben Finney <bignose@debian.org>

[signature.asc (application/pgp-signature, inline)]

Message #72 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Sergio Durigan Junior <sergiodj@sergiodj.net>

To: Alexander Wirt <formorer@debian.org>

Cc: 829046@bugs.debian.org

Subject: Re: Bug#829046: Status of pagure

Date: Fri, 02 Sep 2016 12:58:17 -0400

[Message part 1 (text/plain, inline)]

On Friday, September 02 2016, Alexander Wirt wrote:

> On Thu, 01 Sep 2016, Sergio Durigan Junior wrote:
>
>> On Thursday, September 01 2016, Alexander Wirt wrote:
>> 
>> > On Mon, 08 Aug 2016, Sergio Durigan Junior wrote:
>> >
>> > Hi,
>> > *snip*
>> >> Well, that's it.  I think I should be able to finish everything by the
>> >> end of the week, and then move to the sponsorship phase :-).
>> > Any updates on that package? 
>> 
>> Yes.
>> 
>> I spent a lot of time packaging some JavaScript dependencies, but
>> unfortunately I won't be able to package them all.  They are *really* a
>> hassle...
>> 
>> Anyway, I talked to Alexandre Viau (aviau) about this and he assured me
>> that I could bundle the non-minified versions of JS libraries needed by
>> the package without problems, because ftp-master is OK with this.
> Yeah, thats no problem as long as the source (non-monified) is available. 

There's a parallel conversation going on with Ben Finney and he wants me
to create RFP's for each missing JS lib so that we can decide which ones
are worth putting more effort to package.  We should probably coordinate
all of these conversations so that everybody is happy.

>> Having said that, I am now working on make pagure use the non-minified
>> JS libs (I've already proposed a patch upstream for this, which is being
>> discussed), and on finishing the other bits of the packaging.
> you don't have to, include the non-minified versions and minify them in the
> buildprocess and use them afterwards. 

Right, that's what I'll do, *if* upstream takes too long to release a
new version :-).  If they release a new version with my patch applied,
then I can use it.

>> As always, you can check the status of my work here:
>> 
>>   http://git.sergiodj.net/?p=debian/pagure.git;a=summary
>> 
>> I try to keep this repo relatively up-to-date.
>> 
>> So yeah, in a nutshell, here's what's missing:
>> 
>>   - Bundle the non-minified versions of the necessary JS libs (note that
>>     most of the libs *are* on Debian)
>> 
>>   - Create the necessary symlinks for the libs that are already on
>>     Debian
>> 
>>   - Install the conffiles, helper scripts and other stuff (see Fedora
>>     package), probably on /usr/share/pagure
>> 
>>   - Write documentation about configuring pagure on Apache (at least)
>> 
>>   - Write documentation about configuring pagure with postfix (see
>>     upstream docs; maybe just refer to them)
>> 
>>   - Test installation
>> 
>> Alexandre Viau told me he'd be glad to sponsor this package for me, so
>> that's it.
> Thanks for your work! I am really looking forward in testing it for alioth. 

My pleasure, I'm really looking forward to helping with alioth as well.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

[signature.asc (application/pgp-signature, inline)]

Message #77 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Ben Finney <bignose@debian.org>

To: Sergio Durigan Junior <sergiodj@sergiodj.net>, 829046@bugs.debian.org

Subject: Re: Bug#829046: Status of pagure

Date: Sat, 3 Sep 2016 03:22:38 +1000

[Message part 1 (text/plain, inline)]

On 02-Sep-2016, Sergio Durigan Junior wrote:
> On Friday, September 02 2016, Alexander Wirt wrote:
> 
> > On Thu, 01 Sep 2016, Sergio Durigan Junior wrote:
> >> Anyway, I talked to Alexandre Viau (aviau) about this and he
> >> assured me that I could bundle the non-minified versions of JS
> >> libraries needed by the package without problems, because
> >> ftp-master is OK with this.
> > Yeah, thats no problem as long as the source (non-monified) is
> > available.

I think Alexander's statement is only true for what will satisfy legal
requirements for FTP master.

For satisfying Debian Policy, though, that is not sufficient. Rather:

    4.13. Convenience copies of code

    […]
    If the included code is already in the Debian archive in the form
    of a library, the Debian packaging should ensure that binary
    packages reference the libraries already in Debian and the
    convenience copy is not used. If the included code is not already
    in Debian, it should be packaged separately as a prerequisite if
    possible.

On that basis I am requesting you to report RFPs for each of the
bundled libraries, to package them as Policy §4.13 says.

-- 
 \       “Pray, v. To ask that the laws of the universe be annulled in |
  `\     behalf of a single petitioner confessedly unworthy.” —Ambrose |
_o__)                           Bierce, _The Devil's Dictionary_, 1906 |
Ben Finney <bignose@debian.org>

[signature.asc (application/pgp-signature, inline)]

Message #82 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Sergio Durigan Junior <sergiodj@sergiodj.net>

To: Ben Finney <bignose@debian.org>

Cc: 829046@bugs.debian.org

Subject: Re: Bug#829046: Status of pagure

Date: Fri, 02 Sep 2016 13:35:33 -0400

[Message part 1 (text/plain, inline)]

On Friday, September 02 2016, Ben Finney wrote:

> On 02-Sep-2016, Sergio Durigan Junior wrote:
>> On Friday, September 02 2016, Alexander Wirt wrote:
>> 
>> > On Thu, 01 Sep 2016, Sergio Durigan Junior wrote:
>> >> Anyway, I talked to Alexandre Viau (aviau) about this and he
>> >> assured me that I could bundle the non-minified versions of JS
>> >> libraries needed by the package without problems, because
>> >> ftp-master is OK with this.
>> > Yeah, thats no problem as long as the source (non-monified) is
>> > available.
>
> I think Alexander's statement is only true for what will satisfy legal
> requirements for FTP master.
>
> For satisfying Debian Policy, though, that is not sufficient. Rather:
>
>     4.13. Convenience copies of code
>
>     […]
>     If the included code is already in the Debian archive in the form
>     of a library, the Debian packaging should ensure that binary
>     packages reference the libraries already in Debian and the
>     convenience copy is not used. If the included code is not already
>     in Debian, it should be packaged separately as a prerequisite if
>     possible.
>
> On that basis I am requesting you to report RFPs for each of the
> bundled libraries, to package them as Policy §4.13 says.

I am filing the RFP's now.

Just to make things clear, I am totally in favour of packaging
everything we can.  To me, the "if possible" part of the paragraph you
posted is subjective and leaves things open for interpretation.

The real problem with the JS libs that are missing on Debian is their
dependency on Grunt.  To be fair, I recently packaged selectize.js
(which also depends on Grunt), and I spent a big time creating a
replacement for it using only GNU tools available on Debian, but I don't
feel like doing that for every other library.

Anyway, I just wanted to explain better why I think packaging the
missing JS libraries is going to be a huge hassle.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

[signature.asc (application/pgp-signature, inline)]

Message #89 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Ben Finney <bignose@debian.org>

To: Sergio Durigan Junior <sergiodj@sergiodj.net>

Cc: 829046@bugs.debian.org

Subject: Re: Bug#829046: Status of pagure

Date: Sun, 4 Sep 2016 18:05:01 +1000

[Message part 1 (text/plain, inline)]

On 02-Sep-2016, Sergio Durigan Junior wrote:

> The real problem with the JS libs that are missing on Debian is
> their dependency on Grunt.

This is a problem with many JavaScript packages, I agree. A related
problem is the common lack of any clear instruction for how the
package is meant to be built from its source.

> To be fair, I recently packaged selectize.js (which also depends on
> Grunt), and I spent a big time creating a replacement for it using
> only GNU tools available on Debian, but I don't feel like doing that
> for every other library.

Please join the discussion at the ‘pkg-javascript-devel’ forum
<URL:https://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2016-September/013682.html>
to join forces with others in tackling this problem.

-- 
 \         “Of all classes the rich are the most noticed and the least |
  `\      studied.” —John Kenneth Galbraith, _The Age of Uncertainty_, |
_o__)                                                             1977 |
Ben Finney <bignose@debian.org>

[signature.asc (application/pgp-signature, inline)]

Message #94 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Sergio Durigan Junior <sergiodj@sergiodj.net>

To: Ben Finney <bignose@debian.org>

Cc: 829046@bugs.debian.org

Subject: Re: Bug#829046: Status of pagure

Date: Mon, 05 Sep 2016 14:45:10 -0400

[Message part 1 (text/plain, inline)]

On Sunday, September 04 2016, Ben Finney wrote:

>> To be fair, I recently packaged selectize.js (which also depends on
>> Grunt), and I spent a big time creating a replacement for it using
>> only GNU tools available on Debian, but I don't feel like doing that
>> for every other library.
>
> Please join the discussion at the ‘pkg-javascript-devel’ forum
> <URL:https://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2016-September/013682.html>
> to join forces with others in tackling this problem.

To be honest, I do not have time nor interest now to spend my energy
solving this JS problem.  My total focus now is getting pagure ready for
Debian in the best way I can.  Also, from my recent experience packaging
some JS libs, I fear that the building issue will not be solved in the
near future.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

[signature.asc (application/pgp-signature, inline)]

Message #99 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Pirate Praveen <praveen@debian.org>

To: 829046@bugs.debian.org

Subject: Re: Bug#829046: Status of pagure

Date: Fri, 21 Oct 2016 16:10:48 +0530

[Message part 1 (text/plain, inline)]

On Mon, 05 Sep 2016 14:45:10 -0400 Sergio Durigan Junior
<sergiodj@sergiodj.net> wrote:
> To be honest, I do not have time nor interest now to spend my energy
> solving this JS problem.  My total focus now is getting pagure ready for
> Debian in the best way I can.  Also, from my recent experience packaging
> some JS libs, I fear that the building issue will not be solved in the
> near future.

We are crowd funding to package grunt - http://igg.me/at/debian-browserify

But right now we can add them to contrib and upload pagure to contrib.
Once we complete grunt, we can move them to main.

[signature.asc (application/pgp-signature, attachment)]

Message #104 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Pirate Praveen <praveen@debian.org>

To: 829046@bugs.debian.org, Sergio Durigan Junior <sergiodj@sergiodj.net>

Subject: Re: Bug#829046: Status of pagure

Date: Sat, 12 Nov 2016 22:50:18 +0530

[Message part 1 (text/plain, inline)]

On Fri, 21 Oct 2016 16:10:48 +0530 Pirate Praveen <praveen@debian.org>
wrote:
> On Mon, 05 Sep 2016 14:45:10 -0400 Sergio Durigan Junior
> <sergiodj@sergiodj.net> wrote:
> > To be honest, I do not have time nor interest now to spend my energy
> > solving this JS problem.  My total focus now is getting pagure ready for
> > Debian in the best way I can.  Also, from my recent experience packaging
> > some JS libs, I fear that the building issue will not be solved in the
> > near future.
> 
> We are crowd funding to package grunt - http://igg.me/at/debian-browserify
Sergio,

grunt is now in debian. Can you try to modify grunt so that we can use
the packaged grunt? see
http://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2016-November/015240.html
for details about the problem.

[signature.asc (application/pgp-signature, attachment)]

Message #109 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Pirate Praveen <praveen@debian.org>

To: 829046@bugs.debian.org, Sergio Durigan Junior <sergiodj@sergiodj.net>

Subject: Re: Bug#829046: Status of pagure

Date: Wed, 23 Nov 2016 19:14:36 +0530

[Message part 1 (text/plain, inline)]

On Sat, 12 Nov 2016 22:50:18 +0530 Pirate Praveen <praveen@debian.org>
wrote:
> grunt is now in debian. Can you try to modify grunt so that we can use
> the packaged grunt?

grunt issue is fixed and libjs-jquery-textcomplete is now in main,
though at.js needs gulp :(

[signature.asc (application/pgp-signature, attachment)]

Message #114 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Ben Finney <bignose@debian.org>

To: Sergio Durigan Junior <sergiodj@sergiodj.net>, 829046@bugs.debian.org

Subject: Bug#829046: pagure dependencies (JavaScript libraries) packaged

Date: Mon, 12 Dec 2016 06:21:35 +1100

[Message part 1 (text/plain, inline)]

On 05-Sep-2016, Sergio Durigan Junior wrote:

> […] from my recent experience packaging some JS libs, I fear that
> the building issue will not be solved in the near future.

I have packaged the two remaining JavaScript libraries that were
blocking this RFP, ‘jquery-at.js’ and ‘jquery-caret.js’.

I don't understand Grunt or Gulp, but from what I could tell those
were just being used for typical build tasks. I do understand Make, so
I reproduced the build tasks in Debian's ‘rules’ makefile :-)

Please try the library packages (they are currently in ‘experimental’)
and let me know whether they are sufficient to allow Pagure packaging
to continue.

-- 
 \        “I knew it was a shocking thing to say, but … no-one has the |
  `\        right to spend their life without being offended.” —Philip |
_o__)                                              Pullman, 2010-03-28 |
Ben Finney <bignose@debian.org>

[signature.asc (application/pgp-signature, inline)]

Message #124 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Pirate Praveen <praveen@debian.org>

To: 829046@bugs.debian.org, Ben Finney <bignose@debian.org>, Sergio Durigan Junior <sergiodj@sergiodj.net>

Subject: Re: Bug#829046: pagure dependencies (JavaScript libraries) packaged

Date: Mon, 19 Dec 2016 16:35:07 +0530

[Message part 1 (text/plain, inline)]

On Mon, 12 Dec 2016 06:21:35 +1100 Ben Finney <bignose@debian.org> wrote:
> I don't understand Grunt or Gulp, but from what I could tell those
> were just being used for typical build tasks. I do understand Make, so
> I reproduced the build tasks in Debian's ‘rules’ makefile :-)

Btw I just uploaded gulp also to debian (its in NEW). Well, the upstream
provides a Gruntfile.js or Gulpfile.js, so usually you need to only
remove hinting and styling tasks (jshint, jscs etc). For grunt, you also
need to provide /usr/lib/nodejs as path for tasks (if someone helps make
that default for grunt, we can remove that step as well).

> Please try the library packages (they are currently in ‘experimental’)
> and let me know whether they are sufficient to allow Pagure packaging
> to continue.

Since Sergio has been silent for sometime and freeze is approaching fast
(we have only time till Dec 25, less than a week to get pagure into
stretch), I will copy his repo to collab-maint and will try to upload it
to experimental.

[signature.asc (application/pgp-signature, attachment)]

Message #129 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Pirate Praveen <praveen@debian.org>

To: 829046@bugs.debian.org, Ben Finney <bignose@debian.org>, Sergio Durigan Junior <sergiodj@sergiodj.net>, Alexandre Viau <aviau@debian.org>, Rahulkrishnan R A <rahulkrishnanfs@gmail.com>, Alexander Wirt <formorer@debian.org>

Subject: Re: Bug#829046: pagure dependencies (JavaScript libraries) packaged

Date: Mon, 19 Dec 2016 17:55:21 +0530

[Message part 1 (text/plain, inline)]

[ccing everyone who showed interest]

On Mon, 19 Dec 2016 16:35:07 +0530 Pirate Praveen <praveen@debian.org>
wrote:
> Since Sergio has been silent for sometime and freeze is approaching fast
> (we have only time till Dec 25, less than a week to get pagure into
> stretch), I will copy his repo to collab-maint and will try to upload it
> to experimental.
> 

Its now pushed to collab-maint. Since all dependencies are now packaged,
we should test it well and try to get it into stretch by Dec 25.

When I try to build the package, I get the following error

File "/usr/lib/python2.7/dist-packages/bleach/__init__.py", line 8, in
<module>
    from html5lib.sanitizer import HTMLSanitizer
ImportError: No module named sanitizer

apt-file-list python-html5lib shows

python-html5lib:
/usr/lib/python2.7/dist-packages/html5lib/filters/sanitizer.py

So I think we need to patch python-bleach.

[signature.asc (application/pgp-signature, attachment)]

Message #134 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Pirate Praveen <praveen@debian.org>

To: Pirate Praveen <praveen@debian.org>, 829046@bugs.debian.org, Ben Finney <bignose@debian.org>, Sergio Durigan Junior <sergiodj@sergiodj.net>, Alexandre Viau <aviau@debian.org>, Rahulkrishnan R A <rahulkrishnanfs@gmail.com>, Alexander Wirt <formorer@debian.org>

Subject: Re: Bug#829046: pagure dependencies (JavaScript libraries) packaged

Date: Mon, 19 Dec 2016 19:25:11 +0530

[Message part 1 (text/plain, inline)]

Control: block -1 by 844943

On തിങ്കള്‍ 19 ഡിസംബര്‍ 2016 05:55 വൈകു, Pirate Praveen wrote:
> When I try to build the package, I get the following error
> 
> File "/usr/lib/python2.7/dist-packages/bleach/__init__.py", line 8, in
> <module>
>     from html5lib.sanitizer import HTMLSanitizer
> ImportError: No module named sanitizer
> 
> apt-file-list python-html5lib shows
> 
> python-html5lib:
> /usr/lib/python2.7/dist-packages/html5lib/filters/sanitizer.py
> 
> So I think we need to patch python-bleach.
> 

This is already reported as #844943

[signature.asc (application/pgp-signature, attachment)]

Message #141 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Sergio Durigan Junior <sergiodj@sergiodj.net>

To: Pirate Praveen <praveen@debian.org>

Cc: 829046@bugs.debian.org, Ben Finney <bignose@debian.org>

Subject: Re: Bug#829046: pagure dependencies (JavaScript libraries) packaged

Date: Mon, 19 Dec 2016 12:37:17 -0500

[Message part 1 (text/plain, inline)]

On Monday, December 19 2016, Pirate Praveen wrote:

> On Mon, 12 Dec 2016 06:21:35 +1100 Ben Finney <bignose@debian.org> wrote:
>> I don't understand Grunt or Gulp, but from what I could tell those
>> were just being used for typical build tasks. I do understand Make, so
>> I reproduced the build tasks in Debian's ‘rules’ makefile :-)
>
> Btw I just uploaded gulp also to debian (its in NEW). Well, the upstream
> provides a Gruntfile.js or Gulpfile.js, so usually you need to only
> remove hinting and styling tasks (jshint, jscs etc). For grunt, you also
> need to provide /usr/lib/nodejs as path for tasks (if someone helps make
> that default for grunt, we can remove that step as well).
>
>> Please try the library packages (they are currently in ‘experimental’)
>> and let me know whether they are sufficient to allow Pagure packaging
>> to continue.
>
> Since Sergio has been silent for sometime and freeze is approaching fast
> (we have only time till Dec 25, less than a week to get pagure into
> stretch), I will copy his repo to collab-maint and will try to upload it
> to experimental.

Hey guys,

First of all, thank you very much for all the work you have done these
last weeks.

I am sorry I was absent and did to participate; I have been very busy
with work and unable to concentrate on anything else.

Things are starting to calm down, and I intend to get back to packaging
pagure.  My intention is to get the latest version imported onto my
repository and work on it.  However, I don't think it will be possible
to finish everything by Dec 25th.  I know it would be good to get pagure
on stretch, but IMHO it is better to make sure everything is working
fine first.

I'll see if I can continue my work tonight and let you know of any
progress.

Cheers,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

[signature.asc (application/pgp-signature, inline)]

Message #146 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Pirate Praveen <praveen@debian.org>

To: Sergio Durigan Junior <sergiodj@sergiodj.net>

Cc: 829046@bugs.debian.org, Ben Finney <bignose@debian.org>

Subject: Re: Bug#829046: pagure dependencies (JavaScript libraries) packaged

Date: Tue, 20 Dec 2016 10:48:12 +0530

[Message part 1 (text/plain, inline)]

On തിങ്കള്‍ 19 ഡിസംബര്‍ 2016 11:07 വൈകു, Sergio Durigan Junior wrote:
> Things are starting to calm down, and I intend to get back to packaging
> pagure.  My intention is to get the latest version imported onto my
> repository and work on it.  However, I don't think it will be possible
> to finish everything by Dec 25th.  I know it would be good to get pagure
> on stretch, but IMHO it is better to make sure everything is working
> fine first.

Dec 25 is the last day of uploading to sid so it can migrate to stretch
before freeze. We have time till stretch release (at least 2 months
more) to fix bugs. We should try our best to have it in stretch and if
not have it in stretch-backports.

[signature.asc (application/pgp-signature, attachment)]

Message #151 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Alexandre Viau <aviau@debian.org>

To: Sergio Durigan Junior <sergiodj@sergiodj.net>

Cc: Pirate Praveen <praveen@debian.org>, 829046@bugs.debian.org

Subject: Any update on pagure?

Date: Tue, 20 Dec 2016 21:46:48 -0500

[Message part 1 (text/plain, inline)]

Hello,

> I'll see if I can continue my work tonight and let you know of any
> progress.

Any update on that?

Should someone take over?

As Praveen said, we just need a "good" package to be uploaded before the
25th. It can have bugs.

-- 
Alexandre Viau
aviau@debian.org

[signature.asc (application/pgp-signature, attachment)]

Message #156 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Sergio Durigan Junior <sergiodj@sergiodj.net>

To: Alexandre Viau <aviau@debian.org>

Cc: 829046@bugs.debian.org, Pirate Praveen <praveen@debian.org>

Subject: Re: Bug#829046: Any update on pagure?

Date: Wed, 21 Dec 2016 01:22:18 -0500

[Message part 1 (text/plain, inline)]

On Tuesday, December 20 2016, Alexandre Viau wrote:

> Hello,

Hey, Alexandre,

>> I'll see if I can continue my work tonight and let you know of any
>> progress.
>
> Any update on that?

I didn't have time to work on pagure that night.  I'll work on it
tomorrow (Wednesday).

> Should someone take over?
>
> As Praveen said, we just need a "good" package to be uploaded before the
> 25th. It can have bugs.

Right.  I'll just finish what I have here and propose it for upload,
then.  The package will have some rough edges here and there but it
should be usable.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

[signature.asc (application/pgp-signature, inline)]

Message #161 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Sergio Durigan Junior <sergiodj@sergiodj.net>

To: Pirate Praveen <praveen@debian.org>

Cc: 829046@bugs.debian.org, Ben Finney <bignose@debian.org>, aviau@debian.org

Subject: Re: Bug#829046: pagure dependencies (JavaScript libraries) packaged

Date: Sat, 24 Dec 2016 00:24:16 -0500

[Message part 1 (text/plain, inline)]

On Tuesday, December 20 2016, Pirate Praveen wrote:

> On തിങ്കള്‍ 19 ഡിസംബര്‍ 2016 11:07 വൈകു, Sergio Durigan Junior wrote:
>> Things are starting to calm down, and I intend to get back to packaging
>> pagure.  My intention is to get the latest version imported onto my
>> repository and work on it.  However, I don't think it will be possible
>> to finish everything by Dec 25th.  I know it would be good to get pagure
>> on stretch, but IMHO it is better to make sure everything is working
>> fine first.
>
> Dec 25 is the last day of uploading to sid so it can migrate to stretch
> before freeze. We have time till stretch release (at least 2 months
> more) to fix bugs. We should try our best to have it in stretch and if
> not have it in stretch-backports.

Hm, guys, I am not sure I'll be able to get this ready until the 25th.
There are still issues with the package and well, tomorrow is christmas
eve, so...

I'll keep trying to get the package in a good shape.  I think it is, but
as Praveen mentioned there is still at least one issue when building
it.  Also, I'm not even considering updating the package to the latest
version (2.10.1) now, because that will certainly introduce a lot of new
issues.

IMO, if you have time, here's what I would do:

- If you manage to get the building issue sorted out, and if there are
  no other critical issues, then I think the package is "good enough"
  (for a very relaxed definition of "good") to be put on stretch.  As
  Praveen said, we will have 2 months to fix remaining bugs.

- If it is not possible to fix the critical bugs, then I'd suggest going
  with the strectch-backports alternative.  It's not a bad option IMHO,
  and gives us even more time to really fix the underlying problems.

Something really concerning me is the fact that pagure keeps adding JS
dependencies that are either not packaged on Debian, or that are
packaged as part of another, bigger package (usually some big ruby
extension or so).  And even in the second case, when the file is already
in Debian, it is not really following our guidelines; for example, the
.js and .min.js files are being shipped without being built from
source.

Anyway, some food for thought.  I'll keep you posted if I manage to make
things work on my side.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

[signature.asc (application/pgp-signature, inline)]

Message #166 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Pirate Praveen <praveen@onenetbeyond.org>

To: Sergio Durigan Junior <sergiodj@sergiodj.net>

Cc: 829046@bugs.debian.org, Ben Finney <bignose@debian.org>, aviau@debian.org

Subject: Re: Bug#829046: pagure dependencies (JavaScript libraries) packaged

Date: Sat, 24 Dec 2016 11:15:47 +0530

[Message part 1 (text/plain, inline)]

On ശനി 24 ഡിസംബര്‍ 2016 10:54 രാവിലെ, Sergio Durigan Junior wrote:
> IMO, if you have time, here's what I would do:
> 
> - If you manage to get the building issue sorted out, and if there are
>   no other critical issues, then I think the package is "good enough"
>   (for a very relaxed definition of "good") to be put on stretch.  As
>   Praveen said, we will have 2 months to fix remaining bugs.
> 
> - If it is not possible to fix the critical bugs, then I'd suggest going
>   with the strectch-backports alternative.  It's not a bad option IMHO,
>   and gives us even more time to really fix the underlying problems.

Its too close to Dec 25, lets take the backports path.

> Something really concerning me is the fact that pagure keeps adding JS
> dependencies that are either not packaged on Debian, or that are
> packaged as part of another, bigger package (usually some big ruby
> extension or so).  And even in the second case, when the file is already
> in Debian, it is not really following our guidelines; for example, the
> .js and .min.js files are being shipped without being built from
> source.

We now have grunt and gulp in main (rollup and babel are on their way),
so rebuilding them would be much easier than before (reimplementing the
build in rules).

The ruby ones are usually just wrappers for the js part. It would be
easy to separate them if needed. ruby packages can just add a symlink
instead of embedded copies when we package the js part separately.

[signature.asc (application/pgp-signature, attachment)]

Message #171 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Sergio Durigan Junior <sergiodj@sergiodj.net>

To: Pirate Praveen <praveen@onenetbeyond.org>

Cc: 829046@bugs.debian.org, Ben Finney <bignose@debian.org>, aviau@debian.org

Subject: Re: Bug#829046: pagure dependencies (JavaScript libraries) packaged

Date: Sat, 24 Dec 2016 01:07:41 -0500

[Message part 1 (text/plain, inline)]

On Saturday, December 24 2016, Pirate Praveen wrote:

> On ശനി 24 ഡിസംബര്‍ 2016 10:54 രാവിലെ, Sergio Durigan Junior wrote:
>> IMO, if you have time, here's what I would do:
>> 
>> - If you manage to get the building issue sorted out, and if there are
>>   no other critical issues, then I think the package is "good enough"
>>   (for a very relaxed definition of "good") to be put on stretch.  As
>>   Praveen said, we will have 2 months to fix remaining bugs.
>> 
>> - If it is not possible to fix the critical bugs, then I'd suggest going
>>   with the strectch-backports alternative.  It's not a bad option IMHO,
>>   and gives us even more time to really fix the underlying problems.
>
> Its too close to Dec 25, lets take the backports path.

Well, I've done some tests here and I think I have a package that
builds.  I've updated pagure to an intermediary version, 2.6, and the
package builds fine on pbuilder/cowbuilder using the latest unstable.
You can find it here:

  http://git.sergiodj.net/?p=debian/pagure-new.git;a=summary

Can you give it a try?  I think we can go with that (even for stretch),
if you are OK with it.  The package contains bundled JS libraries, and
minifies them during the build, so it's not perfect in this aspect.  But
we can fix this later, when we have more time.

>> Something really concerning me is the fact that pagure keeps adding JS
>> dependencies that are either not packaged on Debian, or that are
>> packaged as part of another, bigger package (usually some big ruby
>> extension or so).  And even in the second case, when the file is already
>> in Debian, it is not really following our guidelines; for example, the
>> .js and .min.js files are being shipped without being built from
>> source.
>
> We now have grunt and gulp in main (rollup and babel are on their way),
> so rebuilding them would be much easier than before (reimplementing the
> build in rules).
>
> The ruby ones are usually just wrappers for the js part. It would be
> easy to separate them if needed. ruby packages can just add a symlink
> instead of embedded copies when we package the js part separately.

Right, that's nice indeed, but it demands work anyway...  But it's
really good that grunt and gulp are now available.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

[signature.asc (application/pgp-signature, inline)]

Message #176 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Pirate Praveen <praveen@onenetbeyond.org>

To: 829046@bugs.debian.org, Sergio Durigan Junior <sergiodj@sergiodj.net>

Subject: Re: Bug#829046: pagure dependencies (JavaScript libraries) packaged

Date: Sat, 24 Dec 2016 12:23:52 +0530

[Message part 1 (text/plain, inline)]

On ശനി 24 ഡിസംബര്‍ 2016 11:37 രാവിലെ, Sergio Durigan Junior wrote:
> Well, I've done some tests here and I think I have a package that
> builds.  I've updated pagure to an intermediary version, 2.6, and the
> package builds fine on pbuilder/cowbuilder using the latest unstable.
> You can find it here:
> 
>   http://git.sergiodj.net/?p=debian/pagure-new.git;a=summary
> 
> Can you give it a try?  I think we can go with that (even for stretch),
> if you are OK with it.  The package contains bundled JS libraries, and
> minifies them during the build, so it's not perfect in this aspect.  But
> we can fix this later, when we have more time.

I tried to build, but debian directory is missing there. May be you
forgot to push new commits?

[signature.asc (application/pgp-signature, attachment)]

Message #181 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Pirate Praveen <praveen@onenetbeyond.org>

To: 829046@bugs.debian.org

Subject: Re: Bug#829046: pagure dependencies (JavaScript libraries) packaged

Date: Sat, 24 Dec 2016 12:25:51 +0530

[Message part 1 (text/plain, inline)]

On ശനി 24 ഡിസംബര്‍ 2016 11:37 രാവിലെ, Sergio Durigan Junior wrote:
> Right, that's nice indeed, but it demands work anyway...  But it's
> really good that grunt and gulp are now available.

Exploding dependencies in new releases is not pagure specific issue. Its
there for every web app, be it gitlab, diaspora or pagure. We have to
keep packaging new dependencies, I don't see another way around it.

[signature.asc (application/pgp-signature, attachment)]

Message #186 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Sergio Durigan Junior <sergiodj@sergiodj.net>

To: Pirate Praveen <praveen@onenetbeyond.org>

Cc: 829046@bugs.debian.org

Subject: Re: Bug#829046: pagure dependencies (JavaScript libraries) packaged

Date: Sat, 24 Dec 2016 08:56:08 -0500

[Message part 1 (text/plain, inline)]

On Saturday, December 24 2016, Pirate Praveen wrote:

> On ശനി 24 ഡിസംബര്‍ 2016 11:37 രാവിലെ, Sergio Durigan Junior wrote:
>> Well, I've done some tests here and I think I have a package that
>> builds.  I've updated pagure to an intermediary version, 2.6, and the
>> package builds fine on pbuilder/cowbuilder using the latest unstable.
>> You can find it here:
>> 
>>   http://git.sergiodj.net/?p=debian/pagure-new.git;a=summary
>> 
>> Can you give it a try?  I think we can go with that (even for stretch),
>> if you are OK with it.  The package contains bundled JS libraries, and
>> minifies them during the build, so it's not perfect in this aspect.  But
>> we can fix this later, when we have more time.
>
> I tried to build, but debian directory is missing there. May be you
> forgot to push new commits?

Yep, I forgot :-/.  Anyway, pushed now.  Sorry about that.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

[signature.asc (application/pgp-signature, inline)]

Message #191 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Pirate Praveen <praveen@onenetbeyond.org>

To: Sergio Durigan Junior <sergiodj@sergiodj.net>

Cc: 829046@bugs.debian.org

Subject: Re: Bug#829046: pagure dependencies (JavaScript libraries) packaged

Date: Sat, 24 Dec 2016 19:40:27 +0530

[Message part 1 (text/plain, inline)]

On ശനി 24 ഡിസംബര്‍ 2016 07:26 വൈകു, Sergio Durigan Junior wrote:
> Yep, I forgot :-/.  Anyway, pushed now.  Sorry about that.

I'm still getting the same error,

from html5lib.sanitizer import HTMLSanitizer
ImportError: No module named sanitizer

I don't see either python-bleach or python-html5lib is updated.

This bug is still open
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844943 May be you have
an older version of python-html5lib in your system. We have to fix this
bug to proceed further.

[signature.asc (application/pgp-signature, attachment)]

Message #196 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Sergio Durigan Junior <sergiodj@sergiodj.net>

To: Pirate Praveen <praveen@onenetbeyond.org>

Cc: 829046@bugs.debian.org

Subject: Re: Bug#829046: pagure dependencies (JavaScript libraries) packaged

Date: Sat, 24 Dec 2016 13:28:11 -0500

[Message part 1 (text/plain, inline)]

On Saturday, December 24 2016, Pirate Praveen wrote:

> On ശനി 24 ഡിസംബര്‍ 2016 07:26 വൈകു, Sergio Durigan Junior wrote:
>> Yep, I forgot :-/.  Anyway, pushed now.  Sorry about that.
>
> I'm still getting the same error,
>
> from html5lib.sanitizer import HTMLSanitizer
> ImportError: No module named sanitizer
>
> I don't see either python-bleach or python-html5lib is updated.
>
> This bug is still open
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844943 May be you have
> an older version of python-html5lib in your system. We have to fix this
> bug to proceed further.

Hm, strange.  I'm using pbuilder/cowdancer to build the package, so it
should catch this.  I'll look into it.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

[signature.asc (application/pgp-signature, inline)]

Message #201 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Pirate Praveen <praveen@onenetbeyond.org>

To: Sergio Durigan Junior <sergiodj@sergiodj.net>

Cc: 829046@bugs.debian.org

Subject: Re: Bug#829046: pagure dependencies (JavaScript libraries) packaged

Date: Sat, 24 Dec 2016 23:59:47 +0530

[Message part 1 (text/plain, inline)]

On ശനി 24 ഡിസംബര്‍ 2016 11:58 വൈകു, Sergio Durigan Junior wrote:
> Hm, strange.  I'm using pbuilder/cowdancer to build the package, so it
> should catch this.  I'll look into it.

Did you update pbuilder recently? You have to run 'pbuilder update' often.

[signature.asc (application/pgp-signature, attachment)]

Message #206 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Sergio Durigan Junior <sergiodj@sergiodj.net>

To: Pirate Praveen <praveen@onenetbeyond.org>

Cc: 829046@bugs.debian.org

Subject: Re: Bug#829046: pagure dependencies (JavaScript libraries) packaged

Date: Sat, 24 Dec 2016 13:31:29 -0500

[Message part 1 (text/plain, inline)]

On Saturday, December 24 2016, Pirate Praveen wrote:

> On ശനി 24 ഡിസംബര്‍ 2016 11:58 വൈകു, Sergio Durigan Junior wrote:
>> Hm, strange.  I'm using pbuilder/cowdancer to build the package, so it
>> should catch this.  I'll look into it.
>
> Did you update pbuilder recently? You have to run 'pbuilder update' often.

Yep, I did it before building pagure.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

[signature.asc (application/pgp-signature, inline)]

Message #211 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Pirate Praveen <praveen@onenetbeyond.org>

To: Sergio Durigan Junior <sergiodj@sergiodj.net>, 829046@bugs.debian.org, Alexandre Viau <aviau@debian.org>

Subject: Re: Bug#829046: pagure dependencies (JavaScript libraries) packaged

Date: Sun, 25 Dec 2016 00:08:19 +0530

[Message part 1 (text/plain, inline)]

On ഞായര്‍ 25 ഡിസംബര്‍ 2016 12:01 രാവിലെ, Sergio Durigan Junior wrote:
> Yep, I did it before building pagure.

It is failing here on sbuild as well.

aviau, can you try to build it?

[signature.asc (application/pgp-signature, attachment)]

Message #216 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Sergio Durigan Junior <sergiodj@sergiodj.net>

To: Pirate Praveen <praveen@onenetbeyond.org>

Cc: 829046@bugs.debian.org, Alexandre Viau <aviau@debian.org>

Subject: Re: Bug#829046: pagure dependencies (JavaScript libraries) packaged

Date: Sat, 24 Dec 2016 16:07:05 -0500

[Message part 1 (text/plain, inline)]

On Saturday, December 24 2016, Pirate Praveen wrote:

> On ഞായര്‍ 25 ഡിസംബര്‍ 2016 12:01 രാവിലെ, Sergio Durigan Junior wrote:
>> Yep, I did it before building pagure.
>
> It is failing here on sbuild as well.

OK, managed to reproduce it here.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

[signature.asc (application/pgp-signature, inline)]

Message #221 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Pirate Praveen <praveen@debian.org>

To: 829046@bugs.debian.org

Cc: Sergio Durigan Junior <sergiodj@sergiodj.net>

Subject: Re: Bug#829046: pagure dependencies (JavaScript libraries) packaged

Date: Thu, 16 Mar 2017 13:29:46 +0530

[Message part 1 (text/plain, inline)]

On Sat, 24 Dec 2016 16:07:05 -0500 Sergio Durigan Junior <sergiodj@sergiodj.net> wrote:
> OK, managed to reproduce it here.

Bleach issue is fixed now, but I get 5 failures and 3 errors.

Attaching log.

[Message part 2 (text/html, inline)]

[pagure-error.log (text/plain, attachment)]

Message #228 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Boyuan Yang <073plan@gmail.com>

To: Pirate Praveen <praveen@onenetbeyond.org>, Sergio Durigan Junior <sergiodj@sergiodj.net>

Cc: debian-devel <debian-devel@lists.debian.org>, 829046@bugs.debian.org

Subject: Re: Moving away from (unsupportable) FusionForge on Alioth?

Date: Sun, 14 May 2017 22:50:32 +0800

[Message part 1 (text/plain, inline)]

在 2017年5月14日星期日 CST 下午3:04:26，Pirate Praveen 写道：
> As far as I understand, the only thing that is blocking is non
> availability of pagure package.
> 
> So helping fix this would help move this forward (currently pagure tests
> are failing).
> 
> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829046
> 
> After we have the package, then DSA standard processes for new service
> would follow, I assume.

I'm a little bit confused. The bug forwarding address in #829046 points at 
http://git.sergiodj.net/, however I couldn't find packaging for pagure 
anywhere. Seems all deleted sometime before.

The repository on collab-maint stops at September 2016 and lacks the work 
around December 2016.

Could you tell me where can I find the proper packaging repository?

Thanks!

--
Boyuan Yang

[signature.asc (application/pgp-signature, inline)]

Message #233 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Pirate Praveen <praveen@onenetbeyond.org>

To: Boyuan Yang <073plan@gmail.com>, Sergio Durigan Junior <sergiodj@sergiodj.net>

Cc: debian-devel <debian-devel@lists.debian.org>, 829046@bugs.debian.org

Subject: Re: Moving away from (unsupportable) FusionForge on Alioth?

Date: Sun, 14 May 2017 21:23:22 +0530

[Message part 1 (text/plain, inline)]

On ഞായര്‍ 14 മെയ് 2017 08:20 വൈകു, Boyuan Yang wrote:
> I'm a little bit confused. The bug forwarding address in #829046 points at 
> http://git.sergiodj.net/, however I couldn't find packaging for pagure 
> anywhere. Seems all deleted sometime before.

I don't know why Sergio does not want to create a stable repo at alioth.

> The repository on collab-maint stops at September 2016 and lacks the work 
> around December 2016.

Sergio,
 Can we finalize on collab-maint and not resetting history for every change?

> Could you tell me where can I find the proper packaging repository?

I have pushed my copy here
https://git.fosscommunity.in/praveen/pagure

It was originally at git://git.sergiodj.net/debian/pagure-new.git

[signature.asc (application/pgp-signature, attachment)]

Message #238 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Sergio Durigan Junior <sergiodj@sergiodj.net>

To: Boyuan Yang <073plan@gmail.com>

Cc: Pirate Praveen <praveen@onenetbeyond.org>, debian-devel <debian-devel@lists.debian.org>, 829046@bugs.debian.org

Subject: Re: Moving away from (unsupportable) FusionForge on Alioth?

Date: Sun, 14 May 2017 18:39:22 -0400

[Message part 1 (text/plain, inline)]

On Sunday, May 14 2017, Boyuan Yang wrote:

> 在 2017年5月14日星期日 CST 下午3:04:26，Pirate Praveen 写道：
>> As far as I understand, the only thing that is blocking is non
>> availability of pagure package.
>> 
>> So helping fix this would help move this forward (currently pagure tests
>> are failing).
>> 
>> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829046
>> 
>> After we have the package, then DSA standard processes for new service
>> would follow, I assume.
>
> I'm a little bit confused. The bug forwarding address in #829046 points at 
> http://git.sergiodj.net/, however I couldn't find packaging for pagure 
> anywhere. Seems all deleted sometime before.

Hi guys,

I have recently-ish moved my private things to another server, and I
think the pagure repo got lost somehow.  I'm currently out of town but
I'll fix this as soon as I get back, next weekend.

> The repository on collab-maint stops at September 2016 and lacks the work 
> around December 2016.

I wasn't really using the collab-maint repository because I haven't
created it, but I can move the latest version of my repo there.

On Sunday, May 14 2017, Pirate Praveen wrote:

> On ഞായര്‍ 14 മെയ് 2017 08:20 വൈകു, Boyuan Yang wrote:
>> I'm a little bit confused. The bug forwarding address in #829046 points at 
>> http://git.sergiodj.net/, however I couldn't find packaging for pagure 
>> anywhere. Seems all deleted sometime before.
>
> I don't know why Sergio does not want to create a stable repo at alioth.

It's not that I don't want.  It's that this is my usual workflow when
packaging things on Debian: I do everything on a local git repo, and
then move to collab-maint when the package is ready.

>> The repository on collab-maint stops at September 2016 and lacks the work 
>> around December 2016.
>
> Sergio,
>  Can we finalize on collab-maint and not resetting history for every change?

Sure.  I'll move everything to collab-maint as soon as I get back home,
as I said earilier.

>> Could you tell me where can I find the proper packaging repository?
>
> I have pushed my copy here
> https://git.fosscommunity.in/praveen/pagure
>
> It was originally at git://git.sergiodj.net/debian/pagure-new.git

Thanks for doing that.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

[signature.asc (application/pgp-signature, inline)]

Message #243 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Boyuan Yang <073plan@gmail.com>

To: debian-devel <debian-devel@lists.debian.org>

Cc: Sergio Durigan Junior <sergiodj@sergiodj.net>, Pirate Praveen <praveen@onenetbeyond.org>, 829046@bugs.debian.org

Subject: Re: Moving away from (unsupportable) FusionForge on Alioth?

Date: Mon, 15 May 2017 15:54:25 +0800

[Message part 1 (text/plain, inline)]

在 2017年5月14日星期日 +08 下午6:39:22，Sergio Durigan Junior 写道：
> On Sunday, May 14 2017, Boyuan Yang wrote:
> > 在 2017年5月14日星期日 CST 下午3:04:26，Pirate Praveen 写道：
> > 
> >> As far as I understand, the only thing that is blocking is non
> >> availability of pagure package.
> >> 
> >> So helping fix this would help move this forward (currently pagure tests
> >> are failing).
> >> 
> >> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829046
> >> 
> >> After we have the package, then DSA standard processes for new service
> >> would follow, I assume.
> Sure.  I'll move everything to collab-maint as soon as I get back home,
> as I said earilier.

That would be great.

> >> Could you tell me where can I find the proper packaging repository?
> > 
> > I have pushed my copy here
> > https://git.fosscommunity.in/praveen/pagure
> > 
> > It was originally at git://git.sergiodj.net/debian/pagure-new.git
> 
> Thanks for doing that.

I took a look into pagure packaging (both upstream latest version 2.14.2 and 
Debian packaging version 2.6+dfsg from the git repo above) and things look 
like a nightmare. Under Debian Testing and Debian Unstable, current packaging 
did not create a working database for unittests. If we create db manually 
(before dh_auto_test) and run unittest again, things can fail severely (around 
60+/290+ units fail, not just 5). 

Hence it would be great if anyone familiar with Python2 and Flask could help 
improve the status of pagure packaging.

--
Boyuan Yang

[signature.asc (application/pgp-signature, inline)]

Message #248 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Boyuan Yang <073plan@gmail.com>

To: 829046@bugs.debian.org

Cc: Sergio Durigan Junior <sergiodj@sergiodj.net>, Pirate Praveen <praveen@onenetbeyond.org>

Subject: Re: Bug#829046: Difficulties in packaging pagure

Date: Tue, 16 May 2017 16:20:16 +0800

[Message part 1 (text/plain, inline)]

I would like to summerize problems found when packaging pagure in May 2017.

* Missing unittest dependency on python-pyclamd.

* Every version (including latest 2.14.2) needs python-bleach (<< 2.0.0).
Current version in testing: 2.0-1.
python-bleach (>= 2.0.0) depends on python-html5lib (>= 0.99999999).
Current version in testing: 0.999999999-1.
python-bleach (<< 2.0.0) depends on python-html5lib (<< 0.99999999).

No patches raised for this problem yet.

* Every version needs py-bcrypt, which exists in fedora but long superceded by 
python-bcrypt.

Patches in pagure source code available.

* Some strange unittest errors for v2.6+dfsg.

* Specific to v2.14.2: pygments style settings in entrypoint not recognized by 
unittest, raising tons of unittest failures.

* Unittest needs a functional database when using "local" auth method but that 
database never exists during dh_auto_test.

* Specific to v2.14.2: pep8-compat testing would invoke pyflake8, which is 
python3 version in Debian. (Fixed in upstream trunk).

* Non-critical: Optional dep fedmsg severely outdated.

Several build logs attached here. Wish that could be useful.

--
Boyuan Yang

[pagure_2.6+dfsg-1_amd64-2017-05-16T07:11:33Z.build (text/plain, attachment)]

[pagure_2.6+dfsg-1_amd64-2017-05-16T07:34:24Z.build (text/plain, attachment)]

[pagure_2.6+dfsg-1_amd64-2017-05-16T07:26:47Z.build (text/plain, attachment)]

[signature.asc (application/pgp-signature, inline)]

Message #253 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Ben Finney <bignose@debian.org>

To: Sergio Durigan Junior <sergiodj@sergiodj.net>

Cc: 829046@bugs.debian.org

Subject: Bug#829046: Git repository for Pagure packaging

Date: Wed, 17 May 2017 09:15:02 +1000

[Message part 1 (text/plain, inline)]

On 14-May-2017, Sergio Durigan Junior wrote:
> On Sunday, May 14 2017, Boyuan Yang wrote:
> 
> > I'm a little bit confused. The bug forwarding address in #829046
> > points at http://git.sergiodj.net/, however I couldn't find
> > packaging for pagure anywhere. Seems all deleted sometime before.
> 
> I have recently-ish moved my private things to another server, and I
> think the pagure repo got lost somehow. I'm currently out of town
> but I'll fix this as soon as I get back, next weekend.

Thanks for acting on that. You will also want to get a valid SSL
certificate for the site, as the current one (as of today) fails to
verify.

> Sure. I'll move everything to collab-maint as soon as I get back
> home […].

Thank you, that would be best IMO.

-- 
 \         “Pinky, are you pondering what I'm pondering?” “I think so, |
  `\    Brain, but if the plural of mouse is mice, wouldn't the plural |
_o__)                      of spouse be spice?” —_Pinky and The Brain_ |
Ben Finney <bignose@debian.org>

[signature.asc (application/pgp-signature, inline)]

Message #258 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Ben Finney <bignose@debian.org>

To: Boyuan Yang <073plan@gmail.com>

Cc: 829046@bugs.debian.org

Subject: Re: Bug#829046: Difficulties in packaging pagure

Date: Wed, 17 May 2017 09:18:42 +1000

[Message part 1 (text/plain, inline)]

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 you mean that the Debian packaging could just take those patches,
and apply them to the existing Pagure version?

> * Some strange unittest errors for v2.6+dfsg.

Thanks for the build logs to show those errors.

> * Unittest needs a functional database when using "local" auth
> method but that database never exists during dh_auto_test.

Perhaps a change to the unit tests, so that they don't rely on an
actual database. (Unit tests should be isolated from external
dependencies that are not reliably available at test time.)

Would this be worthwhile?

> * Specific to v2.14.2: pep8-compat testing would invoke pyflake8,
> which is python3 version in Debian. (Fixed in upstream trunk).

Another patch that can just be taken from upstream and applied in the
packaging?

-- 
 \         “I have yet to see any problem, however complicated, which, |
  `\      when you looked at it in the right way, did not become still |
_o__)                                more complicated.” —Paul Anderson |
Ben Finney <bignose@debian.org>

[signature.asc (application/pgp-signature, inline)]

Message #263 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Boyuan Yang <073plan@gmail.com>

To: Ben Finney <bignose@debian.org>

Cc: 829046@bugs.debian.org

Subject: Re: Bug#829046: Difficulties in packaging pagure

Date: Wed, 17 May 2017 16:09:47 +0800

[Message part 1 (text/plain, inline)]

在 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 patches,
> and apply them to the existing Pagure version?

Yes. There is a patch left from 2.6+dfsg debian/patches directory on collab-
maint. Also there is an unmerged https://pagure.io/pagure/pull-request/2014.

> > * Some strange unittest errors for v2.6+dfsg.
> 
> Thanks for the build logs to show those errors.
> 
> > * Unittest needs a functional database when using "local" auth
> > method but that database never exists during dh_auto_test.
> 
> Perhaps a change to the unit tests, so that they don't rely on an
> actual database. (Unit tests should be isolated from external
> dependencies that are not reliably available at test time.)
> 
> Would this be worthwhile?

I'm not quite sure. The dh_auto_test has some different behaviour when compared 
with upstream "runtests.sh". More investigations are needed.

> 
> > * Specific to v2.14.2: pep8-compat testing would invoke pyflake8,
> > which is python3 version in Debian. (Fixed in upstream trunk).
> 
> Another patch that can just be taken from upstream and applied in the
> packaging?

Upstream just released shiny new v2.15 so that would be unnecessary.

There are some ongoing works to deal with dependency problems (such as python-
bleach >= 2.0.0, see https://pagure.io/pagure/pull-request/2269) and make 
pagure suitable for Debian. However, we are still in lack of human power for 
testing and packaging.

--
Boyuan Yang

[signature.asc (application/pgp-signature, inline)]

Message #268 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Boyuan Yang <073plan@gmail.com>

To: 829046@bugs.debian.org

Subject: Re: Bug#829046: Difficulties in packaging pagure

Date: Wed, 17 May 2017 18:43:24 +0800

[Message part 1 (text/plain, inline)]

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 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 we should sort them out.

Logs attached.

[1] https://anonscm.debian.org/git/collab-maint/pagure.git/log/?h=dev

--
Boyuan Yang

[pagure_2.15_test.log (text/x-log, attachment)]

[signature.asc (application/pgp-signature, inline)]

Message #273 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Boyuan Yang <073plan@gmail.com>

To: 829046@bugs.debian.org

Cc: zsj950618 <zsj950618@gmail.com>

Subject: Re: Bug#829046: Difficulties in packaging pagure

Date: Thu, 18 May 2017 02:43:19 +0800

[Message part 1 (text/plain, inline)]

在 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 we should sort them out.

With the help of zsj (on cc list), we managed to have previous unittest 
problems fixed and the package can be built successfully now.

The alioth repo is converted to a full-history full-sourced packaging 
repository to ease the interoperability with backporting upstream patches 
using gbp. Original tarball committed onto "pristine-tar" branch and packaging 
instructions in "master-2.15" branch.

Current packaging instructions still need extensive review in the following 
aspects:

* Stripping non-DFSG files, if any
* Status of JavaScript and CSS in the package
* Review of patches
* Actual installation tests
* Rewriting debian/copyright file

--
Sincerely,
Boyuan Yang

[signature.asc (application/pgp-signature, inline)]

Message #278 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Shengjing Zhu <zsj950618@gmail.com>

To: 829046@bugs.debian.org

Cc: Boyuan Yang <073plan@gmail.com>, Ben Finney <bignose@debian.org>, Sergio Durigan Junior <sergiodj@sergiodj.net>, Pirate Praveen <praveen@onenetbeyond.org>

Subject: Re: Bug#829046: Difficulties in packaging pagure

Date: Thu, 18 May 2017 02:43:33 +0800

-----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 work is to deal with the JS libraries,
some are still not in Debian:
* jdenticon.js
* cal-heatmap
* jquery.atwho
* emojione

I can't push it to collab-maint and I may apply permission
to continue work on it.

Best regards,
Shengjing Zhu
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE85F2DZP0aJKsSKyHONAPABi+PjUFAlkcmX0ACgkQONAPABi+
PjVS+gf/TiI+0wgomJV74nR1CApSOnpCTceJpSh3VVeQ1PwYC/asFnZsBpN1uhCe
85f30JTZHxc9Ta3l6oxQ0viEkQa3YH9NBh3XGJ332WVMKdXW2yuDbpNRmAQ2aK5k
Dc1Y/0lawOX8ITezJwi/O5yEQUUc5+S/0Zw/xa2OOPVnIXiL6oj/ugX6xQ8hNmca
+BOr5E5tpaSjHZ6FiNtt3g9f608uUSdwYYQqDcW7umjDU+ra/jIn+VyVftUQG5X+
KoVt4S8kaWEZLdnx1dcHzgYefgShv/ysKTbTILdpPzXbRixZqmYX43vebXzRfrvr
Jzo1yNqQuIA151pZ7jKrtEXjN1mp3w==
=Hesi
-----END PGP SIGNATURE-----

Message #283 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Pirate Praveen <praveen@onenetbeyond.org>

To: Shengjing Zhu <zsj950618@gmail.com>, 829046@bugs.debian.org

Cc: Boyuan Yang <073plan@gmail.com>, Ben Finney <bignose@debian.org>, Sergio Durigan Junior <sergiodj@sergiodj.net>

Subject: Re: Bug#829046: Difficulties in packaging pagure

Date: Thu, 18 May 2017 08:49:58 +0530

[Message part 1 (text/plain, inline)]

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. one of them is applied
> in trunk.
> 
> 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.

> * jquery.atwho

Same for ruby-jquery-atwho-rails

> * emojione

This is already there
https://packages.debian.org/unstable/libjs-emojione

[signature.asc (application/pgp-signature, attachment)]

Message #290 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Boyuan Yang <073plan@gmail.com>

To: 829046@bugs.debian.org

Cc: Shengjing Zhu <zsj950618@gmail.com>, Ben Finney <bignose@debian.org>, Sergio Durigan Junior <sergiodj@sergiodj.net>, Pirate Praveen <praveen@onenetbeyond.org>

Subject: Re: Bug#829046: Difficulties in packaging pagure

Date: Thu, 18 May 2017 11:59:36 +0800

[Message part 1 (text/plain, inline)]

在 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 trunk.

There are some problems: this packaging uses upstream source code directly 
from from Git repository, not the tarball upstream released on https://
pagures.io.

The tarballs contain different distributed files than git repo because tarballs 
are generated by "python setup.py sdist", which would drop some scripts. Among 
the dropped files there is the "runtest.sh" script, on which this packaging 
instruction relies.

There is a known workaround: we could switch the upstream from https://
pagures.io/pagures to its mirror on GitHub [1]. The tarball provided by GitHub 
is simply a compression of files checked out from git tag. I'm not sure if that 
is acceptable.

[1] https://github.com/pypingou/pagure/

--
Boyuan Yang

[signature.asc (application/pgp-signature, inline)]

Message #295 received at 829046@bugs.debian.org (full text, mbox, reply):

From: SJ Zhu <zsj950618@gmail.com>

To: Pirate Praveen <praveen@onenetbeyond.org>

Cc: 829046@bugs.debian.org, Boyuan Yang <073plan@gmail.com>, Ben Finney <bignose@debian.org>, Sergio Durigan Junior <sergiodj@sergiodj.net>

Subject: Re: Bug#829046: Difficulties in packaging pagure

Date: Thu, 18 May 2017 12:01:43 +0800

[Message part 1 (text/plain, inline)]

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, since I don't want this python package
to depend on ruby(bring by ruby-cal-heatmap-rails)

> 
> > * jquery.atwho
> 
> Same for ruby-jquery-atwho-rails
> 
> > * emojione
> 
> This is already there
> https://packages.debian.org/unstable/libjs-emojione
> 

I need some time to figure out how the emojione js work,
upstream pin it at version 1.3.1, see here:
https://pagure.io/pagure/pull-request/1475

I will try to setup a working pagure server to see what if we use
newer emojione.

Besides, in pagure/static/emoji dir,

emoji/jquery.textcomplete-1.7.1.js
emoji/emoji_strategy.json
emoji/jquery.textcomplete.js
emoji/emojione.sprites.min.css
emoji/emojione.sprites.png
emoji/emoji_strategy-1.3.1.json
emoji/emojione.sprites.css
emoji/emojione-1.3.1.js
emoji/emojicomplete.js
emoji/jquery.textcomplete.min.js
emoji/emojione.js
emoji/emojione.min.js
emoji/emojione.sprites.min-1.3.1.css
emoji/emojione.sprites-1.3.1.png
emoji/emojione.sprites-1.3.1.css

libjs-emojione only covers emojione{,.min}.js

I think we need to dig more on this, and one new library I missed,

* jquery.textcomplete

Best regards,
Shengjing Zhu

[signature.asc (application/pgp-signature, inline)]

Message #300 received at 829046@bugs.debian.org (full text, mbox, reply):

From: SJ Zhu <zsj950618@gmail.com>

To: Boyuan Yang <073plan@gmail.com>

Cc: 829046@bugs.debian.org, Ben Finney <bignose@debian.org>, Sergio Durigan Junior <sergiodj@sergiodj.net>, Pirate Praveen <praveen@onenetbeyond.org>

Subject: Re: Bug#829046: Difficulties in packaging pagure

Date: Thu, 18 May 2017 12:07:41 +0800

[Message part 1 (text/plain, inline)]

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 js,
then import it to upstream branch like what sergiodj did.

PS. I think I forget to remove some files which filename is not matched
by "*.min.js"

> The tarballs contain different distributed files than git repo because tarballs 
> are generated by "python setup.py sdist", which would drop some scripts. Among 
> the dropped files there is the "runtest.sh" script, on which this packaging 
> instruction relies.
> 
> There is a known workaround: we could switch the upstream from https://
> pagures.io/pagures to its mirror on GitHub [1]. The tarball provided by GitHub 
> is simply a compression of files checked out from git tag. I'm not sure if that 
> is acceptable.
> 
> [1] https://github.com/pypingou/pagure/
> 
> --
> Boyuan Yang

[signature.asc (application/pgp-signature, inline)]

Message #305 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Pirate Praveen <praveen@debian.org>

To: 829046@bugs.debian.org, Shengjing Zhu <zsj950618@gmail.com>

Subject: Re: Bug#829046: Difficulties in packaging pagure

Date: Thu, 18 May 2017 09:50:34 +0530

[Message part 1 (text/plain, inline)]

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
> emoji/emoji_strategy.json
> emoji/jquery.textcomplete.js
> emoji/emojione.sprites.min.css
> emoji/emojione.sprites.png
> emoji/emoji_strategy-1.3.1.json
> emoji/emojione.sprites.css
> emoji/emojione-1.3.1.js
> emoji/emojicomplete.js
> emoji/jquery.textcomplete.min.js
> emoji/emojione.js
> emoji/emojione.min.js
> emoji/emojione.sprites.min-1.3.1.css
> emoji/emojione.sprites-1.3.1.png
> emoji/emojione.sprites-1.3.1.css
> 
> libjs-emojione only covers emojione{,.min}.js
> 
> I think we need to dig more on this, 

yes. I will have a look.

> and one new library I missed, 
> * jquery.textcomplete

This is already packaged libjs-jquery-textcomplete

[signature.asc (application/pgp-signature, attachment)]

Message #310 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Boyuan Yang <073plan@gmail.com>

To: 829046@bugs.debian.org

Cc: SJ Zhu <zsj950618@gmail.com>, Ben Finney <bignose@debian.org>, Sergio Durigan Junior <sergiodj@sergiodj.net>, Pirate Praveen <praveen@onenetbeyond.org>

Subject: Re: Bug#829046: Difficulties in packaging pagure

Date: Fri, 19 May 2017 00:05:50 +0800

[Message part 1 (text/plain, inline)]

在 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 the source by `git archvie` and remove the minified js,
> then import it to upstream branch like what sergiodj did.
> 
> PS. I think I forget to remove some files which filename is not matched
> by "*.min.js"

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 
removed javascript libraries
* If that package does not exist, package them first

Option 2
------------

* Only minified javascripts are not acceptable
* Will use tools like yui-compressor to generate minified js files without using 
libjs-* packages
* Write d/copyright for unminified js files

Option 3
-------------

* An mixture of 1 & 2
* Use libjs-* if that lib has been packaged in Debian
* If not packaged, use non-minified version and run processor to generate 
minified js files


I am not very familiar with Debian's JavaScript policies. Which of my 
understandings is correct?

--
Boyuan Yang

[signature.asc (application/pgp-signature, inline)]

Message #315 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Pirate Praveen <praveen@onenetbeyond.org>

To: Boyuan Yang <073plan@gmail.com>,829046@bugs.debian.org

Cc: SJ Zhu <zsj950618@gmail.com>,Ben Finney <bignose@debian.org>,Sergio Durigan Junior <sergiodj@sergiodj.net>

Subject: Re: Bug#829046: Difficulties in packaging pagure

Date: Fri, 19 May 2017 15:06:30 +0530

On 2017, മേയ് 18 9:35:50 PM IST, Boyuan Yang <073plan@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 
>removed javascript libraries
>* If that package does not exist, package them first

This is the ideal option.

>Option 2
>------------
>
>* Only minified javascripts are not acceptable
>* Will use tools like yui-compressor to generate minified js files
>without using 
>libjs-* packages
>* Write d/copyright for unminified js files

If the minified javascript comes with its corresponding non minified form, its okay. Or you could provide the source in debian/missing-sources (not 100% sure if the directory name is correct or not, but there is an option to provide source). But it is best to minify them during build to really make sure the min corresponds to the source file since we have the minification tools already packaged. node-uglify is better as yui-compressor will pull in a jdk as dependency.

>Option 3
>-------------
>
>* An mixture of 1 & 2
>* Use libjs-* if that lib has been packaged in Debian
>* If not packaged, use non-minified version and run processor to
>generate 
>minified js files

It should be enough for most cases. But if there are some libs that uses browserify/webpack or babel, we have a problem (I have to keep diaspora out of main because handlebars.js needs these). We will have to generate those files in debian. I have been working on this and we are in a pretty good position now. grunt and gulp are available, browserify and webpack is close to finish. Though babel is a bit complicated as it has circular dependency on rollup.

>I am not very familiar with Debian's JavaScript policies. Which of my 
>understandings is correct?
>

I hope its clear now.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Message #320 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Boyuan Yang <073plan@gmail.com>

To: Pirate Praveen <praveen@onenetbeyond.org>

Cc: 829046@bugs.debian.org, SJ Zhu <zsj950618@gmail.com>, Ben Finney <bignose@debian.org>, Sergio Durigan Junior <sergiodj@sergiodj.net>

Subject: Re: Bug#829046: Difficulties in packaging pagure

Date: Fri, 19 May 2017 17:53:33 +0800

[Message part 1 (text/plain, inline)]

在 2017年5月19日星期五 CST 下午3:06:30，Pirate Praveen 写道：
> On 2017, മേയ് 18 9:35:50 PM IST, Boyuan Yang <073plan@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
> >removed javascript libraries
> >* If that package does not exist, package them first
> 
> This is the ideal option.
> 
> >Option 2
> >------------
> >
> >* Only minified javascripts are not acceptable
> >* Will use tools like yui-compressor to generate minified js files
> >without using
> >libjs-* packages
> >* Write d/copyright for unminified js files
> 
> If the minified javascript comes with its corresponding non minified form,
> its okay. Or you could provide the source in debian/missing-sources (not
> 100% sure if the directory name is correct or not, but there is an option
> to provide source). But it is best to minify them during build to really
> make sure the min corresponds to the source file since we have the
> minification tools already packaged. node-uglify is better as
> yui-compressor will pull in a jdk as dependency.
> >Option 3
> >-------------
> >
> >* An mixture of 1 & 2
> >* Use libjs-* if that lib has been packaged in Debian
> >* If not packaged, use non-minified version and run processor to
> >generate
> >minified js files
> 
> It should be enough for most cases. But if there are some libs that uses
> browserify/webpack or babel, we have a problem (I have to keep diaspora out
> of main because handlebars.js needs these). We will have to generate those
> files in debian. I have been working on this and we are in a pretty good
> position now. grunt and gulp are available, browserify and webpack is close
> to finish. Though babel is a bit complicated as it has circular dependency
> on rollup.
> >I am not very familiar with Debian's JavaScript policies. Which of my
> >understandings is correct?
> 
> I hope its clear now.

Thanks a lot. If all three options are acceptable then we are already in a 
good position: check out the master branch on Alioth repo [1] and we already 
have a working build script now, (with option 3 above). I call it a "+ds1" 
version since actually no file in the repo is of non-DFSG. Luckily, upstream 
provides all non-minified javascripts files together with minified ones.

I checked debian/copyright for the first round and completed it. Remaining 
problems:

* emojione v1 as bundled in pagure is free/libre library (MIT/CC-BY-SA-4.0) 
but later versions (e.g., v3) restricted its use (non-commercial or pay for 
license). That might be a trouble if we are to package it separately.
* Embedded fonts-hack-web and fonts-hack-ttf not stripped off (yet). Perhaps 
it's fine if we use upstream bundled fonts?
* libjs-codemirror in the Debian repository is outdated. We might need a newer 
version to make sure pagure works correctly.
* Several other js libraries not in Debian, as stated by Shengjing Zhu before.

For other problems and a TODO list, see git commit a83dd06ccc and debian/TODO 
file.

[1] https://anonscm.debian.org/git/collab-maint/pagure.git/log/

--
Boyuan Yang

[signature.asc (application/pgp-signature, inline)]

Message #325 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Shengjing Zhu <zsj950618@gmail.com>

To: Boyuan Yang <073plan@gmail.com>

Cc: Pirate Praveen <praveen@onenetbeyond.org>, 829046@bugs.debian.org, Ben Finney <bignose@debian.org>, Sergio Durigan Junior <sergiodj@sergiodj.net>

Subject: Re: Bug#829046: Difficulties in packaging pagure

Date: Fri, 19 May 2017 18:23:33 +0800

[Message part 1 (text/plain, inline)]

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,
https://anonscm.debian.org/git/collab-maint/wordpress.git/tree/debian/wordpress.linktrees

Besides, I'm trying to make upstream to put the vendor libraries to one
folder, which can be more convenient for packaging in Debian.
https://pagure.io/pagure/pull-request/2287

Best regards,
Shengjing Zhu

On Fri, May 19, 2017 at 05:53:33PM +0800, Boyuan Yang wrote:
> Thanks a lot. If all three options are acceptable then we are already in a 
> good position: check out the master branch on Alioth repo [1] and we already 
> have a working build script now, (with option 3 above). I call it a "+ds1" 
> version since actually no file in the repo is of non-DFSG. Luckily, upstream 
> provides all non-minified javascripts files together with minified ones.
> 
> I checked debian/copyright for the first round and completed it. Remaining 
> problems:
> 
> * emojione v1 as bundled in pagure is free/libre library (MIT/CC-BY-SA-4.0) 
> but later versions (e.g., v3) restricted its use (non-commercial or pay for 
> license). That might be a trouble if we are to package it separately.
> * Embedded fonts-hack-web and fonts-hack-ttf not stripped off (yet). Perhaps 
> it's fine if we use upstream bundled fonts?
> * libjs-codemirror in the Debian repository is outdated. We might need a newer 
> version to make sure pagure works correctly.
> * Several other js libraries not in Debian, as stated by Shengjing Zhu before.
> 
> For other problems and a TODO list, see git commit a83dd06ccc and debian/TODO 
> file.
> 
> [1] https://anonscm.debian.org/git/collab-maint/pagure.git/log/
> 
> --
> Boyuan Yang

[signature.asc (application/pgp-signature, inline)]

Message #330 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Ben Finney <bignose@debian.org>

To: Shengjing Zhu <zsj950618@gmail.com>

Cc: 829046@bugs.debian.org

Subject: Bug#829046: Bundled third-party libraries should not be used

Date: Sat, 20 May 2017 07:03:21 +1000

[Message part 1 (text/plain, inline)]

On 19-May-2017, Shengjing Zhu wrote:
> I checked the repo in collab-maint. I think it's not ideal to remove
> the vendor js/css in source tree.

Can you explain why?

Removing files from the source is one of the most straightforward way
to be certain that the Debian source package does not use them, and
instead declares the dependency on a separate Debian package for those
files.

Why do you say that is not ideal?

> Besides, I'm trying to make upstream to put the vendor libraries to
> one folder, which can be more convenient for packaging in Debian.
> https://pagure.io/pagure/pull-request/2287

Debian Policy §4.13 states the Debian package should not use those
bundled third-party libraries, so I am not sure what you mean by
bundled libraries being “more convenient” when in one directory.

Do you mean, more convenient for removing those files?

-- 
 \     “Not to be absolutely certain is, I think, one of the essential |
  `\                         things in rationality.” —Bertrand Russell |
_o__)                                                                  |
Ben Finney <bignose@debian.org>

[signature.asc (application/pgp-signature, inline)]

Message #335 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Shengjing Zhu <zsj950618@gmail.com>

To: Ben Finney <bignose@debian.org>

Cc: 829046@bugs.debian.org

Subject: Re: Bug#829046: Bundled third-party libraries should not be used

Date: Sat, 20 May 2017 12:14:50 +0800

[Message part 1 (text/plain, inline)]

On Sat, May 20, 2017 at 07:03:21AM +1000, Ben Finney wrote:
> Can you explain why?
> 
> Removing files from the source is one of the most straightforward way
> to be certain that the Debian source package does not use them, and
> instead declares the dependency on a separate Debian package for those
> files.
> 
> Why do you say that is not ideal?
> 

My feeling is based on what other packages do. Take python-pip for
example, _vendor dir is not removed in source tree, but removed in
dh_auto_build pass.

IMHO, this way we keep the source tree more consistent with upstream.

I'm not so experient with debian package, maybe wrong here :)

> Debian Policy §4.13 states the Debian package should not use those
> bundled third-party libraries, so I am not sure what you mean by
> bundled libraries being “more convenient” when in one directory.
> 
> Do you mean, more convenient for removing those files?
> 

Yes, more convenient to remove bundles and link to libjs-*.


Best regards,
Shengjing Zhu

[signature.asc (application/pgp-signature, inline)]

Message #342 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Sergio Durigan Junior <sergiodj@sergiodj.net>

To: Boyuan Yang <073plan@gmail.com>

Cc: 829046@bugs.debian.org, SJ Zhu <zsj950618@gmail.com>, Ben Finney <bignose@debian.org>, Pirate Praveen <praveen@onenetbeyond.org>

Subject: Re: Bug#829046: Difficulties in packaging pagure

Date: Sun, 21 May 2017 15:56:35 -0400

[Message part 1 (text/plain, inline)]

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 on https://
>> > pagures.io.
>> 
>> Hi,
>> I import the source by `git archvie` and remove the minified js,
>> then import it to upstream branch like what sergiodj did.
>> 
>> PS. I think I forget to remove some files which filename is not matched
>> by "*.min.js"

Thanks for taking a look at the package and fixing some of the issues.

I'm now back from my vacation and can dedicate some time to pagure
again.

> 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 
> removed javascript libraries
> * If that package does not exist, package them first

This is what I was trying to do from the beginning.  I packaged some
libjs-* packages last year, but not all of them.  Also, I was following
upstream and noticed that the they add extra dependencies/bump versions
of existing dependencies indiscriminately, which is not very good for
us.  I was trying to talk with upstream and come up with a saner
approach for this, but got sidetracked.

> Option 2
> ------------
>
> * Only minified javascripts are not acceptable
> * Will use tools like yui-compressor to generate minified js files without using 
> libjs-* packages
> * Write d/copyright for unminified js files

> Option 3
> -------------
>
> * An mixture of 1 & 2
> * Use libjs-* if that lib has been packaged in Debian
> * If not packaged, use non-minified version and run processor to generate 
> minified js files

After a while, I was starting to wonder whether it would make sense to
follow this approach.  I noticed that packaging all the JS deps would
take a long time (at the time we didn't have Grunt packaged for Debian).

Anyway, I believe it may be possible to pursue the first option now that
Grunt is available.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

[signature.asc (application/pgp-signature, inline)]

Message #349 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Sébastien <seb@k-7.ch>

To: 829046@bugs.debian.org

Subject: Status of pagure

Date: Thu, 28 Dec 2017 20:11:48 +0100

[Message part 1 (text/plain, inline)]

Hello.

Any news about this package?


-- 
Sébastien

[signature.asc (application/pgp-signature, inline)]

Message #354 received at 829046@bugs.debian.org (full text, mbox, reply):

From: "bill auger" <bill-auger@programmer.net>

To: 829046@bugs.debian.org

Subject: progress?

Date: Thu, 28 Dec 2017 21:13:56 +0100

i see no activity here or on the collab-maint repo in some time - is anyone still intending to package pagure for debian ?

Message #359 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Sergio Durigan Junior <sergiodj@sergiodj.net>

To: Sébastien <seb@k-7.ch>

Cc: 829046@bugs.debian.org, "bill auger" <bill-auger@programmer.net>

Subject: Re: Bug#829046: Status of pagure

Date: Thu, 28 Dec 2017 16:45:08 -0500

[Message part 1 (text/plain, inline)]

On Thursday, December 28 2017, Sébastien wrote:

> Hello.
>
> Any news about this package?

Hey,

Yeah, I'm still working on packaging pagure.  I'm currently packaging
the missing Python dependencies.  Without them, there isn't much one can
do about packaging pagure itself.

As for pagure, I'm mostly happy about the state of the package.  IIRC
there were some failures happening on a specific test, and I confess I
don't know if the failure is still present or not.  I think there's
information about this on the ITP bug.

Another important thing that remains to be done is to verify all the
JavaScript dependencies and make sure that they're packaged for Debian.
I'm looking into helping with the package of node-rollup and its
dependencies, which is a necessary dependency to build one of pagure's
JS files (see the pagure/static/vendor folder upstream for a list of JS
deps).

I would welcome any help with these tasks, but please let's communicate
via this bug in order to avoid duplicating efforts.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

[signature.asc (application/pgp-signature, inline)]

Message #364 received at 829046@bugs.debian.org (full text, mbox, reply):

From: "bill auger" <bill-auger@programmer.net>

To: 829046@bugs.debian.org

Subject: recap

Date: Fri, 29 Dec 2017 00:15:54 +0100

at this point i think the first thing to do is to verify the packaging state of the dependencies noted previously (re-posted below) and to see that any remaining dependencies that need packaging should have themselves ITP issues attached to this one as blockers

currently this ITP has ITP blockers:
* 863244: ITP: libjs-cal-heatmap
* 862880: ITP: node-at.js

then perhaps to look over the TODO lists and see if any items can be ticked off as completed

here is a re-cap of the progress so far according to this thread:

--------------------------------------------------------------------------------

On വ്യാഴം 18 മെയ് 2017 12:13 രാവിലെ, Shengjing Zhu wrote:
> There still needs three patches. one of them is applied
> in trunk.
> 
> The remain work is to deal with the JS libraries,
> some are still not in Debian:
> * jdenticon.js
> * cal-heatmap

On 18 May 2017 Pirate Praveen wrote:
> There is ruby-cal-heatmap, which I can split or package it separately.
> 
> > * jquery.atwho
> 
> Same for ruby-jquery-atwho-rails
> 
> > * emojione
> 
> This is already there
> https://packages.debian.org/unstable/libjs-emojione

On Thu, May 18, 2017 Pirate Praveen wrote:
> There is ruby-cal-heatmap, which I can split or package it separately.

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)

On 18 May 2017 Pirate Praveen wrote:
yes, I will work on it. I already started working on at.js
(jquery.atwho.js)

On വ്യാഴം 18 മെയ് 2017 09:31 രാവിലെ, SJ Zhu wrote: 
> Besides, in pagure/static/emoji dir,
> libjs-emojione only covers emojione{,.min}.js
> 
> I think we need to dig more on this, and one new library I missed,
> 
> * jquery.textcomplete

On 18 May 2017 Pirate Praveen wrote:
> > * jquery.textcomplete
> This is already packaged libjs-jquery-textcomplete

On Fri, May 19, 2017 at 05:53:33PM +0800, Boyuan Yang wrote:
> I checked debian/copyright for the first round and completed it. Remaining 
> problems:
> 
> * emojione v1 as bundled in pagure is free/libre library (MIT/CC-BY-SA-4.0) 
> but later versions (e.g., v3) restricted its use (non-commercial or pay for 
> license). That might be a trouble if we are to package it separately.
> * Embedded fonts-hack-web and fonts-hack-ttf not stripped off (yet). Perhaps 
> it's fine if we use upstream bundled fonts?
> * libjs-codemirror in the Debian repository is outdated. We might need a newer 
> version to make sure pagure works correctly.
> * Several other js libraries not in Debian, as stated by Shengjing Zhu before.
> 
> For other problems and a TODO list, see git commit a83dd06ccc and debian/TODO 
> file.

TODO (from the a83dd06ccc commit):
==== 
* libjs-emojione (exists incomplete version mismatch) 
* jdenticon (not yet available) 
* jquery.atwho (ruby-jquery-atwho-rails) 
* cal-heatmap (ruby-cal-heatmap-rails) 
* libjs-codemirror is OUTDATED 
* pagure/static/fonts_hack fonts-hack-* needs analysis!

and the latest debian/TODO on master
* https://anonscm.debian.org/git/collab-maint/pagure.git/tree/debian/TODO

Message #369 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Pirate Praveen <praveen@debian.org>

To: 829046@bugs.debian.org

Subject: Re: Bug#829046: Status of pagure

Date: Fri, 29 Dec 2017 18:46:30 +0530

[Message part 1 (text/plain, inline)]

On 12/29/2017 03:15 AM, Sergio Durigan Junior wrote:

> Another important thing that remains to be done is to verify all the
> JavaScript dependencies and make sure that they're packaged for Debian.
> I'm looking into helping with the package of node-rollup and its
> dependencies, which is a necessary dependency to build one of pagure's
> JS files (see the pagure/static/vendor folder upstream for a list of JS
> deps).

You can use webpack to replace rollup. I have been using webpack for
many modules that decalred adevDependency on rollup. See
https://wiki.debian.org/Javascript/Nodejs#Using_build_tools_like_grunt

[signature.asc (application/pgp-signature, attachment)]

Message #374 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Pirate Praveen <praveen@debian.org>

To: 829046@bugs.debian.org

Subject: Re: Bug#829046: recap

Date: Fri, 29 Dec 2017 20:23:26 +0530

[Message part 1 (text/plain, inline)]

On 12/29/2017 04:45 AM, bill auger wrote:
> TODO (from the a83dd06ccc commit):
> ==== 
> * libjs-emojione (exists incomplete version mismatch) 
> * jdenticon (not yet available) 
> * jquery.atwho (ruby-jquery-atwho-rails) 

This is now available
https://packages.debian.org/unstable/libjs-jquery-atwho

> * cal-heatmap (ruby-cal-heatmap-rails) 

ITP https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863244

> * libjs-codemirror is OUTDATED 
> * pagure/static/fonts_hack fonts-hack-* needs analysis!
> 
> and the latest debian/TODO on master
> * https://anonscm.debian.org/git/collab-maint/pagure.git/tree/debian/TODO
> 

[signature.asc (application/pgp-signature, attachment)]

Message #379 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Sergio Durigan Junior <sergiodj@sergiodj.net>

To: "bill auger" <bill-auger@programmer.net>

Cc: 829046@bugs.debian.org

Subject: Re: Bug#829046: recap

Date: Fri, 29 Dec 2017 12:42:54 -0500

On Thursday, December 28 2017, bill auger wrote:

> at this point i think the first thing to do is to verify the packaging
> state of the dependencies noted previously (re-posted below) and to
> see that any remaining dependencies that need packaging should have
> themselves ITP issues attached to this one as blockers
>
> currently this ITP has ITP blockers:
> * 863244: ITP: libjs-cal-heatmap
> * 862880: ITP: node-at.js
>
> then perhaps to look over the TODO lists and see if any items can be ticked off as completed

More dependencies need to be added to the list.

I'm specifically working on getting python-Pillow packaged; it's a new
dependency for pagure that was added recently.  I'm using the following
list:

  https://pagure.io/pagure/blob/master/f/requirements.txt

And python-Pillow has the following dependencies:

  https://github.com/python-pillow/Pillow/blob/master/requirements.txt

I'll make sure to open ITP's for each dep and add them as blockers of
this bug.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

Message #384 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Sergio Durigan Junior <sergiodj@sergiodj.net>

To: "bill auger" <bill-auger@programmer.net>

Cc: 829046@bugs.debian.org

Subject: Re: Bug#829046: recap

Date: Fri, 29 Dec 2017 12:52:06 -0500

On Friday, December 29 2017, I wrote:

> On Thursday, December 28 2017, bill auger wrote:
>
>> at this point i think the first thing to do is to verify the packaging
>> state of the dependencies noted previously (re-posted below) and to
>> see that any remaining dependencies that need packaging should have
>> themselves ITP issues attached to this one as blockers
>>
>> currently this ITP has ITP blockers:
>> * 863244: ITP: libjs-cal-heatmap
>> * 862880: ITP: node-at.js
>>
>> then perhaps to look over the TODO lists and see if any items can be ticked off as completed
>
> More dependencies need to be added to the list.
>
> I'm specifically working on getting python-Pillow packaged; it's a new
> dependency for pagure that was added recently.  I'm using the following
> list:
>
>   https://pagure.io/pagure/blob/master/f/requirements.txt
>
> And python-Pillow has the following dependencies:
>
>   https://github.com/python-pillow/Pillow/blob/master/requirements.txt

Well, as it turns out, python-pil *is* the Pillow fork, so please ignore
what I said above.  We're good to go on this front.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

Message #389 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Sergio Durigan Junior <sergiodj@sergiodj.net>

To: "bill auger" <bill-auger@programmer.net>

Cc: 829046@bugs.debian.org, Pirate Praveen <praveen@onenetbeyond.org>

Subject: Re: Bug#829046: recap

Date: Fri, 29 Dec 2017 13:15:06 -0500

On Friday, December 29 2017, I wrote:

> On Friday, December 29 2017, I wrote:
>
>> On Thursday, December 28 2017, bill auger wrote:
>>
>>> at this point i think the first thing to do is to verify the packaging
>>> state of the dependencies noted previously (re-posted below) and to
>>> see that any remaining dependencies that need packaging should have
>>> themselves ITP issues attached to this one as blockers
>>>
>>> currently this ITP has ITP blockers:
>>> * 863244: ITP: libjs-cal-heatmap
>>> * 862880: ITP: node-at.js
>>>
>>> then perhaps to look over the TODO lists and see if any items can be ticked off as completed
>>
>> More dependencies need to be added to the list.
>>
>> I'm specifically working on getting python-Pillow packaged; it's a new
>> dependency for pagure that was added recently.  I'm using the following
>> list:
>>
>>   https://pagure.io/pagure/blob/master/f/requirements.txt
>>
>> And python-Pillow has the following dependencies:
>>
>>   https://github.com/python-pillow/Pillow/blob/master/requirements.txt
>
> Well, as it turns out, python-pil *is* the Pillow fork, so please ignore
> what I said above.  We're good to go on this front.

I would also like to notice that I'm still working on my personal copy
of the repository, located at:

  https://git.sergiodj.net/debian/pagure.git/

Although I appreciate the help from Boyuan Yang, I think the pagure.git
repository on collab-maint is very disorganized and hard to work on.
Since we're going to move from Alioth to salsa.debian.org anyway, I
think this is a good opportunity to readjust the current repository
(without losing Boyuan Yang's changes, of course).

Pirate, I am not yet a DD, so could you please create a "pagure" project
under the Debian group on salsa.debian.org and put me as the
responsible?  My username there is "sergiodj-guest".

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

Message #394 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Pirate Praveen <praveen@onenetbeyond.org>

To: Sergio Durigan Junior <sergiodj@sergiodj.net>, bill auger <bill-auger@programmer.net>

Cc: 829046@bugs.debian.org

Subject: Re: Bug#829046: recap

Date: Sat, 30 Dec 2017 01:54:58 +0530

[Message part 1 (text/plain, inline)]

On 12/29/2017 11:45 PM, Sergio Durigan Junior wrote:

> I would also like to notice that I'm still working on my personal copy
> of the repository, located at:
> 
>   https://git.sergiodj.net/debian/pagure.git/
> 
> Although I appreciate the help from Boyuan Yang, I think the pagure.git
> repository on collab-maint is very disorganized and hard to work on.
> Since we're going to move from Alioth to salsa.debian.org anyway, I
> think this is a good opportunity to readjust the current repository
> (without losing Boyuan Yang's changes, of course).
> 
> Pirate, I am not yet a DD, so could you please create a "pagure" project
> under the Debian group on salsa.debian.org and put me as the
> responsible?  My username there is "sergiodj-guest".

Created the repo and made you a master.
https://salsa.debian.org/debian/pagure

[signature.asc (application/pgp-signature, attachment)]

Message #399 received at 829046@bugs.debian.org (full text, mbox, reply):

From: Sergio Durigan Junior <sergiodj@sergiodj.net>

To: Pirate Praveen <praveen@onenetbeyond.org>

Cc: bill auger <bill-auger@programmer.net>, 829046@bugs.debian.org

Subject: Re: Bug#829046: recap

Date: Fri, 29 Dec 2017 17:12:56 -0500

[Message part 1 (text/plain, inline)]

On Friday, December 29 2017, Pirate Praveen wrote:

> On 12/29/2017 11:45 PM, Sergio Durigan Junior wrote:
>
>> I would also like to notice that I'm still working on my personal copy
>> of the repository, located at:
>> 
>>   https://git.sergiodj.net/debian/pagure.git/
>> 
>> Although I appreciate the help from Boyuan Yang, I think the pagure.git
>> repository on collab-maint is very disorganized and hard to work on.
>> Since we're going to move from Alioth to salsa.debian.org anyway, I
>> think this is a good opportunity to readjust the current repository
>> (without losing Boyuan Yang's changes, of course).
>> 
>> Pirate, I am not yet a DD, so could you please create a "pagure" project
>> under the Debian group on salsa.debian.org and put me as the
>> responsible?  My username there is "sergiodj-guest".
>
> Created the repo and made you a master.
> https://salsa.debian.org/debian/pagure

Thanks, Pirate!

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

[signature.asc (application/pgp-signature, inline)]

Message #404 received at 829046-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 829046-close@bugs.debian.org

Subject: Bug#829046: fixed in pagure 5.8.1+dfsg-1

Date: Mon, 24 Feb 2020 10:00:15 +0000

Source: pagure
Source-Version: 5.8.1+dfsg-1
Done: Sergio Durigan Junior <sergiodj@debian.org>

We believe that the bug you reported is fixed in the latest version of
pagure, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 829046@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sergio Durigan Junior <sergiodj@debian.org> (supplier of updated pagure package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 03 Feb 2020 18:49:20 -0500
Source: pagure
Binary: pagure pagure-ci pagure-doc pagure-ev-server pagure-loadjson pagure-logcom pagure-milters pagure-mirror pagure-webhook
Architecture: source all
Version: 5.8.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Sergio Durigan Junior <sergiodj@debian.org>
Changed-By: Sergio Durigan Junior <sergiodj@debian.org>
Description:
 pagure     - git-centered forge using pygit2
 pagure-ci  - git-centered forge using pygit2 - CI integration server
 pagure-doc - git-centered forge using pygit2 (documentation)
 pagure-ev-server - git-centered forge using pygit2 - EventSource server
 pagure-loadjson - git-centered forge using pygit2 - JSON load server
 pagure-logcom - git-centered forge using pygit2 - commit log server
 pagure-milters - git-centered forge using pygit2 - milters (mail filters)
 pagure-mirror - git-centered forge using pygit2 - mirror
 pagure-webhook - git-centered forge using pygit2 - web-hook server
Closes: 829046
Changes:
 pagure (5.8.1+dfsg-1) unstable; urgency=medium
 .
   * Initial release (Closes: #829046).
Checksums-Sha1:
 a1d6e131072b5e553b4af661466db38146ab8de7 3359 pagure_5.8.1+dfsg-1.dsc
 0a2787f9c59ea3249ac9e380884a69f603e9587b 3740488 pagure_5.8.1+dfsg.orig.tar.xz
 930abff1d248526544e3a0dcc6e6f4827c7aeab4 20964 pagure_5.8.1+dfsg-1.debian.tar.xz
 5d8afa5ab1e6973b5cbbb26f3544951bf16b170a 37784 pagure-ci_5.8.1+dfsg-1_all.deb
 760635992bbb0c0eb9533f25149d8429fef067c6 804732 pagure-doc_5.8.1+dfsg-1_all.deb
 a10c14e0a07801e7218b85778d86a996782f2b3e 40844 pagure-ev-server_5.8.1+dfsg-1_all.deb
 8391a81bbf4883bb59f7b7293afc3093f39608b7 37844 pagure-loadjson_5.8.1+dfsg-1_all.deb
 0c9d6abf7e1f10c0868ca8d6730e5de4d09d8a98 37852 pagure-logcom_5.8.1+dfsg-1_all.deb
 d8f8a82c3f05595ce93e18e4fa06cbea67b3a137 40544 pagure-milters_5.8.1+dfsg-1_all.deb
 5f9bfb517046528d3bdd50581efee8139c8a1b3d 37740 pagure-mirror_5.8.1+dfsg-1_all.deb
 88000f6d8b3115a75e99bbc85be93d369767f75d 37736 pagure-webhook_5.8.1+dfsg-1_all.deb
 3dd63b7269f9bbde56fed26924d7c29fc86b1faa 3030760 pagure_5.8.1+dfsg-1_all.deb
 e1d919fa6c113a75dc88ccdf3c217e854ba49783 15796 pagure_5.8.1+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 894a60685ae92cef69008ccdc5e39f6113cfcdb5f6fdabd6e993e1b51423e70f 3359 pagure_5.8.1+dfsg-1.dsc
 15495f8dd3bfebef56cfcb3602438029dd13fa2c332d2acf7b50789e228429f1 3740488 pagure_5.8.1+dfsg.orig.tar.xz
 2e8600345232662d9e8b7e78cd355c5e522df66401def9b00d3b069aff618834 20964 pagure_5.8.1+dfsg-1.debian.tar.xz
 73c918749a2c9a9e3b779bf79ebdef97ed1f4218d713887b625a7cfb248a5386 37784 pagure-ci_5.8.1+dfsg-1_all.deb
 758dca4f466462e07817c290c4ee99a2e7ab6bcd61dbb89c400f35d81866c7e9 804732 pagure-doc_5.8.1+dfsg-1_all.deb
 91efff89a12782cf1cf86cdcccd4619e8bf8bc683f99d77328997b00fcf1c3f5 40844 pagure-ev-server_5.8.1+dfsg-1_all.deb
 91be8be5d6a1ba719b806be318f0f6e0151d4076a9048902b1a38e83fc828004 37844 pagure-loadjson_5.8.1+dfsg-1_all.deb
 f73950f7c50c94958c79b464f47a5addf3146a75711386ed47ff2db13e273d2b 37852 pagure-logcom_5.8.1+dfsg-1_all.deb
 b65b682fb0fd940d7bd7dd22af714bd39af7d56511aaae16735eaef447030879 40544 pagure-milters_5.8.1+dfsg-1_all.deb
 868402695788c0b8e0e402cf95dd5be276ad5bffdca995ce626a2d72de8b12fc 37740 pagure-mirror_5.8.1+dfsg-1_all.deb
 65f5061bbeb2cc30a0e726de831e90a45b1dc4715a409256d7fe83093aba37ce 37736 pagure-webhook_5.8.1+dfsg-1_all.deb
 8cfa4b99eb6f67d3a61426754dfcce258507543da1f476b4d16800439a0fcda1 3030760 pagure_5.8.1+dfsg-1_all.deb
 d3500c1fcba0fb65b4b692d245c1d44092bb6e0f49179b0e7cd15d1253cc7e9a 15796 pagure_5.8.1+dfsg-1_amd64.buildinfo
Files:
 f304f99c83270fb67e7ebcda70cdf66b 3359 net optional pagure_5.8.1+dfsg-1.dsc
 df294967871f87990736f2b9ad311815 3740488 net optional pagure_5.8.1+dfsg.orig.tar.xz
 84bae24ea164e074f955cd464d292e82 20964 net optional pagure_5.8.1+dfsg-1.debian.tar.xz
 ec541fc222a0dbbcf45af310c8e30e59 37784 net optional pagure-ci_5.8.1+dfsg-1_all.deb
 31e0011b6261f0be7f0dba29f74d28dd 804732 doc optional pagure-doc_5.8.1+dfsg-1_all.deb
 2b64ed872421fbc9519dd30779c09293 40844 net optional pagure-ev-server_5.8.1+dfsg-1_all.deb
 6323dbe1aba3710490feecf0e7927293 37844 net optional pagure-loadjson_5.8.1+dfsg-1_all.deb
 feda327a3e4fecfe361b47d838b3712c 37852 net optional pagure-logcom_5.8.1+dfsg-1_all.deb
 282c6266fdc7d9a277e3013ee57fc278 40544 net optional pagure-milters_5.8.1+dfsg-1_all.deb
 7873d895318faca20e5dbd1664253143 37740 net optional pagure-mirror_5.8.1+dfsg-1_all.deb
 b749614dc0c234d03e03d54164d3aa83 37736 net optional pagure-webhook_5.8.1+dfsg-1_all.deb
 8d1858ff92ab407f96cca681cddd46df 3030760 net optional pagure_5.8.1+dfsg-1_all.deb
 b3f874f1d0ff36ee67f8b5c04f8d7586 15796 net optional pagure_5.8.1+dfsg-1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJIBAEBCgAyFiEEI3pUsQKHKL8A7zH00Ot2KGX8XjYFAl443vIUHHNlcmdpb2Rq
QGRlYmlhbi5vcmcACgkQ0Ot2KGX8XjZy0g/+I+wzM30lGC8k8f5c2is0eAir1KMz
4HQ5UJrOZPJLbzzo33jMd1RXnWYsX46/ldMDHJFGj8omxnkfxGKcZBA0FiF3sbIs
Nd1VjbvTNYq31bkRqo43yKfyZbKHMg9fuzRd2rZKx8C4Z+umDWTWTmca0vcRgExE
8CM2u8KOhqvmAohP4laiEJ1sPHGf+6en9Su8EtfwtUFHU/jEmmWEAHBma+LOG5c6
JdOxGA4RpH09Od+CY9RVJRhZM0nLgwu4nidnNOrF07CAA6F2WfparSgkB5WvvB2b
cXS1PEEYKkodDU7ZwLz+L2h9mafIOXeQ7hRnFbM5j3jX4uEOqdbsBIWhVnlCRCuJ
zIZ9TRdICzYnbEEKzZOkrklXZdZFTLPhXPEZ2bn9WhUjOh8hW8gmUM+UVBzlywGW
yMwHNdoeFN0agw2Qe8ROj5NBE86wTn+SPXzLmCZsUQwRmJlzI2mpJrqGSEPIv9Pd
dbO7ZE5BHto+KU4ykz0k/dMrWE9BV5/axE0sGaXIYRGN8M+xYhzPQ+fsoYNeM1q7
WK4twL03sdjJQLoNqEEg1WSz8PbMdl+j9ZUS6ZQ4GbfK6ZLzgId8huszBvjC78vV
vix8HUNfmPOE+Cifn3oMWw2Rov1NK3h/stLZowGFdK8LgKVIDihjobIlQymQHh+L
i2VoXAkyvUSTe/c=
=WwhW
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.