Compare commits
2 commits
e8580ca4c8
...
3044eb4088
| Author | SHA1 | Date | |
|---|---|---|---|
3044eb4088
|
|||
| 3151985e7d |
2 changed files with 102 additions and 2 deletions
|
|
@ -1,5 +1,56 @@
|
|||
#+hugo_base_dir: ../
|
||||
|
||||
* The Pagure Debian package is now orphan
|
||||
:PROPERTIES:
|
||||
:EXPORT_FILE_NAME: pagure-debian-is-now-orphan
|
||||
:END:
|
||||
|
||||
As [[* Planning to orphan Pagure on Debian][promised]] in the last post, I have now orphaned the Pagure Debian
|
||||
package. Here's the full text I posted on the BTS:
|
||||
|
||||
#+BEGIN_QUOTE
|
||||
After several years, I finally decided to orphan pagure :-(.
|
||||
|
||||
I haven't been using it as my personal forge anymore, and unfortunately
|
||||
upstream development slowed down quite a bit after the main author and
|
||||
maintainer stopped contributing regularly to the project. But that is
|
||||
not to say that upstream is dead; they are still working towards
|
||||
preparing the next release.
|
||||
|
||||
Pagure is a big package with several components and an extensive list of
|
||||
build dependencies (and an even bigger testsuite which I never managed
|
||||
to make fully work on Debian). It is not for the faint of heart, and
|
||||
most of the time is usually spent fixing its (build) dependencies so
|
||||
that it doesn't get removed from testing.
|
||||
|
||||
If I may, I would like to leave some suggestions for a future
|
||||
maintainer.
|
||||
|
||||
- I never had the time to write dep8 tests, mainly because setting up
|
||||
the software is not trivial. It would be great if the package had
|
||||
more Debian-centric testing.
|
||||
|
||||
- Speaking of the hurdles to setting up Pagure, I believe the package
|
||||
installation could be made a bit more automated using debconf. I
|
||||
don't see a way to fully automate it (look at d/README.Debian), but
|
||||
there is certainly room for improvement.
|
||||
|
||||
I also left a brief TODO list inside d/README.source; feel free to
|
||||
tackle any item there!
|
||||
|
||||
I wish the next maintainer can have as much fun with the package as I
|
||||
did when I first made it for Debian!
|
||||
|
||||
Thank you,
|
||||
#+END_QUOTE
|
||||
|
||||
That's it. It was while it lasted, but I needed to feel myself
|
||||
unburdened so that I don't have that constant feeling of "I should be
|
||||
properly maintaining this package...".
|
||||
|
||||
If you feel like you'd like to give it a try at maintaining Pagure,
|
||||
now is the time!
|
||||
|
||||
* DONE Planning to orphan Pagure on Debian :english:debian:free_software:
|
||||
CLOSED: [2024-02-25 Sun 22:23]
|
||||
:PROPERTIES:
|
||||
|
|
@ -133,7 +184,7 @@ little configuration.
|
|||
On the server side (i.e., VPS or dedicated server), you will create
|
||||
the first endpoint. Something like the following should do:
|
||||
|
||||
#+begin_src
|
||||
#+begin_src ini
|
||||
[Interface]
|
||||
PrivateKey = PRIVATE_KEY_HERE
|
||||
Address = 10.0.0.1/32
|
||||
|
|
@ -163,7 +214,7 @@ A few interesting points to note:
|
|||
|
||||
At your home, you will configure the peer:
|
||||
|
||||
#+begin_src
|
||||
#+begin_src ini
|
||||
[Interface]
|
||||
PrivateKey = PRIVATE_KEY_HERE
|
||||
Address = 10.0.0.2/32
|
||||
|
|
|
|||
49
content/posts/pagure-debian-is-now-orphan.md
Normal file
49
content/posts/pagure-debian-is-now-orphan.md
Normal file
|
|
@ -0,0 +1,49 @@
|
|||
+++
|
||||
title = "The Pagure Debian package is now orphan"
|
||||
author = ["Sergio Durigan Junior"]
|
||||
draft = false
|
||||
+++
|
||||
|
||||
As [promised]({{< relref "planning-to-orphan-pagure" >}}) in the last post, I have now orphaned the Pagure Debian
|
||||
package. Here's the full text I posted on the BTS:
|
||||
|
||||
> After several years, I finally decided to orphan pagure :-(.
|
||||
>
|
||||
> I haven't been using it as my personal forge anymore, and unfortunately
|
||||
> upstream development slowed down quite a bit after the main author and
|
||||
> maintainer stopped contributing regularly to the project. But that is
|
||||
> not to say that upstream is dead; they are still working towards
|
||||
> preparing the next release.
|
||||
>
|
||||
> Pagure is a big package with several components and an extensive list of
|
||||
> build dependencies (and an even bigger testsuite which I never managed
|
||||
> to make fully work on Debian). It is not for the faint of heart, and
|
||||
> most of the time is usually spent fixing its (build) dependencies so
|
||||
> that it doesn't get removed from testing.
|
||||
>
|
||||
> If I may, I would like to leave some suggestions for a future
|
||||
> maintainer.
|
||||
>
|
||||
> - I never had the time to write dep8 tests, mainly because setting up
|
||||
> the software is not trivial. It would be great if the package had
|
||||
> more Debian-centric testing.
|
||||
>
|
||||
> - Speaking of the hurdles to setting up Pagure, I believe the package
|
||||
> installation could be made a bit more automated using debconf. I
|
||||
> don't see a way to fully automate it (look at d/README.Debian), but
|
||||
> there is certainly room for improvement.
|
||||
>
|
||||
> I also left a brief TODO list inside d/README.source; feel free to
|
||||
> tackle any item there!
|
||||
>
|
||||
> I wish the next maintainer can have as much fun with the package as I
|
||||
> did when I first made it for Debian!
|
||||
>
|
||||
> Thank you,
|
||||
|
||||
That's it. It was while it lasted, but I needed to feel myself
|
||||
unburdened so that I don't have that constant feeling of "I should be
|
||||
properly maintaining this package...".
|
||||
|
||||
If you feel like you'd like to give it a try at maintaining Pagure,
|
||||
now is the time!
|
||||
Loading…
Reference in a new issue