Greetings again,
#1
Changes rejected:
mini-httpd_1.30-4.dsc: Invalid size hash for mini-
httpd_1.30.orig.tar.gz:
According to the control file the size hash should be 43469,
but mini-httpd_1.30.orig.tar.gz has 43889.
If you did not include mini-httpd_1.30.orig.tar.gz in your upload, a
different
Hi Alexandru,
Alexandru Mihail writes:
>> # Fix git config email and gpg identity, then
[snip]
>>
> I fixed my git config and redid the tag as discussed above
Thanks!
>> Sorry I only noticed this when I manually inspected and compared the
>> tag
> Yeah, sorry too :)
> I'll be going on
Hello Nicholas,
> Did you realise that you're still committing using your protonmail.ch
> address (and presumably GPG identity)? Early in this process you
> switched to a gmail address, and I understood that that was the one
> that
> you would be using for for your Debian work.
Damn, it
Hello Alexandru,
Thank you for the ping :)
Alexandru Mihail writes:
> I've commited and pushed the changes to the remote I was using for the
> MR so far:
> commit:
> https://salsa.debian.org/alexandru_mihail/mini-httpd/-/commit/fc7c4f664dc1369b1bf5d46c8c9b7aa11de68407
>
>
> But I think I may
Hello,
Gently pinging about my last mail.
Sorry for nagging; I think we both want this release finalized and to
crack a cold one admiring our work :)
> I've commited and pushed the changes to the remote I was using for
> the
> MR so far:
> commit:
>
Hello Nicholas,
> They're about the same for me. Honestly I'd prefer to do a git
upload
> at this time, and save the GPG key discussion for your next upload.
> We can use dput and mentors then, and I think we'll both agree that
> we've both worked hard enough for this first upload haha.
Hi Alexandru,
On Fri, 18 Aug 2023 02:07:46 +0300 Alexandru Mihail
wrote:
> >After that, let's talk about uploading. Think about whether you'd
> >like
> >to start gaining practice with dput (or dput-ng), or whether you'd
> >like
> >me to sponsor directly from git.
> I'm pretty ambivalent to
Hello, Nicholas !
>Thanks again for your work! I submitted a second (I think we're at
>the
>second one) gitlab review here:
Fixes for review items are commited :)
I cannot yet review the untested patch about VHOSTING as I cannot
replicate (or maybe miss something in my mini_httpd.conf ?) the bug.
Hi Alexandru,
Thanks again for your work! I submitted a second (I think we're at the
second one) gitlab review here:
https://salsa.debian.org/debian/mini-httpd/-/merge_requests/2/diffs
Summary:
1. One minor nitpick for multi-maint changelog format
2. Two lines that I can't make sense of
I committed the fixes, after reading your review on salsa.
Please take a look at
https://salsa.debian.org/debian/mini-httpd/-/merge_requests/2/diffs?commit_id=f89931149c0c7105585061cbfbdcc2cd2ac212b5
when you can.
Cheers,
Alexandru
signature.asc
Description: This is a digitally signed message
Hello Nicholas,
I was in the process of writing this mail when I just saw your gitlab
activity.
>+1 and where can I see this new work?
git checkout 1.5c
git diff 1.4.2 -- conf/httpd.conf-dist | grep -B 2 -A 4 " VirtualHost "
+#BindAddress 127.0.0.1
+
+# VirtualHost allows you to look differently
Alexandru Mihail writes:
> I've redone some diffs, too. Also, my previous statement of 1.4.2 httpd
> makes no sense, because, at a quick glance, I could observe the
> introduction of virtual hosting in httpd 1.5*, which mini-httpd had
> from the beginning. You're right to advise to look at 1.5*
Hello Nicholas,
>Remember my Wed, 21 Jun 2023 email (as well as the one with the
>diagram)?
I remembered this also:
>"...then if httpd 1.15 is older then mini-httpd 1.30, you must choose
>1.15. Meanwhile, Robert McCool's copyright still exists in 1.15 even
>if he hasn't made a contribution since
Hi Alexandru,
Alexandru Mihail writes:
> MR filed:
> https://salsa.debian.org/debian/mini-httpd/-/merge_requests/2
Thanks. We can rebase and squash at the end, but for now please don't
force push.
>>Oh man, yeah, hello early days of the internet! All you need now is
>>some MIDI files and
Hi Nicholas,
MR filed:
https://salsa.debian.org/debian/mini-httpd/-/merge_requests/2
>Does that link really work? Are you sure it's not this one?
I have no idea what automagically happened, somehow the first one
worked for me, but now does not. :) Using yours (thanks!).
>The copyright info
Hello Alexandru,
Thank you for this latest update. Notes follow inline. Please count
the TODO items, resolve 4/4, and file an MR.
Alexandru Mihail writes:
> Hello again, Nicholas !
>
> ---
> debian/copyright:
>
> Files:
Hello again, Nicholas !
---
debian/copyright:
Files: htpasswd.c htpasswd.1
Copyright: 1993-1994 Rob McCool
Copyright: 1997 Jef Poskanzer
License: BSD-2-clause
Comment: htpasswd* are mostly NCSA licensed.
RobMcCool's
Hi Alexandru,
For brevity I've omitted the parts that look good.
Alexandru Mihail writes:
> RobMcCool's copyright was traced from a git repository which
> imported NCSA httpd (which was verified to be precise).
> Multiple commits by RobMcCool on HEAD
> show his contributions on the files
Hello again,
Public key is up:
https://keys.openpgp.org/vks/v1/by-fingerprint/CEC2B41FDE5A803B6B08C01471CA8C5A78AA77BB
I also imported your key into my gpg keyring.
Thanks a lot !
Alexandru Mihail
signature.asc
Description: This is a digitally signed message part
Hello Nicholas,
No problem about the later reply :)
>Also, you'll need to
>say a few words about how you established copyright--a very short too
>long didn't read version of this thread. Find out how to do this at
>§5.1 of the following (read the short list of fields, and you'll see
>which one it
Hi Alexandru,
Alexandru Mihail writes:
> After a bit more research into how other projects treat NCSA bits I'd
> propose something along the lines of:
>
> debian/copyright:
> Files: htpasswd.c
Yes, and htpasswd.1.
> Copyright: 1993-1994 Rob McCool
> Copyright: 1997 Jef Poskanzer ?
Yes, and
Hellow Alexandru,
Alexandru Mihail writes:
> Hello Nicholas,
>>That's ok, you don't need to find the original version. Remember
>>that
>>it's a fork and child relationship,
>
> Yes, I'm terribly sorry, I'm familiar with the fork-child relationship
> but I still found your analogy very helpful
Hello again,
>In short, considering debian-legal's input, should I mention the NCSA
>copyright notice in debian/copyright for Files: htpasswd.c, adding a
>separate License: NCSA field to clarify the provenance of said source
>?
After a bit more research into how other projects treat NCSA bits
Hello Nicholas,
>That's ok, you don't need to find the original version. Remember
>that
>it's a fork and child relationship,
Yes, I'm terribly sorry, I'm familiar with the fork-child relationship
but I still found your analogy very helpful and concise, I might
present it to my interns (if that's
Hi Alexandru,
Alexandru Mihail writes:
> After yet some more software archaeology, I've uncovered some more
> rusty HTML 1.0 documents which are of interest to our dilemma.
> Apparently, NCSA HTTPd Acknowledgements as of 7-14-95 state:
> "Thanks to:
> Robert McCool
> For developing NCSA
Hello Nicholas,
> Because of the ambiguity as to which license (and license version)
> applies, and because Debian's copy of mini-httpd is now the defacto
> upstream, I insist that the applicable license is also documented.
I agree, we need to document the NCSA bits.
> Do you think that httpd
Hello Alexandru,
Alexandru Mihail writes:
> Hello Nicholas,
> debian-legal replied, I could only find occurences of Rob McCool's NCSA
> derived code in htpasswd.c as well. The NCSA license states we might(not
> must) include a copy of their short legal excerpt on derivative works (and
>
Hello Nicholas,
debian-legal replied, I could only find occurences of Rob McCool's NCSA derived
code in htpasswd.c as well. The NCSA license states we might(not must) include
a copy of their short legal excerpt on derivative works (and mini-httpd is one)
Maybe we should include a mention of said
Hello,
Posting the debian-legal original post link here for easy reference:
https://lists.debian.org/debian-legal/2023/06/msg00019.html
Best,
Alexandru
--- Original Message ---
On Thursday, June 22nd, 2023 at 4:46 PM, Alexandru Mihail
wrote:
> Hello Nicholas,
> Hehe, thanks a lot
Hello Nicholas,
Hehe, thanks a lot :D
>
> Wow, you are good at this! :D
>
I mailed debian-legal and am waiting for a reply.
Cheers,
Alex
--- Original Message ---
On Wednesday, June 21st, 2023 at 9:52 PM, Nicholas D Steeves
wrote:
> Hi Alexandru,
>
> Thanks for the ping. I had
Hi Alexandru,
Thanks for the ping. I had forgotten that I had a WIP draft.
Alexandru Mihail writes:
>> > remember the original NCSA httpd licence. P.S. It feels like
>> > archaeology to find missing documentation for something from the > > dawn
>> > of
>
> Eureka !
> I present the original
Hello,
Gently pinging in regard to the NCSA license situation
Best,
Alexandru
On Fri, Jun 16, 2023 at 10:54, Alexandru Mihail
<[alexandru_mih...@protonmail.ch](mailto:On Fri, Jun 16, 2023 at 10:54,
Alexandru Mihail < wrote:
> Hello again Nicholas,
> I hope this mail finds you well.
>
>> >
Hello again Nicholas,
I hope this mail finds you well.
> > remember the original NCSA httpd licence. P.S. It feels like
> > archaeology to find missing documentation for something from the > > dawn of
Eureka !
I present the original NCSA httpd license in its purest form after some
software
Hello again,
> I hope that the forests aren't burning, wherever you are.
>
> Take care,
Oh damn, I really hope you and your family are going to be safe if you're
facing wildfires near you..
Here in Eastern Europe it's not really that much of an issue, thankfully.
> remember the original NCSA
Hello Alexandru,
Alexandru Mihail writes:
> Hello Nicholas,
>
>> Sorry, my mistake. I meant to write "debian/copyright". One or more
>> entries in the copyright file conflicts with upstream evidence.
>
> No problem, I think I found what you were referring to and corrected our
> copyright,
Hello Nicholas,
> Sorry, my mistake. I meant to write "debian/copyright". One or more
> entries in the copyright file conflicts with upstream evidence.
No problem, I think I found what you were referring to and corrected our
copyright, upstream is right. I documented the changes in the
Hi Alexandru,
Alexandru Mihail writes:
>> 2. I found an inaccuracy in the upstream sections of debian/changelog;
>> please fix it. Plain old grep or manual header check should be enough
>> to spot this.
>
> Can you please elaborate a bit ? Are you referring to my changelog entry or
> any
Hello Nicholas,
> Nice catch, and if someone using OpenRC is affected, I hope that person
> will be willing to provide a patch for what sounds like a corner-case.
Thanks, I hope so as well
> 1. What is the purpose of the dh_installsystemd override? (hint: see the
> dh_installsystemd man page
Hi Alexandru,
Alexandru Mihail writes:
> Turns out bullseye-backports lintian (2.115.1~bpo11+1) only checks for 4.6.1
> Standards, therefore a more serious error (depends-on-obsolete-package
> lsb-base) was reported by sid lintian.
> Upon inspecting the situation (lsb-base is now a
Hello again,
Uploaded again to mentors.
Turns out bullseye-backports lintian (2.115.1~bpo11+1) only checks for 4.6.1
Standards, therefore a more serious error (depends-on-obsolete-package
lsb-base) was reported by sid lintian.
Upon inspecting the situation (lsb-base is now a transitional empty
Hi,
Thanks everyone for the input !
Indeed the forking service type is the correct one for this package as daemon()
is called as part of the initialization sequence. (if daemon() is not
available, plain fork() is called anyway)
I've adjusted debian/rules, taking into consideration Lorenzo's
Alexandru Mihail writes:
> As for the old bugs, at least #491078 and #1018900 are stil present, I
> shall test a user submitted patch for the first one.
Thank you for taking the time to verify and document this. While not
required, it would also be nice if #491078 was noted in the appropriate
Hi Lorenzo, Thank you for the help with reviewing :)
Hi Alexandru, Reply follows inline with two hints.
Lorenzo writes:
> On Thu, 01 Jun 2023 12:05:51 +
> Alexandru Mihail wrote:
>
>> I've uploaded again to mentors, the (now gone) lintian warning
>> complained about missing the SystemD
Hi Alexandru,
On Thu, 01 Jun 2023 12:05:51 +
Alexandru Mihail wrote:
> Hi Nicholas,
> I've uploaded again to mentors, the (now gone) lintian warning
> complained about missing the SystemD service for the package. I've
> added one from scratch and upon initial testing it performs OK. I
>
Hi Nicholas,
I've uploaded again to mentors, the (now gone) lintian warning complained about
missing the SystemD service for the package. I've added one from scratch and
upon initial testing it performs OK.
I modified debian/rules to take the service into consideration though this
raises some
Hello again, Nicholas
ProtonMail wins this time, I shall send directly to the bug as of now.
> Since you're comfortable with git, please consider creating a Salsa
> account and continuing to maintain the package in the Debian (previously
> collab-maint) group. Here's more info on what that
Hello Alexandrus,
It appears that your mail user agent (possibly webmail) is encrypting
emails to me when you "reply all" to the bug; the effect is non-public.
It may be that the only way to fix that effect is to either 1. not CC me
(just send to the bug) 2. Make that interface forget my key,
Hello Nicholas,
Of course, please quote the first email at the bug. My apologies for omitting
to reply all :)
Best,
Alexandru
On Tue, May 30, 2023 at 23:17, Nicholas D Steeves <[s...@debian.org](mailto:On
Tue, May 30, 2023 at 23:17, Nicholas D Steeves < wrote:
> Hi Alexandru,
>
> Please take
Hi Alexandru,
Please take care to reply in cleartext to this RFS bug (#1036751), using
"reply to all" or "reply to list", because it's expected that most
Debian development and discussion happens in the open.
It's also important to have evidence of progress so that someone's bug
cleanup script
Hello again, I have reuploaded mini-httpd to mentors as per your
recommandations Nicholas. Please see my last mail for some questions regarding
upstream/VCS.
Regards,
Alexandru Mihail
Control: owner -1 !
Control: tag -1 +moreinfo
Control: block 927950 by -1
Hi Alexandru,
Welcome! I'd like to sponsor your work, and I hope that attention to
detail doesn't annoy you. Please take a look at the questions in the
following reply:
Alexandru Mihail writes:
> * Package name :
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "mini-httpd":
* Package name : mini-httpd
Version : 1.30-4
Upstream contact : Jef Poskanzer j...@mail.acme.com
* URL :
52 matches
Mail list logo
