On Wed, 2017-12-13 at 13:31 +0100, Tomas Popela wrote:
> On Wed, Dec 13, 2017 at 1:17 PM, Sérgio Basto
> wrote:
> > On Wed, 2017-12-13 at 12:58 +0100, Tomas Popela wrote:
> > > On Wed, Dec 13, 2017 at 11:54 AM, Sérgio Basto > >
> > > wrote:
> > > > BTW , I checked debian package and they build we
On Wed, Dec 13, 2017 at 1:17 PM, Sérgio Basto wrote:
> On Wed, 2017-12-13 at 12:58 +0100, Tomas Popela wrote:
> > On Wed, Dec 13, 2017 at 11:54 AM, Sérgio Basto
> > wrote:
> > > BTW , I checked debian package and they build webkit2gtk3 and
> > > webkit2gtk2 [1] and also his naming looks better ;
On Wed, 2017-12-13 at 12:58 +0100, Tomas Popela wrote:
> On Wed, Dec 13, 2017 at 11:54 AM, Sérgio Basto
> wrote:
> > BTW , I checked debian package and they build webkit2gtk3 and
> > webkit2gtk2 [1] and also his naming looks better ;) (webkit2gtk-
> > 4.0) .
> > So I would suggest webkit2gtk3-4.0
On Wed, Dec 13, 2017 at 11:54 AM, Sérgio Basto wrote:
> BTW , I checked debian package and they build webkit2gtk3 and webkit2gtk2
> [1] and also his naming looks better ;) (webkit2gtk-4.0) .
> So I would suggest webkit2gtk3-4.0 , webkit2gtk2-4.0 and webkit2gtk4-4.0
>
Just a note - there is nothi
On Wed, 2017-12-13 at 07:00 +0100, Tomas Popela wrote:
> Hi,
>
> On Sat, Dec 9, 2017 at 5:06 PM, Neal Gompa
> wrote:
> > On Fri, Dec 8, 2017 at 10:16 PM, Sérgio Basto
> > wrote:
> > > Thank you Michael , btw about package naming IMHO webkitgtk4
> > should be
> >
> > > called webkit2gtk3 and for
Hi,
On Sat, Dec 9, 2017 at 5:06 PM, Neal Gompa wrote:
> On Fri, Dec 8, 2017 at 10:16 PM, Sérgio Basto wrote:
> > Thank you Michael , btw about package naming IMHO webkitgtk4 should be
> > called webkit2gtk3 and for gtk4 webkit2gtk4
> >
>
> The webkitgtk4-devel package already provides pkgconfig
On Fri, Dec 8, 2017 at 10:16 PM, Sérgio Basto wrote:
> On Thu, 2017-12-07 at 23:26 +, Sérgio Basto wrote:
>> On Wed, 2017-12-06 at 16:19 -0800, Adam Williamson wrote:
>> > On Thu, 2017-12-07 at 00:04 +, Sérgio Basto wrote:
>> > >
>> > > hum Markdown plugin is build with GTK3 , the plus of
On Thu, 2017-12-07 at 23:26 +, Sérgio Basto wrote:
> On Wed, 2017-12-06 at 16:19 -0800, Adam Williamson wrote:
> > On Thu, 2017-12-07 at 00:04 +, Sérgio Basto wrote:
> > >
> > > hum Markdown plugin is build with GTK3 , the plus of GTK+ is
> > > confusing
> > > me
> >
> > GTK+ is the corr
On Wed, 2017-12-06 at 16:19 -0800, Adam Williamson wrote:
> On Thu, 2017-12-07 at 00:04 +, Sérgio Basto wrote:
> >
> > hum Markdown plugin is build with GTK3 , the plus of GTK+ is
> > confusing
> > me
>
> GTK+ is the correct name of the project and the product. It is not
> called GTK. "GTK+
On Thu, 2017-12-07 at 00:04 +, Sérgio Basto wrote:
>
> hum Markdown plugin is build with GTK3 , the plus of GTK+ is confusing
> me
GTK+ is the correct name of the project and the product. It is not
called GTK. "GTK+ 3" and "GTK 3" refer to the same thing, and "GTK+ 3"
is technically the corr
On Mon, 2017-11-20 at 09:03 -0600, Michael Catanzaro wrote:
> webkitgtk4: This package is the modern version of WebKitGTK+
> (currently
> 2.18.3). It's the only version that you should be using. It exposes
> a
> newer multiprocess API. The "4" in the package name is related to
> the
> API versio
On Mon, Nov 20, 2017 at 5:59 AM, Sérgio Basto
wrote:
Please remember me what is the difference of webkitgtk, webkitgtk3
and webkitgtk4 ?
The package names are very confusing, sorry.
webkitgtk: This package is WebKitGTK+ 2.4 built with the original
WebKitGTK+ API, for use by GTK+ 2 applicatio
On Fri, 2017-07-07 at 11:34 -0500, Michael Catanzaro wrote:
> On Fri, Jul 7, 2017 at 8:08 AM, Vít Ondruch
> wrote:
> > It does not seems to be properly retired in pkgdb [1], although it
> > seem
> > to be retired in dist-git [2].
> >
> >
> > BTW what is the state of Empathy which is broken by
On Fri, Jul 7, 2017 at 8:08 AM, Vít Ondruch
wrote:
It does not seems to be properly retired in pkgdb [1], although it
seem
to be retired in dist-git [2].
BTW what is the state of Empathy which is broken by this retirement :(
Upstream master is ported to WK2, but there are bugs that need fix
It does not seems to be properly retired in pkgdb [1], although it seem
to be retired in dist-git [2].
BTW what is the state of Empathy which is broken by this retirement :(
Vít
[1] https://admin.fedoraproject.org/pkgdb/package/rpms/webkitgtk3/
[2]
http://pkgs.fedoraproject.org/cgit/rpms/w
On Tue, 2017-04-18 at 19:20 -0700, Adam Williamson wrote:
> fedora-obsolete-packages.
>
> https://fedoraproject.org/wiki/Packaging:Guidelines#Renaming.2FReplac
> ing_Existing_Packages
OK, I filed this request:
https://bugzilla.redhat.com/show_bug.cgi?id=1443614
Michael
_
On Tue, 2017-04-18 at 21:01 -0500, Michael Catanzaro wrote:
> On Tue, 2017-04-18 at 18:03 -0700, Adam Williamson wrote:
> > It seems that nothing has been set to obsolete these packages. This
> > is
> > breaking upgrade from Fedora 24 to Fedora 27 (without --allow-
> > erasing),
> > since webkitgtk
On Tue, 2017-04-18 at 18:03 -0700, Adam Williamson wrote:
> It seems that nothing has been set to obsolete these packages. This
> is
> breaking upgrade from Fedora 24 to Fedora 27 (without --allow-
> erasing),
> since webkitgtk3 is installed by default in many Fedora 24 package
> sets, and is built
On Mon, 2017-01-23 at 07:35 -0600, Michael Catanzaro wrote:
> Hi,
>
> This is a reminder that the webkitgtk and webkitgtk3 packages will be
> retired from rawhide shortly after F26 is branched from rawhide. This
> is due to numerous security issues affecting those packages (I just
> counted 204 CV
On Wed, 2017-03-22 at 09:48 -0600, Kevin Fenzi wrote:
> I could have sworn FESCo discussed and approved this plan, but I
> cannot
> seem to find it. I guess it might have been discussed, but didn't
> have a
> ticket. If needed we could discuss it at the next meeting.
I never created a ticket, and
On 03/22/2017 09:40 AM, Michael Catanzaro wrote:
>
> You have to make a request to releng, as Neal says. I hope that releng
> will not approve such a request without a decision on the matter from
> FESCo, since this would entail reintroducing a security-critical
> package to the distribution that
On Wed, 2017-03-22 at 18:28 +0300, Pete Walter wrote:
> I would like to unretire webkitgtk3 as removing it breaks one of my
> packages (bijiben). My intention is to keep maintaining the
> webkitgtk3 package until bijiben gets ported to something else.
I recommend publishing a git snapshot of bijib
On Wed, Mar 22, 2017 at 11:28 AM, Pete Walter wrote:
> Looks like this was done without involving FESCo and without going through a
> proper Change process. I don't think it's a proper way to approach it like
> this as it breaks a large part of the distro.
>
> I would like to unretire webkitgtk3
Looks like this was done without involving FESCo and without going through a
proper Change process. I don't think it's a proper way to approach it like this
as it breaks a large part of the distro.
I would like to unretire webkitgtk3 as removing it breaks one of my packages
(bijiben). My intent
On Mon, 2017-01-23 at 07:35 -0600, Michael Catanzaro wrote:
> Hi,
>
> This is a reminder that the webkitgtk and webkitgtk3 packages will be
> retired from rawhide shortly after F26 is branched from rawhide. This
> is due to numerous security issues affecting those packages (I just
> counted 204 CV
Michael Catanzaro wrote:
> This is a reminder that the webkitgtk and webkitgtk3 packages will be
> retired from rawhide shortly after F26 is branched from rawhide.
There are still several high-profile applications depending on those
libraries, including Gnucash. I don't see how it is practical at
Hi,
This is a reminder that the webkitgtk and webkitgtk3 packages will be
retired from rawhide shortly after F26 is branched from rawhide. This
is due to numerous security issues affecting those packages (I just
counted 204 CVEs), many of which could allow remote code execution.
Bugs have already
27 matches
Mail list logo
