Bug#887692: casync: FTBFS and Debci failure with glibc 2.26
Source: casync Version: 2-1 Severity: serious https://ci.debian.net/packages/c/casync/unstable/amd64/ https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/casync.html ... FAILED: src/shared@sta/caremote.c.o cc -Isrc/shared@sta -Isrc -I../src -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -std=gnu99 -Wextra -Werror=undef -Werror=format=2 -Wformat-security -Wformat-nonliteral -Wlogical-op -Wmissing-include-dirs -Werror=old-style-definition -Werror=pointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wsuggest-attribute=noreturn -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=missing-declarations -Werror=return-type -Werror=incompatible-pointer-types -Werror=shadow -Wstrict-prototypes -Wredundant-decls -Wmissing-noreturn -Wendif-labels -Wstrict-aliasing=2 -Wwrite-strings -Wno-unused-parameter -Wno-missing-field-initializers -Wno-unused-result -Werror=overflow -Werror=sign-compare -Wdate-time -Wnested-externs -ffast-math -fno-common -fdiagnostics-show-option -fno-strict-aliasing -fvisibility=hidden -fstack-protector -fstack-protector-strong -fPIE --param=ssp-buffer-size=4 -include config.h -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MMD -MQ 'src/shared@sta/caremote.c.o' -MF 'src/shared@sta/caremote.c.o.d' -o 'src/shared@sta/caremote.c.o' -c ../src/caremote.c In file included from ../src/caformat-util.h:7:0, from ../src/caremote.c:8: ../src/caremote.c: In function ‘ca_remote_forget_chunk’: ../src/util.h:471:13: error: argument 1 null where non-null expected [-Werror=nonnull] if (strncmp(s, prefix, l) == 0) ^ In file included from ../src/util.h:12:0, from ../src/caformat-util.h:7, from ../src/caremote.c:8: /usr/include/string.h:139:12: note: in a call to function ‘strncmp’ declared here extern int strncmp (const char *__s1, const char *__s2, size_t __n) ^~~ cc1: some warnings being treated as errors ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: Re: Bug#884784: systemd-network segfaults
Processing commands for cont...@bugs.debian.org: > forwarded 884784 https://github.com/systemd/systemd/issues/7760 Bug #884784 [systemd] systemd-network segfaults Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/7760'. > tags 884784 + upstream Bug #884784 [systemd] systemd-network segfaults Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 884784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ 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: problems with pkg systemd
Am 18.01.2018 um 15:59 schrieb Matthieu Castay: > Hi > > I installed a new debian buster and the systemd-timesync did not start. > I had to create user & group manualy to make systemd-timesync able to start > > user : > systemd-timesync:x:121:126:systemd Time > Synchronization,,,:/run/systemd:/usr/sbin/nologin > > group : > systemd-timesync:x:126: > > > Thanks > Matthieu > See #887343 Short answer is, you need libnss-systemd (then you don't have to create a system user statically). -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ 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#887456: init-system-helpers: deb-systemd-helper does not honor the same package-relevant unit paths as systemd
On Wed, Jan 17, 2018 at 9:44 PM, Michael Biebl wrote:
> Am 17.01.2018 um 11:35 schrieb Guillem Jover:
>> --- a/script/deb-systemd-helper
>> +++ b/script/deb-systemd-helper
>> @@ -122,6 +122,8 @@ sub find_unit {
>> $service_path = "/etc/systemd/system/$scriptname";
>> } elsif (-f "/lib/systemd/system/$scriptname") {
>> $service_path = "/lib/systemd/system/$scriptname";
>> +} elsif (-f "/usr/lib/systemd/system/$scriptname") {
>> +$service_path = "/usr/lib/systemd/system/$scriptname";
>> }
>> return $service_path;
>> }
>
> Looks ok to me on a cursory glance.
LGTM too.
> With merged-usr in mind, I wonder though if we should prefer
> /usr/lib/systemd over /lib/systemd. The latter will be a symlink in such
> a case and by prefering /usr/lib/systemd we'd avoid one indirection.
>
> Felipe, wdyt?
I'm indifferent. I don't think there is much impact, but we still
don't enable usrmerge by default...
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
problems with pkg systemd
Hi I installed a new debian buster and the systemd-timesync did not start. I had to create user & group manualy to make systemd-timesync able to start user : systemd-timesync:x:121:126:systemd Time Synchronization,,,:/run/systemd:/usr/sbin/nologin group : systemd-timesync:x:126: Thanks Matthieu ___ 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#887396: systemd-timesyncd.service: Start request repeated too quickly.
Am 18.01.2018 um 05:26 schrieb Andre Verwijs: > additional information: > > > > /etc/passwd should have this line by default : > > systemd-timesync:x:100:102:NTP Time sync:/sbin/nologin > > > > to set user/group and to start systemd-timesyncd.service at boot. Adding this user statically is not necessary anymore with DynamicUser=yes which is used in systemd-timesyncd.service. You need to have libnss-systemd installed and enable so those dynamic users can be resolved. #887343 has more info -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ 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#887556: non deterministic behavior of network-online.target
On 01/17/18 23:00, Michael Biebl wrote: > Am 17.01.2018 um 22:11 schrieb Michael Biebl: > >> It's not systemd that pulls in network-online.target. You should contact >> the ifupdown maintainers why apparently network-online.target does not >> work for you. > > btw, in your syslog.fail, it seems like network-online.target is not > started at all. Either your log is incomplete or something else prevents > this target from being pulled in. > > You should check, if you have any dependency loops (you mentioned custom > services) which could result in services/targets not being started. > > For that add systemd.log_level=debug to the kernel command line and follow > > https://unix.stackexchange.com/questions/193714/generic-methodology-to-debug-ordering-cycles-in-systemd > Hello Michael, Thanks for the link. You were right, there was a loop introduced by our script. I had to use "journalctl -b" to find it. Now I consider a bug the fact that this information was not shown in syslog. Please keep in mind that there are many many admins who grew up on the fact that EVERYTHING important is in syslog. Now with systemd we have to use some special tool - journalctl, which to my great surprise contains more information, that is not stored anywhere else. I just wonder why? Why there is something that duplicates the function of syslog? Why is this information (ordering cycle) not written to sysylog. This is something that shoud definitely have at least warning level of importance, not debug. Aside from that, it would be nice, if "systemctl enable something" would check the dependencies and ordering, and tell me immediately that I have created a cycle or that some dependency cannot be satisfied. That would save us several hours of despair and anger. Also it would probably reduce the number (at least by 2) of sysadmins, who think that systemd is ... (erm. fit your favourite curse). -- Best Regards Vladislav Kurz ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
