<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/debian, branch 1.4.3</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.4.3</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.4.3'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2017-05-11T12:46:58Z</updated>
<entry>
<title>Release 1.4.3</title>
<updated>2017-05-11T12:46:58Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-05-11T12:46:58Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=59929e14271f82baa4c7cba4a071df21fe5b9d27'/>
<id>urn:sha1:59929e14271f82baa4c7cba4a071df21fe5b9d27</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Do not try to (re)start timers outside 'apt' package</title>
<updated>2017-05-07T10:23:23Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-05-07T10:17:05Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=315d6aac02b657a4742b5fe2695707904c6033dd'/>
<id>urn:sha1:315d6aac02b657a4742b5fe2695707904c6033dd</id>
<content type='text'>
dh_systemd_start inserted postinst commands in all packages,
rather than just the package containing the timers.

This also gets rid of postinst scripts for all other
packages, yay.

Closes: #862001
</content>
</entry>
<entry>
<title>Release 1.4.2</title>
<updated>2017-05-04T20:57:12Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-05-04T20:57:12Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=1179ac70e9ad100d507c276e6d8de1f9aba08104'/>
<id>urn:sha1:1179ac70e9ad100d507c276e6d8de1f9aba08104</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Split apt-daily timer into two</title>
<updated>2017-05-04T20:49:48Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-04-26T18:03:56Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=496313fb8e83af2ba71f6ce3d729be687c293dfd'/>
<id>urn:sha1:496313fb8e83af2ba71f6ce3d729be687c293dfd</id>
<content type='text'>
The timer doing downloading runs throughout the day, whereas
automatic upgrade and clean actions only happen in the morning.

The upgrade service and timer have After= ordering requirements
on their non-upgrade counterparts to ensure that upgrading at
boot takes place after downloading.

LP: #1686470
</content>
</entry>
<entry>
<title>apt.systemd.daily: Add locking</title>
<updated>2017-05-04T20:49:48Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-04-28T09:11:53Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ea49b66372912354143b810e2826301d651a2b37'/>
<id>urn:sha1:ea49b66372912354143b810e2826301d651a2b37</id>
<content type='text'>
Use a lock file to make sure only one instance of the
script is running at the same time.
</content>
</entry>
<entry>
<title>Run unattended-upgrade -d in download part</title>
<updated>2017-05-03T17:08:50Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-04-26T19:39:16Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=01e324a6893164feace153bc17fe6453b6fa97db'/>
<id>urn:sha1:01e324a6893164feace153bc17fe6453b6fa97db</id>
<content type='text'>
We want to download the upgrades first, if unattended-upgrades
is configured. We don't want to use the normal dist-upgrade -d
thing for it, though, as unattended-upgrades only upgrades a
subset.
</content>
</entry>
<entry>
<title>Allow the daily script to be run in two phases</title>
<updated>2017-04-26T18:45:38Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-04-26T17:58:56Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=007b22ee6fd33d9b03637577f8401a43c5e7c90c'/>
<id>urn:sha1:007b22ee6fd33d9b03637577f8401a43c5e7c90c</id>
<content type='text'>
This adds an argument to the script which may be update, install,
or empty. In the update cases, downloads are performed. In the
install case, installs are performed. If empty, both are run.

Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>Release 1.4.1</title>
<updated>2017-04-24T16:48:35Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-04-24T16:48:35Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=7f18715769a93da7a99438f6de4e2533ac8c7ed8'/>
<id>urn:sha1:7f18715769a93da7a99438f6de4e2533ac8c7ed8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>debian/rules: Actually invoke dh_clean in override_dh_clean</title>
<updated>2017-04-24T16:44:34Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-04-23T20:26:21Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=5a97eaeb839470a7d08a8e21a5529e6b4a2a7e25'/>
<id>urn:sha1:5a97eaeb839470a7d08a8e21a5529e6b4a2a7e25</id>
<content type='text'>
Regression from commit f5e9be1da89725f9bf1915bdf86fdc4a77edf917
</content>
</entry>
<entry>
<title>systemd: Rework timing and add After=network-online</title>
<updated>2017-04-24T16:44:34Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-04-21T19:18:59Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=b4f32b13055287d2ac46a08255db475af195b5f7'/>
<id>urn:sha1:b4f32b13055287d2ac46a08255db475af195b5f7</id>
<content type='text'>
The timeout values were so large that the timer could run at any
random time of the day, possibly easily interfering with business
hours, and causing trouble. Reduce them to 30 minutes of random
delay and an accuracy to the default value (1 minute).

Also drop the 18:00 event. People still actively use their device
during that time, and for servers, there might be less attendance
than in the regular 06:00 time slot, so longer time to fix things
if something breaks.

During a boot, the service might be run to catch up with a timer
that would have normally elapsed. Due to no dependencies, it would
have run before the network is online - that's bad. Adding an After
and a Wants fixes that for boots, but still leaves the same issue
for Resume.

LP: #1615482
</content>
</entry>
</feed>
