Tails

#1 Updated by BitingBird 2014-06-09 10:53:05

• Subject changed from report Veewee unusable with gem --user to Report Veewee unusable with gem --user
• Description updated
• Starter set to No

#2 Updated by BitingBird 2014-06-09 10:59:01

• Type of work changed from Code to Communicate

#3 Updated by intrigeri 2014-06-09 12:00:53

• Category set to Build system
• Type of work changed from Communicate to Code

#4 Updated by intrigeri 2014-06-09 12:01:18

• Subject changed from Report Veewee unusable with gem --user to Report that Veewee is unusable with gem --user
• Type of work changed from Code to Communicate

#5 Updated by intrigeri 2014-06-09 12:01:59

• related to Bug #7218: Update Vagrant basebox to Wheezy added

#6 Updated by sajolida 2014-06-16 11:32:00

• Type of work changed from Communicate to Upstream

#7 Updated by intrigeri 2014-06-16 12:25:34

• Type of work changed from Upstream to Communicate

“Upstream” is being used for too many different things these days. See the topic I’ve proposed for the summit. In the meantime, when all that’s needed is to tell upstream something, I’d rather use “Communicate”, and keep “Upstream” for e.g. “we need to upstream some patches of ours” and “we’re hoping that upstream will implement this”, which is already confusing enough IMO.

#9 Updated by intrigeri 2014-07-21 08:57:41

• Status changed from Confirmed to Rejected

Apparently, it now works (see feature/vagrant-wheezy-basebox).