Re: [Reproducible-builds] arm64 reproducible build network
Hi, On Wed, Mar 23, 2016 at 06:40:09PM -0700, Vagrant Cascadian wrote: > There's about US$1200 left. > > To follow through with number of boards in the original proposal, I > should probably get at least 3-4 more boards... or should we branch out > into an arm64 network with the remaining funds? tbm will give us something like 4 cello boards (iirc), but it will take some months as they are only scheduled in the 2nd quarter of 2016. These are to be hosted at Xtaran. For those we will need to get SSDs too, so leaving some funds for that would be useful. And then some company also has offered us (privately to me so far) some moonshot cartriges (which are 8 core, 64gb ram systems, each), but it's also not clear when we get access to them. (The company will host them for us.) Once we get them, we can _probably_ build armel, armhf and arm64 on those, but I might be wrong here. And it might take some time. If/when this moonshot hardware becomes reality your armhf build network will still be useful, as we then can keep it for hw diversity. Until then, I'm not convinced we should invest in arm64 hardware (+testing), but rather improve the armhf setup. long story short: if you think more/different hw is useful in your setup, go and use the funds for it. It might take some more months til we can test arm64 and the armhf build network IMO is still too slow. -- cheers, Holger signature.asc Description: Digital signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] arm64 reproducible build network
On 2016-03-06, Holger Levsen wrote: > On Sonntag, 6. März 2016, Axel Beckert wrote: >> I now wonder if a bunch of Raspberry Pi 3 -- since they have 64-bit >> CPUs (IIRC an Allwinner A53T) -- would make us able to check >> reproducible-builds for Debian arm64, too. > > as far as I know, yes. Though I would want to use some other arm64 boards as > well, to have hardware variety right from the start. ... > I think we'd need 10-12 of such boards for a start, not sure if we still have > Debian funds to buy those (but I almost think so… Vagrant?) - providing we > would find someone interested+able to host these. Would you (Axel) be able > too? There's about US$1200 left. To follow through with number of boards in the original proposal, I should probably get at least 3-4 more boards... or should we branch out into an arm64 network with the remaining funds? If that's the case, I'd probably need someone else to host the boards, though I could proably host some initial experimentation just to get the basic infrastructure set up. I could also experiment with using the arm64 boards but building armhf packages, which seems like an interesting middle-ground. Curious what folks think. Could get a few odroid-c2 for ~$60 with usb-sata adapter, power supply, and case. Mainline linux for similar boards exists... but not for odroid-c2 explicitly. The LeMaker Hikey goes for ~$100+accessories. Limited mainline support exists. I already have one donated by LeMaker for experimenting with. The Pine64 boards are currently going for ~$30 for the 2GB ram variants. Not sure what the timeline on delivery is, though I have a few coming for experimentation. Seems like raspberry PI 3 doesn't yet really support arm64, and only has 1GB of ram. I don't think it's worth considering. Cheap 120GB SSD costs around US$40-50 each. So, you might be able to get 8-10 boards running with the remaining funds... The LeMaker Cello is about ~US$300+accessories, with dual native SATA, and may come with 8GB ram out of the box, upgradable to 32GB or more: http://www.lenovator.com/product/103.html Two to three LeMaker Cello might outperform a network of 8-10 lower spec machines, and probably be a lot easier to maintain. Mainline linux support for similar boards exists... that said, The Cello isn't actually shipping yet (but soon?)... s... live well, vagrant signature.asc Description: PGP signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] Applying to Outreachy to work on Reproducible Builds
Hi Val, On Wed, Mar 23, 2016 at 03:34:33PM -0400, Valerie R Young wrote: > I'm applying to Outreachy (https://www.gnome.org/outreachy/) to work on the > Reproducible Builds project, specifically to improve > test.reproducible-builds.org. Very excited to potential join this project! welcome to the wonderful world of Reproducible builds! ;-) > Here is a rough timeline I've put together based on the work Holger/Lunar > would like to see on the site -- further feedback welcome: I think the timeline is roughly fine, just one thing: Please make sure / be aware that you can test all the things locally, on some system of yours. I'm usually pretty good at merging things and bringing them online rather immediatly but there will be times when I'm not so available and this shouldnt result in you getting stuck. (And you should have a local testbed anyway, to be able to develop+test your code. As its mostly about the webpages, you also dont need jenkins for that nor do you need to be running tests. Just experimenting with the existing reproduicble.db should be fine.) > Timeline: things I'm missing here: - an initial working piece to prove that you understand the setup (eg one of the 4 things I suggested in private mail yesterday) - inclusion of the the 3 other things from those list of 4 :) > Week 5 > - Become intimately familiar with reproducible.db > - Become intimately familiar with test results and project/packaging design > of other projects to record in database > > Week 6 > - Re-design database to add results from other distros to the database > > Week 7 > - Migrate from SQLight to Postgres (with new schema design!) note that you will also need to migrate the data from the old to the new database design. and this should be scripted. (and tested locally…) and it misses creating documentation of the new database scheme! everything else I havent commented on is fine from my side. -- cheers, Holger signature.asc Description: Digital signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Applying to Outreachy to work on Reproducible Builds
Hi all! I'm applying to Outreachy (https://www.gnome.org/outreachy/) to work on the Reproducible Builds project, specifically to improve test.reproducible-builds.org. Very excited to potential join this project! You'll see me on irc getting up to speed and submitting the first commit :) Here is a rough timeline I've put together based on the work Holger/Lunar would like to see on the site -- further feedback welcome: Timeline: Week 1 - Become intimately familiar with the test.reproducible-builds.org - Basic understanding of all projects presently tested - Detailed understanding of site design/map for the Debian project - Detailed understanding results of tests/graphs/purpose and use of site Week 2-4 - Improve UI and UX of tests.reproducible-builds.org for debian - Less intimidating front page for test.reproducible-builds.org with links to all projects - Common navigation on left for dashboards, indexes and package pages (similar to package pages) - Look into templating/CSS - Improve documentation/description of status on each dashboard Week 5 - Become intimately familiar with reproducible.db - Become intimately familiar with test results and project/packaging design of other projects to record in database Week 6 - Re-design database to add results from other distros to the database Week 7 - Migrate from SQLight to Postgres (with new schema design!) Week 8-9 - Update scripts running reproducibility tests for non-Debian projects to record test information to database Week 10-12 - Adapt/extend code which builds Debian's test.reproducibile-builds.org pages to surface results from all projects The rest of my application is attached if you are curious :) see you around, Valerie P.S. Today is my birthday! :D A quick notice: I just learned about Outreach on 20th at libreplanet! Unfortunately, due to the two day time constraint, this application will be submitted on the 22nd partially completed. I will complete the text part of the application by Thursday (the 24th) and submit a contribution to the project (reproducible-builds) by the following Thursday (March 31st). Name: Valerie Ruth Young Do you meet the eligibility requirements outlined at https://wiki.gnome.org/Outreachy#Eligibility (if no, explain why not)? Yes Preferred pronoun (e.g. she, he, they): She E-mail address: spectran...@riseup.net IRC nick: spectranaut Internet presence (e.g. web page, blog, portfolio, GitHub, Twitter, LinkedIn links): https://www.linkedin.com/in/vayoung Location (city, state/province, and country): Boston, MA Education completed or in progress (include university, major/concentration, degree level, and graduation year): Bachelor's degrees in Physics and Computer Science How did you hear about this program? From Jennie Rose Halprin, a previous participant. Are you applying for Google Summer of Code and, if so, with what organization(s)? Nope. Please describe your experience with the organization's product as a user and as a contributor (include the information, as well as a link or an attachment, for the required contribution you made to the project you are interested in here): I've used the Debian operating system for a year, and ubuntu for the three years before that. I'm presently working on an initial contribution with my potential mentors (Holger, Mattia and Lunar) and will update this application as soon as the project has been decided. Please describe your experience with any other FOSS projects as a user and as a contributor: I'm a huge enthusiast of free software, and I contribute regularly by evangelizing. The last half year I co-organized a free software reading group, where we've reading the GPLv3 and other licenses, case law on DRM, and anthropological analysis of free software organizations. I hope Outreachy can be a gateway to developing for free software project as well – up until now, I've only written scripts for research or closed source code for companies! Please describe any relevant projects that you have worked on previously and what knowledge you gained from working on them (include links): For the last two years, I've worked on a web application, the Electronic Medical Record product offered by athenahealth (athenahealth.com). This work has provide me a great deal of experience thinking about usability (a huge concern when writing a tool for doctors to use to document and diagnosis you) and, of course, building a webapp. I've experience with both backend and frontend data modeling and management (javascript backbone.js, perl Moose, Oracle SQL) and frontend web design (HTML, LESS/CSS). This is all relevant to the project of interest, which is making tests.reproducible-builds.org a more useful and usable site for projects interested in achieving reproducible builds – including Debian and beyond. What project(s) are you interested in (these can be in the same or different organizations)? Like mentioned above, I'm interesting in c
Re: [Reproducible-builds] I'd like to help
Hi Scott, welcome to the Debian reproducible builds team! On Wed, Mar 23, 2016 at 02:28:27PM -0400, Scott C. MacCallum wrote: > I'd like to help. I've been using a Unix-like operating system since the > late 90's and I have a lot of experience writing shell scripts, Git, etc. > Building and testing is something that I think I could do without much > help. Where should I start? https://wiki.debian.org/ReproducibleBuilds/Contribute is the canonical starting point if you want to help out. Then I also have just started https://wiki.debian.org/ReproducibleBuilds/Help/h01ger which currently is pretty low on useful pointers but I plan to put more things there in future… To others on this list: other suggestions where/how to help are much welcome! -- cheers, Holger signature.asc Description: Digital signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] I'd like to help
Greetings, I'd like to help. I've been using a Unix-like operating system since the late 90's and I have a lot of experience writing shell scripts, Git, etc. Building and testing is something that I think I could do without much help. Where should I start? Thank you, Scott ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Processed: update
Processing control commands: > retitle -1 "Add option to ignore mtimes" Bug #814057 [src:diffoscope] Add option to ignore mtime and ctime in report Changed Bug title to '"Add option to ignore mtimes"' from 'Add option to ignore mtime and ctime in report' -- 814057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Bug#814057: update
control: retitle -1 "Add option to ignore mtimes" < deki> jfyi, ctimes are ignored since version 50 -- cheers, Holger signature.asc Description: Digital signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] [PATCH] Upstreaming a large amount of patches
Hi, On Wed, Mar 23, 2016 at 12:33:04AM +0100, Reiner Herrmann wrote: > > [https://lists.gnu.org/archive/html/info-gnu/2010-07/msg00023.html] > > > > " * WARNING: Future backward-incompatibility! > > " Wildcards are not documented as returning sorted values, but up to and > > " including this release the results have been sorted and some makefiles > > are > > " apparently depending on that. In the next release of GNU make, for > > " performance reasons, we may remove that sorting. If your makefiles > > " require sorted results from wildcard expansions, use the $(sort ...) > > " function to request it explicitly. > > > > (But the change actually went into 3.82, not a future release; as the > > ChangeLog in the source says: > > > > " 2010-08-13 Paul Smith > > " > > " * NEWS: Accidentally forgot to back out the sorted wildcard > > " enhancement in 3.82, so update NEWS. > > > > -- after it had already been posted to the mailing list as a threat of > > *future* change...) > > > > "for performance reasons", they broke backwards compatibility and > > potentially packages throughout the universe of software development? > > Augh... > > Yes, I also think that this is very unfortunate. > The performance "impact" is only visible in build processes and doesn't > affect end users, and even there it is probably negligible for almost all > packages. > But at the time of the change reproducible builds weren't considered as > that important yet and they probably didn't see any disadvantage in omitting > the sorting. ouch. did someone already reported this to the make upstream developers as a problem for reproducible builds everywhere? > I think the best solution would be to change the default again to let > wildcard sort the lists (it will probably make a bunch of packages > reproducible without having to touch them). And if someone really > needs this bit of extra-performance, a fast-wildcard or unsorted-wildcard > could be added. yup & thanks for bringing this news to us! -- cheers, Holger signature.asc Description: Digital signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] [GSoC 2016] : Application review
Satyam Zode: > >> Official coding period. > >> 3) Week 1 - 2 (May 27 - June 9): > >> - Work on "Allow users to ignore arbitrary differences" part. > >> - Work simultaneously on unreproducible packages. > > > > How much time are you going to give to the community so they can review > > your proposed user interfaces? > > > I think, I will be ready with a design of above by 1st May. After that > till 10th May we can discuss user interfaces because from 11th May I > will have exams so I won't be available for active discussions. If > some things will be remained to discuss then we can always discuss > alongside during a coding period. Mh… I was not expecting you to work during the community bounding period, but it's your call. > >> 4) Week 3 - 4 (June 10 - June 22): > >> - Work on Parallel processing part. > >> - Work simultaneously on unreproducible packages. > > > > This is unlikely to work. Implementing parallel processing requires > > deep focus because it's also about adding missing locks and > > understanding subtle concurrency issues. > > > > How much experience do you have with concurrent programming? > I have good experience with concurrent programming. I have written > many concurrent programs in golang and I believe it'll help me here. > > > I think you underevaluate how hard this is to get right. To the very > > least you shoud be entirely focused on this and not fixing packages at > > the same time. > I understand that this is not going to be a piece of cake for me. I believe it applies to you as well as anyone else. I've been working myself on and off on that code for six months without getting it to a point where it was stable enough to be usable! It's reassuring that you have previous experience in concurrent programing. > However, If we remove fixing of packages from this schedule then I > will get enough time to concentrate on this particular problem. Alright. :) > In my opinion, there must a buffer time in software development > process for any unexpected incidence. Hence, I am planning to keep > this time as a buffer time. What do you think about it ? (Of course, I > will devote this time for community work only). If you feel you need buffer time, then let's call it that way. :) I'd rather have it stated as such than promising stuff you should be doing along the way. -- Lunar.''`. lu...@debian.org: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Премахване и превенция на врастнали и подкожни косми
pfb Vanish и pfb Vanish + Chromabright ™ за премахване и превенция появата на врастнали косми с нови цени! pseudofolliculitis barbae (PFB) е медицинското наименование на варстналите косми в резултат от обезкомяването - достатъчно сериозен и изискващ адекватни действия проблем. pfb Vanish е рол-он серум за премахване и превенция на врастнали и подкожни косми. pfb Vanish предлага нежно и щадящо ексфолиране и отстраняване на врастналите косми pfb Vanish е специална формула с salicylic acid, glycolic acid , екстракт от кората на върба, камфорово масло и млечна киселина pfb Vanish е с видими резултати в рамките на 24-48 часа и се ползва се с препоръката и доверието на специалистите pfb Vanish е иновативен рол – он апликатор (не се разлива по ръцете) и е икономичен за употреба pfb Vanish не дразни кожата и охлажда, не оставя следи по кожата, съдържа повече ексфолоиращи компоненти и опълнително обогатен с билкови екстракти, предлага се във варинат 60 и 120 мл. Вижте продукта тук: http://www.vanishbg.com/ Сега Ви представяме НОВИЯ pfb Vanish + Chromabright ™ (хромабрайт) Иновация - рол-он Флакон, 120 мл + възвръща баланса на пигментацията на кожата за 2 месеца + отстранява враснали косми за 24-48 часа + премахване на черните точки и успокоява при обезкосмяване от всякакъв вид Сега е pfb Vanish е с добавена Chromabright ™ (хромабрайт) - патентована съставка, предназначена за изсветляване на кожата, няма цитотоксичен ефект, не дразни и не предизвиква сенсибилизация (чувствителност). Вижте продукта тук: http://www.vanishbg.com/ · pfb Vanish предотвратява врастването на космите в следствие обезкосмяване чрез : бръснене, кола маска, крем-депилатоaр ,механична или лазерна епилаци и др. Подходящ за употреба и от двата пола, както и при мазна кожа и пре-акне състояния. pfb Vanish рол-он серум с бързо действие и ефективност в рамките на 48 часа! Goodbye Ingrown Hair!™ Кажете сбогом на врастналите косми За контакти и поръчки : http://www.vanishbg.com/Order.aspx WEB http://www.vanishbg.com/ Съгласно Закона за Електронната Търговия ви информираме, че това може да е непоискано търговско съобщение. Вие може да го приемете или отхвърлите. Ние може да сме получили вашия имейл от вас, от ваш партньор или от публичното пространство. Ако не желаете да получавате информация от "pfb Vanish", моля натиснете ТУК и ние ще ви отпишем от списъците ни. Ако сме Ви обезпокоили, моля да ни извините. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] Every LED per cut strips froｍ Wisva
| Dear , Wisva new released ONE LED Per Cut Strip this month, the minimum cutting length is 10mm width. | | | | Features: One LED Per Cut The minimum cutting length is 10mm, every LED per cut. Suitable for more applications. Ideal for DIY. 100LED Per Meter 100 LEDs per meter, high luminous, every 20-22lm per LED. Epistar Lighting Source High quality Epistar 5050 SMD Lighting Source, 3 times brightness as 3528 SMD. Waterproof available IP65/IP66/IP67/IP68 available for strips. | | Looking forward to your reply. |___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
