<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><div>I want to unsubscribe.</div><div><br></div><div>Sorry but I use Windows 10.</div><div><br></div><div>Thanks.</div><div><br></div><div>Best regards</div><div><br></div><div>David Neil Kristensen<br><br></div><div>> From: ubuntu-studio-devel-request@lists.ubuntu.com<br>> Subject: ubuntu-studio-devel Digest, Vol 101, Issue 50<br>> To: ubuntu-studio-devel@lists.ubuntu.com<br>> Date: Tue, 22 Sep 2015 12:00:25 +0000<br>> <br>> Send ubuntu-studio-devel mailing list submissions to<br>> ubuntu-studio-devel@lists.ubuntu.com<br>> <br>> To subscribe or unsubscribe via the World Wide Web, visit<br>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel<br>> or, via email, send a message with subject or body 'help' to<br>> ubuntu-studio-devel-request@lists.ubuntu.com<br>> <br>> You can reach the person managing the list at<br>> ubuntu-studio-devel-owner@lists.ubuntu.com<br>> <br>> When replying, please edit your Subject line so it is more specific<br>> than "Re: Contents of ubuntu-studio-devel digest..."<br>> <br>> <br>> Today's Topics:<br>> <br>> 1. Re: Artwork license (lukefromdc@hushmail.com)<br>> 2. Artwork license (Mike Holstein)<br>> 3. Re: ISO breakage (Kaj Ailomaa)<br>> 4. Re: ISO breakage (Kaj Ailomaa)<br>> 5. Re: ISO breakage (Kaj Ailomaa)<br>> <br>> <br>> ----------------------------------------------------------------------<br>> <br>> Message: 1<br>> Date: Mon, 21 Sep 2015 18:05:42 -0400<br>> From: lukefromdc@hushmail.com<br>> To: "Ubuntu Studio Development & Technical Discussion"<br>> <ubuntu-studio-devel@lists.ubuntu.com><br>> Subject: Re: [ubuntu-studio-devel] Artwork license<br>> Message-ID: <20150921220542.592C0200DA@smtp.hushmail.com><br>> Content-Type: text/plain; charset="UTF-8"<br>> <br>> That's a good point. Consider this scenario: People put their names on everything.<br>> and the software is used by insurgents against a repressive regime. Unable to catch<br>> the insurgents, the regime in question simply goes after any and all persons whose <br>> names can be tied to the work, copyright holders of the tools included.<br>> <br>> Here in the US, if someone is arrested with a cell phone, every person whose phone<br>> number is in that phone is potentially placed at risk if the case is "hot" enough. In <br>> addition, metadata attached to finished work can be used to tie one piece of work<br>> to another. That plus concealing the camera I use is why all jpegs I publish shot from<br>> my camera are stripped of their metadata. For years I have encouraged the anonymization<br>> of such things: if you always strip metadata, you won't forget to do so when it really <br>> counts, like when a police shooting triggers an uprising and police hunt independent<br>> cameramen and videographers for "evidence." <br>> <br>> It is also a common practice here that when underground activists put "points on the <br>> board" against something like logging or gas fracking, aboveground activists whose <br>> names are known are harassed. <br>> <br>> There is a lot of media published by those who must conceal their true names! I don't<br>> permit my "legal" name to cross the Internet, and release the news media pieces I <br>> write to public domain with no names on photos or videos other than those of other<br>> activists who want their names used and provided 3ed party media.<br>> <br>> <br>> On 9/21/2015 at 5:29 AM, "Ralf Mardorf" <ralf.mardorf@alice-dsl.net> wrote:<br>> ><br>> >On Mon, 21 Sep 2015 09:28:15 +0200, ttoine wrote:<br>> >>why not the latest CC-by-sa 4.0 ?<br>> ><br>> >Hi,<br>> ><br>> >I don't want to read texts I'm anyway unable to understand, because<br>> >they are written in lawyer language, instead I prefer to read how <br>> >to<br>> >make a svg file look equal, what ever application is used to open <br>> >the<br>> >svg file.<br>> >Assumed I should use the Ubuntu Studio logo from the<br>> >ubuntustudio-icon-theme package, can I update the license?<br>> ><br>> >$ dpkg -l ubuntustudio-icon-theme|tail -n1|awk '{print $2" "$3}'<br>> >ubuntustudio-icon-theme 0.16<br>> >$ grep CC-BY-SA /usr/share/doc/ubuntustudio-icon-theme/copyright<br>> >License: CC-BY-SA-2.5<br>> ><br>> >[ironic] If somebody should misuse a Creative Commons spray paint<br>> >stencils, would the police in some countries knock on the doors of <br>> >the<br>> >copyright holders? [/ironic]<br>> ><br>> >Sharing art was much easier in the punk-rocking 80s. Still today I<br>> >would make my own art public without a license.<br>> ><br>> >The other question was about meta data add by applications. I <br>> >didn't<br>> >miss a law that nowadays enforces us to mention the used tools to<br>> >create a jpg, png, svg?<br>> ><br>> >For art I made in the past I never mentioned Canon AE-1 Program,<br>> >DeVilbiss Aerograph "Super 63", Yamaha DX7, Yamaha SPX90II, Fender<br>> >150XL or what ever else was used.<br>> ><br>> >A wallpaper I already made without the Ubuntu Studio logo includes<br>> ><br>> >$ exiftool Pictures/moonstudio_wallpaper_1.png | grep Comment<br>> >Comment : Created with GIMP<br>> ><br>> >because it's a default for GIMP. Is it just craving for <br>> >recognition by<br>> >the coders or do they help to fulfil laws?<br>> ><br>> >I never mentioned, if I used a Da Vinci Kolinsky or a No-name<br>> >Kolinsky or if I used water-colours from Schmincke or not.<br>> ><br>> >My understanding is, that comments mentioning the software that was<br>> >used can be removed. Namespace data for svg sometimes perhaps can't<br>> >be removed, but I guess it's allowed to rename "Adobe" to "foo" and<br>> >"Inkscape" to "bar".<br>> ><br>> >I'm serious! I've got concerns against all that sharing of data.<br>> >Making art I don't have secret recipes, I'm willing to share all<br>> >information, but I dislike to include advertising and privacy data <br>> >to a<br>> >file of a picture or song.<br>> ><br>> >Regards,<br>> >Ralf<br>> ><br>> >-- <br>> >ubuntu-studio-devel mailing list<br>> >ubuntu-studio-devel@lists.ubuntu.com<br>> >Modify settings or unsubscribe at: <br>> >https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel<br>> <br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 2<br>> Date: Mon, 21 Sep 2015 18:19:01 -0400<br>> From: Mike Holstein <mikeh789@gmail.com><br>> To: "Ubuntu Studio Development & Technical Discussion"<br>> <ubuntu-studio-devel@lists.ubuntu.com><br>> Subject: [ubuntu-studio-devel] Artwork license<br>> Message-ID:<br>> <CADmgLayPBfc2iM0r8+wLb-V98zhYrE5jJ=pFDyfagC-g-_0eCQ@mail.gmail.com><br>> Content-Type: text/plain; charset="utf-8"<br>> <br>> On Monday, September 21, 2015, Ralf Mardorf <ralf.mardorf@alice-dsl.net<br>> <javascript:_e(%7B%7D,'cvml','ralf.mardorf@alice-dsl.net');>> wrote:<br>> <br>> > On Mon, 21 Sep 2015 09:28:15 +0200, ttoine wrote:<br>> > >why not the latest CC-by-sa 4.0 ?<br>> ><br>> > Hi,<br>> ><br>> > I don't want to read texts I'm anyway unable to understand, because<br>> > they are written in lawyer language, instead I prefer to read how to<br>> > make a svg file look equal, what ever application is used to open the<br>> > svg file.<br>> > Assumed I should use the Ubuntu Studio logo from the<br>> > ubuntustudio-icon-theme package, can I update the license?<br>> ><br>> > $ dpkg -l ubuntustudio-icon-theme|tail -n1|awk '{print $2" "$3}'<br>> > ubuntustudio-icon-theme 0.16<br>> > $ grep CC-BY-SA /usr/share/doc/ubuntustudio-icon-theme/copyright<br>> > License: CC-BY-SA-2.5<br>> ><br>> > [ironic] If somebody should misuse a Creative Commons spray paint<br>> > stencils, would the police in some countries knock on the doors of the<br>> > copyright holders? [/ironic]<br>> ><br>> > Sharing art was much easier in the punk-rocking 80s. Still today I<br>> > would make my own art public without a license.<br>> ><br>> > The other question was about meta data add by applications. I didn't<br>> > miss a law that nowadays enforces us to mention the used tools to<br>> > create a jpg, png, svg?<br>> ><br>> > For art I made in the past I never mentioned Canon AE-1 Program,<br>> > DeVilbiss Aerograph "Super 63", Yamaha DX7, Yamaha SPX90II, Fender<br>> > 150XL or what ever else was used.<br>> ><br>> > A wallpaper I already made without the Ubuntu Studio logo includes<br>> ><br>> > $ exiftool Pictures/moonstudio_wallpaper_1.png | grep Comment<br>> > Comment : Created with GIMP<br>> ><br>> > because it's a default for GIMP. Is it just craving for recognition by<br>> > the coders or do they help to fulfil laws?<br>> ><br>> > I never mentioned, if I used a Da Vinci Kolinsky or a No-name<br>> > Kolinsky or if I used water-colours from Schmincke or not.<br>> ><br>> > My understanding is, that comments mentioning the software that was<br>> > used can be removed. Namespace data for svg sometimes perhaps can't<br>> > be removed, but I guess it's allowed to rename "Adobe" to "foo" and<br>> > "Inkscape" to "bar".<br>> ><br>> > I'm serious! I've got concerns against all that sharing of data.<br>> <br>> <br>> No one will make you share anything. Is that the question? How to make a<br>> file with no meta data? I think, it's safe to assume graphics are created<br>> and/or edited in a graphics manipulation program. Identifying said program<br>> really just does that. It identifies the tool. Advertising for said tool is<br>> a great reason. Maybe the developers of gimp would have more to offer on<br>> the decision to include metadata that identifies the tool. I'm +1 for<br>> leaving that identifying information in by default. I'm sure we can discuss<br>> constructively how to create a file in gimp or Linux, generally, without<br>> said identifiers.<br>> <br>> <br>> <br>> > Making art I don't have secret recipes, I'm willing to share all<br>> > information, but I dislike to include advertising and privacy data to a<br>> > file of a picture or song.<br>> ><br>> > Regards,<br>> > Ralf<br>> ><br>> > --<br>> > ubuntu-studio-devel mailing list<br>> > ubuntu-studio-devel@lists.ubuntu.com<br>> > Modify settings or unsubscribe at:<br>> > https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel<br>> ><br>> <br>> <br>> -- <br>> MH<br>> <br>> likethecow.com<br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <https://lists.ubuntu.com/archives/ubuntu-studio-devel/attachments/20150921/d83a46b8/attachment-0001.html><br>> <br>> ------------------------------<br>> <br>> Message: 3<br>> Date: Tue, 22 Sep 2015 10:15:16 +0200<br>> From: Kaj Ailomaa <zequence@mousike.me><br>> To: ubuntu-studio-devel@lists.ubuntu.com<br>> Subject: Re: [ubuntu-studio-devel] ISO breakage<br>> Message-ID:<br>> <1442909716.2427714.390195849.3B744A43@webmail.messagingengine.com><br>> Content-Type: text/plain<br>> <br>> On Fri, Sep 18, 2015, at 09:20 AM, Kaj Ailomaa wrote:<br>> > On Thu, Sep 17, 2015, at 11:44 PM, Ross Gammon wrote:<br>> > > On 09/17/2015 09:48 PM, Len Ovens wrote:<br>> > > > Hmm, our ISO is not building. Problem seems to be:<br>> > > > ------------------8<-------------------<br>> > > > The following packages have unmet dependencies:<br>> > > > python-enum : Conflicts: python-enum34 but 1.0.4-2 is to be installed<br>> > > > E: Unable to correct problems, you have held broken packages.<br>> > > > -------------------8<------------------<br>> > > > <br>> > <br>> > This is usually a problem with a version mismatch.<br>> > <br>> <br>> <br>> Seems python-enum was made to conflict with python-enum34. This due to<br>> python-enum not being available to laditools, if python-enum34 is also<br>> installed. Not really a fix, but the situation renders all ladi tools<br>> unusable, so I'm temporarily removing Gladish from our seeds so our ISOs<br>> can build.<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 4<br>> Date: Tue, 22 Sep 2015 10:16:03 +0200<br>> From: Kaj Ailomaa <zequence@mousike.me><br>> To: ubuntu-studio-devel@lists.ubuntu.com<br>> Subject: Re: [ubuntu-studio-devel] ISO breakage<br>> Message-ID:<br>> <1442909763.2427990.390197121.528A40BD@webmail.messagingengine.com><br>> Content-Type: text/plain<br>> <br>> Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795444<br>> New LP bug:<br>> https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1498345<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 5<br>> Date: Tue, 22 Sep 2015 12:48:35 +0200<br>> From: Kaj Ailomaa <zequence@mousike.me><br>> To: ubuntu-studio-devel@lists.ubuntu.com<br>> Subject: Re: [ubuntu-studio-devel] ISO breakage<br>> Message-ID:<br>> <1442918915.3136280.390304553.6AF080C7@webmail.messagingengine.com><br>> Content-Type: text/plain<br>> <br>> On Thu, Sep 17, 2015, at 11:44 PM, Ross Gammon wrote:<br>> > The "conflicts" was added very recently:<br>> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795444<br>> > <br>> > I am not sure how the black listing works, but certainly enum & enum34<br>> > cannot live together.<br>> > <br>> > I suppose python-enum34 has to be kept, as there are quite few reverse<br>> > dependencies. Bit of a shame though. We could always ask Alessio (Debian<br>> > Multimedia Team) who seems to have forked laditools if he believes<br>> > laditools could be made to work with enum34?<br>> > <br>> <br>> Ah, sorry. You already were on top of the problem.<br>> <br>> If anyone wants to try to fix this for the sake of reintroducing ladi to<br>> Ubuntu Studio, be my guest.<br>> Either laditools needs to be able to import python-enum, if both<br>> python-enum and python-enum34 are installed at the same time (and the<br>> conflict can then be removed), or as Ross suggests, laditools needs to<br>> be rewritten to support python-enum34.<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> -- <br>> ubuntu-studio-devel mailing list<br>> ubuntu-studio-devel@lists.ubuntu.com<br>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel<br>> <br>> <br>> End of ubuntu-studio-devel Digest, Vol 101, Issue 50<br>> ****************************************************<br></div> </div></body>
</html>