Re: Is there system-config-lvm for Debian 10?

On Sat, Jul 13, 2019 at 5:27 AM Joe Irungu wrote: > Thus is there a system-config-lvm for Debian 10 or how else can I manage logical volumes in Buster? system-config-lvm was removed from Debian buster in 2017: https://tracker.debian.org/pkg/system-config-lvm https://tracker.debian.org/news/85184

Bug#931290: general: Asrock A300 Deskmini AMD Athlon 200GE ends in black screen Monitor has no Signal

On Sat, Jul 13, 2019 at 1:21 AM Joe Lobeck wrote: > in the meantime I found that the most things work form kernel 5.0 or higher. > Unfortunately so I will have to choose an other linux distribution as such a > kernel > is for debian only from the experimantal repository avaiable. > If you have an

Is there system-config-lvm for Debian 10?

- - - Is there system-config-lvm for Debian 10? [i

Bug#931290: general: Asrock A300 Deskmini AMD Athlon 200GE ends in black screen Monitor has no Signal

Dear Mantainer, in the meantime I found that the most things work form kernel 5.0 or higher. Unfortunately so I will have to choose an other linux distribution as such a kernel is for debian only from the experimantal repository avaiable. If you have any other idea how to make debian stable or

Re: Notes on packaging PCYNLITX

Bagas Sanjaya wrote: Hello, I've filed RFP for PCYNLITX sometimes ago [1]: In PCYNLITX download page [2], it can be installed by using installation script. However, after examining install script, I noticed following: - PCYNLITX doesn't employ version numbering like any other project/packages.

Re: Notes on packaging PCYNLITX

On 2019-07-12 19:52:14, Bagas Sanjaya wrote: > - Evince will be installed as runtime dependency, possibly for documentation. > For non-GNOME users (KDE, XFCE, etc.) > which use different readers (like Okular and Atril) this can bloat their > system and become unnecessary. You might want to have

Re: Suite name for security updates changing with Debian 11 "bullseye"

Hi Ansgar, Ansgar Burchardt ezt írta (időpont: 2019. júl. 11., Cs, 22:02): > > Hi, > > over the last years we had people getting confused over -updates > (recommended updates) and /updates (security updates). Starting > with Debian 11 "bullseye" we have therefore renamed the suite including > th

Re: Notes on packaging PCYNLITX

Hi Bagas, On 12.07.19 14:52, Bagas Sanjaya wrote: > I've filed RFP for PCYNLITX sometimes ago [1]: [...] > - The script install wxWidgets library from third-party repository, not from > Debian. It use codelite repo (for Stretch): >> apt-add-repository 'deb http://repos.codelite.org/wx3.0.4/debian

Re: Detecting (upcoming) problems using automatic tests

Hi Simon, > > Hm, although perhaps DEB_BUILD_OPTIONS is the prefered place for this > > kind of toggle rather than an environment variable? > > We already have "nocheck" to disable tests, and IMO the default should be > to run tests if we can. Unless I am grossly misunderstanding him, Julian's s

Notes on packaging PCYNLITX

Hello, I've filed RFP for PCYNLITX sometimes ago [1]: In PCYNLITX download page [2], it can be installed by using installation script. However, after examining install script, I noticed following: - PCYNLITX doesn't employ version numbering like any other project/packages. It would be difficul

Re: git & Debian packaging sprint report

On Thu, 2019-07-11 at 17:58 -0300, Antonio Terceiro wrote: > > We designed and implemented a system to make it possible for DDs to > > upload new versions of packages by simply pushing a specially > > formatted git tag to salsa. [...] > If the uploads will be done by a service, this means that all

Re: Detecting (upcoming) problems using automatic tests

Hi, On Thu, Jul 11, 2019 at 10:23:59PM -0300, Chris Lamb wrote: > > I feel like it would be nice to come up with a standard environment > > variable to turn warnings into errors, so we can ensure issues are > > fixed and the warnings are actually useful. > Hm, although perhaps DEB_BUILD_OPTIONS

Re: git & Debian packaging sprint report

Hello Scott, On Fri 12 Jul 2019 at 04:30am +00, Scott Kitterman wrote: > Has there been any analysis of the security implications of this > proposed service? Nothing formal, though of course we were thinking about it while we were working on it. > If I am understanding the description correctly