From: Adolf Belka <adolf.belka@ipfire.org>
To: "IPFire: Infrastructure-List" <infrastructure@lists.ipfire.org>,
"IPFire: Development-List" <development@lists.ipfire.org>
Subject: Permission Denied message for uploadsrc and ssh into builders
Date: Mon, 8 Sep 2025 12:59:15 +0200 [thread overview]
Message-ID: <1f13ce21-4526-48b4-bb2e-a2bf09898afd@ipfire.org> (raw)
Hi All,
EDIT:I added the development list to the To: list as I found that I could not find infrastructure in the email lists so wasn't sure if it still existed.
I am not sure when this would have started as it is a few days since I did an uploadsrc but when I tried it today I got asked as usual for bonnietwin@people.ipfire.org's password and I got the following message
Permission denied, please try again.
However access into IPFire People with the same username and password is still working fine so nothing changed with those credentials but they are no longer accepted.
Any idea what could have happened or changed?
At the moment it is not a big thing but if I find any new updates I won't be able to upload the sourcefile and also if there is an update that has different rootfiles between x86_64 and aarch64 then I won't be able to run those builders to get the rootfile results.
Regards,
Adolf.
reply other threads:[~2025-09-08 10:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1f13ce21-4526-48b4-bb2e-a2bf09898afd@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
--cc=infrastructure@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox