Re: Call for help on testing ceph

2020-09-21 Thread Bernd Zeimetz

Hi Ola,

while I appreciate your work, I'm not sure if removing ceph from the
list of supported packages wouldn't be the better option.
Doing a mistake while patching things might destroy data...
But I'll happily leave the descision to you.

Bernd

On 2020-09-21 23:26, Ola Lundqvist wrote:

Hi LTS team and fellow ceph maintainers

I have prepared an updated package of ceph with fixes for a few CVEs.
It took me longer time than I expected due to the cheer size of the
package build and compile time.
I have based the fixes on upstream patches or patches done for jessie.
The patches I based the fixes on had to be modified for the package to
build. They are quite straight forward, but as always I could make a
mistake.
More information on what I did is available in my preliminary monthly
report here:
https://inguza.com/report/debian-long-term-support-work-2020-september


What I would like to know is whether you know of any good methods of
testing ceph in order to verify that the package works as it should.

Thank you in advance.

If you are interested you can look at the build here:

http://apt.inguza.net/stretch-lts/ceph/

The packag build is not signed. I plan to do that when it is properly
tested.
When I have tested it, I will upload and remove the files from the
above location.

Thank you in advance,

// Ola

On Sun, 13 Sep 2020 at 23:01, Ola Lundqvist  wrote:


Hi LTS team

I'm currently building ceph. I have prepared the patches for the
vulnerabilities and it looks fine. I cannot yet promised that it
will build fine. The build takes quite some time since it produces
some 45 GB of data...

Anyway the reason I'm contacting you is that I do not think I will
be able to test this package in any useful way. It looks way too
complicated to set up. Do any of you have experience in it?

Cheers

// Ola

--

--- Inguza Technology AB --- MSc in Information Technology 
|  o...@inguza.como...@debian.org|
|  http://inguza.com/Mobile: +46 (0)70-332 1551 |
---


--

 --- Inguza Technology AB --- MSc in Information Technology 
|  o...@inguza.como...@debian.org|
|  http://inguza.com/Mobile: +46 (0)70-332 1551 |
 ---


--
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F



Re: Call for help on testing ceph

2020-09-21 Thread Ola Lundqvist
Hi LTS team and fellow ceph maintainers

I have prepared an updated package of ceph with fixes for a few CVEs. It
took me longer time than I expected due to the cheer size of the package
build and compile time.
I have based the fixes on upstream patches or patches done for jessie.
The patches I based the fixes on had to be modified for the package to
build. They are quite straight forward, but as always I could make a
mistake.
More information on what I did is available in my preliminary monthly
report here:
https://inguza.com/report/debian-long-term-support-work-2020-september

What I would like to know is whether you know of any good methods of
testing ceph in order to verify that the package works as it should.

Thank you in advance.

If you are interested you can look at the build here:

http://apt.inguza.net/stretch-lts/ceph/

The packag build is not signed. I plan to do that when it is properly
tested.
When I have tested it, I will upload and remove the files from the above
location.

Thank you in advance,

// Ola

On Sun, 13 Sep 2020 at 23:01, Ola Lundqvist  wrote:

> Hi LTS team
>
> I'm currently building ceph. I have prepared the patches for the
> vulnerabilities and it looks fine. I cannot yet promised that it will build
> fine. The build takes quite some time since it produces some 45 GB of
> data...
>
> Anyway the reason I'm contacting you is that I do not think I will be able
> to test this package in any useful way. It looks way too complicated to set
> up. Do any of you have experience in it?
>
> Cheers
>
> // Ola
>
> --
>  --- Inguza Technology AB --- MSc in Information Technology 
> |  o...@inguza.como...@debian.org|
> |  http://inguza.com/Mobile: +46 (0)70-332 1551 |
>  ---
>
>

-- 
 --- Inguza Technology AB --- MSc in Information Technology 
|  o...@inguza.como...@debian.org|
|  http://inguza.com/Mobile: +46 (0)70-332 1551 |
 ---


Re: IRC meeting this Thursday 24th - Agenda

2020-09-21 Thread Chris Lamb
Hi Sylvain,

> As promised, here's a reminder that we have an IRC meeting this
> Thursday, and we can prepare which topics to discuss a bit in advance :)

Can you confirm the time for us? I have this down at 15:00 UTC (ie.
8am Pacific, 11am Eastern, 4pm London, 5pm Berlin, 11pm Hong Kong),
but a confirmation would be really appreciated.


Regards,

--
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-



IRC meeting this Thursday 24th - Agenda

2020-09-21 Thread Sylvain Beucler
Hi,

As promised, here's a reminder that we have an IRC meeting this
Thursday, and we can prepare which topics to discuss a bit in advance :)

One issue: https://pad.riseup.net/p/lts-meeting-agenda is currently
unresponsive for me.
Their home page https://pad.riseup.net/ says they are experiencing troubles.

Holger, should we use a different service for the next meeting?
( https://framapad.org/ comes to mind )

Cheers!
Sylvain



(semi-)automatic unclaim of packages with more than 2 weeks of inactivity (and missing DLAs on www.do)

2020-09-21 Thread Holger Levsen
hi,

today three packages were unclaimed for LTS:

- ark (Abhijith PA)
- guacamole-client (Mike Gabriel)
- samba (Mike Gabriel)

and two for ELTS:

- clamav (Utkarsh Gupta)
- rails (Mike Gabriel)

Then, noone claimed too many packages, yay!

Also, while there are two DLAs which have been reserved but not yet been
published, this is indeed fine as they have been reserved today:
so yay once more! :)

- DLA 2377-1 (21 Sep 2020) (qt4-x11)
- DLA 2376-1 (21 Sep 2020) (qtbase-opensource-src)


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C


signature.asc
Description: PGP signature