Hello, about two months ago I submitted a package to driver:wireless without hearing anything more. Yesterday I tried to contact the maintainer (vbotka) directly but the email bounced. Is there someone else who is in charge? Regards
On Thu, Sep 11, 2014 at 08:22:06AM +0200, LB wrote:
Hello, about two months ago I submitted a package to driver:wireless without hearing anything more. Yesterday I tried to contact the maintainer (vbotka) directly but the email bounced.
Vlado (vbotka) left SUSE some time ago.
Is there someone else who is in charge?
Not sure if hschaa is, but maybe you would like to?
Petr
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 09/11/2014, 08:52 AM, Petr Gajdos wrote:
On Thu, Sep 11, 2014 at 08:22:06AM +0200, LB wrote:
Is there someone else who is in charge?
Not sure if hschaa is, but maybe you would like to?
Hmm, the project is a big mess. It contains packages which are in their devel projects elsewhere. And sometimes packaged differently. For example most (maybe all) the firmwares should be deleted (kernel-firmware contains them). wireless-regdb, and iw live elsewhere and should be only linked here (if anything).
I can sort that out after conferences if nobody beats me to it...
thanks, - -- js suse labs
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 09/11/2014, 09:32 AM, Jiri Slaby wrote:
On 09/11/2014, 08:52 AM, Petr Gajdos wrote:
On Thu, Sep 11, 2014 at 08:22:06AM +0200, LB wrote:
Is there someone else who is in charge?
Not sure if hschaa is, but maybe you would like to?
Hmm, the project is a big mess. It contains packages which are in their devel projects elsewhere. And sometimes packaged differently. For example most (maybe all) the firmwares should be deleted (kernel-firmware contains them). wireless-regdb, and iw live elsewhere and should be only linked here (if anything).
I can sort that out after conferences if nobody beats me to it...
Ok, so I created request 264716, since nobody stepped up. Can somebody with the right permissions accept the request?
thanks,
- -- js suse labs
Am 10.12.2014 um 20:05 schrieb Jiri Slaby:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 09/11/2014, 09:32 AM, Jiri Slaby wrote:
On 09/11/2014, 08:52 AM, Petr Gajdos wrote:
On Thu, Sep 11, 2014 at 08:22:06AM +0200, LB wrote:
>Is there someone else who is in charge?
Not sure if hschaa is, but maybe you would like to?
Hmm, the project is a big mess. It contains packages which are in their devel projects elsewhere. And sometimes packaged differently. For example most (maybe all) the firmwares should be deleted (kernel-firmware contains them). wireless-regdb, and iw live elsewhere and should be only linked here (if anything).
I can sort that out after conferences if nobody beats me to it...
Ok, so I created request 264716, since nobody stepped up. Can somebody with the right permissions accept the request?
thanks,
js suse labs
There was this longer thread in September which you are referring to : http://lists.opensuse.org/opensuse-factory/2014-09/msg00163.html
I still think, that this complete DRIVER: project should be removed!
Best regards, Johannes
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 12/10/2014, 08:05 PM, Jiri Slaby wrote:
On 09/11/2014, 09:32 AM, Jiri Slaby wrote:
On 09/11/2014, 08:52 AM, Petr Gajdos wrote:
On Thu, Sep 11, 2014 at 08:22:06AM +0200, LB wrote:
Is there someone else who is in charge?
Not sure if hschaa is, but maybe you would like to?
Hmm, the project is a big mess. It contains packages which are in their devel projects elsewhere. And sometimes packaged differently. For example most (maybe all) the firmwares should be deleted (kernel-firmware contains them). wireless-regdb, and iw live elsewhere and should be only linked here (if anything).
I can sort that out after conferences if nobody beats me to it...
Ok, so I created request 264716, since nobody stepped up. Can somebody with the right permissions accept the request?
The only meaningful package rfkill has been moved to the hardware project. Its develproject has been changed a minute ago too. So driver:wireless has been killed right now 8-).
PS drivers:wlan has a pending delete request: https://build.opensuse.org/request/show/280125
drivers:nic detto: https://build.opensuse.org/request/show/280126
thanks, - -- js suse labs
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 01/07/2015, 09:48 AM, Jiri Slaby wrote:
On 12/10/2014, 08:05 PM, Jiri Slaby wrote:
On 09/11/2014, 09:32 AM, Jiri Slaby wrote:
On 09/11/2014, 08:52 AM, Petr Gajdos wrote:
On Thu, Sep 11, 2014 at 08:22:06AM +0200, LB wrote:
Is there someone else who is in charge?
Not sure if hschaa is, but maybe you would like to?
Hmm, the project is a big mess. It contains packages which are in their devel projects elsewhere. And sometimes packaged differently. For example most (maybe all) the firmwares should be deleted (kernel-firmware contains them). wireless-regdb, and iw live elsewhere and should be only linked here (if anything).
I can sort that out after conferences if nobody beats me to it...
Ok, so I created request 264716, since nobody stepped up. Can somebody with the right permissions accept the request?
The only meaningful package rfkill has been moved to the hardware project. Its develproject has been changed a minute ago too. So driver:wireless has been killed right now 8-).
PS drivers:wlan has a pending delete request: https://build.opensuse.org/request/show/280125
drivers:nic detto: https://build.opensuse.org/request/show/280126
Adrian, could you schedule a timed delete request? Otherwise these won't be deleted ever...
thanks, - -- js suse labs
Sorry for hijacking this thread,
but the same is valid for driver:nic; I've requested maintainer-ship a year ago but no answer.
Best regards, Johannes
Am 11.09.2014 um 08:52 schrieb Petr Gajdos:
On Thu, Sep 11, 2014 at 08:22:06AM +0200, LB wrote:
Hello, about two months ago I submitted a package to driver:wireless without hearing anything more. Yesterday I tried to contact the maintainer (vbotka) directly but the email bounced.
Vlado (vbotka) left SUSE some time ago.
Is there someone else who is in charge?
Not sure if hschaa is, but maybe you would like to?
Petr
Dne Čt 11. září 2014 12:29:50, Johannes Weberhofer napsal(a):
Sorry for hijacking this thread,
but the same is valid for driver:nic; I've requested maintainer-ship a year ago but no answer.
Best regards, Johannes
Thats quite easy, none of the drivers:* projects are actually used for developement of Factory.
So nobody involved in the Factory seen your request. Only the two people that are there, god knows how active.
It would be actually nice to mandate all these projects to be home projects or actually linked to factory.
And all devel projects should contain only packages that are in Factory (or planned to be sent there) [or linked from other devel project].
Cheers
Tom
On Thursday 2014-09-11 12:34, Tomáš Chvátal wrote:
Thats quite easy, none of the drivers:* projects are actually used for developement of Factory.
Or just move it to hardware:.
I don't have any objections against that, but I can't do this.
It would be a good time to clean up:
drivers:acpi : 7 years no change drivers:webcam : projets between 4 and 8 years old (is the buildservice already that old?) drivers:wlan : all repos removed by admin drivers:platform: 6 years no change drivers:isci 6 years no change drivers:scsi: 7 years no change drivers:filesystem : emtpy
Looks, as if I'm the only one maintaining the projects
drivers:nic/intel-e1000e and drivers:io/snx
There as some other drivers in drivers:nic which are no longer maintained and which might not be used anymore. I could move my two projects and "drivers:" could be completely removed.
Best regards, Johannes
Am 11.09.14 um 13:33 schrieb Jan Engelhardt:
On Thursday 2014-09-11 12:34, Tomáš Chvátal wrote:
Thats quite easy, none of the drivers:* projects are actually used for developement of Factory.
Or just move it to hardware:.
On Thursday 2014-09-11 18:45, Johannes Weberhofer wrote:
drivers:acpi : 7 years no change
The only package in there, acer_acpi, it would seem that it might have been obsoleted by general advances kernel development plus the acer_wmi.ko module (also shipped in kernel). Delete the prj.
drivers:webcam : projets between 4 and 8 years old (is the buildservice already that old?)
Yes, it is that old.
drivers:wlan : all repos removed by admin
That might have been the (semi-)automatic removal, i.e. admin deleted unsupported openSUSE versions, but no one added repos for new versions. It would not make much sense either, all packages are obsoleted. ipw2200 -> ipw2x00.ko in kernel, rt2500 -> rt2500pci.ko in kernel, zd1211 -> zd1211rw.ko in kernel. Delete the prj.
drivers:platform: 6 years no change
applesmc .. is in the kernel. Delete prj.
drivers:isci 6 years no change
iscsitarget... was that not the Redhat ISCSI, which is now obsolete, because the kernel has LIO? So yeah. And open-iscsi is in /network. Delete prj.
drivers:scsi: 7 years no change drivers:filesystem : emtpy
Delete. The filesystem repo is at, well, /filesystems.
Looks, as if I'm the only one maintaining the projects
drivers:nic/intel-e1000e
In principle, the drivers are in the kernel too. Intel however releases e1000 updates as a standalone tarball too (at least did so a year ago), and someone might be hot for it. Delete prj? ;)
Am 11.09.14 um 20:49 schrieb Jan Engelhardt:
Looks, as if I'm the only one maintaining the projects
drivers:nic/intel-e1000e
In principle, the drivers are in the kernel too. Intel however releases e1000 updates as a standalone tarball too (at least did so a year ago), and someone might be hot for it. Delete prj?;)
Hmm... I am using those drivers at some systems where I hab problems with the kernel drivers, so I'm still maintaining them.
And there is another driver I'm maintaining in drivers:io which supports several IO cards from sunix;
Both drivers I'd not like to loose, but at least the first one should not go into factory in my option.
On Thu, 11 Sep 2014 21:08, Johannes Weberhofer <jweberhofer@...> wrote:
Am 11.09.14 um 20:49 schrieb Jan Engelhardt:
Looks, as if I'm the only one maintaining the projects
drivers:nic/intel-e1000e
In principle, the drivers are in the kernel too. Intel however releases e1000 updates as a standalone tarball too (at least did so a year ago), and someone might be hot for it. Delete prj?;)
Hmm... I am using those drivers at some systems where I hab problems with the kernel drivers, so I'm still maintaining them.
And there is another driver I'm maintaining in drivers:io which supports several IO cards from sunix;
Both drivers I'd not like to loose, but at least the first one should not go into factory in my option.
Maybe move those that you maintain into the "hardware:" project? That way the "driver:" project would be open to removal.
Even if not closing "driver:", reducing the structure to the still maintained parts would be a help, not just for OBS, but also for those that seek a specific piece of software.
- Yamaban.
Am 11.09.14 um 21:20 schrieb Yamaban:
On Thu, 11 Sep 2014 21:08, Johannes Weberhofer <jweberhofer@...> wrote:
Am 11.09.14 um 20:49 schrieb Jan Engelhardt:
Looks, as if I'm the only one maintaining the projects
drivers:nic/intel-e1000e
In principle, the drivers are in the kernel too. Intel however releases e1000 updates as a standalone tarball too (at least did so a year ago), and someone might be hot for it. Delete prj?;)
Hmm... I am using those drivers at some systems where I hab problems with the kernel drivers, so I'm still maintaining them.
And there is another driver I'm maintaining in drivers:io which supports several IO cards from sunix;
Both drivers I'd not like to loose, but at least the first one should not go into factory in my option.
Maybe move those that you maintain into the "hardware:" project? That way the "driver:" project would be open to removal.
Even if not closing "driver:", reducing the structure to the still maintained parts would be a help, not just for OBS, but also for those that seek a specific piece of software.
- Yamaban.
Have submitted both packages to hardware. Please review...
On Thursday 11 of September 2014 20:49:11 Jan Engelhardt wrote:
iscsitarget... was that not the Redhat ISCSI, which is now obsolete, because the kernel has LIO? So yeah. And open-iscsi is in /network.
There is still iscsitarget package (not sure if it's the same), including KMP's, in 13.1. But, well, so is ndiswrapper...
Michal Kubeček
Am 12.09.2014 um 06:53 schrieb Michal Kubecek:
On Thursday 11 of September 2014 20:49:11 Jan Engelhardt wrote:
iscsitarget... was that not the Redhat ISCSI, which is now obsolete, because the kernel has LIO? So yeah. And open-iscsi is in /network.
There is still iscsitarget package (not sure if it's the same), including KMP's, in 13.1. But, well, so is ndiswrapper...
Michal Kubeček
hardware:iscsitarget seem to be removed from factory and does currently not work hardware:.
drivers:iscsitarget is around six years old and has no build targets defined.
On Friday 2014-09-12 06:53, Michal Kubecek wrote:
On Thursday 11 of September 2014 20:49:11 Jan Engelhardt wrote:
iscsitarget... was that not the Redhat ISCSI, which is now obsolete, because the kernel has LIO? So yeah. And open-iscsi is in /network.
There is still iscsitarget package (not sure if it's the same), including KMP's, in 13.1. But, well, so is ndiswrapper...
JFTR: Redhat's was called tgt. Looks like iscsitarget is even older.
-
Jan Engelhardt -
Jiri Slaby -
Johannes Weberhofer -
LB -
Michal Kubecek -
Petr Gajdos -
Tomáš Chvátal -
Yamaban