-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
We have a rather sizable backlog of issues around the PureBrowser:
https://tracker.pureos.net/project/board/1/
I point this out not as a criticism of Jonas, the PureBrowser
maintainer, but to highlight that we do not have a clear, distilled
policy document that might mitigate some of the issues in the backlog.
One example is this issue: https://tracker.pureos.net/T699 That issue
comes from a video of PureOS which makes some inaccurate claims. The
video was linked in our bug tracker and I went through the video and
pulled out the claims so that they can be refuted, T699 tracks one such
claim of not having httpseverywhere enabled per default.
Having a policy for an issue like this would allow someone to quickly
go to our policy, quote it in the issue tracker and/or demonstrate that
in fact we do have httpseverywhere installed, and then close the bug
which I feel is a positive outcome. As it stands now, we have a lot of
issues that seem to attract a lot of commentary but little change is
effecutated. For me the point of an issue tracker is to track the
progress of the issue to the point where it is no longer an issue and
it is closed. Is this a shared view from folks on this list?
Regards,
jeremiah
-----BEGIN PGP SIGNATURE-----
iQGzBAEBCgAdFiEEBkkHqXr+u7OUqMKseFgrT+6RsjkFAlxm9YQACgkQeFgrT+6R
sjnVagv+L0v1WkdLZ3jL2NoZbJr8ROE2/SPUyBe67chr1v1dOJIyyxcw9/Ol1FGU
dztk+/XwKri9SHlV9lP7lTim/RxPbZ5wxVPQf+S3n8KDNnOOBdpRbo0xRYd/qqTM
aIeYrfZTwmJcK+cszrr8Zpse1YUaB6RgMvj/0XFHRlbGVvUCXeYafxomtsAz4Ron
huz57a50lqXgOP0hQ4mYp3mCvPOJZQokTnNVJon5oifNbGf7+Ex/qW68B9/5aVoU
I7TCY3W2TT26RnKxIHMKOHMOkmidWt+DRxh7QCxS1OMkhf+4KxDGboyRRDUBGH1/
IJu7XQFCwQ+bbtWT2ZSRqxgnPxaPgjhIt3ypGOBiBOWDX/f8Wrdq0I+RsS/boIGS
A26CGs47NTEU/C4LActM3Sg+IvS7+r2LHr4USgw/Zxyn7lvO1EJ/332whA+ZAsvg
XXQOc1PznOrIovUZJsTVoReQbOPIS/p9W4CM0bBFCN0R/JiuT57eBKEzA8+/EKUE
T349zjsC
=a8Ly
-----END PGP SIGNATURE-----
Am Mi., 6. März 2019 um 21:38 Uhr schrieb Jeremiah C. Foster
<jeremiah.foster(a)puri.sm>:
>
> Hi,
>
> I've added a firmware updater package to the repos, it looks like it is
> still stuck in landing though it is hard to say since I can't seem to
> find it.
The package is likely the one stuck in NEW - I rejected it a few days
ago, but maybe you haven't received an email about that. I kicked the
system again, as there were some log messages on mails not being able
to be sent.
In any case, I sent you this message about the package:
------8<------
Hi!
I am sorry but I have to reject the package at its current state:
* It has a Debian revision number (-1) but does not exist in Debian.
Uploads to PureOS must follow the PureOS versioning rules,
otherwise we break compatibility with Debian. See
https://tracker.pureos.net/w/development/packaging_overview/#version-numbers
for details.
* The binary package is in an unknown section. I can not add
overrides for the package unless you set a proper section.
* The changelog contains the default "new package" boilerplate, it
would be neat to have a slightly more descriptive message there.
Cheers,
Matthias
------>8------
Only the first points are actually issues which made me reject the
upload. Packages which introduce new binary packages or source
packages to PureOS and therefore require override changes always end
up in NEW for manual review, and you should get an email about that
event as well.
You can also take a look at what is in NEW via this (realtively
hidden) URL: https://master.pureos.net/raw/web/new.html
If you ever wonder on what is going on with the archive or packages in
it, I can almost guarantee that the answer exists on master.pureos.net
somewhere :-)
> I've asked for a login from the sys folks so I can look around
> in the repos. I'd love it if someone (Matthias?) were to let me know
> how to ensure that packages get picked up - seems like a manual process
> at the moment and there are lots of packages coming from the L5 phone
> folks so this doesn't really scale well.
It's fully automated. Only packages that go through new need an extra
review step.
> Also, I read with interest this discussion on how folks are moving away
> from Discourse back to mailing lists (largely because they're
> asynchronous).
> https://lwn.net/ml/fedora-council-discuss/CAEg-Je-wUDS+RAvS-8v4Qpu+GeiWv0-w…
That is indeed interesting - I always found Discourse a bit confusing
and hard to keep track of discussions with it, but I also never
actually gave it a fair chance (so far I didn't participate in a
project that was exclusively using Discourse for communication).
Cheers,
Matthias
Hi,
I've added a firmware updater package to the repos, it looks like it is
still stuck in landing though it is hard to say since I can't seem to
find it. I've asked for a login from the sys folks so I can look around
in the repos. I'd love it if someone (Matthias?) were to let me know
how to ensure that packages get picked up - seems like a manual process
at the moment and there are lots of packages coming from the L5 phone
folks so this doesn't really scale well.
Also, I read with interest this discussion on how folks are moving away
from Discourse back to mailing lists (largely because they're
asynchronous).
https://lwn.net/ml/fedora-council-discuss/CAEg-Je-wUDS+RAvS-8v4Qpu+GeiWv0-w…
Regards,
Jeremiah
Hi Jeremiah,
> > You mentioned to me «en passant» recently that you had built ISO
> > images of PureOS. I was wondering whether you had documented the
> > process for doing this yet?
>
> I have not documented this yet. I have been merely building packages so
> far, I have every intention of building images. So far my approach is
> to follow whatever info I can get from Matthias and use that
> information to build up the wiki. At the moment I cannot find the
> information on building images on the wiki, but I'm determined to find
> or create it.
Great stuff! Any progress on this? :)
Best wishes,
--
Chris Lamb
https://puri.sm
Hi Jeremiah et al.,
You mentioned to me «en passant» recently that you had built ISO
images of PureOS. I was wondering whether you had documented the
process for doing this yet?
(My motivation is to push forward on reproducible builds of said
images as discussed.)
Best wishes,
--
Chris Lamb
https://puri.sm
Hi Jeremiah,
Thanks for your reply. :) I don't disagree with anything specific in
your mail but think we should just briefly pause and zoom out here:
> > > Whilst extremely kind of them, how will this work for our users?
>
> For power users we can simply […]
>
> > Do you mean how do we enable our users to easily take advantage of
> > the mirrors? E.g. not having to edit source.list.d/ by hand?
>
> Ideally the 'Software' tool from GNOME might be a good candidate [..]
>
> > > Ask them to alter their sources.list? Are we going to commit to
> > > providing a CDN of some description?
>
> I intend to speak to […]
So, again, these are all very sensible replies & solutions and
furthermore I'm not at all against the conceptual idea of a mirror,
but I am just wondering whether introducing such infrastructure (with
all the inherent technical and support overheads) should appear to be
so high on our priority list right now? :)
Best wishes,
--
Chris Lamb
https://puri.sm
Jeremiah wrote:
> There are some folks who're will to mirror our PureOS distro which is
> very generous of them.
Alas, I fear this is a bigger question that just rsync daemon
settings. :)
Whilst extremely kind of them, how will this work for our users?
Ask them to alter their sources.list? Are we going to commit to
providing a CDN of some description?
Even a round-robin DNS solution has issues in that we have no
immediate, insight or control over whether any "non-official"
mirror is up-to-date, something obviously important from a user
point of view.
Thoughts?
Best wishes,
--
Chris Lamb
https://puri.sm
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
There are some folks who're will to mirror our PureOS distro which is
very generous of them. One of them, linux.pizza (
https://mirror.linux.pizza/) recommends we use rsync to support
mirrors. There is another potential mirror in the US who'll work with
rsync too.
What are the recommended locations to point our rsync daemon at so that
other sites might mirror our repos? This is what they mirror for
Debian; https://mirror.linux.pizza/debian/
Regards,
Jeremiah
-----BEGIN PGP SIGNATURE-----
iQGzBAEBCgAdFiEEBkkHqXr+u7OUqMKseFgrT+6RsjkFAlxSHH0ACgkQeFgrT+6R
sjnjBAwA26y8DR9JURhTJWluuq/LfrfvnhwbMoG0cCsU0WLNCNj8iafTrw2an7ys
e+yyHyb/Ysv10uqKObrUpehvJEUmV6HIQtaCDHrj1jzkDfVXVKG/ESfkKgqhB1KH
H8//w6hqjTpA4zKAVCi/8qF1LvhXkF7ys6eBl5vVM6cR000n29UVdxCwOM4lrYvp
62TEHN6hkEB+Vib58FGkucs0bBnQ5EJIa88wyb83h2FiUQnbYGESwje4k1N8bEAX
Lhs0/KZwQtcDU9ZCxwI6wVDm9tYrfwki76O7Fw0qymwwwqLAKhXxUoFMnY3fizId
M3MWIhsRnvW1Sl8E1zU1PrIUT67lSvWu11Ab1fKrDV7GlVkU9wiZXt2teQE4yy7d
0kvE//ZRWIEM0u/S/I4saLFBRCW03+gWdW1jgZqSkjGXfyBlXL1ZHtSIvp92WJVp
1dq5svUKouBpu+obk3/LlDLEH77yP0MgATXa3iPXmYPb8UPTBOyyA0gJMqksffDC
kK6dLQT9
=51Sb
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On Tue, 2019-01-29 at 23:27 +0100, Matthias Klumpp wrote:
> Am Di., 29. Jan. 2019 um 22:22 Uhr schrieb Jeremiah C. Foster
> <jeremiah.foster(a)puri.sm>:
> > [...]
> > Checksums match but it fails to boot. Message is;
> > firmware: failed to load i915/skl_dmc_ver1_27.bin (-2)
> > firmware_class: See https://wiki.debian.org/Firmware for
> > imformation
> > about missing firmware.
> >
> > rm: can't remove '/root/var/crash/crash.init': No such file or
> > directory
>
> All of these are not hard errors. The first issue is just missing
> firmware, the second ones are from us not using any crash reporter in
> PureOS and casper still having some code for that (the messages are
> harmless though).
> Which virtualization solution are you using?
I'm booting on a Librem13 v3.
> On real metal, like the Librems, this issue never appeared though. If
> the issue stems from a Librem, we need to look into what's causing it
> (try removing quiet splash from the kernel command-line, if it boots
> then, it's an indicator Plymouth is to blame).
In the end I was able to install. I tried three times, first time
failed, the second time worked with failsafe, the third time worked
with the regular installation.
Where would I change the command-line? I suppose I need to edit the
image I'm booting from, but where? In grub.cfg?
Regards,
Jeremiah
-----BEGIN PGP SIGNATURE-----
iQGzBAEBCgAdFiEEBkkHqXr+u7OUqMKseFgrT+6RsjkFAlxSEP8ACgkQeFgrT+6R
sjnLegv/WjBzJhzWWj8FYMgRtEZdoMVI80uIH4aCcQMdgGmbvNx7PREJFhJEn6JY
rRnaG2t5AWTM7GK3+DMx4G2AXzKMVHSZxWdoornEcvT5vfKo44FLZdEBvoVA5eQg
53uIG6AhjzlPm0b4QmMhvgRmFC4iGzaMFWKTV+TM/60/XmXA03URyrXC0DQitT4C
UoRw+0FdVNx0iJqjfu0zMKgkDrUl1kLZ7r0fqBq1xu/Qlrpo6ZAmAehsd8YrqxaS
lyiNEkvKUXHrTmiJPF7CDWsGwgVhloZVXAFo7kTZajJeplD9CRb2JXxGoUpnAXkA
00NutP9U0VP8UtHVklEymcSto9zB8SdA4Bk6a4fBnuZd8YHt3k9MCxem5z0Ep4m8
LaCD+R4noLToZaKSjJVV81Jd1iqQo6XsSJ7xH75ORL8qCAMQCuTwhBp5kT4LNzyI
mmABVwhWsAURDJ0sTAz1YRYi79jRuc3m/KI2TLcfxOLGM9HyWTN6zJJSORSSK/2l
vgZqVqzT
=uqeo
-----END PGP SIGNATURE-----
Hey,
> I think I just inferred a "I need this info as soon as possible
> since it blocks my work" from the ping
Thanks for the feedback; I can relate to that point of view.
> I hope you didn't interpret my statement as rude, I seriously thought
> I missed some information/request to do something in the mails.
Heh, but if there was something to do I would have … *evil grin
spreads slowly over his face* … used the issue tracker!
Thanks. :)
Best wishes,
--
Chris Lamb
https://puri.sm
