Re: Bug#886238: closed by Bastian Blank (Re: Bug#886238: Please introduce official nosystemd build profile)

2018-01-07 Thread Alec Leamas
On 07/01/18 22:41, Hleb Valoshka wrote: > Have you sent the same warnings to your mates from LP fanclub Please, stop this. This is the Debian devel list, and personal opinions about Lennart Poettering (or anyone else) IMHO just have no place here. Time to create a new list systemd-flamewars?

Bug#886599: RFH: broadcom-sta -- Broadcom STA Wireless driver (non-free)

2018-01-07 Thread Eduard Bloch
Package: wnpp Severity: normal I request assistance with maintaining the broadcom-sta package. I don't have permanent access to related hardware nor do I use similar devices regularly, so my detector for all new breakages (mostly kernel change related) has been non-functional for months, causing

Re: kernel nvidia dkms rebuild after upgrade?

2018-01-07 Thread Boyan Penkov
Hello Dan — thanks kindly, I had indeed not noticed…. I guess I’ll have a chance to test if the libelf-dev issue is really the fix when the patches do roll out. In that vein, I would like to note that https://security-tracker.debian.org/tracker/CVE-2017-5754

Re: kernel nvidia dkms rebuild after upgrade?

2018-01-07 Thread Boyan Penkov
Thanks, Yao — in messing around with this, I did end up finding a thread that suggested installing libelf-dev — I did so, but I guess the order in which I did it make me recompile my dkms modules manually. Thanks for the note! -- Boyan Penkov www.boyanpenkov.com > On Jan 7, 2018, at 18:31, Yao

Re: kernel nvidia dkms rebuild after upgrade?

2018-01-07 Thread Daniel Reichelt
On 01/07/2018 07:47 PM, Boyan Penkov wrote: > and a backport (4.14.0-bpo2) -- in light of meltdown -- To avoid a false sense of security: according to [1], [2], [3], the current stretch-bpo kernel (linux-image-4.14.0-0.bpo.2-$arch) does *NOT* yet include any mitigations against meltdown. Daniel

Re: kernel nvidia dkms rebuild after upgrade?

2018-01-07 Thread Yao Wei
It is caused by a missing dependency libelf-dev. It is already reported against linux-headers-4.14.0-3-amd64: https://bugs.debian.org/886474 I have the same symptom of broadcom-sta-dkms On Mon, 8 Jan 2018 at 02:47 Boyan Penkov wrote: > Hello, > > After the latest update to 4.9.0-5, and a backpo

Re: Bug#886526: ITP: rt4-extension-commandbymail -- Change metadata of ticket via email (Request Tracker)

2018-01-07 Thread Andrew Ruthven
Hi Tollef, On Sun, 2018-01-07 at 13:29 +0100, Tollef Fog Heen wrote: > ]] Andrew Ruthven  > > > The intial packaging work has been carried but by myself for my > > employer. > > Ongoing maintenance will be by the Debian Request Tracker Group (of > > which > > I'm a member). > > This is already p

Bug#886238: closed by Bastian Blank (Re: Bug#886238: Please introduce official nosystemd build profile)

2018-01-07 Thread Hleb Valoshka
On 1/5/18, Debian Bug Tracking System wrote: > From: Bastian Blank ... > As you have been already told by several people, Debian supports > systemd-less systems. If you find bugs running in this mode, please > file bug reports. I've already posted a bug number which perfectly shows how bugs for

Re: e2fsprogs as Essential: yes?: Maybe we should be separating l10n files first?

2018-01-07 Thread Theodore Ts'o
On Sat, Jan 06, 2018 at 02:25:55AM +0100, Manuel A. Fernandez Montecelo wrote: > 2018-01-02 03:10 Theodore Ts'o: > > My only real concern is whether this might complicate building the > > latest version of e2fsprogs for stable and old-stable for > > debian-backports. > > I think that it's fine, th

Bug#886238: Please introduce official nosystemd build profile

2018-01-07 Thread Chris Lamb
Matthias, > > > > (accusing Debian to "vandalize" open source by supporting systemd) [..] > > > I was accused of this on the "dng" mailing list. It should be easy to > > > find the relevant threads. [..] > > And you were accused because you had removed (broken) functionality > > from sysv script a

Re: Bug#886238: Please introduce official nosystemd build profile

2018-01-07 Thread Simon McVittie
On Sun, 07 Jan 2018 at 18:55:28 +0100, Thomas Goirand wrote: > IMO, [a nosystemd profile] is a relevant bug because of non-Linux > ports. If it existed, it would probably make sense for those buildd > to always select the nosystemd profile when building, which would make > life easier. We can alre

Bug#886238: Please introduce official nosystemd build profile

2018-01-07 Thread Matthias Klumpp
2018-01-07 20:00 GMT+01:00 Hleb Valoshka <375...@gmail.com>: > On 1/6/18, Chris Lamb wrote: >>> > (accusing Debian to "vandalize" open source by supporting systemd) >> […] >>> 1) Proofs please. DDG & Google find only your words. >> >> I was accused of this on the "dng" mailing list. It should be e

Bug#886238: Please introduce official nosystemd build profile

2018-01-07 Thread Hleb Valoshka
On 1/6/18, Chris Lamb wrote: >> > (accusing Debian to "vandalize" open source by supporting systemd) > […] >> 1) Proofs please. DDG & Google find only your words. > > I was accused of this on the "dng" mailing list. It should be easy to > find the relevant threads. To be honest there were quite o

kernel nvidia dkms rebuild after upgrade?

2018-01-07 Thread Boyan Penkov
Hello, After the latest update to 4.9.0-5, and a backport (4.14.0-bpo2) -- in light of meltdown -- my nvidia drivers failed to load. Rebulding the modules manually -- https://askubuntu.com/questions/53364/command-to-rebuild-all-dkms-modules-for-all-installed-kernels/174017 -- did fix it. Did I m

Re: Bug#886238: Please introduce official nosystemd build profile

2018-01-07 Thread Marco d'Itri
On Jan 07, Thomas Goirand wrote: > > duplicates that code. The correct response to a patch to build without > > libsystemd is "no, that's what libsystemd exists for". > Does this approach also work for non-Linux ports? Yes, as long as somebody would bother to update the libsystemd-dummy package.

Re: Bug#886238: Please introduce official nosystemd build profile

2018-01-07 Thread Thomas Goirand
On 01/04/2018 01:33 AM, Josh Triplett wrote: > Building without *libsystemd*, on the other hand, *is* invasive, > precisely because libsystemd *already* includes the necessary code to > handle systems without systemd, and building without libsystemd > duplicates that code. The correct response to a

Re: Bug#886238: Please introduce official nosystemd build profile

2018-01-07 Thread Thomas Goirand
On 01/03/2018 08:01 PM, Steve Langasek wrote: > Catering to fanatics who insist on treating it specially, without technical > merit, has no bearing on the freeness or universality of Debian. Probably, though IMO if your sentence can in some degree be socially correct (aren't we all tired of those

Re: Why do we list individual copyright holders?

2018-01-07 Thread Sean Whitton
Hello, On Sun, Jan 07 2018, Guido Günther wrote: > gbp-dch allows you to skip these commits based on tags present in the > commit message: "Gbp-Dch: Ignore". I use this frequently for patch > series that add up to "a user visible result" I want present in the > changelog. I also find deleting tex

Bug#886346: marked as done (general: USB 3.0 Disk Drive Not Recognized)

2018-01-07 Thread Debian Bug Tracking System
Your message dated Sun, 7 Jan 2018 18:38:00 +0100 with message-id <20180107173800.f4jwgvy6md7f3...@betterave.cristau.org> and subject line Re: Bug#886346: general: USB 3.0 Disk Drive Not Recognized has caused the Debian Bug report #886346, regarding general: USB 3.0 Disk Drive Not Recognized to be

Re: Ssh access on salsa denied

2018-01-07 Thread Balasankar C
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, On 01/07/2018 10:19 PM, Andreas Tille wrote: > Hi, > > I verified in the web interface on Salsa that my public ssh key > from alioth was imported and to be very sure I uploaded it again. > Unfortunately this does not changed anything > > $

Re: Ssh access on salsa denied

2018-01-07 Thread Alexander Wirt
On Sun, 07 Jan 2018, Andreas Tille wrote: > Hi, > > I verified in the web interface on Salsa that my public ssh key > from alioth was imported and to be very sure I uploaded it again. > Unfortunately this does not changed anything > >$ ssh -i ~/.ssh/id_rsa_debian2 ti...@salsa.debian.org >

Ssh access on salsa denied

2018-01-07 Thread Andreas Tille
Hi, I verified in the web interface on Salsa that my public ssh key from alioth was imported and to be very sure I uploaded it again. Unfortunately this does not changed anything $ ssh -i ~/.ssh/id_rsa_debian2 ti...@salsa.debian.org ti...@salsa.debian.org: Permission denied (publickey). Th

Re: Why do we list individual copyright holders?

2018-01-07 Thread Guido Günther
Hi, On Wed, Jan 03, 2018 at 02:26:43PM +, Sean Whitton wrote: > Hello, > > On Tue, Jan 02 2018, Markus Koschany wrote: > > > The changelog is something which can be naturally derived from the > > changes made to a source package and excellent tools like > > git-buildpackage ("gbp dch") make t

Re: Bug#886238: Please introduce official nosystemd build profile

2018-01-07 Thread Ansgar Burchardt
Simon McVittie writes: > On Sun, 07 Jan 2018 at 00:27:15 +0100, Ansgar Burchardt wrote: >> sysvinit probably only stays in testing because systemd >> depends on sysv-rc for compatability with LSB init scripts... > > I think it did during the default init system transition, but it doesn't > any more

Re: Bug#886526: ITP: rt4-extension-commandbymail -- Change metadata of ticket via email (Request Tracker)

2018-01-07 Thread Tollef Fog Heen
]] Andrew Ruthven > The intial packaging work has been carried but by myself for my employer. > Ongoing maintenance will be by the Debian Request Tracker Group (of which > I'm a member). This is already packaged as librt-extension-commandbymail-perl, but feel free to have the team take it over.

Re: Bug#886238: Please introduce official nosystemd build profile

2018-01-07 Thread Simon McVittie
On Sun, 07 Jan 2018 at 00:27:15 +0100, Ansgar Burchardt wrote: > sysvinit probably only stays in testing because systemd > depends on sysv-rc for compatability with LSB init scripts... I think it did during the default init system transition, but it doesn't any more. sysvinit-utils is still Essen

Bug#886493: general: debian should support nosystemd build profile

2018-01-07 Thread Wouter Verhelst
Hi Britton, On Sat, Jan 06, 2018 at 09:34:32AM -0900, Britton Kerin wrote: > If debian is remotely serious about keeping non-systmed use an option, > is should support a nosystemd build profile. There's no other real > way to guarantee that packages don't use it. Sure they don't *have* > to link

Bug#886528: ITP: dumb-jump-el -- jump to definition for multiple languages without configuration

2018-01-07 Thread Lev Lamberov
Package: wnpp Owner: Lev Lamberov Severity: wishlist * Package name: dumb-jump-el Version : 0.5.1 Upstream Author : Jack Angers * URL or Web page : https://github.com/jacktasia/dumb-jump * License : GPL-3+ Programming Lang: Emacs Lisp Description : jump to definit

Bug#886527: ITP: rt4-extension-assets-import-csv -- Import Assets from CSV files (Request Tracker)

2018-01-07 Thread Andrew Ruthven
Package: wnpp Severity: wishlist Owner: Andrew Ruthven * Package name: rt4-extension-assets-import-csv Version : 2.2 Upstream Author : Best Practical Solutions, LLC * URL : https://metacpan.org/release/RT-Extension-Assets-Import-CSV * License : GPL v2 Progra

Bug#886526: ITP: rt4-extension-commandbymail -- Change metadata of ticket via email (Request Tracker)

2018-01-07 Thread Andrew Ruthven
Package: wnpp Severity: wishlist Owner: Andrew Ruthven * Package name: rt4-extension-commandbymail Version : 3.00 Upstream Author : Best Practical Solutions, LLC * URL : https://metacpan.org/release/RT-Extension-CommandByMail * License : GPL v2 Programming L

Bug#886525: ITP: rt4-extension-mergeusers -- Merge users (Request Tracker)

2018-01-07 Thread Andrew Ruthven
Package: wnpp Severity: wishlist Owner: Andrew Ruthven * Package name: rt4-extension-mergeusers Version : 1.03 Upstream Author : Best Practical Solutions, LLC * URL : https://metacpan.org/release/RT-Extension-MergeUsers * License : GPL v2 Programming Lang: P