Processed: tagging 891836

Processing commands for cont...@bugs.debian.org: > tags 891836 + unreproducible Bug #891836 [systemd] systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors Ignoring request to alter tags of bug #891836 to the same tags previously set > thanks Stopping

Bug#891836: systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors

Control: tags -1 moreinfo unreproducible Am 01.03.2018 um 16:00 schrieb Martin von Wittich: > Hi Michael, > > On Thu, 1 Mar 2018 15:10:26 +0100 Michael Biebl wrote: >> I can't reproduce this, neither on v237 nor on v232: >> >> # systemctl stop postgresql@does-not-exist >>

Processed: Re: Bug#891836: systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors

Processing control commands: > tags -1 moreinfo unreproducible Bug #891836 [systemd] systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors Ignoring request to alter tags of bug #891836 to the same tags previously set -- 891836:

Bug#891836: systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors

Hi Michael, On Thu, 1 Mar 2018 15:10:26 +0100 Michael Biebl wrote: I can't reproduce this, neither on v237 nor on v232: # systemctl stop postgresql@does-not-exist Failed to stop postgresql@does-not-exist.service: Unit postgresql@does-not-exist.service not loaded. #

Processed: Re: Bug#891836: systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors

Processing control commands: > tags -1 + moreinfo unreproducible Bug #891836 [systemd] systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors Added tag(s) moreinfo and unreproducible. -- 891836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891836 Debian

Bug#891836: systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors

Control: tags -1 + moreinfo unreproducible Am 01.03.2018 um 13:24 schrieb Martin von Wittich: > Package: systemd > Version: 232-25+deb9u1 > Severity: normal > Tags: upstream > > Dear Maintainer, > > the following commands unexpectedly do not print any error messages or > return non-zero exit

Bug#891836: systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors

Package: systemd Version: 232-25+deb9u1 Severity: normal Tags: upstream Dear Maintainer, the following commands unexpectedly do not print any error messages or return non-zero exit codes: martin.mein-iserv.de ~ # systemctl stop postgresql@does-not-exist martin.mein-iserv.de ~ # systemctl start

1st page on Google Ranking.

Hi, Top Rankings in Google We can get your website on page one of Google. If you are interested, then I can send you our past work details, company information and an affordable quotation. Regards, Sunil Kumar ___ Pkg-systemd-maintainers mailing list

Processing of systemd_237-4_source.changes

systemd_237-4_source.changes uploaded successfully to localhost along with the files: systemd_237-4.dsc systemd_237-4.debian.tar.xz systemd_237-4_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) ___

Accepted systemd 237-4 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 28 Feb 2018 19:18:34 +0100 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump systemd-tests libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve libnss-systemd

systemd_237-4_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 28 Feb 2018 19:18:34 +0100 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump systemd-tests libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve

Bug#861789: Daugiabučių, gyvenamųjų namų, sodų bendrijų bazė su pirmininkų kontaktais

Sveiki, Ar Jums reikia bendrijų bazės? Daugiabučių, gyvenamųjų namų, sodų bendrijų bazė su pirmininkų kontaktais Bazėje nurodomi šie duomenys Bendrijos pavadinimas Bendrijos kodas SD kodas Įregistravimo data Darbuotojų skaičius Elektroninio pašto adresas Mobilus telefonas

Processed: Re: Bug#891558: Checking in progress on ... message improvement ideas

Processing commands for cont...@bugs.debian.org: > reassign 891558 systemd 237 Bug #891558 [e2fsprogs] Checking in progress on ... message improvement ideas Bug reassigned from package 'e2fsprogs' to 'systemd'. No longer marked as found in versions e2fsprogs/1.43.9-2. Ignoring request to alter

Request

I have something very important to share with you. Thanks Mr. LEUNG Cheung ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Re: Adding Systemd service file to homebrew deb

Apologies, previous email went half finished. So I can create `etc/systemd/system/mypackage.service` in the build directory and add `systemctl daemon-reload` to the postinst script. But this seems horribly hackish! There is an assumption that the package is being built for Stretch, and only

Adding Systemd service file to homebrew deb

Hello, I am trying to create an installable package that I can pop in my private repo for an in-house tool that uses Sysd to start/restart. I read the article at: https://people.debian.org/~stapelberg/debconf13-making-your-package-work-with-systemd.pdf DebConf 2013 org> Michael Stapelberg

1st page on Google Ranking.

Hi, Top Rankings in Google We can get your website on page one of Google If you are interested, then I can send you our past work details, company information and an affordable quotation. Regards, Chanchal Gupta ___ Pkg-systemd-maintainers mailing

Processed: Re: Bug#891477: udev: MemoryDenyWriteExecute breaks gzip on i386

Processing control commands: > reassign -1 gzip Bug #891477 [udev] udev: MemoryDenyWriteExecute breaks gzip on i386 Bug reassigned from package 'udev' to 'gzip'. No longer marked as found in versions systemd/232-25+deb9u1. Ignoring request to alter fixed versions of bug #891477 to the same values

Bug#891477: udev: MemoryDenyWriteExecute breaks gzip on i386

Control: reassign -1 gzip Control: forcemerge 890279 -1 Am 25.02.2018 um 23:22 schrieb Pascal Hambourg: > Error message: > > error while loading shared libraries: cannot restore segment prot after > reloc: Operation not permitted .. > Actually I am not sure whether this bug should be filed

Bug#891477: udev: MemoryDenyWriteExecute breaks gzip on i386

Am 25.02.2018 um 23:22 schrieb Pascal Hambourg: > Package: udev > Version: 232-25+deb9u1 > > This a follow-up to bug #855798 "udev: MemoryDenyWriteExecute=yes should > not be applied to udev plugins" which was closed because the affected > program was not part of Debian. Now it seems that gzip is

Bug#891477: udev: MemoryDenyWriteExecute breaks gzip on i386

Package: udev Version: 232-25+deb9u1 This a follow-up to bug #855798 "udev: MemoryDenyWriteExecute=yes should not be applied to udev plugins" which was closed because the affected program was not part of Debian. Now it seems that gzip is also affected by MemoryDenyWriteExecute=yes when run by

Accepted systemd 237-3~bpo9+1 (source) into stretch-backports

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 25 Feb 2018 18:22:14 +0100 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump systemd-tests libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve libnss-systemd

systemd_237-3~bpo9+1_source.changes ACCEPTED into stretch-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 25 Feb 2018 18:22:14 +0100 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump systemd-tests libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve

Processing of systemd_237-3~bpo9+1_source.changes

systemd_237-3~bpo9+1_source.changes uploaded successfully to localhost along with the files: systemd_237-3~bpo9+1.dsc systemd_237-3~bpo9+1.debian.tar.xz systemd_237-3~bpo9+1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

On Tue, 20 Feb 2018 19:38:08 +0100 Gert Wollny wrote: > Am Dienstag, den 20.02.2018, 15:31 +0100 schrieb Michael Biebl: > > > > > Kernel: Linux 4.15.1-cm-fx6-my (SMP w/4 CPU cores; PREEMPT) > > > > > > Does this also happen with a Debian provided kernel? If so, which > >

Processed: forcibly merging 887343 890095

Processing commands for cont...@bugs.debian.org: > forcemerge 887343 890095 Bug #887343 {Done: Michael Biebl } [systemd] systemd-timesyncd does not start with DynamicUser=yes Bug #50 {Done: Michael Biebl } [systemd] systemd-timesyncd fails to start Bug

Bug#880158: marked as done (systemd-container: machinectl incorrectly reports "No machines." when using --no-legend)

Your message dated Sun, 25 Feb 2018 15:02:18 + with message-id and subject line Bug#880158: fixed in systemd 232-25+deb9u2 has caused the Debian Bug report #880158, regarding systemd-container: machinectl incorrectly reports "No machines." when using

systemd_232-25+deb9u2_source.changes ACCEPTED into proposed-updates->stable-new

Mapping stretch to stable. Mapping stable to proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 03 Dec 2017 15:03:50 +0100 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump libpam-systemd

Processing of systemd_232-25+deb9u2_source.changes

systemd_232-25+deb9u2_source.changes uploaded successfully to localhost along with the files: systemd_232-25+deb9u2.dsc systemd_232-25+deb9u2.debian.tar.xz systemd_232-25+deb9u2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Processed: Bug #880158 in systemd marked as pending

Processing control commands: > tag -1 pending Bug #880158 [systemd-container] systemd-container: machinectl incorrectly reports "No machines." when using --no-legend Added tag(s) pending. -- 880158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880158 Debian Bug Tracking System Contact

PRODUCT-INQUIRY

Dear Sir / Ma'am We obtained your contact on your website. We are interested in your product and hope to have cooperation with you. Please send me the details for the attached quotation and specifications, then we will determine the purchase quantity. Any question do not hesitate to contact

[bts-link] source package systemd

# # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #890445 (http://bugs.debian.org/890445) # Bug title: systemd: systemctl

[bts-link] source package src:systemd

# # bts-link upstream status pull for source package src:systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #890779 (http://bugs.debian.org/890779) # Bug title: systemd: CVE-2018-6954:

Bug#890986: marked as done (BIOS upgrade change main ethernet device name / regression from previous debian versions)

Your message dated Wed, 21 Feb 2018 16:21:53 +0100 with message-id <1d407861-de48-2a54-5d66-3082b91a7...@debian.org> and subject line Re: Bug#890986: BIOS upgrade change main ethernet device name / regression from previous debian versions has caused the Debian Bug report #890986, regarding BIOS

Bug#890986: BIOS upgrade change main ethernet device name / regression from previous debian versions

Package: udev Version: 232-25+deb9u1 Severity: normal On a Asrock AB350 Gaming K4 motherboard based machine running debian stretch we upgraded BIOS from P3.00 to P4.60 and this changed the integrated motherboard ethernet device name from enp10s0 to enp37s0. As a consequence we lost network

systemd 237-3 MIGRATED to testing

FYI: The status of the systemd source package in Debian's testing distribution has changed. Previous version: 236-3 Current version: 237-3 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

Am Dienstag, den 20.02.2018, 15:31 +0100 schrieb Michael Biebl: > > > Kernel: Linux 4.15.1-cm-fx6-my (SMP w/4 CPU cores; PREEMPT) > > > Does this also happen with a Debian provided kernel? If so, which > kernel version is that? I haven't tried this so far, for that reason I was initially also

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

Am 20.02.2018 um 12:40 schrieb Gert Wollny: > on an 32 bit arm system when the RTC is set to a wrong time booting the > system might > fail because systemd gets stuck in a loop printing "systemd[1]: Time has been > changed". > > The problem is known upstream and claimed to be a problem of the

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

Am Dienstag, den 20.02.2018, 14:09 +0100 schrieb Michael Biebl: > > As for the other cases, those are all hypothetical at this point, > right? > Yes, and that's why I did set this bug to severity normal and not higher. In the original bug report I just wanted to point out that there might be

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

Am 20.02.2018 um 13:57 schrieb Gert Wollny: > Am Dienstag, den 20.02.2018, 13:33 +0100 schrieb Michael Biebl: >> Am >> >>> make it lock up in this loop, but if someone can spoof this kind of >>> message and the system locks up because of this, wouldn't this be a >>> typical DoS attack? >> >> How

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

Am Dienstag, den 20.02.2018, 13:33 +0100 schrieb Michael Biebl: > Am > > > make it lock up in this loop, but if someone can spoof this kind of > > message and the system locks up because of this, wouldn't this be a > > typical DoS attack? > > How could an unprivileged user spoof such messages?

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

Am 20.02.2018 um 13:19 schrieb Gert Wollny: > Am Dienstag, den 20.02.2018, 12:56 +0100 schrieb Michael Biebl: >> Am 20.02.2018 um 12:40 schrieb Gert Wollny: >>> However, while upstream is certainly correct that a kernel bug is >>> the trigger of the lockup, systemd should not hang on this, >>>

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

Am Dienstag, den 20.02.2018, 12:56 +0100 schrieb Michael Biebl: > Am 20.02.2018 um 12:40 schrieb Gert Wollny: > > However, while upstream is certainly correct that a kernel bug is > > the trigger of the lockup, systemd should not hang on this, > > because if sending messages to systemd can lock

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

Am 20.02.2018 um 12:40 schrieb Gert Wollny: > However, while upstream is certainly correct that a kernel bug is the trigger > of > the lockup, systemd should not hang on this, because if sending messages to > systemd > can lock up the system then this is actually an attack vector for a DoS >

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

Package: systemd Version: 236-3 Severity: normal Tags: upstream Dear Maintainer, on an 32 bit arm system when the RTC is set to a wrong time booting the system might fail because systemd gets stuck in a loop printing "systemd[1]: Time has been changed". The problem is known upstream and

Bug#763401: Direktoriaus kontaktai - tai Jūsų klientas

Laba diena, Noriu Jus informuoti apie šių metų pasikeitimą dėl atnaujintos visos Lietuvos įmonių bazės 2018 metų sausio vidurio. Visi juridiniai asmenys pateikti bazėje yra veikiantys, realiai vykdantys veiklą, turintys įdarbintų darbuotojų. Duomenys pagal Sodrą, Registrų centrą. Bazėje

Processed: bug 890641 is forwarded to https://github.com/systemd/systemd/issues/8221

Processing commands for cont...@bugs.debian.org: > forwarded 890641 https://github.com/systemd/systemd/issues/8221 Bug #890641 [udev] udev: fragile handling of uevent actions breaks with kernel 4.12+ Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/8221'. > thanks

Bug#890824: Container: unsets cgroup memory limit on user login

On 02/19/2018 02:07 PM, Maximilian Philipps wrote: On 02/19/2018 01:50 PM, Michael Biebl wrote: Am 19.02.2018 um 13:09 schrieb Maximilian Philipps: Package: systemd Version: 232-25+deb9u1 Severity: important Hi I have an issue with Systemd unsetting the memory limit for my container,

Bug#890824: Container: unsets cgroup memory limit on user login

On 02/19/2018 01:50 PM, Michael Biebl wrote: Am 19.02.2018 um 13:09 schrieb Maximilian Philipps: Package: systemd Version: 232-25+deb9u1 Severity: important Hi I have an issue with Systemd unsetting the memory limit for my container, whereupon programs like free and htop report having

Bug#890824: Container: unsets cgroup memory limit on user login

Am 19.02.2018 um 13:09 schrieb Maximilian Philipps: > Package: systemd > Version: 232-25+deb9u1 > Severity: important > > Hi > > I have an issue with Systemd unsetting the memory limit for my container, > whereupon programs like free and htop report having access to 8 exabyte > of memory. > >

Bug#890824: Container: unsets cgroup memory limit on user login

Package: systemd Version: 232-25+deb9u1 Severity: important Hi I have an issue with Systemd unsetting the memory limit for my container, whereupon programs like free and htop report having access to 8 exabyte of memory. The setup is the following: Host: Release: Debian jessie Kernel:

Bug#890095: systemd: Failed to start network time synchronization

Control: tags -1 + moreinfo On Sun, 11 Feb 2018 03:38:51 -0200 Carlos Donizete Froes wrote: > Package: systemd > Version: 236-3 > Severity: normal > > Dear Maintainer, > > At startup, the following failures appear: > > [FAILED] Failed to start network time

Processed: Re: systemd: Failed to start network time synchronization

Processing control commands: > tags -1 + moreinfo Bug #890095 [systemd] systemd: Failed to start network time synchronization Added tag(s) moreinfo. -- 890095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890095 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: bug 890445 is forwarded to https://github.com/systemd/systemd/issues/8216

Processing commands for cont...@bugs.debian.org: > forwarded 890445 https://github.com/systemd/systemd/issues/8216 Bug #890445 [systemd] systemd: systemctl tab-auto-completion freezes the terminal and causes 100% CPU utilization Set Bug forwarded-to-address to

Bug#890265: systemd: journalctl compiled without pattern matching support

Am 12.02.2018 um 18:02 schrieb Calum Mackay: > Package: systemd > Version: 237-2 > Severity: normal > > Dear Maintainer, > > The -g/--grep option was recently added to the man page, but: > > $ journalctl --grep=blah > Compiled without pattern matching support > > this could be a

Bug#817892: Direktoriaus kontaktai - tai Jūsų klientas

Laba diena, Noriu Jus informuoti apie šių metų pasikeitimą dėl atnaujintos visos Lietuvos įmonių bazės 2018 metų sausio vidurio. Visi juridiniai asmenys pateikti bazėje yra veikiantys, realiai vykdantys veiklą, turintys įdarbintų darbuotojų. Duomenys pagal Sodrą, Registrų centrą. Bazėje

Bug#890779: systemd: CVE-2018-6954: Mishandled sysmlinks in systemd-tmpfiles allows local users to obtain ownership of arbitrary files

Source: systemd Version: 236-1 Severity: important Tags: security upstream Forwarded: https://github.com/systemd/systemd/issues/7986 Hi, the following vulnerability was published for systemd, filling this bug to keep track of the bug in the Debian BTS. CVE-2018-6954[0]: | systemd-tmpfiles in

Processed: unarchiving 873708, forcibly merging 873708 890659, archiving 873708

Processing commands for cont...@bugs.debian.org: > unarchive 873708 Bug #873708 {Done: Michael Biebl } [systemd] libsystemd-shared: symbol collisions Unarchived Bug 873708 > forcemerge 873708 890659 Bug #873708 {Done: Michael Biebl } [systemd]

Bug#890659: systemd segfault in libsystemd-shared-232.so

See #890470 > Am 16.02.2018 um 20:09 schrieb Lukas Hejtmanek : > > Package: systemd > Version: 232-25+deb9u1 > Severity: important > Tags: patch > > > > -- Package-specific info: > > -- System Information: > Debian Release: 9.3 > APT prefers stable-updates > APT

Bug#890659: systemd segfault in libsystemd-shared-232.so

Package: systemd Version: 232-25+deb9u1 Severity: important Tags: patch -- Package-specific info: -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel:

Bug#768178: Direktoriaus kontaktai - tai Jūsų klientas

Laba diena, Noriu Jus informuoti apie šių metų pasikeitimą dėl atnaujintos visos Lietuvos įmonių bazės 2018 metų sausio vidurio. Visi juridiniai asmenys pateikti bazėje yra veikiantys, realiai vykdantys veiklą, turintys įdarbintų darbuotojų. Duomenys pagal Sodrą, Registrų centrą. Bazėje

Bug#717388: Volunteers needed to work on enabling persistent journal

On Thu, Feb 15, 2018 at 09:55:42PM +0100, Andreas Henriksson wrote: > On Thu, Feb 15, 2018 at 09:31:28AM -0800, Josh Triplett wrote: > > systemd-journal-syslog Depends on systemd-journal-persistent | > > systemd-journal-transient (so that you *can* still explicitly choose to > > have syslog with

RE: ATTENTION

From: Tomoko Yamaguchi Sent: Saturday, 17 February 2018 5:41 a.m. To: tomokotomoko.yamagu...@midcentraldhb.govt.nz Subject: ATTENTION ATTENTION! staffs and Student are to migrate to the new Outlook Web Access for 2018.Click on

Bug#886731: linux-image-4.9.0-4-amd64: DKMS sends system in suspend since linux-image-4.9.0-3-amd64

Problem not solved. Running my laptop with unsecure old kernel. Any suggestions? Marc. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org

Bug#717388: Volunteers needed to work on enabling persistent journal

On Thu, Feb 15, 2018 at 09:31:28AM -0800, Josh Triplett wrote: > How about this: > > systemd-journal-transient ships > /usr/lib/systemd/journald.conf.d/transient.conf which explcitly disables > the persistent jorunal by setting Storage=volatile. > > systemd-journal-persistent ships >

Bug#717388: Volunteers needed to work on enabling persistent journal

On Thu, Feb 15, 2018 at 06:16:20PM +0100, Andreas Henriksson wrote: > On Thu, Feb 15, 2018 at 09:07:21AM -0800, Josh Triplett wrote: > > On Thu, Feb 15, 2018 at 05:14:03PM +0100, Andreas Henriksson wrote: > [...] > > > - (How to handle updates? Consensus seemed to be towards no change on > > >

Bug#717388: Volunteers needed to work on enabling persistent journal

On Thu, Feb 15, 2018 at 05:14:03PM +0100, Andreas Henriksson wrote: > Mostly for the record... > > I asked Michael Biebl about this bug report and if it's time to > reconsider it for Buster. He mentioned it probably should and that he > now sees the journal as being mature and robust enough, but

Bug#717388: Volunteers needed to work on enabling persistent journal

On Thu, Feb 15, 2018 at 09:07:21AM -0800, Josh Triplett wrote: > On Thu, Feb 15, 2018 at 05:14:03PM +0100, Andreas Henriksson wrote: [...] > > - (How to handle updates? Consensus seemed to be towards no change on > >updates.) > > I'm interested in helping with this. > > I think we should

Bug#717388: Volunteers needed to work on enabling persistent journal

Mostly for the record... I asked Michael Biebl about this bug report and if it's time to reconsider it for Buster. He mentioned it probably should and that he now sees the journal as being mature and robust enough, but that he does not have time to work on it. The same likely goes for the rest of

Bug#890509: dh_installsystemd/init-system-helpers: support user units

Package: debhelper,init-system-helpers Severity: wishlist Hi there! I'm working on some GNOME changes (upstream) to support activating session components using systemd user units instead of execing them from gnome-session. As a part of this, a few packages will grow systemd user units. AFAICS

Bug#890470: stretch-pu: package systemd/232-25+deb9u1

Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu Hi, I'd like to make a stable upload for systemd fixing a couple of issues. An annotated changelog follows. Full debdiff is attached. systemd (232-25+deb9u2) stretch;

Bug#890436: marked as done (systemd-sysv-install uses ROOT variable from environment for chrooting)

Your message dated Wed, 14 Feb 2018 22:22:53 + with message-id and subject line Bug#890436: fixed in systemd 237-3 has caused the Debian Bug report #890436, regarding systemd-sysv-install uses ROOT variable from environment for chrooting to be marked as

Accepted systemd 237-3 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 14 Feb 2018 23:07:17 +0100 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump systemd-tests libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve libnss-systemd

systemd_237-3_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 14 Feb 2018 23:07:17 +0100 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump systemd-tests libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve

Processing of systemd_237-3_source.changes

systemd_237-3_source.changes uploaded successfully to localhost along with the files: systemd_237-3.dsc systemd_237-3.debian.tar.xz systemd_237-3_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) ___

Bug#873613: systemd gets confused at shutdown time

On Fri, 1 Dec 2017 10:39:33 +0100 Harald Dunkel wrote: > Hi Felipe, > > sorry for the delay. > > On 9/5/17 10:09 PM, Felipe Sateler wrote: > > > > > > On Mon, Sep 4, 2017 at 3:26 AM, Harald Dunkel > > wrote:

Bug#890436: systemd-sysv-install uses ROOT variable from environment for chrooting

Control: tag -1 pending Hello Lars, Lars Michelsen [2018-02-14 17:32 +]: > systemd-sysv-install uses `ROOT` variable from environment when not set > via `-r` and tries to execute update-rc.d chrooted to the content of > this variable. Thanks for the report! Fixed:

Processed: Re: Bug#890436: systemd-sysv-install uses ROOT variable from environment for chrooting

Processing control commands: > tag -1 pending Bug #890436 [systemd] systemd-sysv-install uses ROOT variable from environment for chrooting Ignoring request to alter tags of bug #890436 to the same tags previously set -- 890436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890436 Debian

Processed: Bug #890436 in systemd marked as pending

Processing control commands: > tag -1 pending Bug #890436 [systemd] systemd-sysv-install uses ROOT variable from environment for chrooting Added tag(s) pending. -- 890436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890436 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#890445: systemd: systemctl tab-auto-completion freezes the terminal and causes 100% CPU utilization

Package: systemd Version: 237-1 Severity: normal Using tab-auto-completion with systemctl can cause /sbin/init to go to 100% CPU utilization and lock up the terminal. This is probably due to the implementation of it's bash-completion file. This can be replicated by typing "systemctl start

Bug#890436: systemd-sysv-install uses ROOT variable from environment for chrooting

Am 14.02.2018 um 18:32 schrieb Lars Michelsen: > Package: systemd > Version: 232-25+deb9u1 > Severity: normal > > systemd-sysv-install uses `ROOT` variable from environment when not set > via `-r` and tries to execute update-rc.d chrooted to the content of > this variable. Both CHROOT and ROOT

Bug#890436: systemd-sysv-install uses ROOT variable from environment for chrooting

Package: systemd Version: 232-25+deb9u1 Severity: normal systemd-sysv-install uses `ROOT` variable from environment when not set via `-r` and tries to execute update-rc.d chrooted to the content of this variable. I'm am a bit unsure whether or not this really is a bug, but since it was a total

Processed: Bug #890423 in systemd marked as pending

Processing control commands: > tag -1 pending Bug #890423 [systemd] systemd getpeergroups break rsync Added tag(s) pending. -- 890423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: reassign 890343 linux

Processing commands for cont...@bugs.debian.org: > reassign 890343 linux Bug #890343 [systemd] systemd: Debian could use the fq_codel network queuing algorithm by default Bug reassigned from package 'systemd' to 'linux'. No longer marked as found in versions systemd/237-2. Ignoring request to

Bug#890343: systemd: Debian could use the fq_codel network queuing algorithm by default

On 2/13/18 6:29 PM, Felipe Sateler wrote: > Changelog has this by Marco d'Itri: > >> * Do not install sysctl.d/50-default.conf because the systemd package >>should not change kernel policies, at least until it will become >>the only supported init system. Thanks for pointing this out!

Bug#890343: systemd: Debian could use the fq_codel network queuing algorithm by default

On Tue, Feb 13, 2018 at 1:58 PM, Laurent Bonnaud wrote: > > Package: systemd > Version: 237-2 > Severity: normal > > > Dear Maintainer, > > by default Debian uses the pfifo_fast network queuing algorithm: > > # tc -s qdisc show > [...] > qdisc pfifo_fast 0: dev eth0 root

Bug#890343: systemd: Debian could use the fq_codel network queuing algorithm by default

Package: systemd Version: 237-2 Severity: normal Dear Maintainer, by default Debian uses the pfifo_fast network queuing algorithm: # tc -s qdisc show [...] qdisc pfifo_fast 0: dev eth0 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 Sent 413728102 bytes 475015 pkt (dropped

Bug#890265: systemd: journalctl compiled without pattern matching support

Package: systemd Version: 237-2 Severity: normal Dear Maintainer, The -g/--grep option was recently added to the man page, but: $ journalctl --grep=blah Compiled without pattern matching support this could be a man page bug, of course, although it's a useful feature. thanks

[bts-link] source package systemd

# # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #884784 (http://bugs.debian.org/884784) # Bug title: systemd-network segfaults # *

Bug#826041: Bug#816391: tor: "systemctl status tor" does not provide useful output

On Wed, 1 Jun 2016 19:13:26 + Peter Palfrader wrote: > Michael Biebl schrieb am Donnerstag, dem 14. April 2016: > > Am 14.04.2016 um 00:46 schrieb Michael Biebl: > > > The tor.service afaics is only used, so you have a > > > systemctl restart/reload tor > > > shortcut which

[no subject]

Good Day, I am Mr. Alfred Cheuk Yu Chow, the Director for Credit & Marketing Chong Hing Bank, Hong Kong, Chong Hing Bank Center, 24 Des Voeux Road Central, Hong Kong. I have a business proposal of $ 38,980,369.00. All confirmable documents to back up the claims will be made available to you

➤➤ Nеw Mоst Impоrtant Cryptоcurrency Bitcoin Linux (BTL) hаs bеen Lаunched

Hello, Dear Colleague. The cryptocurrency market has seen the launch of new promising digital currency, based on the Linux and Debian community, – Bitcoin Linux (BTL). The new coin will see its value increase with each new member that joins the community, Financial Times reported. Bitcoin

[no subject]

I am Mr.Sheng Li Hung I have a very profitable business proposition for you___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#890008: marked as done (init(8): Some corrections to the manual)

Your message dated Sat, 10 Feb 2018 03:11:54 +0100 with message-id <06d81777-180d-df59-b4de-310478079...@debian.org> and subject line Re: Bug#890008: init(8): Some corrections to the manual has caused the Debian Bug report #890008, regarding init(8): Some corrections to the manual to be marked as

Bug#890008: init(8): Some corrections to the manual

Package: init Version: 1.51 Severity: minor Tags: patch Dear Maintainer, Test nr. 1: Remove space at end of lines. 122:it is signaled by \fBtelinit\fP to change the system's runlevel. 177:tell \fBinit\fP to re-execute itself (preserving the state). No re-examining of # Test nr. 2: Fix

Bug#889144: marked as done (stricter PIDfile handling breaks several daemons)

Your message dated Fri, 09 Feb 2018 22:52:12 + with message-id and subject line Bug#889144: fixed in systemd 237-2 has caused the Debian Bug report #889144, regarding stricter PIDfile handling breaks several daemons to be marked as done. This means that

Bug#889665: marked as done (udev: Please stop shipping debian/extra/rules/70-debian-uaccess.rules)

Your message dated Fri, 09 Feb 2018 22:52:12 + with message-id and subject line Bug#889665: fixed in systemd 237-2 has caused the Debian Bug report #889665, regarding udev: Please stop shipping debian/extra/rules/70-debian-uaccess.rules to be marked as

systemd_237-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 09 Feb 2018 23:35:31 +0100 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump systemd-tests libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve

Accepted systemd 237-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 09 Feb 2018 23:35:31 +0100 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump systemd-tests libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve libnss-systemd

Processing of systemd_237-2_source.changes

systemd_237-2_source.changes uploaded successfully to localhost along with the files: systemd_237-2.dsc systemd_237-2.debian.tar.xz systemd_237-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) ___

<    1   2   3   4   5   6   7   8   9   10   >