devuan's apt repo merger
git clone git://
Log | Files | Refs | README | LICENSE

commit 198ab28f3bff343175099626b40066f53a0c6d80
Author: parazyd <>
Date:   Fri, 21 Apr 2017 21:56:43 +0200


A.gitignore | 3+++
ALICENSE | 661+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
AMakefile | 2++
Aamprolla-init | 62++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adoc/ | 50++++++++++++++++++++++++++++++++++++++++++++++++++
Adoc/dan-notes | 109+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adoc/directories | 26++++++++++++++++++++++++++
Adoc/file-formats | 96+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Alib/ | 0
Alib/ | 198+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Alib/ | 106+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Alib/ | 33+++++++++++++++++++++++++++++++++
Alib/ | 21+++++++++++++++++++++
Alib/ | 26++++++++++++++++++++++++++
14 files changed, 1393 insertions(+), 0 deletions(-)

diff --git a/.gitignore b/.gitignore @@ -0,0 +1,3 @@ +*.pyc +spool/ +merged/ diff --git a/LICENSE b/LICENSE @@ -0,0 +1,661 @@ + GNU AFFERO GENERAL PUBLIC LICENSE + Version 3, 19 November 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 Affero General Public License is a free, copyleft license for +software and other kinds of works, specifically designed to ensure +cooperation with the community in the case of network server software. + + The licenses for most software and other practical works are designed +to take away your freedom to share and change the works. By contrast, +our General Public Licenses are 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. + + 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. + + Developers that use our General Public Licenses protect your rights +with two steps: (1) assert copyright on the software, and (2) offer +you this License which gives you legal permission to copy, distribute +and/or modify the software. + + A secondary benefit of defending all users' freedom is that +improvements made in alternate versions of the program, if they +receive widespread use, become available for other developers to +incorporate. Many developers of free software are heartened and +encouraged by the resulting cooperation. However, in the case of +software used on network servers, this result may fail to come about. +The GNU General Public License permits making a modified version and +letting the public access it on a server without ever releasing its +source code to the public. + + The GNU Affero General Public License is designed specifically to +ensure that, in such cases, the modified source code becomes available +to the community. It requires the operator of a network server to +provide the source code of the modified version running there to the +users of that server. Therefore, public use of a modified version, on +a publicly accessible server, gives the public access to the source +code of the modified version. + + An older license, called the Affero General Public License and +published by Affero, was designed to accomplish similar goals. This is +a different license, not a version of the Affero GPL, but Affero has +released a new version of the Affero GPL which permits relicensing under +this license. + + 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 Affero 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. Remote Network Interaction; Use with the GNU General Public License. + + Notwithstanding any other provision of this License, if you modify the +Program, your modified version must prominently offer all users +interacting with it remotely through a computer network (if your version +supports such interaction) an opportunity to receive the Corresponding +Source of your version by providing access to the Corresponding Source +from a network server at no charge, through some standard or customary +means of facilitating copying of software. This Corresponding Source +shall include the Corresponding Source for any work covered by version 3 +of the GNU General Public License that is incorporated pursuant to the +following paragraph. + + 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 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 work with which it is combined will remain governed by version +3 of the GNU General Public License. + + 14. Revised Versions of this License. + + The Free Software Foundation may publish revised and/or new versions of +the GNU Affero 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 Affero 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 Affero 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 Affero 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. + + <one line to give the program's name and a brief idea of what it does.> + Copyright (C) <year> <name of author> + + This program is free software: you can redistribute it and/or modify + it under the terms of the GNU Affero 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 Affero General Public License for more details. + + You should have received a copy of the GNU Affero General Public License + along with this program. If not, see <>. + +Also add information on how to contact you by electronic and paper mail. + + If your software can interact with users remotely through a computer +network, you should also make sure that it provides a way for users to +get its source. For example, if your program is a web application, its +interface could display a "Source" link that leads users to an archive +of the code. There are many ways you could offer source, and different +solutions will be better for different programs; see section 13 for the +specific requirements. + + 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 AGPL, see +<>. diff --git a/Makefile b/Makefile @@ -0,0 +1,2 @@ +clean: + rm -f **/*.pyc diff --git a/amprolla-init b/amprolla-init @@ -0,0 +1,62 @@ +#!/usr/bin/env python2 +# copyright (c) 2017 - Ivan J. <> +# see LICENSE file for copyright and license details + +import os +#import re +import requests +import sys +import threading + +import lib.config as config +import as delta +import lib.fs as fs +import as net +from lib.log import die, notice, warn, cleanexit + + +def popDirs(): + paths = fs.crawl() + + notice("creating initial directory structure") + for i in range(0, len(paths)): + baseurl = "http://" + "/".join([config.repos[i]["host"], config.repos[i]["dists"]]) + basepath = "/".join([config.amprolla["spooldir"], config.repos[i]["dists"]]) + + for j in paths[config.repos[i]["name"]]: + suiteurl = "/".join([baseurl, j]) + suitepath = "/".join([basepath, j]) + if not os.path.exists(suitepath): + os.makedirs(suitepath) + + for k in config.mainrepofiles: + relurl = "/".join([suiteurl, k]) + relfile = "/".join([suitepath, k]) + if not os.path.isfile(relfile): +, relfile) + + try: + with open(suitepath + "/Release", "rb") as frel: + rels = + relmap = delta.parseRel(rels) + except IOError: + warn("no Release file for %s" % suitepath) + + try: + for k in relmap: + if relmap[k] == "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855": + continue # ^ this is /dev/null + fileurl = "/".join([suiteurl, k]) + filepath = "/".join([suitepath, k]) + if not os.path.exists(os.path.dirname(filepath)): + os.makedirs(os.path.dirname(filepath)) + if not os.path.isfile(filepath): +, filepath) + except TypeError: + warn("Typeerror") + +def merge(): + for i in config.amprolla["mergedsubdirs"]: + mdir = "/".join([config.amprolla["mergedir"], i]) + if not os.path.exists(mdir): + os.makedirs(mdir) diff --git a/doc/ b/doc/ @@ -0,0 +1,50 @@ +* an older spool directory hierarchy, for testing the merging: + (2GB) + + +workflow +-------- + +`amprolla-init` creates the `spool` directory hierarchy. This hierarchy +is the untouched repositories we want to merge. They can be found in +`lib/` in the `repos` dict. + +`fs.crawl()` takes the info from `` and generates the paths we +use to figure out what to download. Then `popDirs()` in `amprolla-init` +uses these paths to actually create the directory structure and download +the `Release` files from there. (NOTE: at a final point it should also +check the gpg signatures from the `InRelease` file) + +After the Release files are downloaded, they are parsed for their +contents and all the files they list are downloaded in series (possibly +should be parallel). + +So now we have all the files we need to create a merge. + + + +The merge will be done in the `merged/` directory. To do a successful +merge, these are the points that need to be accomplished: + + * we must skip packages that are in `` + * for each `binary-$arch` we must create a new `Packages` file, + containing our merge: + * we parse every package and fill in a dict + * first priority 0, then 1, then 2, etc... + * if a package already exists from a higher-priority repo - it + gets skipped + * (NOT SURE): if a package from `banpkgs` is in a package's + dependency list - that package gets skipped + * once we've finished the iteration, we dump a new Packages file + from the updated dict + + + +After the initial merge, we need to watch for updates. My idea is to +make amprolla pool the above-mentioned Release files as they contain +enough metadata for us to find out what changed. They also contain a +date entry so we can see if there was actually an update without digging +too deep. + +So if we figure out there was an update, we download the new file, parse +it into a dict and compare it to the old version of that file/dict. diff --git a/doc/dan-notes b/doc/dan-notes @@ -0,0 +1,109 @@ +Ok... so the debian repo is essentially a directory heirarchy... + +Ok.. Do you understand the repo heirarchy? ie the main folder (in +amprolla case /merged) with sub folders 'dist' (for repo metadata) and +'pool' (where the actual binary and source packages go)?? +forget about the "pool" folder, amprolla doesn't touch it... + +in "dists/" you have all the suites ie: jessie, ascii, ceres and all +the and stable, unstable and version symlinks. + +in the suite folder, you find the section folders: main contrib non-free +and files InRelease, Release and Release.gpg + +InRelease is just the pgp/smime version of the Release file - the gpg +sig is the same as Release.gpg + +Anyway the Release file basically is a dictionary of most of the files +in the subdirectory with size and checksums (SHA256, SHA512 etc) in what +is essentially RFC822 format, with a bunch of headers at the top that +specify details about the Release of that suite. + +In the suite subdirectories you have a bunch of folders, binary-<arch> +which contains the Packages file, and compressed copies of that, and a +Release Stanza, and similar for the source folder with Sources file and +compressed copies etc. + +the Contents files (currently not processed) are their too. +(They contain a list of all the files in each package) + +their is also the i8n - folder which contains the processed files. +oops s/processed files/translation files/ + + +Amprolla takes several mirrors and merges them in order of priority +starting with the highest priority. It firsts iterates over the structure +to create it's repo structure, ie dists/<suite>/<section>/ etc and then first +copies the highest priority mirror Packages and Sources files in and then for +the othermirrors iterates over the Packages and Sources files and compares +each package stanza for a match, and if there is a match on name then the highest +priority mirror version is kept, if not then the package is added in. +(This is where the inefficient model really shows up) + + +After all the new Source and Packages files are processed then the Release and +InRelease files are generated by walking the hierarchy and adding those files in. + +There is a lot of complexities, part of which is in the design of amprolla. +What I had started to do, and in describing it now, it seems obvious to me +I should probably have started pretty much from scratch is instead of this +iterative approach of compare and add or skip is keep a cache of each mirrors +last state, and then on each run create a delta between the last state and +current state. + + +* and how does dak integrate in all of this? +it doesn't. Dak is a standalone repository which just deals with the packages built by our CI +* so it's the same as any debian repo +Yup, slightly modified to handle our CI and some other tweaks +and I checked and our version is in gdo too. + + +anyway as I was saying about my approach re delta's: +There are big efficiencies in this approach. For starters, we only download the InRelease or +Release and Release.gpg file and after verifying it, compare to the previous state, and we +can use the delta generated to pick what files are new, changed or removed from the repo. +This means we only download the changed files in the repo for a start. And for the +Packages and Sources files we create a delta list of changed stanza's to apply. + +Instead of building the entire repo from scratch, we apply the delta +to a copy of our merged repo with handling for priority etc... + +What stumped me in the end is we actually should verify that we only have packages go in that +have a matching source stanza and we really need to process the contents and translations +at the same time. + +I suspect that nextime realised this which is why he started on amprolla2 which essentially +replicates dak + amprolla function... + +I just realised, I forgot to mention the overrides processing in amprolla. In the very +top of the dir in "merged/" is the "indices" folder that contains overrides. These +files specify for each Packages files, any metadata changes that need to be applied to +package stanza's + +In debian their is a entry for every single deb package/source in the archive making +them very large. We did away with that to reduce the overhead of processing it created. + +So we only have entries for those that need changing, usually to change priorities of +systemd packages and remove recommends and suggests for systemd related packages. + +* are indices a part of the repo or only needed by amprolla? +both. In debian, dak generates them and they are hand modified by the repo masters to +apply needed fixes. With amprolla, we only create them for applying our own changes as needed. +Technically they don't need to be in the repo, as they're not used by apt, but practically +it's good to have them there. + +hmmm, I think I've cracked my problem... +If I use the Sources delta to identify changed packages, I can use that to pick and apply +the changed Packages stanza's Contents and Translations. This would save lot's of +iterations, and I only need the delta Processing to be done on the Sources files. +Wow that would really speed things up + +The other benefit, is we can side load packages this way too and use it to replace dak +as well as either a standalone repo or directly into the merged repo. +And all without a hefty database. or the writeup + +your welcome. It has helped me probably as much as you. I think it's +turning into a full rewrite, but seems better design and possibly far easier to +write from scratch. +Anyway, it's nearly 3:30am here, so better get a couple hours sleep! diff --git a/doc/directories b/doc/directories @@ -0,0 +1,26 @@ +example aliases(?) + + +1.0 -> jessie +2.0 -> ascii +ascii +ascii-backports +ascii-proposed-updates +ascii-security +ascii-updates +ceres -> unstable +jessie +jessie-backports +jessie-proposed-updates +jessie-security +jessie-updates +sid -> unstable +stable -> jessie +stable-backports -> jessie-backports +stable-proposed-updates -> jessie-proposed-updates/ +stable-updates -> jessie-updates/ +testing -> ascii +testing-backports -> ascii-backports +testing-proposed-updates -> ascii-proposed-updates/ +testing-updates -> ascii-updates +unstable diff --git a/doc/file-formats b/doc/file-formats @@ -0,0 +1,96 @@ +example package: +---------------- + Package: apache2-mpm-event + Source: apache2 + Version: 2.4.10-10+deb8u8 + Installed-Size: 22 + Maintainer: Debian Apache Maintainers <> + Architecture: amd64 + Provides: httpd, httpd-cgi + Depends: apache2 (= 2.4.10-10+deb8u8) + Description: transitional event MPM package for apache2 + Homepage: + Description-md5: e8836e8c2c34524fb11cc83011803e4e + Section: httpd + Priority: optional + Filename: pool/updates/main/a/apache2/apache2-mpm-event_2.4.10-10+deb8u8_amd64.deb + Size: 1520 + MD5sum: e82aa67838c581d8217795dd6dbcb614 + SHA1: a0d59e70ea06d145af068f46649ba80a75bb75cf + SHA256: e756d82ab7111a9c76291c91e344bbbddc0d9945704ad42f1140af0594c74cad + +example source: +--------------- + + Package: apache2 + Binary: apache2, apache2-data, apache2-bin, apache2-mpm-worker, apache2-mpm-prefork, apache2-mpm-event, apache2-mpm-itk, apache2.2-bin, apache2.2-commo + n, libapache2-mod-proxy-html, libapache2-mod-macro, apache2-utils, apache2-suexec, apache2-suexec-pristine, apache2-suexec-custom, apache2-doc, apache2 + -dev, apache2-dbg + Version: 2.4.10-10+deb8u8 + Maintainer: Debian Apache Maintainers <> + Uploaders: Stefan Fritsch <>, Arno Töll <> + Build-Depends: debhelper (>= 9.20131213~), lsb-release, dpkg-dev (>= 1.16.1~), libaprutil1-dev (>= 1.5.0), libapr1-dev (>= 1.5.0), libpcre3-dev, zlib1g + -dev, libssl-dev (>= 0.9.8m), perl, liblua5.1-0-dev, libxml2-dev, autotools-dev, gawk | awk + Architecture: any all + Standards-Version: 3.9.6 + Format: 3.0 (quilt) + Files: + 4cc0006932cbdb7a2597691505f39424 3277 apache2_2.4.10-10+deb8u8.dsc + 44543dff14a4ebc1e9e2d86780507156 5031834 apache2_2.4.10.orig.tar.bz2 + 7d43a85707568321b98305fe61e386d5 555484 apache2_2.4.10-10+deb8u8.debian.tar.xz + Vcs-Browser: + Vcs-Git: git:// + Checksums-Sha1: + dd6e773c03c22eb97beffe56e39b9f4b17eea31e 3277 apache2_2.4.10-10+deb8u8.dsc + 00f5c3f8274139bd6160eda2cf514fa9b74549e5 5031834 apache2_2.4.10.orig.tar.bz2 + a789b374f989dfe3734cb9b1895e7d2891b5fd04 555484 apache2_2.4.10-10+deb8u8.debian.tar.xz + Checksums-Sha256: + c20dc666e6192c3db716e1dfb60afed3248aabd9a2d3232301a11fe8d936dac6 3277 apache2_2.4.10-10+deb8u8.dsc + 176c4dac1a745f07b7b91e7f4fd48f9c48049fa6f088efe758d61d9738669c6a 5031834 apache2_2.4.10.orig.tar.bz2 + 352be8c8245c162a9d97cf167a904fd1684904ffede565f23a654935701b40fa 555484 apache2_2.4.10-10+deb8u8.debian.tar.xz + Homepage: + Build-Conflicts: autoconf2.13 + Package-List: + apache2 deb httpd optional arch=any + apache2-bin deb httpd optional arch=any + apache2-data deb httpd optional arch=all + apache2-dbg deb debug extra arch=any + apache2-dev deb httpd optional arch=any + apache2-doc deb doc optional arch=all + apache2-mpm-event deb oldlibs extra arch=any + apache2-mpm-itk deb oldlibs extra arch=any + apache2-mpm-prefork deb oldlibs extra arch=any + apache2-mpm-worker deb oldlibs extra arch=any + apache2-suexec deb oldlibs extra arch=any + apache2-suexec-custom deb httpd extra arch=any + apache2-suexec-pristine deb httpd optional arch=any + apache2-utils deb httpd optional arch=any + apache2.2-bin deb oldlibs extra arch=any + apache2.2-common deb oldlibs extra arch=any + libapache2-mod-macro deb oldlibs extra arch=any + libapache2-mod-proxy-html deb oldlibs extra arch=any + Directory: pool/updates/main/a/apache2 + Priority: source + Section: httpd + +example translation: +-------------------- + + Package: libactivemq-java + Description-md5: b7875bda385f5f6b4e36597054392132 + Description-en: Java message broker core libraries + Apache ActiveMQ is a message broker built around Java Message Service (JMS) + API : allow sending messages between two or more clients in a loosely coupled, + reliable, and asynchronous way. + . + This message broker supports : + * JMS 1.1 and J2EE 1.4 with support for transient, persistent, transactional + and XA messaging + * Spring Framework, CXF and Axis integration + * pluggable transport protocols such as in-VM, TCP, SSL, NIO, UDP, multicast, + JGroups and JXTA + * persistence using JDBC along with journaling + * OpenWire (cross language wire protocol) and + Stomp (Streaming Text Orientated Messaging Protocol) protocols + . + This package contains a core Java library for ActiveMQ. diff --git a/lib/ b/lib/ diff --git a/lib/ b/lib/ @@ -0,0 +1,198 @@ +#!/usr/bin/env python +# copyright (c) 2017 - Ivan J. <> +# see LICENSE file for copyright and license details + +amprolla = { + "spooldir": "./spool", + "sign_key": "fa1b0274", + "mergedir": "./merged", + "mergedsubdirs": [ "dists", "pool"], + "banpkgs": [ 'systemd', 'systemd-sysv' ] + #"checksums": [ 'md5sum', 'sha1', 'sha256', 'sha512' ] +} + +repos = { + ## key name is priority, first is 0 + 0: { + "name": "DEVUAN", + "host": "", + "dists": "devuan/dists", + "pool": "devuan/pool", + "aliases": False, + "skipmissing": False + }, + 1: { + "name": "DEBIAN-SECURITY", + "host": "", + "dists": "dists", + "pool": "pool", + "aliases": True, + "skipmissing": True + }, + 2: { + "name": "DEBIAN", + #"host": "", + "host": "", + "dists": "debian/dists", + "pool": "debian/pool", + "aliases": True, + "skipmissing": False + } +} + +suites = { + 'jessie': [ + 'jessie', + 'jessie-backports', + 'jessie-proposed-updates', + 'jessie-security', + 'jessie-updates' + ], + 'ascii': [ + 'ascii', + 'ascii-backports', + 'ascii-proposed-updates', + 'ascii-security', + 'ascii-updates' + ], + 'unstable': [ + 'unstable' + ] +} + +aliases = { + "DEBIAN-SECURITY": { + 'ascii-security': 'testing/updates', + 'jessie-security': 'jessie/updates' + }, + "DEBIAN": { + 'ascii': 'testing', + 'ascii-backports': 'testing-backports', + 'ascii-proposed-updates': 'testing-proposed-updates', + 'ascii-updates': 'testing-updates' + } +} + +categories = [ 'main', 'contrib', 'non-free' ] + + +releases = { + "Release-jessie": { + "Suite": "stable", + "Codename": "jessie", + "Label": "Devuan", + "Version": "1.0", + "Description": "Devuan 1.0 Jessie (stable release)" + }, + "Release-ascii": { + "Suite": "testing", + "Codename": "ascii", + "Label": "Devuan", + "Version": "2.0", + "Description": "Devuan 2.0 Ascii (testing release)" + }, + "Release-unstable": { + "Suite": "unstable", + "Codename": "ceres", + "Label": "Devuan", + "Version": "x.x", + "Description": "Devuan x.x Ceres (unstable release)" + } +} + + +binaryarches = [ + 'all', + 'alpha', + 'amd64', + 'arm64', + 'armel', + 'armhf', + 'hppa', + 'hurd-i386', + 'i386', + 'ia64', + 'kfreebsd-amd64', + 'kfreebsd-i386', + 'mips', + 'mips64el', + 'mipsel', + 'powerpc', + 'ppc64el', + 's390x', + 'sparc' +] + +installerarches = [ + 'amd64', + 'arm64', + 'armel', + 'i386' +] + +mainrepofiles = [ + "InRelease", + "Release", + "Release.gpg" +] + +pkgfmt = [ + 'Package:', + 'Version:', + 'Essential:', + 'Installed-Size:', + 'Maintainer:', + 'Architecture:', + 'Replaces:', + 'Provides:', + 'Depends:', + 'Conflicts:', + 'Pre-Depends:', + 'Breaks:', + 'Homepage:', + 'Apport:', + 'Auto-Built-Package:', + 'Build-Ids', + 'Origin:', + 'Bugs:', + 'Built-Using:', + 'Enhances:', + 'Recommends:', + 'Description:', + 'Description-md5:', + 'Ghc-Package:', + 'Gstreamer-Decoders:', + 'Gstreamer-Elements:', + 'Gstreamer-Encoders:', + 'Gstreamer-Uri-Sinks:', + 'Gstreamer-Uri-Sources:', + 'Gstreamer-Version:', + 'Lua-Versions:', + 'Modaliases:', + 'Npp-Applications:', + 'Npp-Description:', + 'Npp-File:', + 'Npp-Mimetype:', + 'Npp-Name:', + 'Origin:', + 'Original-Maintainer:', + 'Original-Source-Maintainer:', + 'Package-Type:', + 'Postgresql-Version:', + 'Python-Version:', + 'Python-Versions:', + 'Ruby-Versions:', + 'Source:', + 'Suggests:', + 'Xul-Appid:', + 'Multi-Arch:', + 'Build-Essential:', + 'Tag:', + 'Section:', + 'Priority:', + 'Filename:', + 'Size:', + 'MD5sum:', + 'SHA1:', + 'SHA256:' +] diff --git a/lib/ b/lib/ @@ -0,0 +1,106 @@ +#!/usr/bin/env python +# copyright (c) 2017 - Ivan J. <> +# see LICENSE file for copyright and license details + +import ast +import gzip +import re +import requests +import time + +import config +from log import notice + +def getTime(date): + return time.mktime(time.strptime(date, "%a, %d %b %Y %H:%M:%S %Z")) + +def getDate(relfile): + match ='Date: .+', relfile) + if match: + line = relfile[match.start():match.end()] + relfile = line.split(': ')[1] + return relfile + + +def parseRel(reltext): + hash = {} + match ='SHA256:+', reltext) + if match: + line = reltext[match.start():-1] + for i in line.split('\n'): + if i == 'SHA256:' or i == '\n': # XXX: hack + continue + hash[(i.split()[2])] = i.split()[0] + return hash + + +def pkgParse(entry): + # for parsing a single package + values = re.split('\\n[A-Z].+?:', entry)[0:] + values[0] = values[0].split(':')[1] + keys = re.findall('\\n[A-Z].+?:', '\n'+entry) + both = zip(keys, values) + return {key.lstrip(): value for key, value in both} + + +def parsePkgs(pkgtext): + # this parses our package file into a hashmap + # key: package name, value: entire package paragraph as a hashmap + map = {} + + # TODO: consider also this approach + #def parsePkgs(pkgfilepath): + #with, "rb") as f: + # pkgs ="\n\n") + + pkgs = pkgtext.split("\n\n") + for pkg in pkgs: + m = re.match('Package: .+', pkg) + if m: + line = pkg[m.start():m.end()] + key = line.split(': ')[1] + map[key] = pkgParse(pkg) + return map + + +def printPkg(map, pkgname): + try: + pkg = ast.literal_eval(map[pkgname]) + sin = [] + for i in config.pkgfmt: + if config.pkgfmt[i] in pkg.keys(): + sin.append(config.pkgfmt[i] + pkg[config.pkgfmt[i]]) + return sin + except: + log.die("nonexistent package") + + +def dictCompare(d1, d2): + d1_keys = set(d1.keys()) + d2_keys = set(d2.keys()) + intersect_keys = d1_keys.intersection(d2_keys) + modified = {o : (d1[o], d2[o]) for o in intersect_keys if d1[o] != d2[o]} + return modified + + +def compareRel(oldrel, newrel): + r = requests.get(newrel) + new = r.text + with open(oldrel, "rb") as f: + old = + + oldtime = getTime(getDate(old)) + newtime = getTime(getDate(new)) + if newtime > oldtime: + notice("Update available") + newhashes = parseRel(new) + oldhashes = parseRel(old) + changes = dictCompare(newhashes, oldhashes) + # k = pkg name, v = sha256 + return changes + + +#relmap = compareRel("../spool/dists/jessie/updates/Release", "") +#print relmap +#for k,v in relmap.iteritems(): +# print(k) diff --git a/lib/ b/lib/ @@ -0,0 +1,33 @@ +#!/usr/bin/env python +# copyright (c) 2017 - Ivan J. <> +# see LICENSE file for copyright and license details + +import config + +def crawl(): + paths = {} + for i in range(0, len(config.repos)): + repo = config.repos[i]["name"] + basepath = config.repos[i]["dists"] + sts = [] + for j in config.suites: + for k in config.suites[j]: + if config.repos[i]["aliases"] == True: + if repo in config.aliases: + try: + suite = config.aliases[repo][k] + except: + if config.repos[i]["skipmissing"] == True: + continue + else: + suite = k + else: + suite = k + skips = [ "jessie-security", "ascii-security" ] ## XXX: HACK: + if repo == "DEBIAN" and suite in skips: + continue + sts.append(suite) + paths[repo] = sts + return paths + +#print(crawl()) diff --git a/lib/ b/lib/ @@ -0,0 +1,21 @@ +#!/usr/bin/env python +# copyright (c) 2017 - Ivan J. <> +# see LICENSE file for copyright and license details + +import sys + +def die(msg): + print("\033[1;31m[E] %s\033[0m" % msg) + sys.exit(1) + +def notice(msg): + print("\033[1;32m(*) %s\033[0m" % msg) + return + +def warn(msg): + print("\033[1;33m[W] %s\033[0m" % msg) + return + +def cleanexit(): + notice("exiting cleanly...") + sys.exit(0) diff --git a/lib/ b/lib/ @@ -0,0 +1,26 @@ +#!/usr/bin/env python +# copyright (c) 2017 - Ivan J. <> +# see LICENSE file for copyright and license details + +import requests + +import config +from log import die, notice, warn, cleanexit + + +def download(url, path): + print("\tdownloading: %s\n\tto: %s" % (url, path)) + r = requests.get(url, stream=True) + if r.status_code == 404: + warn("not found!") + return + elif r.status_code != 200: + die("fail!") + + with open(path, "wb") as f: + for chunk in r.iter_content(chunk_size=1024): # XXX: should be more on gbit servers + if chunk: + f.write(chunk) + #f.flush() + print("\033[1;32m . done\033[0m") + return