Given that #Gentoo #Bugzilla mail is down for three days now, if anybody needed to search for bugs changed since Friday:
https://bugs.gentoo.org/buglist.cgi?f1=delta_ts&o1=greaterthan&order=changeddate&v1=2025-07-11
bugs.gentoo.orgBug List
#bugzilla
0 posts0 participants0 posts today
Replied in thread
@Natanox i kept miss-identifying the "proper" components on bug-/issue-/feature trackers (#github / #bugzilla / #Canonical #Ubuntu #launchpad), so i've switched to hash-tagging my fave projects on #SocialMedia, instead.
Instead of getting "my issue" rejected or closed as "irrelevant", because i failed to ID&target the correct COMPONENT, i just toot about it on the #Fediverse, let #Karma sort it out! 
I consider this a win-win "shituation"! 
Filed Bug 287268 to add -devel version of #nvidia GPU driver on #FreeBSD #Bugzilla. This is planned to track basically New Feature Branch (NFB) of drivers, but if Production Branch of driver has larger version number, temporarily switches to it until new NFB is released upstream.
Note that Beta Branch of drivers are not tracked, although supports for them are incorporated in-tree in preparation of new NFB release, as versions on -devel branch.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287268
Now it's at 575.57.08.
https://www.nvidia.com/en-us/drivers/details/245539/
Currently, pruning of deprecated ports seems to be ongoing (and some of which are requested to be reverted), causing category Makefile to be modified. So holding to open review on Phablicator to see there could be more or not for maybe 1 or 2 more days.
bugs.freebsd.org287268 – [NWE PORT] x11/nvidia-driver-devel, x11/linux-nvidia-libs-devel, graphics/nvidia-drm[,510,515,61,66]-kmod-devel: Add new port
Gdyby ktoś potrzebował zaktualizować tytuły setek zgłoszeń na Bugzilli z automatu, np. podmieniając starą nazwę paczki na nową, to proponuję mój nowy wynalazek… bugsed!
https://github.com/projg2/bugsed
A, i wszystkie paczki #LLVM w #Gentoo są teraz w kategoriach llvm-*/.
GitHubGitHub - projg2/bugsed: A quick tool to perform search-and-replace over bug summaries on BugzillaA quick tool to perform search-and-replace over bug summaries on Bugzilla - projg2/bugsed
Ever needed to update summaries of hundred of #Bugzilla bugs automatically, e.g. by updating the package name? I give you… bugsed!
https://github.com/projg2/bugsed
Oh, and all #LLVM packages in #Gentoo are now in llvm-*/ categories.
GitHubGitHub - projg2/bugsed: A quick tool to perform search-and-replace over bug summaries on BugzillaA quick tool to perform search-and-replace over bug summaries on Bugzilla - projg2/bugsed
It's a few days late, But this year is our 10th anniversary of the #WikimediaFoundation started it's final steps in the #Bugzilla to #Phabricator migration, On the 2014-11-21 the import of the old Bugzilla archives into the Phabricator started, access to Phabricator to the public was reopened 2014-11-24.
Replied in thread
Looks like I’ll be signing up for #bugzilla, I was able to search through their reports and found this has been reported as recently as this May, but not reproduced. Once again, thank you @thunderbird and a shoutout to @killyourfm who’s recent work and efforts on their marketing team got me to reinstall and make it my default client once again.
Continued thread
After Gavin (@_calmdowndear ) asked about password managers checking and warning for http connections, I did some tests; see https://infosec.exchange/@ErikvanStraten/113183533717083748.
In addition to those and my original test, in the email to myself I replaced "example.com" by both:
http:⧸⧸192.168.178.1 (*)
and
https:⧸⧸192.168.178.1 (*)
(*) I'm using the Unicode '⧸' here instead of ASCII '/' to prevent Mastodon from hiding the protocol prefix (and turning it into a clickable link).
If I follow the instructions in the email (fully close Firefox) and tap http:⧸⧸192.168.178.1 , then I (erroneously) get to see the padlock without strike through.
I can then use the iOS autofill function to fill in the password without being warned that an http connection is being used. Even after autofilling the password, Firefox has not changed the padlock as can be seen in the left screenshot below.
OTOH, if I follow the instructions in the mail but tap https:⧸⧸192.168.178.1 instead (and then tap "Advanced"), I *do* get warned because a self signed certificate is being used (see the screenshot at the right).
Firefox iOS vulnerability
Nearly three months ago I reported a vulnerability in Firefox for iOS to Mozilla (https://bugzilla.mozilla.org/show_bug.cgi?id=1904885) - it remains unfixed while my "bumps" do not seem to wake anyone up (yes that's frustrating - and I encounter that everywhere).
VULNERABILITY
The vulnerability appears to be that if Firefox is opened with an http link "on the command line", while the last page open was using https, it gets confused and erroneously shows a https padlock for an http website.
CONDITIONS TO REPRODUCE
It's easy to reproduce, provided that:
• Firefox is configured as your default browser (on iOS or iPadOS)
• You use an app to read emails that is not webbased (Apple's mail app works fine).
REPRODUCE VIA MAIL
One way to te reproduce is to send yourself a ("phishing") email with the following instructions:
«
1) Tap bleepingcomputer.com to open it;
2) For security reasons (XSS attacks etc.), now close Firefox (make sure to swipe its window off screen);
3) Tap example.com to open it.
»
(Instead of example.com you can use any website that does not automatically forward your browser to an https connection to the website, such as http://http.badssl.com).
SYMPTOMS
Firefox for iOS now reopens, shows "example.com/" in the address bar *and* a padlock icon indicating an https connection.
However, it is NOT using an https connection, but http. The padlock is not trustworthy.
PICS OR IT AINT SO
See the screenshots below: the second one is after tapping the padlock icon (or tap in the address bar to see the -selected- URL start with http://).
FULL POC
Since it's not yet 90 days ago (but rather 88) I'll wait a bit with publishing a full phishing PoC.
Replied in thread
I don’t expect much has changed since I wrote https://lwn.net/Articles/967922/
For personal independence of development is IMHO better what we have right now working … #SourceHut or #Cgit, #Mailman, #Bugzilla on your own server.
lwn.netRadicle: peer-to-peer collaboration with Git [LWN.net]
#Bugzilla tarballs are rolled, patches have been generated, FTP upload and website changes are staged and ready to upload, and now my problem is that I just can't type fast enough writing the release announcement. We're so close! Probably another hour just to be safe.
Many thanks to an anonymous donor who just contributed $25 to #bugzilla !
If you can spare a few dollars or just want to see how we're doing towards our fundraising goals, visit https://bugzilla.org/donate
bugzilla.orgRedirecting…
Replied in thread
@dee Nice! This is a feature I used a lot in #Bugzilla times at #Wikimedia. https://wiki.mozilla.org/BMO/UserGuide/Filtering_Bugzilla_Email_in_GMail
wiki.mozilla.orgBMO/UserGuide/Filtering Bugzilla Email in GMail - MozillaWiki
Інтеграція з Jira та GitHub, 50 ГБ хмарного простору. За що TestRail цінують тестувальники https://itc.ua/ua/articles/integratsiya-z-jira-ta-github-50-gb-hmarnogo-prostoru-za-shho-testrail-tsinuyut-testuvalnyky/ #Програмнезабезпечення #управліннятестуванням #TestRailProfessional #Партнерськийпроєкт #FastTrackEditing #TestRailPlatinum #PivotalTracker #TestRailCloud #VisualStudio #Lighthouse #Тестування #Bugzilla #Softlist #TestRail #Redmine #GitHub #Rally #Jira
ITC.ua · Інтеграція з Jira та GitHub, 50 ГБ хмарного простору. За що TestRail цінують тестувальникиУ сучасному високотехнологічному суспільстві попит на якісне програмне забезпечення постійно підвищується, вимоги до нього теж зростають. Що робить тестування ПЗ одним із ключових процесів у розробці, адже ефективне тестування має вирішальне значення для забезпечення безпомилкової роботи програм і задоволення потреб ринку. Щоб зменшити ймовірність пропускання помилок у ході тестування, вкрай важливо використовувати відповідні інструменти. Вони […]
@allanday describes some good methods to keep on top of issue tracking in the new GNOME Handbook.
blogs.gnome.orgGNOME maintainers: here’s how to keep your issue tracker in good shape – Form and Function
Live on stream right now! Working on preparation for the upcoming #Bugzilla 4.4.14, 5.0.4.1, and 5.2 releases.
TwitchBugzillaProject - TwitchWhat's new in Bugzilla 5.2? Miscellaneous prep for impending release.
Progress towards releases:
Remaining #bugzilla release blockers:
* 4.4.14: 7 bugs
* 5.0.4.1: 7 bugs
* 5.2: 8 bugs
* 5.3.3: 6 bugs
* 5.9.1: 11 bugs
* Total: 29 bugs (many of them affect multiple branches, so show up multiple times in the above list)
TechHubBugzilla (@bugzilla@techhub.social)Progress towards releases:
Remaining #bugzilla release blockers:
* 4.4.14: 9 bugs
* 5.0.4.1: 8 bugs
* 5.2: 15 bugs
* 5.3.3: 6 bugs
* 5.9.1: 13 bugs
* Total: 35 bugs (many of them affect multiple branches, so show up multiple times in the above list)
Bug tracker for RDE.
RDE is already quite big project with a few subprojects and it's hard to track feature requests, reports, milestones, their dependencies and to collocate and organize them properly and share publicly.
That's why for last few weeks I was looking at different project management/bug tracking solutions.
From what I found so far it seems that Bugzilla is the best option at the moment.
Thoughts?
BugzillaBugzillaThe software solution designed to drive software development Bugzilla lets you plan, organize and release software on your own teams' schedule...
We'll be streaming on Saturday April 6 at 1pm EDT/10am PDT/5pm UTC to take another dive into the #Bugzilla 5.2 release notes.
Twitch: https://www.twitch.tv/bugzillaproject
YouTube: https://www.youtube.com/watch?v=iKjCBxkrJmk