Re: [projects/pld-builder.new] drop building intel drivers and nvidiabl for head kernels

[Elan Ruusamäe]

On 12.10.2016 00:44, Jan Rękorajski wrote:

 From now on, if a kernel package does not build for new head kernel and
no obvious fix is available, I will drop such package on head.
If you want antique module, stick to old kernel.
please announce any of such droppings. that's what i asked here! and 
have asked historycally as well. if you plan to drop something you 
announce the list of packages and the reason.


--
glen

___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

Re: [projects/pld-builder.new] drop building intel drivers and nvidiabl for head kernels

[Elan Ruusamäe]

On 12.10.2016 00:44, Jan Rękorajski wrote:

On Wed, 12 Oct 2016, Elan Ruusamäe wrote:


>On 12.10.2016 00:15, Jan Rękorajski wrote:

> >Fix it then. This driver is unmaintained for years and does not build
> >with kernel 4.8.

>that was not the point of the email to tell me "fix it then"
>
>the point was that you drop some package, don't even inform you are
>about to do so, or ask for help updating. with bulld errors, etc details
>like normal bugreports are createA

I remove packages after I see breakage sitting around in th-test for a
long time and no one interested in fixing it.

Any dev breaking stuff should be aware of the consequences and take
action to minimize breakage.

I'm not a nanny or Mr. Fix-it for everything.

how i should know any of that? i do not read your /dev/brain! or monitor 
your /dev/tty to see what you are doing.


and how exactly i broke anything personally here? i was just an user of 
a kernel module.


--
glen

___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

Re: [projects/pld-builder.new] drop building intel drivers and nvidiabl for head kernels

[Jan Rękorajski]

On Wed, 12 Oct 2016, Elan Ruusamäe wrote:

> On 12.10.2016 00:15, Jan Rękorajski wrote:
> > Fix it then. This driver is unmaintained for years and does not build
> > with kernel 4.8.
> that was not the point of the email to tell me "fix it then"
> 
> the point was that you drop some package, don't even inform you are 
> about to do so, or ask for help updating. with bulld errors, etc details 
> like normal bugreports are createA

I remove packages after I see breakage sitting around in th-test for a
long time and no one interested in fixing it.

Any dev breaking stuff should be aware of the consequences and take
action to minimize breakage.

I'm not a nanny or Mr. Fix-it for everything.

> and now you respond: "why don't i update myself?"
> 
> because you've being doing it so well i don't even notice problems that 
> i should bother myself with and can keep occupied with other projects.

Sorry, but I'm sick of kernel modules being randomly dropped on ftp and
then forgotten by package authors. I end up maintaining antiquated junk
I have no way of testing, and until reently, we did ship not working
crap there (chnages to kernel compile flags helped finding those).

From now on, if a kernel package does not build for new head kernel and
no obvious fix is available, I will drop such package on head.
If you want antique module, stick to old kernel.

-- 
Jan Rękorajski| PLD/Linux
SysAdm | bagginspld-linux.org | http://www.pld-linux.org/
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

Re: [projects/pld-builder.new] drop building intel drivers and nvidiabl for head kernels

[Elan Ruusamäe]

On 12.10.2016 00:15, Jan Rękorajski wrote:

Fix it then. This driver is unmaintained for years and does not build
with kernel 4.8.

that was not the point of the email to tell me "fix it then"

the point was that you drop some package, don't even inform you are 
about to do so, or ask for help updating. with bulld errors, etc details 
like normal bugreports are created.


and now you respond: "why don't i update myself?"

because you've being doing it so well i don't even notice problems that 
i should bother myself with and can keep occupied with other projects.


--
glen

___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

Re: [projects/pld-builder.new] drop building intel drivers and nvidiabl for head kernels

[Jan Rękorajski]

On Wed, 12 Oct 2016, Elan Ruusamäe wrote:

> On 11.10.2016 23:53, baggins wrote:
> > commit c856373d926bb13ff6e38acf0bd0fc5c5baef880
> > Author: Jan Rękorajski 
> > Date:   Tue Oct 11 22:53:04 2016 +0200
> >
> >  drop building intel drivers and nvidiabl for head kernels
> 
> i'm using nvidiabl. why stuff gets secretly dropped?
> 
> please announce if you're going to drop something.
> 
> # lsmod|grep nvidiabl
> nvidiabl   53248  0
> 
> # uname -r
> 4.7.2-1

Fix it then. This driver is unmaintained for years and does not build
with kernel 4.8.

-- 
Jan Rękorajski| PLD/Linux
SysAdm | bagginspld-linux.org | http://www.pld-linux.org/
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

Re: [projects/pld-builder.new] drop building intel drivers and nvidiabl for head kernels

[Elan Ruusamäe]

On 11.10.2016 23:53, baggins wrote:

commit c856373d926bb13ff6e38acf0bd0fc5c5baef880
Author: Jan Rękorajski 
Date:   Tue Oct 11 22:53:04 2016 +0200

 drop building intel drivers and nvidiabl for head kernels


i'm using nvidiabl. why stuff gets secretly dropped?

please announce if you're going to drop something.

# lsmod|grep nvidiabl
nvidiabl   53248  0

# uname -r
4.7.2-1

--
glen

___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

Re: glibc <> libselinux dep loop

[Elan Ruusamäe]

On 11.10.2016 09:59, Zbyniu Krzystolik wrote:

nss_db-2.2.3-0.pre1.11 + nss_updatedb-10-3 (LDAP backend) works for me
for many years, while nss_db from glibc segfaults.


does 2.5.0 from master also work for you?

also, like to hear how you installed it (the file conflicts i mentioned 
in earlier replies)


--
glen

___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

Re: glibc <> libselinux dep loop

[Elan Ruusamäe]

On 11.10.2016 08:49, Elan Ruusamäe wrote:

ok, WIP on nss_db branch

but to ensure safe upgrade must R: it from glibc? R: from basesystem?

i personally do not use nss_db, so i'm not scared if it becames lost 
in system upgrade. imho it was stupid to include optional component 
in base glibc in first place.



oh, and we already have nss_db in th. to be dropped?

root@distrib ~# rpm -Uhv --test 
/srv/pld/th/PLD/x86_64/RPMS/nss_db-2.2.3-0.pre1.11.x86_64.rpm 

i propose:

1. rename nss_db.spec -> nss_bdb.spec:
https://github.com/pld-linux/nss_db/commit/c3050c19465c9a42bc8796dcb22bb3d3380cc785

2. package -n nss_db from glibc.spec

3. add to glibc.spec
requires: nss_db = %{version}

4. add glibc.spec:
conflicts: nss_db < 1:2.15

so that systems having nss_db 2.2 installed don't get accidentally 
upgraded to glibc version


5. after X time, remove 3
TBD: RM decision or define some date?


--
glen

___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

Re: glibc <> libselinux dep loop

[Elan Ruusamäe]

On 11.10.2016 09:59, Zbyniu Krzystolik wrote:

nss_db-2.2.3-0.pre1.11 + nss_updatedb-10-3 (LDAP backend) works for me
for many years, while nss_db from glibc segfaults.

Zbyniu

how did you install it? because there's fileconflict, you used --force?

--
glen

___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

Re: glibc <> libselinux dep loop

[Zbyniu Krzystolik]

Elan Ruusamäe wrote:
> On 11.10.2016 08:42, Elan Ruusamäe wrote:
> > On 11.10.2016 06:44, Jakub Bogusz wrote:
> >> On Tue, Oct 11, 2016 at 12:29:11AM +0300, Elan Ruusamäe wrote:
> >>> proposition to move it to subpackage.
> >>>
> >>> question: by what name? what else to include in it?
> >>>
> >>> i think it's the tool used to make /var/db files that used to be in 
> >>> 'db'
> >>> package...
> >> AFAIK it's used with nss_db - so maybe separate %package -n nss_db
> >> (libnss_db*, makedb)?
> >>
> >>
> > ok, WIP on nss_db branch
> >
> > but to ensure safe upgrade must R: it from glibc? R: from basesystem?
> >
> > i personally do not use nss_db, so i'm not scared if it becames lost 
> > in system upgrade. imho it was stupid to include optional component in 
> > base glibc in first place.
> >
> oh, and we already have nss_db in th. to be dropped?
> 
> root@distrib ~# rpm -Uhv --test 
> /srv/pld/th/PLD/x86_64/RPMS/nss_db-2.2.3-0.pre1.11.x86_64.rpm
> Preparing... ### [100%]
> error: Install/Erase problems:
>  file /lib64/libnss_db.so.2 from install of 
> nss_db-2.2.3-0.pre1.11.x86_64 conflicts with file from package 
> glibc-2.24-3.x86_64
>  file /usr/bin/makedb from install of 
> nss_db-2.2.3-0.pre1.11.x86_64 conflicts with file from package 
> glibc-2.24-3.x86_64
>  file /var/db/Makefile from install of 
> nss_db-2.2.3-0.pre1.11.x86_64 conflicts with file from package 
> glibc-2.24-3.x86_64

nss_db-2.2.3-0.pre1.11 + nss_updatedb-10-3 (LDAP backend) works for me
for many years, while nss_db from glibc segfaults.

Zbyniu
-- 
%% Absolutely nothing we trust %%
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en