Public bug reported:
Possible to manually set display brightness to 0 on Ubuntu Touch
It is possible to move the brightness slider to the very left position,
which will set the display brightness of affected device to zero, or, to
total darkness.
This is a bug, since this leads to user's inabili
Public bug reported:
Aquaris E5: Ringtone + buzzer cannot be heard when jack/headphones are
plugged.
This I consider a bug, since user cannot depend on the such a device
with hearing calls / being woken up in the morning.
Typical scenario: listening to music/watching movies during the night
and
Bug still present on E5 after OTA-10.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1483427
Title:
Possible to manually set display brightness to 0 on Ubuntu Touch on
Aquaris E5
Issue still present after OTA-11 and OTA-12.
1) Why is this closed as invalid please?
2) Shall this be re-assigned somewhere else? Please advise...
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchp
Fixed with OTA-13. Thank you.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1483427
Title:
Possible to manually set display brightness to 0 on Ubuntu Touch on
Aquaris E5
Status
Unfortunately, bug re-introduced for E5 by OTA-14.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1483427
Title:
Possible to manually set display brightness to 0 on Ubuntu Touch on
My config attached.
** Attachment added: "config-default.xml"
https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1483427/+attachment/4790904/+files/config-default.xml
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in
In the example above, I dimmed backlight to complete black (nothing
visible) 2x, just before posting the log...
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1483427
Title:
Possib
And here is the second one...
** Attachment added: "repowerd.log"
https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1483427/+attachment/4790905/+files/repowerd.log
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in U
I had exactly the same issue. Commenting out the content of
/etc/X11/Xsession.d/50_check_unity_support works around the issue.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.laun
ram on it...
Thanks again. Hopefully this will fix it.
Stefan
> From: Christopher Kolp <[EMAIL PROTECTED]>
> Reply-To: "Duo/2400 List" <[EMAIL PROTECTED]>
> Date: Mon, 18 Aug 2003 19:02:53 -0400
> To: "Duo/2400 List" <[EMAIL PROTECTED]>
> Subject: [
Hmm interesting. Ok.
here's mine:
g3 newer 240mhz
Cardbus upgrade
112mb ram (now back to 80mb)
25gb harddrive
That's whats been altered.
Stefan
> From: Larry <[EMAIL PROTECTED]>
> Reply-To: "Duo/2400 List" <[EMAIL PROTECTED]>
> Date: Tue, 19 Aug
work. Maybe it wasn't the RAM :)
Here we go.
Stefan
> From: "Bodenschatz, Robert B CDR J42426," <[EMAIL PROTECTED]>
> Reply-To: "Duo/2400 List" <[EMAIL PROTECTED]>
> Date: Tue, 19 Aug 2003 11:20:18 -1000
> To: "Duo/2400 List" <[EMAIL PRO
Does anyone know of a web shop that sells backup batteries for a Powerbook
2400c and will ship internationally?
Apple in Sweden does not carry it unfortunately...
Stefan
--
Duo/2400 List, The friendliest place on the Net!
A listserv for users and fans of Mac subportables.
FAQ at <h
How much more would you earn?
F ast Tr ack Degre e Prog ram
Obtain the degr ee you deserve, based on your present knowledge and life
experience. A prosperous future, m oney earning power, and the Admiration of
all.
Degre es from an Established, Prestigio us, Leading Institution.
Your degr ee wil
Nice work, Yann!
> Am 06.02.2021 um 13:17 schrieb yla...@apache.org:
>
> Author: ylavic
> Date: Sat Feb 6 12:17:40 2021
> New Revision: 1886255
>
> URL: http://svn.apache.org/viewvc?rev=1886255&view=rev
> Log:
> mod_http2: Fix workers synchronization on pchild cleanup.
>
> When the MPM child e
onfig['default_host'] = 'ssl://localhost:993';
Stefan
On Mon, 17 Oct 2005 11:03:14 -0700, Gary <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm trying to use RoundCube with UW-IMAP but am having a login problem
> that I can't seem to pin down. I've set th
I'm trying to use a very simple key/value table, where both the key and the
value are byte arrays. The key is limited to 64 bytes length, the value can
be a lot bigger (I'm using a blob for that).
I've read documentation and googled for two days now but I haven't found a
working solution that is w
able to better have something ready now, then be sorry later.
>
>
> Of course we should fix things to not break, but that is a different
> story.
>
Absolutely right (and my reply in the previous section actually assumes
that the current issues would be solved).
Regards,
Stefan
smime.p7s
Description: S/MIME Cryptographic Signature
On 2/21/2017 13:54, Stefan Sperling wrote:
> The new 1.10.1-alpha2 release is up for signing.
>
> The proposed 1.10.0-alpha1 release had a compilation problem on Windows.
> The alpha2 release should fix this problem. It is based on trunk@r1783880.
>
> Full committers, please get
On 6/30/2017 15:05, Daniel Shahaf wrote:
> The 1.9.6 release artifacts are now available for testing/signing.
>
> Please get the tarballs from
> https://dist.apache.org/repos/dist/dev/subversion
> and add your signatures there.
>
> I'm aiming to release this within a week. (CHANGES points to thi
On 7/3/2017 12:55, Stefan Sperling wrote:
> The 1.8.18 release can now be tested and signed.
> Get it from https://dist.apache.org/repos/dist/dev/subversion
> as usual, and add your signatures there. Thanks!
Summary
---
+0.5 to release (+1 once subversion-1.8.18.tar.gz.sha512
On 7/6/2017 04:13, Daniel Shahaf wrote:
> Stefan wrote on Thu, 06 Jul 2017 00:14 +0200:
>> Summary
>> ---
>> +0.5 to release (+1 once subversion-1.8.18.tar.gz.sha512 has been
>> corrected - see below)
>>
>> Verified
>>
>>
On 7/6/2017 08:04, Stefan wrote:
> On 7/6/2017 04:13, Daniel Shahaf wrote:
>> Stefan wrote on Thu, 06 Jul 2017 00:14 +0200:
>>> Summary
>>> ---
>>> +0.5 to release (+1 once subversion-1.8.18.tar.gz.sha512 has been
>>> corrected - see below)
On 6/28/2017 10:06, Stefan Hett wrote:
> Hi,
>
> I'd just like to drop a quick note letting all know that despite my
> absence over the past weeks/months I'm all fine and still alive.
>
> I've had several very busy weeks the past months (and this is likely
>
dition to "Resolution" or instead of it). If a change needs to be
> made, please tell me. (Or commit it directly :-))
>
> Thanks,
>
> Daniel
FWIW: Reviewed the JIRA link and looks correct to me.
Regards,
Stefan
> +
> # finally, run the subcommand, and give it the parsed arguments
> args.func(args)
>
>
Thanks for changing this. I had put that one on my todo-list while
signing the 1.9.7/1.8.18 releases to simplify the verification process.
Regards,
Stefan
/release.py?rev=1805277&r1=1805276&r2=1805277&view=diff
> ==
> [...]
>
>
Thanks for improving the checks.
I've tested the current release.py on trunk (@1805277). It works like a
charm. :-)
Regards,
Stefan
that
kind of issue by running release.py check-sigs in the future, so we
should not run into such problem again.
Shortly discussed on IRC with brane whether we'd be ok with making the
correcting commit on dist.apache.org (with the conclusion to just fix it).
Regards,
Stefan
[1] http://mirro
can be used to debug/test issues yourself
(by shipping symbol files)
Regards,
Stefan
smime.p7s
Description: S/MIME Cryptographic Signature
On 03/09/2017 11:20, Johan Corveleyn wrote:
> On Fri, Sep 1, 2017 at 2:23 AM, Daniel Shahaf wrote:
>> Stefan Sperling wrote on Thu, 31 Aug 2017 12:05 +0200:
>>> On Wed, Aug 30, 2017 at 11:36:17PM +, Daniel Shahaf wrote:
>>>> Johan Corveleyn wrote on Wed, 30 Aug
.
As far as I see it, one of the main restrictions we regularly face is
the use of //-comment styles (especially when talking here integrated
external libraries/code). This is something which has long been
supported even in VS.
The wikipedia page also provides quite a summary of C99-support in
different compilers [1].
Regards,
Stefan
[1] https://en.wikipedia.org/wiki/C99#Implementations
On 24/09/2017 19:55, Branko Čibej wrote:
> On 24.09.2017 11:36, Stefan wrote:
>> On 22/09/2017 13:29, Branko Čibej wrote:
>>> On 22.09.2017 13:18, Julian Foad wrote:
>>>> Julian Foad wrote:
>>>>> When we released Subversion 1.0 in 2004, we were st
as just for the
sake of the //-comment-usage.
But I see that there's some reluctance to make this step, and while I'd
certainly would appreciate us moving ahead, I personally also don't see
that much an urge to use C99-features atm. Hence, I'll leave the idea
rested now.
Regards,
Stefan
smime.p7s
Description: S/MIME Cryptographic Signature
;
> The event is planned to be held in Aachen, Germany in the late November.
> The approximate dates for the main part of this event are either November
> 13-17th or 20-24th. One of the Subversion PMC members, Stefan Hett, who
> currently resides in Aachen, is going to take on most of th
e interested in joining us, please send me a PM and whether you
are planning to have dinner there as well (or just come over for a
drink), so I can make sure we get a proper location which is large
enough for all of us.
Regards,
Stefan
smime.p7s
Description: S/MIME Cryptographic Signature
On 26/10/2017 23:28, Branko Čibej wrote:
> [Restoring all Cc:]
> On 26.10.2017 22:34, Stefan wrote:
>> The meet-and-greet event will happen on November 23rd in Aachen at 8pm
>> local time (UTC: +02:00).
>
> On 23rd November it will be UTC+01:00, daylight savings time in t
On 26/10/2017 22:34, Stefan wrote:
> Hi,
>
> the Apache Subversion project organizes a yearly hackathon for its
> project members. This year we are planning something special during that
> event for the community as well: A meet-and-greet event.
>
> If you always wanted to
Thanks Sally,
everything which will increase the visibility of the event is much
appreciated.
Regards,
Stefan
On 12/11/2017 19:09, Sally Khudairi wrote:
> Thanks, Stefan. I'll add it to the Apache Weekly News Round-Up and will
> also promote on our social channels.
>
> Here&#x
On 24/11/2017 12:25, Branko Čibej wrote:
> On 24.11.2017 12:20, Johan Corveleyn wrote:
>> At the hackathon we (me, Stefan Hett, Stefan Fuhrmann, Bert, Julian)
>> discussed migrating our wiki from the current MoinMoin
>> (wiki.apache.org/subversion) to the AS
On 25/11/2017 22:14, Julian Foad wrote:
> Julian Foad wrote:
>> At the hackathon today we (me, Stefan Hett, Bert, Johan) have been
>> talking about how to progress 1.10.
>
> It seems we have general consensus to move to an RC1. A few things
> we'd like to fix but n
e.org/viewvc/subversion/site/staging/quick-start.html?rev=1815812&r1=1815811&r2=1815812&view=diff
>> ==
>> --- subversion/site/staging/quick-start.html (original)
>> +++ subversion/site/staging/quick-start.
On 25/11/2017 16:12, Stefan Sperling wrote:
> On Fri, Nov 24, 2017 at 02:42:05PM +0100, Bert Huijben wrote:
>> Hi,
>>
>> At the Aachen hackathon I promised to write some code to spit out the sparse
>> definition of a working copy, or in other words some init
bout the acceptance of faster releases (i.e.
once every 6 months). Maybe we'd simply send out a mail to maintainers
polling for which time line they'd prefer (i.e. 6, 9, 12, 24 months for
new releases)? Just for us to get some idea on what those people who'd
be directly impacted by our decision would think about before we are
making a call?
Regards,
Stefan
smime.p7s
Description: S/MIME Cryptographic Signature
On 28/11/2017 16:16, Branko Čibej wrote:
> On 28.11.2017 15:01, Stefan wrote:
>> I'm also a bit worried about the acceptance of faster releases (i.e.
>> once every 6 months). Maybe we'd simply send out a mail to maintainers
>> polling for which time line they'd
On 28/11/2017 22:34, Branko Čibej wrote:
> On 28.11.2017 20:23, Stefan wrote:
>> On 28/11/2017 16:16, Branko Čibej wrote:
>>> On 28.11.2017 15:01, Stefan wrote:
>>>> I'm also a bit worried about the acceptance of faster releases (i.e.
>>>> once every
ge is working again, but it doesn't seem to provide
any archive of the subversion mailing lists anymore [4]. Hence I take
it, we'd rather drop these no longer working links from our webpage.
Regards,
Stefan
[1] https://en.wikipedia.org/wiki/Gmane
[2] https://lars.ingebrigtsen.no/2016/07/28/the-end-of-gmane/
[3] https://lwn.net/Articles/695695/
[4] http://gmane.org/find.php?list=subversion
On 01/12/2017 00:48, Daniel Shahaf wrote:
> Stefan wrote on Thu, 30 Nov 2017 23:52 +0100:
>> On 30/11/2017 23:47, luke1...@apache.org wrote:
>>> Author: luke1410
>>> Date: Thu Nov 30 22:47:41 2017
>>> New Revision: 1816774
>>>
>>> URL: htt
'
(include_path='.:/usr/local/lib/php') in
//*/kunden/156453_33729/hosting/4833/afaik.de/usenet/faq/zitieren/zitieren.php3*//on
line //*2"*/
I could find a replacement which claims to be a local copy of the
content which was available at the now broken linked page. Again I don't
have any doubt that this is a correct capture of the original content
(though it might not have been the latest version). Still, IMO this
seems to be a reasonable replacement for the broken link, or does
anybody think otherwise?
Regards,
Stefan
**
to end-of-life their moinmoin service, if I understood
> correctly.
I'm still all for doing the migration, regardless of the pointed out
restrictions.
> gmcdonald will be sending me the Universal Wiki Converter tools and
> actual moinmoin pages of Subversion, so I can experiment a bit with
> it.
>
Great. Hope there's not too much work required there.
Regards,
Stefan
e 1.8 release notes page [1].
Adding these links/sections however also changed the layout so the
h3-sections are now indented. Initially I thought to resolve this, but
after checking think it looks better that way. To see the change,
compare these two pages [2/3]. Anybody against keeping this change?
Also note that in order to use HTML 4.01 compliant ids, I did not go
with #1.8 but rather #release-1.8, since in HTML 4.01 ids are not
allowed to start with numbers.
Regards,
Stefan
[1] http://subversion.apache.org/docs/release-notes/1.8.html (see link:
"API users").
[2] http://subversion-staging.apache.org/docs/
[3] http://subversion.apache.org/docs/
111";>XXX
> (dead link) åæã
>
>
>
>
>
I was thinking how to handle links where we can't determine a working
replacement. For the Chinese 1.6 release notes I went with adding "XXX
(dead link)" markers to at least point out that these are broken. This
seems to be acceptable to me here, since the page contains a couple of
other "XXX"-style TODO-/note-markers.
I'm open for alternative ideas though (or do we have some defined
style/handling for this I missed?).
Regards,
Stefan
and the corresponding log message matching the
content from the 1.6-release notes page, I conclude that the
corresponding previous commit (r872853) is the one which previously was
referred to as r32778 in the collabnet repository:
https://svn.apache.org/viewvc?view=revision&revision=872852
I'd still appreciate, if someone who happens to slightly remember which
revision this release notes was linked against, could verify that the
replacement link is correct (see:
http://subversion-staging.apache.org/docs/release-notes/1.6.html ).
Regards,
Stefan
PI documentation for unsupported versions still
laying around (it should not cause any significant resources keeping
them available, IMO).
Note that I'd reinstate the old 1.6 docus directly on publish (rather
than on staging) since this would be easier to do (i.e. reverting the
corresponding changes from r1696552 which obviously were done on publish).
Any objections and/or better ideas?
Regards,
Stefan
On 10/12/2017 17:11, Branko Čibej wrote:
> On 10.12.2017 17:00, Stefan wrote:
>> On 10/12/2017 16:54, luke1...@apache.org wrote:
>>> Author: luke1410
>>> Date: Sun Dec 10 15:54:23 2017
>>> New Revision: 1817718
>>>
>>> URL: http://svn.apac
rge conflict when they are published?
Since I was working on the site right now, I took the liberty and
quickly did it in r1817860.
Regards,
Stefan
ng from previous versions of Berkeley DB chapter of the Berkeley
> DB
> +Upgrade Guide for instructions on upgrading Berkeley DB environments.
>
>
>
>
I'd appreciate if anybody more familiar with the BDB setup/instructions
back around the 1.4 release could verify that the substitution for the
old dead link is correct here rather than only relying on my
google/DuckDuckGo-search skills.
Regards,
Stefan
only note it down
in the text. Note that as far as I can see JavaSVN no longer exists and
therefore I couldn't find a replacement for the old link.
Any objections/alternative suggestions?
Regards,
Stefan
On 13/12/2017 09:08, Johan Corveleyn wrote:
> On Wed, Dec 13, 2017 at 1:38 AM, Stefan wrote:
>> On 13/12/2017 01:31, luke1...@apache.org wrote:
>>> Author: luke1410
>>> Date: Wed Dec 13 00:31:56 2017
>>> New Revision: 1817969
>>>
>>> URL: htt
On 10/12/2017 17:23, Stefan wrote:
> On 10/12/2017 17:11, Branko Čibej wrote:
>> On 10.12.2017 17:00, Stefan wrote:
>>> On 10/12/2017 16:54, luke1...@apache.org wrote:
>>>> Author: luke1410
>>>> Date: Sun Dec 10 15:54:23 2017
>>>> New Revisio
On 13/12/2017 21:28, Julian Foad wrote:
> Stefan wrote:
>> On 11/12/2017 18:15, Daniel Shahaf wrote:
>>> julianf...@apache.org wrote on Mon, 11 Dec 2017 13:41 +:
>>>> Modified:
>>>> subversion/site/publish/docs/community-guide/releasing.part.html
.edu/ECN/Support/KB/Docs/SSHIntroductionToSSH
> -http://www.zip.com.au/~roca/ttssh.html";>TTSSH: A Win32 SSH
> client capable of port forwarding
>
>
>
>
>
FTR: I got in touch with Robert O'Callahan (the author of TTSSH) and he
stated/suggested to drop the link since nobody should be using TTSSH
anymore (i.e. was discontinued). Hence, removed the link.
Regards,
Stefan
ortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-serversetup-svnserve.html";>
> -TortoiseSVNæåè¿æä¸ç¹å
容å
³äºæä¹å°svnserveå®è£
> ææå¡çå½¢å¼ã
> -
>
>
>
>
>
FTR: Two of the three links in these sections are dead and given that
SVN 1.4 is way beyond it's end of life, I really don't see much purpose
keeping that old information still in the FAQ section. It only bloats
the page unnecessarily with information which is simply outdated.
If anybody disagrees, please let me know.
Regards,
Stefan
ed in 1.6 (as I
did). That's less likely to happen with danielsh's phrasing, since it
points out that these line endings were (always) considered invalid.
So to not just reply here without taking action, I went ahead and
committed danielsh's suggested change in r1818517.
Regards,
Stefan
score.
>
>
>
>
Originally I only intended to unbreak the links in the CVSSv2 section
but then decided to update the documentation to CVSSv3 which we are
using meanwhile.
Since I never calculated the CVSS score for a Subversion vulnerability
before, maybe someone familiar with the details could verify the
information I changed are accurate?
In principle I only replaced what was called "Complete" in CVSSv2 to
"High" for CVSSv3 and "Partial" got changed to "Low". As far as the
specification goes, this should be how we handle it for CVSSv3, right?
Regards,
Stefan
On 20/12/2017 01:08, Daniel Shahaf wrote:
> Stefan wrote on Tue, 19 Dec 2017 23:39 +0100:
> [...]
>> Since I never calculated the CVSS score for a Subversion vulnerability
>> before,
> If you're interested, you could go through the more recent advisories
> (the secu
here we only provide bugfixes for
the latest builds is something we'd do. At the hackathon this was
slightly touched too and was discussed that if we introduce shorter
release cycles, we also should introduce LTS versions.
Regards,
Stefan
smime.p7s
Description: S/MIME Cryptographic Signature
On 28/12/2017 22:37, Daniel Shahaf wrote:
> Stefan wrote on Thu, Dec 28, 2017 at 18:19:12 +0100:
>> On 28/12/2017 04:52, danie...@apache.org wrote:
>>> Author: danielsh
>>> Date: Thu Dec 28 03:52:02 2017
>>> New Revision: 1819391
>>>
>>>
ï¼
>
> ä¸ç®¡æä¹æ ·ï¼å¦æä½ å¨2005å¹´11æ15å·çæ¶åå¨Debian
> GNU/Linuxç³»ç»ä¸é¢è¿è¡ææ°çtestingåè¡çï¼ç¶åéå°è¿ä¸ªé®é¢ï¼é£ä¹è§£å³æ¹æ³å°±æ¯ï¼å°libtool
> 1.5.20çæºä»£ç 使ç¨æ åçâ./configure && make &&
>
>
Committed this by accident directly to publish (rather than staging). If
anybody feels like this should be reverted/discussed/replace with
something else, please reply. Since it's just a dead link correction, I
didn't think it was worth reverting the accidental commit in this case.
Regards,
Stefan
On 19/02/2018 17:16, Julian Foad wrote:
> The 1.10.0-rc1 release artifacts are now available for testing/signing.
> Please get the tarballs from
> https://dist.apache.org/repos/dist/dev/subversion
> and add your signatures there.
>
> Thanks!
Summary
---
+1 to release
Platform
On 29/03/2018 15:17, Julian Foad wrote:
> The 1.10.0-rc2 release artifacts are now available for testing/signing.
> Please get the tarballs from
> https://dist.apache.org/repos/dist/dev/subversion
> and add your signatures there.
>
> Thanks!
Summary
---
+1 to release
Platform
these properties just once
at the top level (i.e. on https://svn.apache.org/repos/asf/subversion)
and remove them on the sub-nodes (i.e. trunk, branches/xxx, tags/xxx,
etc.). This will ensure we have a consistent setting for these project wise.
Thoughts?
Regards,
Stefan
smime.p7s
Description: S
On 04/04/2018 23:47, Branko Čibej wrote:
> On 04.04.2018 23:12, Stefan wrote:
>> Hi,
>>
>> atm we specify the following svn properties on trunk:
>>
>> * bugtraq:url
>> * bugtraq:logregexp
>> * tsvn:logwidthmarker
>> * tsvn:projectlanguag
o I'd
place it right below the first line (after "Apache Subversion
[version].") but then there's already the link to the download page two
lines below... Therefore, I'm quite a bit unsure about whether it
wouldn't be unnecessary and just bloat the mail with yet another link...
So I'll better leave that part for someone else to decide (not going to
argue against it being added).
Regards,
Stefan
smime.p7s
Description: S/MIME Cryptographic Signature
On 18/07/2016 00:08, Stefan wrote:
> On 7/17/2016 22:09, Branko Čibej wrote:
>> On 17.07.2016 20:53, Stefan wrote:
>>> Hi Daniel,
>>>> Stefan wrote on Thu, Jul 14, 2016 at 00:14:31 +0200:
>>>>> Note that SVN 1.7 is EOL and therefore isn't supporte
On 18/11/2016 12:23, Stefan Hett wrote:
> On 7/26/2016 12:13 AM, Stefan wrote:
>>
>> Hi,
>>
>> building SVN 1.8 using sqlite >= SQLite 3.12.0 (amalgamation) and VS
>> 2005+ raises the following error:
>>
>> [...]\sqlite\sqlite3.c(42437): err
On 11/04/2018 09:31, Julian Foad wrote:
> The 1.10.0 release artifacts are now available for testing/signing.
> Please get the tarballs from
> https://dist.apache.org/repos/dist/dev/subversion
> and add your signatures there.
>
> Thanks!
> - Julian
Summary
---
+1 to release
Platform
---
On 05/04/2018 00:09, Stefan wrote:
> On 04/04/2018 23:47, Branko Čibej wrote:
>> On 04.04.2018 23:12, Stefan wrote:
>>> Hi,
>>>
>>> atm we specify the following svn properties on trunk:
>>>
>>> * bugtraq:url
>>> * bugtraq:log
On 15/04/2018 22:56, Julian Foad wrote:
> Branko Čibej wrote on 2018-04-15:
>> On 15.04.2018 21:01, Stefan wrote:
>>> On 05/04/2018 00:09, Stefan wrote:
>>>> I'm not sure if there are other tools around using these. I'm talking
>>>> here TSVN
On 16/04/2018 09:15, Julian Foad wrote:
> Branko Čibej wrote:
>> On 15.04.2018 23:42, Stefan wrote:
>>> On 15/04/2018 22:56, Julian Foad wrote: [...]
>
>>>> - If the properties are not set for a folder, the client should
>>>> search upwards
>>&
not a non-controversial matter so I'm certainly fine
with leaving this for tags as they are, of course. :-)
Regards,
Stefan
smime.p7s
Description: S/MIME Cryptographic Signature
stribution which can be used to debug/test issues yourself
(by shipping symbol files)
Regards,
Stefan
smime.p7s
Description: S/MIME Cryptographic Signature
On 24/06/2018 08:20, Stefan Sperling wrote:
> While we're on the subject of changing the supported release
> process, we could use this opportunity to lower the number of
> signatures required for a release.
>
> While we never failed to meet the current requirements event
On 29/06/2018 17:38, Julian Foad wrote:
> Stefan wrote:
>> new:
>> [...] Before a release is officially made public, it must receive
>> three +1 votes from members of the Subversion PMC. In addition, as a
>> matter of project policy, we require testing and signatur
On 03/07/2018 00:54, Stefan wrote:
> On 29/06/2018 17:38, Julian Foad wrote:
>> Stefan wrote:
>> [...]
>>
>> Do you want to go ahead and update it (after waiting 5 days for
>> anybody else to chime in)?
> Will do Thursday 2018-07-05 to give everybody enough
On 05/07/2018 23:34, Julian Foad wrote:
> Stefan wrote:
>> Done in r1835191.
>
> Great -- except didn't we mean to change it to say "at least one on
> each platform"? It still says "three"...
>
> - Julian
>
>
Correct, my oversight -
sting the release" and "to allow anybody planning
> to test the release" is helpful. I suggest to pick one and drop the other :-)
Done in r1835497 (incl. some more minor rephrasing).
Regards,
Stefan
On 13/07/2018 18:12, Julian Foad wrote:
> Stefan Hett wrote:
>> On 7/13/2018 4:28 PM, Branko Čibej wrote:
>>> On 13.07.2018 16:19, Julian Foad wrote:
>>>>svn ps svn:externals '^/subversion/CHANGES CHANGES' trunk-wc/.
>>> This would be mildly
rsion's
branch but were not yet backported to the previous version
* just reading up old changelog entries out of interest
As stated, none of these are major arguments against changing our
process, but still I'd personally miss a complete changelog. That said,
if the majority of the team is fine with a change, so will I be in the
end and won't argue against it.
Regards,
Stefan
smime.p7s
Description: S/MIME Cryptographic Signature
On 17/07/2018 11:24, Branko Čibej wrote:
> On 17.07.2018 11:17, Stefan wrote:
>> That said, if the majority of the team is fine with a change, so will
>> I be in the end and won't argue against it.
> Correction: not "if the majority of the team etc." but "
3clWmFXRDwm34=
=DKZZ
-END PGP SIGNATURE-
Regards,
Stefan
smime.p7s
Description: S/MIME Cryptographic Signature
qeyA4X4ik0WQLs1NCEcZ5PpMDgDIDPXBi/UjdRai96ND
kJDuwYUYHaB3cn3ROwF5RIosdZv1gbWWGYN/2agMWXZpAOvQvOs=
=mKpT
-END PGP SIGNATURE-
Regards,
Stefan
smime.p7s
Description: S/MIME Cryptographic Signature
- provide early access to versions of SVN while they are in development
- provide a distribution which can be used to debug/test issues yourself
(by shipping symbol files)
Regards,
Stefan
smime.p7s
Description: S/MIME Cryptographic Signature
On 23/08/2018 20:01, s...@apache.org wrote:
> Author: sebb
> Date: Thu Aug 23 18:01:30 2018
> New Revision: 1838746
>
> URL: http://svn.apache.org/viewvc?rev=1838746&view=rev
> Log:
> SVN-4736 - fix gpg command
>
> Modified:
> subversion/site/staging/download.html
>
> Modified: subversion/site/
On 25/08/2018 14:37, Stefan wrote:
> On 23/08/2018 20:01, s...@apache.org wrote:
>> Author: sebb
>> Date: Thu Aug 23 18:01:30 2018
>> New Revision: 1838746
>>
>> URL: http://svn.apache.org/viewvc?rev=1838746&view=rev
>> Log:
>> SVN-4736 - fix g
s.
>> + On Windows you can use the certutil command line tool, for instance.
> Perhaps add the specific --option flags here? Or at least use
> tags to get the monospaced font.
Added more specific usage sample for cerutils (incl. the missing
-tags) in r1839052.
Regards,
Stefan
On 25/08/2018 18:06, sebb AT ASF wrote:
> On 25 August 2018 at 13:44, Stefan wrote:
>> On 25/08/2018 14:37, Stefan wrote:
>>> On 23/08/2018 20:01, s...@apache.org wrote:
>>>> Author: sebb
>>>> Date: Thu Aug 23 18:01:30 2018
>>>> New Revisio
OpenSSL >= 1.0.0.
]]
Regards,
Stefan
Index: INSTALL
===
--- INSTALL (revision 1693972)
+++ INSTALL (working copy)
@@ -955,6 +955,8 @@
*Note: Use "call ms\do_nasm" if you have nasm instead of MASM, or
&
OpenSSL >= 1.0.0.
]]
Regards,
Stefan
Index: INSTALL
===
--- INSTALL (revision 1693972)
+++ INSTALL (working copy)
@@ -955,6 +955,8 @@
*Note: Use "call ms\do_nasm" if you have nasm instead of MASM, or
&
laced with than here.
Regards,
Stefan
1301 - 1400 of 38083 matches
Mail list logo
