Hi,
I've just uploaded version 10.43-1 of pcre2 to experimental. There are
quite a few changes from 10.42, summarised by upstream in NEWS:
https://salsa.debian.org/debian/pcre2/-/blob/master/NEWS
I'll do an upload to unstable in due course, assuming no show-stoppers
are found :)
Regards,
M
Hi,
On 21/12/2023 09:41, Helmut Grohne wrote:
Is it ok to call upgrade scenarios failures that cannot be reproduced
using apt unsupported until we no longer deal with aliasing?
I incline towards "no"; if an upgrade has failed part-way (as does
happen), people may then reasonably use dpkg dir
Luca Boccassi writes:
> On Thu, 9 Nov 2023 at 22:54, Benjamin Barenblat wrote:
>> What would you think about having coreutils Depend on libssl3? This
>> would make the libssl3 package essential, which is potentially
>> undesirable, but it also has the potential for serious user time savings
>>
Andreas Henriksson writes:
> If you want me to take suggestions like coordination seriously then
> please consider adressing https://bugs.debian.org/934463 soon or admit
> that sysvinit maintenance lacks the resources to do coordinated
> transitions. Dropping things and letting people pick them u
Alastair McKinstry writes:
>> On Thu, Jun 29, 2023 at 08:55:11PM +0100, Matthew Vernon wrote:
>>> Bookworm is now out; I will shortly be increasing the severity of
>>> the outstanding bugs to RC, with the intention being to remove
>>> src:pcre3 from Debian
Hi,
On 13/11/2021 11:41, Matthew Vernon wrote:
TL;DR> pcre3 is obsolete and upstream don't want to fix it any more. I
propose a MBF to track our progress in getting rid of it for Bookworm
Bookworm is now out; I will shortly be increasing the severity of the
outstanding bugs to RC,
Marco d'Itri writes:
> On Jun 22, Martin-Éric Racine wrote:
>
>> The point has always been to ship some ifupdown-supported DHCP client
>> by default. This can be done either by keeping the default client's
>> priority to important or by making ifupdown Depends on one. I prefer
>> the later.
> I
Ansgar writes:
> I think this should be NetworkManager for desktop environments and I
> personally like systemd-networkd for other environments. In both cases
> these replace both ifupdown and isc-dhcp-client.
We might be using slightly different terms, but for desktops I still
tend to use ifupd
On 26/05/2023 09:24, Luca Boccassi wrote:
On Fri, 26 May 2023 at 08:39, Matthew Vernon wrote:
Consider: it is consistent to believe that it would have been better for
dpkg not to have had that warning added (quite some time ago now), but
that by now most derivatives that care will likely
Hi,
On 26/05/2023 07:03, Ansgar wrote:
On Wed, 2023-05-10 at 14:36 -0700, Russ Allbery wrote:
Ansgar writes:
Debian going out of its way to tell derivative users to switch back from
merged-/usr to split-/usr is the *opposite* of trying to make things as
smooth for them as possible.
Yes, I a
Hi,
Perry Naseck writes:
> I am in the process of updating/upgrading a package from an init.d service
> to a Systemd service. Are there any recommended guidelines for this process?
>
> Looking through some current packages I see that a lot of them have both an
> init script and a Systemd service
Package: wnpp
Severity: wishlist
Owner: Matthew Vernon
Control: block 1001261 by -1
Control: block 1024445 by -1
X-Debbugs-CC: debian-devel@lists.debian.org, debian...@lists.debian.org
* Package name: golang-github-jcmturner-rpc.v2
Version : 2.0.3-1
Upstream Author : Jonathan
Package: wnpp
Severity: wishlist
Owner: Matthew Vernon
Control: block 1001261 by -1
Control: block 1024445 by -1
X-Debbugs-CC: debian-devel@lists.debian.org, debian...@lists.debian.org
* Package name: golang-github-jcmturner-goidentity.v6
Version : 6.0.1-1
Upstream Author
Package: wnpp
Severity: wishlist
Owner: Matthew Vernon
Control: block 1001261 by -1
Control: block 1024445 by -1
X-Debbugs-CC: debian-devel@lists.debian.org, debian...@lists.debian.org
* Package name: golang-github-jcmturner-dnsutils.v2
Version : 2.0.0-1
Upstream Author
Package: wnpp
Severity: wishlist
Owner: Matthew Vernon
Control: block 1001261 by -1
Control: block 1024445 by -1
X-Debbugs-CC: debian-devel@lists.debian.org, debian...@lists.debian.org
* Package name: golang-github-jcmturner-aescts.v2
Version : 2.0.0-1
Upstream Author : Jonathan
Bastian Blank writes:
> On Wed, Mar 09, 2022 at 01:08:59PM +0100, Lucas Nussbaum wrote:
>> can we find a middleground where the git workflows don't require staying
>> with 1.0? Even if that means switching to 3.0 (quilt) using the
>> single-debian-patch approach?
>
> Well. There is a specific so
Andrey Rahmatullin writes:
> On Tue, Mar 15, 2022 at 10:49:17AM +0000, Matthew Vernon wrote:
>> but even if it were, is that an entirely unreasonable position for a
>> package maintainer (or team thereof) to take?
> Probably not? Just yet another case where you need t
Andrey Rahmatullin writes:
> On Tue, Mar 15, 2022 at 08:54:50AM +0000, Matthew Vernon wrote:
>> It's probably unfashionable, but I think debian/patches is not a great
>> way to manage changes, particularly if you're using a VCS for
>> maintaining your packages. As
Hi,
Lucas Nussbaum writes:
[bit late to this thread; came here when I got some MBF bugs and saw
"make them Severity: serious..." in the linked mail. I think in this
case use of source format 1.0 isn't against policy, _shouldn't_ be
against policy (or at least, not in all cases), and that de fact
Matthew Vernon writes:
> User: matthew-pcre...@lists.debian.org
Sigh, always one typo gets through. That should be:
User: matthew-pcre...@debian.org
Regards,
Matthew
--
"At least you know where you are with Microsoft."
"True. I just wish I'd brought a paddle."
http://www.debian.org
Hi,
TL;DR> pcre3 is obsolete and upstream don't want to fix it any more. I
propose a MBF to track our progress in getting rid of it for Bookworm
PCRE is the perl-compatible regular expression library,
https://pcre.org/ For historical reasons, the old PCRE library ended up
as libpcre3 in Debi
Matthew Vernon writes:
> I've uploaded 10.35-1 of pcre2 to experimental; I'll upload -2 to
> unstable next weekend if there aren't any show-stoppers in the mean
> time.
>
> We may yet see 10.36 out in time for it to get into bullseye (upstream
> have an RC), b
Hi,
I've uploaded 10.35-1 of pcre2 to experimental; I'll upload -2 to
unstable next weekend if there aren't any show-stoppers in the mean time.
We may yet see 10.36 out in time for it to get into bullseye (upstream
have an RC), but I wanted 10.35 in in case that doesn't work out.
Regards,
Scott Kitterman writes:
> On May 7, 2019 8:50:57 PM UTC, Sam Hartman wrote:
>>> "Ian" == Ian Jackson writes:
>>Ian> The latter point is because using dgit push is an ethical
>>Ian> imperative, not because the two somehow have some deep
>> Ian> technical linkage. IMO almost *any*
Josh Triplett writes:
> Ian Jackson wrote:
>> Stepping back a bit I think the ideal situation is this:
>>
>> * All packages have sysvinit scripts for compatibility.
>
> Preferably in a package maintained by someone who actually uses that
> daemon with sysvinit, rather than one maintained by some
Marco d'Itri writes:
> In the worst case it will fail explaining that some local change (in
> a directory which should not have been modified by the local admin, BTW)
> needs to be addressed by the local admin and then it can be restarted
> and continue its work.
Could you expand on this? I'm r
Hi,
Adam Borowski writes:
FTR, I agree with the broad thrust of your mail; I'm not sure I've seen
a convincing case for /usr-merge yet.
> I am seriously claiming that RHEL is in the place Solaris was in 2010.
But I want to take issue with this. RHEL is moderately-widely used,
because if you w
Ian Jackson writes:
> Matthew Vernon writes ("Re: salsa.debian.org: merge requests and such"):
>> Colin Watson writes:
>> > This seems like a little bit of an overreaction to somebody removing a
>> > single redundant line from a control file, though. Is
Jonathan Dowland writes:
> On Fri, Nov 09, 2018 at 11:54:50AM +0000, Matthew Vernon wrote:
>>Putting it under a personal namespace doesn't make it much less visible,
>>and folk can still open MRs...
>
> Oh I beg to differ, there's a huge difference of visibil
Colin Watson writes:
> On Fri, Nov 09, 2018 at 11:54:50AM +0000, Matthew Vernon wrote:
>> Jonathan Dowland writes:
>> > On Tue, Nov 06, 2018 at 03:42:01PM +0000, Matthew Vernon wrote:
>> >>Hm, I had not quite appreciated that was the expected behaviou
Jonathan Dowland writes:
> On Tue, Nov 06, 2018 at 03:42:01PM +0000, Matthew Vernon wrote:
>>Hm, I had not quite appreciated that was the expected behaviour. Ah
>>well, I can move it :)
>
> Please re-consider whether this trade-off (other people pushing to
> master) is
On 06/11/2018 15:32, Guillem Jover wrote:
> Because, I'm not sure what's the point of hosting a git repo, on a
> platform like gitlab with its trivial forking facilities, on a group
> with wide write permissions, if you don't want others to directly
> write to it? :)
Hm, I had not quite appreciat
Jacob Adams writes:
> The consensus seems to be that people should enable email
> notifications in salsa and open a bug when filing a merge request.
>
> https://lists.debian.org/debian-devel/2018/08/msg00235.html
>
> https://lists.debian.org/debian-devel/2018/08/msg00259.html
Relatedly, what's
Ian Jackson writes:
> Also we are hampered by the lack of a safe space to communicate and
> coordinate. I looked at some of the technical work done in other
> distros to try to make desktoppy stuff continue to work well, and it
> generally seems sane. But some of those projects are quite toxic
Holger Levsen writes:
> On Sat, Oct 13, 2018 at 06:01:43AM +0100, Ben Hutchings wrote:
>> > Has policy changed regarding support for multiple inits, or is it just that
>> > no one is maintaining the shim and sysvinit-core?
>>
>> The latter. systemd-shim has been orphaned for over 2 years, and h
Stephan Seitz writes:
> On Di, Jul 24, 2018 at 11:49:55 +0100, Matthew Vernon wrote:
>>accept that they are authoritative in this regard. Therefore, you should
>>rename the offensive parts of this package.
>
> He certainly should NOT rename any parts of the package witho
Hi,
"Marc Dequènes (duck)" writes:
[snip]
> So apart from objectification of women, but without
> instrumentalization or degrading message, I was not able to find
> serious consequences. As much as I would prefer things to be different
> (I already told upstream in the past) I don't feel I have
Jonathan Dowland writes:
> I think we ought to more concretely determine what changes we wish to
> take place. To do this properly I need to spend more time looking at the
> package in more detail, so what follows is just my initial feelings. I
> welcome feedback. For now I suggest we hash it out
"Marc Dequènes (duck)" writes:
> It has been brought to my attention that this package, its name and
> the name of the binaries and further content was deemed
> offensive. This was already raised in the past (~2012 IIRC) but the
> package was reintroduced and has been in the archive since then.
Ralf Treinen writes:
> I had a cursory look over the listed maintainer scripts, and did not
> find any that does a careful checking of exit statuses. Though some
> of them are quite trivial, or even sometimes empty. It looks to me
> as not using strict mode in these cases is an oversight, and I w
Package: wnpp
Severity: wishlist
Owner: Matthew Vernon
* Package name: pcre2
Version : 10.20
Upstream Author : Philip Hazel
* URL : http://www.pcre.org/
* License : BSD
Programming Lang: C
Description : New Perl Compatible Regular Expression Library
Hi,
Simon Richter writes:
> Hi Matthew,
>
> On 22.10.2015 16:47, Matthew Vernon wrote:
>
> > Upstream has a new PCRE library, which they hope everyone will
> > eventually migrate to, which is called PCRE2. It is currently version
> > 10.20. It ships things named
Hi,
PCRE has been in Debian for some time; the current packages correspond
to upstream 8.35 (with a pile of backported security fixes, which I hope
will end up as an 8.38 release some time soon). These packages are
called pcre3 (and libpcre3 ships libpcre.so.3).
Upstream has a new PCRE library, w
Simon McVittie writes:
> On 24/11/14 11:42, Svante Signell wrote:
> > A question remains (for me):
> > How to build a package in a clean jessie environment? Seems like the
> > buildds are using sbuild.
>
> Have a minimal jessie chroot with build-essential, and a minimum of
> supporting tools to
Dominic Hargreaves writes:
> I've agreed to give a one day Debian packaging workshop at $dayjob aimed at
> sysadmins and developers, and I'd be interested in hearing from those who
> have already run similar sessions to get advice/tips for how to approach
> such a thing. Would there be any intere
Package: wnpp
Severity: wishlist
Owner: Matthew Vernon
Package name: rsbackup
Version : 0.4.3
Upstream Author : Richard Kettlewell
URL : http://www.greenend.org.uk/rjk/2010/rsbackup.html
License : GPL
Programming Lang: C++
Description : rsync
Package: wnpp
Severity: wishlist
Owner: Matthew Vernon
Package name: libshib-common-java
Version : 2.4.0
Upstream Author : University Corporation for Advanced Internet Development,
Inc.
URL : http://shibboleth.net/shibboleth-common
License : Apache-2.0
Package: wnpp
Severity: wishlist
Owner: Matthew Vernon
Package name: libshib-parent-project2-java
Version : 1
Upstream Author : University Corporation for Advanced Internet Development,
Inc.
URL : http://shibboleth.net/
License : Apache-2.0
Package: wnpp
Severity: wishlist
Owner: Matthew Vernon
Package name: libvt-ldap-java
Version : 3.3.7
Upstream Author : Middleware Services
URL : http://code.google.com/p/vt-middleware/wiki/vtldap
License : LGPL-3 or Apache-2.0
Programming Lang: Java
Package: wnpp
Severity: wishlist
Owner: Matthew Vernon
Package name: libowasp-esapi-java
Version : 2.1.0
Upstream Author : Jeff Williams
URL : https://code.google.com/p/owasp-esapi-java/
License : BSD (documentation CC-BY-SA-3.0)
Programming Lang
Package: wnpp
Severity: wishlist
Owner: Matthew Vernon
Package name: libowasp-antisamy-java
Version : 1.5.3
Upstream Author : Arshan Dabirsiaghi
URL : https://code.google.com/p/owaspantisamy/
License : BSD
Programming Lang: Java
Description
[nothing in this email is private]
On 18 Sep 2008, at 11:53, Holger Levsen wrote:
Hi,
On Thursday 18 September 2008 06:57, Jimmy Kaplowitz wrote:
Except that, as reported by Jimmy, the version of the open use
logo with
the "Debian" name *does* suffer from this problem; which I think
is a
On 23 Oct 2007, at 15:04, Lars Wirzenius wrote:
ti, 2007-10-23 kello 12:35 +0100, Matthew Vernon kirjoitti:
The Authorized Version of the Bible isn't covered by Copyright in
the
conventional sense. The Queen's Printer (currently Cambridge
University Press) has an exclusive commercia
t meant
to print and sell Bibles in England, but no action has been taken
against them. It's not at all clear whether electronic copies are
covered.
Matthew
[1] http://www.btinternet.com/~akme/75cass1b.html
--
Matthew Vernon MA VetMB LGSM MRCVS
Farm Animal Epidemiology and Informatics Uni
Amaya <[EMAIL PROTECTED]> writes:
> Hi there, fellow DDs, Debian enthusiasts and groff experts,
>
> I am looking at #394635. My eyes are starting to bleed. This bug is not
> even RC, but it is ugly, and I would hate to ship Etch with it.
>
> All the man pages for this package use macros, sitting
Manoj Srivastava <[EMAIL PROTECTED]> writes:
> Hi,
>
> Three days ago, I sent in a patch in Bug#394795 which updated
> SELinux patches to bring 'em in line with currently released SELinux
> code in Debian. I updated that patch [0], and the binaries were
I know nothing about SELinux,
Stephen Zander writes:
> > "Vincent" == Vincent Renardias <[EMAIL PROTECTED]> writes:
> Vincent> short summary: lilo v22 works only with 2.0 kernels; it
> Vincent> won't boot a 2.2.x or a 2.3.y. a v21 version has been
> Vincent> reuploaded to master this morning.
>
> Hmmm, s
Marek Habersack writes:
> Hi,
>
> Latest potato update contains a package, aleph-dev, with a wrong Priority:
> line which prevents (until manually fixed) the apt update operation, which
> aborts with:
>
> E: Malformed Priority line
> E: Error occured while processing aleph-dev (NewVers
Rene Mayrhofer writes:
> portsentry is a daemon that listens for port scans (also stealth scans)
> and is able to disconnect and remember the attacking hosts in real-time.
> It uses ipchains for disconnecting and tcp wrappers for preventing hosts
> from further connections.
> Please look at ht
David Starner writes:
> On Fri, Sep 24, 1999 at 05:59:27PM -0400, Jaldhar H. Vyas wrote:
> > Nevertheless it is moot point because we are running out of room and there
> > has to be a third CD. It might as well contain all the documents and
> > other packages non-essential to using an OS.
> >
Russell Coker writes:
> On Fri, 24 Sep 1999, Karl M. Hegbloom wrote:
> >I'd love to go to the conference. Let's go to Redmond and infiltrate
> > Microsoft, or to the Portland area and infiltrate Intel.
> >
> > I'll hike there if I have to. I don't mind sleeping bag
> > accomodations; I'm
Samuel Tardieu writes:
> On 23/09, Marco d'Itri wrote:
>
> | I see no point in checking signatures if you don't also reject unsigned
> | messages.
>
> For me, a message with no signature is a message with a bad signature :)
This is all very well, except for those of us who email from work,
62 matches
Mail list logo
