Re: unblock: webkit2gtk/2.16.3-2
On 2017-06-01 22:29, Jeremy Bicha wrote: On Tue, May 30, 2017 at 5:47 PM, Jeremy Bicha wrote: On Tue, May 30, 2017 at 5:32 PM, Moritz Mühlenhoff wrote: You're best technical bet would be to upgrade to new webkit releases in stretch point releases, this would allow proper binNMUs and allow people to testdrive via s-p-u. But that's up for the SRMs to decide (and I doubt they want to deal with that kind of API "stability" either). That sounds like a good way to start. I want webkit2gtk 2.16.3 in Debian 9.0. Does it just need a regular unblock bug? unblock bug filed: https://bugs.debian.org/863915 "the current proposal [2] is to use Debian's s-p-u procedures and get these updates into Debian point releases" I don't believe that's actually what Moritz said. Regards, Adam
Bug#863979: ITP: ruby-email-reply-trimmer -- Library to trim replies from plain text email
Package: wnpp Severity: wishlist Owner: Abhijith PA X-Debbugs-CC: debian-devel@lists.debian.org * Package name: ruby-email-reply-trimmer Version : 0.1.6 Upstream Author : Régis Hanol * URL : https://github.com/discourse/email_reply_trimmer * License : Expact Programming Lang: Ruby Description : Library to trim replies from plain text email EmailReplyTrimmer is a small library to trim replies from plain text email. This is needed for packaging gitlab 9.2 -- Abhijith PA abhij...@openmailbox.org Debian Maintainer 4096R/ED9C28EF:EF13 EA26 A698 FF35 FD7C 902E 863D 4DF2 ED9C 28EF
Re: Too many Recommends (in particular on mail-transport-agent)
On 06/01/2017 01:00 PM, Henrique de Moraes Holschuh wrote: Anything on the top three priorities (critical, alert and emergency) is supposed to be displayed immediately to all logged-in users (including remote ones), no matter what. Only LOG_EMERG does that, at least on my machine and I'm pretty sure that's the default rsyslog config. Unfortunately, a RAID member failure is only legitimately LOG_ALERT. Sort of a moot point though... It would be great it we had an alert program to use instead of email KDE displays high-priority system alerts as high priority notifications by default (maybe some of it because of the default configuration of rsyslog). Running KDE here, so familiar with them. The first problem with those is they automatically vanish after a few seconds. They remain around, if you pull up the alert notifier, but that little (1) in the systray is easy to miss. Second problem is that only works if you're logged in. Even on a typical desktop where the main user is the admin, it's not safe to assume a that user will always be logged in: * Turn on machine, go grab coffee or tea while it's booting. Disk failure occurs before you get back and log in. * Log out for the night, but leave it on for e.g. backups, file serving, or remote access * Log out so your kids can use the machine Third problem, syslog imposes some pretty severe format restrictions on the message. An alert sent via email can have a lot more details & instructions than a syslog message. Using a machine as a home media server (e.g., a NAS) is a reasonably common thing too—then it'll hardly ever have a local logged in user. You can surely configure rsyslog to get that alert to you anyway. (Probably using ommail!). But that's no easier than configuring outgoing email.
Bug#863985: ITP: node-chownr -- Javascript implementation of chown -R.
Package: wnpp Severity: wishlist Owner: hacksk X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-chownr Version : 1.0.1 Upstream Author : Isaac Z. Schlueter (http://blog.izs.me/) * URL : https://github.com/isaacs/chownr#readme * License : ISC Programming Lang: JavaScript Description : Javascript implementation of chown -R. Javascript implementation of chown -R. . This library can be used recursively change ownership of files. It supports all options of fs.chown() . This library is a dependency of npm, nodejs package manager. . Node.js is an event-based server-side JavaScript engine. This is a dependency of npm (required for updating npm). Praveen has agreed to sponsor this package. -- kiran
Re: Too many Recommends (in particular on mail-transport-agent)
On Fri, 02 Jun 2017, Anthony DeRobertis wrote: > On 06/01/2017 01:00 PM, Henrique de Moraes Holschuh wrote: > >Anything on the top three priorities (critical, alert and emergency) is > >supposed to be displayed immediately to all logged-in users (including > >remote ones), no matter what. > > Only LOG_EMERG does that, at least on my machine and I'm pretty sure that's > the default rsyslog config. Unfortunately, a RAID member failure is only > legitimately LOG_ALERT. Sort of a moot point though... Hmm, true. I misrecalled this detail and failed to check it to be correct before posting. We should consider changing that to at least include ALERT as well. > >>It would be great it we had an alert program to use instead of email > >KDE displays high-priority system alerts as high priority notifications > >by default (maybe some of it because of the default configuration of > >rsyslog). > > Running KDE here, so familiar with them. The first problem with those is > they automatically vanish after a few seconds. They remain around, if you > pull up the alert notifier, but that little (1) in the systray is easy to > miss. Yes. I just tested it in Debian stable with "logger -p EMERG this_is_only_a_test". It would be far better if KDE used the (!) pictogram at least for ALERT and EMERG priorities, but it seems to be getting the messages from the ttys instead of from journald or the syslog daemon. I did not test this throughoutly, though. And yes, I stand corrected. It does not display ALERT or CRIT priorities by default, only EMERG. Which is Not Good Enough as far as I am concerned. > Second problem is that only works if you're logged in. Even on a typical > desktop where the main user is the admin, it's not safe to assume a that > user will always be logged in: Well, yes. Remote syslog (wherever deployed) will receive the messages quasi-real-time, though. And the messages *are* going to be recorded on the journal and /var/log/syslog. Whether someone will read the logs or not, well... it is the same issue with notifications over local email to root: one has to assume the system has been properly configured as an Unix workstation (and thus it has local email routing that goes somewhere it will be read). I am for doing the three by default: email (for stuff like mdadm), proper syslog or journald (for everything), and proper desktop- environment notifications for whomever is logged in. > * Turn on machine, go grab coffee or tea while it's booting. Disk >failure occurs before you get back and log in. In the older days, you'd have the messages on the login tty, even if it screwed up the graphical screen (Solaris and Sun-OS style ;p). Or you'd have a xconsole window open, even on the xdm screen (which I never tried to do, I wonder if this was a local xdm change...) -- Henrique Holschuh
