On 04. 09. 23 17:30, Ankur Sinha wrote:
On Mon, Sep 04, 2023 17:10:55 +0200, Miro Hrončok wrote:
python-mne-bids neuro-sig, orphan0 weeks ago
This is a neuro-sig package, so I've taken over as primary maintainer.
This is one of the packages that failed the
On Mon, Sep 04, 2023 17:10:55 +0200, Miro Hrončok wrote:
> python-mne-bids neuro-sig, orphan0 weeks ago
This is a neuro-sig package, so I've taken over as primary maintainer.
--
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) |
,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
On Mon, Jul 31, 2023 at 12:26:12PM +0200, Miro Hrončok wrote:
> ocaml-ancient orphan 2 weeks ago
> ocaml-charinfo-width orphan 2 weeks ago
> ocaml-cil orphan 2
,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
On 25/07/2023 12:35, Hans de Goede wrote:
How do I proceed with this ? Should I run "fedpkg retire" for these 4,
or is orphaning them preferred ?
Orphaned packages will be retired automatically if no one adopts them
after 4 weeks.
--
Sincerely,
Vitaly Zaitsev (vit...@easy
eople.org/orphans-2023-07-17.txt
> grep it for your FAS username and follow the dependency chain.
>
> For human readable dependency chains,
> see https://packager-dashboard.fedoraproject.org/
> For all orphaned packages,
> see https://packager-dashboard.fedoraproject.org
On 24-07-2023 17:38, Julio Faracco wrote:
I also need access to the packager group to claim maintainership.
Who could provide it to me?
The route you are looking at is described in "Adopting an orphaned or
freshly retired package":
On Mon, 24 Jul 2023 15:38:03 -
"Julio Faracco" wrote:
> I also need access to the packager group to claim maintainership.
> Who could provide it to me?
> I will probably take twincam.
I'm not a packager, but these are some links to official information on
how to become a Fedora packager.
Hi Folks,
I also need access to the packager group to claim maintainership.
Who could provide it to me?
I will probably take twincam.
Thanks again.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
On Wed, Jul 19, 2023 at 01:08:32AM +0200, Alexander Ploumistos wrote:
> Hello,
>
> On Mon, Jul 17, 2023 at 8:49 PM Miro Hrončok wrote:
> >
> > switcheroo-controlorphan 2 weeks
> > ago
>
> Has anyone from the Workstation WG noticed this? Won't losing
>
Hello all,
What is the situation of nvml and twincam?
Which one is still orphan? I use both... I can maintain them easily.
I would like to do it for one of them if there is no objection.
Regards,
--
Julio Faracco
___
devel mailing list --
On Mon, Jul 17, 2023 at 08:48:56PM +0200, Miro Hrončok wrote:
> The following packages are orphaned and will be retired when they
> are orphaned for six weeks, unless someone adopts them. If you know for sure
> that the package should be retired, please do so now with a proper reason:
>
On Mon, Jul 17, 2023 at 08:48:56PM +0200, Miro Hrončok wrote:
> The following packages are orphaned and will be retired when they
> are orphaned for six weeks, unless someone adopts them. If you know for sure
> that the package should be retired, please do so now with a proper reason:
>
Bob Mauchin wrote:
> I'm currently assessing what is needed by our binaries packages and will
> take packages needed that have been orphaned.
Thank you! I was getting really worried that Restic would drop out and
I'd have to design a new backup solution yet again.
Björn Persson
Hello,
On Mon, Jul 17, 2023 at 8:49 PM Miro Hrončok wrote:
>
> switcheroo-controlorphan 2 weeks ago
Has anyone from the Workstation WG noticed this? Won't losing
switcheroo-control be a considerable usability regression? At the same
time, the upstream
Dne 17. 07. 23 v 20:48 Miro Hrončok napsal(a):
rpkg-macros orphan 2 weeks ago
Copr team is taking this one as it is dependence of rpkg. Which is used in Copr.
But we will be actively investigating how to replace rpkg in Copr. Unless somebody will take over the
Hi,
I'm working on the Go situation due to my non responsive situation.
I'm currently assessing what is needed by our binaries packages and will
take packages needed that have been orphaned. The reminder will be thus
retired.
Some package are probably FTBFS and I will need time to get them
On Mon, Jul 17, 2023 at 08:48:56PM +0200, Miro Hrončok wrote:
> ocaml-ancient orphan 0 weeks ago
> ocaml-charinfo-width orphan 0 weeks ago
> ocaml-cil orphan 0
,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
On 6/27/23 17:46, Simon de Vlieger wrote:
Hi,
I've orphaned some packages that I am too unfamiliar with to maintain,
especially
now that these are mostly FTBS/FTI and have unmaintained upstreams:
- preproc: https://src.fedoraproject.org/rpms/preproc
- preproc-rpmspec:
On Tue, Jun 27, 2023 at 05:48:06PM +0200, Simon de Vlieger wrote:
> Side-question: am I supposed to do anything with Bugzilla's currently related
> to these packages that are assigned to me? (unassign/assign to orphan?).
You shouldn't have to. Automation should come along and reassign them.
Side-question: am I supposed to do anything with Bugzilla's currently related
to these packages that are assigned to me? (unassign/assign to orphan?).
Regards,
Simon
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email
Hi,
I've orphaned some packages that I am too unfamiliar with to maintain,
especially
now that these are mostly FTBS/FTI and have unmaintained upstreams:
- preproc: https://src.fedoraproject.org/rpms/preproc
- preproc-rpmspec: https://src.fedoraproject.org/rpms/preproc-rpmspec
- rpkg-macros:
Dne 27. 06. 23 v 8:43 Jeffrey Stewart napsal(a):
Would like to take**golang-github-lithammer-dedent and aqemu but I
believe I still need a sponsor. Anyone willing to sponsor?
I think you can follow this guideline:
Would like to take**golang-github-lithammer-dedent and aqemu but I
believe I still need a sponsor. Anyone willing to sponsor?
On 6/9/23 07:24, Omair Majid wrote:
Hi,
Jens-Ulrik Petersen writes:
What would be really helpful is to know how it compares with other Naskh fonts
like Paktype
Hi,
Jens-Ulrik Petersen writes:
> What would be really helpful is to know how it compares with other Naskh fonts
> like Paktype (current default) and Nafees, and even Noto Nastaliq Urdu
> (they are all in Fedora 38).
I lack the tools/skills/knowledge/jargon to describe the differences I
see.
On Thu, Jun 8, 2023 at 7:47 PM Omair Majid wrote:
> Not an expert, just a casual Urdu speaker with a drive by contribution.
> I don't write Urdu much these days but I can read it.
>
Cool
Akira TAGOH writes:
> > I have no idea if Noto Sans Arabic or Noto Naskh Arabic is qualified
> > for Urdu
Hi,
Not an expert, just a casual Urdu speaker with a drive by contribution.
I don't write Urdu much these days but I can read it.
Akira TAGOH writes:
> I have no idea if Noto Sans Arabic or Noto Naskh Arabic is qualified
> for Urdu and Punjabi. Even though they have minimal coverage in
>
Actually nafees-naskh-fonts would need some font config to become default.
So I guess the easiest thing is indeed to unretire the old default package.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
I suggest we can go with nafees-naskh-fonts for now.
Though we should have caught some of the paktype fonts anyway. :-(
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora
I have no idea if Noto Sans Arabic or Noto Naskh Arabic is qualified
for Urdu and Punjabi. Even though they have minimal coverage in
fontconfig perspective, there might be minor differences which look
strange for native speakers like punctuation marks in CJK etc.
If we are going to change, we
On Wed, 2023-06-07 at 11:56 -0700, Adam Williamson wrote:
> On Mon, 2023-05-15 at 13:45 +0200, Miro Hrončok wrote:
> > paktype-naskh-basic-fonts orphan, vishalvvr 2 weeks
> > ago
>
> So this one is a problem: it appears to be our intended default font
> for Arabic. It's
On Mon, 2023-05-15 at 13:45 +0200, Miro Hrončok wrote:
> paktype-naskh-basic-fonts orphan, vishalvvr 2 weeks ago
So this one is a problem: it appears to be our intended default font
for Arabic. It's part of the @fonts group in comps and it's also in the
lorax templates
,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
On Wed, 2023-06-07 at 11:43 +0200, Miro Hrončok wrote:
> plexus-component-api orphan 6
> weeks ago
- this package (plexus-component-api) was retired an hour ago, running
[1] I checked the depending packages are: maven-native plexus-active-
collections
-
,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
g/rpms/
> >
> > Full report available at:
> > https://churchyard.fedorapeople.org/orphans-2023-05-01.txt
> > grep it for your FAS username and follow the dependency chain.
> >
> > For human readable dependency chains,
> > see https://packager-dashboard.fedo
your FAS username and follow the dependency chain.
>
> For human readable dependency chains,
> see https://packager-dashboard.fedoraproject.org/
> For all orphaned packages,
> see https://packager-dashboard.fedoraproject.org/orphan
>
&
,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
gt;
>
> Full report available at:
> https://churchyard.fedorapeople.org/orphans-2023-05-15.txt
> grep it for your FAS username and follow the dependency chain.
>
> For human readable dependency chains,
> see https://packager-dashboard.fedoraproject.org/
> For all orphaned packages,
> s
On 15. 05. 23 15:09, Sandro wrote:
oclock orphan 107 weeks ago
I don't know how that got into the list. From what I understood [1] the package
was already orphaned and has recently been unretired after passing a re-review.
Due to the
On 15-05-2023 13:45, Miro Hrončok wrote:
Maelstrom
I took Maelstrom.
oclockorphan 107 weeks ago
I don't know how that got into the list. From what I understood [1] the
package was already orphaned and has recently been unretired after
On 15. 05. 23 14:40, Sérgio Basto wrote:
On Mon, 2023-05-15 at 14:31 +0200, Sandro wrote:
On 15-05-2023 14:25, Miro Hrončok wrote:
On 15. 05. 23 14:14, Sérgio Basto wrote:
Hi,
I see a lot of new packages , can we have a report what users
have been
removed ? please
I have no idea what you ask
On Mon, 2023-05-15 at 14:31 +0200, Sandro wrote:
> On 15-05-2023 14:25, Miro Hrončok wrote:
> > On 15. 05. 23 14:14, Sérgio Basto wrote:
> > > Hi,
> > > I see a lot of new packages , can we have a report what users
> > > have been
> > > removed ? please
> >
> > I have no idea what you ask for,
On 15-05-2023 14:25, Miro Hrončok wrote:
On 15. 05. 23 14:14, Sérgio Basto wrote:
Hi,
I see a lot of new packages , can we have a report what users have been
removed ? please
I have no idea what you ask for, sorry. What do you mean by "what users
have been removed"?
I think he's wondering
On 15. 05. 23 14:14, Sérgio Basto wrote:
Hi,
I see a lot of new packages , can we have a report what users have been
removed ? please
I have no idea what you ask for, sorry. What do you mean by "what users have
been removed"?
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
via the *Take* button in he left column on
> https://src.fedoraproject.org/rpms/
>
> Full report available at:
> https://churchyard.fedorapeople.org/orphans-2023-05-15.txt
> grep it for your FAS username and follow the dependency chain.
>
> For human readable dependency chains,
> se
,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
On Mon, May 01, 2023 at 10:26:27PM +0200, Miro Hrončok wrote:
ruby-augeas brandfbb, ignatenkobrain,0 weeks ago
orphan
Taken
___
devel mailing list -- devel@lists.fedoraproject.org
To
On Tue, May 02, 2023 at 12:24:35PM +0200, Miro Hrončok wrote:
> On 02. 05. 23 11:59, Richard W.M. Jones wrote:
> >However I think there is a problem in your script because there is no
> >direct dependency from qemu to ucs-miscfixed-opentype-fonts. Instead
> >what seems to be happening is that a
On 02. 05. 23 11:59, Richard W.M. Jones wrote:
However I think there is a problem in your script because there is no
direct dependency from qemu to ucs-miscfixed-opentype-fonts. Instead
what seems to be happening is that a binary subpackage of brltty
called brltty-xw does requires
(Adding qemu maintainers)
On Tue, May 02, 2023 at 10:59:58AM +0100, Richard W.M. Jones wrote:
> On Mon, May 01, 2023 at 10:26:27PM +0200, Miro Hrončok wrote:
> > Full report available at:
> > https://churchyard.fedorapeople.org/orphans-2023-05-01.txt
> > grep it for your FAS username and follow
On Mon, May 01, 2023 at 10:26:27PM +0200, Miro Hrončok wrote:
> Full report available at:
> https://churchyard.fedorapeople.org/orphans-2023-05-01.txt
> grep it for your FAS username and follow the dependency chain.
So the one which appeared to break all the virt packages is
'ucs-miscfixed-fonts'
I have adopted:
imapfilter
Will push an update shortly.
-- Sandro
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
I've taken the following:
mingw-gstreamer1
mingw-gstreamer1-plugins-base
python-flask-login
I'd also pick up the following if the gtk maintainers are not interested:
gtksourceviewmm3
Sandro
___
devel mailing list -- devel@lists.fedoraproject.org
,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
On 04-04-2023 09:45, Miro Hrončok wrote:
libunibreak orphan 3 weeks ago
I've taken libunibreak since coolreader depends on it. Will update to
latest release as time permits.
-- Sandro
___
devel
,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
On 06-03-2023 23:19, Miro Hrončok wrote:
python-managesieveorphan 0 weeks ago
I've taken managesieve.
-- Sandro
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
.. in case of parcellite, there's clearly active upstream working towards new
release 1.2.2 - so I fail to see any reason to think about orphan :)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
> lxsession-edit, lxpolkit is now built from lxsession.src.rpm, so no need for
> these
> anymore.
> parcellite is not in LXDE spin, LXDE spin uses clipit, so I did not take this.
Okay. Well, we should retire properly lxsession-edit and lxpolkit then. I've
taken both. As well, parcellite is
Raphael Groner wrote on 2023/02/23 6:11:
Hi,
why are those packages orphan? lxsession-edit, lxpolkit and parcellite? Is LXDE
spin officially dead, what's current maintainer or do we still need mentioned
packages as additional option?
lxsession-edit, lxpolkit is now built from
> Think LXDE is pretty much dead and LXqt is much more alive as it seems now
That does not answer my question. Again: Who takes responsible for LXDE spin,
as we still have in Fedora officially?
___
devel mailing list -- devel@lists.fedoraproject.org
To
Hey!
Think LXDE is pretty much dead and LXqt is much more alive as it seems now
On 2/22/23, Raphael Groner wrote:
> Hi,
>
> why are those packages orphan? lxsession-edit, lxpolkit and parcellite? Is
> LXDE spin officially dead, what's current maintainer or do we still need
> mentioned packages
Hi,
why are those packages orphan? lxsession-edit, lxpolkit and parcellite? Is LXDE
spin officially dead, what's current maintainer or do we still need mentioned
packages as additional option?
Regards, Raphael
___
devel mailing list --
,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainersStatus Change
==
belle
On 20-02-2023 08:39, Miro Hrončok wrote:
maildirproc orphan 0 weeks ago
Taken. I may have some personal use case for it.
-- Sandro
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe
,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainersStatus Change
==
belle
On Tue, Jan 31, 2023 at 02:13:11PM -0700, Jerry James wrote:
> On Tue, Jan 31, 2023 at 2:14 AM Richard W.M. Jones wrote:
> >
> > On Mon, Jan 30, 2023 at 11:36:52AM +0100, Miro Hrončok wrote:
> > > ocaml-dose3 orphan 2 weeks
> > > ago
> > > ocaml-mccs
On Tue, Jan 31, 2023 at 2:14 AM Richard W.M. Jones wrote:
>
> On Mon, Jan 30, 2023 at 11:36:52AM +0100, Miro Hrončok wrote:
> > ocaml-dose3 orphan 2 weeks ago
> > ocaml-mccsorphan 2 weeks ago
> >
On Mon, Jan 30, 2023 at 11:36:52AM +0100, Miro Hrončok wrote:
> ocaml-dose3 orphan 2 weeks ago
> ocaml-mccsorphan 2 weeks ago
> ocaml-opam-file-formatorphan 2 weeks ago
,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainersStatus Change
==
belle
,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainersStatus Change
==
belle
On 16. 01. 23 20:53, Simo Sorce wrote:
On Fri, 2023-01-13 at 12:28 +0100, Miro Hrončok wrote:
On 13. 01. 23 0:35, Chuck Anderson wrote:
For receiving/filtering emails, you can filter on the List-Id: header
rather than the To: or Cc: headers. In that way you can differentiate
between normal
On Fri, 2023-01-13 at 12:28 +0100, Miro Hrončok wrote:
> On 13. 01. 23 0:35, Chuck Anderson wrote:
> > For receiving/filtering emails, you can filter on the List-Id: header
> > rather than the To: or Cc: headers. In that way you can differentiate
> > between normal list distribution and Bcc:. If
On 14. 01. 23 12:45, Susi Lehtola wrote:
On 1/12/23 20:57, Miro Hrončok wrote:
On 12. 01. 23 18:53, Susi Lehtola wrote:
On 1/12/23 19:48, Miro Hrončok wrote:
On 12. 01. 23 18:42, Susi Lehtola wrote:
On 12/5/22 13:36, Miro Hrončok wrote:
The following packages are orphaned and will be
On 13. 01. 23 0:35, Chuck Anderson wrote:
For receiving/filtering emails, you can filter on the List-Id: header
rather than the To: or Cc: headers. In that way you can differentiate
between normal list distribution and Bcc:. If there is no List-Id:
header, the mail can be directed to your
On Monday, 05 December 2022 at 12:36, Miro Hrončok wrote:
> The following packages are orphaned and will be retired when they
> are orphaned for six weeks, unless someone adopts them. If you know for sure
> that the package should be retired, please do so now with a proper reason:
>
On Thursday, 12 January 2023 at 18:42, Susi Lehtola wrote:
> On 12/5/22 13:36, Miro Hrončok wrote:
> > The following packages are orphaned and will be retired when they
> > are orphaned for six weeks, unless someone adopts them. If you know for sure
> > that the package should be retired, please
> Can take this if no-one else is interested (@Sergio Basto?)
>
> > docker-compose lsm5, orphan, ttomecek 1 weeks
> > ago
The Python docker-compose is deprecated upstream in favor of the Compose
V2 Docker CLI Plugin written in Go. The latter is not yet packaged for
On Thu, Jan 12, 2023 at 07:57:28PM +0100, Miro Hrončok wrote:
> On 12. 01. 23 18:53, Susi Lehtola wrote:
> > On 1/12/23 19:48, Miro Hrončok wrote:
> >> On 12. 01. 23 18:42, Susi Lehtola wrote:
> >>> On 12/5/22 13:36, Miro Hrončok wrote:
> The following packages are orphaned and will be
On 12. 01. 23 18:53, Susi Lehtola wrote:
On 1/12/23 19:48, Miro Hrončok wrote:
On 12. 01. 23 18:42, Susi Lehtola wrote:
On 12/5/22 13:36, Miro Hrončok wrote:
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know
On 12. 01. 23 18:42, Susi Lehtola wrote:
On 12/5/22 13:36, Miro Hrončok wrote:
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper
On 12/5/22 13:36, Miro Hrončok wrote:
> The following packages are orphaned and will be retired when they
> are orphaned for six weeks, unless someone adopts them. If you know for sure
> that the package should be retired, please do so now with a proper reason:
>
,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
On 04.01.23 14:16, Richard W.M. Jones wrote:
On Mon, Dec 19, 2022 at 04:43:23PM +0100, Miro Hrončok wrote:
mingw-pcreorphan 3 weeks ago
Note this is PCRE not PCRE2. Lots of packages, mainly Qt related,
seem to depend on it, and they should
On Mon, Dec 19, 2022 at 04:43:23PM +0100, Miro Hrončok wrote:
> mingw-pcreorphan 3 weeks ago
Note this is PCRE not PCRE2. Lots of packages, mainly Qt related,
seem to depend on it, and they should move to PCRE2 (packaged as
mingw-pcre2), although
On Monday, January 2, 2023 7:25:39 PM CST Robby Callicotte wrote:
> On January 2, 2023 6:45:53 PM CST, Maxwell G wrote:
> >On Mon Jan 2, 2023 at 11:46 -0600, Robby Callicotte via devel wrote:
> >> I went ahead and took vim-nerdtree.
> >
> >FYI: Nerdtree is unmaintained upstream:
>
On 02-01-2023 19:21, Dale Turner via devel wrote:
As I mentioned last week, I would be interested in xaos. BUT, I am
not presently a packager/maintainer...
I've taken xaos for safekeeping as explained in my reply to Dale's
introduction.
-- Sandro
101 - 200 of 2409 matches
Mail list logo
