pax_global_header 0000666 0000000 0000000 00000000064 13727517464 0014532 g ustar 00root root 0000000 0000000 52 comment=be2f596522225a36239fdd666dedfbf57b5ad378
pibootctl-0.5.2/ 0000775 0000000 0000000 00000000000 13727517464 0013535 5 ustar 00root root 0000000 0000000 pibootctl-0.5.2/.gitignore 0000664 0000000 0000000 00000000330 13727517464 0015521 0 ustar 00root root 0000000 0000000 # Python stuff
*.py[cdo]
# Vim stuff
*.vim
*.swp
# Miscellaneous
tags
# Packages
*.egg
*.egg-info
*.pyc
*.whl
dist
build
man
# Unit test / coverage reports
coverage
.cache
.coverage
.tox
.pytest_cache
.env
.eggs
pibootctl-0.5.2/LICENSE.txt 0000664 0000000 0000000 00000104516 13727517464 0015367 0 ustar 00root root 0000000 0000000
GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc.
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The GNU General Public License is a free, copyleft license for
software and other kinds of works.
The licenses for most software and other practical works are designed
to take away your freedom to share and change the works. By contrast,
the GNU General Public License is intended to guarantee your freedom to
share and change all versions of a program--to make sure it remains free
software for all its users. We, the Free Software Foundation, use the
GNU General Public License for most of our software; it applies also to
any other work released this way by its authors. You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you
these rights or asking you to surrender the rights. Therefore, you have
certain responsibilities if you distribute copies of the software, or if
you modify it: responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received. You must make sure that they, too, receive
or can get the source code. And you must show them these terms so they
know their rights.
Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software. For both users' and
authors' sake, the GPL requires that modified versions be marked as
changed, so that their problems will not be attributed erroneously to
authors of previous versions.
Some devices are designed to deny users access to install or run
modified versions of the software inside them, although the manufacturer
can do so. This is fundamentally incompatible with the aim of
protecting users' freedom to change the software. The systematic
pattern of such abuse occurs in the area of products for individuals to
use, which is precisely where it is most unacceptable. Therefore, we
have designed this version of the GPL to prohibit the practice for those
products. If such problems arise substantially in other domains, we
stand ready to extend this provision to those domains in future versions
of the GPL, as needed to protect the freedom of users.
Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
software on general-purpose computers, but in those that do, we wish to
avoid the special danger that patents applied to a free program could
make it effectively proprietary. To prevent this, the GPL assures that
patents cannot be used to render the program non-free.
The precise terms and conditions for copying, distribution and
modification follow.
TERMS AND CONDITIONS
0. Definitions.
"This License" refers to version 3 of the GNU General Public License.
"Copyright" also means copyright-like laws that apply to other kinds of
works, such as semiconductor masks.
"The Program" refers to any copyrightable work licensed under this
License. Each licensee is addressed as "you". "Licensees" and
"recipients" may be individuals or organizations.
To "modify" a work means to copy from or adapt all or part of the work
in a fashion requiring copyright permission, other than the making of an
exact copy. The resulting work is called a "modified version" of the
earlier work or a work "based on" the earlier work.
A "covered work" means either the unmodified Program or a work based
on the Program.
To "propagate" a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
infringement under applicable copyright law, except executing it on a
computer or modifying a private copy. Propagation includes copying,
distribution (with or without modification), making available to the
public, and in some countries other activities as well.
To "convey" a work means any kind of propagation that enables other
parties to make or receive copies. Mere interaction with a user through
a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays "Appropriate Legal Notices"
to the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to the
extent that warranties are provided), that licensees may convey the
work under this License, and how to view a copy of this License. If
the interface presents a list of user commands or options, such as a
menu, a prominent item in the list meets this criterion.
1. Source Code.
The "source code" for a work means the preferred form of the work
for making modifications to it. "Object code" means any non-source
form of a work.
A "Standard Interface" means an interface that either is an official
standard defined by a recognized standards body, or, in the case of
interfaces specified for a particular programming language, one that
is widely used among developers working in that language.
The "System Libraries" of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form. A
"Major Component", in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system
(if any) on which the executable work runs, or a compiler used to
produce the work, or an object code interpreter used to run it.
The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
work) run the object code and to modify the work, including scripts to
control those activities. However, it does not include the work's
System Libraries, or general-purpose tools or generally available free
programs which are used unmodified in performing those activities but
which are not part of the work. For example, Corresponding Source
includes interface definition files associated with source files for
the work, and the source code for shared libraries and dynamically
linked subprograms that the work is specifically designed to require,
such as by intimate data communication or control flow between those
subprograms and other parts of the work.
The Corresponding Source need not include anything that users
can regenerate automatically from other parts of the Corresponding
Source.
The Corresponding Source for a work in source code form is that
same work.
2. Basic Permissions.
All rights granted under this License are granted for the term of
copyright on the Program, and are irrevocable provided the stated
conditions are met. This License explicitly affirms your unlimited
permission to run the unmodified Program. The output from running a
covered work is covered by this License only if the output, given its
content, constitutes a covered work. This License acknowledges your
rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not
convey, without conditions so long as your license otherwise remains
in force. You may convey covered works to others for the sole purpose
of having them make modifications exclusively for you, or provide you
with facilities for running those works, provided that you comply with
the terms of this License in conveying all material for which you do
not control copyright. Those thus making or running the covered works
for you must do so exclusively on your behalf, under your direction
and control, on terms that prohibit them from making any copies of
your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under
the conditions stated below. Sublicensing is not allowed; section 10
makes it unnecessary.
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological
measure under any applicable law fulfilling obligations under article
11 of the WIPO copyright treaty adopted on 20 December 1996, or
similar laws prohibiting or restricting circumvention of such
measures.
When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such circumvention
is effected by exercising rights under this License with respect to
the covered work, and you disclaim any intention to limit operation or
modification of the work as a means of enforcing, against the work's
users, your or third parties' legal rights to forbid circumvention of
technological measures.
4. Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice;
keep intact all notices stating that this License and any
non-permissive terms added in accord with section 7 apply to the code;
keep intact all notices of the absence of any warranty; and give all
recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey,
and you may offer support or warranty protection for a fee.
5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to
produce it from the Program, in the form of source code under the
terms of section 4, provided that you also meet all of these conditions:
a) The work must carry prominent notices stating that you modified
it, and giving a relevant date.
b) The work must carry prominent notices stating that it is
released under this License and any conditions added under section
7. This requirement modifies the requirement in section 4 to
"keep intact all notices".
c) You must license the entire work, as a whole, under this
License to anyone who comes into possession of a copy. This
License will therefore apply, along with any applicable section 7
additional terms, to the whole of the work, and all its parts,
regardless of how they are packaged. This License gives no
permission to license the work in any other way, but it does not
invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display
Appropriate Legal Notices; however, if the Program has interactive
interfaces that do not display Appropriate Legal Notices, your
work need not make them do so.
A compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called an
"aggregate" if the compilation and its resulting copyright are not
used to limit the access or legal rights of the compilation's users
beyond what the individual works permit. Inclusion of a covered work
in an aggregate does not cause this License to apply to the other
parts of the aggregate.
6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms
of sections 4 and 5, provided that you also convey the
machine-readable Corresponding Source under the terms of this License,
in one of these ways:
a) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by the
Corresponding Source fixed on a durable physical medium
customarily used for software interchange.
b) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a
written offer, valid for at least three years and valid for as
long as you offer spare parts or customer support for that product
model, to give anyone who possesses the object code either (1) a
copy of the Corresponding Source for all the software in the
product that is covered by this License, on a durable physical
medium customarily used for software interchange, for a price no
more than your reasonable cost of physically performing this
conveying of source, or (2) access to copy the
Corresponding Source from a network server at no charge.
c) Convey individual copies of the object code with a copy of the
written offer to provide the Corresponding Source. This
alternative is allowed only occasionally and noncommercially, and
only if you received the object code with such an offer, in accord
with subsection 6b.
d) Convey the object code by offering access from a designated
place (gratis or for a charge), and offer equivalent access to the
Corresponding Source in the same way through the same place at no
further charge. You need not require recipients to copy the
Corresponding Source along with the object code. If the place to
copy the object code is a network server, the Corresponding Source
may be on a different server (operated by you or a third party)
that supports equivalent copying facilities, provided you maintain
clear directions next to the object code saying where to find the
Corresponding Source. Regardless of what server hosts the
Corresponding Source, you remain obligated to ensure that it is
available for as long as needed to satisfy these requirements.
e) Convey the object code using peer-to-peer transmission, provided
you inform other peers where the object code and Corresponding
Source of the work are being offered to the general public at no
charge under subsection 6d.
A separable portion of the object code, whose source code is excluded
from the Corresponding Source as a System Library, need not be
included in conveying the object code work.
A "User Product" is either (1) a "consumer product", which means any
tangible personal property which is normally used for personal, family,
or household purposes, or (2) anything designed or sold for incorporation
into a dwelling. In determining whether a product is a consumer product,
doubtful cases shall be resolved in favor of coverage. For a particular
product received by a particular user, "normally used" refers to a
typical or common use of that class of product, regardless of the status
of the particular user or of the way in which the particular user
actually uses, or expects or is expected to use, the product. A product
is a consumer product regardless of whether the product has substantial
commercial, industrial or non-consumer uses, unless such uses represent
the only significant mode of use of the product.
"Installation Information" for a User Product means any methods,
procedures, authorization keys, or other information required to install
and execute modified versions of a covered work in that User Product from
a modified version of its Corresponding Source. The information must
suffice to ensure that the continued functioning of the modified object
code is in no case prevented or interfered with solely because
modification has been made.
If you convey an object code work under this section in, or with, or
specifically for use in, a User Product, and the conveying occurs as
part of a transaction in which the right of possession and use of the
User Product is transferred to the recipient in perpetuity or for a
fixed term (regardless of how the transaction is characterized), the
Corresponding Source conveyed under this section must be accompanied
by the Installation Information. But this requirement does not apply
if neither you nor any third party retains the ability to install
modified object code on the User Product (for example, the work has
been installed in ROM).
The requirement to provide Installation Information does not include a
requirement to continue to provide support service, warranty, or updates
for a work that has been modified or installed by the recipient, or for
the User Product in which it has been modified or installed. Access to a
network may be denied when the modification itself materially and
adversely affects the operation of the network or violates the rules and
protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.
7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this
License by making exceptions from one or more of its conditions.
Additional permissions that are applicable to the entire Program shall
be treated as though they were included in this License, to the extent
that they are valid under applicable law. If additional permissions
apply only to part of the Program, that part may be used separately
under those permissions, but the entire Program remains governed by
this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy, or from any part of
it. (Additional permissions may be written to require their own
removal in certain cases when you modify the work.) You may place
additional permissions on material, added by you to a covered work,
for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you
add to a covered work, you may (if authorized by the copyright holders of
that material) supplement the terms of this License with terms:
a) Disclaiming warranty or limiting liability differently from the
terms of sections 15 and 16 of this License; or
b) Requiring preservation of specified reasonable legal notices or
author attributions in that material or in the Appropriate Legal
Notices displayed by works containing it; or
c) Prohibiting misrepresentation of the origin of that material, or
requiring that modified versions of such material be marked in
reasonable ways as different from the original version; or
d) Limiting the use for publicity purposes of names of licensors or
authors of the material; or
e) Declining to grant rights under trademark law for use of some
trade names, trademarks, or service marks; or
f) Requiring indemnification of licensors and authors of that
material by anyone who conveys the material (or modified versions of
it) with contractual assumptions of liability to the recipient, for
any liability that these contractual assumptions directly impose on
those licensors and authors.
All other non-permissive additional terms are considered "further
restrictions" within the meaning of section 10. If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term. If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
additional terms that apply to those files, or a notice indicating
where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the
form of a separately written license, or stated as exceptions;
the above requirements apply either way.
8. Termination.
You may not propagate or modify a covered work except as expressly
provided under this License. Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights under
this License (including any patent licenses granted under the third
paragraph of section 11).
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
provisionally, unless and until the copyright holder explicitly and
finally terminates your license, and (b) permanently, if the copyright
holder fails to notify you of the violation by some reasonable means
prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, you do not qualify to receive new licenses for the same
material under section 10.
9. Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or
run a copy of the Program. Ancillary propagation of a covered work
occurring solely as a consequence of using peer-to-peer transmission
to receive a copy likewise does not require acceptance. However,
nothing other than this License grants you permission to propagate or
modify any covered work. These actions infringe copyright if you do
not accept this License. Therefore, by modifying or propagating a
covered work, you indicate your acceptance of this License to do so.
10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
propagate that work, subject to this License. You are not responsible
for enforcing compliance by third parties with this License.
An "entity transaction" is a transaction transferring control of an
organization, or substantially all assets of one, or subdividing an
organization, or merging organizations. If propagation of a covered
work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or could
give under the previous paragraph, plus a right to possession of the
Corresponding Source of the work from the predecessor in interest, if
the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you may
not impose a license fee, royalty, or other charge for exercise of
rights granted under this License, and you may not initiate litigation
(including a cross-claim or counterclaim in a lawsuit) alleging that
any patent claim is infringed by making, using, selling, offering for
sale, or importing the Program or any portion of it.
11. Patents.
A "contributor" is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based. The
work thus licensed is called the contributor's "contributor version".
A contributor's "essential patent claims" are all patent claims
owned or controlled by the contributor, whether already acquired or
hereafter acquired, that would be infringed by some manner, permitted
by this License, of making, using, or selling its contributor version,
but do not include claims that would be infringed only as a
consequence of further modification of the contributor version. For
purposes of this definition, "control" includes the right to grant
patent sublicenses in a manner consistent with the requirements of
this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free
patent license under the contributor's essential patent claims, to
make, use, sell, offer for sale, import and otherwise run, modify and
propagate the contents of its contributor version.
In the following three paragraphs, a "patent license" is any express
agreement or commitment, however denominated, not to enforce a patent
(such as an express permission to practice a patent or covenant not to
sue for patent infringement). To "grant" such a patent license to a
party means to make such an agreement or commitment not to enforce a
patent against the party.
If you convey a covered work, knowingly relying on a patent license,
and the Corresponding Source of the work is not available for anyone
to copy, free of charge and under the terms of this License, through a
publicly available network server or other readily accessible means,
then you must either (1) cause the Corresponding Source to be so
available, or (2) arrange to deprive yourself of the benefit of the
patent license for this particular work, or (3) arrange, in a manner
consistent with the requirements of this License, to extend the patent
license to downstream recipients. "Knowingly relying" means you have
actual knowledge that, but for the patent license, your conveying the
covered work in a country, or your recipient's use of the covered work
in a country, would infringe one or more identifiable patents in that
country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or
arrangement, you convey, or propagate by procuring conveyance of, a
covered work, and grant a patent license to some of the parties
receiving the covered work authorizing them to use, propagate, modify
or convey a specific copy of the covered work, then the patent license
you grant is automatically extended to all recipients of the covered
work and works based on it.
A patent license is "discriminatory" if it does not include within
the scope of its coverage, prohibits the exercise of, or is
conditioned on the non-exercise of one or more of the rights that are
specifically granted under this License. You may not convey a covered
work if you are a party to an arrangement with a third party that is
in the business of distributing software, under which you make payment
to the third party based on the extent of your activity of conveying
the work, and under which the third party grants, to any of the
parties who would receive the covered work from you, a discriminatory
patent license (a) in connection with copies of the covered work
conveyed by you (or copies made from those copies), or (b) primarily
for and in connection with specific products or compilations that
contain the covered work, unless you entered into that arrangement,
or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.
12. No Surrender of Others' Freedom.
If conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot convey a
covered work so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you may
not convey it at all. For example, if you agree to terms that obligate you
to collect a royalty for further conveying from those to whom you convey
the Program, the only way you could satisfy both those terms and this
License would be to refrain entirely from conveying the Program.
13. Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
under version 3 of the GNU Affero General Public License into a single
combined work, and to convey the resulting work. The terms of this
License will continue to apply to the part which is the covered work,
but the special requirements of the GNU Affero General Public License,
section 13, concerning interaction through a network will apply to the
combination as such.
14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of
the GNU General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the
Program specifies that a certain numbered version of the GNU General
Public License "or any later version" applies to it, you have the
option of following the terms and conditions either of that numbered
version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the
GNU General Public License, you may choose any version ever published
by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.
Later license versions may give you additional or different
permissions. However, no additional obligations are imposed on any
author or copyright holder as a result of your choosing to follow a
later version.
15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
reviewing courts shall apply local law that most closely approximates
an absolute waiver of all civil liability in connection with the
Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
Copyright (C)
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see .
Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:
Copyright (C)
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, your program's commands
might be different; for a GUI interface, you would use an "about box".
You should also get your employer (if you work as a programmer) or school,
if any, to sign a "copyright disclaimer" for the program, if necessary.
For more information on this, and how to apply and follow the GNU GPL, see
.
The GNU General Public License does not permit incorporating your program
into proprietary programs. If your program is a subroutine library, you
may consider it more useful to permit linking proprietary applications with
the library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License. But first, please read
.
pibootctl-0.5.2/Makefile 0000664 0000000 0000000 00000013654 13727517464 0015206 0 ustar 00root root 0000000 0000000 # vim: set noet sw=4 ts=4 fileencoding=utf-8:
# External utilities
PYTHON=python3
PIP=pip
PYTEST=pytest
COVERAGE=coverage
TWINE=twine
PYFLAGS=
DEST_DIR=/
# Calculate the base names of the distribution, the location of all source,
# documentation, packaging, icon, and executable script files
NAME:=$(shell $(PYTHON) $(PYFLAGS) setup.py --name)
PKG_DIR:=$(subst -,_,$(NAME))
VER:=$(shell $(PYTHON) $(PYFLAGS) setup.py --version)
DEB_ARCH:=$(shell dpkg --print-architecture)
DEB_SUFFIX:=
PY_SOURCES:=$(shell \
$(PYTHON) $(PYFLAGS) setup.py egg_info >/dev/null 2>&1 && \
grep -v "\.egg-info" $(PKG_DIR).egg-info/SOURCES.txt)
DEB_SOURCES:=debian/changelog \
debian/control \
debian/copyright \
debian/rules \
debian/docs \
$(wildcard debian/*.init) \
$(wildcard debian/*.default) \
$(wildcard debian/*.manpages) \
$(wildcard debian/*.docs) \
$(wildcard debian/*.doc-base) \
$(wildcard debian/*.desktop)
DOC_SOURCES:=docs/conf.py \
$(wildcard docs/*.png) \
$(wildcard docs/*.svg) \
$(wildcard docs/*.dot) \
$(wildcard docs/*.mscgen) \
$(wildcard docs/*.gpi) \
$(wildcard docs/*.rst) \
$(wildcard docs/*.pdf)
SUBDIRS:=
# Calculate the name of all outputs
DIST_WHEEL=dist/$(NAME)-$(VER)-py3-none-any.whl
DIST_TAR=dist/$(NAME)-$(VER).tar.gz
DIST_ZIP=dist/$(NAME)-$(VER).zip
DIST_DEB=dist/$(NAME)-master_$(VER)$(DEB_SUFFIX)_all.deb \
dist/$(NAME)-slave_$(VER)$(DEB_SUFFIX)_all.deb \
dist/$(NAME)-docs_$(VER)$(DEB_SUFFIX)_all.deb \
dist/$(NAME)_$(VER)$(DEB_SUFFIX)_$(DEB_ARCH).build \
dist/$(NAME)_$(VER)$(DEB_SUFFIX)_$(DEB_ARCH).buildinfo \
dist/$(NAME)_$(VER)$(DEB_SUFFIX)_$(DEB_ARCH).changes
DIST_DSC=dist/$(NAME)_$(VER)$(DEB_SUFFIX).tar.xz \
dist/$(NAME)_$(VER)$(DEB_SUFFIX).dsc \
dist/$(NAME)_$(VER)$(DEB_SUFFIX)_source.build \
dist/$(NAME)_$(VER)$(DEB_SUFFIX)_source.buildinfo \
dist/$(NAME)_$(VER)$(DEB_SUFFIX)_source.changes
MAN_PAGES=man/pibootctl.1 \
man/pibootctl-help.1 \
man/pibootctl-status.1 \
man/pibootctl-get.1 \
man/pibootctl-set.1 \
man/pibootctl-save.1 \
man/pibootctl-load.1 \
man/pibootctl-diff.1 \
man/pibootctl-show.1 \
man/pibootctl-list.1 \
man/pibootctl-remove.1 \
man/pibootctl-rename.1
# Default target
all:
@echo "make install - Install on local system"
@echo "make develop - Install symlinks for development"
@echo "make test - Run tests"
@echo "make doc - Generate HTML and PDF documentation"
@echo "make source - Create source package"
@echo "make wheel - Generate a PyPI wheel package"
@echo "make zip - Generate a source zip package"
@echo "make tar - Generate a source tar package"
@echo "make deb - Generate Debian packages"
@echo "make dist - Generate all packages"
@echo "make clean - Get rid of all generated files"
@echo "make release - Create and tag a new release"
@echo "make upload - Upload the new release to repositories"
install: $(SUBDIRS)
$(PYTHON) $(PYFLAGS) setup.py install --root $(DEST_DIR)
doc: $(DOC_SOURCES)
$(MAKE) -C docs clean
$(MAKE) -C docs html
$(MAKE) -C docs epub
$(MAKE) -C docs latexpdf
$(MAKE) $(MAN_PAGES)
source: $(DIST_TAR) $(DIST_ZIP)
wheel: $(DIST_WHEEL)
zip: $(DIST_ZIP)
tar: $(DIST_TAR)
deb: $(DIST_DEB) $(DIST_DSC)
dist: $(DIST_WHEEL) $(DIST_DEB) $(DIST_DSC) $(DIST_TAR) $(DIST_ZIP)
develop: tags
@# These have to be done separately to avoid a cockup...
$(PIP) install -U setuptools
$(PIP) install -U pip
$(PIP) install tox
$(PIP) install -e .[doc,test]
test:
$(PYTHON) -m $(PYTEST)
clean:
-[ -d debian ] && dh_clean
rm -fr build/ dist/ man/ $(NAME).egg-info/ tags
for dir in $(SUBDIRS); do \
$(MAKE) -C $$dir clean; \
done
find $(CURDIR) -name "*.pyc" -delete
find $(CURDIR) -name "__pycache__" -delete
tags: $(PY_SOURCES)
ctags -R --exclude="build/*" --exclude="debian/*" --exclude="docs/*" --languages="Python"
lint: $(PY_SOURCES)
pylint piwheels
$(SUBDIRS):
$(MAKE) -C $@
$(MAN_PAGES): $(DOC_SOURCES)
$(PYTHON) $(PYFLAGS) setup.py build_sphinx -b man
mkdir -p man/
cp build/sphinx/man/*.[0-9] man/
$(DIST_TAR): $(PY_SOURCES) $(SUBDIRS)
$(PYTHON) $(PYFLAGS) setup.py sdist --formats gztar
$(DIST_ZIP): $(PY_SOURCES) $(SUBDIRS)
$(PYTHON) $(PYFLAGS) setup.py sdist --formats zip
$(DIST_WHEEL): $(PY_SOURCES) $(SUBDIRS)
$(PYTHON) $(PYFLAGS) setup.py bdist_wheel
$(DIST_DEB): $(PY_SOURCES) $(SUBDIRS) $(DEB_SOURCES) $(MAN_PAGES)
# build the binary package in the parent directory then rename it to
# project_version.orig.tar.gz
$(PYTHON) $(PYFLAGS) setup.py sdist --dist-dir=../
rename -f 's/$(NAME)-(.*)\.tar\.gz/$(NAME)_$$1\.orig\.tar\.gz/' ../*
debuild -b
mkdir -p dist/
for f in $(DIST_DEB); do cp ../$${f##*/} dist/; done
$(DIST_DSC): $(PY_SOURCES) $(SUBDIRS) $(DEB_SOURCES) $(MAN_PAGES)
# build the source package in the parent directory then rename it to
# project_version.orig.tar.gz
$(PYTHON) $(PYFLAGS) setup.py sdist --dist-dir=../
rename -f 's/$(NAME)-(.*)\.tar\.gz/$(NAME)_$$1\.orig\.tar\.gz/' ../*
debuild -S
mkdir -p dist/
for f in $(DIST_DSC); do cp ../$${f##*/} dist/; done
changelog: $(PY_SOURCES) $(DOC_SOURCES) $(DEB_SOURCES)
$(MAKE) clean
# ensure there are no current uncommitted changes
test -z "$(shell git status --porcelain)"
# update the debian changelog with new release information
dch --newversion $(VER)$(DEB_SUFFIX)
# commit the changes and add a new tag
git commit debian/changelog -m "Updated changelog for release $(VER)"
release-pi: $(PY_SOURCES) $(DOC_SOURCES) $(DIST_DEB) $(DIST_DSC)
git tag -s release-$(VER) -m "Release $(VER)"
git push --tags
git push
# build a source archive and upload to PyPI
$(TWINE) upload $(DIST_TAR) $(DIST_WHEEL)
# build the deb source archive and upload to Raspbian
dput raspberrypi dist/$(NAME)_$(VER)$(DEB_SUFFIX)_source.changes
dput raspberrypi dist/$(NAME)_$(VER)$(DEB_SUFFIX)_$(DEB_ARCH).changes
release-ubuntu: $(DIST_DEB) $(DIST_DSC)
# build the deb source archive and upload to the PPA
dput waveform-ppa dist/$(NAME)_$(VER)$(DEB_SUFFIX)_source.changes
.PHONY: all install develop test doc source wheel zip tar deb dist clean tags changelog release-pi release-ubuntu $(SUBDIRS)
pibootctl-0.5.2/README.rst 0000664 0000000 0000000 00000004110 13727517464 0015220 0 ustar 00root root 0000000 0000000 =========
pibootctl
=========
pibootctl is a utility for querying and manipulating the boot configuration of
a `Raspberry Pi`_. It is a relatively low level utility, and not intended to be
as friendly (or as widely applicable) as ``raspi-config``. It provides a
command line interface only, but does attempt to be useful as a basis for more
advanced interfaces (by providing input and output in human-readable,
shell-interpretable, JSON, or YAML formats) as well as being useful in its own
right.
The design philosophy of the utility is as follows:
#. Be safe: the utility manipulates the boot configuration and it's entirely
possible to create a non-booting system as a result. To that end, if no
backup of the current boot configuration exists, always take one before
manipulating it.
#. Be accessible: the Pi's boot configuration lives on a FAT partition and is a
simple ASCII text file. This means it can be read and manipulated by almost
any platform (Windows, Mac OS, etc). Any backups of the configuration should
be as accessible. To that end we use simple PKZIP files to store backups of
boot configurations (in their original format), and place them on the same
FAT partition as the configuration.
#. Be extensible: Almost all commands should default to human readable input
and output, but options should be provided for I/O in JSON, YAML, and a
shell-parseable format.
Links
=====
* The code is licensed under the `GPL v3`_ or above
* The `source code`_ can be obtained from GitHub, which also hosts the
`bug tracker`_
* The `documentation`_ (which includes installation and quick start examples)
can be read on ReadTheDocs
* Packages can be `downloaded`_ from PyPI, although reading the installation
instructions will probably be more useful
.. _Raspberry Pi: https://raspberrypi.org/
.. _GPL v3: https://www.gnu.org/licenses/gpl-3.0.html
.. _source code: https://github.com/waveform80/pibootctl
.. _bug tracker: https://github.com/waveform80/pibootctl/issues
.. _documentation: https://pibootctl.readthedocs.io/
.. _downloaded: https://pypi.org/project/pibootctl
pibootctl-0.5.2/copyrights 0000775 0000000 0000000 00000021736 13727517464 0015667 0 ustar 00root root 0000000 0000000 #!/usr/bin/env python
"""
This is a small utility script I originally whipped up for dealing with
re-writing the copyright headers in GPIO-Zero which had so many myriad
contributors it was becoming a pain to keep the headers accurate.
Usage is simple: just run ./copyrights in a clone of the repo after all PRs
have been merged and just before you're about to do a release. It should (if
it's working properly!) rewrite the copyright headers in all the files.
If you want to change its operation, the crucial bits are get_license() which
dictates what legalese gets written at the top, and update_copyright() which
does the actual re-writing (and which can be adapted to insert, e.g. a
corporate copyright holder before/after all individual contributors).
Everything else gets derived from the git history, so as long as this is
reasonable the output should be too.
Obviously, you should check the "git diff" is vaguely sane before committing
it!
"""
import io
import re
import sys
from collections import namedtuple
from operator import attrgetter
from itertools import groupby, tee
from datetime import datetime
from subprocess import Popen, PIPE, DEVNULL
from pathlib import Path
from fnmatch import fnmatch
from functools import lru_cache
Contribution = namedtuple('Contribution', ('author', 'email', 'year', 'filename'))
class Copyright(namedtuple('Copyright', ('author', 'email', 'years'))):
def __str__(self):
if self.email:
name = '{self.author} <{self.email}>'.format(self=self)
else:
name = self.author
return 'Copyright (c) {years} {name}'.format(
years=int_ranges(self.years), name=name)
def main():
includes = {
'**/*.py',
'**/*.rst',
}
excludes = {
'docs/examples/*.py',
'docs/license.rst',
}
prefixes = {
'.py': '#',
'.rst': '..',
}
if len(sys.argv) > 1:
includes = set(sys.argv[1:])
contributions = get_contributions(includes, excludes)
for filename, copyrights in contributions.items():
filename = Path(filename)
update_copyright(filename, copyrights, prefixes[filename.suffix])
def get_contributions(include, exclude):
sorted_blame = sorted(
get_blame(include, exclude),
key=lambda c: (c.filename, c.author, c.email)
)
blame_by_file = {
filename: list(file_contributions)
for filename, file_contributions in groupby(
sorted_blame, key=attrgetter('filename')
)
}
return {
filename: {
Copyright(author, email, frozenset(y.year for y in years))
for (author, email), years in groupby(
file_contributors, key=lambda c: (c.author, c.email)
)
}
for filename, file_contributors in blame_by_file.items()
}
def get_blame(include, exclude):
for filename in get_source_files(include, exclude):
blame = Popen(
['git', 'blame', '--line-porcelain', 'HEAD', '--', filename],
stdout=PIPE,
stderr=PIPE,
universal_newlines=True
)
author = email = year = None
for line in blame.stdout:
if line.startswith('author '):
author = line.split(' ', 1)[1].rstrip()
elif line.startswith('author-mail '):
email = line.split(' ', 1)[1].rstrip().lstrip('<').rstrip('>')
elif line.startswith('author-time '):
# Forget the timezone; we only want the year anyway
year = datetime.fromtimestamp(int(line.split(' ', 1)[1].rstrip())).year
elif line.startswith('filename '):
yield Contribution(
author=author, email=email, year=year, filename=filename)
author = email = year = None
blame.wait()
assert blame.returncode == 0
def get_source_files(include, exclude):
ls_tree = Popen(
['git', 'ls-tree', '-r', '--name-only', 'HEAD'],
stdout=PIPE,
stderr=DEVNULL,
universal_newlines=True
)
if not include:
include = {'*'}
for filename in ls_tree.stdout:
filename = filename.strip()
if any(fnmatch(filename, pattern) for pattern in exclude):
continue
if any(fnmatch(filename, pattern) for pattern in include):
yield filename
ls_tree.wait()
assert ls_tree.returncode == 0
insertion_point = object()
def parse_source_file(filename, prefix):
license = get_license()
license_start = license[0]
license_end = license[-1]
with filename.open('r') as source:
state = 'preamble'
for linenum, line in enumerate(source, start=1):
if state == 'preamble':
if linenum == 1 and line.startswith('#!'):
yield line
elif linenum < 10 and 'set fileencoding' in line:
yield line
elif line.rstrip() == prefix:
pass # skip blank comment lines
elif line.startswith(prefix + ' Copyright (c)'):
pass # skip existing copyright lines
elif line.startswith(prefix + ' ' + license_start):
state = 'license' # skip existing license lines
else:
yield insertion_point
state = 'blank'
elif state == 'license':
if line.startswith(prefix + ' ' + license_end):
yield insertion_point
state = 'blank'
continue
if state == 'blank':
# Ensure there's a blank line between license and start of the
# source body
if line.strip():
yield '\n'
yield line
state = 'body'
elif state == 'body':
yield line
def update_copyright(filename, copyrights, prefix):
print('Re-writing {filename}...'.format(filename=filename))
license = get_license()
copyrights = [
Copyright('Canonical Ltd.', '', {datetime.now().year}),
] + sorted(
copyrights, reverse=True, key=lambda c:
(c.years[::-1] if isinstance(c.years, tuple) else (c.years,), c.author)
)
content = []
for line in parse_source_file(filename, prefix):
if line is insertion_point:
if len(content) > 0:
content.append(prefix + '\n')
for copyright in copyrights:
content.append(prefix + ' ' + str(copyright) + '\n')
content.append(prefix + '\n')
content.extend(
(prefix + ' ' + l).strip() + '\n'
for l in license
)
else:
content.append(line)
# Yes, if I was doing this "properly" I'd write to a temporary file and
# rename it over the target. However, I'm assuming you're running this
# under a git clone ... after all, you are ... aren't you?
with filename.open('w') as target:
for line in content:
target.write(line)
@lru_cache()
def get_license():
return """\
This file is part of pibootctl.
pibootctl is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
pibootctl is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with pibootctl. If not, see .
""".splitlines()
def pairwise(iterable):
"""
Taken from the recipe in the documentation for :mod:`itertools`.
"""
a, b = tee(iterable)
next(b, None)
return zip(a, b)
def int_ranges(values):
"""
Given a set of integer *values*, returns a compressed string representation
of all values in the set. For example:
>>> int_ranges({1, 2})
'1, 2'
>>> int_ranges({1, 2, 3})
'1-3'
>>> int_ranges({1, 2, 3, 4, 8})
'1-4, 8'
>>> int_ranges({1, 2, 3, 4, 8, 9})
'1-4, 8-9'
"""
if len(values) == 0:
return ''
elif len(values) == 1:
return '{0}'.format(*values)
elif len(values) == 2:
return '{0}, {1}'.format(*values)
else:
ranges = []
start = None
for i, j in pairwise(sorted(values)):
if start is None:
start = i
if j > i + 1:
ranges.append((start, i))
start = j
if j == i + 1:
ranges.append((start, j))
else:
ranges.append((j, j))
return ', '.join(
('{start}-{finish}' if finish > start else '{start}').format(
start=start, finish=finish)
for start, finish in ranges
)
if __name__ == '__main__':
main()
pibootctl-0.5.2/design.txt 0000664 0000000 0000000 00000006303 13727517464 0015551 0 ustar 00root root 0000000 0000000 pibootctl set ...
pibootctl get
pibootctl get --json
pibootctl set i2c=on spi=on
pibootctl get i2c
Example output:
$ pibootctl get
Setting Value Config
================= ===== ======
x audio.enabled off dtparam=audio
bt.enabled off dtoverlay?
x i2c.enabled on dtparam=i2c_arm
x i2c.baud 100000 dtparam=i2c_arm_baudrate
x i2s.enabled off dtparam=i2s
w1.enabled off dtoverlay=w1-gpio
w1.gpio 4 dtparam=gpiopin=4
x spi.enabled on dtparam=spi
uart.enabled on enable_uart
camera.enabled off start_x/start
x video.cec.enabled on hdmi_ignore_cec
x video.cec.init on hdmi_ignore_cec_init
x video.cec.osd_name "Raspberry Pi" cec_osd_name
x video.hdmi.force_3d off hdmi_force_edid_3d
x video.hdmi.blanking off hdmi_blanking
video.hdmi.timings auto hdmi_timings
video.hdmi.pixel_encoding 0 hdmi_pixel_encoding
video.hdmi.boost 5 config_hdmi_boost
video.hdmi0.flip none display_hdmi_rotate
video.hdmi0.force_mode off hdmi_force_mode
video.hdmi0.group auto hdmi_group
video.hdmi0.mode auto hdmi_mode
video.hdmi0.rotate 0 display_hdmi_rotate
video.hdmi1.flip off display_hdmi_rotate:1
video.hdmi1.force_mode off hdmi_force_mode:1
video.hdmi1.group auto hdmi_group:1
video.hdmi1.mode auto hdmi_mode:1
video.hdmi1.rotate 0 display_hdmi_rotate:1
video.dpi.enabled off enable_dpi_lcd
video.dpi.group auto dpi_group
video.dpi.mode auto dpi_mode
video.dpi.timings auto dpi_timings
video.lcd.default on display_default_lcd
video.lcd.flip off display_lcd_rotate
video.lcd.framerate 60 lcd_framerate
video.lcd.ignore off ignore_lcd
video.lcd.rotate 0 lcd_rotate / display_lcd_rotate
video.lcd.touchscreen on disable_touchscreen
video.mem auto gpu_mem
x video.overscan.enabled off disable_overscan
x video.overscan.left 0 overscan_left
x video.overscan.right 0 overscan_left
x video.overscan.top 0 overscan_top
x video.overscan.bottom 0 overscan_bottom
x watchdog.enabled off dtparam=watchdog
pibootctl-0.5.2/docs/ 0000775 0000000 0000000 00000000000 13727517464 0014465 5 ustar 00root root 0000000 0000000 pibootctl-0.5.2/docs/Makefile 0000664 0000000 0000000 00000017036 13727517464 0016134 0 ustar 00root root 0000000 0000000 # Makefile for Sphinx documentation
#
# You can set these variables from the command line.
SPHINXOPTS =
SPHINXBUILD = sphinx-build
PAPER =
BUILDDIR = ../build
DOT_DIAGRAMS := $(wildcard images/*.dot)
MSC_DIAGRAMS := $(wildcard images/*.mscgen)
GPI_DIAGRAMS := $(wildcard images/*.gpi)
SVG_IMAGES := $(wildcard images/*.svg) $(DOT_DIAGRAMS:%.dot=%.svg) $(MSC_DIAGRAMS:%.mscgen=%.svg)
PNG_IMAGES := $(wildcard images/*.png) $(GPI_DIAGRAMS:%.gpi=%.png) $(SVG_IMAGES:%.svg=%.png)
PDF_IMAGES := $(SVG_IMAGES:%.svg=%.pdf) $(GPI_DIAGRAMS:%.gpi=%.pdf) $(DOT_DIAGRAMS:%.dot=%.pdf) $(MSC_DIAGRAMS:%.mscgen=%.pdf)
# User-friendly check for sphinx-build
ifeq ($(shell which $(SPHINXBUILD) >/dev/null 2>&1; echo $$?), 1)
$(error The '$(SPHINXBUILD)' command was not found. Make sure you have Sphinx installed, then set the SPHINXBUILD environment variable to point to the full path of the '$(SPHINXBUILD)' executable. Alternatively you can add the directory with the executable to your PATH. If you don't have Sphinx installed, grab it from http://sphinx-doc.org/)
endif
# Internal variables.
PAPEROPT_a4 = -D latex_paper_size=a4
PAPEROPT_letter = -D latex_paper_size=letter
ALLSPHINXOPTS = -d $(BUILDDIR)/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) .
# the i18n builder cannot share the environment and doctrees with the others
I18NSPHINXOPTS = $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) .
help:
@echo "Please use \`make ' where is one of"
@echo " html to make standalone HTML files"
@echo " dirhtml to make HTML files named index.html in directories"
@echo " singlehtml to make a single large HTML file"
@echo " pickle to make pickle files"
@echo " json to make JSON files"
@echo " htmlhelp to make HTML files and a HTML help project"
@echo " qthelp to make HTML files and a qthelp project"
@echo " devhelp to make HTML files and a Devhelp project"
@echo " epub to make an epub"
@echo " latex to make LaTeX files, you can set PAPER=a4 or PAPER=letter"
@echo " latexpdf to make LaTeX files and run them through pdflatex"
@echo " latexpdfja to make LaTeX files and run them through platex/dvipdfmx"
@echo " text to make text files"
@echo " man to make manual pages"
@echo " texinfo to make Texinfo files"
@echo " info to make Texinfo files and run them through makeinfo"
@echo " gettext to make PO message catalogs"
@echo " changes to make an overview of all changed/added/deprecated items"
@echo " xml to make Docutils-native XML files"
@echo " pseudoxml to make pseudoxml-XML files for display purposes"
@echo " linkcheck to check all external links for integrity"
@echo " doctest to run all doctests embedded in the documentation (if enabled)"
clean:
rm -rf $(BUILDDIR)/*
html: $(SVG_IMAGES) $(PNG_IMAGES)
$(SPHINXBUILD) -b html $(ALLSPHINXOPTS) $(BUILDDIR)/html
@echo
@echo "Build finished. The HTML pages are in $(BUILDDIR)/html."
dirhtml: $(SVG_IMAGES) $(PNG_IMAGES)
$(SPHINXBUILD) -b dirhtml $(ALLSPHINXOPTS) $(BUILDDIR)/dirhtml
@echo
@echo "Build finished. The HTML pages are in $(BUILDDIR)/dirhtml."
singlehtml: $(SVG_IMAGES) $(PNG_IMAGES)
$(SPHINXBUILD) -b singlehtml $(ALLSPHINXOPTS) $(BUILDDIR)/singlehtml
@echo
@echo "Build finished. The HTML page is in $(BUILDDIR)/singlehtml."
pickle:
$(SPHINXBUILD) -b pickle $(ALLSPHINXOPTS) $(BUILDDIR)/pickle
@echo
@echo "Build finished; now you can process the pickle files."
json:
$(SPHINXBUILD) -b json $(ALLSPHINXOPTS) $(BUILDDIR)/json
@echo
@echo "Build finished; now you can process the JSON files."
htmlhelp:
$(SPHINXBUILD) -b htmlhelp $(ALLSPHINXOPTS) $(BUILDDIR)/htmlhelp
@echo
@echo "Build finished; now you can run HTML Help Workshop with the" \
".hhp project file in $(BUILDDIR)/htmlhelp."
qthelp:
$(SPHINXBUILD) -b qthelp $(ALLSPHINXOPTS) $(BUILDDIR)/qthelp
@echo
@echo "Build finished; now you can run "qcollectiongenerator" with the" \
".qhcp project file in $(BUILDDIR)/qthelp, like this:"
@echo "# qcollectiongenerator $(BUILDDIR)/qthelp/pibootctl.qhcp"
@echo "To view the help file:"
@echo "# assistant -collectionFile $(BUILDDIR)/qthelp/pibootctl.qhc"
devhelp:
$(SPHINXBUILD) -b devhelp $(ALLSPHINXOPTS) $(BUILDDIR)/devhelp
@echo
@echo "Build finished."
@echo "To view the help file:"
@echo "# mkdir -p $$HOME/.local/share/devhelp/pibootctl"
@echo "# ln -s $(BUILDDIR)/devhelp $$HOME/.local/share/devhelp/pibootctl"
@echo "# devhelp"
epub:
$(SPHINXBUILD) -b epub $(ALLSPHINXOPTS) $(BUILDDIR)/epub
@echo
@echo "Build finished. The epub file is in $(BUILDDIR)/epub."
latex: $(PDF_IMAGES)
$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
@echo
@echo "Build finished; the LaTeX files are in $(BUILDDIR)/latex."
@echo "Run \`make' in that directory to run these through (pdf)latex" \
"(use \`make latexpdf' here to do that automatically)."
latexpdf: $(PDF_IMAGES)
$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
@echo "Running LaTeX files through pdflatex..."
$(MAKE) -C $(BUILDDIR)/latex all-pdf
@echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
latexpdfja: $(PDF_IMAGES)
$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
@echo "Running LaTeX files through platex and dvipdfmx..."
$(MAKE) -C $(BUILDDIR)/latex all-pdf-ja
@echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
text:
$(SPHINXBUILD) -b text $(ALLSPHINXOPTS) $(BUILDDIR)/text
@echo
@echo "Build finished. The text files are in $(BUILDDIR)/text."
man:
$(SPHINXBUILD) -b man $(ALLSPHINXOPTS) $(BUILDDIR)/man
@echo
@echo "Build finished. The manual pages are in $(BUILDDIR)/man."
texinfo:
$(SPHINXBUILD) -b texinfo $(ALLSPHINXOPTS) $(BUILDDIR)/texinfo
@echo
@echo "Build finished. The Texinfo files are in $(BUILDDIR)/texinfo."
@echo "Run \`make' in that directory to run these through makeinfo" \
"(use \`make info' here to do that automatically)."
info:
$(SPHINXBUILD) -b texinfo $(ALLSPHINXOPTS) $(BUILDDIR)/texinfo
@echo "Running Texinfo files through makeinfo..."
make -C $(BUILDDIR)/texinfo info
@echo "makeinfo finished; the Info files are in $(BUILDDIR)/texinfo."
gettext:
$(SPHINXBUILD) -b gettext $(I18NSPHINXOPTS) $(BUILDDIR)/locale
@echo
@echo "Build finished. The message catalogs are in $(BUILDDIR)/locale."
changes:
$(SPHINXBUILD) -b changes $(ALLSPHINXOPTS) $(BUILDDIR)/changes
@echo
@echo "The overview file is in $(BUILDDIR)/changes."
linkcheck:
$(SPHINXBUILD) -b linkcheck $(ALLSPHINXOPTS) $(BUILDDIR)/linkcheck
@echo
@echo "Link check complete; look for any errors in the above output " \
"or in $(BUILDDIR)/linkcheck/output.txt."
doctest:
$(SPHINXBUILD) -b doctest $(ALLSPHINXOPTS) $(BUILDDIR)/doctest
@echo "Testing of doctests in the sources finished, look at the " \
"results in $(BUILDDIR)/doctest/output.txt."
xml:
$(SPHINXBUILD) -b xml $(ALLSPHINXOPTS) $(BUILDDIR)/xml
@echo
@echo "Build finished. The XML files are in $(BUILDDIR)/xml."
pseudoxml:
$(SPHINXBUILD) -b pseudoxml $(ALLSPHINXOPTS) $(BUILDDIR)/pseudoxml
@echo
@echo "Build finished. The pseudo-XML files are in $(BUILDDIR)/pseudoxml."
%.svg: %.mscgen
mscgen -T svg -o $@ $<
%.svg: %.dot
dot -T svg -o $@ $<
%.png: %.gpi
gnuplot -e "set term pngcairo transparent size 400,400" $< > $@
%.png: %.svg
inkscape -e $@ $<
%.pdf: %.svg
inkscape -A $@ $<
%.pdf: %.gpi
gnuplot -e "set term pdfcairo size 5cm,5cm" $< > $@
%.pdf: %.mscgen
mscgen -T eps -o - $< | ps2pdf -dEPSCrop - $@
.PHONY: help clean html dirhtml singlehtml pickle json htmlhelp qthelp devhelp epub latex latexpdf text man changes linkcheck doctest gettext
pibootctl-0.5.2/docs/_static/ 0000775 0000000 0000000 00000000000 13727517464 0016113 5 ustar 00root root 0000000 0000000 pibootctl-0.5.2/docs/_static/style_override.css 0000664 0000000 0000000 00000000516 13727517464 0021666 0 ustar 00root root 0000000 0000000 /* override table width restrictions */
.wy-table-responsive table td, .wy-table-responsive table th {
/* !important prevents the common CSS stylesheets from
overriding this as on RTD they are loaded after this stylesheet */
white-space: normal !important;
}
.wy-table-responsive {
overflow: visible !important;
}
pibootctl-0.5.2/docs/api.rst 0000664 0000000 0000000 00000002621 13727517464 0015771 0 ustar 00root root 0000000 0000000 .. Copyright (c) 2020 Canonical Ltd.
.. Copyright (c) 2020 Dave Jones
..
.. This file is part of pibootctl.
..
.. pibootctl is free software: you can redistribute it and/or modify
.. it under the terms of the GNU General Public License as published by
.. the Free Software Foundation, either version 3 of the License, or
.. (at your option) any later version.
..
.. pibootctl is distributed in the hope that it will be useful,
.. but WITHOUT ANY WARRANTY; without even the implied warranty of
.. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
.. GNU General Public License for more details.
..
.. You should have received a copy of the GNU General Public License
.. along with pibootctl. If not, see .
===
API
===
:doc:`pibootctl ` can be used both as a standalone application, and as
an API within Python. The primary class of interest when using :doc:`pibootctl
` as an API is :class:`~pibootctl.store.Store` in the
:mod:`pibootctl.store` module, but :mod:`pibootctl.main` is useful for
providing an instance of this, constructed from the pibootctl configuration.
The API is split into several modules, documented in the following sections:
.. toctree::
:maxdepth: 1
api_exc
api_files
api_formatter
api_info
api_main
api_parser
api_setting
api_settings
api_store
api_term
api_userstr
pibootctl-0.5.2/docs/api_exc.rst 0000664 0000000 0000000 00000001516 13727517464 0016632 0 ustar 00root root 0000000 0000000 .. Copyright (c) 2020 Canonical Ltd.
.. Copyright (c) 2020 Dave Jones
..
.. This file is part of pibootctl.
..
.. pibootctl is free software: you can redistribute it and/or modify
.. it under the terms of the GNU General Public License as published by
.. the Free Software Foundation, either version 3 of the License, or
.. (at your option) any later version.
..
.. pibootctl is distributed in the hope that it will be useful,
.. but WITHOUT ANY WARRANTY; without even the implied warranty of
.. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
.. GNU General Public License for more details.
..
.. You should have received a copy of the GNU General Public License
.. along with pibootctl. If not, see .
=============
pibootctl.exc
=============
.. automodule:: pibootctl.exc
pibootctl-0.5.2/docs/api_files.rst 0000664 0000000 0000000 00000001526 13727517464 0017156 0 ustar 00root root 0000000 0000000 .. Copyright (c) 2020 Canonical Ltd.
.. Copyright (c) 2020 Dave Jones
..
.. This file is part of pibootctl.
..
.. pibootctl is free software: you can redistribute it and/or modify
.. it under the terms of the GNU General Public License as published by
.. the Free Software Foundation, either version 3 of the License, or
.. (at your option) any later version.
..
.. pibootctl is distributed in the hope that it will be useful,
.. but WITHOUT ANY WARRANTY; without even the implied warranty of
.. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
.. GNU General Public License for more details.
..
.. You should have received a copy of the GNU General Public License
.. along with pibootctl. If not, see .
===============
pibootctl.files
===============
.. automodule:: pibootctl.files
pibootctl-0.5.2/docs/api_formatter.rst 0000664 0000000 0000000 00000001546 13727517464 0020061 0 ustar 00root root 0000000 0000000 .. Copyright (c) 2020 Canonical Ltd.
.. Copyright (c) 2020 Dave Jones
..
.. This file is part of pibootctl.
..
.. pibootctl is free software: you can redistribute it and/or modify
.. it under the terms of the GNU General Public License as published by
.. the Free Software Foundation, either version 3 of the License, or
.. (at your option) any later version.
..
.. pibootctl is distributed in the hope that it will be useful,
.. but WITHOUT ANY WARRANTY; without even the implied warranty of
.. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
.. GNU General Public License for more details.
..
.. You should have received a copy of the GNU General Public License
.. along with pibootctl. If not, see .
===================
pibootctl.formatter
===================
.. automodule:: pibootctl.formatter
pibootctl-0.5.2/docs/api_info.rst 0000664 0000000 0000000 00000001522 13727517464 0017003 0 ustar 00root root 0000000 0000000 .. Copyright (c) 2020 Canonical Ltd.
.. Copyright (c) 2020 Dave Jones
..
.. This file is part of pibootctl.
..
.. pibootctl is free software: you can redistribute it and/or modify
.. it under the terms of the GNU General Public License as published by
.. the Free Software Foundation, either version 3 of the License, or
.. (at your option) any later version.
..
.. pibootctl is distributed in the hope that it will be useful,
.. but WITHOUT ANY WARRANTY; without even the implied warranty of
.. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
.. GNU General Public License for more details.
..
.. You should have received a copy of the GNU General Public License
.. along with pibootctl. If not, see .
==============
pibootctl.info
==============
.. automodule:: pibootctl.info
pibootctl-0.5.2/docs/api_main.rst 0000664 0000000 0000000 00000001522 13727517464 0016774 0 ustar 00root root 0000000 0000000 .. Copyright (c) 2020 Canonical Ltd.
.. Copyright (c) 2020 Dave Jones
..
.. This file is part of pibootctl.
..
.. pibootctl is free software: you can redistribute it and/or modify
.. it under the terms of the GNU General Public License as published by
.. the Free Software Foundation, either version 3 of the License, or
.. (at your option) any later version.
..
.. pibootctl is distributed in the hope that it will be useful,
.. but WITHOUT ANY WARRANTY; without even the implied warranty of
.. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
.. GNU General Public License for more details.
..
.. You should have received a copy of the GNU General Public License
.. along with pibootctl. If not, see .
==============
pibootctl.main
==============
.. automodule:: pibootctl.main
pibootctl-0.5.2/docs/api_parser.rst 0000664 0000000 0000000 00000001532 13727517464 0017345 0 ustar 00root root 0000000 0000000 .. Copyright (c) 2020 Canonical Ltd.
.. Copyright (c) 2020 Dave Jones
..
.. This file is part of pibootctl.
..
.. pibootctl is free software: you can redistribute it and/or modify
.. it under the terms of the GNU General Public License as published by
.. the Free Software Foundation, either version 3 of the License, or
.. (at your option) any later version.
..
.. pibootctl is distributed in the hope that it will be useful,
.. but WITHOUT ANY WARRANTY; without even the implied warranty of
.. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
.. GNU General Public License for more details.
..
.. You should have received a copy of the GNU General Public License
.. along with pibootctl. If not, see .
================
pibootctl.parser
================
.. automodule:: pibootctl.parser
pibootctl-0.5.2/docs/api_setting.rst 0000664 0000000 0000000 00000001536 13727517464 0017532 0 ustar 00root root 0000000 0000000 .. Copyright (c) 2020 Canonical Ltd.
.. Copyright (c) 2020 Dave Jones
..
.. This file is part of pibootctl.
..
.. pibootctl is free software: you can redistribute it and/or modify
.. it under the terms of the GNU General Public License as published by
.. the Free Software Foundation, either version 3 of the License, or
.. (at your option) any later version.
..
.. pibootctl is distributed in the hope that it will be useful,
.. but WITHOUT ANY WARRANTY; without even the implied warranty of
.. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
.. GNU General Public License for more details.
..
.. You should have received a copy of the GNU General Public License
.. along with pibootctl. If not, see .
=================
pibootctl.setting
=================
.. automodule:: pibootctl.setting
pibootctl-0.5.2/docs/api_settings.rst 0000664 0000000 0000000 00000001542 13727517464 0017712 0 ustar 00root root 0000000 0000000 .. Copyright (c) 2020 Canonical Ltd.
.. Copyright (c) 2020 Dave Jones
..
.. This file is part of pibootctl.
..
.. pibootctl is free software: you can redistribute it and/or modify
.. it under the terms of the GNU General Public License as published by
.. the Free Software Foundation, either version 3 of the License, or
.. (at your option) any later version.
..
.. pibootctl is distributed in the hope that it will be useful,
.. but WITHOUT ANY WARRANTY; without even the implied warranty of
.. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
.. GNU General Public License for more details.
..
.. You should have received a copy of the GNU General Public License
.. along with pibootctl. If not, see .
==================
pibootctl.settings
==================
.. automodule:: pibootctl.settings
pibootctl-0.5.2/docs/api_store.rst 0000664 0000000 0000000 00000001526 13727517464 0017210 0 ustar 00root root 0000000 0000000 .. Copyright (c) 2020 Canonical Ltd.
.. Copyright (c) 2020 Dave Jones
..
.. This file is part of pibootctl.
..
.. pibootctl is free software: you can redistribute it and/or modify
.. it under the terms of the GNU General Public License as published by
.. the Free Software Foundation, either version 3 of the License, or
.. (at your option) any later version.
..
.. pibootctl is distributed in the hope that it will be useful,
.. but WITHOUT ANY WARRANTY; without even the implied warranty of
.. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
.. GNU General Public License for more details.
..
.. You should have received a copy of the GNU General Public License
.. along with pibootctl. If not, see .
===============
pibootctl.store
===============
.. automodule:: pibootctl.store
pibootctl-0.5.2/docs/api_term.rst 0000664 0000000 0000000 00000001522 13727517464 0017017 0 ustar 00root root 0000000 0000000 .. Copyright (c) 2020 Canonical Ltd.
.. Copyright (c) 2020 Dave Jones
..
.. This file is part of pibootctl.
..
.. pibootctl is free software: you can redistribute it and/or modify
.. it under the terms of the GNU General Public License as published by
.. the Free Software Foundation, either version 3 of the License, or
.. (at your option) any later version.
..
.. pibootctl is distributed in the hope that it will be useful,
.. but WITHOUT ANY WARRANTY; without even the implied warranty of
.. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
.. GNU General Public License for more details.
..
.. You should have received a copy of the GNU General Public License
.. along with pibootctl. If not, see .
==============
pibootctl.term
==============
.. automodule:: pibootctl.term
pibootctl-0.5.2/docs/api_userstr.rst 0000664 0000000 0000000 00000001536 13727517464 0017564 0 ustar 00root root 0000000 0000000 .. Copyright (c) 2020 Canonical Ltd.
.. Copyright (c) 2020 Dave Jones
..
.. This file is part of pibootctl.
..
.. pibootctl is free software: you can redistribute it and/or modify
.. it under the terms of the GNU General Public License as published by
.. the Free Software Foundation, either version 3 of the License, or
.. (at your option) any later version.
..
.. pibootctl is distributed in the hope that it will be useful,
.. but WITHOUT ANY WARRANTY; without even the implied warranty of
.. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
.. GNU General Public License for more details.
..
.. You should have received a copy of the GNU General Public License
.. along with pibootctl. If not, see .
=================
pibootctl.userstr
=================
.. automodule:: pibootctl.userstr
pibootctl-0.5.2/docs/changelog.rst 0000664 0000000 0000000 00000005121 13727517464 0017145 0 ustar 00root root 0000000 0000000 .. Copyright (c) 2020 Canonical Ltd.
.. Copyright (c) 2020 Dave Jones
..
.. This file is part of pibootctl.
..
.. pibootctl is free software: you can redistribute it and/or modify
.. it under the terms of the GNU General Public License as published by
.. the Free Software Foundation, either version 3 of the License, or
.. (at your option) any later version.
..
.. pibootctl is distributed in the hope that it will be useful,
.. but WITHOUT ANY WARRANTY; without even the implied warranty of
.. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
.. GNU General Public License for more details.
..
.. You should have received a copy of the GNU General Public License
.. along with pibootctl. If not, see .
=========
Changelog
=========
.. currentmodule:: pibootctl
Release 0.5.2 (2020-09-14)
==========================
* Fix handling of initramfs (ramfsaddr=0 doesn't work)
Release 0.5.1 (2020-09-09)
==========================
* Handle future model numbers elegantly
* Rewrote the configuration setting code to always target :file:`config.txt`
as several settings don't work in included files (e.g. ``start_x``).
* Added ``comment_lines`` configuration option to permit commenting out lines
instead of deleting them
* Enhanced the configuration setting code to search for and uncomment existing
lines in preference to writing new ones
* Added ``--this-model`` and ``--this-serial`` options to permit adding
settings in new conditional sections
Release 0.4 (2020-03-31)
========================
* Handle unrecognized commands correctly in the "help" command
* Implemented loading settings with the ``--shell`` style
* Improved help output for reference lists
* Fixed all legal stuff (added copyright headers where required, re-licensed to
GPL 3+)
Release 0.3 (2020-03-27)
========================
* Added full bash completion support
Release 0.2 (2020-03-26)
========================
* The application now reports which lines overrode a setting when the
"ineffective setting" error occurs
* Added the max_framebuffers setting, and detection for the vc4-\*-v3d overlays
* Fixed restoring the default configuration in which config.txt doesn't exist
(i.e. when config.txt should be deleted or blanked; the prior version simply
left the old config.txt in place incorrectly)
* Various documentation fixes
Release 0.1.1 (2020-03-13)
==========================
* Fixed broken build on Bionic
Release 0.1 (2020-03-13)
========================
* Initial release.
* Please note that as this is a pre-v1 release, API stability is not yet
guaranteed.
pibootctl-0.5.2/docs/commands.rst 0000664 0000000 0000000 00000003165 13727517464 0017025 0 ustar 00root root 0000000 0000000 .. Copyright (c) 2020 Canonical Ltd.
.. Copyright (c) 2020 Dave Jones
..
.. This file is part of pibootctl.
..
.. pibootctl is free software: you can redistribute it and/or modify
.. it under the terms of the GNU General Public License as published by
.. the Free Software Foundation, either version 3 of the License, or
.. (at your option) any later version.
..
.. pibootctl is distributed in the hope that it will be useful,
.. but WITHOUT ANY WARRANTY; without even the implied warranty of
.. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
.. GNU General Public License for more details.
..
.. You should have received a copy of the GNU General Public License
.. along with pibootctl. If not, see .
:doc:`diff`
Display the differences between the specified boot configuration and the
current one, or another specified configuration.
:doc:`get`
Retrieve the value of specified setting(s).
:doc:`help`
The default command, which describes the specified command or configuration
setting.
:doc:`list`
List the stored boot configurations.
:doc:`load`
Restore the named boot configuration to be used at the next boot.
:doc:`remove`
Delete the specified boot configuration.
:doc:`rename`
Rename the specified boot configuration.
:doc:`save`
Save the current boot configuration to the specified name.
:doc:`set`
Modify or reset the specified configuration setting(s).
:doc:`show`
Show the specified stored configuration.
:doc:`status`
Output the current boot configuration; by default this only prints modified
settings.
pibootctl-0.5.2/docs/conf.py 0000664 0000000 0000000 00000014034 13727517464 0015766 0 ustar 00root root 0000000 0000000 #!/usr/bin/env python3
#
# Copyright (c) 2020 Canonical Ltd.
# Copyright (c) 2020 Dave Jones
#
# This file is part of pibootctl.
#
# pibootctl is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# pibootctl is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with pibootctl. If not, see .
# vim: set et sw=4 sts=4 fileencoding=utf-8:
import sys
import os
import pkginfo
from datetime import datetime
on_rtd = os.environ.get('READTHEDOCS', None) == 'True'
info = pkginfo.Installed('pibootctl')
if info.version is None:
# pkginfo prior to 1.5 seems broken (succeeds in construction, but doesn't
# contain any info); fall back to a horrific configparser hack...
import configparser
cfg = configparser.ConfigParser()
class Attr(dict):
__getattr__ = dict.__getitem__
assert cfg.read(('../setup.cfg',))
info = Attr(**cfg['metadata'])
if info.version is None:
raise RuntimeError('Failed to load distro info')
# -- General configuration ------------------------------------------------
extensions = ['sphinx.ext.autodoc', 'sphinx.ext.viewcode', 'sphinx.ext.intersphinx']
if on_rtd:
needs_sphinx = '1.4.0'
extensions.append('sphinx.ext.imgmath')
imgmath_image_format = 'svg'
tags.add('rtd')
else:
extensions.append('sphinx.ext.mathjax')
mathjax_path = '/usr/share/javascript/mathjax/MathJax.js?config=TeX-AMS_HTML'
templates_path = ['_templates']
source_suffix = '.rst'
#source_encoding = 'utf-8-sig'
master_doc = 'index'
project = info.name
copyright = '2019-%s %s' % (datetime.now().year, info.author)
version = info.version
#release = None
#language = None
#today_fmt = '%B %d, %Y'
exclude_patterns = ['_build']
highlight_language = 'python3'
#default_role = None
#add_function_parentheses = True
#add_module_names = True
#show_authors = False
pygments_style = 'sphinx'
#modindex_common_prefix = []
#keep_warnings = False
# -- Autodoc configuration ------------------------------------------------
autodoc_member_order = 'groupwise'
# -- Intersphinx configuration --------------------------------------------
intersphinx_mapping = {
'python': ('https://docs.python.org/3.5', None),
}
intersphinx_cache_limit = 7
# -- Options for HTML output ----------------------------------------------
if on_rtd:
html_theme = 'sphinx_rtd_theme'
pygments_style = 'default'
#html_theme_options = {}
#html_sidebars = {}
else:
html_theme = 'default'
#html_theme_options = {}
#html_sidebars = {}
html_title = '%s %s Documentation' % (project, version)
#html_theme_path = []
#html_short_title = None
#html_logo = None
#html_favicon = None
html_static_path = ['_static']
#html_extra_path = []
#html_last_updated_fmt = '%b %d, %Y'
#html_use_smartypants = True
#html_additional_pages = {}
#html_domain_indices = True
#html_use_index = True
#html_split_index = False
#html_show_sourcelink = True
#html_show_sphinx = True
#html_show_copyright = True
#html_use_opensearch = ''
#html_file_suffix = None
htmlhelp_basename = '%sdoc' % info.name
# Hack to make wide tables work properly in RTD
# See https://github.com/snide/sphinx_rtd_theme/issues/117 for details
def setup(app):
app.add_stylesheet('style_override.css')
# -- Options for LaTeX output ---------------------------------------------
latex_engine = 'xelatex'
latex_elements = {
'papersize': 'a4paper',
'pointsize': '10pt',
'preamble': r'\def\thempfootnote{\arabic{mpfootnote}}', # workaround sphinx issue #2530
}
latex_documents = [
(
'index', # source start file
'%s.tex' % project, # target filename
'%s %s Documentation' % (project, version), # title
info.author, # author
'manual', # documentclass
True, # documents ref'd from toctree only
),
]
#latex_logo = None
#latex_use_parts = False
latex_show_pagerefs = True
latex_show_urls = 'footnote'
#latex_appendices = []
#latex_domain_indices = True
# -- Options for epub output ----------------------------------------------
epub_basename = project
#epub_theme = 'epub'
#epub_title = html_title
epub_author = info.author
epub_identifier = 'https://pibootctl.readthedocs.io/'
#epub_tocdepth = 3
epub_show_urls = 'no'
#epub_use_index = True
# -- Options for manual page output ---------------------------------------
man_pages = [
('pibootctl', 'pibootctl', 'pibootctl manual', [info.author], 1),
('help', 'pibootctl-help', 'pibootctl manual', [info.author], 1),
('status', 'pibootctl-status', 'pibootctl manual', [info.author], 1),
('get', 'pibootctl-get', 'pibootctl manual', [info.author], 1),
('set', 'pibootctl-set', 'pibootctl manual', [info.author], 1),
('save', 'pibootctl-save', 'pibootctl manual', [info.author], 1),
('load', 'pibootctl-load', 'pibootctl manual', [info.author], 1),
('diff', 'pibootctl-diff', 'pibootctl manual', [info.author], 1),
('show', 'pibootctl-show', 'pibootctl manual', [info.author], 1),
('list', 'pibootctl-list', 'pibootctl manual', [info.author], 1),
('remove', 'pibootctl-remove', 'pibootctl manual', [info.author], 1),
('rename', 'pibootctl-rename', 'pibootctl manual', [info.author], 1),
]
man_show_urls = True
# -- Options for Texinfo output -------------------------------------------
texinfo_documents = []
#texinfo_appendices = []
#texinfo_domain_indices = True
#texinfo_show_urls = 'footnote'
#texinfo_no_detailmenu = False
# -- Options for linkcheck builder ----------------------------------------
linkcheck_retries = 3
linkcheck_workers = 20
linkcheck_anchors = True
pibootctl-0.5.2/docs/development.rst 0000664 0000000 0000000 00000007747 13727517464 0017560 0 ustar 00root root 0000000 0000000 .. Copyright (c) 2020 Canonical Ltd.
.. Copyright (c) 2020 Dave Jones
..
.. This file is part of pibootctl.
..
.. pibootctl is free software: you can redistribute it and/or modify
.. it under the terms of the GNU General Public License as published by
.. the Free Software Foundation, either version 3 of the License, or
.. (at your option) any later version.
..
.. pibootctl is distributed in the hope that it will be useful,
.. but WITHOUT ANY WARRANTY; without even the implied warranty of
.. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
.. GNU General Public License for more details.
..
.. You should have received a copy of the GNU General Public License
.. along with pibootctl. If not, see .
.. _dev_install:
===========
Development
===========
If you wish to install a copy of pibootctl for development purposes, clone the
git repository and set up a configuration to use the cloned directory as the
source of the boot configuration:
.. code-block:: console
$ sudo apt install python3-dev git virtualenvwrapper
$ cd
$ git clone https://github.com/waveform80/pibootctl.git
$ mkvirtualenv -p /usr/bin/python3 pibootctl
$ cd pibootctl
$ workon pibootctl
(pibootctl) $ make develop
(pibootctl) $ cat > ~/.config/pibootctl.conf << EOF
[defaults]
boot_path=.
store_path=store
reboot_required=
reboot_required_pkgs=
EOF
At this point you should be able to call the :doc:`pibootctl ` utility,
and have it store the (empty) boot configuration as a `PKZIP`_ file under the
working directory:
.. code-block:: console
$ pibootctl save foo
$ pibootctl ls
+------+--------+---------------------+
| Name | Active | Timestamp |
|------+--------+---------------------|
| foo | x | 2020-03-08 22:40:28 |
+------+--------+---------------------+
To work on the clone in future simply enter the directory and use the
:command:`workon` command:
.. code-block:: console
$ cd ~/pibootctl
$ workon pibootctl
To pull the latest changes from git into your clone and update your
installation:
.. code-block:: console
$ cd ~/pibootctl
$ workon pibootctl
(pibootctl) $ git pull
(pibootctl) $ make develop
To remove your installation, destroy the sandbox and the clone:
.. code-block:: console
(pibootctl) $ cd
(pibootctl) $ deactivate
$ rmvirtualenv pibootctl
$ rm -fr ~/pibootctl
Building the docs
=================
If you wish to build the docs, you'll need a few more dependencies. Inkscape is
used for conversion of SVGs to other formats, Graphviz and Gnuplot are used for
rendering certain charts, and TeX Live is required for building PDF output. The
following command should install all required dependencies:
.. code-block:: console
$ sudo apt install texlive-xetex fonts-freefont-otf graphviz gnuplot inkscape
Once these are installed, you can use the "doc" target to build the
documentation:
.. code-block:: console
$ cd ~/pibootctl
$ workon pibootctl
(pibootctl) $ make doc
The HTML output is written to :file:`build/html` while the PDF output goes to
:file:`build/latex`.
Test suite
==========
If you wish to run the test suite, follow the instructions in
:ref:`dev_install` above and then make the "test" target within the sandbox:
.. code-block:: console
$ cd ~/pibootctl
$ workon pibootctl
(pibootctl) $ make test
A `tox`_ configuration is also provided that will test the utility against all
supported Python versions:
.. code-block:: console
$ cd ~/pibootctl
$ workon pibootctl
(pibootctl) $ pip install tox
...
(pibootctl) $ tox -p auto
.. note::
If developing under Ubuntu, the `Dead Snakes PPA`_ is particularly useful
for obtaining additional Python installations for testing.
.. _PKZIP: https://en.wikipedia.org/wiki/Zip_(file_format)
.. _tox: https://tox.readthedocs.io/en/latest/
.. _Dead Snakes PPA: https://launchpad.net/~deadsnakes/+archive/ubuntu/ppa
pibootctl-0.5.2/docs/diff.rst 0000664 0000000 0000000 00000006175 13727517464 0016140 0 ustar 00root root 0000000 0000000 .. Copyright (c) 2020 Canonical Ltd.
.. Copyright (c) 2020 Dave Jones
..
.. This file is part of pibootctl.
..
.. pibootctl is free software: you can redistribute it and/or modify
.. it under the terms of the GNU General Public License as published by
.. the Free Software Foundation, either version 3 of the License, or
.. (at your option) any later version.
..
.. pibootctl is distributed in the hope that it will be useful,
.. but WITHOUT ANY WARRANTY; without even the implied warranty of
.. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
.. GNU General Public License for more details.
..
.. You should have received a copy of the GNU General Public License
.. along with pibootctl. If not, see .
====
diff
====
.. program:: pibootctl-diff
Synopsis
========
.. code-block:: text
pibootctl diff [-h] [--json | --yaml | --shell] [left] right
Description
===========
Display the settings that differ between two stored boot configurations, or
between one stored boot configuration and the current configuration.
Options
=======
.. option:: left
The boot configuration to compare from, or the current configuration if
omitted.
.. option:: right
The boot configuration to compare against.
.. option:: -h, --help
Show a brief help page for the command.
.. option:: --json
Use JSON as the output format.
.. option:: --yaml
Use YAML as the output format.
.. option:: --shell
Use a tab-delimited output format suitable for the shell.
Usage
=====
The :command:`diff` command is used to display the differences between two boot
configurations; either two stored configurations (if two names are supplied on
the command line), or between the current boot configuration and a stored one
(if one name is supplied on the command line):
.. code-block:: console
$ sudo pibootctl save default
$ sudo pibootctl set video.hdmi0.group=1 video.hdmi0.mode=4
$ pibootctl diff default
+-------------------+----------------+--------------------+
| Name | | default |
|-------------------+----------------+--------------------|
| video.hdmi0.group | 1 (CEA) | 0 (auto from EDID) |
| video.hdmi0.mode | 4 (720p @60Hz) | 0 (auto from EDID) |
+-------------------+----------------+--------------------+
$ sudo pibootctl save 720p
$ pibootctl diff default 720p
+-------------------+--------------------+----------------+
| Name | default | 720p |
|-------------------+--------------------+----------------|
| video.hdmi0.group | 0 (auto from EDID) | 1 (CEA) |
| video.hdmi0.mode | 0 (auto from EDID) | 4 (720p @60Hz) |
+-------------------+--------------------+----------------+
For developers wishing to build on top of pibootctl, options are provided to
produce the output in JSON (:option:`--json`), YAML (:option:`--yaml`), and
shell-friendly (:option:`--shell`):
.. code-block:: console
$ pibootctl diff --json default 720p
{"video.hdmi0.mode": {"right": 4, "left": 0}, "video.hdmi0.group":
{"right": 1, "left": 0}}
pibootctl-0.5.2/docs/get.rst 0000664 0000000 0000000 00000005636 13727517464 0016010 0 ustar 00root root 0000000 0000000 .. Copyright (c) 2020 Canonical Ltd.
.. Copyright (c) 2020 Dave Jones
..
.. This file is part of pibootctl.
..
.. pibootctl is free software: you can redistribute it and/or modify
.. it under the terms of the GNU General Public License as published by
.. the Free Software Foundation, either version 3 of the License, or
.. (at your option) any later version.
..
.. pibootctl is distributed in the hope that it will be useful,
.. but WITHOUT ANY WARRANTY; without even the implied warranty of
.. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
.. GNU General Public License for more details.
..
.. You should have received a copy of the GNU General Public License
.. along with pibootctl. If not, see .
===
get
===
.. program:: pibootctl-get
Synopsis
========
.. code-block:: text
pibootctl get [-h] [--json | --yaml | --shell] setting [setting ...]
Description
===========
Query the status of one or more boot configuration settings. If a single
setting is requested then just that value is output. If multiple values are
requested then both setting names and values are output. This applies whether
output is in the default, JSON, YAML, or shell-friendly styles.
Options
=======
.. option:: setting
The name(s) of the setting(s) to query; if a single setting is given its
value alone is output, if multiple settings are queried the names and
values of the settings are output.
.. option:: -h, --help
Show a brief help page for the command.
.. option:: --json
Use JSON as the output format.
.. option:: --yaml
Use YAML as the output format.
.. option:: --shell
Use a var=value output format suitable for the shell.
Usage
=====
The :command:`get` command is primarily of use to those wishing to build
something on top of :command:`pibootctl`; for end users wishing to query the
current boot configuration the :doc:`status` command is of more use. When given
a single setting to query the value of that setting is output on its own, in
whatever output style is selected:
.. code-block:: console
$ pibootctl get video.overscan.enabled
on
$ pibootctl get --json video.overscan.enabled
true
When given multiple settings, names and values of those settings are both
output:
.. code-block:: console
$ pibootctl get serial.enabled serial.baud serial.uart
+----------------+-------------------------+
| Name | Value |
|----------------+-------------------------|
| serial.baud | 115200 |
| serial.enabled | on |
| serial.uart | 0 (/dev/ttyAMA0; PL011) |
+----------------+-------------------------+
$ pibootctl get --json serial.enabled serial.baud serial.uart
{"serial.enabled": true, "serial.baud": 115200, "serial.uart": 0}
Note that wildcards are not permitted with this command, unlike with the
:doc:`status` command.
pibootctl-0.5.2/docs/help.rst 0000664 0000000 0000000 00000006636 13727517464 0016162 0 ustar 00root root 0000000 0000000 .. Copyright (c) 2020 Canonical Ltd.
.. Copyright (c) 2020 Dave Jones
..
.. This file is part of pibootctl.
..
.. pibootctl is free software: you can redistribute it and/or modify
.. it under the terms of the GNU General Public License as published by
.. the Free Software Foundation, either version 3 of the License, or
.. (at your option) any later version.
..
.. pibootctl is distributed in the hope that it will be useful,
.. but WITHOUT ANY WARRANTY; without even the implied warranty of
.. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
.. GNU General Public License for more details.
..
.. You should have received a copy of the GNU General Public License
.. along with pibootctl. If not, see .
====
help
====
.. program:: pibootctl-help
Synopsis
========
.. code-block:: text
pibootctl help [-h] [command | setting]
Description
===========
With no arguments, displays the list of :command:`pibootctl` commands. If a
command name is given, displays the description and options for the named
command. If a setting name is given, displays the description and default value
for that setting.
Options
=======
.. option:: -h, --help
Show a brief help page for the command.
.. option:: command
The name of the command to output help for. The full command name must be
given; abbreviations are not accepted.
.. option:: setting
The name of the setting to output help for.
If the setting is not recognized, and contains an underscore ('_')
character, the utility will assume it is a config.txt configuration command
and attempt to output help for the setting that corresponds to it. If
multiple settings correspond, their names will be printed instead.
Usage
=====
The :command:`help` command is the default command, and thus will be invoked if
:command:`pibootctl` is called with no other arguments. However it can also be
used to retrieve help for specific commands:
.. code-block:: console
$ pibootctl help ls
usage: pibootctl list [-h] [--json | --yaml | --shell]
List all stored boot configurations.
optional arguments:
-h, --help show this help message and exit
--json Use JSON as the format
--yaml Use YAML as the format
--shell Use a var=value or tab-delimited format suitable for the
shell
Alternatively, it can be used to describe settings:
.. code-block:: console
$ pibootctl help boot.debug.enabled
Name: boot.debug.enabled
Default: off
Command(s): start_debug, start_file, fixup_file
Enables loading the debugging firmware. This implies that start_db.elf (or
start4db.elf) will be loaded as the GPU firmware rather than the default
start.elf (or start4.elf). Note that the debugging firmware incorporates
the camera firmware so this will implicitly switch camera.enabled on if it
is not already.
The debugging firmware performs considerably more logging than the default
firmware but at a performance cost, ergo it should only be used when
required.
Finally, if you are more familiar with the "classic" boot configuration
commands, it can be used to discover which :command:`pibootctl` settings
correspond to those commands:
.. code-block:: console
$ pibootctl help start_file
start_file is affected by the following settings:
camera.enabled
boot.debug.enabled
boot.firmware.filename
pibootctl-0.5.2/docs/images/ 0000775 0000000 0000000 00000000000 13727517464 0015732 5 ustar 00root root 0000000 0000000 pibootctl-0.5.2/docs/images/setting_hierarchy.dot 0000664 0000000 0000000 00000001353 13727517464 0022157 0 ustar 00root root 0000000 0000000 digraph classes {
graph [rankdir=RL, splines=ortho];
node [shape=rect, style=filled, fontname=Sans, fontsize=10];
edge [];
/* Abstract classes */
node [color="#9ec6e0", fontcolor="#000000"]
Setting;
/* Concrete classes */
node [color="#2980b9", fontcolor="#ffffff"];
Overlay->Setting;
OverlayParam->Overlay;
OverlayParamInt->OverlayParam;
OverlayParamBool->OverlayParam;
Command->Setting;
CommandInt->Command;
CommandIntHex->CommandInt;
CommandBool->Command;
CommandBoolInv->CommandBool;
CommandForceIgnore->CommandBool;
CommandMaskMaster->CommandInt;
CommandMaskDummy->CommandMaskMaster;
CommandFilename->Command;
CommandIncludedFile->CommandFilename;
}
pibootctl-0.5.2/docs/images/setting_hierarchy.pdf 0000664 0000000 0000000 00000022445 13727517464 0022147 0 ustar 00root root 0000000 0000000 %PDF-1.4
%µí®û
3 0 obj
<< /Length 4 0 R
/Filter /FlateDecode
>>
stream
xœ¥WMs7½ï¯àQ:˜! $¯jÓÖ™ñô#ºerÐÄk'©VžÊNÚüû‚ÜoiåÕÌŽÇcÒx ÁGàûO*ýÕ›QÏ…QF1EÔ±T…Ñ‘MPF{ÏÖƒ‚–²×+Ö¿~•…ÿ•ßÉï×âÃG1u_Xu§¬BŒÊYuCœ¶Ùä}MZq³- žÈ mBVð&h§¶UñæáÆÜˆEmŠ«÷åËË—Ããúãö]ñv+ÁÙ^¶rFKáxt6Ö±^2¦PüWa QT;ã¨$ã˜-(d<kõû÷ò¸ßýXo¿æ ²_Ú‚BËB¨ªž!«½â´4“÷=cH›UÊ
ñ-Šm¯>'àÍR)$G^fHA`ÍÑ#³°§îªaåµ¥ÕºKk™¶ƒ(·àCØj'™Tϧ©é1ÙÃ=:kÀÌͽ„r©F¬’pgˆ!&í‚‹©¨,]CÌía}C«—3~Èy©2’eX¢G‡y´¯Gh4¸À:—.²Á4¾Ðz
kâ鿌)j’Ìli‘‹9ÖwvUmžžöL‘ƒ
#Jôd$à<›æ§C„:ó0=z×ÔØ)~ ?Ñ*td?/; ½h‡‰užŸsóÓSUíròÜŸQ²¸ì£ÉåBI³èóq’`P즗(Cl#?|cCütÐeâ“å}œŸ¨Ù;/É
f¨¹=œ—VÚ,IxSKm ›ùéi1ruI¬Æý
¶–žzYAq"ƱŠáñ±$¿Ü¿•kàÕõÄòK¾#5ê‘Fµò$ê@^ó×”§Å4¾¦õ¨•§_¡Už¿(ƒ¤/T˜¥ !F$á ÐÏð4©8hD›¥u Û¥hXš½’<Í[7ôè¡QœSü²r™”ùüNeº’˜ÛÃ÷‰ì±:¤Ô'ÎjÌòÊCž]Rã=zkìÔxŒ_ÄôšI‘q¶á!g4Iwªüä³>`æ—5ÙÕÓq°úTÞ>dqUž3%AD«ÓåTyh›#£Åfv‰²a:ÊzÞê”
ñË(£,Ó€ó½:˜Ü9ÏëôÝîùï»4Ú=¿”Ç ®P3¦…lÎ*ö³ž]¢¨E´
=zkOÑ¿„"glM™9Šœ´eÌ1"^IÑÏßÒ°ª~œ1ä¤K‰-AVZb$û
A=¢>°¼ÞÚtŠ_B4©˜ååPCê¾,Ï–‡Õ—}yØU絖¦ü)/Çb#½òU×Ì.IwFP褻÷èýÝ@º‡ø…ò$kX9¬äÇ%O†T%LvÒ£§ÿÓþÛ})„qL„M›Õ$¹”›©6ðÚÊç'¹‹ÝQ©;ð¾³Õoþº)þ,þG¢tí
endstream
endobj
4 0 obj
1051
endobj
2 0 obj
<<
/ExtGState <<
/a0 << /CA 1 /ca 1 >>
>>
/Font <<
/f-0-0 5 0 R
>>
>>
endobj
6 0 obj
<< /Type /Page
/Parent 1 0 R
/MediaBox [ 0 0 638 368 ]
/Contents 3 0 R
/Group <<
/Type /Group
/S /Transparency
/I true
/CS /DeviceRGB
>>
/Resources 2 0 R
>>
endobj
7 0 obj
<< /Length 8 0 R
/Filter /FlateDecode
/Length1 8480
>>
stream
xœíY{|TŽŸ9¿™³ç±¯³ÙÍû±ÉæµHš <ÌŠ€<,
‘`Ñ !j "
LÄ’A #BÄ€#RÜ`D¨‘‡‘ÚVð–KU,õ6bÚ‹Ú†drgÔÖÚÏýï~îçsÏÉ윙9gæ÷þ}gB(!D#•ˆwî}³Ë~·qG!ž „H3ç>ø€—,ˆË#$¢‘*JËî¾oñ…m²ÿî{——Fþáè1|n"Ľ}þ¼Ù%Ê=›>'$ç Cçc‡m§e-¶×`;yþ},{<Û¹Ûø>yàÞEsgšî%$Yvßìeel¼ÛÛ°í-»^ÙHË_ð1&HŸO$R*êX)oDj-$:`e׈|*¼Bb$³ílLjólÇÙŽ¬0#ÑHI4Ké^1ÝŸˆ:‹ýo½_öJª{?f»x'I#FÙ¬’]—ââU²hRBBüMO`J<Ϻ·DÖ¬–lIyÒX—¯é 1’ed‰r'¥;/´utw\2\yxáÒ—®^êp^ùòŠó„‘—5yÚ‹Óþ>öWEI~JgNðgúä‡YÔ3˜ú’d;<ÆS›%&¥¦åÆÓœì¡¹CR3é`š;$9';œMXòÎ]»_yhÏÃý‡ø@\^øyeyÇý/¶V×—ô6øbÁoyã[ÆV>8w^BTÆùÃçÿ•ùËqã×<ò“ ‘ƒŽí?q)ÕI#߬œ¸I)$U«”5Üóå-VúZd‹+h]ã‘B&K.ǸXgwÇÕŽ6d0Ä]Ç%缯^Áެ€??®,®!î—qq<ŸäÓ|)ß“ÃZ2•Lu ¶ˆ,¢‹¤EžE1ê¬ÅyM16Ìc§>/1œ$'›XBü[XE÷Aë™Wžœ3÷—÷ˆ«â$õwD-Ai÷šú»tçÌ£'‡90` N5Fo´m=t`š$†Œý•ï adx Êμ@ÚªTk:*”Åé²w;»Gµá_¶©¥ÌŽ«£Ú:²¼¼¬ƒ/yPÔHô$îð‘ÔãKJÍ5|¹9}ˆ–‹Õ“—¼þú¹]ÕÕ|‡øù†ž†š)õ;-o 7 E¢<#ËewÈ3vù({™´Jœ*ŒŒWpÉŽl\íRwGV@wªµ@-VËTNg…å>#Çã;Ä‹_kÝŸš¼!„• ~ÂÈÐ@¨ìT®¶Ak«F%…L±©ŠnòÒ‘}
=sÔ¥«m†-íP±ç]drâ3†¤šZàjÚNIpÅŠÚ¦––1¯,=~Bjìù±´c玣=Õ¬øÀ¼’ÏM»ÓÙL\W'édRÀeS]Uaá-hIõÓZÕÇëÑq©QD±Þ,»\Þq~gwÚE¶É_Û¥“§8gZE^Öáâ• RÓGŠ;µá”¾±íÑM I2œ.¤/"7ví®Ý²{÷–ÚÝA!ºf7MºãÖŸÊ;¸âÝÝ¿Xq0/(>uá©“.üY|$>‹eà€×߸cî:‚etÄœ¹ûL},éý˜ŸG¿ÖIñÂäZ©µ>éZ©F9r ÊãŒDÙuwô™²óJMê7CüM™dbèÒ.ˆ
.P*z/à"ËÄqB¼%ªér~‹ŠOÄEN Ñ4†Nhwˆb§¸ƒ6Ò9xï&¦.G£.+X1‘ɵ@Œ3É 7+d"SƒyŒä
.s(gÄâ<;¹Y+œÑ‚†MnvNnöÞavô^Ô²ÞìþÈÂ?³8•þÂ?+J¢'&H¥r©Bª’*¥'¥FI1RAeôõhˆf©$•úÁϼJ.É¥#`ËRÆ“ñt"Ldãù9 L'Ói±¥””Ò°€ÝÍçËÅÊRò -‡r¶”?,¯&«i
Ô°^%ב:ºUª‡mlß*ïåÏËÍÊ1å¢Ò«Ü0‹ ¥«4‡úF¿Iï¤w¾)~ÜÅŠ»¡éZé·w˜„vg¬€[Ö-ÄСÚT[-š¬e¼Ë4³a:ûŽt„í3-½/p~cæ0)aâÀíÏ·´Œ8²:lp,ríG{¢‘—Îå<´Þ7þšô*Ù*Q…ŒgNÓ2ÑEmN༘—ñN.÷9):¨ìþ{‡i[å;!I!´¨=Bµ“"ä»áJ8Ûâë"¬$"M?M Å=.gç,ú‰