Re: [arch-dev-public] Moving KDE3 and Gtk1 from [extra]
On Thu, May 15, 2014 at 10:59 AM, Eric Bélanger wrote: > > > > On Wed, Apr 16, 2014 at 3:55 PM, Alexander Rødseth wrote: > >> There was a message on arch-general, noting that kiwi does not depend on >> gtk1. >> >> As I understand the situation, the holdups concerning gtk1, kdelibs3 >> and qt3 are now resolved, and there is a strong consensus that moving >> these packages is a good idea. We don't want to act as upstream for >> old, unmaintained, obsolete and potentially insecure libraries. >> >> >> Best regards, >> Alexander / xyproto >> > > I've just removed qt3/kdelibs3 (as well as packages depending on them) > from the repos. In the next few days, I'll check your work on imlib and see > what can be done with gtk1. This thread was started when I was inactive so > I didn't really had time to go through this earlier. > Everything is done now. glib, gtk and frinds have beed removed from the repos. In case someone is interested, here's the packages that were removed: glib gtk xmms lib32-glib lib32-gtk dfm gdk-pixbuf manedit amidi-plug perl-xmms xmmsctrl xmms-imms xmms-pulse xmms-volnorm
Re: [arch-dev-public] Moving KDE3 and Gtk1 from [extra]
Hi, Great, thanks! Just tested the updated imlib and fvwm packages from [extra] here, and both builds without problems. Best regards, Alexander / xyproto
Re: [arch-dev-public] Moving KDE3 and Gtk1 from [extra]
On Wed, Apr 16, 2014 at 3:55 PM, Alexander Rødseth wrote: > There was a message on arch-general, noting that kiwi does not depend on > gtk1. > > As I understand the situation, the holdups concerning gtk1, kdelibs3 > and qt3 are now resolved, and there is a strong consensus that moving > these packages is a good idea. We don't want to act as upstream for > old, unmaintained, obsolete and potentially insecure libraries. > > > Best regards, > Alexander / xyproto > I've just removed qt3/kdelibs3 (as well as packages depending on them) from the repos. In the next few days, I'll check your work on imlib and see what can be done with gtk1. This thread was started when I was inactive so I didn't really had time to go through this earlier.
Re: [arch-dev-public] Moving KDE3 and Gtk1 from [extra]
There was a message on arch-general, noting that kiwi does not depend on gtk1. As I understand the situation, the holdups concerning gtk1, kdelibs3 and qt3 are now resolved, and there is a strong consensus that moving these packages is a good idea. We don't want to act as upstream for old, unmaintained, obsolete and potentially insecure libraries. Best regards, Alexander / xyproto
Re: [arch-dev-public] Moving KDE3 and Gtk1 from [extra]
Hi, I made a few changes to imlib and it compiles without Gtk1 now. Here is the source package: http://roboticoverlords.org/arch/imlib-1.9.15-14.src.tar.gz I wanted to test it with fvwm, but I could not, because ftp://ftp.fvwm.org/pub/fvwm/version-2/fvwm-2.6.5.tar.bz2 is no longer available. Please update the imlib package. If it is now possible to move the old and unmaintained gtk1, qt3 and kdelibs3 packages from the official repositories to AUR, that would be great. Best regards, Alexander Rødseth xyproto / TU
Re: [arch-dev-public] Moving KDE3 and Gtk1 from [extra]
On Sat, Apr 5, 2014 at 3:48 PM, Connor Behan wrote: > On 05/04/14 11:57 AM, rods...@gmail.com wrote: > > The only two packages I think might be worth extra concern here is: > > > > * imlib: needed by dfm, fvwm (should be possible to compile without > > depending on imlib), kuickshow and tksystray. > > > > * libdv: used by a lot of packages. gtk is listed as both optional and > > a make dependency. I assume this means that it can be compiled without > > Gtk1. > It is very easy to make libdv build (and the viewer run) against gtk2 > instead, as my libdv-gtk2 package in the AUR does. If imlib is still a > concern, I don't mind maintaining gtk1 in [community]. > > If we keep gtk1 in the repos, I can continue maintaining it in [extra].
Re: [arch-dev-public] Moving KDE3 and Gtk1 from [extra]
On Sat, Apr 5, 2014 at 2:57 PM, Alexander Rødseth wrote: > Hi, > > > 2014-04-04 21:13 GMT+02:00 Eric Bélanger : > >> * imlib: needed by dfm, fvwm (should be possible to compile without > >> depending on imlib), > > > > Last time I check, it wasn't possible. As fvwm is the WM I use (I believe > > it has also decent usage statistics), I would like to keep them in the > > repos. > > Last time you checked, it was possible. Gentoo builds imlib without > Gtk1. Let me refresh your memory by linking to your own reply on the > matter: > https://mailman.archlinux.org/pipermail/arch-dev-public/2013-May/024976.html > > > The patch they use wasn't applying or working. > +1 for also moving qt3 > > > -- > Best regards, > Alexander Rødseth > xyproto / TU >
Re: [arch-dev-public] Moving KDE3 and Gtk1 from [extra]
On 05/04/14 11:57 AM, rods...@gmail.com wrote: > The only two packages I think might be worth extra concern here is: > > * imlib: needed by dfm, fvwm (should be possible to compile without > depending on imlib), kuickshow and tksystray. > > * libdv: used by a lot of packages. gtk is listed as both optional and > a make dependency. I assume this means that it can be compiled without > Gtk1. It is very easy to make libdv build (and the viewer run) against gtk2 instead, as my libdv-gtk2 package in the AUR does. If imlib is still a concern, I don't mind maintaining gtk1 in [community]. signature.asc Description: OpenPGP digital signature
Re: [arch-dev-public] Moving KDE3 and Gtk1 from [extra]
Hi, 2014-04-04 21:13 GMT+02:00 Eric Bélanger : >> * imlib: needed by dfm, fvwm (should be possible to compile without >> depending on imlib), > > Last time I check, it wasn't possible. As fvwm is the WM I use (I believe > it has also decent usage statistics), I would like to keep them in the > repos. Last time you checked, it was possible. Gentoo builds imlib without Gtk1. Let me refresh your memory by linking to your own reply on the matter: https://mailman.archlinux.org/pipermail/arch-dev-public/2013-May/024976.html +1 for also moving qt3 -- Best regards, Alexander Rødseth xyproto / TU
Re: [arch-dev-public] Moving KDE3 and Gtk1 from [extra]
On Fri, Apr 4, 2014 at 5:09 PM, Alexander Rødseth wrote: > Hi, > > So, can we move kdelibs3 and gtk from [extra] to either [community] or AUR? I'm for dropping all of this to AUR if possible. Pretty much all mentioned applications have better alternatives already (well, maybe not ktechlab, but that is a rather specific package). > I prefer the GUI of qalculate-kde but I could live with qalculate-gtk. I > use this not very often. Therefore I wouldn't mind removing kdelibs3 from > the repos. We might also remove qt3 as well. There's some kde4 interface in the git repo, maybe you want to try that: http://sourceforge.net/p/qalculate/qalculate-kde4/ci/master/tree/ Good point with qt3, that's pretty ancient, too. And there are not many packages using it either. Lukas
Re: [arch-dev-public] Moving KDE3 and Gtk1 from [extra]
> So, in conclusion: > > 0 for removing kdelibs3 > -1 for removing gtk1 I think if we ship either qt3 or gtk1, that makes us upstream and we become responsible for backporting any security fixes made in qt4/qt5 and gtk2/gtk3. We usually hand wave away this kind of responsibility because we promptly ship the upstream releases, but it doesn't work here. Even Debian isn't shipping gtk1 anymore. signature.asc Description: OpenPGP digital signature
Re: [arch-dev-public] Moving KDE3 and Gtk1 from [extra]
On Fri, Apr 4, 2014 at 11:09 AM, Alexander Rødseth wrote: > Hi, > > > KDE3 and Gtk1 are pretty old by now. Upstream development has stopped > and the few pages that still needs the "kdelibs3" or "gtk" package > seems to be of less importance. > > The topic was discussed briefly on IRC and there were only positive > comments about making this move. > > One of the many arguments for moving them is that when upstream > development stops, we don't want to take on the responsibility of > fixing security problems with kde3/gtk1. > > So, can we move kdelibs3 and gtk from [extra] to either [community] or AUR? > > > Here are the packages that depends on kdelibs3 (maintained by Eric > Bélanger), together with the name of the current maintainer(s): > > kleansweep, Sergej Pupykin > kovpn, Sergej Pupykin > ksniffer, Sergej Pupykin > ktechlab, Sergej Pupykin > pwmanager, Sergej Pupykin > qalculate-kde, Eric Bélanger > tork, Felix Yan > > I prefer the GUI of qalculate-kde but I could live with qalculate-gtk. I use this not very often. Therefore I wouldn't mind removing kdelibs3 from the repos. We might also remove qt3 as well. > Here are the packages that depends on gtk (maintained by Eric Bélanger): > > dfm, Sergej Pupykin > gdk-pixbuf, Sergej Pupykin > imlib, Eric Bélanger > kiwi, Federico Cinelli > lib32-gtk, Pierre Schmitz > madman, Sergej Pupykin > manedit, Giovanni Scafora > xmms, Eric Bélanger > libdv (optional+make), Jan de Groot > twin (optional), Sergej Pupykin > librcc (make), Sergej Pupykin > > > The only two packages I think might be worth extra concern here is: > > * imlib: needed by dfm, fvwm (should be possible to compile without > depending on imlib), Last time I check, it wasn't possible. As fvwm is the WM I use (I believe it has also decent usage statistics), I would like to keep them in the repos. So, in conclusion: 0 for removing kdelibs3 -1 for removing gtk1 kuickshow and tksystray. > > * libdv: used by a lot of packages. gtk is listed as both optional and > a make dependency. I assume this means that it can be compiled without > Gtk1. > > > Which packages should be moved to [community] or AUR as a result of > kdelibs3 and gtk being moved, is up for discussion. > > > I think the timing is right for this and there seems to be consensus > that moving them is a good idea. > > > -- > Best regards, > Alexander Rødseth > xyproto / TU >
Re: [arch-dev-public] Moving KDE3 and Gtk1 from [extra]
On Fri, 4 Apr 2014 17:09:47 +0200 Alexander Rødseth wrote: > Hi, > > > KDE3 and Gtk1 are pretty old by now. Upstream development has stopped > and the few pages that still needs the "kdelibs3" or "gtk" package > seems to be of less importance. > > The topic was discussed briefly on IRC and there were only positive > comments about making this move. > > One of the many arguments for moving them is that when upstream > development stops, we don't want to take on the responsibility of > fixing security problems with kde3/gtk1. > > So, can we move kdelibs3 and gtk from [extra] to either [community] > or AUR? > > > Here are the packages that depends on kdelibs3 (maintained by Eric > Bélanger), together with the name of the current maintainer(s): > > kleansweep, Sergej Pupykin > kovpn, Sergej Pupykin > ksniffer, Sergej Pupykin > ktechlab, Sergej Pupykin > pwmanager, Sergej Pupykin > qalculate-kde, Eric Bélanger > tork, Felix Yan > > Here are the packages that depends on gtk (maintained by Eric > Bélanger): > > dfm, Sergej Pupykin > gdk-pixbuf, Sergej Pupykin > imlib, Eric Bélanger > kiwi, Federico Cinelli > lib32-gtk, Pierre Schmitz > madman, Sergej Pupykin > manedit, Giovanni Scafora > xmms, Eric Bélanger > libdv (optional+make), Jan de Groot > twin (optional), Sergej Pupykin > librcc (make), Sergej Pupykin > > > The only two packages I think might be worth extra concern here is: > > * imlib: needed by dfm, fvwm (should be possible to compile without > depending on imlib), kuickshow and tksystray. > > * libdv: used by a lot of packages. gtk is listed as both optional and > a make dependency. I assume this means that it can be compiled without > Gtk1. > > > Which packages should be moved to [community] or AUR as a result of > kdelibs3 and gtk being moved, is up for discussion. > > > I think the timing is right for this and there seems to be consensus > that moving them is a good idea. > > Neither of these packages is crucial enough to justify shipping so old libraries in the official repositories. There are good alternatives to XMMS and other packages like qalculate can just disable GTK1 support. +1. -- Bartłomiej Piotrowski http://bpiotrowski.pl/ signature.asc Description: PGP signature
[arch-dev-public] Moving KDE3 and Gtk1 from [extra]
Hi, KDE3 and Gtk1 are pretty old by now. Upstream development has stopped and the few pages that still needs the "kdelibs3" or "gtk" package seems to be of less importance. The topic was discussed briefly on IRC and there were only positive comments about making this move. One of the many arguments for moving them is that when upstream development stops, we don't want to take on the responsibility of fixing security problems with kde3/gtk1. So, can we move kdelibs3 and gtk from [extra] to either [community] or AUR? Here are the packages that depends on kdelibs3 (maintained by Eric Bélanger), together with the name of the current maintainer(s): kleansweep, Sergej Pupykin kovpn, Sergej Pupykin ksniffer, Sergej Pupykin ktechlab, Sergej Pupykin pwmanager, Sergej Pupykin qalculate-kde, Eric Bélanger tork, Felix Yan Here are the packages that depends on gtk (maintained by Eric Bélanger): dfm, Sergej Pupykin gdk-pixbuf, Sergej Pupykin imlib, Eric Bélanger kiwi, Federico Cinelli lib32-gtk, Pierre Schmitz madman, Sergej Pupykin manedit, Giovanni Scafora xmms, Eric Bélanger libdv (optional+make), Jan de Groot twin (optional), Sergej Pupykin librcc (make), Sergej Pupykin The only two packages I think might be worth extra concern here is: * imlib: needed by dfm, fvwm (should be possible to compile without depending on imlib), kuickshow and tksystray. * libdv: used by a lot of packages. gtk is listed as both optional and a make dependency. I assume this means that it can be compiled without Gtk1. Which packages should be moved to [community] or AUR as a result of kdelibs3 and gtk being moved, is up for discussion. I think the timing is right for this and there seems to be consensus that moving them is a good idea. -- Best regards, Alexander Rødseth xyproto / TU
