On Wed, 2016-08-31 at 00:19 +, Sean Whitton wrote:
> The nice thing about the homepage being there is that the user can get
> it by running `apt-cache show foo`. Unless you plan to pull in that
> information when building the binary package?
It woudn't need to be present when building the bi
Hello,
On Tue, Aug 30, 2016 at 02:56:07PM +0100, Martin List-Petersen wrote:
> I'm currently not an active maintainer within Debian, but freeradius is
> essential (also to what i do), so I will have a go at it.
On Tue, Aug 30, 2016 at 05:21:17PM +0200, Vito Mulè wrote:
> I'm also interested.
>
>
Hello,
On Tue, Aug 30, 2016 at 10:20:21AM +0800, Paul Wise wrote:
> On Tue, Aug 30, 2016 at 1:56 AM, Niels Thykier wrote:
>
> > Frankly, I do not think that the source package is the correct place for
> > the Maintainer / Uploaders data. There are plenty of cases where it
> > would make sense to
would like to suggest running
> the rebuild with those patches.
>
> I think Matthias would be OK with the patch since it is very small and brings
> Debian's gcc closer to Ubuntu's.
>
> Lucas, could you please run the rebuild with the three patches?
Hi,
Results are ava
Package: wnpp
Severity: wishlist
Owner: Mike Gabriel
* Package name: credential-sheets
Version : 0.0.2
Upstream Author : Mike Gabriel
* URL : https://github.com/sunweaver/credential-sheets
* License : GPL
Programming Lang: Perl
Description : User accou
Hi,
I am an active porter for the following architectures and I intend
to continue this for the lifetime of the Stretch release (est. end
of 2020):
For ppc64el, I
- test most packages on this architecture
- run a Debian testing or unstable system on port that I use regularly
- triage arch-specifi
Hi,
I am an active porter for the following architectures and I intend
to continue this for the lifetime of the Stretch release (est. end
of 2020):
For mips, mipsel and mips64el, I
- test most packages on this architecture
- run a Debian testing or unstable system on port that I use
Sorry for the previous post without signature.
Hi,
I am an active porter for the following architectures and I intend
to continue this for the lifetime of the Stretch release (est. end
of 2020):
For mips, mipsel and mips64el, I
- test most packages on this architecture
- run a Debi
]] Jonathan de Boyne Pollard
> Russ Allbery:
>
> > I think that... says the same thing I said?
> >
> Read again, and let your eye dwell upon Laurent Bercot's name this
> time. (-: The world has changed since 2014 and the Debian systemd
> packaging Hoo-Hah, and I've been keeping tabs.
s6 doesn
>Hi,
>I'm currently not an active maintainer within Debian, but freeradius is
>essential (also to what i do), so I will have a go at it.
>Kind regards,
>Martin List-Petersen
Hello,
I'm also interested.
I wanted to get into being a Debian Maintainer for a long time. I
think this could be th
On 30/08/16 14:43, Raphael Hertzog wrote:
[ Bcc debian-mentors ]
Hello,
following the recent discussions in #806617 it has become apparent that
we need a new maintainer for freeradius. Debian still has version
2.2.x when upstream is now on 3.0.x.
Is there anyone interested?
It would be a pity
[ Bcc debian-mentors ]
Hello,
following the recent discussions in #806617 it has become apparent that
we need a new maintainer for freeradius. Debian still has version
2.2.x when upstream is now on 3.0.x.
Is there anyone interested?
It would be a pity to see freeradius gone from Debian.
Cheers
Russ,
On Tue, Aug 30, 2016 at 01:24:44AM -0700, Russ Allbery wrote:
[...]
> It's kind of a perfect storm. It makes sense if you sit down and
> enumerate the reasons, but it's still kind of amazing just how much of a
> perfect storm it is.
*g*
[...]
> TL;DR: I fear this init system is going to g
On 08/30/2016 09:43 AM, Holger Levsen wrote:
> Hi,
>
> http://www.jonobacon.org/2016/08/29/linux-linus-bradley-open-source-protection/
> just popped up in my rss feed and I thought I'd share it with you… it's
> a comment on the recent GPL enforcement debate on the (upstream) kernel
> list.
>
>
Russ Allbery:
I think that... says the same thing I said?
Read again, and let your eye dwell upon Laurent Bercot's name this
time. (-: The world has changed since 2014 and the Debian systemd
packaging Hoo-Hah, and I've been keeping tabs.
* https://jdebp.eu./FGA/unix-daemon-readiness-proto
retitle 809158 ITP: gajim-plugin-omemo -- Gajim plugin for OMEMO Multi-End
Message and Object Encryption
thanks
Update: New homepage, new version
* Package name: gajim-plugin-omemo
Version : 0.9.0 / 2016-08-28
Upstream Author : Bahtiar Gadimov
* URL : https://github.
[2016-08-29 18:30] Russ Allbery
>
> part text/plain1918
> Dmitry Bogatov writes:
>
> > Socket is not bad thing. Inventing daemon for no reason is complicating
> > things for no reason => bad. Thanks history, we have pid files, not
> > `libpid' to talk to `pidd'.
>
> Uh, the
[2016-08-30 08:55] Jonathan de Boyne Pollard
>
> part text/plain 198
> Dmitry Bogatov:
>
> > Thanks history, we have pid files, not `libpid' to talk to `pidd'.
> >
> You have forgotten about the existence of Debian Hurd. (-:
I like Hurd idea, but I was talking about Linux
Jonathan de Boyne Pollard, on Tue 30 Aug 2016 08:55:26 +0100, wrote:
> >Thanks history, we have pid files, not `libpid' to talk to `pidd'.
> >
> You have forgotten about the existence of Debian Hurd. (-:
The Hurd precisely tries to expose things as files.
Samuel
Marc Haber writes:
> Russ Allbery wrote:
>> Debian historically tries to handle these situations by just providing
>> everything simultaneously. The debate over init systems is as heated
>> as it is because it's quite difficult to do a good job at supporting
>> multiple init systems.
> And bec
Dmitry Bogatov:
Thanks history, we have pid files, not `libpid' to talk to `pidd'.
You have forgotten about the existence of Debian Hurd. (-:
* https://jdebp.eu./FGA/hurd-daemons.html#proc
Hi,
http://www.jonobacon.org/2016/08/29/linux-linus-bradley-open-source-protection/
just popped up in my rss feed and I thought I'd share it with you… it's
a comment on the recent GPL enforcement debate on the (upstream) kernel
list.
I basically agree with Jono here.
--
cheers,
Holger
On Mon, 29 Aug 2016 20:18:49 -0700, Russ Allbery
wrote:
>Debian historically tries to handle these situations by just providing
>everything simultaneously. The debate over init systems is as heated as
>it is because it's quite difficult to do a good job at supporting multiple
>init systems.
And
23 matches
Mail list logo
