| 1 |
On 170314-06:18+0000, J. Roeleveld wrote: |
| 2 |
> On March 14, 2017 6:57:59 AM GMT+01:00, Miroslav Rovis <miro.rovis@××××××××××××××.hr> wrote: |
| 3 |
... |
| 4 |
> >/etc/portage/package.mask/package.mask.file:>=media-libs/mesa-13.0.0 |
| 5 |
> > |
| 6 |
> >( Btw. how does one search for only recent bugs, anybody? ) |
| 7 |
> |
| 8 |
> To see most recent bugs, sort on ID. |
| 9 |
> To see most recently modified bug, sort on changed. |
| 10 |
> |
| 11 |
> (Click on the column headers) |
| 12 |
|
| 13 |
Yes, it was right there for my understanding... Thanks! |
| 14 |
|
| 15 |
Can an address this long be sent, and received, in an email correctly? : |
| 16 |
"https://bugs.gentoo.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&field0-0-0=alias&field0-0-1=short_desc&order=changeddate DESC%2Cbug_id DESC&query_format=advanced&type0-0-0=substring&type0-0-1=substring&value0-0-0=mesa&value0-0-1=mesa" |
| 17 |
|
| 18 |
Anyway, it's, currently, 15 bugs that have the status changed with the latest |
| 19 |
timestamp somewhere in 2017. What's happening in that development? |
| 20 |
|
| 21 |
Maybe what happens will be something like what happened with syslog-ng, where |
| 22 |
we kind of have this mid-2014 created ebuild (only be looking in Changelog which I wasn't able to find on the gitweb, but in portage: |
| 23 |
|
| 24 |
# cat /usr/portage/app-admin/syslog-ng/ChangeLog-2015 |
| 25 |
... |
| 26 |
*syslog-ng-3.4.8 (06 Jun 2014) |
| 27 |
|
| 28 |
06 Jun 2014; Michael Sterrett <mr_bones_@g.o> +syslog-ng-3.4.8.ebuild: |
| 29 |
version bump for 3.4 branch |
| 30 |
|
| 31 |
17 May 2014; Michael Sterrett <mr_bones_@g.o> -syslog-ng-3.4.2.ebuild, |
| 32 |
-syslog-ng-3.5.4.ebuild: |
| 33 |
clean old |
| 34 |
... |
| 35 |
|
| 36 |
): |
| 37 |
|
| 38 |
https://gitweb.gentoo.org/repo/gentoo.git/tree/app-admin/syslog-ng/syslog-ng-3.4.8.ebuild |
| 39 |
for almost forever... |
| 40 |
|
| 41 |
( |
| 42 |
I still have: |
| 43 |
# grep -r syslog-ng /etc/portage/p* |
| 44 |
/etc/portage/package.keywords/package.keywords.file:=app-admin/syslog-ng-3.4.8 |
| 45 |
/etc/portage/package.mask/package.mask.file:>=app-admin/syslog-ng-3.5.6 |
| 46 |
# |
| 47 |
because there really were issues: |
| 48 |
app-admin/syslog-ng-3.6.2: scary time stamp jumps |
| 49 |
https://bugs.gentoo.org/show_bug.cgi?id=533328 |
| 50 |
and: |
| 51 |
Kernel log message time drift #121 |
| 52 |
https://github.com/balabit/syslog-ng/issues/121 |
| 53 |
which I described in: |
| 54 |
Syslog-ng from Delay Logging to BrokenPipe/no Logging |
| 55 |
http://forums.gentoo.org/viewtopic-t-1001994.html |
| 56 |
) |
| 57 |
|
| 58 |
No time to investigate mesa... Anybody can give us a summary of what's really |
| 59 |
going on upstream with mesa? |
| 60 |
|
| 61 |
-- |
| 62 |
Miroslav Rovis |
| 63 |
Zagreb, Croatia |
| 64 |
https://www.CroatiaFidelis.hr |
Archives