Merge ~chad.smith/ubuntu/+source/update-notifier:ua-motd-bionic into ubuntu/+source/update-notifier:ubuntu/bionic-proposed
- Git
- lp:~chad.smith/ubuntu/+source/update-notifier
- ua-motd-bionic
- Merge into ubuntu/bionic-proposed
Status: | Needs review | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Proposed branch: | ~chad.smith/ubuntu/+source/update-notifier:ua-motd-bionic | ||||||||||||
Merge into: | ubuntu/+source/update-notifier:ubuntu/bionic-proposed | ||||||||||||
Diff against target: |
729 lines (+204/-182) (has conflicts) 8 files modified
INSTALL (+159/-161) config.h.in (+8/-0) data/apt_check.py (+11/-10) data/hooks.py (+1/-1) data/package-data-downloader (+2/-2) debian/changelog (+15/-0) tests/test_package-data-downloader.py (+7/-7) tests/test_pep8.py (+1/-1) Conflict in debian/changelog |
||||||||||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Brian Murray | Pending | ||
Review via email: mp+392487@code.launchpad.net |
Commit message
Description of the change
Cherry-picks to sort FTSBFS and missed cherry-pick for motd wording on package updates.
git cherry-pick 6794d0f3d507705
git cherry-pick af28cd4d6 # motd wording
git cherry-pick f881447e2fc755b
Unmerged commits
- 433be1a... by Gianfranco Costamagna
-
Fix E117 over-indented pep issues.
- 1eedf60... by Julian Andres Klode
-
apt-check: Update wording to match spec
- 2d7ed67... by Andrea Azzarone
-
* data/apt_check.py, data/package-
data-downloader , tests/test_pep8.py:
- update the code formating to be not hit W504 warnings,
change to ignore W503 and be consistent with update-manager. - 5e8cdcf... by Chad Smith
-
changelog
- 131011b... by Julian Andres Klode
-
Fix multiple disabled ESM repositories being counted as enabled ones.
- e4b340a... by Brian Murray
-
data/apt_check.py: modify wording and output regarding ESM support.
(LP: #1842508) - 7a72a66... by Andreas Hasenack
-
* data/apt_check.py: Update ESM security pockets names (LP: #1881632)
- the UbuntuESM pocket was renamed from <distro>-security to
<distro> -infra- security
- new origin UbuntuESMApps, with a corresponding pocket of
<distro> -apps-security Patch from
https://bugs.launchpad .net/ubuntu/ +source/ update- notifier/ +bug/1881632/ comments/ 1 - 14b2284... by Julian Andres Klode
-
We told people ESM is not enabled, but not how to enable it.
LP: #1822340
- abaf607... by Julian Andres Klode
-
apt-check: Tell people to enable ESM if ESM updates are available
- 6f97e28... by Julian Andres Klode
-
apt-check: Count enabled ESM upgrades
Preview Diff
1 | diff --git a/INSTALL b/INSTALL |
2 | index 2099840..8865734 100644 |
3 | --- a/INSTALL |
4 | +++ b/INSTALL |
5 | @@ -1,8 +1,8 @@ |
6 | Installation Instructions |
7 | ************************* |
8 | |
9 | -Copyright (C) 1994-1996, 1999-2002, 2004-2013 Free Software Foundation, |
10 | -Inc. |
11 | + Copyright (C) 1994-1996, 1999-2002, 2004-2016 Free Software |
12 | +Foundation, Inc. |
13 | |
14 | Copying and distribution of this file, with or without modification, |
15 | are permitted in any medium without royalty provided the copyright |
16 | @@ -12,97 +12,96 @@ without warranty of any kind. |
17 | Basic Installation |
18 | ================== |
19 | |
20 | - Briefly, the shell command `./configure && make && make install' |
21 | + Briefly, the shell command './configure && make && make install' |
22 | should configure, build, and install this package. The following |
23 | -more-detailed instructions are generic; see the `README' file for |
24 | +more-detailed instructions are generic; see the 'README' file for |
25 | instructions specific to this package. Some packages provide this |
26 | -`INSTALL' file but do not implement all of the features documented |
27 | +'INSTALL' file but do not implement all of the features documented |
28 | below. The lack of an optional feature in a given package is not |
29 | necessarily a bug. More recommendations for GNU packages can be found |
30 | in *note Makefile Conventions: (standards)Makefile Conventions. |
31 | |
32 | - The `configure' shell script attempts to guess correct values for |
33 | + The 'configure' shell script attempts to guess correct values for |
34 | various system-dependent variables used during compilation. It uses |
35 | -those values to create a `Makefile' in each directory of the package. |
36 | -It may also create one or more `.h' files containing system-dependent |
37 | -definitions. Finally, it creates a shell script `config.status' that |
38 | +those values to create a 'Makefile' in each directory of the package. |
39 | +It may also create one or more '.h' files containing system-dependent |
40 | +definitions. Finally, it creates a shell script 'config.status' that |
41 | you can run in the future to recreate the current configuration, and a |
42 | -file `config.log' containing compiler output (useful mainly for |
43 | -debugging `configure'). |
44 | +file 'config.log' containing compiler output (useful mainly for |
45 | +debugging 'configure'). |
46 | |
47 | - It can also use an optional file (typically called `config.cache' |
48 | -and enabled with `--cache-file=config.cache' or simply `-C') that saves |
49 | -the results of its tests to speed up reconfiguring. Caching is |
50 | -disabled by default to prevent problems with accidental use of stale |
51 | -cache files. |
52 | + It can also use an optional file (typically called 'config.cache' and |
53 | +enabled with '--cache-file=config.cache' or simply '-C') that saves the |
54 | +results of its tests to speed up reconfiguring. Caching is disabled by |
55 | +default to prevent problems with accidental use of stale cache files. |
56 | |
57 | If you need to do unusual things to compile the package, please try |
58 | -to figure out how `configure' could check whether to do them, and mail |
59 | -diffs or instructions to the address given in the `README' so they can |
60 | +to figure out how 'configure' could check whether to do them, and mail |
61 | +diffs or instructions to the address given in the 'README' so they can |
62 | be considered for the next release. If you are using the cache, and at |
63 | -some point `config.cache' contains results you don't want to keep, you |
64 | +some point 'config.cache' contains results you don't want to keep, you |
65 | may remove or edit it. |
66 | |
67 | - The file `configure.ac' (or `configure.in') is used to create |
68 | -`configure' by a program called `autoconf'. You need `configure.ac' if |
69 | -you want to change it or regenerate `configure' using a newer version |
70 | -of `autoconf'. |
71 | + The file 'configure.ac' (or 'configure.in') is used to create |
72 | +'configure' by a program called 'autoconf'. You need 'configure.ac' if |
73 | +you want to change it or regenerate 'configure' using a newer version of |
74 | +'autoconf'. |
75 | |
76 | The simplest way to compile this package is: |
77 | |
78 | - 1. `cd' to the directory containing the package's source code and type |
79 | - `./configure' to configure the package for your system. |
80 | + 1. 'cd' to the directory containing the package's source code and type |
81 | + './configure' to configure the package for your system. |
82 | |
83 | - Running `configure' might take a while. While running, it prints |
84 | + Running 'configure' might take a while. While running, it prints |
85 | some messages telling which features it is checking for. |
86 | |
87 | - 2. Type `make' to compile the package. |
88 | + 2. Type 'make' to compile the package. |
89 | |
90 | - 3. Optionally, type `make check' to run any self-tests that come with |
91 | + 3. Optionally, type 'make check' to run any self-tests that come with |
92 | the package, generally using the just-built uninstalled binaries. |
93 | |
94 | - 4. Type `make install' to install the programs and any data files and |
95 | + 4. Type 'make install' to install the programs and any data files and |
96 | documentation. When installing into a prefix owned by root, it is |
97 | recommended that the package be configured and built as a regular |
98 | - user, and only the `make install' phase executed with root |
99 | + user, and only the 'make install' phase executed with root |
100 | privileges. |
101 | |
102 | - 5. Optionally, type `make installcheck' to repeat any self-tests, but |
103 | + 5. Optionally, type 'make installcheck' to repeat any self-tests, but |
104 | this time using the binaries in their final installed location. |
105 | This target does not install anything. Running this target as a |
106 | - regular user, particularly if the prior `make install' required |
107 | + regular user, particularly if the prior 'make install' required |
108 | root privileges, verifies that the installation completed |
109 | correctly. |
110 | |
111 | 6. You can remove the program binaries and object files from the |
112 | - source code directory by typing `make clean'. To also remove the |
113 | - files that `configure' created (so you can compile the package for |
114 | - a different kind of computer), type `make distclean'. There is |
115 | - also a `make maintainer-clean' target, but that is intended mainly |
116 | + source code directory by typing 'make clean'. To also remove the |
117 | + files that 'configure' created (so you can compile the package for |
118 | + a different kind of computer), type 'make distclean'. There is |
119 | + also a 'make maintainer-clean' target, but that is intended mainly |
120 | for the package's developers. If you use it, you may have to get |
121 | all sorts of other programs in order to regenerate files that came |
122 | with the distribution. |
123 | |
124 | - 7. Often, you can also type `make uninstall' to remove the installed |
125 | + 7. Often, you can also type 'make uninstall' to remove the installed |
126 | files again. In practice, not all packages have tested that |
127 | uninstallation works correctly, even though it is required by the |
128 | GNU Coding Standards. |
129 | |
130 | - 8. Some packages, particularly those that use Automake, provide `make |
131 | + 8. Some packages, particularly those that use Automake, provide 'make |
132 | distcheck', which can by used by developers to test that all other |
133 | - targets like `make install' and `make uninstall' work correctly. |
134 | + targets like 'make install' and 'make uninstall' work correctly. |
135 | This target is generally not run by end users. |
136 | |
137 | Compilers and Options |
138 | ===================== |
139 | |
140 | Some systems require unusual options for compilation or linking that |
141 | -the `configure' script does not know about. Run `./configure --help' |
142 | +the 'configure' script does not know about. Run './configure --help' |
143 | for details on some of the pertinent environment variables. |
144 | |
145 | - You can give `configure' initial values for configuration parameters |
146 | -by setting variables in the command line or in the environment. Here |
147 | -is an example: |
148 | + You can give 'configure' initial values for configuration parameters |
149 | +by setting variables in the command line or in the environment. Here is |
150 | +an example: |
151 | |
152 | ./configure CC=c99 CFLAGS=-g LIBS=-lposix |
153 | |
154 | @@ -113,21 +112,21 @@ Compiling For Multiple Architectures |
155 | |
156 | You can compile the package for more than one kind of computer at the |
157 | same time, by placing the object files for each architecture in their |
158 | -own directory. To do this, you can use GNU `make'. `cd' to the |
159 | +own directory. To do this, you can use GNU 'make'. 'cd' to the |
160 | directory where you want the object files and executables to go and run |
161 | -the `configure' script. `configure' automatically checks for the |
162 | -source code in the directory that `configure' is in and in `..'. This |
163 | -is known as a "VPATH" build. |
164 | +the 'configure' script. 'configure' automatically checks for the source |
165 | +code in the directory that 'configure' is in and in '..'. This is known |
166 | +as a "VPATH" build. |
167 | |
168 | - With a non-GNU `make', it is safer to compile the package for one |
169 | + With a non-GNU 'make', it is safer to compile the package for one |
170 | architecture at a time in the source code directory. After you have |
171 | -installed the package for one architecture, use `make distclean' before |
172 | +installed the package for one architecture, use 'make distclean' before |
173 | reconfiguring for another architecture. |
174 | |
175 | On MacOS X 10.5 and later systems, you can create libraries and |
176 | executables that work on multiple system types--known as "fat" or |
177 | -"universal" binaries--by specifying multiple `-arch' options to the |
178 | -compiler but only a single `-arch' option to the preprocessor. Like |
179 | +"universal" binaries--by specifying multiple '-arch' options to the |
180 | +compiler but only a single '-arch' option to the preprocessor. Like |
181 | this: |
182 | |
183 | ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ |
184 | @@ -136,105 +135,104 @@ this: |
185 | |
186 | This is not guaranteed to produce working output in all cases, you |
187 | may have to build one architecture at a time and combine the results |
188 | -using the `lipo' tool if you have problems. |
189 | +using the 'lipo' tool if you have problems. |
190 | |
191 | Installation Names |
192 | ================== |
193 | |
194 | - By default, `make install' installs the package's commands under |
195 | -`/usr/local/bin', include files under `/usr/local/include', etc. You |
196 | -can specify an installation prefix other than `/usr/local' by giving |
197 | -`configure' the option `--prefix=PREFIX', where PREFIX must be an |
198 | + By default, 'make install' installs the package's commands under |
199 | +'/usr/local/bin', include files under '/usr/local/include', etc. You |
200 | +can specify an installation prefix other than '/usr/local' by giving |
201 | +'configure' the option '--prefix=PREFIX', where PREFIX must be an |
202 | absolute file name. |
203 | |
204 | You can specify separate installation prefixes for |
205 | architecture-specific files and architecture-independent files. If you |
206 | -pass the option `--exec-prefix=PREFIX' to `configure', the package uses |
207 | +pass the option '--exec-prefix=PREFIX' to 'configure', the package uses |
208 | PREFIX as the prefix for installing programs and libraries. |
209 | Documentation and other data files still use the regular prefix. |
210 | |
211 | In addition, if you use an unusual directory layout you can give |
212 | -options like `--bindir=DIR' to specify different values for particular |
213 | -kinds of files. Run `configure --help' for a list of the directories |
214 | -you can set and what kinds of files go in them. In general, the |
215 | -default for these options is expressed in terms of `${prefix}', so that |
216 | -specifying just `--prefix' will affect all of the other directory |
217 | +options like '--bindir=DIR' to specify different values for particular |
218 | +kinds of files. Run 'configure --help' for a list of the directories |
219 | +you can set and what kinds of files go in them. In general, the default |
220 | +for these options is expressed in terms of '${prefix}', so that |
221 | +specifying just '--prefix' will affect all of the other directory |
222 | specifications that were not explicitly provided. |
223 | |
224 | The most portable way to affect installation locations is to pass the |
225 | -correct locations to `configure'; however, many packages provide one or |
226 | +correct locations to 'configure'; however, many packages provide one or |
227 | both of the following shortcuts of passing variable assignments to the |
228 | -`make install' command line to change installation locations without |
229 | +'make install' command line to change installation locations without |
230 | having to reconfigure or recompile. |
231 | |
232 | The first method involves providing an override variable for each |
233 | -affected directory. For example, `make install |
234 | +affected directory. For example, 'make install |
235 | prefix=/alternate/directory' will choose an alternate location for all |
236 | directory configuration variables that were expressed in terms of |
237 | -`${prefix}'. Any directories that were specified during `configure', |
238 | -but not in terms of `${prefix}', must each be overridden at install |
239 | -time for the entire installation to be relocated. The approach of |
240 | -makefile variable overrides for each directory variable is required by |
241 | -the GNU Coding Standards, and ideally causes no recompilation. |
242 | -However, some platforms have known limitations with the semantics of |
243 | -shared libraries that end up requiring recompilation when using this |
244 | -method, particularly noticeable in packages that use GNU Libtool. |
245 | - |
246 | - The second method involves providing the `DESTDIR' variable. For |
247 | -example, `make install DESTDIR=/alternate/directory' will prepend |
248 | -`/alternate/directory' before all installation names. The approach of |
249 | -`DESTDIR' overrides is not required by the GNU Coding Standards, and |
250 | +'${prefix}'. Any directories that were specified during 'configure', |
251 | +but not in terms of '${prefix}', must each be overridden at install time |
252 | +for the entire installation to be relocated. The approach of makefile |
253 | +variable overrides for each directory variable is required by the GNU |
254 | +Coding Standards, and ideally causes no recompilation. However, some |
255 | +platforms have known limitations with the semantics of shared libraries |
256 | +that end up requiring recompilation when using this method, particularly |
257 | +noticeable in packages that use GNU Libtool. |
258 | + |
259 | + The second method involves providing the 'DESTDIR' variable. For |
260 | +example, 'make install DESTDIR=/alternate/directory' will prepend |
261 | +'/alternate/directory' before all installation names. The approach of |
262 | +'DESTDIR' overrides is not required by the GNU Coding Standards, and |
263 | does not work on platforms that have drive letters. On the other hand, |
264 | it does better at avoiding recompilation issues, and works well even |
265 | -when some directory options were not specified in terms of `${prefix}' |
266 | -at `configure' time. |
267 | +when some directory options were not specified in terms of '${prefix}' |
268 | +at 'configure' time. |
269 | |
270 | Optional Features |
271 | ================= |
272 | |
273 | If the package supports it, you can cause programs to be installed |
274 | -with an extra prefix or suffix on their names by giving `configure' the |
275 | -option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. |
276 | - |
277 | - Some packages pay attention to `--enable-FEATURE' options to |
278 | -`configure', where FEATURE indicates an optional part of the package. |
279 | -They may also pay attention to `--with-PACKAGE' options, where PACKAGE |
280 | -is something like `gnu-as' or `x' (for the X Window System). The |
281 | -`README' should mention any `--enable-' and `--with-' options that the |
282 | +with an extra prefix or suffix on their names by giving 'configure' the |
283 | +option '--program-prefix=PREFIX' or '--program-suffix=SUFFIX'. |
284 | + |
285 | + Some packages pay attention to '--enable-FEATURE' options to |
286 | +'configure', where FEATURE indicates an optional part of the package. |
287 | +They may also pay attention to '--with-PACKAGE' options, where PACKAGE |
288 | +is something like 'gnu-as' or 'x' (for the X Window System). The |
289 | +'README' should mention any '--enable-' and '--with-' options that the |
290 | package recognizes. |
291 | |
292 | - For packages that use the X Window System, `configure' can usually |
293 | + For packages that use the X Window System, 'configure' can usually |
294 | find the X include and library files automatically, but if it doesn't, |
295 | -you can use the `configure' options `--x-includes=DIR' and |
296 | -`--x-libraries=DIR' to specify their locations. |
297 | +you can use the 'configure' options '--x-includes=DIR' and |
298 | +'--x-libraries=DIR' to specify their locations. |
299 | |
300 | Some packages offer the ability to configure how verbose the |
301 | -execution of `make' will be. For these packages, running `./configure |
302 | +execution of 'make' will be. For these packages, running './configure |
303 | --enable-silent-rules' sets the default to minimal output, which can be |
304 | -overridden with `make V=1'; while running `./configure |
305 | +overridden with 'make V=1'; while running './configure |
306 | --disable-silent-rules' sets the default to verbose, which can be |
307 | -overridden with `make V=0'. |
308 | +overridden with 'make V=0'. |
309 | |
310 | Particular systems |
311 | ================== |
312 | |
313 | - On HP-UX, the default C compiler is not ANSI C compatible. If GNU |
314 | -CC is not installed, it is recommended to use the following options in |
315 | + On HP-UX, the default C compiler is not ANSI C compatible. If GNU CC |
316 | +is not installed, it is recommended to use the following options in |
317 | order to use an ANSI C compiler: |
318 | |
319 | ./configure CC="cc -Ae -D_XOPEN_SOURCE=500" |
320 | |
321 | and if that doesn't work, install pre-built binaries of GCC for HP-UX. |
322 | |
323 | - HP-UX `make' updates targets which have the same time stamps as |
324 | -their prerequisites, which makes it generally unusable when shipped |
325 | -generated files such as `configure' are involved. Use GNU `make' |
326 | -instead. |
327 | + HP-UX 'make' updates targets which have the same time stamps as their |
328 | +prerequisites, which makes it generally unusable when shipped generated |
329 | +files such as 'configure' are involved. Use GNU 'make' instead. |
330 | |
331 | On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot |
332 | -parse its `<wchar.h>' header file. The option `-nodtk' can be used as |
333 | -a workaround. If GNU CC is not installed, it is therefore recommended |
334 | -to try |
335 | +parse its '<wchar.h>' header file. The option '-nodtk' can be used as a |
336 | +workaround. If GNU CC is not installed, it is therefore recommended to |
337 | +try |
338 | |
339 | ./configure CC="cc" |
340 | |
341 | @@ -242,26 +240,26 @@ and if that doesn't work, try |
342 | |
343 | ./configure CC="cc -nodtk" |
344 | |
345 | - On Solaris, don't put `/usr/ucb' early in your `PATH'. This |
346 | + On Solaris, don't put '/usr/ucb' early in your 'PATH'. This |
347 | directory contains several dysfunctional programs; working variants of |
348 | -these programs are available in `/usr/bin'. So, if you need `/usr/ucb' |
349 | -in your `PATH', put it _after_ `/usr/bin'. |
350 | +these programs are available in '/usr/bin'. So, if you need '/usr/ucb' |
351 | +in your 'PATH', put it _after_ '/usr/bin'. |
352 | |
353 | - On Haiku, software installed for all users goes in `/boot/common', |
354 | -not `/usr/local'. It is recommended to use the following options: |
355 | + On Haiku, software installed for all users goes in '/boot/common', |
356 | +not '/usr/local'. It is recommended to use the following options: |
357 | |
358 | ./configure --prefix=/boot/common |
359 | |
360 | Specifying the System Type |
361 | ========================== |
362 | |
363 | - There may be some features `configure' cannot figure out |
364 | + There may be some features 'configure' cannot figure out |
365 | automatically, but needs to determine by the type of machine the package |
366 | will run on. Usually, assuming the package is built to be run on the |
367 | -_same_ architectures, `configure' can figure that out, but if it prints |
368 | +_same_ architectures, 'configure' can figure that out, but if it prints |
369 | a message saying it cannot guess the machine type, give it the |
370 | -`--build=TYPE' option. TYPE can either be a short name for the system |
371 | -type, such as `sun4', or a canonical name which has the form: |
372 | +'--build=TYPE' option. TYPE can either be a short name for the system |
373 | +type, such as 'sun4', or a canonical name which has the form: |
374 | |
375 | CPU-COMPANY-SYSTEM |
376 | |
377 | @@ -270,101 +268,101 @@ where SYSTEM can have one of these forms: |
378 | OS |
379 | KERNEL-OS |
380 | |
381 | - See the file `config.sub' for the possible values of each field. If |
382 | -`config.sub' isn't included in this package, then this package doesn't |
383 | + See the file 'config.sub' for the possible values of each field. If |
384 | +'config.sub' isn't included in this package, then this package doesn't |
385 | need to know the machine type. |
386 | |
387 | If you are _building_ compiler tools for cross-compiling, you should |
388 | -use the option `--target=TYPE' to select the type of system they will |
389 | +use the option '--target=TYPE' to select the type of system they will |
390 | produce code for. |
391 | |
392 | If you want to _use_ a cross compiler, that generates code for a |
393 | platform different from the build platform, you should specify the |
394 | "host" platform (i.e., that on which the generated programs will |
395 | -eventually be run) with `--host=TYPE'. |
396 | +eventually be run) with '--host=TYPE'. |
397 | |
398 | Sharing Defaults |
399 | ================ |
400 | |
401 | - If you want to set default values for `configure' scripts to share, |
402 | -you can create a site shell script called `config.site' that gives |
403 | -default values for variables like `CC', `cache_file', and `prefix'. |
404 | -`configure' looks for `PREFIX/share/config.site' if it exists, then |
405 | -`PREFIX/etc/config.site' if it exists. Or, you can set the |
406 | -`CONFIG_SITE' environment variable to the location of the site script. |
407 | -A warning: not all `configure' scripts look for a site script. |
408 | + If you want to set default values for 'configure' scripts to share, |
409 | +you can create a site shell script called 'config.site' that gives |
410 | +default values for variables like 'CC', 'cache_file', and 'prefix'. |
411 | +'configure' looks for 'PREFIX/share/config.site' if it exists, then |
412 | +'PREFIX/etc/config.site' if it exists. Or, you can set the |
413 | +'CONFIG_SITE' environment variable to the location of the site script. |
414 | +A warning: not all 'configure' scripts look for a site script. |
415 | |
416 | Defining Variables |
417 | ================== |
418 | |
419 | Variables not defined in a site shell script can be set in the |
420 | -environment passed to `configure'. However, some packages may run |
421 | +environment passed to 'configure'. However, some packages may run |
422 | configure again during the build, and the customized values of these |
423 | variables may be lost. In order to avoid this problem, you should set |
424 | -them in the `configure' command line, using `VAR=value'. For example: |
425 | +them in the 'configure' command line, using 'VAR=value'. For example: |
426 | |
427 | ./configure CC=/usr/local2/bin/gcc |
428 | |
429 | -causes the specified `gcc' to be used as the C compiler (unless it is |
430 | +causes the specified 'gcc' to be used as the C compiler (unless it is |
431 | overridden in the site shell script). |
432 | |
433 | -Unfortunately, this technique does not work for `CONFIG_SHELL' due to |
434 | -an Autoconf limitation. Until the limitation is lifted, you can use |
435 | -this workaround: |
436 | +Unfortunately, this technique does not work for 'CONFIG_SHELL' due to an |
437 | +Autoconf limitation. Until the limitation is lifted, you can use this |
438 | +workaround: |
439 | |
440 | CONFIG_SHELL=/bin/bash ./configure CONFIG_SHELL=/bin/bash |
441 | |
442 | -`configure' Invocation |
443 | +'configure' Invocation |
444 | ====================== |
445 | |
446 | - `configure' recognizes the following options to control how it |
447 | + 'configure' recognizes the following options to control how it |
448 | operates. |
449 | |
450 | -`--help' |
451 | -`-h' |
452 | - Print a summary of all of the options to `configure', and exit. |
453 | +'--help' |
454 | +'-h' |
455 | + Print a summary of all of the options to 'configure', and exit. |
456 | |
457 | -`--help=short' |
458 | -`--help=recursive' |
459 | +'--help=short' |
460 | +'--help=recursive' |
461 | Print a summary of the options unique to this package's |
462 | - `configure', and exit. The `short' variant lists options used |
463 | - only in the top level, while the `recursive' variant lists options |
464 | - also present in any nested packages. |
465 | + 'configure', and exit. The 'short' variant lists options used only |
466 | + in the top level, while the 'recursive' variant lists options also |
467 | + present in any nested packages. |
468 | |
469 | -`--version' |
470 | -`-V' |
471 | - Print the version of Autoconf used to generate the `configure' |
472 | +'--version' |
473 | +'-V' |
474 | + Print the version of Autoconf used to generate the 'configure' |
475 | script, and exit. |
476 | |
477 | -`--cache-file=FILE' |
478 | +'--cache-file=FILE' |
479 | Enable the cache: use and save the results of the tests in FILE, |
480 | - traditionally `config.cache'. FILE defaults to `/dev/null' to |
481 | + traditionally 'config.cache'. FILE defaults to '/dev/null' to |
482 | disable caching. |
483 | |
484 | -`--config-cache' |
485 | -`-C' |
486 | - Alias for `--cache-file=config.cache'. |
487 | +'--config-cache' |
488 | +'-C' |
489 | + Alias for '--cache-file=config.cache'. |
490 | |
491 | -`--quiet' |
492 | -`--silent' |
493 | -`-q' |
494 | +'--quiet' |
495 | +'--silent' |
496 | +'-q' |
497 | Do not print messages saying which checks are being made. To |
498 | - suppress all normal output, redirect it to `/dev/null' (any error |
499 | + suppress all normal output, redirect it to '/dev/null' (any error |
500 | messages will still be shown). |
501 | |
502 | -`--srcdir=DIR' |
503 | +'--srcdir=DIR' |
504 | Look for the package's source code in directory DIR. Usually |
505 | - `configure' can determine that directory automatically. |
506 | + 'configure' can determine that directory automatically. |
507 | |
508 | -`--prefix=DIR' |
509 | - Use DIR as the installation prefix. *note Installation Names:: |
510 | - for more details, including other options available for fine-tuning |
511 | - the installation locations. |
512 | +'--prefix=DIR' |
513 | + Use DIR as the installation prefix. *note Installation Names:: for |
514 | + more details, including other options available for fine-tuning the |
515 | + installation locations. |
516 | |
517 | -`--no-create' |
518 | -`-n' |
519 | +'--no-create' |
520 | +'-n' |
521 | Run the configure checks, but stop before creating any output |
522 | files. |
523 | |
524 | -`configure' also accepts some other, not widely useful, options. Run |
525 | -`configure --help' for more details. |
526 | +'configure' also accepts some other, not widely useful, options. Run |
527 | +'configure --help' for more details. |
528 | diff --git a/config.h.in b/config.h.in |
529 | index bcdf201..fb9979f 100644 |
530 | --- a/config.h.in |
531 | +++ b/config.h.in |
532 | @@ -15,6 +15,14 @@ |
533 | /* Define to 1 if you have the `bind_textdomain_codeset' function. */ |
534 | #undef HAVE_BIND_TEXTDOMAIN_CODESET |
535 | |
536 | +/* Define to 1 if you have the Mac OS X function CFLocaleCopyCurrent in the |
537 | + CoreFoundation framework. */ |
538 | +#undef HAVE_CFLOCALECOPYCURRENT |
539 | + |
540 | +/* Define to 1 if you have the Mac OS X function CFPreferencesCopyAppValue in |
541 | + the CoreFoundation framework. */ |
542 | +#undef HAVE_CFPREFERENCESCOPYAPPVALUE |
543 | + |
544 | /* Define to 1 if you have the `dcgettext' function. */ |
545 | #undef HAVE_DCGETTEXT |
546 | |
547 | diff --git a/data/apt_check.py b/data/apt_check.py |
548 | index 6bb716f..ed729c9 100755 |
549 | --- a/data/apt_check.py |
550 | +++ b/data/apt_check.py |
551 | @@ -68,8 +68,8 @@ def isESMUpgrade(ver): |
552 | |
553 | def write_package_names(outstream, cache, depcache): |
554 | " write out package names that change to outstream " |
555 | - pkgs = [pkg for pkg in cache.packages if depcache.marked_install(pkg) or |
556 | - depcache.marked_upgrade(pkg)] |
557 | + pkgs = [pkg for pkg in cache.packages if depcache.marked_install(pkg) |
558 | + or depcache.marked_upgrade(pkg)] |
559 | outstream.write("\n".join([p.name for p in pkgs])) |
560 | |
561 | |
562 | @@ -90,8 +90,10 @@ def write_human_readable_summary(outstream, upgrades, security_updates, |
563 | outstream.write("\n\n") |
564 | |
565 | outstream.write(gettext.dngettext("update-notifier", |
566 | - "%i package can be updated.", |
567 | - "%i packages can be updated.", |
568 | + "%i update can be installed " |
569 | + "immediately.", |
570 | + "%i updates can be installed " |
571 | + "immediately.", |
572 | upgrades) % upgrades) |
573 | outstream.write("\n") |
574 | if esm_updates > 0: |
575 | @@ -228,8 +230,8 @@ def run(options=None): |
576 | disabled_esm_updates += 1 |
577 | |
578 | # skip packages that are not marked upgraded/installed |
579 | - if not (depcache.marked_install(pkg) or |
580 | - depcache.marked_upgrade(pkg)): |
581 | + if not (depcache.marked_install(pkg) |
582 | + or depcache.marked_upgrade(pkg)): |
583 | continue |
584 | # check if this is really a upgrade or a false positive |
585 | # (workaround for ubuntu #7907) |
586 | @@ -262,10 +264,9 @@ def run(options=None): |
587 | # now check for security updates that are masked by a |
588 | # candidate version from another repo (-proposed or -updates) |
589 | for ver in pkg.version_list: |
590 | - if (inst_ver and apt_pkg.version_compare(ver.ver_str, |
591 | - inst_ver.ver_str) <= |
592 | - 0): |
593 | - # print("skipping '%s' " % ver.VerStr) |
594 | + if (inst_ver |
595 | + and apt_pkg.version_compare(ver.ver_str, |
596 | + inst_ver.ver_str) <= 0): |
597 | continue |
598 | if isESMUpgrade(ver): |
599 | esm_updates += 1 |
600 | diff --git a/data/hooks.py b/data/hooks.py |
601 | index 5585e33..034852c 100755 |
602 | --- a/data/hooks.py |
603 | +++ b/data/hooks.py |
604 | @@ -75,7 +75,7 @@ class HookFiles(object): |
605 | # we last saw it |
606 | h = self._hooks[hook] |
607 | if os.stat(self.hookDir + hook).st_mtime > int(h.mtime): |
608 | - h.seen = False |
609 | + h.seen = False |
610 | else: |
611 | self._hooks[hook] = self.HookFile(hook) |
612 | |
613 | diff --git a/data/package-data-downloader b/data/package-data-downloader |
614 | index f7d8566..00b4aff 100755 |
615 | --- a/data/package-data-downloader |
616 | +++ b/data/package-data-downloader |
617 | @@ -160,8 +160,8 @@ def get_hook_file_names(): |
618 | res = [] |
619 | for relfile in os.listdir(DATADIR): |
620 | # ignore files ending in .dpkg-* |
621 | - if (os.path.splitext(relfile)[1] and |
622 | - os.path.splitext(relfile)[1].startswith(".dpkg")): |
623 | + if (os.path.splitext(relfile)[1] |
624 | + and os.path.splitext(relfile)[1].startswith(".dpkg")): |
625 | continue |
626 | res.append(relfile) |
627 | return res |
628 | diff --git a/debian/changelog b/debian/changelog |
629 | index b688483..6f198c7 100644 |
630 | --- a/debian/changelog |
631 | +++ b/debian/changelog |
632 | @@ -1,3 +1,18 @@ |
633 | +<<<<<<< debian/changelog |
634 | +======= |
635 | +update-notifier (3.192.1.9) bionic; urgency=medium |
636 | + |
637 | + [ Gianfranco Costamagna ] |
638 | + * Fix E117 over-indented pep issues. |
639 | + |
640 | + [ Andrea Azzarone ] |
641 | + * data/apt_check.py, data/package-data-downloader, tests/test_pep8.py: |
642 | + - update the code formating to be not hit W504 warnings, |
643 | + change to ignore W503 and be consistent with update-manager. |
644 | + |
645 | + -- Chad Smith <chad.smith@canonical.com> Tue, 16 Oct 2020 15:35:29 -0600 |
646 | + |
647 | +>>>>>>> debian/changelog |
648 | update-notifier (3.192.1.8) bionic; urgency=medium |
649 | |
650 | [ Andreas Hasenack ] |
651 | diff --git a/tests/test_package-data-downloader.py b/tests/test_package-data-downloader.py |
652 | index 8680d4c..9c7e53c 100644 |
653 | --- a/tests/test_package-data-downloader.py |
654 | +++ b/tests/test_package-data-downloader.py |
655 | @@ -123,7 +123,7 @@ class ProcessDownloadRequestsTestCase(unittest.TestCase): |
656 | stampfile = os.path.join(package_data_downloader.STAMPDIR, |
657 | hookfile) |
658 | with open(stampfile, "w"): |
659 | - pass |
660 | + pass |
661 | orig_stamp_time = os.stat(stampfile).st_mtime |
662 | package_data_downloader.process_download_requests() |
663 | new_stamp_time = os.stat(stampfile).st_mtime |
664 | @@ -141,7 +141,7 @@ class ProcessDownloadRequestsTestCase(unittest.TestCase): |
665 | stampfile = os.path.join(package_data_downloader.STAMPDIR, |
666 | hookfile) |
667 | with open(stampfile, "w"): |
668 | - pass |
669 | + pass |
670 | orig_stamp_date = os.stat(stampfile).st_mtime |
671 | time.sleep(0.01) |
672 | # create the hook file |
673 | @@ -191,7 +191,7 @@ class ProcessDownloadRequestsTestCase(unittest.TestCase): |
674 | stampfile = os.path.join(package_data_downloader.STAMPDIR, |
675 | hookfile) |
676 | with open(stampfile, "w"): |
677 | - pass |
678 | + pass |
679 | time.sleep(0.01) |
680 | # create the hook file |
681 | self._setup_hook_file(hookfile, "/bin/false") |
682 | @@ -207,7 +207,7 @@ class ProcessDownloadRequestsTestCase(unittest.TestCase): |
683 | stampfile = os.path.join(package_data_downloader.STAMPDIR, |
684 | hookfile) |
685 | with open(stampfile, "w"): |
686 | - pass |
687 | + pass |
688 | time.sleep(0.01) |
689 | self._setup_hook_file(hookfile) |
690 | # create an empty notifier file |
691 | @@ -222,7 +222,7 @@ class ProcessDownloadRequestsTestCase(unittest.TestCase): |
692 | stampfile = os.path.join(package_data_downloader.STAMPDIR, |
693 | hookfile) |
694 | with open(stampfile, "w"): |
695 | - pass |
696 | + pass |
697 | time.sleep(0.01) |
698 | self._setup_hook_file(hookfile) |
699 | # create empty notifier files |
700 | @@ -241,7 +241,7 @@ class ProcessDownloadRequestsTestCase(unittest.TestCase): |
701 | stampfile = os.path.join(package_data_downloader.STAMPDIR, |
702 | hookfile) |
703 | with open(stampfile, "w"): |
704 | - pass |
705 | + pass |
706 | time.sleep(0.01) |
707 | self._setup_hook_file(hookfile) |
708 | # create an empty permanent notifier file |
709 | @@ -257,7 +257,7 @@ class ProcessDownloadRequestsTestCase(unittest.TestCase): |
710 | stampfile = os.path.join(package_data_downloader.STAMPDIR, |
711 | hookfile) |
712 | with open(stampfile, "w"): |
713 | - pass |
714 | + pass |
715 | time.sleep(0.01) |
716 | # overwrite canary file to create a failure |
717 | self.canary_file = "not-there.txt" |
718 | diff --git a/tests/test_pep8.py b/tests/test_pep8.py |
719 | index fa6c416..96f68c0 100644 |
720 | --- a/tests/test_pep8.py |
721 | +++ b/tests/test_pep8.py |
722 | @@ -6,7 +6,7 @@ import subprocess |
723 | import unittest |
724 | |
725 | # pep8 is overdoing it a bit IMO |
726 | -IGNORE_PEP8 = "E265" |
727 | +IGNORE_PEP8 = "E265, W503" |
728 | IGNORE_FILES = ( |
729 | ) |
730 |