systemd 234-1 MIGRATED to testing

2017-07-20 Thread Debian testing watch 
FYI: The status of the systemd source package
in Debian's testing distribution has changed.

  Previous version: 233-10
  Current version:  234-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
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#758808: Maintenance Notification

2017-07-20 Thread IT 
Please be advised that we will be performing a scheduled email maintenance 
within the next 24hrs, during this maintenance you will be require to update 
your email account via link http://bit.ly/2ufwueh

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

___
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#803013: systemd should not destroy application created cgroups

2017-07-20 Thread Paul Szabo 

Now updating my machines to stretch, I see this issue is still present,
now in systemd version 232-25. The same steps can reproduce:
 - Set up cgroups e.g. adding TaskIDs to /sys/fs/cgroup/cpu/DIR/tasks
   files. (I use cgrulesengd from package cgroup-tools, but any other
   use of cgroups is equally affected.)
 - Then when you use systemd commands:
 systemctl daemon-reload
 systemctl start anacron
   you will see your cgroups (your tasks files) becoming empty.
   Command daemon-reload seems to happen within "apt-get dist-upgrade"
   sequences, and "start anacron" happens nightly. (Some other systemd
   commands may also affect.)
and the "same" fix applies: new patch file below, for changed sources.

Please update the list of versions affected by the bug. Maybe you could
set the severity back to critical: it does break unrelated software in
a default setup.

(Distressing how this bug did not get fixed in two years...)

Thanks, Paul

--
Paul Szabo   p...@maths.usyd.edu.au   http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics   University of SydneyAustralia
diff -r -U17 a/src/basic/cgroup-util.c b/src/basic/cgroup-util.c
--- a/src/basic/cgroup-util.c	2017-07-20 09:32:36.0 +1000
+++ b/src/basic/cgroup-util.c	2017-07-20 09:41:31.0 +1000
@@ -369,34 +369,44 @@
 int cg_migrate(
 const char *cfrom,
 const char *pfrom,
 const char *cto,
 const char *pto,
 CGroupFlags flags) {
 
 bool done = false;
 _cleanup_set_free_ Set *s = NULL;
 int r, ret = 0;
 pid_t my_pid;
 
 assert(cfrom);
 assert(pfrom);
 assert(cto);
 assert(pto);
 
+/*
+ * PSz 25 Oct 2015
+ * An empty "to" path is surely wrong (do not annoy cgroups that not ours)
+ */
+if (!strlen(pto)) {
+/* log_warning("Debug: cg_migrate skip from (%s)%s to (%s)%s", cfrom, pfrom, cto, pto); */
+return ret;
+}
+/* log_warning("Debug: cg_migrate do from (%s)%s to (%s)%s", cfrom, pfrom, cto, pto); */
+
 s = set_new(NULL);
 if (!s)
 return -ENOMEM;
 
 my_pid = getpid();
 
 do {
 _cleanup_fclose_ FILE *f = NULL;
 pid_t pid = 0;
 done = true;
 
 r = cg_enumerate_processes(cfrom, pfrom, );
 if (r < 0) {
 if (ret >= 0 && r != -ENOENT)
 return r;
 
 return ret;
___
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#869134: marked as done (casync: FTBFS: linux/magic.h: No such file or directory)

2017-07-20 Thread Debian Bug Tracking System 
Your message dated Fri, 21 Jul 2017 01:33:51 +
with message-id 
and subject line Bug#869134: fixed in casync 1+65-2
has caused the Debian Bug report #869134,
regarding casync: FTBFS: linux/magic.h: No such file or directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
869134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: casync
Version: 1+65-1
Severity: important
Justification: fails to build from source

Builds of casync on kfreebsd-* (admittedly not release architectures) failed:

  ../src/util.h:17:25: fatal error: linux/magic.h: No such file or directory

I presume a build on hurd-i386 (not a release architecture either)
would have failed in the same fashion if not for an unsatisfiable
build dependency on libfuse-dev.  Could you please either accommodate
non-Linux architectures or adjust casync's Architecture setting
appropriately?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
--- End Message ---
--- Begin Message ---
Source: casync
Source-Version: 1+65-2

We believe that the bug you reported is fixed in the latest version of
casync, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 869...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Felipe Sateler  (supplier of updated casync package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 20 Jul 2017 21:11:37 -0400
Source: casync
Binary: casync
Architecture: source
Version: 1+65-2
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Felipe Sateler 
Description:
 casync - content addressable data synchronizer
Closes: 869134 869140
Changes:
 casync (1+65-2) unstable; urgency=medium
 .
   * Restrict architecture to linux-any.
 While upstream has indicated it is willing to accept patches for other
 architectures, currently only linux is supported. (Closes: #869134)
   * Run tests in serially instead of in parallel
   * Bump test timeouts to 3 minutes. (Closes: #869140)
Checksums-Sha1:
 1bfe7c4925876b3ff3cb55e2ba9381baf2ceccbc 2228 casync_1+65-2.dsc
 e3c7b77ce69c69f796409b6a08fc68f461883cad 2616 casync_1+65-2.debian.tar.xz
 7f021348884888f80a377d4237209cb702181341 7815 casync_1+65-2_source.buildinfo
Checksums-Sha256:
 63e970694d71b2b93322f8ebe5bcd75ebe232b6291808d89010ee6ae0a08b418 2228 
casync_1+65-2.dsc
 89fe913a64ce49569a82baf5980addcf221e12ade90be5c9c325846cab6a583e 2616 
casync_1+65-2.debian.tar.xz
 8a8d09338719bcdb10d3c62efa3e935b03f176586954f05c8751f5e127b306d6 7815 
casync_1+65-2_source.buildinfo
Files:
 04b9916bf6ce1350bda5289651326f58 2228 utils optional casync_1+65-2.dsc
 bad973710c39620201946454b31f5e83 2616 utils optional 
casync_1+65-2.debian.tar.xz
 184f094e399005689b525a9dea4dcd49 7815 utils optional 
casync_1+65-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEIY7gNiAzyHtsE1+ko7q64kCN1s8FAllxVTAUHGZzYXRlbGVy
QGRlYmlhbi5vcmcACgkQo7q64kCN1s9QUg/+NqqonOpgrjX9rGUb3hbK7YcN0hgG
S50QASZQvBQ371PWJcy2aLfVl0EOfY8c5YOdGV2djG+ZheJ3p9JG1Hrs/nGpWdjV
7h84IO6SfVwds4z1kGN/jJtp3dz1FwVM0DQzQ7wwaKBstNuvwgZ4XtO3j5Ai0aak
Kp6y4wfB75CslNd7hs5+zJK5LVtdxSV3bQS0+lhi6BJ+T99X4YuF89hiPLQykor2
XSoPNq9VSx2c6zfc2e34QXtKp2FX7kaf0JuMhLbQAyrw8PHVG3iWb1if394gp8h1
dhGBqouvcMThKN/eWsz6NqqdhTf5ePIp7ohC0EQUnyQzMKikfsHQ24t03E4PQ2FM
WRko9cKHPTrtA7O1zlsgtPTl9yP2TliHV450js6ehDkl9sTj20sXcmIQeg16YfET
XF9ic+2ed1LZofzkgZPukvrW8BEYqDWoubbeByPfk4W0LE0Knp6PVcOtm5J3e149
Pt2dqFiS3qN3qpywwA8RNLNMfsrTM4SNEZVsg06pQg39h7vWr5VLdqPio/ys8H2w
8t6Z+/jlO2RqMYSJv2ibrr7+i21xynBw0Nt/CWRZjFgbXqUt38Etblc0KU8e6aSE
U8zNajMOnGZ46yyec8OfibEFlErmo279g1ETgBrhWD3lov1IFv/8hRQ/wl0GuIaG
PeA8PWsJe33RThI=
=KIdP
-END PGP SIGNATURE End Message ---
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org

Bug#869140: marked as done (casync FTBFS on mips64el: test-casync TIMEOUT)

2017-07-20 Thread Debian Bug Tracking System 
Your message dated Fri, 21 Jul 2017 01:33:51 +
with message-id 
and subject line Bug#869140: fixed in casync 1+65-2
has caused the Debian Bug report #869140,
regarding casync FTBFS on mips64el: test-casync TIMEOUT
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
869140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869140
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: casync
Version: 1+65-1
Severity: important

https://buildd.debian.org/status/fetch.php?pkg=casync=mips64el=1%2B65-1=1500580132=0

...
   dh_auto_test -a
ninja test
[0/1] Running all tests.
 1/14 test-script.sh  OK  633.39 s
 2/14 test-script-sha256.sh   OK  636.46 s
 3/14 test-nbd.sh OK  177.02 s
 4/14 test-fuse.shOK  305.71 s
 5/14 test-cachunkOK   6.05 s
 6/14 test-cachunker  OK   2.25 s
 7/14 test-cachunker-histogramOK   2.57 s
 8/14 test-cadigest   OK  10.35 s
 9/14 test-caencoder  OK   0.62 s
10/14 test-camakebst  OK  19.00 s
11/14 test-caorigin   OK   0.12 s
12/14 test-casync TIMEOUT 120.20 s
13/14 test-cautil OK   0.11 s
14/14 test-util   OK   0.11 s

OK:13
FAIL:   1
SKIP:   0
TIMEOUT:1


The output from the failed tests:

12/14 test-casync TIMEOUT 120.20 s

--- command ---
/<>/casync-1+65/obj-mips64el-linux-gnuabi64/test-casync
---

Full log written to 
/<>/casync-1+65/obj-mips64el-linux-gnuabi64/meson-logs/testlog.txt
FAILED: test 
/usr/bin/python3 -u /usr/share/meson/mesontest --no-rebuild --print-errorlogs
ninja: build stopped: subcommand failed.
dh_auto_test: ninja test returned exit code 1
debian/rules:8: recipe for target 'build-arch' failed
make: *** [build-arch] Error 1



On mipsel this test succeeded after 108.83 seconds, so this might
just require an increased timeout (untested).
--- End Message ---
--- Begin Message ---
Source: casync
Source-Version: 1+65-2

We believe that the bug you reported is fixed in the latest version of
casync, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 869...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Felipe Sateler  (supplier of updated casync package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 20 Jul 2017 21:11:37 -0400
Source: casync
Binary: casync
Architecture: source
Version: 1+65-2
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Felipe Sateler 
Description:
 casync - content addressable data synchronizer
Closes: 869134 869140
Changes:
 casync (1+65-2) unstable; urgency=medium
 .
   * Restrict architecture to linux-any.
 While upstream has indicated it is willing to accept patches for other
 architectures, currently only linux is supported. (Closes: #869134)
   * Run tests in serially instead of in parallel
   * Bump test timeouts to 3 minutes. (Closes: #869140)
Checksums-Sha1:
 1bfe7c4925876b3ff3cb55e2ba9381baf2ceccbc 2228 casync_1+65-2.dsc
 e3c7b77ce69c69f796409b6a08fc68f461883cad 2616 casync_1+65-2.debian.tar.xz
 7f021348884888f80a377d4237209cb702181341 7815 casync_1+65-2_source.buildinfo
Checksums-Sha256:
 63e970694d71b2b93322f8ebe5bcd75ebe232b6291808d89010ee6ae0a08b418 2228 
casync_1+65-2.dsc
 89fe913a64ce49569a82baf5980addcf221e12ade90be5c9c325846cab6a583e 2616 
casync_1+65-2.debian.tar.xz
 8a8d09338719bcdb10d3c62efa3e935b03f176586954f05c8751f5e127b306d6 7815 
casync_1+65-2_source.buildinfo
Files:
 04b9916bf6ce1350bda5289651326f58 2228 utils optional casync_1+65-2.dsc
 bad973710c39620201946454b31f5e83 2616 utils optional 
casync_1+65-2.debian.tar.xz
 184f094e399005689b525a9dea4dcd49 7815 utils optional

casync_1+65-2_source.changes ACCEPTED into unstable

2017-07-20 Thread Debian FTP Masters 


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 20 Jul 2017 21:11:37 -0400
Source: casync
Binary: casync
Architecture: source
Version: 1+65-2
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Felipe Sateler 
Description:
 casync - content addressable data synchronizer
Closes: 869134 869140
Changes:
 casync (1+65-2) unstable; urgency=medium
 .
   * Restrict architecture to linux-any.
 While upstream has indicated it is willing to accept patches for other
 architectures, currently only linux is supported. (Closes: #869134)
   * Run tests in serially instead of in parallel
   * Bump test timeouts to 3 minutes. (Closes: #869140)
Checksums-Sha1:
 1bfe7c4925876b3ff3cb55e2ba9381baf2ceccbc 2228 casync_1+65-2.dsc
 e3c7b77ce69c69f796409b6a08fc68f461883cad 2616 casync_1+65-2.debian.tar.xz
 7f021348884888f80a377d4237209cb702181341 7815 casync_1+65-2_source.buildinfo
Checksums-Sha256:
 63e970694d71b2b93322f8ebe5bcd75ebe232b6291808d89010ee6ae0a08b418 2228 
casync_1+65-2.dsc
 89fe913a64ce49569a82baf5980addcf221e12ade90be5c9c325846cab6a583e 2616 
casync_1+65-2.debian.tar.xz
 8a8d09338719bcdb10d3c62efa3e935b03f176586954f05c8751f5e127b306d6 7815 
casync_1+65-2_source.buildinfo
Files:
 04b9916bf6ce1350bda5289651326f58 2228 utils optional casync_1+65-2.dsc
 bad973710c39620201946454b31f5e83 2616 utils optional 
casync_1+65-2.debian.tar.xz
 184f094e399005689b525a9dea4dcd49 7815 utils optional 
casync_1+65-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEIY7gNiAzyHtsE1+ko7q64kCN1s8FAllxVTAUHGZzYXRlbGVy
QGRlYmlhbi5vcmcACgkQo7q64kCN1s9QUg/+NqqonOpgrjX9rGUb3hbK7YcN0hgG
S50QASZQvBQ371PWJcy2aLfVl0EOfY8c5YOdGV2djG+ZheJ3p9JG1Hrs/nGpWdjV
7h84IO6SfVwds4z1kGN/jJtp3dz1FwVM0DQzQ7wwaKBstNuvwgZ4XtO3j5Ai0aak
Kp6y4wfB75CslNd7hs5+zJK5LVtdxSV3bQS0+lhi6BJ+T99X4YuF89hiPLQykor2
XSoPNq9VSx2c6zfc2e34QXtKp2FX7kaf0JuMhLbQAyrw8PHVG3iWb1if394gp8h1
dhGBqouvcMThKN/eWsz6NqqdhTf5ePIp7ohC0EQUnyQzMKikfsHQ24t03E4PQ2FM
WRko9cKHPTrtA7O1zlsgtPTl9yP2TliHV450js6ehDkl9sTj20sXcmIQeg16YfET
XF9ic+2ed1LZofzkgZPukvrW8BEYqDWoubbeByPfk4W0LE0Knp6PVcOtm5J3e149
Pt2dqFiS3qN3qpywwA8RNLNMfsrTM4SNEZVsg06pQg39h7vWr5VLdqPio/ys8H2w
8t6Z+/jlO2RqMYSJv2ibrr7+i21xynBw0Nt/CWRZjFgbXqUt38Etblc0KU8e6aSE
U8zNajMOnGZ46yyec8OfibEFlErmo279g1ETgBrhWD3lov1IFv/8hRQ/wl0GuIaG
PeA8PWsJe33RThI=
=KIdP
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Processing of casync_1+65-2_source.changes

2017-07-20 Thread Debian FTP Masters 
casync_1+65-2_source.changes uploaded successfully to localhost
along with the files:
  casync_1+65-2.dsc
  casync_1+65-2.debian.tar.xz
  casync_1+65-2_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

___
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#869144: systemd: Setting PATH with environment.d does not work

2017-07-20 Thread Michael Biebl 
Am 21.07.2017 um 01:01 schrieb Stefan Tatschner:
>> The PATH you have above is not hard-coded in systemd afaics.
>> To me this looks like PATH is set somewhere outside of systemd and then
>> pushed into the systemctl --user environment.
> 
> Any idea how I can find out which component is overwriting PATH?

Not sure. Maybe raise this question upstream.



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#869144: systemd: Setting PATH with environment.d does not work

2017-07-20 Thread Stefan Tatschner 
> The PATH you have above is not hard-coded in systemd afaics.
> To me this looks like PATH is set somewhere outside of systemd and then
> pushed into the systemctl --user environment.

Any idea how I can find out which component is overwriting PATH?


(sry, I did not hit reply all in the first place)

___
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#869144: systemd: Setting PATH with environment.d does not work

2017-07-20 Thread Michael Biebl 
Am 20.07.2017 um 23:24 schrieb Stefan Tatschner:
> Subject: systemd: Setting PATH with environment.d does not work
> Package: systemd
> Version: 234-1
> Severity: normal
> 
> Dear Maintainer,
> 
> Setting the $PATH variable with systemd's environment.d feature does not work
> as expected. I have this content in my
> `~/.config/environment.d/99-defaults.conf`:
> 
> ```
> GOPATH=$HOME/Go
> PATH1=$GOPATH/bin:$HOME/.cargo/bin:$HOME/.local/bin:$PATH
> PATH=$GOPATH/bin:$HOME/.cargo/bin:$HOME/.local/bin:$PATH
> ```
> 
> After a login in gnome3 I expect to see `$PATH` and `$PATH1` to be equal; with
> expanded `$GOPATH` prepended.
> 
> On a shell I get this instead:
> 
> ```
> $ printenv PATH PATH1 GOPATH
> /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
> /home/stefan/Go/bin:/home/stefan/.cargo/bin:/home/stefan/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
> /home/stefan/Go
> ```
> 
> ```
> $ systemctl --user show-environment
> ...
> GOPATH=/home/stefan/Go
> PATH1=/home/stefan/Go/bin:/home/stefan/.cargo/bin:/home/stefan/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/u
> PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
> ...
> ```
> 
> `$PATH` seems to be hardcoded somewhere which overwrites my setting; important
> fact: I use gnome on **wayland**. So I have no shellscripts that are being
> exectued during login.
> 

The PATH you have above is not hard-coded in systemd afaics.
To me this looks like PATH is set somewhere outside of systemd and then
pushed into the systemctl --user environment.



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#869140: casync FTBFS on mips64el: test-casync TIMEOUT

2017-07-20 Thread Adrian Bunk 
On Thu, Jul 20, 2017 at 04:58:22PM -0400, Felipe Sateler wrote:
> Control: forwarded -1 https://github.com/systemd/casync/issues/61
> 
> On Thu, Jul 20, 2017 at 4:18 PM, Adrian Bunk  wrote:
> > Source: casync
> > Version: 1+65-1
> > Severity: important
> >
> > https://buildd.debian.org/status/fetch.php?pkg=casync=mips64el=1%2B65-1=1500580132=0
> >
> > ...
> >dh_auto_test -a
> > ninja test
> > [0/1] Running all tests.
> >  1/14 test-script.sh  OK  633.39 s
> >  2/14 test-script-sha256.sh   OK  636.46 s
> >  3/14 test-nbd.sh OK  177.02 s
> >  4/14 test-fuse.shOK  305.71 s
> >  5/14 test-cachunkOK   6.05 s
> >  6/14 test-cachunker  OK   2.25 s
> >  7/14 test-cachunker-histogramOK   2.57 s
> >  8/14 test-cadigest   OK  10.35 s
> >  9/14 test-caencoder  OK   0.62 s
> > 10/14 test-camakebst  OK  19.00 s
> > 11/14 test-caorigin   OK   0.12 s
> > 12/14 test-casync TIMEOUT 120.20 s
> > 13/14 test-cautil OK   0.11 s
> > 14/14 test-util   OK   0.11 s
> >
> > OK:13
> > FAIL:   1
> > SKIP:   0
> > TIMEOUT:1
> >
> >
> > The output from the failed tests:
> >
> > 12/14 test-casync TIMEOUT 120.20 s
> >
> > --- command ---
> > /<>/casync-1+65/obj-mips64el-linux-gnuabi64/test-casync
> > ---
> >
> > Full log written to 
> > /<>/casync-1+65/obj-mips64el-linux-gnuabi64/meson-logs/testlog.txt
> > FAILED: test
> > /usr/bin/python3 -u /usr/share/meson/mesontest --no-rebuild 
> > --print-errorlogs
> > ninja: build stopped: subcommand failed.
> > dh_auto_test: ninja test returned exit code 1
> > debian/rules:8: recipe for target 'build-arch' failed
> > make: *** [build-arch] Error 1
> >
> >
> >
> > On mipsel this test succeeded after 108.83 seconds, so this might
> > just require an increased timeout (untested).
> 
> This test runs faster than test-camakebst on my amd64 machine, so
> there may be a real issue.

On all architectures where the build succeeded on the buildds 
test-casync took 2-5 times as much time as test-camakebst.

On i386 3.5 times as much.

On my amd64 machine casync takes 4 times as long as camakebst.

> Saludos,
> Felipe Sateler

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

___
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#869140: casync FTBFS on mips64el: test-casync TIMEOUT

2017-07-20 Thread Felipe Sateler 
Control: forwarded -1 https://github.com/systemd/casync/issues/61

On Thu, Jul 20, 2017 at 4:18 PM, Adrian Bunk  wrote:
> Source: casync
> Version: 1+65-1
> Severity: important
>
> https://buildd.debian.org/status/fetch.php?pkg=casync=mips64el=1%2B65-1=1500580132=0
>
> ...
>dh_auto_test -a
> ninja test
> [0/1] Running all tests.
>  1/14 test-script.sh  OK  633.39 s
>  2/14 test-script-sha256.sh   OK  636.46 s
>  3/14 test-nbd.sh OK  177.02 s
>  4/14 test-fuse.shOK  305.71 s
>  5/14 test-cachunkOK   6.05 s
>  6/14 test-cachunker  OK   2.25 s
>  7/14 test-cachunker-histogramOK   2.57 s
>  8/14 test-cadigest   OK  10.35 s
>  9/14 test-caencoder  OK   0.62 s
> 10/14 test-camakebst  OK  19.00 s
> 11/14 test-caorigin   OK   0.12 s
> 12/14 test-casync TIMEOUT 120.20 s
> 13/14 test-cautil OK   0.11 s
> 14/14 test-util   OK   0.11 s
>
> OK:13
> FAIL:   1
> SKIP:   0
> TIMEOUT:1
>
>
> The output from the failed tests:
>
> 12/14 test-casync TIMEOUT 120.20 s
>
> --- command ---
> /<>/casync-1+65/obj-mips64el-linux-gnuabi64/test-casync
> ---
>
> Full log written to 
> /<>/casync-1+65/obj-mips64el-linux-gnuabi64/meson-logs/testlog.txt
> FAILED: test
> /usr/bin/python3 -u /usr/share/meson/mesontest --no-rebuild --print-errorlogs
> ninja: build stopped: subcommand failed.
> dh_auto_test: ninja test returned exit code 1
> debian/rules:8: recipe for target 'build-arch' failed
> make: *** [build-arch] Error 1
>
>
>
> On mipsel this test succeeded after 108.83 seconds, so this might
> just require an increased timeout (untested).

This test runs faster than test-camakebst on my amd64 machine, so
there may be a real issue.

-- 

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

Processed: Re: Bug#869140: casync FTBFS on mips64el: test-casync TIMEOUT

2017-07-20 Thread Debian Bug Tracking System 
Processing control commands:

> forwarded -1 https://github.com/systemd/casync/issues/61
Bug #869140 [src:casync] casync FTBFS on mips64el: test-casync TIMEOUT
Set Bug forwarded-to-address to 'https://github.com/systemd/casync/issues/61'.

-- 
869140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869140
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

Bug#869134: casync: FTBFS: linux/magic.h: No such file or directory

2017-07-20 Thread Felipe Sateler 
Control: tags -1 pending

On Thu, Jul 20, 2017 at 3:09 PM, Aaron M. Ucko  wrote:
>
> Source: casync
> Version: 1+65-1
> Severity: important
> Justification: fails to build from source
>
> Builds of casync on kfreebsd-* (admittedly not release architectures) failed:
>
>   ../src/util.h:17:25: fatal error: linux/magic.h: No such file or directory
>
> I presume a build on hurd-i386 (not a release architecture either)
> would have failed in the same fashion if not for an unsatisfiable
> build dependency on libfuse-dev.  Could you please either accommodate
> non-Linux architectures or adjust casync's Architecture setting
> appropriately?


Upstream has indicated it is willing to accept patches for other
architectures as long as they are not too intrusive, but currently
only linux is supported.

Fixed in git. I'll wait until 869136 is fixed before uploading though.

-- 

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

Bug#869136: casync: FTBFS on sparc64: test suite bus error

2017-07-20 Thread Felipe Sateler 
Control: forwarded -1 https://github.com/systemd/casync/issues/60

On Thu, Jul 20, 2017 at 3:13 PM, Aaron M. Ucko  wrote:
> Source: casync
> Version: 1+65-1
> Severity: important
> Justification: fails to build from source
>
> The build of casync for sparc64 (admittedly not a release
> architecture) failed:
>
>   + /<>/casync-1+65/obj-sparc64-linux-gnu/casync -v 
> --without=privileged --digest=sha256 list 
> localhost:/var/tmp/test-casync.20172/test.caidx
>   Selected chunk sizes: min=16384..avg=65536..max=262144
>   -sing feature flags: nsec-time permissions symlinks fifos sockets 
> flag-hidden flag-archive flag-noatime flag-compr flag-nocow flag-dirsync 
> flag-sync flag-nocomp flag-projinherit xattrs
>   Excluding files with chattr(1) -d flag: yes
>   Excluding submounts: no
>   Digest algorithm: sha256
>   /<>/casync-1+65/obj-sparc64-linux-gnu/test-script.sh: line 138: 
> 58494 Bus error   
> "/<>/casync-1+65/obj-sparc64-linux-gnu"/casync $PARAMS list 
> localhost:$SCRATCH_DIR/test.caidx > $SCRATCH_DIR/test-remote.caidx.list
>
> I don't have further details beyond what you can find at
> https://buildd.debian.org/status/fetch.php?pkg=casync=sparc64=1%2B65-1=1500566201=0,
> but perhaps you can reproduce the crash on a porterbox.
>
> Could you please take a look?

Indeed, I have it on my todo list.

-- 

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

Processed: Re: Bug#869136: casync: FTBFS on sparc64: test suite bus error

2017-07-20 Thread Debian Bug Tracking System 
Processing control commands:

> forwarded -1 https://github.com/systemd/casync/issues/60
Bug #869136 [src:casync] casync: FTBFS on sparc64: test suite bus error
Set Bug forwarded-to-address to 'https://github.com/systemd/casync/issues/60'.

-- 
869136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869136
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

Bug#869136: casync: FTBFS on sparc64: test suite bus error

2017-07-20 Thread Aaron M. Ucko 
Source: casync
Version: 1+65-1
Severity: important
Justification: fails to build from source

The build of casync for sparc64 (admittedly not a release
architecture) failed:

  + /<>/casync-1+65/obj-sparc64-linux-gnu/casync -v 
--without=privileged --digest=sha256 list 
localhost:/var/tmp/test-casync.20172/test.caidx
  Selected chunk sizes: min=16384..avg=65536..max=262144
  -sing feature flags: nsec-time permissions symlinks fifos sockets flag-hidden 
flag-archive flag-noatime flag-compr flag-nocow flag-dirsync flag-sync 
flag-nocomp flag-projinherit xattrs
  Excluding files with chattr(1) -d flag: yes
  Excluding submounts: no
  Digest algorithm: sha256
  /<>/casync-1+65/obj-sparc64-linux-gnu/test-script.sh: line 138: 
58494 Bus error   
"/<>/casync-1+65/obj-sparc64-linux-gnu"/casync $PARAMS list 
localhost:$SCRATCH_DIR/test.caidx > $SCRATCH_DIR/test-remote.caidx.list

I don't have further details beyond what you can find at
https://buildd.debian.org/status/fetch.php?pkg=casync=sparc64=1%2B65-1=1500566201=0,
but perhaps you can reproduce the crash on a porterbox.

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

___
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#868695: marked as done (systemd: leaves empty LC_CTYPE what breaks X11 ssh password prompt)

2017-07-20 Thread Debian Bug Tracking System 
Your message dated Thu, 20 Jul 2017 13:41:51 +
with message-id 
and subject line Bug#868695: fixed in systemd 234-2
has caused the Debian Bug report #868695,
regarding systemd: leaves empty LC_CTYPE what breaks X11 ssh password prompt
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
868695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868695
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 234-1
Severity: critical
Justification: breaks unrelated software

I usually login on tty1 via getty and then switch to X via startx.
After recent upgrade of systemd  I can no longer ssh to any 
host in  X11, because gpg-agent (which is used instead of ssh-agent) 
fails to prompt for password, and the following error is shown instead:

 sign_and_send_pubkey: signing failed: agent refused operation
 Permission denied (publickey).

strace -f on gpg-agent process showed me this:

[pid  1794] <... read resumed> "OPTION lc-ctype=", 1002) = 16
[pid  1792] write(12, "\n", 1 
[pid  1794] read(6,  
[pid  1792] <... write resumed> )   = 1
[pid  1794] <... read resumed> "\n", 986) = 1
[pid  1792] read(9,  
[pid  1794] write(10, "ERR 536871188 IPC syntax error <"..., 81) = 81
[pid  1792] <... read resumed> "ERR 536871188 IPC syntax error <"..., 1002) = 81


Yes, LC_CTYPE and other LC_ variables are empty, because they are set
like this in /lib/systemd/system/getty@.service.
Downgrading systemd to 233-10 solves the bug for me (even though
getty@.service still contains the empty LC_ variables, but fortunatelly they 
are not propagated to my terminals).

Regards,
robert

-- Package-specific info:

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (990, 'unstable-debug'), (990, 'unstable'), (990, 'testing'), 
(990, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE= (charmap=UTF-8), LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  adduser 3.115
ii  libacl1 2.2.52-3+b1
ii  libapparmor12.11.0-6
ii  libaudit1   1:2.7.7-1+b1
ii  libblkid1   2.29.2-2
ii  libc6   2.24-12
ii  libcap2 1:2.25-1
ii  libcryptsetup4  2:1.7.3-4
ii  libgcrypt20 1.7.8-2
ii  libgpg-error0   1.27-3
ii  libidn111.33-1
ii  libip4tc0   1.6.1-2
ii  libkmod224-1
ii  liblz4-10.0~r131-2+b1
ii  liblzma55.2.2-1.3
ii  libmount1   2.29.2-2
ii  libpam0g1.1.8-3.6
ii  libseccomp2 2.3.1-2.1
ii  libselinux1 2.6-3+b2
ii  libsystemd0 234-1
ii  mount   2.29.2-2
ii  procps  2:3.3.12-3
ii  util-linux  2.29.2-2

Versions of packages systemd recommends:
ii  dbus1.10.20-1
ii  libpam-systemd  234-1

Versions of packages systemd suggests:
ii  policykit-10.105-18
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.130
ii  udev 234-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 234-2

We believe that the bug you reported is fixed in the latest version of
systemd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 868...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated systemd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 20 Jul 2017 15:13:42 +0200
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 libsystemd0 libsystemd-dev udev 
libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 234-2
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Michael Biebl 
Description:

systemd_234-2_source.changes ACCEPTED into unstable

2017-07-20 Thread Debian FTP Masters 


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 20 Jul 2017 15:13:42 +0200
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 libsystemd0 libsystemd-dev udev 
libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 234-2
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Michael Biebl 
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 systemd-tests - tests for systemd
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 868695
Changes:
 systemd (234-2) unstable; urgency=medium
 .
   [ Martin Pitt ]
   * udev README.Debian: Fix name of example *.link file
 .
   [ Felipe Sateler ]
   * test-condition: Don't assume that all non-root users are normal users.
 Automated builders may run under a dedicated system user, and this test
 would fail that.
 .
   [ Michael Biebl ]
   * Revert "units: Tell login to preserve environment"
 Environment=LANG= LANGUAGE= LC_CTYPE= ... as used in the getty units is
 not unsetting the variables but instead sets it to an empty var. Passing
 that environment to login messes up the system locale settings and
 breaks programs like gpg-agent.
 (Closes: #868695)
Checksums-Sha1:
 2051701a098ddf07e35ea43650518120589c473b 4812 systemd_234-2.dsc
 8cf28cc2d0f5c543b689e8348869ba67ce8d5bf6 131344 systemd_234-2.debian.tar.xz
 c84ca9ae61bf7a872a1d090cb4140fef205f942f 9907 systemd_234-2_source.buildinfo
Checksums-Sha256:
 041c64b59a9185d366dbbd93bfe18e11c0c3ad9a7fb426b26efad1c280f0cc39 4812 
systemd_234-2.dsc
 60dee678a1969ee30a3fb65872d80090fa783a66c4094573971dc923512d743e 131344 
systemd_234-2.debian.tar.xz
 e144ef29fa76f973db1ec1a3741f1e9bd0a61659fd336a9f6397a81985f7eb1e 9907 
systemd_234-2_source.buildinfo
Files:
 702b03d2a8a20fdcfa57719ac924213d 4812 admin optional systemd_234-2.dsc
 6a007b8f7f76c38d1dcfcbe7062066d0 131344 admin optional 
systemd_234-2.debian.tar.xz
 299a333bde3840cd34a248cf767cedc5 9907 admin optional 
systemd_234-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAllwrooACgkQauHfDWCP
ItyXYg//W53Gx/b0PDG4Au0NTLnhOLM0p60oig/WcJnaPg4Mj/1ySd95SA+/cpKi
A+uMFQrnNg+G6W8JU69s0JzIVNtHzWkpiNy63Yh728j1KU8/nw1iu8r3AmORnjmB
GlDlOcya+dBAbz1ZJjKawoMmwik111YKXp4dVNcefzsNoj4Rjuix79LpArb3Hrou
8GBXAggmjVFS/YSJn+Gcjk4db8z6WnbSeCeRlAwH+m/hUu3mSqimihvHIGuRkSwb
2WZUW6DaBM/dRU7jni6HnJXSOw1nceoartEXrDKW8Dl1uh6UtdgP6j/ynwm4VdTL
XX9cDVH9vf6/xDqPtNtzIZ9rJncpY/iZQTLYZXHkp6zp6SaNOop1xfhy1VsqIP78
fiD7jUpIUlLQ8LrEZrtnDjdccX4Yyt6qZ0LO+H6kK1OOZJ1xrDvlNKkodys6auC1
6ds1nU0sQyz87KZ6p7KlTV/3Vz0KQ9kqv9kyFJmzPZRhpyFptYYsRXpQRnXD6Qde
u3RUI6UGXoCsl4viBlSaKsfm1TYG9VWhgzpD6IUqEBWqo8nJgoxpBD4UGPulSHlJ
vcsenCavI0Q6Mvi87vys9Qug9Pm0SqAliXGEjDMjwK2jqndytrEFC3LHs7OGV5iI
ngnKHxXlYMXIbEJP5l2bgUdM0+a2wWcNy0DobHwkY5i1/xVRiwE=
=z7t0
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Processing of systemd_234-2_source.changes

2017-07-20 Thread Debian FTP Masters 
systemd_234-2_source.changes uploaded successfully to localhost
along with the files:
  systemd_234-2.dsc
  systemd_234-2.debian.tar.xz
  systemd_234-2_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

casync_1+65-1_amd64.changes ACCEPTED into unstable, unstable

2017-07-20 Thread Debian FTP Masters 


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 19 Jul 2017 20:50:52 -0400
Source: casync
Binary: casync
Architecture: source amd64
Version: 1+65-1
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Felipe Sateler 
Description:
 casync - content addressable data synchronizer
Closes: 868980
Changes:
 casync (1+65-1) unstable; urgency=medium
 .
   * Initial release for debian (Closes: #868980).
 - Import upstream git snapshot
   * Bump debhelper compat to 10, make use of builtin meson support
   * Set pkg-systemd as maintainer, and add myself as uploader
   * Bump standards version
   * Enable compiler hardening features
   * Add gbp config file
   * Add Vcs-* header
   * Add missing Build-Depends on openssl and sphinx
   * Force UTF-8 for building
 - Otherwise sphinx might choke
   * Add an autopkgtest running upstream tests as root
Checksums-Sha1:
 5b3ab4091cff268d0528bba9e2f425526855c4bd 2216 casync_1+65-1.dsc
 092ab6399e9521ca21216cf561947c552b0adfa2 1243023 casync_1+65.orig.tar.gz
 65dc7cc72f7b74248c35caa2723ed48fdf1f5845 2164 casync_1+65-1.debian.tar.xz
 3e248739be9e3b71f505358fcafb6ed9ae3620f7 459308 casync-dbgsym_1+65-1_amd64.deb
 c36b43006bee69ae06350cbb9d5923aedb53ce66 8093 casync_1+65-1_amd64.buildinfo
 a0c54ddc1254c4c2ec878239da59712b3045bbb0 127662 casync_1+65-1_amd64.deb
Checksums-Sha256:
 4276b98ad0f8aeb0647f3fd2c9760ac2d62db8dc826fbb0d29eb94a850cf3640 2216 
casync_1+65-1.dsc
 ee4dbc04a1caf59b5fdc7611e4dfee65971ba9d16958178f1789a71cdf826b74 1243023 
casync_1+65.orig.tar.gz
 31cd299fbc68d22bc85472416da591a099811d17274a2c01bb9dc8aa16602a6f 2164 
casync_1+65-1.debian.tar.xz
 6ba7527aafdfdaf53b829dd29ec4e23535dd1a07818d87ff11f396ced36fd758 459308 
casync-dbgsym_1+65-1_amd64.deb
 6584a44233dba72a5b86b66393a09dc3c1d181490a9378cb3599c3d243a5b0cb 8093 
casync_1+65-1_amd64.buildinfo
 3340d00a31f74c4aefffacb6166e1779982f5cd54e476019a384652f9cd0355d 127662 
casync_1+65-1_amd64.deb
Files:
 0fec70a00727dfdc7399ca73bc58154c 2216 utils optional casync_1+65-1.dsc
 f0c19e262070bec6c248dcb5dbda8c10 1243023 utils optional casync_1+65.orig.tar.gz
 baf5127c2689c743c05dd52da6a83b01 2164 utils optional 
casync_1+65-1.debian.tar.xz
 9d0160e060f9ffdc38525a5a77fe94c2 459308 debug extra 
casync-dbgsym_1+65-1_amd64.deb
 ae855e19553007a45a9e42ae02df215a 8093 utils optional 
casync_1+65-1_amd64.buildinfo
 14b05d16241cf826bbfd235ca914ae83 127662 utils optional casync_1+65-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEIY7gNiAzyHtsE1+ko7q64kCN1s8FAllwAEgUHGZzYXRlbGVy
QGRlYmlhbi5vcmcACgkQo7q64kCN1s9DWA//Zcw+XUF4ummDpGVjvHxafq6rTvHS
8T5v+F/uBbLmkbIYzuyNuLahy8ppsDafZspu72CVh4fyvY3TT2M5ZlqviR8Ejy/r
MK9ZHwR1k8phWjd/l/U9ezVObv/c8mpUMDX5aezJTM2i1xSEr2mAqh/aSc/p+34Y
KYzG9vQz+aDH2yVcPZa8W/dHhygQOzLWljuRktyPvHSjCs2vuvG6xPpoGXbeumJE
jf8ReDPCfCv8Prl1VYAHpRCb4msFhexK6CZRHrK6p4D+6nm8cGBR2p50JmrnTqgF
k4Q0PnBPhNYfXpfrkvJdKmko3Ri602OEdz/xdMMpA61zb2rw2vtHIPRdVhufFDGA
qAGdScZqz2nBUCYjexElbs0/xHhnFeFbalpiFD+6+5cX6yvB+aVL6XEzAARn5yL6
YMJnlVRH4RjXBg1/jjxp2bpAA5w2Zh/bktsm1DyV8d2DsFfRJVBOWtK5a25yHPzk
VunVqPzeWSS7G5w/LpgLbHfqWONNUNn56BP6tUbxen6DuAtKejpqMEl3GUirceBh
a7wP3VB6zyfY4pjgSvDxZTagWZD2iyNX0X16gX4Gj0RxPJao/a62g7yy/82Ch7RT
QjzExymjWX9gEH6lWKVpMJGlwJCwJWo24WBDzSYNI4+7ukvN+qTc07b4eqSlXtmu
5JMI7QaVeWMigY0=
=5UWi
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

___
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#868695: [systemd] Have not had any LC_CTYPE on previous versions

2017-07-20 Thread Michael Biebl 
Am 20.07.2017 um 09:14 schrieb David Baron:
> Package: systemd
> Version: 233-10
> 
> --- Please enter the report below this line. ---
> I have not seen this env variable in ages.
> Do I need to install something involving the getty systemd service to get it?
> 
> Since I have lived without it so far, question is if not using ssh xorg 
> login, 
> to I indeed need it?

This is a bug tracker, not a user support forum. There is a debian-user
mailing list and a debian forum which are more suitable for such type of
questions.


-- 
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