bug#34565: ungoogled-chromium contains Widevine DRM

Marius Bakke wrote: > not present in the Guix source. Please keep in mind I was discussing upstream Chromium in that piece. It's also not an exhaustive list. > I cannot find these images: grepping for CC-BY-NC-SA or 'Creative > Commons' did not aid.  Did you record the absolute paths to these > f

bug#34565: ungoogled-chromium contains Widevine DRM

On Wed, 2019-02-20 at 22:49 +0100, Ricardo Wurmus wrote: > If it does after all contain objectionable files please point them > out so that we can remove them ASAP. That was done earlier in the thread. It might also be interesting to try building with enable_widevine=true. In the context of the F

bug#34565: ungoogled-chromium contains Widevine DRM

Jason Self wrote: > I should probably add on that this position comes from my interaction > with the FSF in 2010: When LibreWRT was founded in 2010 (before it > later merged into libreCMC) we submitted a similar question to the > FSF,as to if it was sufficient for the LibreWRT build sc

bug#34565: ungoogled-chromium contains Widevine DRM

Leo Famulari wrote: > To clarify this general point about Guix for anyone who is reading > along, as a matter of policy the end user does not receive non-free > source code from Guix. Right; the source is downloaded from commondatastorage.googleapis.com but that is a technicality. What I'm saying

bug#34565: ungoogled-chromium contains Widevine DRM

> should not be hidden/removed after the fact by asking the user to run > a clean-up program after downloading the source, even if that has > been automated by the package manager. What is sent to the end user > to compile should itself be 100% free software and FSDG compliant > from the beginning.

bug#34565: ungoogled-chromium contains Widevine DRM

A different but related matter is the build process itself. I understand this is not exactly related to the DRM matter but it does seem similiar. I can open another bug over this if needed. I have recently submitted upstream's Chromium 73.0.3683.45 into my FOSSology instance for analysis. Actually,

bug#34565: ungoogled-chromium contains Widevine DRM

Based on http://issues.guix.info/issue/28004#2 it is disabled at build time; but not removed. The person said they thought this was FSDG compliant but a reading of "the distro must contain no DRM" from the FSDG could be taken to mean the distro still "contains" it, since it's still within the sourc

bug#34565: ungoogled-chromium contains Widevine DRM

On Tue, 2019-02-19 at 02:06 -0500, Leo Famulari wrote: Why do you think this is the case? We know Chromium comes with it. Have you looked through ungoogled- chromium to see where it's being deleted? signature.asc Description: This is a digitally signed message part

bug#34565: ungoogled-chromium contains Widevine DRM

Package: guix Unless I am mistaken, ungoogled-chromium is not removing Widevine DRM from upstream Chromium. Guix should remove that if upstream won't, as I believe this goes against "the distro must contain no DRM..." in the FSDG.

bug#25551: Upstart Init System

The guix docs in [0] have a small bug of omission for upstart. After doing: # ln -s ~root/.guix-profile/lib/upstart/system/guix- daemon.conf /etc/init/ you should then do: initctl reload-configuration Otherwise the next part (start guix-daemon) fails saying it's not a service upstart knows about

bug#18571: dmesg please

Oops, forgot to reply to the bug: It would be interesting to know if you continue to have problems with the new version of eudev that was just added. signature.asc Description: PGP signature

bug#18571: dmesg please

I'd love to see some output from the boot process, like a dmesg or something. Perhaps it will help provide some clues.

bug#18581: IceCat fails to build on i686 and needs security updates

Mark H Weaver said: > I also asked on #parabola to find out how they deal with this issue. > Apparently their IceCat is also old and unpatched, but they have > scripts to modify Debian's Iceweasel to comply with the FSDG here: > > https://projects.parabola.nu/abslibre.git/tree/libre/iceweasel > >

bug#14851: linux-libre-3.3.8-gnu disappeared

My understanding is that the change from gnu to gnu1 is the result of changes that were needed to the deblobbing. Specifically to allow the loading of the firmware used by ath9k-htc, now that it's free [0]... i.e. 3.3.8-gnu and 3.3.8-gnu1 aren't the same source code. [0] https://www.fsf.org/news/r

Re: Coming back from ELS

Ludovic Courtès said: > Perhaps we could mirror the latter on audio-video.gnu.org And what sort of license do you want to attach to your talk?

Re: New to Guix

Ludovic Courtès said: > Exactly. We package only free software, as per the broad definition > that can be found at . May I also suggest that, if there is an intention to make a free distro, this following the guidelines in this might also be appropriat

Re: A logo

Ludovic Courtès wrote .. > Should we do it differently? Ah, you're referring to the "Use of Graphics" section in the stylesheet [0]. That's actually referring to main graphics page [1] although this is fine too. Adding it to the GNU Art Gallery might be a good thing too. I'll make sure that gets

Re: A logo

> Can we ask the GNU webmasters? > > I think there’s one lurking here. Jason? :-) > > Ludo’. Yeah, I think it's better to the left as well. Assuming that's the decision... it's currently in an href tag and it doesn't really need to be. I'm also assuming that the right margin between the logo an

Re: A logo

Nikita Karetnikov decreed: > I created a new version. I like this. > What license should be used? Maybe the same as Guix itself?

Re: To-do lists

Ludovic Courtès wrote .. > Perhaps we should ask savannah-hackers for a secondary Git repo? I don't suppose there's any harm in that, except that it means using Git but I'll go be quiet now.

Re: To-do lists

Ludovic Courtès wrote .. > Another option would be to have a simple Org-mode file in a repo hosted > on hydra.gnu.org (say), but that means that everyone would need to have > an SSH account on that machine (unless we can use a single SSH account > for everyone who needs to access the repo?). > > S

Re: Distro name

Dmitri Paduchikh wrote .. > For 30 years "GNU" has acquired much broader meaning than just a > distro. > You will have to differentiate distro name from this broader meaning > constantly qualifying that it is Guix distro which you are talking > about. And it will be harder to search in Google. T

Re: Distro name

Ludovic Courtès said: > The problem is that “GNU” is (supposedly) synonym for GNU/Hurd, or > at least for the operating system. > I think it makes sense to distinguish the OS from the distro, no? Hmm. It might make sense to differentiate when a third party is involved, but not when the GNU Proje

Re: Distro name

Why not call the distro "GNU"? :) After almost 30 years it's about time.

Re: Add GNU fdisk

Ludovic Courtès said: > Yes, I’ve been wondering too. The thing is, while most are purely > declarative like this, some, like those in base.scm, are trickier > and definitely copyrightable. In base.scm, the composition of > packages in the bootstrap phase may also be copyrightable in itself. I s

Re: Add GNU fdisk

Nikita Karetnikov said: > Add a copyright notice. I left it out because as a series of facts (package name, version, URL, hash, dependencies, etc.) I'm not sure that these files are even copyrightable to begin with. "When there is only one way to express an idea or function, then everyone is free

Add GNU fdisk

I hope that I've done this correctly. diff --git a/Makefile.am b/Makefile.am index b57e7db..d5a4111 100644 --- a/Makefile.am +++ b/Makefile.am @@ -51,6 +51,7 @@ MODULES = \ distro/packages/cpio.scm \ distro/packages/ddrescue.scm \ distro/packages/ed.scm \ + distro/packages/fdisk