[PATCH 1/1] v2: Implement clockrdlock / clockwrlock and test

Added implementations of the pthread_rwlock_clockrdlock and the pthread_rwlock_clockwrlock methods to cpukit/posix/src. Both of these methods have been newly added to the POSIX Issue 8 Standard. Added psxrwlock02 test to testsuites/psxtests to test the newly added methods. ---

[PATCH 0/1] v2: Implement clockrdlock / clockwrlock and test

Dr. Joel, Thanks very much for your review! Please see the updated version with pared-down test, check for invalid clock, and check for invalid abstime->tv_nsec. Sincerely, Matt Matt Joyce (1): Added implementations of the pthread_rwlock_clockrdlock and the pthread_rwlock_clockwrl

[PATCH 1/1] Implement clockrdlock / clockwrlock and test

Added implementations of the pthread_rwlock_clockrdlock and the pthread_rwlock_clockwrlock methods to cpukit/posix/src. Both of these methods have been newly added to the POSIX Issue 8 Standard. psxrwlock02 test added to testsuites/psxtests to test the newly added methods. ---

[PATCH 0/1] Implement clockrdlock / clockwrlock and test

Hello, Please find the attached implementions of pthread_rwlock_clockrdlock and pthread_rwlock_clockwrlock, two newly added POSIX Issue 8 Standard methods. Also included is the psxrwlock02 test, which is based on the previously existing test for the rwlock_timed*lock methods. Thank you! Matt

[PATCH 1/1] Added Implementation / tests for pthread_cond_clockwait()

Added implementation of the pthread_cond_clockwait() method to cpukit/posix/src/condclockwait.c. Additional logic added to condwaitsupp.c to implement the new method. Pthread_cond_clockwait() has been added to the Issue 8 POSIX Standard. psxcond03 test added to testsuites/psxtests to test the

[PATCH 0/1] v4: Implementation of Condclockwait and Test

This version contains some formatting fixes from v3. Thank you! Matt Joyce (1): Added Implementation / tests for pthread_cond_clockwait() cpukit/include/rtems/posix/condimpl.h | 9 +- cpukit/posix/src/condclockwait.c | 78 +++ cpukit/posix/src/condtimedwait.c

[PATCH 0/1] v3: Implementation of Condclockwait and Test

! Sincerely, Matt Matt Joyce (1): Added implementation / tests for pthread_cond_clockwait() cpukit/include/rtems/posix/condimpl.h | 9 +- cpukit/posix/src/condclockwait.c | 78 +++ cpukit/posix/src/condtimedwait.c | 3 +- cpukit/posix/src/condwait.c

[PATCH 1/1] v3: Implemention of Condclockwait and Test

Added implementation of the pthread_cond_clockwait() method to cpukit/posix/src/condclockwait.c. Additional logic added to condwaitsupp.c to implement the new method. Pthread_cond_clockwait() has been added to the Issue 8 POSIX Standard. psxcond03 test added to testsuites/psxtests to test the

[PATCH 1/1] v2: Implement Condclockwait and Test

Added implementation of the pthread_cond_clockwait() method to cpukit/posix/src/condclockwait.c. Additional logic added to condwaitsupp.c to implement new method. pthread_cond_clockwait() has been added to the Issue 8 POSIX Standard. psxcond03 test added to testsuites/psxtests to test the newly

[PATCH 0/1] v2: Implement Condclockwait and Test

Dr Joel, Thank you for your feedback! This patch aims to implement your suggested edits. Sincerely, Matt Matt Joyce (1): Added implementation / tests for pthread_cond_clockwait() cpukit/include/rtems/posix/condimpl.h | 7 +- cpukit/posix/src/condclockwait.c | 78

[PATCH 1/1] Implementation / tests for pthread_cond_clockwait()

Added implementation of the pthread_cond_clockwait() method to cpukit/posix/src/condclockwait.c. Additional logic added to condwaitsupp.c to implement new method. pthread_cond_clockwait() has been added to the Issue 8 POSIX Standard. psx17 test added to testsuites/psxtests to test the newly added

[PATCH 0/1] Implementation and Test for pthread_cond_clockwait

by for any feedback. Sincerely, Matt Matt Joyce (1): Added implementation / tests for pthread_cond_clockwait() cpukit/include/rtems/posix/condimpl.h | 1 + cpukit/posix/src/condclockwait.c | 69 +++ cpukit/posix/src/condtimedwait.c | 1 + cpukit/posix/src

[PATCH 1/1] testsuites: added compile tests for new APIs

Added compile only tests for the following POSIX standard APIs: 1) pthread_rwlock_clockrdlock() 2) pthread_rwlock_clockwrlock() 3) pthread_cond_clockwait() 4) pthread_mutex_clocklock() All four were added to Issue 8 POSIX Standard and were added to testsuites/psxtests/psxhdrs/pthread. ---

[PATCH 0/1] testsuites: Add Compile Tests for POSIX Clock APIs

) pthread_cond_clockwait() 2) pthread_mutex_clocklock() 3) pthread_rwlock_clockrdlock() 4) pthread_rwlock_clockwrlock() All four methods are being added to the Issue 8 POSIX Standard. Matt Joyce (2): testsuites: added compile tests for new APIs testsuites: added compile tests for new APIs spec/build/testsuites

[PATCH 2/2] testsuites: added compile tests for new APIs

Added compile only tests for new POSIX standard APIs pthread_cond_clockwait and pthread_mutex_clocklock in testsuites/psxtests/psxhdrs/pthread --- spec/build/testsuites/psxtests/libpsxhdrs.yml | 2 + .../psxhdrs/pthread/pthread_cond_clockwait.c | 54 ++

[PATCH 1/2] testsuites: added compile tests for new APIs

Added compile only tests for new POSIX standard APIs pthread_rwlock_clockrdlock() and pthread_rwlock_clockwrlock() in testsuites/psxtests/psxhdrs/pthread --- spec/build/testsuites/psxtests/libpsxhdrs.yml | 2 + .../pthread/pthread_rwlock_clockrdlock.c | 59 +++

[PATCH 0/2] testsuites: Add Compile Tests for POSIX Clock APIs

Added compile only tests in cpukit/testsuites/psxtests/psxhdrs/pthread for the following APIs: 1) pthread_cond_clockwait() 2) pthread_mutex_clocklock() 3) pthread_rwlock_clockrdlock() 4) pthread_rwlock_clockwrlock() All four methods are being added to the Issue 8 POSIX Standard. Matt Joyce (2

[PATCH 0/1] libc: Added Prototypes for POSIX Clock APIs

Added function prototypes to newlib/libc/include/pthread.h for the following APIs: 1) pthread_cond_clockwait() 2) pthread_mutex_clocklock() 3) pthread_rwlock_clockrdlock() 3) pthread_rwlock_clockwrlock() All four will be newly added to the Issue 8 POSIX Standard. Matt Joyce (1): libc: Added

[PATCH 1/1] libc: Added prototypes for new POSIX APIs

Added function prototypes to newlib/libc/include/pthread.h for the following Issue 8 Standard APIs: pthread_cond_clockwait() pthread_mutex_clocklock() pthread_rwlock_clockrdlock() pthread_rwlock_clockwrlock() --- newlib/libc/include/pthread.h | 31 +++ 1 file changed,

[PATCH 1/1] testsuites: Added tests for sig2str/str2sig methods

Added psxsignal09 in psxtests and compile only test in psxhdrs in order to evaluate newly added POSIX standard methods in Newlib. --- spec/build/testsuites/psxtests/grp.yml| 2 + spec/build/testsuites/psxtests/libpsxhdrs.yml | 1 + .../build/testsuites/psxtests/psxsignal09.yml | 21

[PATCH 0/1] Edited Tests for sig2str/str2sig

Hello, I would like to submit the following updated version of the tests for the sig2str/str2sig methods based on Newlib's requested changes to the source. Thank you very much for your time! Sincerely, Matt Matt Joyce (1): testsuites: Added tests for sig2str/str2sig methods spec/build

[PATCH 1/1] testsuites: Added tests for sig2str/str2sig methods

Added psxsignal09 in psxtests and compile only test in psxhdrs in order to evaluate newly added POSIX standard methods in Newlib. --- spec/build/testsuites/psxtests/grp.yml| 2 + spec/build/testsuites/psxtests/libpsxhdrs.yml | 1 + .../build/testsuites/psxtests/psxsignal09.yml | 21

[PATCH 0/1] Edited sig2str/str2sig tests per mentor feedback

Here is the new version of the psxsignal09 test and the compile only test based on mentor's feedback. Matt Joyce (1): testsuites: Added tests for sig2str/str2sig methods spec/build/testsuites/psxtests/grp.yml| 2 + spec/build/testsuites/psxtests/libpsxhdrs.yml | 1 + .../build

[PATCH v3] testsuites: Added tests for sig2str/str2sig methods

Fixed newline error at end of psxsignal09.yml. Added psxsignal09 in psxtests and compile only test in psxhdrs in order to evaluate newly added POSIX standard methods in Newlib. --- spec/build/testsuites/psxtests/grp.yml| 2 + spec/build/testsuites/psxtests/libpsxhdrs.yml | 1 +

[PATCH v2] testsuites: Added tests for sig2str/str2sig methods

Added psxsignal09 in psxtests and compile only test in psxhdrs in order to evaluate newly added POSIX standard methods in Newlib. --- spec/build/testsuites/psxtests/grp.yml| 2 + spec/build/testsuites/psxtests/libpsxhdrs.yml | 1 + .../build/testsuites/psxtests/psxsignal09.yml | 20

[PATCH v2] libc: Added implementations for sig2str/str2sig methods

Added implementations for sig2str() and str2sig() in libc/signal in order to improve POSIX compliance. Added function prototypes added to sys/signal.h. --- newlib/libc/include/sys/signal.h | 12 ++ newlib/libc/signal/sig2str.c | 235 +++ 2 files changed, 247

[PATCH 2/2] testsuites: Edited tests for sig2str/str2sig methods

Added additional tests to init.c and added psxsignal09.scn and psxsignal09.doc to conform to RTEMS standards. --- testsuites/psxtests/Makefile.am | 2 + testsuites/psxtests/psxsignal09/init.c| 207 +- .../psxtests/psxsignal09/psxsignal09.doc | 34 +++

[PATCH 1/2] testsuites: Added tests for sig2str/str2sig methods

Added psxsignal09 in psxtests and compile only test in psxhdrs in order to evaluate newly added POSIX standard methods in Newlib. --- spec/build/testsuites/psxtests/grp.yml| 2 + spec/build/testsuites/psxtests/libpsxhdrs.yml | 1 + .../build/testsuites/psxtests/psxsignal09.yml | 20

[PATCH 2/2] libc: Edited implementations for sig2str/str2sig

Added features to function implementations to conform with POSIX standard. --- newlib/libc/signal/sig2str.c | 96 ++-- 1 file changed, 81 insertions(+), 15 deletions(-) diff --git a/newlib/libc/signal/sig2str.c b/newlib/libc/signal/sig2str.c index

[PATCH 1/2] libc: Added implementations for sig2str/str2sig

Added function implementations for sig2str() and str2sig() in libc/signal in order to improve POSIX compliance. --- newlib/libc/signal/sig2str.c | 156 +++ 1 file changed, 156 insertions(+) create mode 100644 newlib/libc/signal/sig2str.c diff --git

[PATCH] libc: Added sig2str/str2sig prototypes

Added definition of SIG2STR_MAX and function prototypes for sig2str and str2sig in sys/signal.h in order to improve POSIX compliance. --- newlib/libc/include/sys/signal.h | 12 1 file changed, 12 insertions(+) diff --git a/newlib/libc/include/sys/signal.h

[PATCH] libc: Added sig2str/str2sig prototypes

***As Requested: For Review Only. Does Not Compile*** Added definition of SIG2STR_MAX and function prototypes for sig2str and str2sig in sys/signal.h in order to improve POSIX compliance. --- newlib/libc/include/sys/signal.h | 12 1 file changed, 12 insertions(+) diff --git

[PATCH 1/1] Edited hello world message in init.c as prerequisite for GSOC application.

@@ static rtems_task Init( { rtems_print_printer_fprintf_putc(_test_printer); TEST_BEGIN(); - printf( "Hello World\n" ); + printf("Hello RTEMS World! From Matt Joyce, GSOC 2021 Applicant.\n"); TEST_END(); rtems_test_exit

[PATCH 0/1] Matt Joyce GSOC Hello World Patch

Hello RTEMS Community! Please see my Hello World patch as per the GSOC instructions. Thank you very much for your time and I'm excited to join you! Sincerely, Matt Matt Joyce (1): Edited hello world message in init.c as prerequisite for GSOC application. testsuites/samples/hello/init.c

Re: [Openstack-operators] [openstack-dev] Speaker Selection Process: OpenStack Summit Berlin

CFP work is hard as hell. Much respect to the review panel members. It's a thankless difficult job. So, in lieu of being thankless, THANK YOU -Matt On Mon, Aug 13, 2018 at 9:59 AM, Allison Price wrote: > Hi everyone, > > One quick clarification. The speakers will be announced on* August 14

Re: [openstack-dev] [Openstack-operators] Speaker Selection Process: OpenStack Summit Berlin

CFP work is hard as hell. Much respect to the review panel members. It's a thankless difficult job. So, in lieu of being thankless, THANK YOU -Matt On Mon, Aug 13, 2018 at 9:59 AM, Allison Price wrote: > Hi everyone, > > One quick clarification. The speakers will be announced on* August 14

[Distutils] Re: Packaging Advice for EFF's Certbot

It's generally easiest to find a maintainer who has an established track record to adopt the project. On Sat, Jul 28, 2018 at 11:53 AM, wrote: > Nathaniel Smith wrote: > > I love Debian. I've been a loyal user for twenty years. But Debian is > > really bad at coping with software that needs to

Re: hey!

Nat routing. Totally possible millions of tutorials and ways to do it. Google Ubuntu NAT router diy or something On Thu, Apr 19, 2018, 2:01 PM Charlie wrote: > i'm finally getting to put together my home server! i've got the computer > i'm going to use and i've got

Re: [Openstack] [Openstack-operators] OpenStack "S" Release Naming Preliminary Results

+1 On Thu, Mar 22, 2018 at 10:03 AM, Jonathan Proulx wrote: > On Wed, Mar 21, 2018 at 08:32:38PM -0400, Paul Belanger wrote: > > :6. Spandau loses to Solar by 195–88, loses to Springer by 125–118 > > Given this is at #6 and formal vetting is yet to come it's probably > not

Re: [Openstack-operators] OpenStack "S" Release Naming Preliminary Results

+1 On Thu, Mar 22, 2018 at 10:03 AM, Jonathan Proulx wrote: > On Wed, Mar 21, 2018 at 08:32:38PM -0400, Paul Belanger wrote: > > :6. Spandau loses to Solar by 195–88, loses to Springer by 125–118 > > Given this is at #6 and formal vetting is yet to come it's probably > not

Re: [openstack-dev] [Openstack-operators] OpenStack "S" Release Naming Preliminary Results

+1 On Thu, Mar 22, 2018 at 10:03 AM, Jonathan Proulx wrote: > On Wed, Mar 21, 2018 at 08:32:38PM -0400, Paul Belanger wrote: > > :6. Spandau loses to Solar by 195–88, loses to Springer by 125–118 > > Given this is at #6 and formal vetting is yet to come it's probably > not

Re: [Openstack-operators] Openstack operational configuration improvement.

Agreed on dashboard use. This is a mistake Google made with their GCP platform. They made their gui a nightmarish ux designed to destroy the souls of their users because they expected folks to use the CLIs... and a lot of the time they didn't... because are you are automating an environment

Re: [liberationtech] [hackerspaces] "How Linux and makerspaces can strengthen our social fabric"

What do you mean 'our' social fabric? Pretty sure I don't share the same sheets you do, fella. -openfly On Tue, Sep 5, 2017 at 8:34 PM, Phil Shapiro wrote: > > Interesting article posted here -- > > https://opensource.com/article/17/6/makerspaces-and-linux > > The author,

Re: [Distutils] PEP 517: Bootstrapping setuptools

venvs within venvs... terrifying concept. On Tue, Aug 22, 2017 at 11:02 AM, Jim Fulton wrote: > > > On Tue, Aug 22, 2017 at 9:23 AM, Daniel Holth wrote: > >> Isn't this a special case of needing . on sys.path when building a >> package? Then the same

Re: [Distutils] Fatal error "Python.h"

Look for a python-dev or python-devel package. On Jun 26, 2017 6:36 AM, "Rick" wrote: > Hi > Can anyone help? > I’m pretty new to Python and Raspberry Pi. > When running PIP, I seem to get fatal error: > > Python.h: No such file or directory > > include “Python.h” >

Re: [Distutils] Can u provide metadata about the PyPI

https://kirankoduru.github.io/python/pypi-stats.html this may be relevant to your interests. some of the pypi info is available on google big table. On Sat, Jun 24, 2017 at 5:02 AM, Priya Lakshmi wrote: > Respected Python expert > > I just want a help. Can u provide

Re: [Distutils] Malicious packages on PyPI

I was more pushing for the transitive trust element than signing. That being said, any signing at all would be progress. On Jun 1, 2017 9:07 PM, "Donald Stufft" <don...@stufft.io> wrote: On Jun 1, 2017, at 8:15 PM, Matt Joyce <m...@nycresistor.com> wrote: Or start doing

Re: [Distutils] Malicious packages on PyPI

Force packages to match their higher level import namespace in future major Python versions and PEP it. On Jun 1, 2017 7:37 PM, "Noah Kantrowitz" wrote: > > > On Jun 1, 2017, at 4:00 PM, Nick Timkovich > wrote: > > > > This issue was also brought

Re: [Distutils] Malicious packages on PyPI

Or start doing signed pgp for package maintainers and build a transitive trust model. On Jun 1, 2017 8:14 PM, wrote: Force packages to match their higher level import namespace in future major Python versions and PEP it. On Jun 1, 2017 7:37 PM, "Noah Kantrowitz" wrote: >

Re: [Distutils] Malicious packages on PyPI

;tho...@kluyver.me.uk> > wrote: > >> On Thu, Jun 1, 2017, at 06:32 PM, Matt Joyce wrote: >> >> It's basically a test dummy package that reports users who have ran that >> package template. >> >> >> That's what I thought, but all the code to do the up

Re: [Distutils] Malicious packages on PyPI

https://github.com/fate0/cookiecutter-evilpy-package/tree/master/%7B%7Bcookiecutter.package_name%7D%7D that's the package repo on github. It's basically a test dummy package that reports users who have ran that package template. the site referenced lists the package name that the user ran to

[Distutils] setuptools 33.1.1 - 35 issue with source package install from pypi

https://stackoverflow.com/questions/44120045/something-is-breaking-my-package-deployment has full info on what i am seeing, but it suffices to say: I use setuptools in my setup.py I iterate a requirements.txt file to satisfy dependencies. I publish as sdist to pypi my package used to work fine

Re: [Openstack-operators] about the R release name

+2 On Mon, Apr 10, 2017 at 5:07 PM, Monty Taylor wrote: > On 04/10/2017 02:10 PM, Amrith Kumar wrote: > >> The naming is based on community input and there's good reason to believe >> that in this round of voting both of these values will get a low score. >> >> But, we

Re: [Openstack-operators] about the R release name

Legit point. +1 Vote Rambler. No one's owned a rambler in like 50 years. =P On Mon, Apr 10, 2017 at 3:02 PM, Saverio Proto wrote: > Hello Ops, > > I got the mail about the Poll for OpenStack R Release Naming > > I am shocked that there are proposed names like Raspberry

[linux-lvm] LVM Cache Error: Manual Repair Required

I am having some issues with the cache on my LV preventing the LV from activating correctly usually some time on google gives me answers to the problem but this time I am having no luck everything I try results in the same "Manual repair required!" error. $ sudo lvchange -ay hdd-vg/data-lv

Re: [Openstack-operators] Packaging Virtualenvs

I want the script to dynamically instantiate the venv is call activate this at execution time and deactivate when done. On June 23, 2016 5:12:07 PM EDT, Doug Hellmann wrote: >Excerpts from Silence Dogood's message of 2016-06-23 15:45:34 -0400: >> I know from

Re: [Openstack-operators] [openstack-operators][neutron] use-case for multiple routers within a tenant

Directing between different PCI environments. On March 8, 2016 5:20:46 PM EST, Rubab Syed wrote: >Hi all, > >I am trying to get a general understanding of OpenStack networking. Can >someone please point out a simple use-case for using multiple routers >within same tenant?

Re: [Openstack-operators] Compressed Images

It might be a function of apache compression ? On July 29, 2015 3:38:25 PM EDT, Joe Topjian j...@topjian.net wrote: Hello, In the Create An Image page of Horizon, it says the following: Currently only images available via an HTTP URL are supported. The image location must be accessible to the

Re: [Openstack-operators] Getting ERROE on compute node

On newer rabbitmq the guest account is disabled for remote access by default. Try not to use it. -Matt On July 8, 2015 10:07:18 AM EDT, MailingLists - EWS mailingli...@expresswebsystems.com wrote: Anwar, It looks like your RabbitMQ isn’t running or isn’t reachable. There were some

Re: [Openstack-operators] Scaling the Ops Meetup

I just assumed this whole outfit was ran by some shadowy kabal. I feel very disillusioned now. -Matt On July 2, 2015 2:26:47 PM EDT, Jesse Keating j...@bluebox.net wrote: BoD, unless they feel the need to delegate, at which point then maybe an Operators committee. But I'd hate to see more

Re: [Openstack-operators] Scaling the Ops Meetup

+1 On July 2, 2015 2:15:02 PM EDT, Jesse Keating j...@bluebox.net wrote: Honestly I'm fine with the elected board helping to make this decision. Folks that want to underwrite the event can submit a proposal to host, board picks from the submissions? Having a wide vote on it seems overkill to me.

Re: [openstack-dev] [Openstack-operators] Resources owned by a project/tenant are not cleaned up after that project is deleted from keystone

Wondering if heat should be performing this orchestration. Would provide for a more pluggable front end to the action set. -matt On Feb 25, 2015 2:37 PM, Joe Gordon joe.gord...@gmail.com wrote: On Sat, Feb 21, 2015 at 5:03 AM, Tim Bell tim.b...@cern.ch wrote: A few inline comments and a

Re: [Openstack-operators] [openstack-dev] Resources owned by a project/tenant are not cleaned up after that project is deleted from keystone

Wondering if heat should be performing this orchestration. Would provide for a more pluggable front end to the action set. -matt On Feb 25, 2015 2:37 PM, Joe Gordon joe.gord...@gmail.com wrote: On Sat, Feb 21, 2015 at 5:03 AM, Tim Bell tim.b...@cern.ch wrote: A few inline comments and a

Re: [Openstack-operators] [Ceilometer] Real world experience with Ceilometer deployments - Feedback requested

I thought stacktach was more in the vein of diagnostic.  Not billable resources.  On Feb 12, 2015 10:47 AM, Tim Bell tim.b...@cern.ch wrote: Does anyone have any proposals regarding - Possible replacements for Ceilometer that you have used instead It seems that many sites have written

Re: [Openstack-operators] Mar 9-10, 2015, Philadelphia, USA - Next Ops Meetup

Curious as well. On Jan 9, 2015 5:08 PM, Stuart Fox stu...@demonware.net wrote: Just pinging out to see if I missed a registration page? There are 2 of us wanting to come BR, Stuart On Wed, Jan 7, 2015 at 7:18 AM, Ignace Mouzannar ign...@enovance.com wrote: Hey Tom, Thanks for

Re: [openstack-dev] TC election by the numbers

On one hand, I agree a member of the TC should be a very active member of the development community. Something I have not been, much to my shame. However, there are obviously some fundamental issues in how the TC has been governing OpenStack in the past few releases. Very serious issues in the

[Desktop-packages] [Bug 1236951] Re: package tex-common 4.04 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

This affected me today on a 12.04 upgrade to 14.04 both LTS obviously. Staggering such a huge bug is still in effect after so long a time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu.

[Desktop-packages] [Bug 1236951] Re: package tex-common 4.04 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

Got around my foul up in a REALLY ugly manner. started with a couple iterations of : dpkg -l | grep texlive | awk '{print $2}' | sort | xargs dpkg -r this cleared out a lot of the easy to hit cruft with no dependency issues. Then I finished off by hitting what i could with specific called out

[Bug 1236951] Re: package tex-common 4.04 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

This affected me today on a 12.04 upgrade to 14.04 both LTS obviously. Staggering such a huge bug is still in effect after so long a time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1236951

[Bug 1236951] Re: package tex-common 4.04 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

Got around my foul up in a REALLY ugly manner. started with a couple iterations of : dpkg -l | grep texlive | awk '{print $2}' | sort | xargs dpkg -r this cleared out a lot of the easy to hit cruft with no dependency issues. Then I finished off by hitting what i could with specific called out

Re: [openstack-dev] [all] The future of the integrated release

On Wed, Aug 06, 2014 at 11:51:27AM -0400, Eoghan Glynn wrote: You've touched on multiple trains-of-thought that could indeed justify separate threads of their own. I agree with your read on the diverging growth rates in the strategic versus the tactical elements of the community. I

Re: [Openstack] Is there any way to migrate the Instance between the projects/tenants?

There is a specific need for this in incident response for some SOC teams. They may need to isolate a compromised instance to a more secure and security controlled tenancy. I think this would be an advantageous blueprint for next release. -Matt On Tue, Jul 16, 2013 at 9:46 AM, Lloyd Dewolf

Re: [Openstack] How to Install OpenStack ???????????

You know, I am surprised none of us OpenStack distribution vendors have taken a page from 1999 and started selling OpenStack grizzly/havana books with installation CDs for our distribution in the back. -Matt On Fri, Jul 12, 2013 at 11:15 AM, Joshua McKenty jos...@pistoncloud.comwrote: Tiny

Re: [Openstack] OpenStack Monitoring with Nagios

Ceilometer is authoritative data taken directly from message bus queries and keeps a back history, as opposed to nagios which does periodic finite state checks. Ceilometer is intended to be a log of transactions necessary to provide billing information. Or potentially an audit log. Nagios is

Re: [Openstack] The OpenStack Community Welcomes Developers in All Programming Languages

I am not sure we want to allow python developers... those guys have a PEP for everything. Can't even sit down to a slice of cake without a PEP to tell them how to cut it and a CI environment to make sure their slice is within those PEP defined tolerances. I've had it up to here with those

Re: [Blabber] Smoothing PLA printed parts

. The greatest danger posed by THF follows from its tendency to form highly-explosive peroxideshttp://en.wikipedia.org/wiki/Organic_peroxide on storage in air. On Sun, Jun 9, 2013 at 10:50 PM, Matt Joyce m...@nycresistor.comwrote: I've ordered some of this stuff: http://www.amazon.com/Tetrahydrofuran

Re: [Openstack] Customer Portal Security from Hackers

Chris, Someone will probably denounce this email as heresy for using this analogy, but so be it. Try to think of OpenStack as you would a motor vehicle's engine. It has many components that all tie together to allow the engine to operate. Sometimes it has different configurations such as having

Re: [Openstack] DevStack Question

most folks would use puppet or chef to accomplish that task. On Sun, May 12, 2013 at 2:46 PM, Arindam Choudhury arin...@live.com wrote: Hi, If the script is updated to use cloud repository instead of source code, it can be used as an automatic installer. Have anybody done it yet? Regards,

Re: [Openstack] [OpenStack Marketing] New code name for networks

to say nothing of the localization that will need complete re-translating. On Sun, May 12, 2013 at 6:27 PM, Sean Dague s...@dague.net wrote: On 05/12/2013 09:14 AM, Mark McLoughlin wrote: On Sat, 2013-05-11 at 19:50 +, Jason Smith wrote: Hello, I understand why we had to give up

Re: [Openstack] New code name for networks

Tyronosaurus Rex Optimus Prime Super Happy Fun Network Times A.N.A.L. - Automated Networking and Logistics And with that I am out of ideas. On Sat, May 11, 2013 at 12:58 PM, Davanum Srinivas dava...@gmail.comwrote: Lattice -- dims On Sat, May 11, 2013 at 3:52 PM, Mark Turner

Re: [Blabber] Hackable guns

Duepner wrote: I agree. It sounds stupid unless you are suicidal or are trying to prove a point. On May 7, 2013 2:36 PM, Matt Joyce m...@nycresistor.com (mailto: m...@nycresistor.com) wrote: easier to make a gun on a lathe. On Tue, May 7, 2013 at 11:35 AM, frac...@maui.net

Re: [Openstack] I release naming (calling APAC community)

'Impossible' might be a good name... seeing as how impossible it is becoming to find a word beginning with I in the region. On Thu, May 9, 2013 at 12:04 PM, John Wong gokoproj...@gmail.com wrote: Good point. A long time ago we used to call Beijing as Peking, but the journalists now will

Re: [Openstack] I release naming (calling APAC community)

”, it should be easier to give a nameJ ** ** -- Shane Wang *From:* Openstack [mailto:openstack-bounces+shane.wang= intel@lists.launchpad.net] *On Behalf Of *Rajesh Vellanki *Sent:* Friday, May 10, 2013 3:50 AM *To:* Atul Jha; Matt Joyce; John Wong *Cc:* Thierry Carrez; openstack

Re: [Blabber] Hackable guns

easier to make a gun on a lathe. On Tue, May 7, 2013 at 11:35 AM, frac...@maui.net wrote: Speaking of hacking and machines, how about the new trend of using stereolithography to print out guns and other weapons? Do you think there could be a legal backlash in the works? (think meth lab vs

Re: [Openstack] Related Projects

This is going to come off as a bit of a rant. Pardon me. I feel it needs saying. There's a few ways to look at what OpenStack is. It's an IaaS solution. It's a cloud solution. But at it's heart, core to the design principles of OpenStack development ideology it is a collection of tools

Re: [Blabber] Tactical Kilts

It's a skirt. It can't be worn in the many fashionable ways a kilt can. It's a skirt. A tactical skirt sure. But a skirt. And more power to you if you wish to eschew the societal norms of gender as it relates to garments. But no bones, you are still wearing a skirt. On Wed, Apr 24, 2013 at

Re: [Pool] Unable to add IPv6 NTP host

On 17/04/13 20:14, AlbyVA wrote: I would add that I doubt the HE Tunnel is at issue. I also have an HE v6 tunnel that is listed in the ntp pool and it is working. http://www.pool.ntp.org/scores/2001:470:8:104::2 I will say this... You need to keep some level of v6 traffic always

Re: [tor-relays] BitTorrent complaint

On 12/04/13 22:54, Moritz Bartl wrote: On 12.04.2013 19:16, Matt Joyce wrote: It would help a lot if we used versioning and stopped sending almost unchanged data constantly and instead only providing the changes I doubt that this is easy to do in a privacy-preserving way. You don't want

Re: [tor-relays] BitTorrent complaint

On 13/04/13 11:49, Moritz Bartl wrote: On 13.04.2013 09:05, Jorge-Leon wrote: 1) Allow everything (except port 25, which is reasonable to block) 2) If you don't want the DMCA spam notices, use the reduced exit policy. Please expand on except port 25, which is reasonable to block, or point me

Re: [tor-relays] BitTorrent complaint

On 09/04/13 20:46, krishna e bera wrote: On Tue, 9 Apr 2013 22:59:06 +0600 Roman Mamedov r...@romanrm.ru wrote: On Tue, 9 Apr 2013 12:50:09 -0400 krishna e bera k...@cyblings.on.ca wrote: So at the risk of being labelled a BadExit (or at best a non-net-neutral exit) i blocked all of

Re: [tor-relays] BitTorrent complaint

On 11/04/13 20:00, Moritz Bartl wrote: On 11.04.2013 12:15, t...@caber.nl wrote: If we want to avoid the packet-dropping problem: We could also reject the IP-addresses of those sites with torrc. What is your opinion about that Moritz? And, would it ok for the authorities and users with little

Re: [tor-relays] BitTorrent complaint

On 12/04/13 15:03, Moritz Bartl wrote: On 12.04.2013 13:33, Matt Joyce wrote: I assume you mean firewall-based blocking? You could have simply rejected those IPs via ExitPolicy (see man tor). That's a clear-cut way to tell the network you don't accept connections to those IPs, and no risk

Re: [tor-relays] On the way to more diversity

On 05/04/13 12:34, Philipp Winter wrote: On Thu, Apr 04, 2013 at 06:37:51AM +0200, Andreas Krey wrote: And do obfs3 bridge help that are run on IPs also used for regular relays? Right now, it is important to get more obfs3 bridges for China since obfs2 no longer works [0]. In general, it

Re: [Shorewall-users] looking for good traffic shaping working example

On 31/03/13 21:37, Alan McKay wrote: On Sun, Mar 31, 2013 at 4:21 PM, Tom Eastep teas...@shorewall.net wrote: Changing the OUTGOING configuration isn't going to do anything. If you have specified an IN-BANDWIDTH, get rid of it; do you have normal download speed then? Duh, so simple! Yeah,

Re: [Shorewall-users] looking for good traffic shaping working example

On 30/03/13 16:33, Alan McKay wrote: On Sat, Mar 30, 2013 at 12:21 PM, Tom Eastep teas...@shorewall.net mailto:teas...@shorewall.net wrote: What does your eth0 entry in tcdevices look like? #NUMBER:IN-BANDWITHOUT-BANDWIDTHOPTIONSREDIRECTED #INTERFACEINTERFACES 1:eth0 35Mbit 1Mbit

Re: [Shorewall-users] looking for good traffic shaping working example

On 29/03/13 12:22, Alan McKay wrote: Hi folks, First of all let me say an enormous THANK YOU for shorewall in general! It is so easy to write powerful firewall configurations with this tool! Well, it was until I wanted to fiddle with QoS ... now it is not so easy unfortunately :-( I

Re: [Shorewall-users] looking for good traffic shaping working example

On 29/03/13 13:25, Alan McKay wrote: On Fri, Mar 29, 2013 at 9:05 AM, Robert K Coffman Jr. -Info From Data Corp. bcoff...@infofromdata.com wrote: Post your tc* files and I'll take a look. I'm just giving those another good going over ... I think Im a bit mixed up on them :-) Part of what

Re: [tor-relays] Ongoing denial of service attack against Tor relays by leased botnet in America and PRC (Nobistech, Datashack, Limestone, HE, Pegtech, WholeSale Interent, and Psychz VPS nodes, etc)

On 28/03/13 17:21, grarpamp wrote: New to the list, I run a Tor exit node from my small cable modem connection in Honolulu, as well as for a short time on a few on VPS's to prove to Over the last several weeks, I have collected substantial evidence indicating that a botnet is degrading the Tor

Re: [Blabber] Building Personal Robot, looking for help.

what are you using for muscle control? also is any of your work available on thingiverse / github? On Tue, Mar 26, 2013 at 1:45 PM, Jason Ravel jsra...@columbia.edu wrote: Hey hackers, For the past 2 months I've been developing a Personal Robot that will be capable of doing tasks in the

Re: [tor-relays] port setup

On 20/03/13 03:43, Lance Hathaway wrote: On 19/03/2013 6:23 PM, Art wrote: On 03/19/2013 03:43 PM, Stephen Mollett wrote: it Hi, On Tuesday, 19 March 2013 at 13:57, Art k...@myfairpoint.net wrote: I entered 9001 in the Global PortStart box andthe other empty boxes on the setup page

  1   2   3   4   >