On Wednesday, November 11, 2020 4:51:47 AM EST Petr Pisar wrote:
> I believe it's unlikely that somobody will adopt xinetd. It was orphaned
> because its maintainer orphaned all his packages.
Xinetd is needed because it does the poly-instantiated network connection
when Linux is used for MLS syst
On Wed, Nov 11, 2020 at 5:40 PM Wolfgang Ulbrich wrote:
> I know where my package are listed at
> https://src.fedoraproject.org/dashboard/projects :)
> But...
> [root@mother rave]# dnf repoquery --whatrequires sgpio
> Letzte Prüfung auf abgelaufene Metadaten: vor 1:28:41 am Mi 11 Nov 2020
> 17:0
I know where my package are listed at
https://src.fedoraproject.org/dashboard/projects :)
But...
[root@mother rave]# dnf repoquery --whatrequires sgpio
Letzte Prüfung auf abgelaufene Metadaten: vor 1:28:41 am Mi 11 Nov 2020
17:04:25 CET.
[root@mother rave]# dnf repoquery --whatrequires sgpio
Let
On Wed, Nov 11, 2020 at 3:01 PM Chris Adams wrote:
> Are there replacements for the old services built in to xinetd?
Not that I know of as being integrated, although
writing such servers (often in perl) can often be
seen in training materials about network socket
programming in a few dozen lines
On Wed, 11 Nov 2020 at 10:01, Chris Adams wrote:
> Once upon a time, Petr Pisar said:
> > I believe it's unlikely that somobody will adopt xinetd. It was orphaned
> > because its maintainer orphaned all his packages.
>
> Are there replacements for the old services built in to xinetd? It's a
> s
Once upon a time, Petr Pisar said:
> I believe it's unlikely that somobody will adopt xinetd. It was orphaned
> because its maintainer orphaned all his packages.
Are there replacements for the old services built in to xinetd? It's a
surprise, but there are still network devices for service provi
On Mon, Nov 02, 2020 at 11:25:39AM -, Michael J Gruber wrote:
> > = NOTE about xinetd =
> >
> > Many packagers are listed as affected by xinetd. The dependency chain is:
> >
> > cvs (kasal, ppisar)
> > cvs-inetd.noarch requires xinetd
> >
> > git (amahdal, besser8
Hi,
Ian McInerney wrote:
> Why not split the cvs package like git and create a cvs-core package that
> actually contains the cvs executables/files and then only BR/require that
> from git/git-cvs? That would be the more immediate solution that prunes the
> affected packages from the xinetd orphani
On Mon, 2020-11-09 at 21:14 +, Gary Buhrmaster wrote:
> On Mon, Nov 9, 2020 at 9:04 PM Sérgio Basto
> wrote:
>
> > Like tftp we may replace xinetd by systemd service files [1] ,
> > if we replace cvs-inetd by a systemd service, the problem is
> > solved.
>
> I am pretty sure cvs already ship
On Mon, Nov 9, 2020 at 9:32 PM Todd Zullinger wrote:
> Hi,
>
> Sérgio Basto wrote:
> > Like tftp we may replace xinetd by systemd service files [1] ,
> > if we replace cvs-inetd by a systemd service, the problem is solved.
> >
> > [1]
> >
> https://src.fedoraproject.org/rpms/tftp/c/15a26fcde8a007
Hi,
Sérgio Basto wrote:
> Like tftp we may replace xinetd by systemd service files [1] ,
> if we replace cvs-inetd by a systemd service, the problem is solved.
>
> [1]
> https://src.fedoraproject.org/rpms/tftp/c/15a26fcde8a0078766b6bbba183d89f920e51535?branch=master
The cvs package has suppo
On Mon, Nov 9, 2020 at 9:04 PM Sérgio Basto wrote:
> Like tftp we may replace xinetd by systemd service files [1] ,
> if we replace cvs-inetd by a systemd service, the problem is solved.
I am pretty sure cvs already ships systemd service files.
The issue is that there is also a sub-package buil
On Mon, 2020-11-09 at 16:59 +, Richard W.M. Jones wrote:
> On Mon, Nov 09, 2020 at 11:50:06AM -0500, Todd Zullinger wrote:
> > Hi,
> >
> > Richard W.M. Jones wrote:
> > > On Mon, Nov 09, 2020 at 11:17:38AM -0500, Todd Zullinger wrote:
> > > > The cvs and cvsps BR's are for the test suite, sinc
On Mon, Nov 09, 2020 at 11:50:06AM -0500, Todd Zullinger wrote:
> Hi,
>
> Richard W.M. Jones wrote:
> > On Mon, Nov 09, 2020 at 11:17:38AM -0500, Todd Zullinger wrote:
> >> The cvs and cvsps BR's are for the test suite, since we
> >> prefer to use the comprehensive test suite that git
> >> include
On Mon, Nov 09, 2020 at 04:46:39PM +, Sven Kieske wrote:
> On Mo, 2020-11-09 at 14:10 +0100, Robert-André Mauchin wrote:
> > On Monday, 9 November 2020 12:09:00 CET you wrote:
> > > numad orphan 1 weeks
> > > ago
> >
> > Any maintainer of l
Hi,
Richard W.M. Jones wrote:
> On Mon, Nov 09, 2020 at 11:17:38AM -0500, Todd Zullinger wrote:
>> The cvs and cvsps BR's are for the test suite, since we
>> prefer to use the comprehensive test suite that git
>> includes. So dropping those BR's is not a useful option.
>
> The test suite still r
On Mo, 2020-11-09 at 14:10 +0100, Robert-André Mauchin wrote:
> On Monday, 9 November 2020 12:09:00 CET you wrote:
> > numad orphan 1 weeks
> > ago
>
> Any maintainer of libvirt interested in taking this or breaking the
> dependency
> link?
On Mon, Nov 09, 2020 at 11:17:38AM -0500, Todd Zullinger wrote:
> Hi,
>
> Richard W.M. Jones wrote:
> > On Mon, Nov 09, 2020 at 12:09:00PM +0100, Miro Hrončok wrote:
> >> rjones: xinetd, numad
> >
> > Your "packager dashboard"[1] which I found for the first time today is
> > very useful!
> >
> >
Hi,
Richard W.M. Jones wrote:
> On Mon, Nov 09, 2020 at 12:09:00PM +0100, Miro Hrončok wrote:
>> rjones: xinetd, numad
>
> Your "packager dashboard"[1] which I found for the first time today is
> very useful!
>
> Turns out the problem for my package is this weird ol' dependency chain:
>
> coc
On Monday, 9 November 2020 12:09:00 CET you wrote:
> numad orphan 1 weeks
> ago
Any maintainer of libvirt interested in taking this or breaking the dependency
link?
Best regards,
Robert-André
___
On Mon, Nov 9, 2020 at 12:25 PM Wolfgang Ulbrich wrote:
> > Affected (co)maintainers (either directly or via packages' dependencies):
>
> < cut >
> > raveit65: sgpio
>
> I am still wondering why i am listed here as (co)maintainers.
> I do not maintain this package.
>
> Cheers
> Wolfgang
>
It is
> Affected (co)maintainers (either directly or via packages' dependencies):
< cut >
> raveit65: sgpio
I am still wondering why i am listed here as (co)maintainers.
I do not maintain this package.
Cheers
Wolfgang
___
devel mailing list -- devel@lists.fe
On 11/9/20 12:55 PM, Richard W.M. Jones wrote:
Turns out the problem for my package is this weird ol' dependency chain:
coccinelle -> git -> cvs -> xinetd
Well the first part of that is understandable, because Cocci uses git
to apply patches (ie. autosetup -S git).
cvs -> xinetd is sort of
On Mon, Nov 09, 2020 at 12:09:00PM +0100, Miro Hrončok wrote:
> rjones: xinetd, numad
Your "packager dashboard"[1] which I found for the first time today is
very useful!
Turns out the problem for my package is this weird ol' dependency chain:
coccinelle -> git -> cvs -> xinetd
Well the first
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:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If
Michael J Gruber wrote:
>> = NOTE about xinetd =
>>
>> Many packagers are listed as affected by xinetd. The dependency chain is:
>>
>> cvs (kasal, ppisar)
>> cvs-inetd.noarch requires xinetd
>>
>> git (amahdal, besser82, chrisw, pcahyna, pstodulk, skisela, tmz)
>>
On 02/11/2020 12.27, Miro Hrončok wrote:
On 11/2/20 12:13 PM, Fabio M. Di Nitto wrote:
On 02/11/2020 12.03, 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
On 11/2/20 12:13 PM, Fabio M. Di Nitto wrote:
On 02/11/2020 12.03, 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
> = NOTE about xinetd =
>
> Many packagers are listed as affected by xinetd. The dependency chain is:
>
> cvs (kasal, ppisar)
> cvs-inetd.noarch requires xinetd
>
> git (amahdal, besser82, chrisw, pcahyna, pstodulk, skisela, tmz)
> git.src requires
On Mon, Nov 02, 2020 at 12:13:18PM +0100, Fabio M. Di Nitto wrote:
> On 02/11/2020 12.03, 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 ret
On 02/11/2020 12.03, 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:
https://fedoraproject.org/wiki/How_t
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:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If
32 matches
Mail list logo
